Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <012501c0faf6$7e7d17c0$0201a8c0@watch5>
From: "Cliff Hones" <cliff AT aonix DOT co DOT uk>
To: "Cygwin Users" <cygwin AT cygwin DOT com>
References: <3B31D642 DOT 6ACDB3C4 AT yahoo DOT com>
Subject: Re: Autoconf's suggestion to use bash as /bin/sh
Date: Fri, 22 Jun 2001 09:36:18 +0100
Organization: Aonix Europe Ltd
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

Earnie Boyd wrote:
> I suppose Cliff Hones had a question and wasn't just posting to be
> posting and I assume the hidden question to be "Why does Cygwin not use
> bash as sh?" and that is covered in the FAQ.  However, once upon a time
> a long time ago Cygwin did use bash as sh.  It was discovered that
> scripts and software builds would happen more quickly if ash was used as
> sh.  So the next release of Cygwin after the discovery included ash as
> sh.  This doesn't prevent you from using it now, simply `cp
> /bin/bash.exe /bin/sh.exe' and you'll be compliant with the autoconf
> suggestion.  However, you would have slowed down the functioning of
> Cygwin scripts and package builds.

I didn't really mean to be asking a hidden question.  Indeed I have
wondered why Cygwin uses ash for sh, and many thanks for the
explanation.  BTW, I couldn't find it in the FAQ - and I've just
looked at all occurrences of bash (of which there are many!).

My main reason for posting was simply the conflicting advice; given
the frequent comments of "you shouldn't suggest that" when people
raise the issue of copying or linking bash to sh, it seemed odd that a
Red Hat document should be doing just that.

And finally, maybe it would help if the "don't do that"
messages gave a reason why it shouldn't be done,
or at least a reference.  The more understanding, the fewer
posts we'll see.  [My guess is that the reason is the usual
one - it's far easier to help people with problems if they
have a full standard installation.]

-- Cliff



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple