X-Spam-Check-By:	sourceware.org
Date:	Mon, 1 May 2006 17:59:30 -0400 (EDT)
From:	Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Eric Blake <ebb9 AT byu DOT net>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Error on /bin/sh -login: "cannot remove /bin/sh.exe: Permission denied"
In-Reply-To:	<4453F6C1.9000507@byu.net>
Message-ID:	<Pine.GSO.4.63.0605011756080.28555@access1.cims.nyu.edu>
References:	<445122D6 DOT 1030409 AT gtri DOT gatech DOT edu> <4453F6C1 DOT 9000507 AT byu DOT net>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Sat, 29 Apr 2006, Eric Blake wrote:

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

Now that the new version of setup doesn't rename the script to .done
unless it succeeds, you can just have the profile script run the
postinstall script and then rename it to .done...

> [snip]
> 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.

Umm, this would only work if the tools it finds are the Cygwin versions.
Many other tools (e.g., Windows' "find") don't understand the --version
argument.

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

It's about time to release one, then, isn't it?
	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!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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

- Raw text -