Re: [Patch]: mkdir -p and network drives

At 06:19 PM 5/9/2005 +, Eric Blake wrote: >Second, the sequence chdir("//"), mkdir("machine") creates machine in the >current directory. Old bug. chdir("/proc"), mkdir("machine") produces the same result. And mkdir("/proc"), mkdir("/proc/machine") creates c:\proc\machine The fix sets errno

RE: [Patch]: mkdir -p and network drives

Original Message >From: Eric Blake >Sent: 06 May 2005 23:29 > Also, what should //.. resolve to, / or //? And if it resolves to /, > should // be an entry in the readdir() of /? I would argue that //.. > should resolve to //, meaning we just have two distinct roots in the > directory tr

Re: [Patch]: mkdir -p and network drives

- Original Message - From: "Eric Blake" To: Sent: Monday, May 09, 2005 2:19 PM Subject: Re: [Patch]: mkdir -p and network drives > Pierre A. Humblet phumblet.no-ip.org> writes: > > > > Here is a patch to allow mkdir -p to easily work with network > > drives and to allow future enumera

Re: [Patch]: mkdir -p and network drives

Pierre A. Humblet 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.