-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Charles Wilson on 4/24/2006 10:42 PM: > Corinna Vinschen wrote: > >> - Reintroducing the dirent member d_ino. 1.5.20 tries hard to return a >> useful d_ino value, which is supposed to be also the same as st_ino as >> returned by stat(2) in all cases, regardless of the obstacles to do >> this on Windows. Do you have strange file systems like HPFS or >> ClearCase? > > I'll take a look at this w.r.t clearcase. How exactly should I test -- > what am I looking for? Just a little app that compares dirent.d_ino and > stat.st_ino for a specified file on the strange filesystem?
Another set of tests is to use the experimental coreutils-5.94-5. Doing/bin/pwd inside a directory on the strange filesystem stress tests d_ino (I already know that on ClearCase (MVFS), /bin/pwd fails inside of versioned directories, such as ccase/foo@@/main/, since ClearCase refuses to list foo@@ in a readdir of ccase, but that is not cygwin's bug). And comparing '\ls -ia' against '\ls -ipa' will show whether d_ino agrees with st_ino. > > Do I only care about the lower 32 bits, or all 64? On cygwin, ino_t is advertised as 64 bits; if all 64 don't match, then cygwin needs to be patched. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEThYr84KuGfSFAYARAjL8AJ9yBV+3pMb5sTNGRNjJVYsJZjblOgCdF9Tt NXHJanCG5F9EYWnYVUmqISU= =W8Q+ -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
