X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
X-Authority-Analysis: v=1.0 c=1 a=lQYmWzwztX0A:10 a=xe8BsctaAAAA:8  a=hw8VYAMqJJ6wjCNKei0A:9 a=smfAD4XVN_qnOBGFJrYA:7  a=JzPRS2N6tLX-F0JME3S2GNmqIjQA:4 a=eDFNAWYWrCwA:10 a=rPt6xJ-oxjAA:10
Message-ID: <47DBC548.6090506@byu.net>
Date: Sat, 15 Mar 2008 06:47:04 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: ash/bash postinstall dance [Was: Cygwin doesn't install on Windows    Server 2008 (x64).]
References: <E6F7A586E0A3F94D921755964F6BE00601674268 AT EXCHANGE2 DOT cs DOT cornell DOT edu> <47DB6508 DOT 50E4B9C9 AT dessent DOT net>
In-Reply-To: <47DB6508.50E4B9C9@dessent.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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

According to Brian Dessent on 3/14/2008 11:56 PM:
| That brings up an interesting, and I think valid question -- Why are we
| still catering to systems that might be stuck in 2005 with an ash
| /bin/sh?

Hmm - maybe it is time that we could assume that such systems have been
phased out.  At any rate, the release of cygwin 1.7.0 is an ideal time for
making any drastic cleanup changes, where we can intentionally change
package layouts compared to old versions.

|  If we change the bash binary package to extract both /bin/sh
| and /bin/bash (the setup program expands hard links in the tarball as
| copies, so we can use a hard link there to save space) then that means
| that we don't have to worry about copying anything to sh.exe anymore, it
| will always be in sync with bash.exe.

Except that the bash postinstall tries to do one other thing - it caters
to users who prefer ksh, zsh, or the relatively recent posh as their
/bin/sh.  While it is not the default installation, I also don't want to
forbid it.  In other words, bash tries to upgrade /bin/sh only if it can
identify it as ash or bash, and not if it is some other shell.

- --
Don't work too hard, make some time for fun as well!

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

iEYEARECAAYFAkfbxUgACgkQ84KuGfSFAYBWgACfT7SxeAWcg3ujoei9kziu/TrS
mfQAniB+gN0yNNLgOlfdrq5UhVylDIEO
=ndK2
-----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/