Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Sat, 9 Jul 2005 10:28:42 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: File Naming Between Cygwin and Windows Message-ID: <20050709082842.GQ7507@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jul 9 05:03, Ross MacGillivray wrote: > > I am trying to access via a cygwin application a file called kdeinit-127.0.0.1:0. > The filename is generated within the software, so it is not trivial to change > the file name in the file access via the file system. > > However the underlying Windows file system does not accept colons (:), so the > file is actually called kdeinit-127.0.0.1_0. > > How does cygwin deal with characters not accepted by the windows file system > such as colon(:). Does it translate these characters automtically in file > system calls? Usually it chokes, like the underlying OS. As a workaround you'll find so called "managed mounts", which only work on fresh created directories so managed mounts are no general solution. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/