So it seems that probably all block devices have this bug. I haven't
tried it with an ATA or SCSI hard drive, tape drive, or any flash RAM
type stuff. The problem does occur on standard floppy disks and on my
parallel port zip drives.
If/when I do mess with it, I think I'll stick with the Unix tradition
of never making the OS assume it knows more than the user. Some kind of
force option to mount the partition read-write, even if it seems to be
read-only seems good...
Expect to see more postings, if I get around to messing with the kernel
and don't understand. Hopefully a couple patches will appear on this
list soon :-)
> > It's not system call but `od' driver does check if the medium is
> > writable or not. It returns EACCESS when the mount option is -rw and
> > the medium is read-only. `od' is drived from `da' so quick hack will
> > do the trick.
>
> This is all for scsi drives. I may not know everything, but I know most
> floppies aren't scsi! But, I am sure the problem exists for both. I know
> from experience that is exists or did exist for ata drives. I think he
> would be more likely to find the code for his problem in the 'ad' driver
> files. I could be wrong about this... but I know I had this happen to me
> on a computer without scsi equipment before. Of course, if he has a scsi
> zip drive as well, then both need to get fixed. ;-)
>
> Kevin Brunelle
> --
> "Do not meddle in the affairs of sysadmins,
> for they are subtle and quick to anger."
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
