From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] GNU vs BSD before the lawsuit and before Linux
Date: Sat, 18 Mar 2017 13:23:23 -0600 [thread overview]
Message-ID: <CANCZdfoYMBE7egm4_D-uw0zg9smPKLq9taTdNfAxQAeO_=vNxA@mail.gmail.com> (raw)
In-Reply-To: <1489859133.340763.915600080.44C5EE3F@webmail.messagingengine.com>
On Sat, Mar 18, 2017 at 11:45 AM, Random832 <random832 at fastmail.com> wrote:
> There's a lot of code in a handful of not-part-of-GNU-proper core
> utility packages used in Linux distributions - bsdmainutils, bsdgames,
> bsdutils, and util-linux [only the last of which has the GPL] - which
> come from some BSD or another and mostly have intact UCB copyright
> statements and licenses at the top. If any of these are improperly
> attributed, it's likely that UCB is to blame.
Anything in 4.4-lite was specifically blessed by USL as non-infringing
as part of the settlement of that suit...
But the bsd* packages aren't what's being talked about here. Those
generally came about later as these BSD programs ported to Linux and
resistance to non-gpl'd code in distributions waned.
Warner
next prev parent reply other threads:[~2017-03-18 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 13:07 Doug McIlroy
2017-03-18 13:27 ` Nick Downing
2017-03-18 15:19 ` Warner Losh
2017-03-18 16:25 ` Doug McIlroy
2017-03-18 17:45 ` Random832
2017-03-18 19:23 ` Warner Losh [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-18 12:45 Doug McIlroy
2017-03-14 14:43 [TUHS] System Economics (was is Linux "officially branded UNIX") Clem Cole
2017-03-14 15:38 ` Larry McVoy
2017-03-14 15:51 ` Arthur Krewat
2017-03-14 15:57 ` Michael Kjörling
2017-03-14 16:20 ` Arthur Krewat
2017-03-14 18:41 ` Warner Losh
2017-03-17 18:16 ` [TUHS] GNU vs BSD before the lawsuit and before Linux Tony Finch
2017-03-17 18:52 ` Jeremy C. Reed
2017-03-19 7:18 ` arnold
2017-03-19 9:05 ` Wesley Parish
2017-03-19 18:37 ` Warner Losh
2017-03-17 19:54 ` 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='CANCZdfoYMBE7egm4_D-uw0zg9smPKLq9taTdNfAxQAeO_=vNxA@mail.gmail.com' \
--to=imp@bsdimp.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).