The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [pups] Interesting PDP/Xenix History
Date: Thu, 28 Mar 2002 11:58:08 +1030	[thread overview]
Message-ID: <20020328115808.C6079@wantadilla.lemis.com> (raw)
In-Reply-To: <1017271451.3ca2549b6692c@w3.fwn.rug.nl>

On Thursday, 28 March 2002 at  0:24:11 +0100, Lars Buitinck wrote:
> I'm getting really confused with all these companies.  If I understand
> correctly...
>
> AT&T/Western Electric sold UNIX rights to Microsoft.
> Microsoft had HCR develop XENIX from V7.
> SCO licensed XENIX from Microsoft.
> SCO then subsubsublicensed XENIX to various vendors.
>
> Please correct me.  I must be wrong.
>
> (What happened to our MERT discussion anyway? :-)
>
> Long & winding PS.: I read this really cute book about Linux at my local
> library some time ago.  It discussed UNIX, Linux, their relation, and the
> current state of affairs when it was written -- in 1994.  The book
> started out with an etymology of XENIX, which would have been derived
> from Dutch "'k Zie niks," meaning "I don't see a thing" -- the first
> thing Dutch users uttered when XENIX booted.

Note that in English, the X is usually pronounced like an S ("zie
niks").  Siemens made a pun on this with their Sinix product; "Sinix"
in German is pronounced the same way as "XENIX" in English :-)

> Last year, I talked to a fellow member of the HCC (Hobby Computer
> Club) UNIX gg (gebruikersgroep, user group) who remembered his worst
> experience with UNIX -- having to use XENIX.  He was still shocked
> by its Microsoftian performance.

I've used XENIX/386 in the early 90s.  The development tools were
terrible, but I found somebody who had ported the GNU tools to XENIX
(doing it yourself would rob you of your sanity).  After that, it
wasn't too bad, but it was a pretty limited system.  I ended up
building a cross-build environment on UnixWare.

Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers



  parent reply	other threads:[~2002-03-28  1:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25  2:39 Frank Wortner
2002-03-25 10:15 ` Johnny Billquist
2002-03-25 15:18   ` Frank Wortner
2002-03-26  7:41     ` Michael Davidson
2002-03-26 18:06       ` Frank Wortner
2002-03-25 10:38 ` Robert Tillyard
2002-03-26 23:41   ` Warren Toomey
2002-03-27  0:47     ` Michael Davidson
2002-03-27 23:24       ` Lars Buitinck
2002-03-27 23:58         ` Michael Davidson
2002-03-29 21:36           ` Lars Buitinck
2002-03-28  1:28         ` Greg 'groggy' Lehey [this message]
2002-03-28  2:33           ` Peter Jeremy
2002-03-30 11:03           ` Lars Buitinck
2002-03-30 23:38             ` Greg 'groggy' Lehey
  -- strict thread matches above, loose matches on Subject: below --
2002-04-03  9:52 asmodai
2002-04-03  9:49 asmodai
2002-04-03  9:14 Fred N. van Kempen
2002-04-03  9:45 ` quapla
2002-04-03 16:25 ` Michael Davidson
2002-04-02 22:38 asmodai
2002-04-03  3:31 ` Frank Wortner
2002-03-23 19:43 Martin Crehan
2002-03-24  4:26 ` Warren Toomey

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=20020328115808.C6079@wantadilla.lemis.com \
    --to=grog@lemis.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).