Hahah... would that be the clock that becomes sentient? On Sunday, December 1, 2019 at 9:23:46 PM UTC-8, gregebert wrote: > > A close-relative of the Y2K problem that was a hot issue 20 years ago. > > Now, for those of you who use software-based solutions such as the RasPi, > there is a ticking time-bomb waiting for us on January 19, 2038. On that > date, all software using 32-bit signed integers for the time will overflow. > UNIX-based operating systems use Jan 01, 1970 as the first point in time. > Jump forward about 2 billion seconds and you land in the year 2038. Not > everything has migrated to 64-bit integers yet, so beware. > > If you use NTP, which I do on a few clocks, there's trouble ahead in the > year 2036. I'm confident that will get patched soon enough. > > An of course, there's the Y10K problem that will bare it's ugly teeth 7980 > years from now.....but none of use will be there to worry about it. But I > think one of my clocks will still show the correct time.... >
-- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/2102c36a-3725-4c81-8851-91c9240e53e2%40googlegroups.com.
