From: Ed Bradford <egbegb2@gmail.com>
To: Charles H Sauer <sauer@technologists.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference
Date: Tue, 6 Apr 2021 21:30:28 -0500 [thread overview]
Message-ID: <CAHTagfG9wVL97Oc5KmJXw-Ka9ciJV3RRUXDrTbBsgcRFC1VXfQ@mail.gmail.com> (raw)
In-Reply-To: <04e60d98-22e3-acb5-686f-93af1f7e2825@technologists.com>
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
What year was this, Charles?
Ed
On Tue, Apr 6, 2021 at 12:33 PM Charles H Sauer <sauer@technologists.com>
wrote:
> For much of my last few years at IBM, my uucp machine, ibmchs, was an AT
> running Xenix, probably that version of Xenix.
>
> On 4/6/2021 12:09 PM, Clem Cole wrote:
> > Doug -- IIRC IBM private-labeled a Microsoft put out a version of Xenix,
> > although I think it required an PC/AT (286)
> > ᐧ
> >
> > 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
> >
>
> --
> voice: +1.512.784.7526 e-mail: sauer@technologists.com
> fax: +1.512.346.5240 Web: https://technologists.com/sauer/
> Facebook/Google/Skype/Twitter
> <https://technologists.com/sauer/Facebook/Google/Skype/Twitter>:
> CharlesHSauer
>
--
Advice is judged by results, not by intentions.
Cicero
[-- Attachment #2: Type: text/html, Size: 2950 bytes --]
next prev parent reply other threads:[~2021-04-07 2:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2021-04-07 0:59 Jason Stevens
2021-04-10 18:12 Paul Ruizendaal via TUHS
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=CAHTagfG9wVL97Oc5KmJXw-Ka9ciJV3RRUXDrTbBsgcRFC1VXfQ@mail.gmail.com \
--to=egbegb2@gmail.com \
--cc=sauer@technologists.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).