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 Date: Thu, 7 Jul 2005 14:45:33 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Latest uopdates to bash and ash, 20050707 Message-ID: <20050707124533.GE2844@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0MKu60-1DqVfT2QSv-0005D2 AT mxeu10 DOT kundenserver DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0MKu60-1DqVfT2QSv-0005D2@mxeu10.kundenserver.de> User-Agent: Mutt/1.4.2i On Jul 7 13:35, fergus wrote: > Just updated bash and ash, seems to involve losing /bin/sh.exe. > > (1) Now all scripts beginning #! /bin/sh fail; should there be a link > /bin/sh -> /bin/bash? No, the postinstall scripts of both, bash and ash are copying bash.exe to sh.exe. How did you install? What does the postinstall script(s) print when run? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/