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: <39AE3840.4E25EA74@cygnus.com>
Date: Thu, 31 Aug 2000 12:49:36 +0200
From: Corinna Vinschen <vinschen AT cygnus DOT com>
Reply-To: cygwin <cygwin AT sources DOT redhat DOT com>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14 i686)
X-Accept-Language: de, en
MIME-Version: 1.0
To: cygwin AT sources DOT redhat DOT com
Subject: Re: [ANNOUNCEMENT] Updated: ash-20000823
References: <200008241611 DOT MAA13017 AT rtl DOT cygnus DOT com> <s1sog2alggh DOT fsf AT jaist DOT ac DOT jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Kazuhiro Fujieda wrote:
> 
> >>> On Thu, 24 Aug 2000 12:11:07 -0400
> >>> Corinna Vinschen <vinschen AT cygnus DOT com> said:
> 
> > I've updated the version of ash in cygwin/latest to 20000823.
> 
> The `conf.sh' script in rcs-5.7 can't work properly with
> ash-20000627 or later.
> 
> This script requires /bin/sh to execute files named a.out
> generated by `gcc -o a.out ...'.  These files has no execute
> permission on the Cygwin environment without ntsec and ntea.
> The above ash can't execute such files differently from older
> versions.
> 
> IMHO, sh should execute any files regardless of their permission
> and put the results into the hands of the kernel (Cygwin DLL)
> from the point of view of emulating UNIX.

The new behaviour is due to a change made to get ash behave correctly
on `type' command. As a result it now checks if the file is executable
when the command is given with path. I had tested that in `bash'. It
reports non executable files on `type' if no path is given while it
reports an error if a path is given. Example:

~> type nonexec
nonexec is /home/corinna/bin/nonexec
~> type bin/nonexec
bash: type: bin/nonexec: not found

So the current implementation is on one hand compatible to bash
behaviour, on the other hand it blocks executing files without exec
bit set.

I could eliminate that check for exec bit if there's an agreement
to do so. 

However, I'm on vacation for another two weeks so don't rely on
fast reply :-)

Corinna 

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin AT sources DOT redhat DOT com
Red Hat, Inc.
mailto:vinschen AT cygnus DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com