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, 12 Aug 2003 07:12:03 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: ash 20020731-3 and/or cygwin 1.5.2 directory vs. executable problem Message-ID: <20030812111203.GA2316@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <20030811180612 DOT GB1136 AT tishler DOT net> <20030811190539 DOT GO3101 AT cygbert DOT vinschen DOT de> <20030811200134 DOT GA1392 AT tishler DOT net> <20030811205002 DOT GT3101 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030811205002.GT3101@cygbert.vinschen.de> User-Agent: Mutt/1.4i On Mon, Aug 11, 2003 at 10:50:02PM +0200, Corinna Vinschen wrote: > On Mon, Aug 11, 2003 at 04:01:34PM -0400, Jason Tishler wrote: > > On Mon, Aug 11, 2003 at 09:05:39PM +0200, Corinna Vinschen wrote: > > > On Mon, Aug 11, 2003 at 02:06:13PM -0400, Jason Tishler wrote: > > > > Since the source of ash 20020731-1 seems identical to ash > > > > 20020731-3, this seems to indicate a build and/or cygwin > > > > problem... > > > > > > It's a situation which is determined by coincidence... > > > > Huh? > > We had a similar discussion in this ML at one point. I remember the discussion, but not all of the details. > You can't rely on this situation to work correctly, given the way > applications try to find out about files. Think "stat". If it worked > so far, you're a lucky guy. I guess that my luck just ran out... :,( Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/