The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 08:11:14 -0800	[thread overview]
Message-ID: <20170222161114.GT9439@mcvoy.com> (raw)
In-Reply-To: <CAC20D2M=ucsTTXx7P8c+P7vd17fDAmEhgR9Qy_q-DHtjVoXxVA@mail.gmail.com>

On Wed, Feb 22, 2017 at 10:36:08AM -0500, Clem Cole wrote:
> I think your counter point is that while I believe folks like yourselves or
> Linus could have gotten BSD UNIX if you had tried to find it it was
> available and folks like Keith and Bill were trying to get it out the door,
> but  have suggest that you don't think so.   You think the walls were too
> high, the access was only for the "chosen few" and a difference was the
> Linux really was available to what Larry referred to as the great unwashed.

The way it felt to me at the time was yes, you could, maybe, get access 
but it was proprietary source code.  If you put it up for FTP you were
going to get sued or something.  It was not freely available.  

You keep saying that 386BSD was up for FTP as a poorly kept secret. 
Why was it secret?  Because it wasn't legal to get it.

A lot of us were pretty sick of that legal bullshit.  Linux didn't 
have that problem.

> To that I say, fair enough.   You could be right, I do hope you are not.  I
> don't think that was the intention/theory - but in practice, it seems
> different.

I think most hackers wanted it to be free, though even there it was
sort of hit and miss.  The BSDi guys thought they saw a market 
opportunity so they weren't so excited about free.


  reply	other threads:[~2017-02-22 16:11 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 [this message]
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
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=20170222161114.GT9439@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).