Johan Adolfsson writes:
> The following patch gives a cramfs filesystem a single timestamp
> stored in the superblock. It uses the "future" field so no space is
> wasted. mkcramfs uses the newest mtime or ctime from the
> filesystem.
Agreed, it seems like a good idea to have a filesystem timestamp.
The future field should probably be saved for use as the offset of a
"secondary superblock" (or something like that) rather than squandered
for one field. At least, I think that was the original intent for the
field and it has always been my plan.
Maybe it would be easiest to overload the super.fsid.edition field?
Then you could have an option (probably a backward-compatible flag in
the superblock, but could be compile-time or mount-time) that indicates
that the edition number is a timestamp.
- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 30 2002 - 22:00:10 EST