From: Warner Losh <imp@bsdimp.com>
To: Arnold Robbins <arnold@skeeve.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] The 2038 bug...
Date: Thu, 31 Dec 2020 08:30:55 -0700 [thread overview]
Message-ID: <CANCZdfoKV7A46ho3ORghFZEddROty3A-y2bn1VY0m=ipBxFF6w@mail.gmail.com> (raw)
In-Reply-To: <202012310810.0BV8ADZ3027195@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
On Thu, Dec 31, 2020, 1:10 AM <arnold@skeeve.com> wrote:
> Will there be that many 32 bit systems left by then?
FreeBSD has 64bit time_t everywhere except i386. We looked at compat shims
and found like 200 system calls would need compat shims to keep a stable
ABI. Creating a new ABI is mostly a matter of fixing the places that know
time_t is 32 bit on i386.
Most likely, though, it will just be retired 15 years or so before the
deadline.
time_t these
> days tends to be 64 bits, and I think at least the Linux file systems
> store them that way.
Time_t was still 32 bits last I checked on i386 and a few others...
Microsoft counts time from January 1, 1980, so
> that buys them until 2048. :-)
>
> I'll be (G-d willing) 79 then; I hope around, but I also hope not
> overly involved with computers. :-)
>
I'll only be 72... with LORAN-C retired in the US the last of the
potentially problematic[*] code I've deployed is gone.
Warner
[*] Purely from a 32 bit time_t perspective.
Arnold
>
> Niklas Karlsson <nikke.karlsson@gmail.com> wrote:
>
> > I'll be a mere 58, so not even retired yet. I fear it will be a very
> > interesting time, in the "May you live in interesting times" sense.
> >
> > Niklas
> >
> > Den tors 31 dec. 2020 kl 08:21 skrev Dave Horsfall <dave@horsfall.org>:
> >
> > > As the new year is about to kick in (down-under anyway), it got me to
> > > thinking (always dangerous): how many here will be around for it to
> pick
> > > up the pieces that are no doubt still lying around?
> > >
> > > I'll be about the ripe old age of 85, so I may be around to see the
> > > Imminent Death of the Internet (Film at 11).
> > >
> > > 2100? Forget it... Too bad, as "Revolt in 2100 (?)" is one of my
> > > favourite Heinlein books.
> > >
> > > Others?
> > >
> > > -- Dave
> > >
>
[-- Attachment #2: Type: text/html, Size: 3366 bytes --]
next prev parent reply other threads:[~2020-12-31 15:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 7:19 Dave Horsfall
2020-12-31 7:24 ` Niklas Karlsson
2020-12-31 8:10 ` arnold
2020-12-31 15:30 ` Warner Losh [this message]
2020-12-31 16:09 ` Adam Thornton
2020-12-31 16:12 ` Larry McVoy
2021-01-11 7:18 ` alan
2021-01-11 14:01 ` Stuart Remphrey
2020-12-31 18:36 ` Theodore Ts'o
2020-12-31 21:34 ` Warner Losh
2021-01-06 16:32 ` Dario Niedermann
2021-01-06 17:08 ` Henry Bent
2021-01-06 18:05 ` Dario Niedermann
2021-01-06 18:20 ` Michael Kjörling
2021-01-06 21:09 ` Dave Horsfall
2020-12-31 19:18 ` Bakul Shah
2021-01-04 8:22 ` Peter Jeremy via TUHS
2021-01-04 9:13 ` Angus Robinson
2021-01-04 21:49 ` Dave Horsfall
2021-01-04 21:56 ` Warner Losh
2021-01-05 18:05 ` Dan Cross
2021-01-06 7:21 ` Warner Losh
2021-01-07 22:56 ` Stuart Remphrey
2021-01-08 1:25 ` Nemo Nusquam
2021-01-10 6:56 ` Stuart Remphrey
2021-01-04 8:59 ` Sergio Pedraja
2021-01-07 22:50 ` Stuart Remphrey
2021-01-10 7:16 ` Valdimar Sigurdsson
2021-01-10 7:24 ` Niklas Karlsson
2021-01-10 10:15 ` Stuart Remphrey
2020-12-31 15:05 M Douglas McIlroy
2020-12-31 16:51 ` arnold
2020-12-31 23:31 ` Steffen Nurpmeso
2021-01-09 8:44 Norman Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANCZdfoKV7A46ho3ORghFZEddROty3A-y2bn1VY0m=ipBxFF6w@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=arnold@skeeve.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).