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]

Message-ID: <20070616021630.GA30660@brong.net>
Date:	Sat, 16 Jun 2007 12:16:30 +1000
From:	Bron Gondwana <brong@...tmail.fm>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Bron Gondwana <brong@...tmail.fm>, Ingo Molnar <mingo@...e.hu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	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>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Fri, Jun 15, 2007 at 04:26:34PM -0300, Alexandre Oliva wrote:
> On Jun 15, 2007, Bron Gondwana <brong@...tmail.fm> wrote:
> 
> > What happens if you're debugging something you think is a bug in the
> > Linux kernel and then you run bang into some interactions that make you
> > think the bug might be in the BIOS instead.
> 
> > have denied your freedom to modify and debug the system they sold you
> 
> If the bug is in the non-GPLed BIOS, not in the GPLed code, too bad.
> One more reason to dislike non-Free Software.

If the bug is in the non-GPLed binary module, not in the GPLed code, too
bad.  One more reason to dislike non-Free Software.

It's the same argument from the other direction.  The BIOS is linked
(inside the machine, sure) to the kernel for all intents and purposes
through a defined interface.  This doesn't affect the BIOS developers
who ship me a machine on to which I then install Linux, but it _does_
affect a hardware vendor who ships me a system with Linux pre-installed,
because it could easily be argued that they linked the BIOS with the
Linux kernel and hence produced a combined work (remember, they reserve
the right to modify the BIOS, but don't give that that right to me) and
the BIOS should now come under the GPL.

Talk about your chilling effects.  It's a strong reason for vendors not
to ship GPL3 or GPL2[your interpretation] code pre-installed while the
legal boundaries of work combination are in any way grey.

Regards,

Bron.
-
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/