From: Rob Landley <rob@landley.net>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Jamie Lokier <jamie@shareable.org>,
"Ihar 'Philips' Filipau" <filia@softhome.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.
Date: Thu, 21 Aug 2003 21:58:23 -0400 [thread overview]
Message-ID: <200308212158.23678.rob@landley.net> (raw)
In-Reply-To: <3F4568D2.5080705@nortelnetworks.com>
On Thursday 21 August 2003 20:50, Chris Friesen wrote:
> > So I take it one of the goals of cleaned and pressed kernel-ABI headers
> > for 2.7 would be to have them distributable under LGPL? (Just trying to
> > be explicit, here...)
>
> I thought that this case (including kernel headers) was the whole point
> of the exemption in the COPYING file. Am I missing something?
It's legal contortionism, and it might leave some dangling technicalities.
The Linux kernel is licensed under the GPL. Linus's statements are just his
interpretation of what consitutes a derived work, and hence the scope of the
GPL. (So it's PROBABLY not an incompatable additional license clause thingy
that makes it "not GPL" for the purpose of linking GPL code to it.) But lots
of other people's code has been combined with Linus's, and they might
consider their code under the straight GPL (sans adendum).
Whether Linus's word is final on this matter is up to a judge. (It PROBABLY
is, since he's the project maintainer and the project license is "GPL plus
this memo about derived work interpretation", and anybody who contributes to
the project without knowing that is Not Paying Attention. Certainly all the
contributors have had warning about this when submitting code to Linux for
more than the past 3 years (which might be the statute of limitations,
depending on who you ask), so for code THEY contributed we should be okay.
The corner case is when somebody other than the code's author lifts code from
other GPL projects and puts it in Linux, but then again that's not amazingly
common either since how many other GPL operating system kernels do you see
out there? (And even then, if Linus's guide is an interpretation about the
scope of derived works rather than a license adendum, then it may not
actually be incompatable with the GPL, but who knows...)
All this is hair splitting, but we've all seen what happens when companies
with more lawyers than sense decide they have no profitable business model to
live for, buy a bunch of liquor, and pledge to take their friends out with
them. Nobody as ornery and stupid as SCO has sued over this fine point yet
to give us a straw man to shoot down, so the issue hasn't been resolved in
court yet. I can't see SCO suing to EXTEND the reach of the GPL right now,
so it's not an immediate pressing issue. And if it did, Linus would be the
main wronged party, who A) doesn't WANT damages, B) would be thrilled to
settle out of court for a gift certificate to Wendy's or something, C) could
obviously whip out a kernel-ABI package in an afternoon to remedy it, D)
would probably rip out the contributions of any author who made a major stink
about never taking even a typo correction patch from them again.
But it would be nice to clean it up beforehand anyway. The LGPL exists for a
reason...
(And predicting SCO's actions based on what's good for their continued
financial or legal health would not have been a particularly accurate
prognostication technique over the past six months...)
This whole issue is about on the level of "do not remove this mattress tag",
by the way. That's why people have been so complacent about it so far...
> Chris
Rob
P.S. Even if I was a lawyer, which I'm not, you'd have to be insane to take
legal advice from a stranger on the internet who you hadn't even paid a
retainer to. If you really care, go find a lawyer who understands
intellectual property as applied to software, and the GPL specifically, and
ask them. (This may take some time. I can think of four in the whole of
north america, and two of them have asked ME for a second opinion...)
P.P.S. Don't even ASK about the "restricted to V2, not later versions" thing.
I'm just not going there right now...
P.P.P.S. If you're REALLY bored, might I suggest getting a copy of "Legal
Battles that Shaped the Computer Industry". (It's dry reading, but where
else are you going to find out about a lawsuit between AT&T and Franklin Ace
that probably helped lead to both AT&T's commercialization of Unix and the
formation of the Free Software Foundation? Of course you have to supply half
the context yourself...) It's reviewed here:
http://www.hmdc.harvard.edu/micah_altman/papers/battles.pdf
next prev parent reply other threads:[~2003-08-22 1:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lRjc.6o4.3@gated-at.bofh.it>
[not found] ` <lRjg.6o4.15@gated-at.bofh.it>
[not found] ` <lWLS.39x.5@gated-at.bofh.it>
[not found] ` <lWLZ.39x.29@gated-at.bofh.it>
2003-08-18 18:54 ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Ihar 'Philips' Filipau
2003-08-18 19:04 ` Jeff Garzik
2003-08-19 12:32 ` Rob Landley
2003-08-19 17:26 ` Jeff Garzik
2003-08-19 21:38 ` Will uclibc be supported in 2.6? (was Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.) Rob Landley
2003-08-19 21:47 ` Jeff Garzik
2003-08-20 1:42 ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Erik Andersen
2003-08-20 23:48 ` Jamie Lokier
2003-08-21 0:02 ` Jeff Garzik
2003-08-22 0:32 ` Rob Landley
2003-08-22 0:50 ` Chris Friesen
2003-08-22 1:58 ` Rob Landley [this message]
2003-08-22 0:54 ` Jeff Garzik
2003-08-18 20:40 ` Sam Ravnborg
2003-08-18 12:36 Andries.Brouwer
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 12:19 Andries.Brouwer
2003-08-18 12:24 ` Christoph Hellwig
2003-08-18 18:08 ` Sam Ravnborg
2003-08-18 18:14 ` Jeff Garzik
2003-08-18 15:21 ` Linus Torvalds
2003-08-18 15:32 ` Jeff Garzik
2003-08-18 16:13 ` Patrick Mansfield
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=200308212158.23678.rob@landley.net \
--to=rob@landley.net \
--cc=cfriesen@nortelnetworks.com \
--cc=filia@softhome.net \
--cc=jamie@shareable.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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