From: imp@bsdimp.com (M. Warner Losh)
Subject: [TUHS] Lexical comparator, was Re: the battle against SCO
Date: Mon, 15 Sep 2003 21:10:11 -0600 (MDT) [thread overview]
Message-ID: <20030915.211011.51703000.imp@bsdimp.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0309152131290.24213@zen.canint.timetraveller.org>
In message: <Pine.LNX.4.56.0309152131290.24213 at zen.canint.timetraveller.org>
Robert Brockway <robert at timetraveller.org> writes:
: a) Code which is licenced in a manner incompatible with the GPL
: b) Code that the copyright holder did not authorise going into the kernel.
There's a lot of code that originated in the BSD world that had its
copyrights shorn off, a GPL splatted on and the mass hacking began.
Many of these are no longer recognizable from there original form, and
aren't a problem. Some have much more in common with the original.
Linux is vulnerable to the original author having a shit fit if they
ever find out. Most of the open source authors are amused when this
happens, so the odds are low a big deal would be made of it. This
practice was wide-spread in the early 1990s, although things have
improved a lot.
However, without something like CVS and the legal assignment of
copyright (or formal acknowledgement of licensing under the GPL, which
is harder to defend), this will always be a problem with Linux.
The BSD projects are a little tigher about this, but still would be
vulnerable.
Warner
next prev parent reply other threads:[~2003-09-16 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 0:02 Norman Wilson
2003-09-16 1:35 ` Robert Brockway
2003-09-16 3:10 ` M. Warner Losh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 2:11 Norman Wilson
2003-09-15 20:39 [TUHS] Fwd: Helping in " Norman Wilson
2003-09-15 22:48 ` [TUHS] Lexical comparator, was " Warren Toomey
2003-09-16 0:46 ` Rhys Weatherley
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=20030915.211011.51703000.imp@bsdimp.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).