X-Spam-Check-By: sourceware.org
Message-ID: <a5f030530606160613k4b10971cy58a8c6a15ce00c41@mail.gmail.com>
Date: Fri, 16 Jun 2006 09:13:33 -0400
From: "Brett Serkez" <bserkez AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Unable to delete directory in Cygwin
In-Reply-To: <20060616130533.GA22975@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1F211FE03383644EAA6BB7A52FCD9B9B0927A0 AT sohm DOT kpit DOT com> 	 <1F211FE03383644EAA6BB7A52FCD9B9B0927A4 AT sohm DOT kpit DOT com> 	 <143umqixuj7aa$.q6uf55wgjg5t$.dlg AT 40tude DOT net> 	 <a5f030530606160435o3a8cdd3bne0c4899cbeebdfad AT mail DOT gmail DOT com> 	 <20060616122412 DOT GB10880 AT trixie DOT casa DOT cgf DOT cx> 	 <a5f030530606160528x5b5ebf5bm93e1be8d601e6fcb AT mail DOT gmail DOT com> 	 <20060616123743 DOT GC10880 AT trixie DOT casa DOT cgf DOT cx> 	 <a5f030530606160559r11ecf1far9a78eb2180b1500d AT mail DOT gmail DOT com> 	 <20060616130533 DOT GA22975 AT calimero DOT vinschen DOT de>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

> > So this brings me back to my original question, what is it in NTFS
> > that provides Inode type functionality that Cygwin is leveraging?
>
> This might sound far-fetched, but can you imagine that this is just
> the way Microsoft implemented the file system?  It doesn't allow to
> remove a directory if *any* process has an open handle to the directory
> or one of its children.

Absolutely, this is precisely my point!

UNIX/Linux specifically allows for this not to be the case via the
inode in the file system. I didn't think that Windows/NTFS allowed for
this possibility.  Christopher seemed to be indicating this was not
the case and I was trying to understand.

So this is clear, the original script will never work on Cygwin
because it is reliant upon NTFS which doesn't support this
functionality.

I would also point out that this functionality might not work under
Linux if the underlying file system isn't inode based.  For instance
one can mount a FAT/FAT32 file system and the script would fail in
that case also.

The original script worked based on file system functionality, not a
particular OS.

Thanks!

Brett

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