From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix half-billion years old 1985
Date: Mon, 4 Nov 2019 16:59:22 -0500 [thread overview]
Message-ID: <CAC0cEp_WX_aXRWnHcat8ZYbdvf8aeudGoU_SA2+Nj0Nc7v9sKA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1911050809230.11612@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
I wrote a near-trivial "timestamp" command to make it easier to do time
arithmetic (handy for scheduling a doctor's appointment a 90-day medicine
supply from now).
TZ=udt timestamp
119 11 04 21 50 06 18204 1572904206 Mon Nov 4 21:50:06 2019
TZ=udt timestamp 0
70 01 01 00 00 00 0 0 Thu Jan 1 00:00:00 1970
TZ=udt timestamp 500000000
85 11 05 00 53 20 5787 500000000 Tue Nov 5 00:53:20 1985
TZ=udt timestamp 1000000000
101 09 09 01 46 40 11574 1000000000 Sun Sep 9 01:46:40 2001
TZ=udt timestamp 1500000000
117 07 14 02 40 00 17361 1500000000 Fri Jul 14 02:40:00 2017
TZ=udt timestamp 2000000000
133 05 18 03 33 20 23148 2000000000 Wed May 18 03:33:20 2033
TZ=udt timestamp 2500000000
149 03 22 04 26 40 28935 2500000000 Mon Mar 22 04:26:40 2049
Not likely I'll live to see 2500000000. I surely won't live to see a
half-billion years.
On Mon, Nov 4, 2019 at 4:11 PM Dave Horsfall <dave@horsfall.org> wrote:
> On Tue, 5 Nov 2019, Dave Horsfall wrote:
>
> > UNIX was half a billion (500000000) seconds old on Tue Nov 5 00:53:20
> > 1985 GMT (measuring since the time(2) epoch).
>
> Aarrgghh! The subject should read "seconds", of course (too much blood in
> my coffee stream).
>
> -- Dave
>
[-- Attachment #2: Type: text/html, Size: 2277 bytes --]
next prev parent reply other threads:[~2019-11-04 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 21:08 Dave Horsfall
2019-11-04 21:10 ` Dave Horsfall
2019-11-04 21:59 ` John P. Linderman [this message]
2019-11-05 1:04 ` Anthony Martin
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=CAC0cEp_WX_aXRWnHcat8ZYbdvf8aeudGoU_SA2+Nj0Nc7v9sKA@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=dave@horsfall.org \
--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).