From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754995AbXFNWkX (ORCPT ); Thu, 14 Jun 2007 18:40:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752468AbXFNWkM (ORCPT ); Thu, 14 Jun 2007 18:40:12 -0400 Received: from mx1.redhat.com ([66.187.233.31]:44095 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752643AbXFNWkK (ORCPT ); Thu, 14 Jun 2007 18:40:10 -0400 Date: Thu, 14 Jun 2007 18:39:23 -0400 From: Bill Nottingham To: Alexandre Oliva Cc: Bron Gondwana , Alan Cox , Chris Adams , linux-kernel@vger.kernel.org Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 Message-ID: <20070614223923.GA6738@nostromo.devel.redhat.com> Mail-Followup-To: Alexandre Oliva , Bron Gondwana , Alan Cox , Chris Adams , linux-kernel@vger.kernel.org References: <20070614013214.GA1124293@hiwaay.net> <20070614025248.6e0f72f0@the-village.bc.nu> <20070614041041.GA6788@brong.net> <20070614070006.GA7393@brong.net> <20070614181626.GF3522@nostromo.devel.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.14 (2007-02-12) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alexandre Oliva (aoliva@redhat.com) said: > But how about inside the TiVO, so as to use Linux and the rest of the > GNU/Linux distro put in there for an even better DVR experience? > > Sure, this might still be accomplished on another hardware platform. > But the TiVO already has all the hardware there, and you already have > all the software ready to work on it. Except that you can't change > it. You'd have to waste time and money just to get to the same status > on another hardware platform. > > What do we gain? Nothing. But that's not the terms it was licensed under, and no matter what someone may claim about the *spirit* of the license, adding clauses that restrict how you can deploy GPL software for use is a fundamental enough change to the practical aspect of the license that it's no wonder that people will choose not to use it. If the designers of the license are more interested in vendettas against those using the software in a way they didn't see beforehand (come on, explicitly trying to define 'consumer product'?) in order to accomplish pyrrhic victories (people moving to other platforms instead of using your newly licensed code), that's fine, it's their choice. But not everyone will want to follow that choice. Bill