linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Jun 2007 08:58:13 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Woodhouse <dwmw2@...radead.org>
cc:	Daniel Hazelton <dhazelton@...er.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Alexandre Oliva <aoliva@...hat.com>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Fri, 15 Jun 2007, David Woodhouse wrote:

> On Fri, 2007-06-15 at 04:58 -0400, Daniel Hazelton wrote:
> > >
> > > But when you distribute the same module as part of a whole which is a
> > > work based on the kernel, the distribution of the whole must be on the
> > > terms of GPL, whose permissions for other licensees extend to the entire
> > > whole, and thus to each and every part regardless of who wrote it.
> > 
> > -ELOGIC
> 
> What's logic got to do with it? It was fairly much a direct quote from
> the licence. You have _read_ the licence, haven't you?

Actually, I suspect Daniel has read it, and is probably referring to 
another facet of the license: distribution of two things together does 
*not* imply that those two things have to both be GPLv2's.

The GPLv2 explicitly mentions "mere aggregation". Strictly speaking, it 
doesn't even *have* to mention it, since it does mention in other places 
that it only covers "derived work", and "derivation" has nothing to do 
with "distributing two things together". But it's a good clarification.

So you guys are *both* right, for different cases!

The issue is simply what you mean by "part of the whole"? If you mean 
"part of the whole kernel distribution", then yes, the kernel is one work, 
and it is, in its entirety, under the GPLv2. But if the "part of the 
whole" is about something like a DVD with the whole being a collection of 
"mere aggregation", the licenses do not necessarily meld together.

Let's say that you're a Linux vendor, and you distribute a DVD with both 
the Linux kernel binary (and all the normal modules that go with it, that 
obviously are "part of the whole kernel") *and* say the NVidia proprietary 
kernel module.

Is that the *only* way to read things? No. It's a matter of 
interpretation, and which "whole" you are talking about. The whole 
aggregation, or the whole program?

And is the NVidia module a "derived work" or not? That's a gray area, and 
that's really what it hinges on. I personally think it's not, but I know 
others think it is.

Which is why I think you're both *potentially* right. Which one of you is 
*actually* right will depend on the exact circumstances ;)

			Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/