Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: ericblake AT comcast DOT net (Eric Blake)
To: cygwin AT cygwin DOT com
Subject: fun with managed mounts
Date: Wed, 10 Aug 2005 15:02:22 +0000
Message-Id: <081020051502.7098.42FA16FE000686E200001BBA22058864420A050E040D0C079D0A@comcast.net>

I don't know if this warrants a fix, or if the fix would introduce an
unacceptable speed penalty, but managed mounts currently have
strange behavior when creating a file that looks like a drive specifier.

$ cd managed
$ touch ./a:
$ stat ./a:
  File: `./a:'
  Size: 0               Blocks: 0          IO Block: 1024   regular empty file
Device: 10292fb1h/271134641d    Inode: 7339460017730359124  Links: 1
Access: (0644/-rw-r--r--)  Uid: (22382/  eblake)   Gid: (10513/Domain Users)
Access: 2005-08-10 08:40:50.873125000 -0600
Modify: 2005-08-10 08:40:50.873125000 -0600
Change: 2005-08-10 08:40:50.873125000 -0600
$ stat a:
stat: cannot stat `a:': Invalid argument

When resolving a filename that does not begin with / (or \), but which
does match letter colon, it would be nice if the pathname resolution
code first checked whether . is managed rather than blindly treating
the name as an absolute path, so that managed mounts don't have
problems with filenames that look like drive letters.  On the other
hand, that means that in managed mounts, a: is never absolute, which
may break assumptions made elsewhere; but then again, since cygwin
is trying to emulate Unix, the user should be using `/cygdrive/a' instead
of `a:' if they are using managed mounts.

--
Eric Blake

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