5 ms·
"OpenBSD is one of the first operating systems to be safe from the “Year 2038 Problem”. 64-bit time was introduced in 2013, so you don’t have to worry about the
by belter 5y ago
"OpenBSD is one of the first operating systems to be safe from the “Year 2038 Problem”. 64-bit time was introduced in 2013, so you don’t have to worry about the Unix Epoch 32-bit issue."
https://why-openbsd.rocks/fact/64bit-time/ https://why-openbsd.rocks/fact/64bit-time/
- doublepg23 5y agoDoes this just break applications expecting 32-bit time? It's certainty one way to do it, but I'm pretty sure this is unacceptable to most kernels.
- mjevans 5y agoIIRC Not if they were using the OS time type. I recall BSD is entirely compiled from a shared repository so the only breaking software would be external applications and possibly saves that have an incompatible timestamp baked into the file format. Anything outside of their 'ports' package repo.
- segfaultbuserr 5y agoYes. OpenBSD famously has an official policy of not providing binary compatibility. You can always break userspace for the benefits of code quality and safety. ABI has changed? No big deal, just recompile. Furthermore, since OpenBSD is an entire operating system, not just a kernel, the project has power to apply technical decisions to userspace, so you have more control to do that at will.