If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Another Year Closer, Linux 4.21 Getting More Preparations For Y2038 Problem
IF we're all running 64 bit machines, there is no problem?
On 64-bit Linux, time_t has always been 64-bit, so the kernel interfaces are Ok (I guess, unless there's some ioctl's or something like that which still use a 32-bit timestamp?). There's still things like file formats, file system on-disk formats, network protocols etc. that store time in a y2038-problematic fashion, regardless of the bitness of the kernel.
So instead of `int` it will now be `unsigned long long int`? Isn't there a better way to tell time than using a 1970 epoch?
It will be a signed long long int, not unsigned. As others mentioned, it's somewhat arbitrary which start point one uses, and which resolution. Seconds since the 1970 epoch has the big advantage that it's compatible with POSIX, and what 64-bit systems already do.
Jokes aside, it it actually worth a thought if the computing landscape can change that dramatically within the next 20 years to hypothesize that Linux and friends might not play a relevant role at this time anymore. . .
Can it?
Current landscape is pretty different from what it was 20 years ago, most markets are saturated, hardware does not increase in power much over many years...
Comment