linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dax Kelson <dax@gurulabs.com>
Cc: Larry McVoy <lm@bitmover.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why DRM exists (or: Larry's cloning complaint)
Date: 28 Apr 2003 11:50:11 +0100	[thread overview]
Message-ID: <1051527010.15571.53.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <1051500506.2974.69.camel@mentor.gurulabs.com>

On Llu, 2003-04-28 at 04:28, Dax Kelson wrote:
> Larry, you did a horrible -- horrible -- job in stating your
> 1. Everyone agrees that using (warezing) software in violation of it's
> license is wrong. Everyone agrees that unauthorized copying of

Not quite so clear. You need a "providing the license and its
enforcement (eg by DRM) don't violate the local law and to an 
extent local society standards

> Multiple competing implementations (Open Source or otherwise) is GOOD
> FOR THE CONSUMER!

But its not good for the Larry 8)



      reply	other threads:[~2003-04-28 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28  3:28 Why DRM exists (or: Larry's cloning complaint) Dax Kelson
2003-04-28 10:50 ` Alan Cox [this message]

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=1051527010.15571.53.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dax@gurulabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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;
as well as URLs for NNTP newsgroup(s).