From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] OT: Grace Hopper, Unix epoch, ARPAnet converted to TCP/IP
Date: Mon, 1 Jan 2018 11:15:19 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1801011056290.99776@aneurin.horsfall.org> (raw)
In-Reply-To: <20171231234728.GA6542@wopr>
On Sun, 31 Dec 2017, Kurt H Maier wrote:
> I am confident ARPANET did not pin time to AEDT. Even if you go by UTC
> you've still got about fifteen minutes to wait for 1 JAN 2018.
So am I, but what reference *am* I supposed to use, FFS? The USA is
several zones behind UTC[*], and almost a whole day behind Australia
(where I live).
My "on this day" policy is to use the local time if it can be narrowed to
a particular zone where the event happened (and if it makes sense); if it
was universal e.g. moon landings then I'll use UTC; otherwise I'll use the
commonly-observed date e.g. the start/end of the world wars.
I'm open to suggestions (including FOAD, in which case I'll simply find
something better to do).
[*]
A lingering gripe that explains my latent anti-Americanism goes back to
when I had to support Uniplus 2.2/2.4 (sorta SysIII-ish) on the WICAT
boxes in here in Australia. At installation time, we had to express the
time offset as hours *west* of GMT; this left me with a lingering belief
that Americans didn't want to be perceived as being backwards (yeah. it
saved an entire keystroke out of the dozens that were otherwise required).
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2018-01-01 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 23:10 Noel Chiappa
2017-12-31 23:22 ` Dave Horsfall
2017-12-31 23:47 ` Kurt H Maier
2018-01-01 0:15 ` Dave Horsfall [this message]
2018-01-01 0:59 ` Kurt H Maier
-- strict thread matches above, loose matches on Subject: below --
2018-01-01 12:59 Noel Chiappa
2018-01-02 0:57 ` Ron Natalie
2018-01-02 16:19 ` Clem Cole
2017-12-31 22:51 Dave Horsfall
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=alpine.BSF.2.21.1801011056290.99776@aneurin.horsfall.org \
--to=dave@horsfall.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).