X-Spam-Check-By: sourceware.org From: Jonathan Lennox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17883.19201.706200.650344@metro-north.cs.columbia.edu> Date: Tue, 20 Feb 2007 14:24:49 -0500 To: cygwin AT cygwin DOT com Subject: Managed mounts fail to support some legal POSIX filenames X-Mailer: VM 7.19 under Emacs 20.7.1 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 While poking around with managed mounts following yesterday's mail, it occured to me that the managed-mount filename munging misses some cases, namely, filenames with trailing spaces, and filenames that look like Windows short-form names corresponding to existing file names. Here's an example: $ mkdir managed $ mount -o managed `cygpath -aw managed` $PWD/managed $ cd managed $ touch foo 'foo ' $ ls -l total 0 -rw-r--r-- 1 Jonathan None 0 Feb 20 13:48 foo $ rm foo $ touch longfilename.c longfi~1.c $ ls -l total 0 -rw-r--r-- 1 Jonathan None 0 Feb 20 13:48 longfilename.c $ rm longfilename.c $ cd .. $ umount `cygpath -aw managed` $ rm -r managed Fixing the first of these should be easy; space just needs to be handled the same as dot in fnmunge, and because of the bug existing managed mounts can't have files with trailing spaces. The second problem is trickier, since you'd want to keep compatibility with filenames containing tildes on existing managed mounts. -- Jonathan Lennox lennox at cs dot columbia dot edu -- 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/