3 ms·
I wonder about that. I expect the replacement system will allow timestamps after 2038, but will we also be able to timestamp files from pre-1970?
by m463 3y ago
I wonder about that. I expect the replacement system will allow timestamps after 2038, but will we also be able to timestamp files from pre-1970?
- TheSoftwareGuy 3y agoI think the easiest thing to do is to love to 64 but timestamps, not changing the epoch
- rsynnott 3y agoThe replacement system’s already here; modern OSes and software tend to use 64bit ints for timestamps. The trouble is all the old embedded systems, and time_t->i32 casts which are currently fine, but lying in wait…
- stabbles 3y agoThe replacement is not without issues: each package can pick an ABI, nothing is enforced. A define in C toggles time_t between 32 and 64 bits, so if that struct is exposed in a library, dependents have to deal with it. Similar of course to 32 vs 64 bit file offsets.
- deleted 3y ago[deleted]
- dylan604 3y ago>but lying in wait… This brings back memories of all of the Y2K doomsayers about airplanes falling out of the sky, gas pumps not working, and all of the other just wildly bonkers theories people came up with. Even without the help of social media, these notions spread like wildfire.
- wizzwizz4 3y agoPlanes will be fine; but many of those things actually will happen as a result of Y2038. Embedded systems with ancient versions of Linux will stop being able to verify certificates, and I bet there are some digitised pumps that rely on that.
- doublepg23 3y agoA lot of stuff would have broken during y2k if a lot of engineers hadn't put in a massive effort. We know this because we just changed the clocks to 2000 and things broke...badly.
- dylan604 3y agoI wasn't suggesting it wasn't a real issue that needed solving. Just that the end of days scenarios were blown well out of proportion. The preppers community really came into their own and out of the shadows. Even my ex-in-laws were buying drums full of flour and what not storing them in their suburban backyard.
- conradludgate 3y agoIf they weren't blown out of proportion, they might not have been fixed and the bad situations might have happened. Sometimes you need to spread fear to get stuff fixed. But then people think "oh it wasn't that bad, those engineers are just the boy who cried wolf" and then next time they won't take us seriously
- hoseja 3y agoFlour? That sounds unoptimal. Probably rice would be better?
- dylan604 3y agoAnd what not. You missed that bit trying to be smart. Their whole 8’ wooden privacy fence was lined with weatherproof blue drums full of various foodstuff. Yes, they had rice, beans, various grains. I’m not a damn prepped, so I just rolled my eyes at the whole thing. I always assumed the weatherproof wasn’t really and it would all be ruined after the first rain. But yes smarty pants, they had all of that stuff. Don’t you feel good about yourself now?
- krebspsycho 3y agoY2K's kin are still out there... I work with an electronic health records system. Recently they delivered a patch to customers because on Nov 8th 2023 around 0100 in the morning their time field internally would exceed its number of characters allowed. This was weird to hear about nowadays but I was still not surprised. They botched the patch and it was not a good time when it happened. A big chunk of their older code based systems use an epoch of Mar 1,1980, another newer code chunk uses Mar 1, 1992 as their epoch. And I've been told their newest platform uses yet another epoch, or calculates times in such a way to not be concerned. So while their patch increased the field size for the seconds counter, it has done so a few times only fixing the fields that use the epoch about to be hit, rather than all of them. In top of that, after the counter grew by a digit on Nov 8th,2023, they then realized, much to many hospital customer displeasure, that not all their code the displayed medical documentation/results, often sorted by most recent, accounted for the field size correctly, requiring two more patches last week. Math with time is hard, and even harder to know what systems have moved forward with enough future thought to still not have these surprises sitting in wait deep in their codebase.