digitalcourage.social

BEOZ👉 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 ☺️🔗 <a href="https://y2k38.ch/time-t-cast-y2k38-bug/" rel="nofollow noopener" translate="no" target="_blank">https://y2k38.ch/time-t-cast-y2k38-bug/</a><a href="https://det.social/tags/Y2K38" class="mention hashtag" rel="nofollow noopener" target="_blank">#Y2K38</a> <a href="https://det.social/tags/time_t" class="mention hashtag" rel="nofollow noopener" target="_blank">#time_t</a> <a href="https://det.social/tags/CProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#CProgramming</a> <a href="https://det.social/tags/Year2038Problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Year2038Problem</a> <a href="https://det.social/tags/Y2038" class="mention hashtag" rel="nofollow noopener" target="_blank">#Y2038</a> <a href="https://det.social/tags/2038Problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#2038Problem</a> <a href="https://det.social/tags/CastAway" class="mention hashtag" rel="nofollow noopener" target="_blank">#CastAway</a>

Pyrzout :vm:The Epochalypse: It’s Y2K, But 38 Years Later <a href="https://hackaday.com/2025/07/22/the-epochalypse-y2k-but-38-years-later/" rel="nofollow noopener" translate="no" target="_blank">https://hackaday.com/2025/07/22/the-epochalypse-y2k-but-38-years-later/</a> <a href="https://social.skynetcloud.site/tags/HackadayColumns" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackadayColumns</a> <a href="https://social.skynetcloud.site/tags/year2038problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#year2038problem</a> <a href="https://social.skynetcloud.site/tags/computerhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#computerhacks</a> <a href="https://social.skynetcloud.site/tags/2038problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#2038problem</a> <a href="https://social.skynetcloud.site/tags/epochtime" class="mention hashtag" rel="nofollow noopener" target="_blank">#epochtime</a> <a href="https://social.skynetcloud.site/tags/timestamp" class="mention hashtag" rel="nofollow noopener" target="_blank">#timestamp</a> <a href="https://social.skynetcloud.site/tags/unixtime" class="mention hashtag" rel="nofollow noopener" target="_blank">#unixtime</a> <a href="https://social.skynetcloud.site/tags/epoch" class="mention hashtag" rel="nofollow noopener" target="_blank">#epoch</a> <a href="https://social.skynetcloud.site/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a>

IT NewsThe Epochalypse: It’s Y2K, But 38 Years Later - Picture this: it’s January 19th, 2038, at exactly 03:14:07 UTC. Somewhere in a dat... - <a href="https://hackaday.com/2025/07/22/the-epochalypse-y2k-but-38-years-later/" rel="nofollow noopener" translate="no" target="_blank">https://hackaday.com/2025/07/22/the-epochalypse-y2k-but-38-years-later/</a> <a href="https://schleuss.online/tags/hackadaycolumns" class="mention hashtag" rel="nofollow noopener" target="_blank">#hackadaycolumns</a> <a href="https://schleuss.online/tags/year2038problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#year2038problem</a> <a href="https://schleuss.online/tags/computerhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#computerhacks</a> <a href="https://schleuss.online/tags/2038problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#2038problem</a> <a href="https://schleuss.online/tags/epochtime" class="mention hashtag" rel="nofollow noopener" target="_blank">#epochtime</a> <a href="https://schleuss.online/tags/timestamp" class="mention hashtag" rel="nofollow noopener" target="_blank">#timestamp</a> <a href="https://schleuss.online/tags/unixtime" class="mention hashtag" rel="nofollow noopener" target="_blank">#unixtime</a> <a href="https://schleuss.online/tags/epoch" class="mention hashtag" rel="nofollow noopener" target="_blank">#epoch</a> <a href="https://schleuss.online/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a>

BEOZWir kommen der Lösung des Jahr-2038-Problems näher....ein kleines Stück <a href="https://det.social/tags/Y2k38" class="mention hashtag" rel="nofollow noopener" target="_blank">#Y2k38</a> <a href="https://det.social/tags/y2038" class="mention hashtag" rel="nofollow noopener" target="_blank">#y2038</a> <a href="https://det.social/tags/2038Problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#2038Problem</a> <a href="https://det.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://det.social/tags/ext2" class="mention hashtag" rel="nofollow noopener" target="_blank">#ext2</a> <a href="https://beoz.ch/ext2-dateisystem-wegen-2038-problem-auf-deprecated-gesetzt/" rel="nofollow noopener" translate="no" target="_blank">https://beoz.ch/ext2-dateisystem-wegen-2038-problem-auf-deprecated-gesetzt/</a>

HeliographTIL about the <a href="https://mastodon.au/tags/year2038" class="mention hashtag" rel="nofollow noopener" target="_blank">#year2038</a> <a href="https://mastodon.au/tags/2038Problem" class="mention hashtag" rel="nofollow noopener" target="_blank">#2038Problem</a> "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker: <a href="https://en.wikipedia.org/wiki/Year_2038_problem" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/Year_2038_problem</a> <a href="https://mastodon.au/tags/Y2038" class="mention hashtag" rel="nofollow noopener" target="_blank">#Y2038</a> <a href="https://mastodon.au/tags/Y2K38" class="mention hashtag" rel="nofollow noopener" target="_blank">#Y2K38</a> <a href="https://mastodon.au/tags/Y2K38" class="mention hashtag" rel="nofollow noopener" target="_blank">#Y2K38</a> <a href="https://mastodon.au/tags/epochalypse" class="mention hashtag" rel="nofollow noopener" target="_blank">#epochalypse</a>

Recent searches

Search options

Administered by:

Server stats:

#2038problem