[bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

[Miklos Szeredi]

Follow-up Comment #4, bug #17877 (project findutils):

Fair enough, I see your point.

However there are filesystems which simply don't have the notion of inode
numbers, or _anything_ that would indentify a file other than it's name.  And
it's not possible to map the name to a unique identifier with bounded memory
requirements.

So while these filesystems may not be POSIX compliant, find should continue
to support them.

Smbfs, cifs and sshfs are examples of this filesystem class.  I'm not sure
about FAT.  Cygwin may _appear_ to provide stable inode numbers for FAT with
some clever heuristics, but I don't think it can do that under all
conditions.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?17877>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/