From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261874AbTD3KcK (ORCPT ); Wed, 30 Apr 2003 06:32:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261944AbTD3KcK (ORCPT ); Wed, 30 Apr 2003 06:32:10 -0400 Received: from 205-158-62-158.outblaze.com ([205.158.62.158]:53909 "HELO spf1.us.outblaze.com") by vger.kernel.org with SMTP id S261874AbTD3KcJ (ORCPT ); Wed, 30 Apr 2003 06:32:09 -0400 Message-ID: <20030430104412.11792.qmail@linuxmail.org> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) From: "Dean McEwan" To: linux-kernel@vger.kernel.org Date: Wed, 30 Apr 2003 10:44:12 +0000 Subject: Re: Flame Linus to a crisp! AKA DRM X-Originating-Ip: 195.195.129.3 X-Originating-Server: ws5-8.us4.outblaze.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 28 Apr 2003, Zack Gilburd wrote: > On Mon, 28 Apr 2003 03:35:10 -0700 (PDT) > Andre Hedrick wrote: Oooh suprise. > > > There is one fundamental problem, and nobody has addressed. > > > > Who will enforce the GPL over DRM violations? The copyright author if they so choose to do so. > > Since it is a blanket over the entire kernel, and you have formally > > (for the most part) have authorized DRM, thus one assumes you are the only > > one who can pursue in a court of law. > > Unless I am missing something, I was hoping for more of a sparse DRM \ > implementation; not a blanket. > I was hoping to be able to `modprobe drm` for when I needed to use DRM and likewise \ > `rmmod drm` for when I didn't want it. Maybe I am a little late in this \ > disucssion, but that's just my hopes and whishes. -- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze