Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<3.0.5.32.20031006195451.0081f100@incoming.verizon.net>
X-Sender:	vze1u1tg AT incoming DOT verizon DOT net (Unverified)
Date:	Mon, 06 Oct 2003 19:54:51 -0400
To:	cygwin AT cygwin DOT com
From:	"Pierre A. Humblet" <pierre AT phumblet DOT no-ip DOT org>
Subject:	Ash woes. [Was: Re: Installation & Uninstallation issues ]
Mime-Version:	1.0

The problem recently reported by Tim Dierks in
<http://www.cygwin.com/ml/cygwin/2003-10/msg00273.html>
turns out to be identical to the one investigated in
<http://www.cygwin.com/ml/cygwin/2003-04/msg00471.html>

The scripts are executable but ash refuses to execute them.
Ash uses various methods to make that decision, none of which
is correct. It should be patched to use access(), as it already
does for its built-in test. PTC.

Perhaps the setup postinstall scripts should change to using bash.
Its behavior is correct and will avoid frustrations.

Pierre

--
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/

- Raw text -