Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932595AbXFRUvG (ORCPT ); Mon, 18 Jun 2007 16:51:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763789AbXFRUux (ORCPT ); Mon, 18 Jun 2007 16:50:53 -0400 Received: from mx1.redhat.com ([66.187.233.31]:42450 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761827AbXFRUuw (ORCPT ); Mon, 18 Jun 2007 16:50:52 -0400 To: "David Schwartz" Cc: "Linux-Kernel\@Vger. Kernel. Org" Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 References: From: Alexandre Oliva Organization: Red Hat OS Tools Group Date: Mon, 18 Jun 2007 17:50:43 -0300 In-Reply-To: (David Schwartz's message of "Mon\, 18 Jun 2007 13\:03\:41 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.990 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2177 Lines: 53 On Jun 18, 2007, "David Schwartz" wrote: >> On Jun 17, 2007, Alan Cox wrote: >> >> >> I don't know any law that requires tivoization. >> >> > In the USSA it is arguable that wireless might need it (if done in >> > software) for certain properties. (The argument being it must be >> > tamperproof to random end consumers). >> >> But this is not tivoization. >> Tivoization is a manufacturer using technical measures to prevent the >> user from tampering (*) with the device, *while* keeping the ability >> to tamper with it changes itself. > You're splitting those hairs might finely. And I was wrong. Please see the "mea culpa on the meaning of tivoization" thread. > So when you ask whether there's any law that "requirse tivoization", > you won't accept a law that creates a situation where the only > practical solution is tivoization? I guess it amounts to what you mean by "*only* practical solution". "I can't fit the corresponding sources in this CD, so you won't get them." is no excuse to disrespect users' freedoms, why should this be different? >> Taking it further, do you know whether any such law requires >> *worldwide* tivoization, as in, applying the restrictions in the law >> even outside its own jurisdiction? > A law that requires certaint things be tamper-proof, where engineering > realities requires that they be controlled by software and the software be > upgradable (for security reasons and for support of future protocol > revisions) isn't good enough for you? "engineering realities" is the weak point of your argument, see above. Is ROM still software? Is replaceable ROM still software? -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ FSF Latin America Board Member http://www.fsfla.org/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org} - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/