From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: linux-kernel@vger.kernel.org
Subject: 2.2.18: writing an R/O floppy
Date: Wed, 10 Jan 2001 08:31:22 +0100 [thread overview]
Message-ID: <3A5C1DCE.19065.27109F@localhost> (raw)
Hi,
I don't know if it's possible to make fd a read-only device if the
inserted media is write-protected, but I had a strange problem:
I had inserted a write protected floppy and accessed it via autofs as
vfat in 2.2.18. It worked. Some time later it had expired (and I'm not
sure whether I had changed floppies in the meantime).
When I tried an "mdel a:*", it did terminate without message, but a
later "mdir a:" showed all the files there. The kernel had
unsuccessfully tried to write to the floppy however.
It's a bit hard to reproduce that, but I could guess that the disc-
change ore write-protect status was not updated in some case.
Maybe it rings some bell for one of you; if not, never mind.
Regards,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-01-10 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A5C1DCE.19065.27109F@localhost \
--to=ulrich.windl@rz.uni-regensburg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox