From: akosela@andykosela.com (Andy Kosela)
Subject: [TUHS] What UNIX Artifacts Are Still Missing?
Date: Wed, 6 Dec 2017 23:40:56 -0600 [thread overview]
Message-ID: <CALMnNGiVsL_gMA18OZNK8YXA-jjs=+vAKw0mO8tprvf267eOGQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1712070923590.35694@aneurin.horsfall.org>
On Wednesday, December 6, 2017, Dave Horsfall <dave at horsfall.org> wrote:
> On Wed, 6 Dec 2017, Paul Ruizendaal wrote:
>
> That is a good point: early Xenix is still missing. It would make an
>> excellent public relations move for Microsoft if they would make early
>> Xenix available to celebrate 50 years of Unix.
>>
>
> Call me a cynical old bastard (which I am), but I can't see M$ raising a
> flag for Unix... Wasn't it Billy Gates who reportedly said that any PC
> running Linux is one not running Windoze, and did his best to discredit it?
>
> I still have horrible memories of porting Unify (an early RDBMS) to Xenix,
> and getting tangled up in the poxy small/large memory models on the
> equally-poxy 286 (no, not the 386).
>
>
I can understand no love for Xenix on this list, but actually M$ is part of
the UNIX history and was actually quite successful with Xenix[1]. In the
late 80s there were more computers running M$ Xenix than all other versions
of UNIX combined.
Some good history here:
http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml
--Andy
[1]
https://books.google.com/books?id=UE1HODexHKoC&pg=PA44#v=onepage&q&f=false
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171206/42969fb0/attachment.html>
next prev parent reply other threads:[~2017-12-07 5:40 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
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 [this message]
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='CALMnNGiVsL_gMA18OZNK8YXA-jjs=+vAKw0mO8tprvf267eOGQ@mail.gmail.com' \
--to=akosela@andykosela.com \
/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).