Date: Fri, 09 Feb 2001 00:03:06 -0500 From: Kenny Drobnack <kdrobnac@columbus.rr.com> To: freebsd-hackers@freebsd.org Subject: mount checking for read-only media Message-ID: <3A837A0A.DAB3520A@columbus.rr.com>
next in thread | raw e-mail | index | archive | help
There's this little problem with FreeBSD that has been bugging me a bit for a while now. There have been a couple times I've tried to mount Zip disks or floppy drives in FreeBSD, and had the /etc/fstab set up to mount read/write, and didn't realize that I had write protect turned on. However, I didn't realize the write protect was turned on until I tried writing to the drive. This caused lots of hard write errors or some such thing, and the system eventual just said "hit any key to reboot". I guess some buffer somewhere got full and crashed the kernel. There's never any kernel dump, so I can't easily send debug messages. Is there some reason that no check is done to make sure the media is writable before writing to it? Is some system call to check the hardware to see if its physically writable? I figure there is. I want to start hacking at the kernel a bit, and it seems like something simple (comparitively) would be a good place to start. Up there on my wish list is getting a journaling filesystem ported to FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A837A0A.DAB3520A>