From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: 'Clem Cole ' <clemc@ccc.com>,
'M Douglas McIlroy ' <m.douglas.mcilroy@dartmouth.edu>
Cc: 'TUHS main list ' <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference
Date: Wed, 7 Apr 2021 08:59:54 +0800 [thread overview]
Message-ID: <0F0B9BFC06289346B88512B91E55670D3011@EXCHANGE> (raw)
There is some information and demos of the early 8086/80286 Xenix,
including the IBM rebranded PC Xenix 1.0 on pcjs.org
https://www.pcjs.org/software/pcx86/sys/unix/ibm/xenix/1.0/
And if you have a modern enough browser you can run them from the browser as
well!
It's amazing that CPU's are fast enough to run interpreted emulation that is
faster than the old machines of the day.
-----Original Message-----
From: Clem Cole
To: M Douglas McIlroy
Cc: TUHS main list
Sent: 4/7/21 1:09 AM
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference
Doug -- IIRC IBM private-labeled a Microsoft put out a version of Xenix,
although I think it required an PC/AT (286)
<https://mailfoogae.appspot.com/t?sender=aY2xlbWNAY2NjLmNvbQ%3D%3D&type=
zerocontent&guid=6f435ae6-0f2c-4fbd-bfe2-adcbf3edac32> ?
On Tue, Apr 6, 2021 at 11:36 AM M Douglas McIlroy <
m.douglas.mcilroy@dartmouth.edu <mailto:m.douglas.mcilroy@dartmouth.edu>
> wrote:
> I wonder. IBM introduced the IBM PC in August of 1981.
> That was years after a non-memory managed version of
> Unix was created by Heinze Lycklama, LSX. Is anyone
> on this list familiar with Bell Labs management thoughts
> on selling IBM on LSX rather than "dos"?
IBM famously failed to buy the well-established CP/M in
1980. (CP/M had been introduced in 1974, before the
advent of the LSI-11 on which LSX ran.) By then IBM had
settled on Basic and Intel. I do not believe they ever
considered Unix and DEC, nor that AT&T considered
selling to IBM. (AT&T had--fortunately--long since been
rebuffed in an attempt to sell to DEC.)
Doug
next reply other threads:[~2021-04-07 0:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 0:59 Jason Stevens [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-10 18:12 Paul Ruizendaal via TUHS
2021-04-06 15:35 M Douglas McIlroy
2021-04-06 17:09 ` Clem Cole
2021-04-06 17:32 ` Charles H Sauer
2021-04-06 20:11 ` Josh Good
2021-04-06 20:26 ` Jim Capp
2021-04-06 20:47 ` Charles H Sauer
2021-04-07 16:42 ` Josh Good
2021-04-07 18:04 ` Charles H. Sauer
2021-04-07 2:49 ` Dave Horsfall
2021-04-07 6:04 ` arnold
2021-04-07 16:01 ` heinz
2021-04-06 21:06 ` Clem Cole
2021-04-07 0:58 ` heinz
2021-04-07 1:37 ` Warner Losh
2021-04-07 3:38 ` Dave Horsfall
2021-04-07 2:30 ` Ed Bradford
2021-04-07 2:44 ` Charles H. Sauer
2021-04-06 20:20 ` Boyd Lynn Gerber
2021-04-06 22:41 ` Dave Horsfall
2021-04-07 1:10 ` Jon Steinhart
2021-04-07 1:47 ` Greg 'groggy' Lehey
2021-04-07 1:49 ` Jon Steinhart
2021-04-07 1:58 ` Larry McVoy
2021-04-07 2:31 ` Serge Burjak
2021-04-09 21:24 ` Michael Parson
2021-04-10 3:33 ` Ed Bradford
2021-04-10 15:12 ` Clem Cole
2021-04-10 15:41 ` Larry McVoy
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=0F0B9BFC06289346B88512B91E55670D3011@EXCHANGE \
--to=jsteve@superglobalmegacorp.com \
--cc=clemc@ccc.com \
--cc=m.douglas.mcilroy@dartmouth.edu \
--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).