So 2038 brings the end of time for 32bit architectures. It being some
twenty four years ahead, it may seem like there is plenty of time for folks
to migrate to 64bit architectures that are (mostly) unaffected by this
issue. However, 32bit processors are still being produced today in
extremely high volumes, and many of those systems are being used in
commercial, industrial and medical environments, where these systems may be
quite literally embedded into the walls and machinery and are expected to
run for 25 years or more. As these small systems become more and more
pervasive, the risks of major trouble in 2038 grow. And thatâs to say
nothing of the impact on future classic-car resale prices for fancy cars
like the Tesla when the high end in-dash display wonât work (gasp!).
Thus, the âjust upgrade to 64bitâ solution isnât really sufficient,
At the end of the day, there's really only two solutions: Either force users to use a 64-bit type, or re-index the time type. Both break capability somehow.
In a student project two-three years ago I have made a GPS tracker on an 8-bit ATmega. So 32-bit processors will probably live till 2100.
It must be pretty hard for them Linuxers to see that OpenBSD was first in quite anything.
It sounds like you have never tried OpenBSD 5.5. It's virtually unusable due to the reckless things OpenBSD lunies did to "solve" the 2038 problem. More then half the ports that do worked previously do not work in this release and more crash randomly. Examples include eclipse, netbeans, qtcreator, geany, etc.
Linux developers are the ones solving the 2038 problem properly. The BSDs are still behind Linux on this and they'll never catch up.
I use OpenBSD 5.6 where everything works well. Can't see your point.
Uhm, yes, I use Mac OS X 5.6. Or Windows 5.6. Or both of them.
No, actually I use OpenBSD-CURRENT. It was 5.5-CURRENT after the time_t switch (and everything worked perfectly), it's 5.6-CURRENT now. Grab the non-existing OpenBSD 5.6 here and tell me what's unusable there.
From the article:
It's the same thing as the Y2K problem back in 2000, isn't it? Fortunately, unlike Y2K, a fix to the kernel and recompiling some programs should solve the problem.For those out of the loop…
atoms in a grain of sand. Unless you meant fewer zeroes and dots, LOL. But, yes, I agree that it's a safe bet that a number of computers may still be running 32-bit Linux; perhaps a few satellites and space vessels; watches; alarm systems; and more. 2038 is only 24 years away.