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: <MDEHLPKNGKAHNMBLJOLKIECJELAC.davids@webmaster.com>
Date:	Mon, 18 Jun 2007 13:03:40 -0700
From:	"David Schwartz" <davids@...master.com>
To:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: RE: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

> Ok, can I please rewrite my argument to:
>
> "The hardware manufacturer has built a custom BIOS and also written
> Linux kernel support for said BIOS.  They have released the kernel
> drivers under GPL as required, but have not released the code to the
> BIOS, instead just releasing the interface documentation.  The BIOS
> didn't exist before, and as they only intend to run Linux on the
> device, the BIOS design was heavily influenced around working well
> with Linux."
>
> Actually, we don't know that last bit, maybe they created the BIOS
> in a total vacuum and then wrote the Linux kernel driver later.
> Maybe not.
>
> Anyway, I think I've wound up arguing two sides of the same argument,
> oops.
>
> Bron.

Why does it matter whether the BIOS was "heavily influenced around working
well" with Linux? Your argument is arguing about things that have nothing to
do with anything. Your comparing things before you have any idea what the
right criteria for the comparison is.

Do you understand that all that matters is whether the BIOS contains
significant portions of the Linux code base? *Nothing* else matters.
Everything else will leave it an independent work and one that the authors
of Linux have nor right to claim any ownership of or control over.

I maintain a private application that has huge amounts of code that are
heavily influenced around working well with Linux. All the epoll code, for
example, in this code base meets that criteria. That doesn't mean it
*resembles* the Linux code in any way. It doesn't mean the Linux folks have
any right to tell me what I can and can't do with that code.

So you're arguing two sides of no argument at all.

DS

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