The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@tuhs.org, dave@horsfall.org
Subject: [TUHS] Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX
Date: Wed, 19 Jun 2024 00:55:46 -0600	[thread overview]
Message-ID: <202406190655.45J6tkVP902384@freefriends.org> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2406190758240.19266@aneurin.horsfall.org>

Dave Horsfall <dave@horsfall.org> wrote:

> On Tue, 18 Jun 2024, segaloco via TUHS wrote:
>
> [...]
>
> > The story I've gotten is AT&T policy was to release odd-numbered 
> > versions, so PWB 1.0, System III, and System V made it out into the 
> > world, PWB 2.0 and Release 4.0 stayed in the labs.  In the most 
> > technical sense, System IV never existed, what could've become it 
> > remained a Bell System-only issue.
>
> Thanks; I'd forgotten about AT&T's "odd-only" policy.
>
> -- Dave

In 1982 I did some contract C programming on Unix 4.0 on a PDP 11/70
at Southern Bell.  At the time, C programmers were not so common.

The "odd only" policy may be true, but it's not what I was told; I
was told that the policy was to release externally one version behind
what was being run internally.

With the consent decree done and Divestiture in the works, AT&T was
going to be allowed get into the computer business. So at some point,
someone decided that for System V, the current system would be released
externally.

I doubt we'll ever know the exact truth.

Interestingly, there was no printed reference manual for Unix 4.0;
I was given a 3.0 manual. The documents for Unix were for 4.0, these
were the equivalent of the Volume 2 doc in the research releases.
It seems that the major changes in 4.0 were kernel improvements.

Arnold

  reply	other threads:[~2024-06-19  6:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 15:41 [TUHS] " Nelson H. F. Beebe
2024-06-18 17:21 ` [TUHS] " Clem Cole
2024-06-18 17:38 ` segaloco via TUHS
2024-06-18 20:59   ` Dave Horsfall
2024-06-18 21:15     ` segaloco via TUHS
2024-06-18 22:00       ` Dave Horsfall
2024-06-19  6:55         ` arnold [this message]
2024-06-19 15:47           ` Clem Cole
2024-06-19 16:00             ` [TUHS] Unix single-machine licensing (was Re: Re: ACM Software System Award to Andrew S. Tanenbaum for MINIX) Al Kossow
2024-06-19 16:44               ` [TUHS] " Clem Cole
2024-06-26  8:42                 ` Al Kossow
2024-06-26 20:57                   ` Clem Cole
2024-06-27 14:10                 ` Jonathan Gray
2024-06-19 19:10               ` segaloco via TUHS
2024-06-19 19:35                 ` Jacobson, Doug W [E CPE]
2024-06-20  4:08                 ` segaloco via TUHS

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=202406190655.45J6tkVP902384@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=dave@horsfall.org \
    --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).