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: Mon, 6 Oct 2003 23:45:59 -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: <3.0.5.32.20031006195451.0081f100@incoming.verizon.net> 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 On Mon, 6 Oct 2003, Pierre A. Humblet wrote: > Perhaps the setup postinstall scripts should change to using > bash. Its behavior is correct and will avoid frustrations. It'd be nice it I could get rid of it. I have to use #!/bin/bash in my scripts, change rxvt (the X11 version) because it defaults to sh, use "shell bash" in my .screenrc... If setup starts using bash, can I get rid of ash, or something would still use it ? -- 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/