From: Marko Kohtala <Marko.Kohtala@nokia.com>
To: dalecki@evision-ventures.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: Removable IDE devices problem
Date: Fri, 08 Mar 2002 12:42:49 +0200 [thread overview]
Message-ID: <3C8895A9.9090705@nokia.com> (raw)
> Your analysis of the problem is entierly right, since the current
> kernel behaviour for removable media is supposed to work for
> floppies (never get this thing out of your computer
> as long as long the diode blinks) or read only media where it doesn't
> really matter. However I still don't see a good way to
> resolve this issue. (Maybe just adding buffer cache flush before
> going into the check_media_change business of "grocking" partitions
> would be sufficient...
But there is ide-floppy and ide-cd with their own media_check functions.
I'm thinking about ignoring the removable bit, at least when the device
does not have door lock. What would be hurt by it?
P.S. Sorry for the previous mail with long lines. I should know better
than using Outlook...
next reply other threads:[~2002-03-08 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 10:42 Marko Kohtala [this message]
2002-03-08 12:01 ` Removable IDE devices problem Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 16:57 marko.kohtala
2002-03-06 17:13 ` Martin Dalecki
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=3C8895A9.9090705@nokia.com \
--to=marko.kohtala@nokia.com \
--cc=dalecki@evision-ventures.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