-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Corinna only replied to the cygwin list. It looks like Windows will populate st_birthtime with st_ctime when reading filesystems that don't support birthtime. This is a bit yucky, as it adds to the problem wrongly being perpetuated by Microsoft that ctime stands for creation time instead of change time. But I guess all findutils can do is go by what stat() reports, and users must be aware that ctime==btime may be the indicator that btime is not supported for that file.
- -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] - -------- Original Message -------- Subject: Re: Support for st_birthtime Date: Mon, 26 Mar 2007 11:00:53 +0200 From: Corinna Vinschen On Mar 25 21:28, James Youngman wrote: > On 3/25/07, Eric Blake <[EMAIL PROTECTED]> wrote: > >And part of the joy of it being a CVS development snapshot is that I can > >give some feedback back to the cygwin developers - what would you rather > >have stat do when btime is not available for a given file? > > Set tv_sec to 0, and tv_nsec to UTIME_OMIT (if available) or to any > negative number. This is a non-issue, afaics. Windows filetime functions always return a creation time and I don't know filesystems which wouldn't return a creation time. Samba on linux for instance returns the last modification time as creation time. Corinna -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGB7yg84KuGfSFAYARAu2bAKDFeyWONKlqx0m9BwRfWed9KcYOSwCgzHqx 3haI0ZH0UtxQBNQDnyQx2wU= =0FLS -----END PGP SIGNATURE----- _______________________________________________ Bug-findutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-findutils
