From: Paul Mackerras <paulus@cs.anu.edu.au>
To: brad@pht.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: floppy driver bug: write-protect
Date: Fri, 15 Jan 1999 14:31:22 +1100 [thread overview]
Message-ID: <199901150331.OAA01845@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.3.95.981115182106.10912A-100000@pacific.pht.com> (message from Brad Midgley on Sun, 15 Nov 1998 18:27:09 -0700 (MST))
Brad Midgley <brad@pht.com> wrote:
> is this a known bug?
well, I didn't know about it. :-)
> on intel linux, if you try to mount a write-protected floppy disk
> read-write, the mount succeeds but is demoted to read-only.
Do you have access to an intel-linux box? Could you do an strace on
the mount command on a write-protected floppy and see whether mount
does two mount system calls (the first failing with EROFS), or if it
does some other ioctl to check whether the disk is write-protected?
> 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
OK, I need to check the write-protect status in the floppy_write
routine in swim3.c.
I have recently looked at the floppy driver source code in MkLinux,
which looks like it is derived from macos sources. It looks like
there are a few tweaks which I need to do to the Linux/PPC driver.
Paul.
[[ 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 3:31 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
1999-01-15 3:30 ` Brad Midgley
1999-01-15 3:31 ` Paul Mackerras [this message]
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=199901150331.OAA01845@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--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.