The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] SunOS vs Linux
Date: Mon, 9 Jan 2017 12:40:47 -0500	[thread overview]
Message-ID: <CAEoi9W432SVDTCTjKJfR6PBkYKpXs+fj2Qd7yGmDBvznd1Xyfw@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYL3G08Ef_35jkD7V9inwgW4nU0zO-H5dHUCzQJJB12+Ng@mail.gmail.com>

On Mon, Jan 9, 2017 at 11:08 AM, ron minnich <rminnich at gmail.com> wrote:

> At the same time, I think some sort of GPL'ed kernel was inevitable for
> any number of reasons.
>
> Also, I worked closely with one of the principals in Linux back then (i.e.
> 1991) and his experience was that the linux community was way more open to
> his contributions than the bsd community. Not surprising, linux was pretty
> much a clean sheet. I expect that was a factor as well.
>

I'll second this. Larry mentioned earlier the USENIX "in-crowd" and I think
that was a real thing (USENET cabal, anyone?). I was near a major American
university at the time, kind of a student, and I couldn't easily get access
to Unix source code (nor could any of the undergrad or grad students I
knew). As I recall, no one had copies of the old stuff anymore (32/V and
prior) and access to BSD source code was tightly controlled; we had an
academic site license for SunOS source, but it was strictly on a
"need-to-know" basis. You had to be part of the local "in-crowd" to get
access to that code, and students weren't members of the "in-crowd." It
wasn't particularly easy to build up the sufficient credibility to get into
the club without access to source either, and they certainly weren't
handing it out to everyone who asked. Further, my sense was that system
administrators in big institutions were often hawks about things like that.
There could be real academic consequences for trying to buck the system in
this area, particularly for undergrads (or in my case, high school students
taking courses).

The ever-accurate Wikipedia says that 386BSD wasn't available until 1992
(and then not really usable until July of that year). But Torvalds had
already announced his Linux project (by which point he had a running kernel
and had ported a significant number of programs over) in August of 1991 and
put it on an FTP server by September; nearly a full year before a usable
version of 386BSD was available.

The thing I wonder is why Linux didn't die off due to lack of networking
once 386BSD came onto the scene: Linux didn't get TCP/IP until September of
1992 and then it was under heavy development until December, by which time
386BSD 0.1 was generally available (and would of course already have had
networking). I suspect by that point two factors were at play: a) Linux had
gathered significant momentum and b) USL v BSDi cause people to shy away
from the BSD source base and embrace Linux as an unencumbered alternative.

By '93ish, when NetBSD and FreeBSD were both real, there wouldn't have been
a need for Linux, but by that time, it had had two years of exciting
activity for a number of people: it's unlikely anyone just walked away from
it because a technically better alternative came along.

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170109/e3743284/attachment-0001.html>


  reply	other threads:[~2017-01-09 17:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 17:08 Clem Cole
2017-01-06  2:32 ` ron minnich
2017-01-06  3:56 ` Dan Cross
2017-01-06  3:58   ` Larry McVoy
2017-01-06 14:27   ` Clem Cole
2017-01-07  2:58     ` Greg 'groggy' Lehey
2017-01-07  3:09       ` Warner Losh
2017-01-07  3:13         ` Larry McVoy
2017-01-07  3:12       ` Larry McVoy
2017-01-08 16:28   ` Angus Robinson
2017-01-08 18:02     ` Kay Parker   
2017-01-08 20:51       ` Clem cole
2017-01-09  3:00         ` Greg 'groggy' Lehey
2017-01-09  6:32           ` Arno Griffioen
2017-01-09  8:27             ` Wesley Parish
2017-01-09 13:07             ` Joerg Schilling
2017-01-09 15:57             ` Clem Cole
2017-01-09 16:08               ` ron minnich
2017-01-09 17:40                 ` Dan Cross [this message]
2017-01-09 17:32               ` Rico Pajarola
2017-01-10 11:02                 ` Joerg Schilling
2017-01-08 22:52     ` Wesley Parish
2017-01-09 19:45   ` Jacob Goense
2017-01-08  6:10 Kirk McKusick
2017-01-08 14:52 ` Ron Natalie

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=CAEoi9W432SVDTCTjKJfR6PBkYKpXs+fj2Qd7yGmDBvznd1Xyfw@mail.gmail.com \
    --to=crossd@gmail.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).