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] [day] [month] [year] [list]

Message-Id: <1182284470.24817.12.camel@rousalka.dyndns.org>
Date:	Tue, 19 Jun 2007 22:21:10 +0200
From:	Nicolas Mailhot <nicolas.mailhot@...oste.net>
To:	Diego Calleja <diegocg@...il.com>
Cc:	davids@...master.com, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

Le mardi 19 juin 2007 à 21:56 +0200, Diego Calleja a écrit :

> Please, stop pretending you are hardware manufacturers. You are not.

Please, stop pretending the end user has no say in the GPL. The GPL (v2
or v3) is written with the end user not the hardware manufacturer in
mind.

Also I can tell you the enterprises who make the living of Red Hat,
Novell and IBM (to name some major kernel contributors) care very much
about their part of the GPL deal. That is they can dump a supplier
(hardware or software) at any moment because he has no lock on their
system. Should the kernel devs ally themselves with entities like Tivo
who put the vendor lock-in back in free/libre systems, said systems
attractivity will decrease sharply (and it only takes a few managers to
notice their Linux systems are just as locked as the usual proprietary
ones)

Tivo didn't make the Linux success. More Tivos can definitely undo it.

-- 
Nicolas Mailhot

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)