Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: jeffdbREMOVETHIS AT goodnet DOT com (Mikey)
To: Anil K Ruia <ruia AT paul DOT rutgers DOT edu>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Here documents in ash shell scripts mess up stdin on 9x
Date: Sat, 13 Feb 1999 01:19:17 GMT
Organization: Never
Reply-To: jeffdbREMOVETHIS AT goodnet DOT com
Message-ID: <36c4cded.69666249@mail.goodnet.com>
References: <36c4737f DOT 46513371 AT mail DOT goodnet DOT com> <36C4874D DOT 71585466 AT paul DOT rutgers DOT edu>
In-Reply-To: <36C4874D.71585466@paul.rutgers.edu>
X-Mailer: Forte Agent 1.5/32.452
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Yes, ash on 9x is much more stable (and faster :) running configure than bash.
On 95a linking /bin/sh -> bash.exe will cause lockups, even with CYGWIN=  tty
or at least it did for me with b19, your mileage may vary.

Do not use the b20 ash, recompile the one from b19, the b20 ash
has several serious bugs, and someone is trying to add features,
that are not needed, for a non-login shell.

The main problem is that once ash exits after running configure if you continue to
use that login shell and a non cygwin app segfaults in it, you can have
hard lockups. 

Can you say reset-button? I knew you could ;^)

Once configure exits I always exit that console and start a new one.

On Fri, 12 Feb 1999 14:55:57 -0500, you wrote:

>Thanx Mike for diagnosing the cause of the problem.  I had been having
>this problem on Win98 with B20.1 also and hadn't been able to find a
>solution.  I just made /bin/sh a link to bash.exe as opposed to sh.exe
>before.  But I remember someone saying something about ash being more
>stable for configures than bash.  Could I run into problems because of
>that?
>
>- Anil
>
>Mikey wrote:
>> 
>> I always wondered why configure screwed up bash
>> on win95, and I finally figured it out.
>> 
>> Here documents in ash shell scripts
>> 
>> This bug doesn't appear under NT4 SP3.
>[stuff deleted]