The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arrigo Triulzi <arrigo@alchemistowl.org>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SPARC is CRAPS spelled backwards.
Date: Thu, 27 Sep 2018 09:52:51 +0200	[thread overview]
Message-ID: <93A6E956-D376-409D-995A-785534D7E5D0@alchemistowl.org> (raw)
In-Reply-To: <A301BE83-980F-4A42-8600-0EACC179B8F8@planet.nl>

On 27 Sep 2018, at 09:35, Paul Ruizendaal <pnr@planet.nl> wrote:
>> Did the 5150 have a UNIX available anywhere near its launch date?   I know
>> that it had DOS, CP/M-86, and the UCSD p-System relatively early on.  It's
>> not clear to me whether Xenix ever supported the original PC; were there
>> other early porting efforts?
> 
> The first version of Venix-86 ran on the PC/XT, almost a 5150, in May 83. It was V7 based. I think it was the first Unix on a PC.
> 
> Heinz Lycklama (who did Unix LSX and MX at Bell labs in the 70’s) did PC/IX about a year later, based  on Sys III. This was marketed by IBM.
> 
> Based on the early Xenix porting chart here http://seefigure1.com/2014/04/15/xenixtime.html , a PC/XT version of Xenix appeared around the same time as PC/IX. However, if the chart is correct there may have been Xenix versions for other 8086-based machines a year before that. Note that in this chart the “Xenix 2.0” and “Xenix 3.0” labels refer to MS internal versions, i.e. these numbers are not to be confused with the marketing labels IBM PC Xenix 2.0 and 3.0.

I am almost certain of the existence of a Unix variant for the Olivetti M24 which was an 8086-equipped PC (The M24 was rebranded as an AT&T 6300 if memory serves me correctly). It might have been Xenix or Venix but I honestly cannot remember it as I certainly recall Xenix floppies & manuals making the rounds later on 286s in Italy but I only faintly recall the M24 Unix.

Arrigo


  reply	other threads:[~2018-09-27  7:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27  7:35 Paul Ruizendaal
2018-09-27  7:52 ` Arrigo Triulzi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-28 12:08 Nelson H. F. Beebe
2018-09-27 21:07 Norman Wilson
2018-09-27 18:03 Nelson H. F. Beebe
2018-09-27 19:34 ` Nemo
2018-09-27 20:30 ` Dan Cross
2018-09-27 20:51   ` Cág
2018-09-27 21:01     ` Henry Bent
2018-09-27 21:04       ` Cág
2018-09-25 18:41 Noel Chiappa
2018-09-25 12:12 Noel Chiappa
2018-09-25 14:49 ` Theodore Y. Ts'o
2018-09-26 19:31   ` Derek Fawcus
2018-09-25 15:29 ` Arthur Krewat
2018-09-24 11:48 Noel Chiappa
     [not found] <mailman.98.1535822297.3725.tuhs@minnie.tuhs.org>
2018-09-23 18:37 ` Don Hopkins
2018-09-23 19:49   ` A. P. Garcia
2018-09-23 21:17     ` Paul Winalski
2018-09-24 11:25       ` Tony Finch
2018-09-24 19:46       ` Peter Jeremy
2018-09-24 20:20         ` Paul Winalski
2018-09-24 20:45           ` Arthur Krewat
2018-09-26  6:20             ` Peter Jeremy
2018-09-26  6:46               ` Lars Brinkhoff
2018-09-26 15:03                 ` Theodore Y. Ts'o
2018-09-26 15:32                   ` Paul Winalski
2018-09-26 15:44               ` Henry Bent
2018-09-26 18:24                 ` Donald ODona
2018-09-25 10:00         ` Tony Finch
2018-09-25 15:01           ` Larry McVoy
2018-09-25 19:48             ` Peter Jeremy
2018-09-25 18:34           ` Paul Winalski

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=93A6E956-D376-409D-995A-785534D7E5D0@alchemistowl.org \
    --to=arrigo@alchemistowl.org \
    --cc=pnr@planet.nl \
    --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).