>hence Linux will have the
>2038 bug.
>
>That said, how do we fix it? Or is it something we just believe will
>fix itself? It sounds like it is both a kernel and a libc issue. It also
>seems to me that the easiest thing is to go to 64 bits.
Seems to me the ideal fix is to add 64-bit time, but keep the 32-bit
interface for compatibility reasons. When 2038 comes the compatibility
interface breaks, while most people hopefully use the 64-bit interface
by then.
People may start fixing libs and apps as soon as the kernel interface is
there,
it is hard to start earlier. This is a good reason to do it early.
Using 64-bit values on a 32-bit machine is of course a bit slower, but
that's merely a reason for upgrading.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:16 EST