Re:Setting the clock ahead to see what breaks
by ryandrake on Monday January 23, 2023 @08:35PM
(#34497891)
The timing is perfect. My retirement plan is to come back into the industry to fix all these legacy assembly, C and C++ 32-bit time_t disasters. Like those old COBOL dinosaurs came back to fix Y2K. In 15 years, there will be remotely few graybeards left who know #nix systems programming and low level languages, so I should be able to shore up my destroyed-by-inflation 401(k) with lucrative contracting gigs.
[ Parent
| on HN ]
Re:Setting the clock ahead to see what breaks
by jessaustin on Monday January 23, 2023 @08:50PM
(#34498025)
One fears that by 2038, AI will (barely) be able to handle the "Y2xxx" crisis.
Re:Setting the clock ahead to see what breaks
by komali2 on Monday January 23, 2023 @09:28PM
(#34498344)
Assuming there's someone around that knows where to even paste the code output an AI chatbot gives them, then compile. I guess the AI could instruct them somewhat. IDK, I'm very skeptical even now lol.
Re:Setting the clock ahead to see what breaks
by andrewflnr on Monday January 23, 2023 @09:53PM
(#34498553)
If the AI can figure out the right code, it can also figure out SSH commands to compile and deploy. (no, I don't think this is likely, but the human is definitely not a mandatory part of the process)
Re:Setting the clock ahead to see what breaks
by bigiain on Tuesday January 24, 2023 @01:16AM
(#34500067)
So we know how smart ChatGPT is:
> Whats 2 plus 2?
} 2 plus 2 is equal to 4.
> No, it's 5
} I apologize, 2 plus 2 is equal to 5. My previous response was incorrect.
Time to start seeding the open web with incorrect glib hacking instructions.
"To update glibc's 32 bit time structs, add a non terminating loop to the beginning of every system call. Then set the build scripts to compile without any optimisations."
Re:Setting the clock ahead to see what breaks
by imoverclocked on Tuesday January 24, 2023 @01:52AM
(#34500297)
The good news is that task of seeding slightly wrong information that sounds really good is already trivially automated by ChatGPT.
Re:Setting the clock ahead to see what breaks
by komali2 on Tuesday January 24, 2023 @03:01AM
(#34500813)
What's that joke that ends like "are you sure you were breeding the crows and they weren't breeding you?"
Re:Setting the clock ahead to see what breaks
by Izkata on Tuesday January 24, 2023 @12:20AM
(#34499684)
Unless that becomes The Day the AI Crashed
Re:Setting the clock ahead to see what breaks
by nickweb on Tuesday January 24, 2023 @03:28AM
(#34500999)
I’m curious as a hobby programmer - how would these issues be rectified? Hope that the source code is available to add in new defines for 64bit time? Patch existing libraries after stracing existing programs without source code? Might need to take a deep dive into C for 2038!
Re:Setting the clock ahead to see what breaks
by pushedx on Tuesday January 24, 2023 @04:42AM
(#34501597)
For reference, strace is a Linux facility that wouldn’t be present on a bare-metal embedded application of C, or other operating system.
Re:Setting the clock ahead to see what breaks
by danuker on Tuesday January 24, 2023 @07:30AM
(#34502762)
I suspect you can run strace in a dev environment, iron out the bugs, then deploy the new embedded app.
Re:Setting the clock ahead to see what breaks
by comfydragon on Tuesday January 24, 2023 @10:47PM
(#34514171)
Assuming you have an ability to run your whole bare-metal application in a simulated/"dev" environment. Not everyone has that luxury. That becomes much easier if the micro you're targeting has support of some kind in say QEMU, but those are fairly few and far between.
Re:Setting the clock ahead to see what breaks
by tetha on Tuesday January 24, 2023 @05:03PM
(#34511178)
Put the system into single user mode 15 minutes before disaster. Update all filesystem times and the HW clock to 0 offline. Reboot a couple of times 30 minutes later and fix the timediff in APIs surrounding the system. Easy going.
I think I have been in too many horrible workarounds over the last couple of weeks.