X-Spam-Check-By: sourceware.org Date: Sun, 10 Dec 2006 23:33:57 -0500 (EST) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Eric Blake cc: cygwin AT cygwin DOT com, evans AT aps DOT anl DOT gov Subject: Re: Postinstall Problem with 01bash.bat In-Reply-To: <457C8476.1000203@byu.net> Message-ID: References: <000601c71c99$915e7850$3c3d36a4 AT Yoda> <457C8476 DOT 1000203 AT byu DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Sun, 10 Dec 2006, Eric Blake wrote: > According to Kenneth Evans, Jr. on 12/10/2006 1:27 PM: > [snip] > > setup.full.log from the last run (which was from the local directory and > > cancelled) is: > > Please attach, rather than sending files inline, to avoid false positives > when searching mailing list archives. > > > > > Path: C:\Program Files\Compaq\Compaq Management Agents\Dmi\Win32\Bin > > C:\Windows\system32 > > C:\Windows > > C:\Windows\System32\Wbem > > C:\Program Files\Common Files\Adaptec Shared\System > > C:\Exceed\Accessories\ > > C:\Program Files\Resource Pro Kit\ > > C:\Exceed\Security\Kerberos\ > > C:\Program Files\Microsoft SQL Server\90\Tools\binn\ > > C:\Program Files\SSH Communications Security\SSH Secure Shell\ > > C:\Exceed\Accessories\ > > . > > C:\Program Files\QuickTime\QTSystem\ > > n:\epics\base314\bin\win32-x86 > > n:\epics\extensions\bin\win32-x86 > > c:\bin > > c:\GNU\emacs\bin > > c:\Cygwin\bin > > c:\CVS > > c:\Exceed\Exceed > > You have quite a few things in your path. Could any of them be providing > an alternate /bin/sh, even though this cygcheck output didn't detect one? Indeed. The following looks pretty suspicious: > > C:\Program Files\SSH Communications Security\SSH Secure Shell\ > Also, when you ran setup.exe, did you have an instance of bash or sh > already running? > > Other than that, all I can suggest is manually doing what 01bash.sh would > have done, which is roughly 'cp /bin/bash.exe /bin/sh.exe'. Which, of course, cannot be run from an instance of /bin/sh... However, that still does not explain why the postinstall script was hanging. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/