-----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 [EMAIL PROTECTED] -----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/
