Comments on: Year 2038 problem

By: doomfan1

doomfan1 — Sun, 15 Feb 2026 21:12:31 +0000

“Windows 7 is so old that its successor is now discontinued.”

Windows 7 is so old now that next year, if it was a person in the United States, it would be eligible to vote next year.

By: ManelGarcia

ManelGarcia — Sat, 24 Jan 2026 11:25:09 +0000

En el 2000 no paso ni hubo ningún efecto, y ahora es otra patraña, para alarmar a la gente, yo creo que más un problema informático, lo vamos a tener entre países, dejemonos de vainas y paremos a Trump, que ese es el verdarero problema del mundo, gente como él sin cabeza.

By: Darren

Darren — Tue, 20 Jan 2026 11:40:29 +0000

Kinda off topic but as you mentioned it, 7:48 in this recent vid from a YT campervan guy, Office Space action 😉 https://www.youtube.com/watch?v=TlRXMqpl7AQ

By: Dave Farquhar

Dave Farquhar — Mon, 19 Jan 2026 23:34:09 +0000

In reply to Shirley Marquez. Yes, the embedded systems are the ones I'm most worried about. Tenable and its competitors can write vulnerability signatures to find non-2038 compliant applications and filesystems to make it easy(ish) to track mainstream Linux and Unix systems. But the embedded systems just sit there doing their thing and are very easy to ignore. And those are the ones doing things we need to not fail in early 2038. We don't notice them now, but we'll notice them when they're glitching.

By: Shirley Marquez

Shirley Marquez — Mon, 19 Jan 2026 22:22:44 +0000

If you go to a 64-bit Linux distro, as most desktop and laptop users already have, the OS won’t have a problem. But 32-bit applications can still have the issue, and users might still be running some of those. So can legacy filesystems, which people who upgraded from an earlier distro may still be using. (A newer filesystem will have 64-bit timestamps.) And there is the issue of embedded systems where the software doesn’t normally get upgraded at all.