The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] What UNIX Artifacts Are Still Missing?
Date: Wed, 6 Dec 2017 20:27:57 +0100	[thread overview]
Message-ID: <B57771B3-4A89-4000-88C9-DE694B636E14@planet.nl> (raw)
In-Reply-To: <CAC20D2Mt42f0P7XYvsNSAJm76T=wvaNsc4Rd7LTxRby6WGfn0A@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]


> On 6 Dec 2017, at 18:13, Clem Cole <clemc at ccc.com> wrote:
> 
> On Wed, Dec 6, 2017 at 9:33 AM, Paul Ruizendaal <pnr at planet.nl> wrote:
> ​A​lthough Xenix predates Venix, I'm not sure it predates it on PC hardware. 

> ​It really depends how you count.   I was there at time when AT&T was negotiating the replacement for the V7 license with 10 of us (the 10 firms included Microsoft - the only time I can say I was in the room with Willy G. - but that's another story)​.  This work would become the System III license.
> 
> ​Xenix, which was V7 based originally, was target for the generic 8086 systems (as well as PDP-11, 68K and Z8000) but the Intel support was generic so it included the PC.
[...]

Yes, you are correct: In november 1981 Xenix ran on the Altos 8600. Once you run on one 8086 machine, the next is minor step.
https://en.wikipedia.org/wiki/Altos_Computer_Systems#ACS_8600

Your insights about licensing match with the chart on the ‘seefigure1’ website, and help explain some things about it.

Paul


  reply	other threads:[~2017-12-06 19:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.400.1512518427.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:25 ` Paul Ruizendaal
2017-12-06 12:58   ` Mutiny 
2017-12-06 14:33     ` Paul Ruizendaal
2017-12-06 17:13       ` Clem Cole
2017-12-06 19:27         ` Paul Ruizendaal [this message]
2017-12-07  6:14         ` Jason Stevens
2017-12-06 22:32       ` Dave Horsfall
2017-12-07  5:05         ` Jason Stevens
2017-12-07  5:46           ` Dave Horsfall
2017-12-07  5:40         ` Andy Kosela
2017-12-07  5:56         ` Robert Brockway
2017-12-07  6:07           ` Warner Losh
2017-12-07 17:47             ` Grant Taylor
2017-12-09  6:03               ` Nigel Williams
2017-12-07  6:14           ` Jon Steinhart
2017-12-07  7:02             ` Robert Brockway
2017-12-07 16:22               ` Jon Steinhart
2017-12-07 14:59             ` Larry McVoy
2017-12-07 15:40               ` Steve Simon
2017-12-07 15:42               ` Chet Ramey
2017-12-07 16:28             ` Clem Cole
2017-12-07 16:30               ` Clem Cole
2017-12-06 17:55   ` Warner Losh
2017-12-07 15:14 Noel Chiappa
2017-12-07 15:36 ` Nevin Liber
  -- strict thread matches above, loose matches on Subject: below --
2017-12-06 17:59 Rudi Blom
     [not found] <mailman.398.1512513526.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:22 ` Paul Ruizendaal
2017-12-05 22:45 Nelson H. F. Beebe
2017-12-05 22:21 Warren Toomey
2017-12-05 22:38 ` Robert Swierczek
2017-12-05 22:55 ` Angelo Papenhoff
2017-12-05 23:06   ` Warner Losh
2017-12-05 23:03 ` Dave Horsfall
2017-12-06  0:00 ` Robert Swierczek
2017-12-06  0:08   ` Grant Taylor
2017-12-06 15:23   ` Clem Cole
2017-12-06  5:54 ` arnold

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=B57771B3-4A89-4000-88C9-DE694B636E14@planet.nl \
    --to=pnr@planet.nl \
    /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).