CYGWIN inode over Samba share not constructed from IndexNumber
Fri May 11 19:49:00 GMT 2012

At 07:58 PM 5/11/2012 +0200, Corinna Vinschen wrote:
>Which Samba version introduced this behaviour?

Don't know.

I'm stepping aside on this now.  Just
reported it since it came up and broke
a script we have.  I've worked around
the inode test by comparing 'sha1sum'
values for the files and re-hard-linking
the files when the sums differ.

I understand this stuff can be tricky,
but if it's at all possible it seems
reasonable to ask that the behavior of
CYGWIN+Samba parallel Linux native
behavior w/r/t apparent inode values being
the same when actual inode values match.

I like the idea that the true inode
values be represented by CYGWIN+Samba
whenever possible.

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list