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 Date: Tue, 7 Oct 2003 19:37:41 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Ash woes. [Was: Re: Installation & Uninstallation issues ] Message-ID: <20031007173741.GA28757@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3 DOT 0 DOT 5 DOT 32 DOT 20031006195451 DOT 0081f100 AT incoming DOT verizon DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.5.32.20031006195451.0081f100@incoming.verizon.net> User-Agent: Mutt/1.4.1i On Mon, Oct 06, 2003 at 07:54:51PM -0400, Pierre A. Humblet wrote: > The problem recently reported by Tim Dierks in > > turns out to be identical to the one investigated in > > > 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. AFAICS, this should only affect commands given with absolute paths, see beginning of function exec.c::find_command(). I'll upload a patched ash in a minute. Could you give it a test? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/