From: Brian Gerst <bgerst@quark.didntduck.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Christian Borntraeger <linux@borntraeger.net>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: ide-related kernel panic in 2.4.19 and 2.4.20-pre11
Date: Sat, 19 Oct 2002 18:39:48 -0400 [thread overview]
Message-ID: <3DB1DF34.3000600@quark.didntduck.org> (raw)
In-Reply-To: Pine.LNX.4.10.10210191451530.24031-100000@master.linux-ide.org
Andre Hedrick wrote:
> So could you ask the question a little more blunt?
>
> "Gee, I am trying to break a US Law on content protection, would you be my
> enabler? Don't worry, it only effects the US, and we are in a public
> forum. Also, do you prefer gray or black in your future pin stripped
> suit?"
Attempting to read a "defective" disc should never, ever, cause a kernel
oops. Whether it succeeds or not is irrelevant.
--
Brian Gerst
next prev parent reply other threads:[~2002-10-19 22:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 19:41 PROBLEM: ide-related kernel panic in 2.4.19 and 2.4.20-pre11 Christian Borntraeger
2002-10-19 22:02 ` Andre Hedrick
2002-10-19 22:32 ` Andreas Steinmetz
2002-10-19 22:49 ` Andre Hedrick
2002-10-21 12:22 ` Alan Cox
2002-10-19 22:39 ` Brian Gerst [this message]
2002-10-19 22:54 ` Andre Hedrick
2002-10-19 23:19 ` Brian Gerst
2002-10-19 23:44 ` Andre Hedrick
2002-10-20 0:14 ` Brian Gerst
2002-10-20 0:41 ` Andre Hedrick
2002-10-20 15:46 ` Denis Vlasenko
2002-10-20 14:59 ` Henning P. Schmiedehausen
2002-10-20 22:54 ` Benjamin Herrenschmidt
2002-10-19 23:20 ` Toon van der Pas
2002-10-20 0:01 ` Andre Hedrick
2002-10-20 15:01 ` Henning P. Schmiedehausen
2002-10-20 10:14 ` Christian Borntraeger
2002-10-20 22:49 ` Bill Davidsen
2002-10-31 22:00 ` Thomas Dodd
2002-11-01 1:24 ` Bill Davidsen
2002-10-20 23:01 ` David Woodhouse
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=3DB1DF34.3000600@quark.didntduck.org \
--to=bgerst@quark.didntduck.org \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@borntraeger.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 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.