From: Brad Midgley <brad@pht.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: floppy driver bug: write-protect
Date: Sun, 15 Nov 1998 18:27:09 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.3.95.981115182106.10912A-100000@pacific.pht.com> (raw)
is this a known bug?
on intel linux, if you try to mount a write-protected floppy disk
read-write, the mount succeeds but is demoted to read-only.
the current pmac kernel will mount the disk read-write and will allow
"writes" to the disk. the writes even appear to succeed and the mounted
filesystem returns really strange results when you look at it (it's
caching the "writes" and everything seems normal until uncached data has
to be loaded from the disk!)
is it known how to query the drive for the write-protect status? does this
problem affect any other removable media?
brad
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1998-11-16 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 1:27 Brad Midgley [this message]
1999-01-15 2:18 ` floppy driver bug: write-protect David A. Gatwood
1999-01-15 3:30 ` Brad Midgley
1999-01-15 3:31 ` Paul Mackerras
1999-01-15 18:34 ` David A. Gatwood
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=Pine.LNX.3.95.981115182106.10912A-100000@pacific.pht.com \
--to=brad@pht.com \
--cc=linuxppc-dev@lists.linuxppc.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.