|
Unix Millennium Bug | Y2K38 | Year 2038 problem | may cause some computer software to fail before or in the year 2038. The problem affects all software and systems that store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 UTC on Thursday, 1 January 1970.[1] The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038.[2] Times beyond this moment will "wrap around" and be stored internally as a negative number, which these systems will interpret as a date in 1901 rather than 2038. This will likely cause problems for users of these systems due to erroneous calculations. Further, while most programs will only be affected in or very close to 2038, programs that work with future dates will begin to run into problems much sooner. For example, a program that works with dates 20 years in the future will have to be fixed no later than in 2018. Because most 32-bit Unix-like systems store and manipulate time in this format, it is usually called Unix time, and so the year 2038 problem is often referred to as the Unix Millennium Bug. However, any other non-Unix operating systems and software that store and manipulate time this way will be just as vulnerable. A search shows that a fix was found in 2008, but I thought the problem targeted almost all 32-bit systems & 64-bit systems like way Way WAY INTO THE FUTURE?!? |
|
Seems like the worse that will happen is your clock will read Fri Dec 13 20:45:52 1901 |
|
I think computers will be upgraded between now and then so we should be fine. Just don't believe the media. If we are lucky they will make a good movie about this. LOL. |
|
It only exists in antiquated systems. Modern OSes, such as Windows, Mac OS X and Linux do not have such an issue. |
Is Unix Millennium Bug | Y2K38 | Year 2038 problem still an issue?: http://bit.ly/hlaXOj