From: Dave Mielke <dave@mielke.cc>
To: linux-sound@vger.kernel.org
Subject: Re: hdparm...
Date: Tue, 31 Aug 1999 12:08:22 +0000 [thread overview]
Message-ID: <marc-linux-sound-93610087916960@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93608992629994@msgid-missing>
On Tue, 31 Aug 1999, Jair-Rohm wrote:
>The man page for 'hdparm' mentions something about use of the '-m' option
>potentially resulting in "...massive filesystem corruption." This of course
>if your EIDE drive "lies" about its support for multiple mode.
>
>Anyone have any experience with this?
To get a good answer to this question, you'll have to identify exactly which
type(s) of disk hardware you have. users with well-behaved, truth-telling
hardware will have had good experiences, whereas users with bad, dishonest
hardware will have had bad experiences.
--
Dave Mielke | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
EMail: dave@mielke.cc | Canada K2B 6G3 | if you're concerned about Hell.
prev parent reply other threads:[~1999-08-31 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-31 8:58 hdparm Jair-Rohm
1999-08-31 9:53 ` hdparm Benno Senoner
1999-08-31 12:08 ` Dave Mielke [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=marc-linux-sound-93610087916960@msgid-missing \
--to=dave@mielke.cc \
--cc=linux-sound@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