Subject: Re: bug#10489: 24.0.92; dired-do-copy may create infinite directory hierarchy

From: Eli Zaretskii <[email-masked]>
Date: Fri, 24 Feb 2012 21:42:42 +0200

> From: Michael Albinus <[email-masked]>
> Cc: [email-masked],  [email-masked]
> Date: Fri, 24 Feb 2012 16:19:13 +0100
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> >> This implementation requires, that inode number and filesystem device
> >> number are always unique. This is true for local files, if you run a
> >> Unix-like system. It is not guaranteed for remote files. And it is even
> >> not guaranted, if the local system is Windows: on mounted drives, the
> >> returned inode number is 0:
> >
> > Mounted how (i.e. with what command or feature)?
> 
> Don't know, somebody has added "network drives" to my login. All I can
> say is
> 
> --8<---------------cut here---------------start------------->8---
> U:\>net use
> New connections will be remembered.
> 
> Status       Local     Remote                    Network
> -------------------------------------------------------------------------------
> Disconnected R:        \\ASLSDA0\ZENTRAL         Microsoft Windows Network
> OK           U:        \\DESTGSFILN2\lb01177$    Microsoft Windows Network
> OK           Y:        \\sambager1\albinus       Microsoft Windows Network
> The command completed successfully.
> --8<---------------cut here---------------end--------------->8---

And all of the \\server\share\foo directories, and also those below
them, return zero inodes?