The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Heinz Lycklama <heinz@osta.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] ACM Fellow, Ken Thompson
Date: Tue, 19 Jan 2021 14:29:57 -0800	[thread overview]
Message-ID: <66d2d6e9-921c-8039-1d84-0461f9192a28@osta.com> (raw)
In-Reply-To: <CANCZdfqNQC3TXMKuppiVybmYTXEz0h+HvE8QXEeh8sWeONPqnA@mail.gmail.com>

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

INTERACTIVE Systems Corp. (ISC) also ported a UNIX system to an
early VAX 750 computer running DEC's VMS operating system
starting in mid- 1978. ISC was in the business of porting the
UNIX operating system to many different computer hardware
architectures, mini-computers to mainframes, but the first
complete UNIX system port was actually done to the DEC VMS
system. We delivered the first UNIX on VMS system to a customer
in the Fall of 1979.  Many of these systems were delivered to
customers in North America as well as in Europe well into
the mid-1980's.

Heinz

On 1/15/2021 6:29 PM, Warner Losh wrote:
>
>
> On Fri, Jan 15, 2021 at 3:18 PM John Cowan <cowan@ccil.org 
> <mailto:cowan@ccil.org>> wrote:
>
>
>
>     On Fri, Jan 15, 2021 at 3:14 PM Dave Horsfall <dave@horsfall.org
>     <mailto:dave@horsfall.org>> wrote:
>
>         > Whose foray? Not DEC's.  Eunice was built at SRI and sold by
>         the
>         > Wollongong Group, who must have had Downundrian connections.
>
>          It was
>         originally developed ca. 1981 by David Kashtan at SRI[1] and later
>         maintained and marketed by The Wollongong Group.''
>
>
>     Where's the disagreement?
>
>
> Eunice post-dated DEC's first Unix offering by several years. They 
> sold V7 and later V7M before rebranding it to Ultrix. Eunice was 
> 4.1BSD (later 4.2 and 4.3) that Dr Kashtan grafted into VMS in ways 
> that... provoke strong feelings among reviewers...  The TCP/IP stack 
> that was inside of Eunice would form the basis for Wollongong's TCP/IP 
> offerings on VMS... A more refined version, also done I think by 
> Kashtan, was marketed by TGV and there was always much rivalry between 
> the two companies...
>
> Wollongong got its license because they were the marketing company 
> formed to market Dr. Miller's port to Interdata, and they later 
> branched out significantly because their license was so special...  Or 
> at least that's the story they told customers and internally... I 
> never saw the original license to know...
>
> Warner


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

  reply	other threads:[~2021-01-19 22:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 23:41 Royce Williams
2021-01-13 23:44 ` Deborah K Scherrer
2021-01-14  4:59 ` Dave Horsfall
2021-01-14  7:12   ` Robert Brockway
2021-01-14 22:35     ` Dave Horsfall
2021-01-14 22:22   ` John Cowan
2021-01-15 20:14     ` Dave Horsfall
2021-01-15 22:17       ` John Cowan
2021-01-16  2:29         ` Warner Losh
2021-01-19 22:29           ` Heinz Lycklama [this message]
2021-01-19 22:33             ` Warner Losh
2021-01-20  5:21               ` Heinz Lycklama
2021-01-17 22:19         ` Dave Horsfall
2021-01-14  9:50 ` Thomas Paulsen
2021-01-14 13:21 ` Jim Capp
2021-01-14 15:19   ` Steffen Nurpmeso
2021-01-14 21:27     ` Ken Thompson
2021-01-14 22:57       ` Steffen Nurpmeso
2021-01-14 14:20 ` Niklas Karlsson
2021-01-15  4:26 ` Ed Bradford

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=66d2d6e9-921c-8039-1d84-0461f9192a28@osta.com \
    --to=heinz@osta.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).