Following the ‘Y2K Bug,’ We Must Brace for the More Serious ‘2038 Problem’

In 1999, humanity held its breath. As we enter the second millennium, it was feared that the entire computer ecosystem worldwide was going to crash. Some even went so far as to say that “the year 2000 bug” could have made the end of our civilization. And … nothing happened. Today, it is feared that January 19, 2038 will be synonymous with the end of time, computer speaking. And it's not nothing.

But let's start at the beginning, what do we mean by the bug or the 2038 problem? Well it's a matter of time.

Indeed, the 2038 problem will concern computer infrastructure that uses UNIX 32-bit time … It is almost the entire computer fleet in the world.

A 32-bit UNIX is a counter that knows how to manage a period of time equivalent to 2^32 seconds or about 136 years. In other words, on a computer with such technology the most remote date that can be achieved is December 13, 1901 at 8:45 p.m. and 52 seconds and the most advanced date is January 19, 2038 at 3:14 and 8 seconds.

After this date, since we will have reached the maximum time capable of being managed by the Unix 32-bit counter, and the time … will return to the minimum date capable of being managed by the counter.

In other words, a second after January 19, 2038 at 3:14 am and 8s, computers under Unix 32-bit will have a date corresponding to December 13, 1901 at 8:45 pm and 52s.

And you will see that it is not a simple bug.

The date changes and what?

It is true that says like that, it may be difficult to see the concern. However, as we have specified to you above, the 2038 problem should concern the majority of computer systems around the world.

In other words, banking, government, military or even data centers are subject to the UNIX 32-bit counter. And no, it will not be enough to open your calendar on Windows to give the time and date correctly because this is a question of display. UNIX 32-bit directly concerns the system of your computer and that of millions of machines around the world.

Thus, certain banking operations may be canceled or prevented because there would be a serious date problem in the bank's database. Indeed, if a transfer must be made on January 20, 2038, but for the bank, which uses a 32-bit UNIX system, we are on December 13, 1901, this transfer will therefore have to wait a very little before being made.

The world economy, among others, could therefore take a serious blow behind the head.

Since when are we informed?

You might think that the 2038 problem has been discovered very recently and that we have a little less than 13 years to react and find a solution. But this is not the case. Indeed, we know that the computer end of time has been scheduled for 2038 since 2006.

32 years to prepare for a problem that we cannot avoid, it is enough to arrive with a solution, right?

Well yes … and no. Since the solution, we know it. To avoid undergoing the 2038 problem which would be caused by the UNIX 32-bit counter, it would be enough to go to a Unix-64 bit system. Especially since it is not a question of moving from simple to double, since we speak of exponential values.

In other words, going to such a global system would allow us to delay so far the next problem of this kind that one could consider that it has been resolved.

Well, we know when the 2038 problem will have and how we can “counter” it. So, are we going?

Well, once again, the answer is not so simple. When it is said that the Unix 32-bit system is integrated into most computer systems in the world, we don't necessarily think that in computers. Some medical devices use the UNIX 32-bit system, also on-board technologies in cars too, connected objects too, IT infrastructure linked to energy or transport too.

In short, are we ready for the 2038 problem?

You will not please the answer since it depends on several factors. Indeed, if we have known the problem of 2038 for twenty years now, we have had time to produce systems that integrate the famous Unix-64 Bits.

However, even if we have started to take the bull by the horns, there are still too many systems today which are affected by the 2038 problem so that we can say that we are really ready.

Especially since an update between the 32 and the 64 bits is not done like that, even if it is possible and feasible, it will require time to adapt to the system concerned which means that whatever happens, “breakdowns” or “failures” could be felt for some time.

But is it always better than losing everything in 2038 not true?

Source : Iflscience