From: Deborah Scherrer <dscherrer@solar.stanford.edu>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Interactive Systems (was Pcc for 386)
Date: Fri, 12 Jul 2019 14:43:44 -0700 [thread overview]
Message-ID: <3f4400b9-a243-d86a-11a6-473f0e93adea@solar.stanford.edu> (raw)
In-Reply-To: <CABH=_VSuUu+UpT1B1U4TUFw4H1zs3SPxaWHTMsua7ErrRkmhCA@mail.gmail.com>
I didn't do this port, so don't know the details. But it was done in
the late 70s (I think) and had broad distribution. When I collected
various Software Tools versions, I was not able to find the VMS one. Sorry.
Deborah
On 7/12/19 1:45 PM, Paul Winalski wrote:
> On 7/12/19, Deborah Scherrer <dscherrer@solar.stanford.edu> wrote:
>> There was also an extensive port of the Software Tools to VMS, done by
>> Joe Sventek at LBNL. Included at the key tools, the shell, pipes,
>> everything. Felt completely like Unix.
> How did the LBNL Software Tools for VMS implement pipes? I'm curious
> because DEC itself did a product in the mid-1980s called DEC Shell
> that was a VMS port of the Bourne shell and associated utilities. I
> wrote a VMS device driver that implemented pipes as a true VMS
> pseudo-device, similar to VMS mailboxes but with true Unix pipe
> semantics.
>
> -Paul W.
next prev parent reply other threads:[~2019-07-12 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 22:02 ron
2019-07-11 22:31 ` Dave Horsfall
2019-07-12 2:52 ` Warner Losh
2019-07-12 3:55 ` Nigel Williams
2019-07-12 17:00 ` Clem Cole
2019-07-12 20:12 ` Deborah Scherrer
2019-07-12 20:45 ` Paul Winalski
2019-07-12 21:43 ` Deborah Scherrer [this message]
2019-07-12 22:45 ` Clem Cole
2019-07-12 23:18 ` Deborah Scherrer
2019-07-13 0:24 ` Dave Horsfall
2019-07-13 0:36 ` Dave Horsfall
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=3f4400b9-a243-d86a-11a6-473f0e93adea@solar.stanford.edu \
--to=dscherrer@solar.stanford.edu \
--cc=paul.winalski@gmail.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).