The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] shared memory on Unix
Date: Wed, 01 Feb 2017 11:33:05 -0700	[thread overview]
Message-ID: <201702011833.v11IX5Yu017326@freefriends.org> (raw)
In-Reply-To: <CAC20D2PJY7yAGARJFsQCOsqiZXKbW-158=kDgHS1V1PHt5YYGw@mail.gmail.com>

Clem Cole <clemc at ccc.com> wrote:

> Note that AT&T Marketing renames PWB 3.0 -- System III thinking that
> "Programmer's Workbench" would be a bad name to sell against IBM, and this
> it the first non-research system for License outside of the the labs.  If
> you look at the documentation set, et al - it all says PWB 3.0 on the cover
> and throughout   Also, the BSD vs AT&T wars basically start around this
> time....
>
> Roll the clock forward and here is an new problem the PWB 4.0 moniker was
> used internally,  but AT&T marketing want to get rid of the PWB term - so
> the decree comes down the next release is to be called System V.

Sort of. I did some contract work for Southern Bell circa 1983. They
were still part of the Bell System then. I worked on a PDP-11 running
Unix 4.0. At the time, the policy was to release externally one version
behind what was being run internally, so System III was released to the
world while the Bell System was using Unix 4.0.  I still have the manual;
I'm pretty sure "PWB" and "Programmer's Workbench" are not on the cover,
it was just called "UNIX".

As UNIX 5.0 was approaching, someone decided that to be one release
behind on the outside was dumb, thus the jump from System III to System V.

The doc I have describes UNIX as an operating system for the PDP-11,
the VAX 11/780 *and* the IBM S/370 series of systems and the source
code directory had the machine dependent bits for the IBM. Too bad
that stuff never made it out.

It's too bad that all I have is just the paper, but that's all I
could get.

That was a fun job, I learned a lot. Over lunch every day I read a few
more pages of the manual, basically reading it from cover to cover
by the time I was done. What a great way to learn the system!

Arnold


  parent reply	other threads:[~2017-02-01 18:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 14:18 Paul Ruizendaal
2017-02-01 16:21 ` Mary Ann Horton
2017-02-01 17:18   ` Clem Cole
2017-02-01 17:24   ` Joerg Schilling
2017-02-01 17:39     ` Marc Rochkind
2017-02-01 18:04       ` Clem Cole
2017-02-01 18:01     ` Clem Cole
2017-02-01 18:07       ` Marc Rochkind
2017-02-01 18:15       ` Joerg Schilling
2017-02-01 18:32         ` Marc Rochkind
2017-02-01 18:35           ` Joerg Schilling
2017-02-01 18:33       ` arnold [this message]
2017-02-01 19:11         ` Steve Johnson
2017-02-01 19:24           ` Marc Rochkind
2017-02-01 19:30         ` Clem Cole
2017-02-02  0:25           ` Nick Downing
2017-02-01 23:11   ` Paul Ruizendaal
2017-02-02  1:10     ` Clem Cole
2017-02-01 19:44 Noel Chiappa
2017-02-01 19:55 ` ron minnich
2017-02-01 21:40 ` Larry McVoy

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=201702011833.v11IX5Yu017326@freefriends.org \
    --to=arnold@skeeve.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).