----- Original Message ----- From: "Eric Blake" To: <cygwin-patches@cygwin.com> Sent: Monday, May 09, 2005 2:19 PM Subject: Re: [Patch]: mkdir -p and network drives
> Pierre A. Humblet <pierre <at> phumblet.no-ip.org> writes: > > > > Here is a patch to allow mkdir -p to easily work with network > > drives and to allow future enumeration of computers and of > > network drives by ls -l. > > > > It works by defining a new FH_NETDRIVE virtual handler for > > names such as // and //machine. > > This also makes chdir work without additional change. > > I've just downloaded the 20050508 snapshot to play with this, and it still > needs some work before coreutils-5.3.0-6 can be released. But it is an > improvement! > > First, `ls -ld // //machine' show that these directories are mode 111 > (searchable, but not readable). Yet opendir("//") and opendir("//machine") > succeed, although POSIX requires that opendir(2) fail with EACCESS if the > directory to be opened is not readable. That's currently a feature. Being compliant means writing extra code that will be junked when we make the directories readable. In what way does non-compliance affect coreutils or the user? A similar case is that getfacl reports the directories as r-x. > Second, the sequence chdir("//"), mkdir("machine") creates machine in the > current directory. That's a bug. I will look into it. Thanks. Pierre