Date: Mon, 30 Oct 2000 17:03:12 -0800
From: "H. Peter Anvin" <[EMAIL PROTECTED]>
I could definitely agree with this. time_t needs to go 64 bits too,
although we have a little more time for that...
Sorry, we don't have more time. NFSv3 already supports time values
that cannot be stored in a 32-bit signed time_t, and I've already had
compatibility problems with this between Linux, Solaris, and other
types of hosts. And NFSv4 will support a full 64-bit signed time_t.
I agree with Ulrich Drepper that LFS is better than nothing, but I'm
afraid that it's not enough. Even with LFS, 32-bit applications
cannot handle files whose timestamps do not fit in a time_t. Because
of this problem it is impossible to build reliable 32-bit versions of
standard GNU utilities (e.g. "find", "rm", "cp") in environments that
I regularly use.
This is a serious problem, one that LFS does not cure, unfortunately.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]