2038 ist näher, als man denkt – und diesmal tickt die Bombe im Silizium.
Ob Hardware-RTC, Mikrocontroller oder FPGA: Viele Chips haben nur 32 Bit Zeit übrig. Im Blog haben wir eine Übersicht erstellt: von Dallas RTCs bis zu STM32 und NXP LPC.
#year2038problem
👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“
Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr 1901.
Auf das Wortspiel bin ich ein bisschen stolz ☺️
🔗 https://y2k38.ch/time-t-cast-y2k38-bug/
#Y2K38 #time_t #CProgramming #Year2038Problem #Y2038 #2038Problem #CastAway
Der Kernel ist gefixt – der Kern des Problems nicht.
2025 sind die meisten Linux-Distributionen im Kernel Y2K38-ready – doch einige bleiben verwundbar oder werden nie aktualisiert.
Wir haben die Lage analysiert, die Distributionen in Kategorien eingeordnet und den aktuellen Stand festgehalten.
➡️ Zum Artikel: https://www.y2k38.ch/linux-distributionen
#Linux #Y2K38 #2038Bug #Kernel
#LinuxDistributionen #Y2K38 #2038Bug #UnixMillenniumBug #LinuxKernel #KernelUpdate #Year2038Problem
The real Y2038 problem is that my kiddo is gonna be a high school graduate
#parenting #y2038 #year2038problem #computing #kindergarten #kindergarteners
Are you worried about Y2K38 or the Year 2038 Problem?
Kinda annoyed that there wasn't even a spike in traffic on my website yesterday at 2025-04-16T19:07:44+00:00
https://www.epochalypse.today/
Was no one watching the bit flip to 01101000 00000000 00000000 00000000?
Anyway, see you guys at 2029-07-18T05:49:52+00:00 when it flips to 01110000 00000000 00000000 00000000, which is when we'll lose the next bit to the epochalypse.
#epochalypse #unix #unixtime #year2038 #year2038problem #y2k38 #software
Every day is one step closer to 03:14:07 UTC on 19 January 2038
https://en.wikipedia.org/wiki/Year_2038_problem
#Year2038Problem #Y2038 #Y2K38 #Y2K38 #Superbug #Epochalypse #UnixTime #Epoch
Fedora 43 will provide improved user experience!
#Fedora #FedoraLinux #Linux #TechNews #TechUpdates #Computers #Fedora43 #Year2038 #Y2038 #Y2038Problem #Year2038Problem
https://officialaptivi.wordpress.com/2025/03/10/fedora-43-and-rpm-6-0-jpeg-xl-wallpapers-and-more/
With LTS Linux distributions that have 10 years support, the #year2038problem will start in 2028 so in just four years.
I started on computers on IBM systems (System/3, OS/360, MVS, and later VM) before migrating to UNIX, BSD, and Linux. It occurs that most of today's *NIX jockeys are actually pure Linux jockeys.
Will UNIX (as opposed to Linux or BSD) will be a vague footnote by the time of the #year2038problem Epoch (03:14:07 UTC on 19 January 2038)???
Oh so THAT'S why Debian testing is such a mess right now...
the end of an era
coming soon(tm)
#year2038 #year2038problem #2038Bug #windowsmediaplayer #Windows #Windows7 #Microsoft #Y2038
Looks like #Debian is doing the #time64_t transition right now to solve the #year2038problem. That means there are a lot of really unstable packages in #unstable #sid right now.
@debian: This is misleading. The ML posting is solely about removing single packages from 32-bit architectures. We're hopefully not yet phasing out 32-bit architectures given that we just made one of the biggest if not the biggest library transition in #Debian ever solely to fix the #year2038problem on 32-bit architectures.
We are now 14 years away from software storing UNIX time as signed 32-bit integers overflowing and taking us back to 1901. Hopefully your software has been upgraded to store UNIX time in 64-bit integers!
It is now 03:14 UTC, January 19, 2023.
We are exactly 15 years away from the #Epochalypse. At this time on January 19, 2038, all computers that use a 32-bit signed integer to represent time will overflow and will show the time as 20:45:52 UTC, December 13, 1901. #Year2038Problem
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst