pulse Report This Comment
Date: January 01, 2025 04:19AM

I was working for a small ISP then. I'd been working to verify everything was Y2K compliant for some time before.

At exactly midnight I got paged for a system down that wasn't; one single, solitary system. And there was nothing wrong with it (and was running BSDi, which was fully Y2K compliant).

Never could figure out why the page.

Anyway, 2038 is the real issue. Hopefully I can be retired by then.

quasi Report This Comment
Date: January 01, 2025 11:45AM

What happens in 2038?

Anon - not logged in Report This Comment
Date: January 01, 2025 12:15PM

I think he means lazy windoze users - who can't adjust the date past 2038. Then again, why does windoze use that setting (all dates are between 1938 and 2038, from memory, not turning on another computer to check). An update from microsoft should fix it, but we've heard that before.

It's not going to bother me, but if you use windoze, from memory it's control panel-date/time-adjust 2038 to 2099 and forget about it. Unless you're going to live to 2099 with the same computer.

pulse Report This Comment
Date: January 01, 2025 02:18PM

Not even remotely windows related. Not even sure where you got such a thing from.

[en.wikipedia.org]

2038 is the 32bit Unix/Linux time issue which frankly makes Y2K look like amateur hour.

Basically every embedded system, from nuclear reactors to your TV, legacy financial systems to healthcare systems, flight controllers and GPS to your cars ABS system will run some variety of this in their infrastructure.

Even in another 14 years there will be a LOT of this still around, anything built from probably 1970-2015.