The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: random832@fastmail.com (Random832)
Subject: [TUHS] OT: American Culture
Date: Wed, 03 Jan 2018 09:19:01 -0500	[thread overview]
Message-ID: <1514989141.883521.1222880744.6EE78710@webmail.messagingengine.com> (raw)
In-Reply-To: <201801030242.w032grt0022600@coolidge.cs.Dartmouth.EDU>

On Tue, Jan 2, 2018, at 21:42, Doug McIlroy wrote:
> > 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).
> 
> But east postive is an artifact of north up.

Who says right is positive? Anyway, there's a natural reason to want east to be positive in this case completely independent of maps - so that your timezone offset is the number that you add to UTC to get the current local time, rather than subtracting.

Incidentally, the V6 code for ctime has the number of *seconds* west of UTC as an *int* - a situation rather worse for parts of Australia than simply requiring a negative number.

I'm not exactly sure what AUSAM does. The archive shows ctime.s (its own implementation) with "timezone" as zero, with a note saying to set it to 1*60.*60. for daylight saving. This suggests that the time was simply maintained with an epoch of 1970-01-01 00:00 AEST, but the time(II) manpage says GMT.


  reply	other threads:[~2018-01-03 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03  2:42 Doug McIlroy
2018-01-03 14:19 ` Random832 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 22:49 Norman Wilson
2018-01-04  2:59 ` Greg 'groggy' Lehey
2018-01-04 16:48   ` Tony Finch
2018-01-04 17:20     ` Warner Losh
2018-01-02 16:43 Clem Cole
2018-01-03 13:25 ` arnold

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=1514989141.883521.1222880744.6EE78710@webmail.messagingengine.com \
    --to=random832@fastmail.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).