The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: arnold@skeeve.com
Cc: ken.unix.guy@gmail.com, tuhs@tuhs.org
Subject: [TUHS] Re: 3bsd tape image
Date: Wed, 30 Aug 2023 16:06:51 -0400	[thread overview]
Message-ID: <CAC20D2ON255uttrPHy+UG-FWrZ8b6WRgbgwX+TG14hwf7ofxng@mail.gmail.com> (raw)
In-Reply-To: <202308301921.37UJLHng001920@freefriends.org>

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

below...

On Wed, Aug 30, 2023 at 3:21 PM <arnold@skeeve.com> wrote:

> IIRC that was developed after 4.3 was released by Arthur David Olsen
> (elsie!ado), and then incorporated into 4.3 via the patches that CSRG
> sent out periodically.
>
You are probably right .. better memory. I knew it became widespread in a
BSD stream, but I did not realize it was donated to CSRG.
Thanks.

But the key point is that the timezone DB development and inclusion in UNIX
systems was much, much later in UNIX time and long after 1984 /usr/group
standard, where the use of the TZ variable began to spread to make it
easier for end users.

As Phil and I pointed out to Ken's original question, the V7-based systems
compiled the TZ info (number of minutes west of GMT) into the kernel and
supported a couple of primarily USA-based TZs in time(3) and the like.
 Which makes changing it for the local user a tad more complicated.   Then
again, you had the sources in those days, and at least the system
administrator recompiled the core kernel from scratch. [I remember Joy once
saying he thought rebuilding the entire system from the source at each site
was a good thing because that way, binaries were not stale].

Anyway, the placing of the TZ string into a program's environment was
pushed by the UNIX vendors, of course, because they were not releasing
binaries.
Thus, by the time of the TZ=xSTdyDT convention, the time(3) family was a
bit more flexible [*i.e.,* most of Europe was easily supported] - but you
still needed to know what to set it all to.

It was only much later, when the timezone DB code was created, that it
became easy to set the timezone in a more worldwide scheme.


ᐧ

[-- Attachment #2: Type: text/html, Size: 3880 bytes --]

  reply	other threads:[~2023-08-30 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  0:13 [TUHS] " Will Senn
2023-08-04  4:41 ` [TUHS] " Warner Losh
2023-08-04 17:17   ` Will Senn
2023-08-04 19:50     ` Clem Cole
2023-08-28 23:03 ` Phil Budne
2023-08-29 17:18   ` KenUnix
2023-08-30 11:11     ` KenUnix
2023-08-30 14:48       ` Clem Cole
2023-08-30 19:21         ` arnold
2023-08-30 20:06           ` Clem Cole [this message]
2023-08-30 20:07           ` Rich Salz
2023-08-30 20:34             ` KenUnix
2023-08-30 15:03       ` Phil Budne

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=CAC20D2ON255uttrPHy+UG-FWrZ8b6WRgbgwX+TG14hwf7ofxng@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=arnold@skeeve.com \
    --cc=ken.unix.guy@gmail.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).