The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 13:18:30 -0700	[thread overview]
Message-ID: <201702222018.v1MKIUKO030787@freefriends.org> (raw)
In-Reply-To: <CAC20D2MK=hrhYP=AQn4PKZMXt_KLPCZu4R+D+FOuXLLPssiecw@mail.gmail.com>

I'll add my two cents. My experience was that source was hard
to get to. My undergrad school had IS/1 - v6 on a PDP-11 - and source
was definitely not available to us seniors. One person who actually
worked for the computer center did have access. This was 1980-1981.

In grad school at Georgia Tech, there was no access to students to
the vax, and even after I went to work there I had to sign something
first before seeing source.

Later I was a sysadmin at Emory U and so I had source but it wasn't
widely open.  We ran Mt. Xinu 4.3 + BSD on vaxen, so there source was
necessary.

By the mid-80s, even if you had AT&T and BSD licenses, it didn't help,
as there were lots of vendors NOT giving out source (Sun, Pyramid, DEC,
Gould, DG, you name it).  This was pretty much OK; things worked
fairly well and you didn't need to fix drivers and recompile the
kernel and so on on those machines.

Vaxen were aging, BSD didn't support 8500s, and so if you wanted BSD
you pretty much had to go to one of the vendors offering it. Sun
was probably the most popular.

At a startup company we ran ESIX, SVR3 (and later SVR4) based on 386s
for our product alongside a few Sun boxen.  It was a good Unix, but
again no source, but no real need for it either. This was ~ 1990-1991.

W.R.T. personal machines, I shelled out $$ to buy an AT&T 3B1 (68010
based, System V kernel, SVR2 user land + vi) which I used happily
for many years. Later I bought a Sun IPC. (More $$.) Also used happily
for quite a while.

I only got into Intel land for myself when I moved to Israel, buying a laptop
and running Linux on it.  I had played some with Linux on Sparc and
was fairly impressed with it. This was circa 1997.

Linux generally "just works" out of the box on PC hardware, and
with Debian/Ubuntu, software updates are a breeze.  I spend almost no
time having to be a sysadmin for myself, which is wonderful.

I mostly watched the whole AT&T/BSD lawsuit stuff from the side. At
one USENIX I remember talking to Keith Bostic about it, and understanding
that it was trade secret, but I asked him "Given the book by Maurice
Bach on how UNIX works, how can they still think it's trade secret?"
He just sorta nodded and said "yep" or something equivalent.

But yes, the sense while it was going on was definitely that BSD
was risky and problematic. And that the whole lawsuit thing was
really, REALLY stupid.

Sigh.

Arnold


  reply	other threads:[~2017-02-22 20:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  3:38 Clem Cole
2017-02-22  4:28 ` Dan Cross
2017-02-22 15:36   ` Clem Cole
2017-02-22 16:11     ` Larry McVoy
2017-02-22 17:00       ` Clem Cole
2017-02-22 17:06         ` Chet Ramey
2017-02-22 18:24         ` Larry McVoy
2017-02-22 19:35           ` Clem Cole
2017-02-22 20:18             ` arnold [this message]
2017-02-22 22:11               ` Clem Cole
2017-02-22 21:34             ` Larry McVoy
2017-02-22 22:56               ` Clem Cole
2017-02-22 23:13                 ` Larry McVoy
2017-02-22 23:51                   ` Clem Cole
2017-02-22 23:51           ` Paul Ruizendaal
2017-02-23 19:15             ` Clem Cole
2017-02-23 20:31               ` Random832
2017-02-23 22:48                 ` Joerg Schilling
2017-02-24  2:07                   ` Jason Stevens
2017-02-23 23:06                 ` Wesley Parish
2017-02-22 17:41       ` Arthur Krewat
2017-02-22 21:00     ` Michael Kerpan
2017-02-22 22:03       ` Arno Griffioen
2017-02-22 22:51         ` Larry McVoy
2017-02-22 23:29         ` Clem Cole
2017-02-23  4:53           ` Gregg Levine
2017-02-22 22:18       ` Clem Cole
2017-02-24  3:53     ` Dan Cross
2017-02-22  5:56 ` Steve Nickolas
2017-02-24  5:31   ` John Labovitz

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=201702222018.v1MKIUKO030787@freefriends.org \
    --to=arnold@skeeve.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).