X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 18 Aug 2010 22:19:21 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: "run" changes behavior with cygwin-17.6
Message-ID: <20100818201921.GI11340@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <AANLkTikBTgg9M=xuZ4S2VkNU+Zr=hy3C=_Tr8BPj5baD AT mail DOT gmail DOT com> <20100818185421 DOT GC22698 AT ednor DOT casa DOT cgf DOT cx> <20100818191340 DOT GB11340 AT calimero DOT vinschen DOT de> <20100818191906 DOT GD22698 AT ednor DOT casa DOT cgf DOT cx> <20100818192238 DOT GA27567 AT ednor DOT casa DOT cgf DOT cx> <20100818193446 DOT GC11340 AT calimero DOT vinschen DOT de> <20100818193940 DOT GA4358 AT ednor DOT casa DOT cgf DOT cx> <AANLkTi=vy5=E2fGJQ-2=cehaQFvsc-+oYLKp1dc7tVS6 AT mail DOT gmail DOT com> <20100818195546 DOT GF11340 AT calimero DOT vinschen DOT de> <4C6C3B15 DOT 2000605 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4C6C3B15.2000605@redhat.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Aug 18 13:57, Eric Blake wrote:
> On 08/18/2010 01:55 PM, Corinna Vinschen wrote:
> >> I'm not convinced such a compromise would be worthwhile, because it
> >> would forfeit Linux compatibility while still breaking some
> >> Win32-using programs. I think it should be one way or the other:
> >> either stick with the current approach, or always sync the Win32
> >> working directory up-to-date (except when that's not possible).
> > 
> > The question here is a bit tricky, me thinks.
> > 
> > 1) Do we want as much POSIX compatibility as possible?
> 
> POSIX allows the refusal to delete an in-use directory; and Solaris NFS
> mounts behave this way.  But since Linux can delete in-use directories
> (where an in-use directory includes the condition of at least one
> process owning that directory as its cwd), and cygwin emulates Linux
> rather than POSIX, we can try harder if it makes sense.

That lets me more tend to 3 now (cgf's idea to defer until the first
chdir).  I'm still chewing nails, though.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple