- cross-posted to:
- hackernews@lemmy.bestiver.se
- debian@lemmy.ml
- cross-posted to:
- hackernews@lemmy.bestiver.se
- debian@lemmy.ml
cross-posted from: https://lazysoci.al/post/30920734
Relevant XKCD: https://xkcd.com/607/

If only we’d chosen 1944-12-02 08:45:52 as the Unix epoch, we could’ve combined two doomsday scenarios into one and added a really boring scene to that Roland Emmerich movie.
‘…(potentially setting time back to 1900)…’
From my understanding, unless I’m mistaken, wouldn’t the 32 bit time reset back to 1970 after the overflow/rollover?
https://en.wikipedia.org/wiki/Year_2038_problem
Timestamps that use signed int will go back to 1901 (-2,147,483,647)
Oh shit, I missed that part, I always thought it was an unsigned int… 🤦♂️
Well today I learned 👍
you’re wrong, but so was the article, so I guess that cancels out :D it’s late 1901
There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.
deleted by creator
Hmm, Debian and other long-term support distros are kind of in a tricky position with problems like these. On the one hand, they don’t want to break things, so they’ll often make changes like these relatively late. But on the other hand, someone might still run a current version of the distro in 2038, so they actually want to solve it as early as possible, too.
The actual transition happened ages ago - 2024 or so. A bunch of transitional packages in Testing and Sid had
-t64appended for a while.









