The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: akosela@andykosela.com (Andy Kosela)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Tue, 6 Feb 2018 18:22:28 -0600	[thread overview]
Message-ID: <CALMnNGiN_Z6mwf0kjJz2Muxw8yWtidpQOB+_2jZad0vHNhc0nQ@mail.gmail.com> (raw)
In-Reply-To: <20180206230254.GB1977@thunk.org>

On Tuesday, February 6, 2018, Theodore Ts'o <tytso at mit.edu> wrote:

> On Tue, Feb 06, 2018 at 02:13:51PM -0800, Dan Stromberg wrote:
> > 2) I think the main reason BSD nearly died, was the AT&T lawsuit.  At
> > the time, Linux appeared to be a safer bet legally.
>
> At the time of the AT&T lawsuit, most of the people who would be
> interested in using a Un*x-like system on their personal x86 systems
> probably wouldn't have been worried about their own personal legal
> liability.  The decision of corporations to use Linux was well *after*
> the AT&T lawsuit was resolved.
>
>
Exactly.  I always stress that the AT&T lawsuit's negative impact on
adoption of Open Source *BSDs is exaggerated.  Remember that back in the
early 90s both Linux and Net/FreeBSD were just hobbyist systems...  We were
all doing it as a hobby for fun.  No one was aware that this is going to
catch on in the enterprise...

I think that if somebody was already exposed to BSD code in the 80s it was
more natural for him to adopt open source *BSD.  Otherwise he went with
Linux.  Initially I think it was a little bit smaller and simpler too.

Until the decision of the really big corporate players like Oracle and IBM
to support Linux in the late 90s, both systems went head-to-head, and one
could even argue that *BSDs had a technical edge over Linux.

It all changed after year 2g when it became apparent that Linux is slowly
winning the battle for "hearts and minds".

We should be happy that hobbyist Open Source Unix systems have been so
widely adopted at all though; otherwise we would all be living in the NT
hell.

--Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180206/ca1f7eb5/attachment.html>


  reply	other threads:[~2018-02-07  0:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 22:13 Dan Stromberg
2018-02-06 22:38 ` Clem Cole
2018-02-06 22:44 ` Warner Losh
2018-02-06 22:59   ` Pete Wright
2018-02-06 22:59 ` Derek Fawcus
2018-02-07  1:14   ` Dave Horsfall
2018-02-06 23:02 ` Theodore Ts'o
2018-02-07  0:22   ` Andy Kosela [this message]
2018-02-07  1:02     ` Robert Brockway
2018-02-07  3:47       ` George Michaelson
2018-02-07  1:29   ` Clem Cole
2018-02-07 15:13     ` Theodore Ts'o
2018-02-07 16:59       ` Jon Forrest
2018-02-07 17:27       ` Clem Cole
2018-02-07 19:21         ` Dan Cross
2018-02-07 21:24           ` Clem Cole
2018-02-07 19:31         ` Nemo
2018-02-07 19:49         ` Theodore Ts'o
2018-02-07 19:53           ` Dan Cross
2018-02-07 20:26             ` Theodore Ts'o
2018-02-07 21:06               ` Clem Cole
2018-02-07 21:31               ` Clem Cole
2018-02-07 17:52       ` Tom Ivar Helbekkmo
2018-02-07  8:04   ` Tom Ivar Helbekkmo
2018-02-07  8:51   ` Arrigo Triulzi
2018-02-07  8:27 ` Wesley Parish
2018-02-07  8:39   ` emanuel stiebler
2018-02-07 10:44     ` Arrigo Triulzi
2018-02-07 13:14   ` Chet Ramey
2018-02-07 14:42   ` Nemo
2018-02-09  2:53     ` Wesley Parish
2018-02-11 20:22       ` Derek Fawcus
2018-02-12  0:31         ` Robert Brockway

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=CALMnNGiN_Z6mwf0kjJz2Muxw8yWtidpQOB+_2jZad0vHNhc0nQ@mail.gmail.com \
    --to=akosela@andykosela.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).