2038: only 21 years away
2038: only 21 years away
Posted Mar 15, 2017 19:34 UTC (Wed) by dmoulding (subscriber, #95171)In reply to: 2038: only 21 years away by amacater
Parent article: 2038: only 21 years away
And what about initramfs? It's a cpio archive, as well.
(Log in to post comments)
2038: only 21 years away
Posted Mar 15, 2017 19:50 UTC (Wed) by arnd (subscriber, #8866) [Link]
It's relatively easy in the kernel as we control the unpacking code.
We can either change the kernel to completely ignore the times in initramfs and pretend every file has the same timestamp, to ensure that nothing breaks in 2038 that isn't already broken, or we can apply some windowing and interpret negative timestamps as post-2038 times.
2038: only 21 years away
Posted Mar 15, 2017 22:23 UTC (Wed) by SEJeff (guest, #51588) [Link]
But what is the correct thing for the kernel to do? That is the fun question worth asking today.
2038: only 21 years away
Posted Mar 17, 2017 4:26 UTC (Fri) by jwarnica (subscriber, #27492) [Link]
Assume any timestamp before, say, 1995 is after (1995-1970)+(2032).
This will work for most of reality.
2038: only 21 years away
Posted Mar 23, 2017 15:03 UTC (Thu) by Wol (subscriber, #4433) [Link]
Until you find a photographer has scanned his negative archive and corrected the exif data ... :-)
I think that's a very dangerous assumption, though not likely to be a problem for the OS. It'll break user-space badly, though.
Cheers,
Wol