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:	Sat, 16 Jun 2007 05:26:57 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	"Scott Preece" <sepreece@...il.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Rob Landley" <rob@...dley.net>,
	"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 Jun 16, 2007, "Scott Preece" <sepreece@...il.com> wrote:

> On 6/15/07, Alexandre Oliva <aoliva@...hat.com> wrote:
>> On Jun 15, 2007, "Scott Preece" <sepreece@...il.com> wrote:
>> 

>> > Whether it's a legal requirement or a business decision, the result is
>> > the same - neither forcing the manufacturer to make the device
>> > non-updatable nor forcing the manufacturer to use different software
>> > benefits anyone.
>> 
>> I agree.  But that's an incomplete picture.
>> 
>> It's the other part of the picture, that you left out twice, that is
>> the case that is good for the users *and* for the community.
> ---

> I don't think I "left it out". The point is that if the manufacturer
> is unwilling to give the right to modify, no change in the language is
> going to cause the user to have that right.

If the alternatives are worse for the manufacturer than letting the
user have it, then it will have the intended effects.  In the other
cases, it won't make much of a difference for anyone else.

The question is: how does tivoization help the community (under the
tit-for-tat reasoning)?  Does it help more than anti-tivoization?

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
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/