The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tih@hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [TUHS] Date madness
Date: Sun, 17 Dec 2017 19:53:22 +0100	[thread overview]
Message-ID: <m2vah5uqxp.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <024e01d37752$f1e95260$d5bbf720$@ronnatalie.com> (Ron Natalie's message of "Sun, 17 Dec 2017 11:20:24 -0500")

Ron Natalie <ron at ronnatalie.com> writes:

> I remember the fun and games when we had systems that went back and forth
> between UNIX and VMS.    VMS set the time of day clock in local time.
> UNIX set it to GMT.

We used TGV Multinet to put our VAX/VMS cluster on the Internet.  Great
product, and really great service!  I loved the simple ingenuity of the
daylight savings switch on that system: for the forward shift in the
spring, it would run the system clock at double speed for an hour, and
for the autumn changeover, it would run it at half speed for two hours.
Since it took place during the night, it didn't bother anyone, and it
let the VMS system (which, as you say, ran on local time) maintain a
strictly increasing system clock at all times.

-tih
-- 
Most people who graduate with CS degrees don't understand the significance
of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay


  reply	other threads:[~2017-12-17 18:53 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2017-12-17 20:07       ` Ron Natalie
2017-12-17 21:24         ` [TUHS] OT: trains [Was: Date madness] Ian Zimmerman
2017-12-17 22:35           ` Dave Horsfall
2017-12-18 13:03             ` Norman Wilson
2017-12-18 16:45               ` Ian Zimmerman
2017-12-19  0:48                 ` Dave Horsfall
2017-12-18 16:12           ` Steve Mynott
  -- strict thread matches above, loose matches on Subject: below --
2017-12-16 10:50 [TUHS] Date madness Doug McIlroy
2017-12-16 16:11 ` Random832
2017-12-16 17:11   ` Ralph Corderoy
2017-12-13 20:22 Noel Chiappa
2017-12-13 19:12 Doug McIlroy
2017-12-14  3:07 ` Random832
2017-12-15  3:04   ` Random832
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 16:31 Noel Chiappa
2017-12-13 16:50 ` arnold
2017-12-13 16:08 Noel Chiappa
2017-12-13 16:23 ` arnold
2017-12-13 15:56 Noel Chiappa
2017-12-12 18:31 Noel Chiappa
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
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

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=m2vah5uqxp.fsf@thuvia.hamartun.priv.no \
    --to=tih@hamartun.priv.no \
    /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).