On Tue, 12 Sep 2000, Jamie Lokier wrote:
> I'd love to see a filesystem feature where I could efficiently identify
> "changed files", where "changed" is defined by last time this application
> checked or something similar.
An in-filesystem revision number would do the trick. Could be REALLY
efficient. All you have to do is stat and you know if the thing really
changed, instead of just knowing a date that can be horked. I like! I
like a lot!
Something else that'd be nice would be to make Linux deal better with NFS
dates. The date presented by an NFS server for files is its timestamp.
If the linux NFS client code were to subsequently check the stamp after
performing an operation, it could use that to approximate the time error
and this problem would about 99% disappear, with a fudge factor of under a
second. Comments?
Later,
David
---------------------------------------------------------------------
A brief Haiku:
Microsoft is bad.
It seems secure at first glance.
Then you read your mail.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:16 EST