posted on Jan, 15 2004 @ 10:20 AM
Originally posted by Byrd
Same with the upcoming "Unix date problem." We know about it but it's a non-issue.
The Unix date problem happens because of the way Unix operating systems keep track of time. Time is measured in seconds since midnight, 1 January 1970
-- this is known as the "epoch." It is stored in such systems in a variable called "time_t," which can store a value up to 2,147,483,647 -- but no
On 19 January 2038 at 03:14:07, that number of seconds will have been reached, and time will be up.
Newer UNIX operating systems are already using 64bits to represent time_t.
Its something like: 9,223,372,036,854,775,807
64 bit signed value, (2^62 - 1)
For some reason I do not think that we will see this anytime soon. Thats well over 291 billion years.
Yawn. 64bit values. 128bit values. A new "Epoch". Wake me when something serious is about to happen.
Heck, even the 64bit versions of windows are safe and have time_t defined as 64bits.
But if you are still worried, I am seeling Year 2038 Insurance. Just in case!
[Edited on 1/15/04 by crayon]