The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@tuhs.org, segaloco@protonmail.com
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Fri, 12 Aug 2022 00:41:29 -0600	[thread overview]
Message-ID: <202208120641.27C6fTNJ015169@freefriends.org> (raw)
In-Reply-To: <zVLkYOXDMULs8ROpKVz-7jbOZXFe5gM0gtnpJhl8hw1g8N737Rts54AWyMzwIAmVFSoHP9mKiIltZkheQ-caace_QQEBe07gyCOccYuRl9g=@protonmail.com>

segaloco via TUHS <tuhs@tuhs.org> wrote:

> - This documentation refers to the last version as System III rather than
>   making any mention of 4.0.

This is because 4.0 was never released outside the Bell System. When I
did contract programming at Southern Bell, they told me that the practice
was to publicly release one version behind what was running internally;
thus System III was released when they were running 4.0 in the Bell System.

They changed their minds when it came to System V, deciding to release
the current internal version publicly as well.

I also suspect that the System V doc drops all mention of IBM S/370
support for Unix.

HTH,

Arnold

  parent reply	other threads:[~2022-08-12  6:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  1:33 segaloco via TUHS
2022-08-12  2:06 ` G. Branden Robinson
2022-08-12  6:41 ` arnold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-12 11:01 Paul Ruizendaal via TUHS
2022-08-12 11:15 ` arnold
2022-08-12 11:41   ` Jonathan Gray
2022-08-12 16:06     ` Warner Losh
2022-08-12 16:37       ` Warner Losh
2022-08-13 19:51         ` Paul Ruizendaal via TUHS
2022-08-08 23:52 segaloco via TUHS
2022-08-09  0:37 ` Al Kossow
2022-08-09  7:00   ` segaloco via TUHS
2022-08-09 12:49     ` Al Kossow
2022-08-09 15:14       ` segaloco via TUHS
2022-08-09 17:16         ` Warner Losh
2022-08-09 17:22           ` Will Senn

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=202208120641.27C6fTNJ015169@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=segaloco@protonmail.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).