Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Rolf Campbell <rcampbell AT tropicnetworks DOT com>
Subject: Re: Use of colon in filenames
Date: Fri, 18 Apr 2003 13:02:58 -0400
Lines: 27
Message-ID: <b7pb2j$ccu$1@main.gmane.org>
References: <3EA01A27 DOT 70703 AT nortelnetworks DOT com>
Reply-To: IDontLikePersonalReplies AT hotmail DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
In-Reply-To: <3EA01A27.70703@nortelnetworks.com>

C. Brian Jones wrote:
> All,
> 
> Should attempts to create files such as "foo::bar" or "foo::bar::baz" 
> really cause a no such file error for 'touch', 'install', etc.?
> 
> $ touch 'foo::bar'
> touch: creating `foo::bar': Invalid argument
> 
> $ touch 'foo::bar::baz'
> touch: creating `foo::bar::baz': No such file or directory
> 
> $ install foo bar::baz
> install: cannot create regular file `bar::baz': Invalid argument
> 
> $ install foo bar::baz::bop
> install: cannot create regular file `bar::baz::bop': No such file or 
> directory
> 
> Any way to get the more UNIX-like behavior?
> 
> Brian


\ / : * ? " < > | are not allowed in ms-filenames.  There is no way to 
avoid this (without direct disk writes).



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