Message-ID: <457C8476.1000203@byu.net>
Date: Sun, 10 Dec 2006 15:04:38 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com, evans AT aps DOT anl DOT gov
Subject: Re: Postinstall Problem with 01bash.bat
References: <000601c71c99$915e7850$3c3d36a4 AT Yoda>
In-Reply-To: <000601c71c99$915e7850$3c3d36a4@Yoda>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Kenneth Evans, Jr. on 12/10/2006 1:27 PM:
> Hi,
> 
>      When I run setup.exe it gets to 99% completion and hangs on:
> 
> /etc/postinstall/01bash.bat

What do the following say?

$ ls -l /bin/sh.exe /bin/bash.exe
$ bash --version
$ sh --version

> 2. Running setup.exe from a command shell with only c:\Cygwin\bin in the
> PATH.

Should not make a difference.  setup.exe is not a cygwin executable, so it
 does not depend on cygwin/bin being in or out of the PATH.

> 
> 4. Running "cmd.exe /c C:\Cygwin\etc\postinstall\01bash.bat" in the command
> shell.

That's exactly what setup.exe does.

Other things to check - are you running a buggy driver?  (Known culprits
include Agnitum outpost, Logitech webcam, McAfee virus products, but this
list is not comprehensive).

> 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?
 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'.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFfIR184KuGfSFAYARAnFjAKClZv+70RTJxPWaWTjnObysLdP+agCeJAPz
dYI2QIE/fwEFhVg6EhAh0aw=
=jLDU
-----END PGP SIGNATURE-----

--
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/