Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755476AbXFVUVx (ORCPT ); Fri, 22 Jun 2007 16:21:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751526AbXFVUVp (ORCPT ); Fri, 22 Jun 2007 16:21:45 -0400 Received: from py-out-1112.google.com ([64.233.166.180]:6633 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751511AbXFVUVp (ORCPT ); Fri, 22 Jun 2007 16:21:45 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WahsHRQ2ey1JuVP58LqbOZuuhdH2mZvnGiwcdLCf8172725hK5aQP7JLW0MljjqHH9LHF3RvxnoLawf4I3jTbMCwwSR6mPcr1lAaHnfUzXjQixCkuH1TiwC6cnoouOcdnA3zoBqzbl8E7n9QD5CCwUeMUuq0Z2ima1IKMan4y5k= Message-ID: <2e6659dd0706221321x536058c4g343c3b43dbf2e29e@mail.gmail.com> Date: Fri, 22 Jun 2007 17:21:44 -0300 From: "Tomas Neme" To: linux-kernel@vger.kernel.org Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4679557C.5080907@iders.ca> <20070620175627.319a6c55@the-village.bc.nu> <46797C52.4020907@iders.ca> <467A99D6.6000605@iders.ca> <467ADC8A.5080401@iders.ca> <2e6659dd0706220945g3592c558h2fe3d56c4b5015ff@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1608 Lines: 34 > In the sense that he can decide to remove all contributions from > dissenting authors, yes, he does. But he can't impose his more lax > interpretation upon other authors. Under copyright, it's the more yes, I saw my argument going weak as I wrote it, but what I said later: > So if you own a part of the kernel, then you can pursuit TiVo on your > own, if they did direct use of that part especifically and break (in > your opinion) what you feel GPLv2 means. You can form the CATV2 > (CodersAgainstTiVo v2) and try to get TiVo to stop using the Linux > Kernel for their product (because, believe me, they WON'T release the > keys). Yeay, we lost Tivo's improvements on the kernel, and the > posibility of having a working kernel if anyone feels like > back-ingeneering TiVo for their own amusement. is still right. What I meant, at least by the end of that email, was that he has the last word on trying to stop TiVo from using The Linux Kernel. Each author can still go and stop them from using his part, and the derivative work that is The Linux Kernel. But that brings another question: what if TiVo decided to remove all code from the complaining parts and rewrite them? that wouldn't be The Linux Kernel anymore, but it would be a derivative work of all the parts that don't disagree with Tivoization, but is that legal? -- |_|0|_| |_|_|0| |0|0|0| - 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/