Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Isn't the title clickbait? If it read "glibc in 32 bit user space is still not Y2038 compliant by default" I would not have clicked it.


Unfortunately you probably daily rely on multiple 32-bit linux machines, most of the time not realizing you do. I agree this should be mentioned in the title though.


Oracle Linux for ARM is purely 64-bit, with no 32-bit support at all. Busybox 32-bit binaries will run, but only 64-bit RPM packages are offered.

Aside from Android, it is the only ARM distribution that I know of with this property.


Which in turn means it doesn't run on a lot of hardware-- not everything is aarch64.


I was feeling the same, about the only thing I have using 32bit userspace these days are a few rPIs, little bit early to be panicking they may suffer from the Y2038 bug, most companies waited to about 6 months before the Y2K bug was going to hit before they started caring.


> I was feeling the same, about the only thing I have using 32bit userspace these days are a few rPIs, little bit early to be panicking they may suffer from the Y2038 bug

Quite the opposite if you're talking about rPIs: the small/embedded space is where things can live for a long time. They're the primary place to worrying about. Especially if you're talking about industrial processes.


But if we techies get way ahead of the problem this time, maybe we can prevent it becoming a mass hysteria as Y2K was.


If you spend large amounts of money today, fixing a system that is later decommissioned in 2029 or 2032… you wasted a lot of money.

The correct play could very well be to wait to the last second and pay absurd money for scarce experts to fix the systems.


The correct play is surely to be the scarce expert available at the last second.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: