From: Tom Perrine <tom.perrine+tuhs@gmail.com>
To: Jon Forrest <nobozo@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Documentation for Sys-V basic interpreter
Date: Sat, 20 May 2023 11:13:27 -0700 [thread overview]
Message-ID: <CAJq=PCUbf8PosTuGkio2PZYvroF3Rc1dHXtTkuKRhcRNNX1vsw@mail.gmail.com> (raw)
In-Reply-To: <6950b3d6-483b-cd7b-2ebf-78fa289e6271@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
I was at Logicon - we inherited some of that - including the PWB install -
when we continued their KSOS work.
That would have been around 1982-1983; when I got there the KSOS work
(hosted on PWB) was already underway.
If I could find that darned Modula compiler - I've got the original KSOS
source code for PDP-11.
Tom
On Sat, May 20, 2023 at 9:05 AM Jon Forrest <nobozo@gmail.com> wrote:
>
>
> On 5/20/2023 6:43 AM, Clem Cole wrote:
> > However, we know that while PWB was never
> > released officially outside of the Bell System
>
> I've mentioned this before. We had PWB at Ford Aerospace in
> the late 1970s. This was in the group that Mike Padlipsky and
> John Nagle were part of.
>
> Jon
>
>
[-- Attachment #2: Type: text/html, Size: 1126 bytes --]
next prev parent reply other threads:[~2023-05-20 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 15:06 [TUHS] " KenUnix
2023-05-19 19:46 ` josh
2023-05-19 20:15 ` [TUHS] " Clem Cole
2023-05-19 20:17 ` Clem Cole
2023-05-19 20:19 ` segaloco via TUHS
2023-05-19 23:26 ` KenUnix
2023-05-20 0:31 ` Clem Cole
2023-05-20 4:28 ` segaloco via TUHS
2023-05-20 13:43 ` Clem Cole
2023-05-20 14:16 ` KenUnix
2023-05-20 16:05 ` Jon Forrest
2023-05-20 18:13 ` Tom Perrine [this message]
[not found] ` <CAC20D2M1whQwZBaDyd0EMiXrxBG6GarxD-6sNGZ_OosYxgkDcA@mail.gmail.com>
[not found] ` <89eeadc5-271a-c984-e55e-662cfeb23f6b@gmail.com>
[not found] ` <CAC20D2MtnzD2DLJsNVecqsWosOdDaVvu+VAQtFr+DZs+gR2LbQ@mail.gmail.com>
2023-05-20 23:39 ` Tom Perrine
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='CAJq=PCUbf8PosTuGkio2PZYvroF3Rc1dHXtTkuKRhcRNNX1vsw@mail.gmail.com' \
--to=tom.perrine+tuhs@gmail.com \
--cc=nobozo@gmail.com \
--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).