Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3FFFC90C.53EE70C4@dessent.net> Date: Sat, 10 Jan 2004 01:42:36 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: cvs and NTFS streams do not play well together... References: <3FFF6964.72555A90@dessent.net> <3FFFC389.3070109@tlinx.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.linuxsv3.net X-AntiAbuse: Original Domain - cygwin.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - dessent.net X-IsSubscribed: yes Reply-To: cygwin@cygwin.com linda w wrote: > > It seems that the standard stream notation is "::". programs like > Notepad can > read and write to NTFS streams using the :: (double colon notation). That > would seem to indicate thay are valid pathnames that describe a "file" > of data. > I.e. -- ":" is valid in a pathname on an NTFS file system to indicate a > stream. > > ":" also is a valid chacter on linux. Sounds like a built-in > incompatibility. > > Note, that if you do a dir of file::stream, it won't showup, but you can > open it, > so if cygwin implements the "open" call by first calling "dir" it will fail. The "::" idiom is used to denote an alternative stream, but that doesn't mean it's a valid character for the name of a file. See also : << NTFS Naming Conventions File and directory names can be up to 255 characters long, including any extensions. Names preserve case, but are not case sensitive. NTFS makes no distinction of filenames based on case. Names can contain any characters except for the following: ? " / \ < > * | : >> Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/