The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: clemc@ccc.com, andrew@humeweb.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] System IV
Date: Thu, 10 Jun 2021 11:36:17 -0600	[thread overview]
Message-ID: <202106101736.15AHaH7t032126@freefriends.org> (raw)
In-Reply-To: <5C5352B2-0CD4-4C9A-8CDF-81363FB26E85@humeweb.com>

Andrew Hume <andrew@humeweb.com> wrote:

> i will simply observe that when i joined bell labs in 1981, i was on
> the System III team. we certainly did internal releases under that name..

I assume you mean under the name "PWB". I stand corrected.  At Southern
Bell I'm pretty sure the doc did not use that name though.  However, it's
been close to 40 years and I don't feel like digging out the manuals
to check. :-)

Thanks,

Arnold

>

> > On Jun 10, 2021, at 9:05 AM, Clem Cole <clemc@ccc.com> wrote:
> > 
> > 
> > 
> > On Thu, Jun 10, 2021 at 3:59 AM <arnold@skeeve.com <mailto:arnold@skeeve.com>> wrote:
> > 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.
> > I was under that impression - I had referred to it in my message as the 'pre-Judge Green release rules.' 
> > 
> > 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.
> > Right.
> >  
> > 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. :-)
> > I remember seeing se -- Brian Redman showed it to me IIRC.  I never tried using it myself.  I remember that he was not happy that it was not vi.   If I recall the argument in USG was many of the BSD tools were not better or even as good as what USG had already created.  But the USG folks did eventually add some of them to their stream because so many internal sites were already using them.  In particular, v, csh and col -- but there were others too and the argument was we have those tools covered already i.e. pg vs. more or se vs. vi
> > 
> >   
> > 
> > Hope this is of interest.
> > Definitely -- thank you.
> > 
> > Clem 
> > ᐧ
> > ᐧ
>

      reply	other threads:[~2021-06-10 17:37 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
2021-06-10 16:05   ` Clem Cole
2021-06-10 16:08     ` Andrew Hume
2021-06-10 17:36       ` arnold [this message]

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=202106101736.15AHaH7t032126@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=andrew@humeweb.com \
    --cc=clemc@ccc.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).