Message-ID: <4B013E09.1010209@towo.net>
Date: Mon, 16 Nov 2009 12:56:57 +0100
From: Thomas Wolff <towo@towo.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin@cygwin.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
References: <26363833.post@talk.nabble.com> <416096c60911151427g12cc5582t6d9bbdc063c5b14a@mail.gmail.com>
In-Reply-To: <416096c60911151427g12cc5582t6d9bbdc063c5b14a@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Andy Koppe wrote:
> I'd suspect the support for ADSs in 1.5 was rather accidental anyway.
> POSIX programs certainly don't know about them, and you get the rather
> weird situation that "files" like foo:bar can be accessed but don't
> show up in the directory they're in. Hence I think the right way to
> access ADSs is via Windows tools. Unless there is a POSIXy way to
> represent them?
>   
I've only learned about this ADS stuff recently but yes, I think, simply 
using the "a:b" syntax (which is also used by Windows tools) and 
handling them as a virtual file is a quite obvious POSIX way to do it.
So if it worked in 1.5, whether accidental or not, I think it should 
continue to work in 1.7.
The loss of this feature may simply be a consequence of handling illegal 
filename characters via the Unicode private range,
so the resolution might be as easy as taking out ":" from this handling 
again, just a guess.

Thomas

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