The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Labovitz <johnl@johnlabovitz.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] First ARPAnet transmission
Date: Mon, 29 Oct 2018 11:34:50 -0400	[thread overview]
Message-ID: <5B2BFC4F-6FAC-4104-9BCC-2D3C5C0B0970@johnlabovitz.com> (raw)
In-Reply-To: <CAC20D2N=HEks=2SK4rfHAU09KGAaCThNijeY6WVSH2OZYbh63Q@mail.gmail.com>

On Oct 29, 2018, at 10:19 AM, Clem Cole <clemc@ccc.com> wrote:

> I >>think<< it is more likely 06:30 UTC, as IIRC Daylight Saving Time finished mid-month so I think it would have been UTC+8:00 [not +7:00 which it would be now].   That said, Nixon [...shutter...] was in office and he put the US went on DST in the winter at some point due to the oil crisis (but I thought that was a year or so later).  I remember it all happening at the time - but I can do not put precise dates on any of it.

According to tzdata...

% zdump -v America/Los_Angeles | grep 1969
America/Los_Angeles  Sun Apr 27 09:59:59 1969 UTC = Sun Apr 27 01:59:59 1969 PST isdst=0
America/Los_Angeles  Sun Apr 27 10:00:00 1969 UTC = Sun Apr 27 03:00:00 1969 PDT isdst=1
America/Los_Angeles  Sun Oct 26 08:59:59 1969 UTC = Sun Oct 26 01:59:59 1969 PDT isdst=1
America/Los_Angeles  Sun Oct 26 09:00:00 1969 UTC = Sun Oct 26 01:00:00 1969 PST isdst=0

...it appears that DST was *not* in effect on October 30, 1969.

A caveat: tzdata’s docs warn that dates before 1970 may not be accurate. But because I’m fascinated by the cultural history embedded within that database, I downloaded the latest tzdata files to check. The relevant rules are in the ‘northamerica’ file:

Rule	CA	1948	only	-	Mar	14	2:01	1:00	D
Rule	CA	1949	only	-	Jan	 1	2:00	0	S
Rule	CA	1950	1966	-	Apr	lastSun	1:00	1:00	D
Rule	CA	1950	1961	-	Sep	lastSun	2:00	0	S
Rule	CA	1962	1966	-	Oct	lastSun	2:00	0	S
Zone America/Los_Angeles -7:52:58 -	LMT	1883 Nov 18 12:07:02
			-8:00	US	P%sT	1946
			-8:00	CA	P%sT	1967
			-8:00	US	P%sT

I wouldn’t say that’s definitive, but usually tzdata is a pretty good source.

Best,
—John

  reply	other threads:[~2018-10-29 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29  1:05 Dave Horsfall
2018-10-29  2:10 ` Greg 'groggy' Lehey
2018-10-29  6:42   ` Dave Horsfall
2018-10-29  7:16   ` Michael Kjörling
2018-10-29 14:19     ` Clem Cole
2018-10-29 15:34       ` John Labovitz [this message]
2018-10-29 21:13         ` Dave Horsfall
2018-10-30  0:11           ` Greg 'groggy' Lehey
2018-10-30 12:50             ` arnold
2018-10-30 22:12               ` Greg 'groggy' Lehey
2018-10-30 22:05             ` Dave Horsfall
2018-10-30  1:09           ` Bakul Shah
2018-10-30  3:55             ` Lars Brinkhoff
2018-10-30  6:07               ` Arno Griffioen
2018-10-31 21:10               ` Steffen Nurpmeso
2018-10-30  0:08         ` Greg 'groggy' Lehey
2018-10-29 23:28       ` Greg 'groggy' Lehey
  -- strict thread matches above, loose matches on Subject: below --
2017-10-28 22:13 Dave Horsfall
2017-10-28 22:40 ` William Cheswick
2017-10-29  2:44   ` 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=5B2BFC4F-6FAC-4104-9BCC-2D3C5C0B0970@johnlabovitz.com \
    --to=johnl@johnlabovitz.com \
    --cc=clemc@ccc.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).