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 Message-ID: <26364830.post@talk.nabble.com> Date: Sun, 15 Nov 2009 15:32:57 -0800 (PST) From: aputerguy 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 In-Reply-To: <416096c60911151427g12cc5582t6d9bbdc063c5b14a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <26363833 DOT post AT talk DOT nabble DOT com> <416096c60911151427g12cc5582t6d9bbdc063c5b14a AT mail DOT gmail DOT com> X-IsSubscribed: yes 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 Andy Koppe writes: > 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. Fair point. But also having 'ls -s' return '0' on a non-empty file is pretty weird too. > Hence I think the right way to > access ADSs is via Windows tools. Unless there is a POSIXy way to > represent them? The key point of my posting was not to advocate for one or the other but rather to give people a heads-up on this change in case anybody had written code based on the old treatment. In particular, I suggest that such fundamental (though certainly not at all common) changes to how files are accessed/named should be mentioned in the "What's changed" section. As a total lay-person to NTFS and filesystem stuff, I would have thought that the thing to do would be to allow ":" to appear by escaping it "\:" while preserving the original 1.5 ":" behavior to allow writing/reading to NTFS ADS. Finally, as an aside and for my edification, if the [] is U+F034, why does cygwin 1.5 seem to encode it as \357\200\272 which is consistent with what I get when I paste the filename into emacs (in UTF-8 encoding) and then look at it in hexl mode which gives ef 80 ba (which is the hex equivalent of the octal cygwin 1.5 codes). -- View this message in context: http://old.nabble.com/Seems-like-treatment-of-NTFS-ADS-%28foo%3Abar%29-changed-between-1.5-and-1.7-but-not-mentioned-in-What%27s-Changed-tp26363833p26364830.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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