The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 18:51:24 -0500	[thread overview]
Message-ID: <CAC20D2MW_0w_pByDrwU9aTYsmFdztnNC4E2Ea11tEnUMeJEpKA@mail.gmail.com> (raw)
In-Reply-To: <20170222231320.GM9439@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

On Wed, Feb 22, 2017 at 6:13 PM, Larry McVoy <lm at mcvoy.com> wrote:

> I just don't think they rewrote as much as they claimed
> ​ ​
> they did,
>
​​Maybe...


> it was not a total rewrite, there was more than enough still
> there that AT&T could have prevailed with a copyright case.
>
​I agreed today and I certainly thought so at the time it all went down ( I
was scared UNIX for the PC was going to disappear).
But we all never know what would have happened if AT&T had only taken on
copyright.   Greed took over and AT&T tried to get everything.  Their
exec's make a choice and they did keep the goose, but they killed it too.

Which brings us back to the original question Noel asked:  W*hy Linux and
not another UNIX flavor?*

While I learned a great deal in the thread and I think I personally have a
better understanding of why different people acted in different ways, the
the answer is to me in unchanged and stays a simple two parts:

   1. I think most if not all of us agree it was the WINTEL economics that
   made the PC/386 the HW platform "win", and
   2. I truly believe that it was the the AT&T/BSDi legal entanglement that
   was the key item in Linux end up in the lead

All of the other contributed things people talked about were good reasons
for some specific choice by different folk, but the common driver behind it
all / the real root of it was the court case.  It did not matter which side
you were on and who you thought was right/wrong, held the moral ground
etc... if that case had not been there, I really don't think Linux would
have gotten the momentum and had the ability to last.

Others may not think so, but too me, that is sad, it was opportunity lost.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170222/b16dc572/attachment-0001.html>


  reply	other threads:[~2017-02-22 23:51 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
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 [this message]
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=CAC20D2MW_0w_pByDrwU9aTYsmFdztnNC4E2Ea11tEnUMeJEpKA@mail.gmail.com \
    --to=clemc@ccc.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).