X-Spam-Check-By:	sourceware.org
Message-ID:	<4424BE59.9184F1E1@dessent.net>
Date:	Fri, 24 Mar 2006 19:51:53 -0800
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: ":" in filename
References:	<8389af8b0603241937m62e9701y596bed40382bd6f0 AT mail DOT gmail DOT com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Hiroki Sakagami wrote:

> What happens in the below commands?  The ":" in filenames seems to be
> a problem.  But I don't understand the rule.

The colon is used by NTFS to signify alternate data streams.  You can
google for more information about this, e.g.
<http://www.ntfs.com/ntfs-multiple.htm>.

This means that the colon is not actually part of the filename (since
it's acting as a delimiter), and the filename cannot contain a colon. 
This is a win32 restriction and has nothing to do with Cygwin per se. 
However, if you need to have a filename with a colon in it, you can use
a Cygwin managed mount which works around the problem of characters
forbidden by win32 to exist in filenames.

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/

- Raw text -