From: "Dean McEwan" <dean_mcewan@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Flame Linus to a crisp! AKA DRM
Date: Wed, 30 Apr 2003 10:44:12 +0000 [thread overview]
Message-ID: <20030430104412.11792.qmail@linuxmail.org> (raw)
On Mon, 28 Apr 2003, Zack Gilburd wrote:
> On Mon, 28 Apr 2003 03:35:10 -0700 (PDT)
> Andre Hedrick <andre@linux-ide.org> 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
reply other threads:[~2003-04-30 10:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030430104412.11792.qmail@linuxmail.org \
--to=dean_mcewan@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox