X-Spam-Check-By: sourceware.org Message-ID: <4453F6C1.9000507@byu.net> Date: Sat, 29 Apr 2006 17:29:05 -0600 From: Eric Blake User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Error on /bin/sh -login: "cannot remove /bin/sh.exe: Permission denied" References: <445122D6 DOT 1030409 AT gtri DOT gatech DOT edu> In-Reply-To: <445122D6.1030409@gtri.gatech.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Webb Roberts on 4/27/2006 2:00 PM: >> I will also try to clean up the profile script to short-circuit when you >> are running /bin/sh instead of /bin/bash > > One thing you might do is to have the /etc/profile.d sh-update-script > delete itself once it's run satisfactorily. Nope. If I did that, cygcheck -c would report bash as incomplete. And the thought of self-modifying scripts, while workable, made this sound more complex than I wanted. So I gave up. With the newly released bash-3.1-6, if you use /bin/sh as your login shell, then upgrade bash, it is your own fault if /bin/sh is out-of-date with respect to the upgraded bash. But since the default cygwin.bat uses bash as the login shell, I'm not too worried about catering to the minority (besides, if someone has dug in deep enough to change their login shell, I suspect they are smart enough to know how to fix things when they go wrong). It does point out a wishlist item of mine - cygcheck -svr output would be nicer if it also included --version output (or at least the first line thereof) for each common tool it searched for, rather than just the path where the common tool was found. > > I guess what got me on this was that there was a zombie /bin/sh process > running during the cygwin update. It might have been a little less > nerve-wracking if there had been a visible message during the > postinstall, instead of picking it up during the login. Well, the CVS sources for setup.exe DO have some better handling of failed postinstalls, but no one has officially released a new version yet (although you can find alpha builds if you look at http://cygwin.com/setup/. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEU/bB84KuGfSFAYARAu5KAKC6AVDrV2mHZ4BQqLSHKM6zM7PVIQCgyzYF 1Ds5JaW6tLHlKfG9wWmWiu8= =D4hT -----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/