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
Subject: Re: colons with rsync
From: Ben Smith <bendees AT cox DOT net>
To: pechtcha AT cs DOT nyu DOT edu
Cc: cygwin AT cygwin DOT com
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 11 Jun 2003 12:46:39 -0500
Message-Id: <1055353600.2558.51.camel@(none)>
Mime-Version: 1.0

Igor Pechtchanski wrote:

> Windows filenames cannot contain ':', so there is no way around this
> limitation in Cygwin, since it uses Windows filenames.

Igor,

So does this mean that Cygwin doesn't do any file munging?  Is this
something that applications are normally left to deal with?

I found this post that mentions how samba deals with similar problems:
http://www.mail-archive.com/rsync AT lists DOT samba DOT org/msg05701.html

I know that cygwin can't just write a file called c:\foo:bar.txt but
shouldn't there be some sort of translation to be able to deal with this
situation, or is it contrary to the design philosophy of cygwin in some
way?

-Ben
bensmith AT zieglers DOT com
bendees AT cox DOT net



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