On Thursday 2010-07-22 14:17, Volker Lendecke wrote: >On Thu, Jul 22, 2010 at 01:14:47PM +0100, David Howells wrote: >> Jan Engelhardt <jengelh@xxxxxxxxxx> wrote: >> >> > Linux already has a creation time field, it's called otime (there is no "b" >> > in "creation"), and you will find scattered fragments of that all over the >> > kernel (foremost, fs/jfs/, now btrfs, and I also notice sysvipc having >> > something with that name). >> >> It is? It's called crtime in Ext4. st_btime, however, would be compatible >> with BSD's stat, and Samba would just use it by way of autoconf magic if it >> appeared. Of course you can find remnants of btime in Linux's BSD-style task accounting, but Linux always looked more like SysV than BSD, speaking for otime. And if you are using autoconf, the cost of using otime over btime seems the same. >Samba has the following check: > ># recent FreeBSD, NetBSD have creation timestamps called birthtime: >AC_CHECK_MEMBERS([struct stat.st_birthtimespec.tv_nsec]) >AC_CHECK_MEMBERS([struct stat.st_birthtime], AC_CHECK_MEMBERS([struct stat.st_birthtimensec])) > >and the supporting code around that. "birth" might also be >where the "b" comes from :-) Well, in all reference to the Matrix movie, files aren't born. Except for Directory Default ACLs and possibly security labels, they usually don't inherit either :) And on a CS level, it's more like copy than inherit, because if the parent changes, the file does not (with the potential exception of security relabeling, bla). -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
