The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Nigel Williams <nw@retrocomputingtasmania.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Interactive Systems (was Pcc for 386)
Date: Fri, 12 Jul 2019 13:00:10 -0400	[thread overview]
Message-ID: <CAC20D2Nw8e2QdyoSxxXS+dwp9xGhxwSJYHsBcj_JdQNhSNJY5A@mail.gmail.com> (raw)
In-Reply-To: <CACCFpdzqjQaQYFwrt0Dfx6vVVNZYLmFvDuGjQG2AYrCk3OtTkg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]

There were a number of them.  As others have meantioned, the TGV folks did
one, there were a number of tools from DECUS, and even DEC actually
released more and more UNIX into VMS themselves.   I used to carry a mag
tape with vi, the shell and few basic tools that allowed me to edit things
on VMS if I had to deal with it.  The biggest issue was TCP/IP, since
DECnet was the only networking for a such a long time from DEC.

Stan Smith and I wrote the original VAX IP/TCP support for Tektronix in
1979, in BLISS and some small amount of VAX assembler.  My friends (former
coworkers) @ CMU took this back in and enhanced it (the CMU folks did a
huge amount of work on the mail interface).  IIRC I sent the tape to Danny
Klein, but it might have been someone else.

I have the code from the CMU's update of our work on 9-track tape, but I
think it eventually also may have gone out on a DECUS tape.    But I do
know that this code base would make its way to DEC, where CJ and Wayne
would take it to become the code base that started OpenVMS's version [CJ
once told me he was impressed at how little they had to rewrite it, mostly
removing some Vaxism's - Stan and I were not worried about portability, we
just wanted something to talk correctly to the UNIX V7 TCP from 3COM (UNET)
and the TCP we had written from the Cyber NOS].

Clem

On Thu, Jul 11, 2019 at 11:56 PM Nigel Williams <
nw@retrocomputingtasmania.com> wrote:

> >> On Thu, 11 Jul 2019, ron@ronnatalie.com wrote:
> >> > (PDP-11, 386) and also there “UNIX running under VMS” product.
>
> Was there only three UNIX on VMS (or under...) options?
>
> Eunice:
> https://en.wikipedia.org/wiki/Eunice_(software)
>
> "phi"-nix: A Unix Emulator for VAX/VMS:
>
> https://scholarship.rice.edu/bitstream/handle/1911/101549/TR82-08.pdf?sequence=1&isAllowed=y
>
> ISC's IS/1-WB Work Bench for VMS (UNIX Tools only?)
>

[-- Attachment #2: Type: text/html, Size: 3111 bytes --]

  reply	other threads:[~2019-07-12 17:01 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 [this message]
2019-07-12 20:12         ` Deborah Scherrer
2019-07-12 20:45           ` Paul Winalski
2019-07-12 21:43             ` Deborah Scherrer
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=CAC20D2Nw8e2QdyoSxxXS+dwp9xGhxwSJYHsBcj_JdQNhSNJY5A@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=nw@retrocomputingtasmania.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).