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: Sun, 10 Jul 2005 00:48:17 -0700 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: File Naming Between Cygwin and Windows Message-ID: <20050710074817.GB1376@efn.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes On Sat, Jul 09, 2005 at 05:03:57AM +0000, 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? cygwin doesn't (except using a managed mode mount). Whatever's translating : to _ for you isn't cygwin. Note that NTFS does have a weird feature involving : $ mkdir tmp $ cd tmp $ cat >ab:cd hello ^D $ cat ab:cd hello $ ls -l ab:cd -rw-r--r-- 1 sthoenna None 6 Jul 10 00:40 ab:cd $ ls -l total 0 -rw-r--r-- 1 sthoenna None 0 Jul 10 00:43 ab $ rm ab $ ls -l ab:cd ls: ab:cd: No such file or directory See: http://www.securityfocus.com/infocus/1822 -- 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/