The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 07:54:25 -0800	[thread overview]
Message-ID: <20180104155425.GC8574@mcvoy.com> (raw)
In-Reply-To: <CAC20D2OZ4ZvbJSfzZxBWLanfzZgg3XBTiMNVzHK_0yV9tEbmvg@mail.gmail.com>

On Thu, Jan 04, 2018 at 09:03:09AM -0500, Clem Cole wrote:
> On Thu, Jan 4, 2018 at 6:53 AM, Harald Arnesen <harald at skogtun.org> wrote:
> > Didn't Linus say that if there had been an affordable BSD available at
> > the time, he wouldn't have started the Linux project?
> 
> ???You need to add >>and that he knew about and had access<<.
> 
> The truth is there was and it had networking and X windows already.  Bill
> Jolitz had completed the original 386 BSD port (and actually started to
> publish about it in DDJ).  The 386BSD sources were available to all BSD
> licensees 

But that's not what Linus (or anyone) wanted.  They wanted it under some
sort of clearly open source license.  None of us knew what the penalty
was for violating the license, we just knew that at one end was us, with
no means to fight a court battle, and at the other end were big entities
that viewed court battles as a cost of doing business.

I didn't know at the time that Bell Labs had to license their stuff as
part of the monopoly deal, that was something I learned here.  So I, and
I suspect lots of other people, most people, the best people :) all 
thought that our access to the source was at the whim of AT&T, it could
be taken away at any time.

That wasn't the rosy "everybody who wanted it could get it" world that
Clem lived in.  Clem was in a special club, heck, he was president of
Usenix at one point, that's sort of the epitome of being in the club.
Not being in the club was a far less rosy place and it made perfect
sense for Linus to start Linux.  I'd argue that if he hadn't, someone
else would have.

Stupid lawsuit means we're mostly running a Unix-clone, not actual Unix.

--lm


  reply	other threads:[~2018-01-04 15:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole
2018-01-03 17:28   ` Bakul Shah
2018-01-03 17:46     ` ron minnich
2018-01-03 18:28       ` Bakul Shah
2018-01-03 18:27     ` Clem Cole
2018-01-03 18:39       ` Forrest, Jon
2018-01-03 18:50         ` ron minnich
2018-01-03 19:56       ` Paul Winalski
2018-01-03 20:24       ` Bakul Shah
2018-01-03 23:40       ` Theodore Ts'o
2018-01-04  0:51         ` Larry McVoy
2018-01-04  2:13           ` Bakul Shah
2018-01-04  2:26             ` Larry McVoy
2018-01-04  3:31               ` Bakul Shah
2018-01-04  2:09         ` Arthur Krewat
2018-01-04  3:21           ` Dan Cross
2018-01-04 17:42             ` Arthur Krewat
2018-01-04 11:53         ` Harald Arnesen
2018-01-04 14:03           ` Clem Cole
2018-01-04 15:54             ` Larry McVoy [this message]
2018-01-04 16:45             ` Theodore Ts'o
2018-01-04 17:10               ` Andy Kosela
2018-01-04 17:17               ` Larry McVoy
2018-01-04 18:29                 ` Bakul Shah
2018-01-04 18:50                   ` Larry McVoy
2018-01-04 20:52                     ` Warner Losh
2018-01-04 20:56                       ` Bakul Shah
2018-01-04 20:56                   ` Theodore Ts'o
2018-01-04 21:16                     ` Warner Losh
2018-01-04 22:55                       ` Andy Kosela
2018-01-05 14:27                         ` Clem Cole
2018-01-04 21:17                     ` Bakul Shah
2018-01-04 17:20               ` Tom Ivar Helbekkmo
2018-01-04 17:28                 ` Warner Losh
2018-01-03 17:07 ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03  7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22   ` Random832

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=20180104155425.GC8574@mcvoy.com \
    --to=lm@mcvoy.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).