The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] SunOS vs Linux
Date: Fri, 06 Jan 2017 02:32:12 +0000	[thread overview]
Message-ID: <CAP6exYK9=t-VSapvxHKvJxLSbOBORM3i6wNun5U+Csmxq3OHJg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PouGXLTScyzSu-yi+NU1JthGwTFeCG5e86C9m=8KeAiQ@mail.gmail.com>

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

On Wed, Jan 4, 2017 at 9:09 AM Clem Cole <clemc at ccc.com> wrote:



​FWIW:  I disagree​.  For details look at my discussion of  rewriting Linux
in RUST
<https://www.quora.com/Would-it-be-possible-advantageous-to-rewrite-the-Linux-kernel-in-Rust-when-the-language-is-stable>
on quora.   But a quick point is this .... Linux original took off (and was
successful) not because of GPL, but in spite of it and later the GPL would
help it.



Not disagreeing with you all, but: I guess it depends on where you were. In
1994-6 I worked with a friend at IBM Watson on getting netbsd going on
powerpc. Linux killed that effort. It turned out that the BSD license would
allow different parts of IBM to hold back code from other parts of IBM and
still ship product. The GPL made such behavior much, much harder. The
engineers inside IBM preferred sharing code, and the GPL made that
possible. At least that's how it was explained to me.

This also proved true for some Agencies in the US Gov't as early as 1993.
See this:
https://github.com/torvalds/linux/blob/master/drivers/net/LICENSE.SRC. I
was there for the internal discussion which began in 1992.

Weirdly enough, though, sometimes lawyers prefer the GPL. On our third
foray into getting a sane license for Plan 9 in 2013, it turned out Lucent
legal preferred GPL to BSD. Go figure. I don't understand lawyers most
times.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170106/ccaa7b41/attachment.html>


  reply	other threads:[~2017-01-06  2:32 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 [this message]
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
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='CAP6exYK9=t-VSapvxHKvJxLSbOBORM3i6wNun5U+Csmxq3OHJg@mail.gmail.com' \
    --to=rminnich@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).