From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] DRM OS
Date: Thu, 3 Jan 2002 11:10:53 +0000 (UTC) [thread overview]
Message-ID: <a11e7t$rsh$1@forge.intermeta.de> (raw)
In-Reply-To: <3C338600.B019EED9@sympatico.ca> <Pine.LNX.4.10.10201021425380.11866-100000@master.linux-ide.org>
Andre Hedrick <andre@linux-ide.org> writes:
>http://www.lsilogic.com/techlib/marketing_docs/consumer/ACF394.pdf
So this chip encrypts before storing data on a HD. Thats' fine with
me, because there is no logic inside the drive involved. If the drive
would contain the "encryption algorithms", so that I cannot run a
"free" OS on it, then I would be concerned.
What I really _do_ hate is the "Advertisment insertion" paragraph.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2002-01-03 11:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 4:00 [OT] DRM OS James Simmons
2001-12-13 4:07 ` Matt
2001-12-13 13:38 ` Rik van Riel
2001-12-14 9:15 ` Andre Hedrick
2001-12-15 0:32 ` Aaron Lehmann
2001-12-17 6:10 ` TimO
2001-12-18 16:17 ` Alan Cox
2001-12-18 18:54 ` James Simmons
2001-12-18 19:06 ` Andre Hedrick
2001-12-18 19:53 ` Aaron Lehmann
2001-12-18 20:05 ` Dave Jones
2001-12-18 20:10 ` Aaron Lehmann
2001-12-18 20:25 ` Dave Jones
2001-12-18 20:45 ` H. Peter Anvin
2001-12-19 10:39 ` Helge Hafting
2001-12-18 20:44 ` Rik van Riel
2001-12-18 20:56 ` Gábor Lénárt
2001-12-19 21:49 ` Thomas Dodd
2001-12-20 22:40 ` Marco Ermini
2001-12-21 16:38 ` Brendan Pike
2002-01-02 22:13 ` Chris Friesen
2002-01-02 22:30 ` Alan Cox
2002-01-03 1:52 ` Andre Hedrick
2002-01-03 11:10 ` Henning P. Schmiedehausen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-13 14:21 Thomas Hood
2001-12-13 15:33 Jesse Pollard
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='a11e7t$rsh$1@forge.intermeta.de' \
--to=hps@intermeta.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.