X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 16 Nov 2009 14:56:44 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
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: <20091116135644.GK29173@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <416096c60911160532j2c49cd7ftb79fcc7295f9be21@mail.gmail.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 Nov 16 13:32, Andy Koppe wrote:
> 2009/11/16 Thomas Wolff:
> > But with it being supported, "foo:bar" *is* a POSIX filename and can quite
> > transparently be handled like a file
> 
> If you create a file called "foo:bar" in Cygwin 1.5, a directory
> listing will actually show a file called "foo" of size 0. You have to
> already know that "foo:bar" exists to access it, and there's no way in
> Cygwin to find those files.
> 
> Furthermore, if you delete the file "foo", you'll also delete
> "foo:bar" and any other ADSs of "foo". Again, something that POSIX
> programs don't expect.

Or, just for kicks, try to create a file "abc:def:ghi" under 1.5 or,
FWIW, under CMD.

> > Moreover, this transparent mapping would also solve the copy/backup problem
> > discussed in the other thread (was it "rsync"?) and actually all problems at
> > once, like including these things in zip archives etc.
> 
> Zip would never know about the ADSs, because they don't show up in
> directory listings. Same in cmd.exe, btw.
> 
> I guess they could be included in Cygwin directory listings, but
> - It would be a chunky piece of work to implement it.
> - It would slow down directory operations.
> - Non-POSIX behaviours would remain: creating "foo:bar" would create
> an empty "foo" and deleting "foo" would also delete "foo:bar" and any
> other ADSs.
> 
> I think they'd need a special API if they were to be supported. Do
> they fit into the xattr stuff?

No, xattrs and ADS are entirely different beasts.


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