From: "David A. Gatwood" <marsmail@globegate.utm.edu>
To: Brad Midgley <brad@pht.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: floppy driver bug: write-protect
Date: Thu, 14 Jan 1999 20:18:16 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.3.96.990114201533.20267D-100000@globegate.utm.edu> (raw)
In-Reply-To: <Pine.LNX.3.95.981115182106.10912A-100000@pacific.pht.com>
On Sun, 15 Nov 1998, Brad Midgley wrote:
> 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?
Wow, so you guys have that problem, too, eh? MkLinux's floppy driver does
the same thing. It's given me fits trying to find something in LinuxPPC
to demote it to read-only. Guess that's why I didn't find anything!!!
:-)
If anybody figures out how to fix this (no doubt the same fix, roughly,
for both), please let me know. I've gotten as far as forcing the device
read-only, but that flag is ignored by at least umsdos filesystem support,
not sure what else.... :-(
Later,
David
David A. Gatwood Visit globegate's internet
dgatwood@globegate.utm.edu talker, Deep Space 36
http://globegate.utm.edu telnet globegate.utm.edu:9624
-----BEGIN GEEK CODE BLOCK-----
Version 3.1
GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++ ++>$ UBLAS*++ ++>$
P+?>$ L++ +>$ !E--- W++ +>$ N++(++ +)>++ +$ !o? K-? !w--- !O
M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t++ +>$ 5+>++ ++$ !X- !R tv+>$
b++>$ !DI !D- G++(++ +)>$ e>++ ++ h--! r--- !y-
------END GEEK CODE BLOCK------
[[ 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 prev parent reply other threads:[~1999-01-15 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 1:27 floppy driver bug: write-protect Brad Midgley
1999-01-15 2:18 ` David A. Gatwood [this message]
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.96.990114201533.20267D-100000@globegate.utm.edu \
--to=marsmail@globegate.utm.edu \
--cc=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.