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 X-Analyze: Velop Mail Shield v0.0.3 Date: Tue, 7 Oct 2003 00:09:39 -0300 (BRT) From: =?ISO-8859-1?Q?Fr=E9d=E9ric_L=2E_W=2E_Meunier?= <1 AT pervalidus DOT net> X-X-Sender: fredlwm AT pervalidus DOT dyndns DOT org To: cygwin AT cygwin DOT com Subject: Re: Ash woes. [Was: Re: Installation & Uninstallation issues ] In-Reply-To: Message-ID: References: <3 DOT 0 DOT 5 DOT 32 DOT 20031006195451 DOT 0081f100 AT incoming DOT verizon DOT net> X-Archive: encrypt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks, I'll do that. I remember when I tried as a symlink and something hung setup (I guess setup doesn't handle them ?). It wasn't the XFree86-bin-icons issue, which also hung when I reverted the symlink. I'll go through the archives to see what I should do for XFree86-bin-icons since I had to use 'Skip' it in the last installs. On Mon, 6 Oct 2003, Igor Pechtchanski wrote: > bash should be fully sh-compatible. If you want to replicate > the Linux setup, simply rename /bin/sh to /bin/ash and > hardlink (or symlink) /bin/bash to /bin/sh (you will get a > noticeable startup time increase for your scripts, which was > the original reason for the ash package, but I doubt you'd > have too many other problems -- except you won't be able to > detect non-portable shell scripts on Cygwin anymore). -- How to contact me - http://www.pervalidus.net/contact.html -- 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/