The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: nobozo@gmail.com (Jon Forrest)
Subject: [TUHS] PWB - what is the history?
Date: Tue, 15 May 2018 08:14:35 -0700	[thread overview]
Message-ID: <34f124e4-9c08-290c-555d-17e6cb7b6190@gmail.com> (raw)
In-Reply-To: <20180515145938.GC7879@mcvoy.com>



On 5/15/2018 7:59 AM, Larry McVoy wrote:
> So what's the back story with PWB?  It seems like sort of a back water
> but as I recall, they had some interesting stuff.  I feel like there
> was a "learn" command and another one that tried to tell you about
> common grammer (english, not yacc) problems in your prose.  So far
> as I know, those didn't make it into the mainstream, or if they did,
> they were weak reimplementations that didn't work as well as the
> originals.

We used PWB at Ford Aerospace in the late 70s. It might have been
the closest to a commercial Unix version there was back then. John 
Mashey had a lot to do with PWB so maybe he can say a few words about
it if he's on here.

It's ironic - back in the late 70s there were almost as many
variations of Unix as there are Linux distributions now. It made the
commercial software vendors crazy because each required separate
development and QA resources, and none of them had enough traction
to be the only version that a vendor would support (like maybe
RedHat now).

Jon Forrest


  parent reply	other threads:[~2018-05-15 15:14 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 12:19 [TUHS] Who used *ROFF? Doug McIlroy
2018-05-14 12:41 ` Dave Horsfall
2018-05-14 13:00   ` Ralph Corderoy
2018-05-14 14:45   ` Clem cole
2018-05-14 15:04     ` Larry McVoy
2018-05-14 15:11       ` Larry McVoy
2018-05-14 15:21         ` Jon Steinhart
2018-05-14 15:46           ` Larry McVoy
2018-05-14 15:57             ` Jon Steinhart
2018-05-14 16:41           ` Nemo Nusquam
2018-05-14 18:13             ` arnold
2018-05-14 18:18               ` Jon Steinhart
2018-05-14 18:25                 ` Larry McVoy
2018-05-14 18:33                   ` Warner Losh
2018-05-14 15:04     ` Clem cole
2018-05-14 15:33       ` arnold
2018-05-14 21:32       ` Jaap Akkerhuis
2018-05-14 21:35         ` Clem Cole
2018-05-14 16:37     ` Ralph Corderoy
2018-05-14 23:04   ` Dave Horsfall
2018-05-14 23:42   ` Ron Natalie
2018-05-14 14:34 ` Larry McVoy
2018-05-14 14:46   ` Clem cole
2018-05-14 21:02   ` Dave Horsfall
2018-05-15 14:07     ` Nemo
2018-05-15 14:37       ` Dan Cross
2018-05-15 14:55         ` Clem cole
2018-05-15 14:59           ` [TUHS] PWB - what is the history? Larry McVoy
2018-05-15 15:13             ` Warner Losh
2018-05-15 15:14             ` Dan Cross
2018-05-15 19:48               ` Lyndon Nerenberg
2018-05-15 20:33                 ` John P. Linderman
2018-05-15 21:11                   ` Clem Cole
2018-05-15 21:41                     ` Lyndon Nerenberg
2018-05-15 15:14             ` Jon Forrest [this message]
2018-05-15 15:38             ` Clem Cole
2018-05-15 15:10           ` [TUHS] Who used *ROFF? Dan Cross
2018-05-15 12:20   ` Doug McIlroy
2018-05-14 15:10 ` arnold
2018-05-15 23:56 [TUHS] PWB - what is the history? Noel Chiappa
2018-05-16  0:08 Noel Chiappa
2018-05-16 14:05 Doug McIlroy
2018-05-17  4:37 Rudi Blom

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=34f124e4-9c08-290c-555d-17e6cb7b6190@gmail.com \
    --to=nobozo@gmail.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).