The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, imp@bsdimp.com, arnold@skeeve.com
Subject: Re: [TUHS] System IV
Date: Thu, 10 Jun 2021 02:04:50 -0600	[thread overview]
Message-ID: <202106100804.15A84oTN014058@freefriends.org> (raw)
In-Reply-To: <202106100758.15A7weqm013326@freefriends.org>

One other thing that was cool was that the doc defined UNIX as "an
operating system for the DEC PDP-11, DEC Vax, and the IBM System/370".  :-)

arnold@skeeve.com wrote:

> Warner Losh <imp@bsdimp.com> wrote:
>
> > So I've seen a number of places that talk about Unix TS 3.0 -> 4.0 -> 5.0
> > progression and how System III was released and System V was released and
> > System IV was internal only.
> >
> > What I've not seen is the "why" part of this. Why was it internal only?
> >
> > Warner
>
> I did some contract programming at Southern Bell (one of the operating
> companies) for a while, starting in the summer of 1982.  We used
> USG Unix 4.0 on a PDP-11/70. There were also vaxen.
>
> It was no longer being called PWB by then. In fact, I think that PWB
> was V6 based and an ancestor of System III.  
>
> System III had been released to the world.  When I asked why AT&T
> hadn't released Unix 4.0, I was told that the policy was to release
> one version behind what was being run internally.
>
> After the Bell System break up (1/1/1984), AT&T decided to just
> release what was current, thus the jump to System V, with "System IV"
> never having gotten outside the Bell System.
>
> When I was doing the contract work, although we were on Unix 4.0,
> we used documentation from Unix 3.0; they didn't bother reprinting /
> updating the manuals since the primary changes were apparently
> performance improvements in the kernel. (For example, they moved
> to hash tables for many things instead of simple linked lists.)
>
> I still have the reference manual and the photocopies I made of all
> the other documentation. :-)
>
> There was also a screen editor, named 'se' (NOT related to the Georgia
> Tech 'se' editor) which they'd managed to shoehorn onto the '11.
> It was kinda cool. I used both it and 'ed'. vi was also available but
> I found the modal stuff weird and didn't end up learning it until a year
> or two later. :-)
>
> Hope this is of interest.
>
> Arnold

  reply	other threads:[~2021-06-10  8:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 19:37 Warner Losh
2021-06-09 20:03 ` Clem Cole
2021-06-10  7:58 ` arnold
2021-06-10  8:04   ` arnold [this message]
2021-06-10 16:05   ` Clem Cole
2021-06-10 16:08     ` Andrew Hume
2021-06-10 17:36       ` 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=202106100804.15A84oTN014058@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=imp@bsdimp.com \
    --cc=tuhs@minnie.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).