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 To: cygwin AT cygwin DOT com From: Ross MacGillivray Subject: Re: File Naming Between Cygwin and Windows Date: Sun, 10 Jul 2005 06:03:27 +0000 (UTC) Lines: 36 Message-ID: References: <20050709082842 DOT GQ7507 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Corinna Vinschen cygwin.com> writes: > > 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 > Do you know happen to know what the 'standard' solution is, when running KDE-on-Cygwin, for this incompatibility in file naming between cygwin and windows? Is it managed mounts or is there some other commonly used solution? /Ross -- 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/