We’ve still got time to fix it, and the next release of Debian will likely have a time-64 complete userland. I don’t know the status of other “bedrock” distributions, but I expect that for all Linux (and BSD) systems that don’t have to support a proprietary time-32 program, everything will be time-64 with nearly a decade to spare.
And it’s represented as a 64 bits value, which is over 500 billions years.
… About that… https://en.wikipedia.org/wiki/Year_2038_problem
We’ve still got time to fix it, and the next release of Debian will likely have a time-64 complete userland. I don’t know the status of other “bedrock” distributions, but I expect that for all Linux (and BSD) systems that don’t have to support a proprietary time-32 program, everything will be time-64 with nearly a decade to spare.
Yup. Gentoo people are working on it as well. This is only a problem on 32-bit Linux too, right?
I think it affects amd64 / x64 because they originally used a 32-bit time_t for compatibility with x86 to make multiarch easier.
I don’t believe it affects arm64.
This is for a 32bits encoded epoch time, which will run out in 2038.
Epoch time on 64 bits will see the sun swallow Earth before it runs out.
That’s the 32 bit timestamp