From: Stefan Smietanowski <stesmi@stesmi.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: OT: DVD-* owners be warned . Please see inside .
Date: Tue, 29 Oct 2002 23:13:02 +0100 [thread overview]
Message-ID: <3DBF07EE.50401@stesmi.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210100949270.6366-100000@filesrv1.baby-dragons.com
Mr. James W. Laferriere wrote:
> Hello All ,
>
> Here we go . Two differant hardware types to prevent users from
> making private backups of items that they have purchased . I hope
> that somewhere in the community there is a methodology to
> circumvent this stupidity .
>
> Below is a snippet from the URL below this :
>
> Why are there two formats? The key reason for the introduction of
> DVD-R for General media is that it contains content protection
> measures that make it physically impossible to make a bit-for-bit
> copies of CSS encrypted entertainment titles.
>
> http://www.pioneerelectronics.com/Pioneer/Files/DVDRMedia-GeneralvsAuthoring.pdf
Thought I'd point out that this is old news. Very old in fact.
This was set when the DVD-R standard was put in place ...
Or actually, shortly thereafter.
At first there was only one standard, DVD-R. Now there are two at
different wavelengths, DVD For General (cannot copy css encrypted
things) and DVD-R For Authoring which can but those discs cost a lot
more. DVD-R was renamed DVD-R For Authoring.
// Stefan
prev parent reply other threads:[~2002-10-29 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 13:57 OT: DVD-* owners be warned . Please see inside Mr. James W. Laferriere
2002-10-29 22:13 ` Stefan Smietanowski [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=3DBF07EE.50401@stesmi.com \
--to=stesmi@stesmi.com \
--cc=babydr@baby-dragons.com \
--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;
as well as URLs for NNTP newsgroup(s).