X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: Seems like treatment of NTFS ADS (foo:bar) changed between 1.5   and 1.7 but not mentioned in What's Changed
Date: Tue, 17 Nov 2009 17:36:48 +0000 (UTC)
Lines: 37
Message-ID:  <loom.20091117T182547-55@post.gmane.org>
References:  <26363833 DOT post AT talk DOT nabble DOT com>  <416096c60911151427g12cc5582t6d9bbdc063c5b14a AT mail DOT gmail DOT com>  <4B013E09 DOT 1010209 AT towo DOT net>  <20091116120650 DOT GH29173 AT calimero DOT vinschen DOT de>  <4B01462A DOT 3080400 AT towo DOT net>  <416096c60911160532j2c49cd7ftb79fcc7295f9be21 AT mail DOT gmail DOT com>  <20091116135644 DOT GK29173 AT calimero DOT vinschen DOT de>  <4B01639C DOT 8000403 AT towo DOT net>  <4B0167EF DOT 8030807 AT towo DOT net> <20091116163415 DOT GD20652 AT ednor DOT casa DOT cgf DOT cx> <4B02BB32 DOT 4090403 AT towo DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Thomas Wolff <towo <at> towo.net> writes:

> Sorry that I take this up once more (after promising <end:of>), but I 
> had this additional idea after seeing your point about being strictly 
> consistent with the POSIX pathname namespace:
> 
> So what about using "/" as a delimiter? If "foo" is a file, "foo/bar" is 
> not a legal pathname in POSIX, so it could be used to access the "bar" 
> fork of "foo" without causing real harm.

NO - a thousand times no.  Using / in file names, but not as a directory, is 
just ASKING to break everything ever written, and penalize speed of interfaces 
that could care less about this.

But, you _could_ borrow a leaf from Solaris, and support and implementation:

openat(open("foo",flags), "bar", flags)

as a way to open the "bar" stream of the "foo" fd, aka "foo:bar" in windows 
terms.  In other words, open("foo/bar") MUST fail, because foo is not a 
directory, but openat(fd_of_foo,"bar") is an extension allowed by POSIX (just 
because we currently fail with ENOTDIR in that situation doesn't mean we have 
to); and by using the *at interfaces, we could isolate the performance penalty 
to just the situations where the fd is not a directory fd.

You would also want to consider implementing opendir2 (borrowing from BSD 
heritage; there, opendir2 exists to allow the user to select whether whiteout 
entries in a union mount will be ignored), and adding a new DTF_* bit that 
allows opening a file to traverse its alternate streams, instead of the normal 
opening a directory to traverse its contents.

But I won't be writing the patches to do that.

-- 
Eric Blake




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