When I worked for Tandem back in the 80s, around 1985, they ran a
project they called Grandfather, where they decided to use the Julian
date in a 64-bit integer representing the number of microseconds since
4713 BC.
Since there are only 31,556,952,000,000 microseconds per year, that
means their clock would not roll over for around 580,000 years.
Good enough for me.
bp
<part15sbs{at}gmail{dot}com>
On 2/12/2024 2:38 PM, dmmoff...@gmail.com wrote:
https://en.wikipedia.org/wiki/System_time#Operating_systems
Fun chart here.
Linux kernels after 5.10 support dates up to July 2486. The 2038 thing
affects older kernels.
It also may impact a variety of other things that might have stored
dates as a 32 bit integer. File system time stamps, database time
fields, etc. The time data type in C was originally 32 bit, and
changing it to 64 bit creates compatibility problems for code which
assumed a 32 bit value. If it’s C compiled recently for a 64 bit
system then it maybe probably has a 64 bit time data type already, but
old software may run for a long time. People are already coding for
dates farther into the future than 2038 so the issue would be with
embedded systems that never get replaced or updated. I’m sure there
are innumerable examples, but I suspect most of them are systems that
don’t really care what year it is. If a negative value breaks it,
then reset the clock to 1978 and buy yourself another 50 years to get
your upgrade budget approved.
Interestingly, according to that chart, Windows supports dates past
the year 30,000, but the IBM PC BIOS only counts up to 2079. I
suppose the next panic will be when 2079 approaches.
-Adam
*From:*AF <af-boun...@af.afmug.com> *On Behalf Of *Bill Prince
*Sent:* Monday, February 12, 2024 3:54 PM
*To:* AnimalFarm Microwave Users Group <af@af.afmug.com>
*Subject:* Re: [AFMUG] OT 2038 Linux
Someone explain to me why the system clock is a signed integer?
We need the IPV6 version of the system clock.
Also please note that David Mills; the inventor of NTP passed away
January 17, 2024. He was known as "Father Time".
bp
<part15sbs{at}gmail{dot}com>
On 2/12/2024 11:53 AM, Ken Hohhof wrote:
I’m not President or a Senator or Supreme Court Justice, so in
2038 I plan to be retired or dead. It will be somebody else’s
problem.
*From:*AF <af-boun...@af.afmug.com>
<mailto:af-boun...@af.afmug.com>*On Behalf Of *Chuck McCown via AF
*Sent:* Monday, February 12, 2024 1:02 PM
*To:* af@af.afmug.com <mailto:af@af.afmug.com>
*Cc:* ch...@go-mtc.com <mailto:ch...@go-mtc.com>
*Subject:* [AFMUG] OT 2038 Linux
"The latest time which can be represented like this is 03:14:07
UTC on January 19, 2038," said Zimmie. "Once the timer is
incremented from this second, the value 'overflows' and goes from
being a large positive number to being a large negative number.
The next second this counter can represent is 20:45:52 UTC on
December 13, 1901. This is called the Year 2038 Problem."
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
