Great news, my Sheevaplug can now cross 2038.
Wow I forgot about those. Always wanted one but too expensive for me at the time.
I know the feeling, I also had to pay extra customs taxes because I’m in Europa and it was sold by an US company. :(
What’s a sheevaplug?
Dude that’s badass haha
@JustUseMint@lemmy.world you should read this: https://lemmy.world/comment/7295421
Thanks for sharing, there fucking awesome. Even more turned off from pi than I was before haha
Well then you may also like this comment here about the RPi’s lack of hardware innovation and features. And this one about how it is just a product that stays in between two very different markets and doesn’t really serve anyone.
I was fairly certain I was going to see an IoT buttplug there…
The thought crossed my mind to do that the actual device seemed more interesting.
The search term is censored by DuckDuckGo in Korea. Even robots apparently think it’s going to be an IoT buttplug.
As one of the first such computers on the market, the device has a 1.2 GHz Marvell Kirkwood 6281 ARM-compatible CPU, a.k.a. Feroceon.
Man this Pokémon thing is crazy, how many Eevolutions are there?!
The SheevaPlug was the OG Raspberry Pi released years before the Raspberry Pi that nobody cared about because there wasn’t a media hype around it.
Now the interesting part is: it included an ARM CPU @ 1.2 GHz and it was released in 2009 with dedicated Gigabit ethernet plus another isolated USB chip. Note that the Raspberry Pi was released years later, in 2012, with a 100M ethernet + USB shared chip that was total garbage. They kept selling that garbage until 2019 with the release of the Raspberry Pi 4 that finally came with Gigabit.
Another interesting fact about the SheevaPlug is that there was a variant with an eSATA port once again totally obliterating the Raspberry Pi 4 and making it the perfect low power system for a NAS at the time.
1.2 GHz
good thing they have 14 years to work on it
Only 9 if they want to include it in LTS release
Just 4 if they want to help Ubuntu prevent it in their LTS releases
Didn’t we learn our lesson 24 years ago with Y2K!?
The data lost that occurred due to the lack of differentiation between year 1900 and 2000 on calendar systems of the older computers?
Yes, that’s why we are patching
This mistake was made in the 70s when time was added to UNIX (or maybe already with Multics, idk)
Does anyone know when the new date limit will be?
Assuming they went to signed 64-bit time, it should be about 3:28:32 pm UTC on Sunday, December 4, 292277026596. Yes, that last number is a year.
That’s Saturday night in North American time zones. Just a heads up in case you’re planning a boys’ night out a couple hundred billion years in advance, maybe move it to Friday night in case the world ends Saturday night.
Holy shit.
It’s always nice to see futureproofing
