#y2k38 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #y2k38, aggregated by home.social.
-
⏰ Debian is doing the right thing, and far ahead of time. Rather than scrambling as 2038 approaches, Debian 13 “Trixie” will switch almost all supported platforms to 64‑bit time_t, even on 32‑bit architectures, to sidestep the Unix Epochalypse. It requires a sweeping change across thousands of packages, and means some older binaries may break, but it is a smart move done years early. I remember being there for the 16-bit to 32-bit migration. 😥 ⏳
TL;DR
⚠️ Y2K38 will overflow signed 32‑bit time at 03:14:07 UTC on January 19 2038
🛠️ Debian is switching to 64‑bit time_t on most 32‑bit platforms starting with Trixie
🧠 The change affects 6,429 packages and changes the ABI
🧪 Developers must test for regressions, especially around legacy compatibilityhttps://www.theregister.com/2025/07/25/y2k38_bug_debian/
#Debian #Y2K38 #UnixEpochalypse #EmbeddedSystems #Epochalypse #ctime #unix #linux #security #privacy #cloud #infosec #cybersecurity -
Die #unixzeit hat einen runden Geburtstag 🎉 Es sind jetzt genau 1710000000 (1.71 Mia) Sekunden seit dem Urknall (The #epoch) am 01.01.1970. Wir haben noch gut 437 Mio. Sekunden bis zur #Epochalypse , geniessen wir es!
-
Wochenrückblick, Ausgabe 24 (2024-03).
Diesmal mit WireViz (GraphViz für Verkabelungen 🤓), einem hypnotisierenden Blick auf die Bits des aktuellen Unix-Timestamps, Applite - dem macOS App Store für Homebrew Casks, noch mal llamafile (LLM für die Ausführung auf dem eigenen Rechner), dem BFG Repo-Cleaner und wie mir dieser helfen soll (BFG9000 kennt ihr auch noch?), Debugging-Tricks für die Browser Developer Tools, wieder Wildschweine im Garten und wie immer Techno.
#WireViz #GraphViz, #Timestamp #Y2K38 #Applite #llamafile #BFGRepoCleaner #BFG9000 #DevTools #Browser #WebDev #Debugging #Wildschwein #Techno
-
@climagic
the y2k38 bug always reminds me of #TimeTravel_0 aka #JohnTitor, someone who claimed to be an American soldier from #Tampa, #Florida, who claimed to have travelled from 2036 to the year 2000 to retrieve an #IBM5100 to debug various legacy programmes to prevent a catastrophe likely related to the #y2k38 problem: https://en.wikipedia.org/wiki/John_Titor