Justin Vallon writes:
>From customize-variable find-file-compare-truenames:
" ... This works if any component of the pathname (including a non-
terminal component) is a symbolic link as well, but doesn't work with hard
links (nothing does). "
Isn't this strictly incorrect? I can determine the inodes of the files in
question (given either paths or file descriptors), and determine if the
two files are indeed two paths to the same file. Right?
Major/minor device numbers plus the inode number should uniquely
identify a file on a local UNIX filesystem. This won't work over
NFS.