Language Selection

English French German Italian Portuguese Spanish

Y2038 bug may hit Unix, Linux machines

Filed under
Linux

After the Millennium bug for which several billions of dollars were committed for research and updations in computer systems the world over, there is yet another bug on the horizon. It is the Year 2038 bug that is slated to hit computer users in that year.

To be precise, on Tuesday, January 19 03:14:07 2038, machines prone to this bug will alter calendars to go back to Friday, December 13 20:45:52 1901.

Computer programmers predict that this can result in incorrect and wildly inaccurate dates being reported by the operating system and applications. It is likely to cause serious problems on many platforms, especially Unix and Unix-like and Linux platforms, because these systems will "run out of time". They are reluctant to predict the extent of the damage.

What is special about this date? It is explained that Unix and similar operating systems do not calculate time based on the Gregorian calendar. Instead, they are known to simply count time in seconds from their arbitrary "birthday", that is, GMT 00:00:00, Thursday, January 1, 1970. The accepted practice among software programmers is to use a 32-bit variable for this number (32-bit signed time_t). The largest possible value for the end integer in this calculation is 2**31-1 = 2,147,483,647. So, 2,147,483,647 seconds after Unix's birthday falls on Tuesday, January 19, 2038. And one second later, theoretically Unix systems will revert to their birth date (like an odometer switching back from 999999 to 000000).

Experts are of the opinion that Linux users will be the hardest hit, because of the wider acceptance of this OS for its security and cost features. They are feared to grind to a virtual halt or go into a loop. This Linux's own Y2K nightmare can be more damaging than the Y2K bug, because the latter basically involved applications while the 2038 bug affects the time-keeping function itself.

Linux gurus are apprehensive about the bug's impact on the embedded field, where software does not get replaced frequently. As such, major telecom gadgets and equipment will be greatly affected. However, one ray of hope is that the 32-bit processing can be replaced thus overcoming the impact of the bug -- definitely before 2038.

But, the optimism must end there. The bug can have severe impact on records created today with calculations going beyond 2038, like insurance policies. There could be error messages splashing on Unix and Linux screens then. And Linux is getting to be the popular operating system these days.

Experts say one and sure-short way to overcome the problem is to switch over to 64-bit or longer time_t data storage. Some of the existing 32-bit codes can be changed and the programs recompiled. However, all these are not very easy tasks.

Source.

Gone

I'll be dead by then so I'm not worried.

me too

that's what I was thinking... or at least so old I won't care... Tongue

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

QNX 7 Can Be Fitted With A Qt5 Desktop

  • QNX 7 Can Be Fitted With A Qt5 Desktop
    While QNX remains targeted as an operating system for mobile/embedded solutions, a BlackBerry developer in his spare time has fitted QNX 7 with a Qt5 desktop. QNX 6 and prior had a desktop option, but was removed in QNX 7, which was released this past March. QNX 7.0 also brought support for 64-bit (and maintaining 32-bit) Intel x86 and ARM platforms along with C++14 support. For those wanting to experiment with QNX 7, a BlackBerry kernel developer has been working on making this operating system more desktop friendly.
  • Building a BlackBerry QNX 7 Desktop
    Having Qt allowed me to port one of my favourite applications, SpeedCrunch. It was a simple matter of running ‘qmake’ followed by ‘make’. Next, I ported the QTermWidget library so that I could have terminal windows.

Kernel Space/Linux

  • Kernel explained
  • [Older] [Video] Audio on Linux: The End of a Golden Age?
  • State of Sway April 2017
    Development on Sway continues. I thought we would have slowed down a lot more by now, but every release still comes with new features - Sway 0.12 added redshift support and binary space partitioning layouts. Sway 0.13.0 is coming soon and includes, among other things, nvidia proprietary driver support. We already have some interesting features slated for Sway 0.14.0, too! Today Sway has 21,446 lines of C (and 4,261 lines of header files) written by 81 authors across 2,263 commits. These were written through 653 pull requests and 529 issues. Sway packages are available today in the official repos of pretty much every distribution except for Debian derivatives, and a PPA is available for those guys.

Supporting Burning Platforms

  • Surface revenue does a U-boat, and dives

    Revenue generated by Microsoft's Surface hardware during the March quarter was down 26% from the same period the year before, the company said yesterday as it briefed Wall Street.

    For the quarter, Surface produced $831 million, some $285 million less than the March quarter of 2016, for the largest year-over-year dollar decline ever.

  • Acer said to me: "do not use our products with Linux. Find another manufacturer"
    Last year, I bought an Acer notebook and it came with Windows 10. As I didn't want spyware neither bloatware, I got Linux installed and asked for a refund of the OEM license. After a little of talking, they were wanting to charge me US$100 (to remove the license, which I already had wiped, as I got FDE Linux installed) to refund US$70 of the OEM license. This year, wondering to buy a new Acer notebook, I asked them again if they would refund me the OEM license without all the hassle (as they did pay me the US$70, without me having to pay the US$100).

today's howtos