From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] Date madness
Date: Sun, 17 Dec 2017 11:33:27 -0500 [thread overview]
Message-ID: <BD315513-6F4C-4F12-9EDD-61BA04973524@cheswick.com> (raw)
In-Reply-To: <024c01d37752$c30d03b0$49270b10$@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
No, these weren’t seconds updates (though Plan 9 has a list it applies.) These were
off-by-one-hour problems at each time shift. There would be a sudden flurry of
hard, indignant work, then repeat next time shift. This was in V10 Unix.
> On 17Dec 2017, at 11:19 AM, Ron Natalie <ron at ronnatalie.com> wrote:
>
> Year corrections? Don't recall that but there were a bunch of changes to handle the insertion of leap SECONDS over the years.
>
> -----Original Message-----
> From: TUHS [mailto:tuhs-bounces at minnie.tuhs.org] On Behalf Of William Cheswick
> Sent: Thursday, December 14, 2017 9:10 AM
> Cc: The Eunuchs Hysterical Society
> Subject: Re: [TUHS] Date madness
>
> During my first few years in the Unix room (starting in 1988) there was what seemed like a semiannual flurry of leap year corrections made to research unix. Apparently, there was some aspect that kept misbehaving, with new bugs appearing at the next shift in time.
>
> I never bothered to investigate the specifics, but it happened over several years. There are probably some on this list who know more details.
>
> I don’t recall this being a problem on Plan 9.
>
> ches
>
>
next prev parent reply other threads:[~2017-12-17 16:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 18:01 Noel Chiappa
2017-12-12 18:21 ` Warner Losh
2017-12-13 15:07 ` Random832
2017-12-13 17:00 ` Jason Stevens
2017-12-13 17:18 ` Ron Natalie
2017-12-13 18:02 ` Arthur Krewat
2017-12-13 15:39 ` Wolfgang Helbig
2017-12-14 0:57 ` Dave Horsfall
2017-12-14 14:09 ` William Cheswick
2017-12-17 16:19 ` Ron Natalie
2017-12-17 16:33 ` William Cheswick [this message]
2017-12-17 17:54 ` Random832
2017-12-17 22:15 ` Dave Horsfall
2017-12-17 22:54 ` Ian Zimmerman
2017-12-16 18:12 ` Wolfgang Helbig
2017-12-12 18:31 Noel Chiappa
2017-12-13 15:56 Noel Chiappa
2017-12-13 16:08 Noel Chiappa
2017-12-13 16:23 ` arnold
2017-12-13 16:31 Noel Chiappa
2017-12-13 16:50 ` arnold
2017-12-13 17:16 Noel Chiappa
2017-12-13 18:53 ` Tom Ivar Helbekkmo
2017-12-13 20:46 ` arnold
2017-12-15 16:41 ` Paul Winalski
2017-12-15 17:19 ` Dave Horsfall
2017-12-16 15:45 ` Clem Cole
2017-12-16 3:39 ` Dave Horsfall
2017-12-16 3:45 ` Lyndon Nerenberg
2017-12-17 1:43 ` Dave Horsfall
2017-12-14 3:08 ` Dave Horsfall
2017-12-14 3:13 ` Warner Losh
2017-12-13 19:12 Doug McIlroy
2017-12-14 3:07 ` Random832
2017-12-15 3:04 ` Random832
2017-12-13 20:22 Noel Chiappa
2017-12-13 22:16 Norman Wilson
2017-12-14 0:24 ` Chris Torek
2017-12-17 16:20 ` Ron Natalie
2017-12-17 18:53 ` Tom Ivar Helbekkmo
2017-12-17 20:07 ` Ron Natalie
2017-12-16 10:50 Doug McIlroy
2017-12-16 16:11 ` Random832
2017-12-16 17:11 ` Ralph Corderoy
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=BD315513-6F4C-4F12-9EDD-61BA04973524@cheswick.com \
--to=ches@cheswick.com \
/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).