X-Spam-Check-By: sourceware.org Message-ID: <4570C4C5.6020908@byu.net> Date: Fri, 01 Dec 2006 17:11:49 -0700 From: Eric Blake 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 Subject: Re: echo hi|egrep -v ho #no output References: <200612012037 DOT kB1KbY8b006101 AT tigris DOT pounder DOT sol DOT net> <4570965A DOT CA1FD5DC AT dessent DOT net> <200612012343 DOT kB1NhDOg006881 AT tigris DOT pounder DOT sol DOT net> <4570C168 DOT AFC3492A AT dessent DOT net> In-Reply-To: <4570C168.AFC3492A@dessent.net> 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-Id: 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 Brian Dessent on 12/1/2006 4:57 PM: > >> setup.exe did not complain though. I know I have to update my > > It wouldn't, because it does not handle replacement of sh.exe directly. > That is done in the postinstall step. The postinstall step cannot replace /bin/sh if it is already in use (perhaps you left a cron job running when you ran setup.exe?). > I'm still not clear how the > events transpire that cause this postinstall to fail. And even if the > postinstall failed it's designed to run anyway the next time bash runs, > so I'm stymied. Maybe based on the ls -l information in your message > someone can figure out why sh.exe was not replaced. Maybe that's a key as well - the ls information showed that the old /bin/sh was owned by a different user than the new bash; perhaps there were permissions problems preventing the postinstall script from overwriting the old file. Maybe I should revisit the postinstall script to forcefully remove the old file rather than trying to write over it (writing over it preserves the inode, but that doesn't buy much if it means /bin/sh is left out-of-date on failure). - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net volunteer cygwin bash maintainer -----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 iD8DBQFFcMTF84KuGfSFAYARAhHTAJ9j+zYQgRsah3nO4vbwXRjdOrohDwCgjPF8 J/hcoE4rGz6I0Kfo6HaPLps= =vBHX -----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/