X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A8AC26D.2010707@cygwin.com> Date: Tue, 18 Aug 2009 11:02:05 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: No etc/passwd (was) Re: (everything!) command not found References: <4A7EE547 DOT 1070309 AT agora-net DOT com> <4A7F9E88 DOT 2060800 AT cygwin DOT com> <4A859905 DOT 9060206 AT agora-net DOT com> <20090814173519 DOT GB10200 AT ednor DOT casa DOT cgf DOT cx> <4A882621 DOT 90104 AT agora-net DOT com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 8/16/2009 12:35 PM, Mark J. Reed wrote: > On Sun, Aug 16, 2009 at 11:30 AM, DY wrote: >> In case anyone else ever needs this, if you install cygwin, then get command >> not found for everything, you need to:[set CYGWIN_HOME and add >> %CYGWIN_HOME%\bin to PATH]. > > That's quite strange; neither of those should be necessary. I have > no CYGWIN_HOME set, and my Cygwin bin dir is not in my Windows PATH. > (The latter is handy if you want to run Cygwin commands from the > Windows shell, of course). Thank you Mark for making this point. Just in case there's any confusion, the CYGWIN_HOME environment variable is not used by Cygwin. It does not need to be set for proper operation. And Cygwin's path only needs to be in the Windows environment if you want/need to run Cygwin commands from the Windows command prompt shell (though this is often awfully convenient). So Mark is spot on with his comments here. Clearly the source of the issues with this installation is wrapped up in the postinstall scripts. Why they failed to run isn't clear based on the information given so far. It would still be nice to see the 'cygcheck' output recommended by and it might be particularly useful to see the original 'setup.log.full', though I expect we'd have to settle for a recent or current version now... There's been a good chunk of useful suggestions generated in this thread so far Debra. Clearly some you have looked at but some seems to have slipped through the cracks. It might prove useful to you if you reviewed the whole thread again. Based on your first email message, I did not get the impression that you moved any of the data from your XP machine to Vista but if you did do this (via clone/ghost or other mechanism that preserves ownership of the data), you may have permissions problems if you're overwriting the Cygwin installation you had on XP. If this describes your environment, I'd recommend removing your Cygwin installation and reinstalling. You can copy over what you want of the old (and adjust permissions and ownerships) once Cygwin is in place. -- Larry -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple