public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dean McEwan" <dean_mcewan@linuxmail.org>
To: "Paul Rolland" <rol@as2917.net>, core@enodev.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Digital Rights Management - An idea
Date: Thu, 15 May 2003 10:46:01 +0000	[thread overview]
Message-ID: <20030515104601.23104.qmail@linuxmail.org> (raw)


> Which would make it impossible to import even the simplest text data
> file on such a machine ????

You would be asked to pick a license for file, pick artistic, 
and anyone could use it, encryption would also compress file...

 
> Paul
> 

-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

             reply	other threads:[~2003-05-15 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 10:46 Dean McEwan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 15:40 Digital Rights Management - An idea Dean McEwan
2003-05-14 16:46 ` Shawn
2003-05-15  9:25 ` Paul Rolland
2003-05-14  8:30 Dean McEwan
2003-05-14  8:39 ` Paul Rolland
2003-05-14 10:50 ` Alan Cox
2003-05-14 14:27 ` Shawn

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=20030515104601.23104.qmail@linuxmail.org \
    --to=dean_mcewan@linuxmail.org \
    --cc=core@enodev.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rol@as2917.net \
    /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