X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Bret Weinraub <bretweinraub AT yahoo DOT com>
Subject:  Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5
Date: Mon, 13 Nov 2006 23:16:46 +0000 (UTC)
Lines: 16
Message-ID:  <loom.20061114T001417-1@post.gmane.org>
References:  <announce DOT 45548308 DOT 9040507 AT byu DOT net> <loom DOT 20061110T184304-348 AT post DOT gmane DOT org> <loom DOT 20061110T193922-553 AT post DOT gmane DOT org>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Eric Blake <ebb9 <at> byu.net> writes:

> Evil.  /bin/sh is supposed to be at the same version of bash, if you installed 
> things correctly.  It sounds like your postinstall scripts did not run 
> correctly (perhaps you had bash or sh open when you ran setup.exe?).  What are 
> the timestamps on those files ('ls -l /bin/{ba,}sh')?
> 
> At any rate, the fix is to rerun the postinstall scripts, or more 
> quickly, 'cp /bin/bash /bin/sh'.


Several machines at my site have turned up with the sh vs bash issue above, so I
think something might be amiss with the installation scripts.  The workaround of
copying  /bin/bash to /bin/sh works of course.




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