X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 17 Nov 2009 10:12:48 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Seems like treatment of NTFS ADS (foo:bar) changed between 1.5 and 1.7 but not mentioned in What's Changed Message-ID: <20091117151248.GC15007@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <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-Disposition: inline In-Reply-To: <4B02BB32.4090403@towo.net> 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: List-Unsubscribe: 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 On Tue, Nov 17, 2009 at 04:03:14PM +0100, Thomas Wolff wrote: >Christopher Faylor wrote: >> On Mon, Nov 16, 2009 at 03:55:43PM +0100, Thomas Wolff wrote: >> >>> Thomas Wolff wrote: >>> >>>>> ... >>> Anyway, maybe some syntax could be found that would not be too harmful >>> to become "reserved" for this purpose... >>> >>> >> >> Sorry but I agree with Corinna. On linux/UNIX you can create a file >> with a colon in it. We can now do this in Cygwin 1.7 and that's a good >> thing. Complicating the path handling to deal specially with colons in >> a filename doesn't sound like a good idea to me. >> >Sorry that I take this up once more (after promising ), 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. There might be stronger >objection to implicitly creating a fork with this syntax than to just >accessing it, which could be resolved with either a $CYGWIN-configurable >option or a mkfork command. How could we possibly use '/' as a delimiter? Are you really advocating that we treat every file as a potential directory? So every time someone says "foo/bar" and "foo" is a file we try to open "foo:bar"? And what happens when someone says "ls -l foo"? Should that work too? cgf -- 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