Date: Thu, 13 Jan 2000 18:44:23 -0700 (MST) From: "Chad R. Larson" <chad@DCFinc.com> To: cwass99@home.com (Colin) Cc: drek@MonsterByMistake.Com, freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system Message-ID: <200001140144.SAA07443@freeway.dcfinc.com> In-Reply-To: <XFMail.20000113185218.cwass99@home.com> from Colin at "Jan 13, 0 06:52:18 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As I recall, Colin wrote: > > On 13-Jan-2000 Agent Drek wrote: > > On Wed, 12 Jan 2000, Chad R. Larson wrote: > > > >|As I recall, Agent Drek wrote: > >|> > >|> I have a repeatable problem on my FreeBSD-3.4Stable workstation. If > >|> the floppy disk is physically tabbed as read-only and I mount it rw I > >|> can then 'lock' the system up by using vim (to read a text-file on the > >|> disk ... less had the same problem). Is this expected behaviour? I > >|> did this from the console and could still <Alt> between the virtual > >|> consoles. The only way to get going again was to reboot. After that > >|> happened twice I tabbed the disk writable and things were fine. > >| > >|I'd start by asking, "Why would you do that?" > > There are, oddly enough, occasionally reaons for things like floppies. > That one could slip, unnoticed, into the drive write-protected...see where this > is going? > This is where I get concerned. Failure writing to a floppy shouldn't hang > the system. That it does would imply a problem with the driver at the very > least. Or am I failing to trip on the blatantly obvious here? Well, I was protesting the logic of doing a read/write mount of read-only media. Mount it R/O and there is no issue. You wouldn't mount a CD-ROM read/write, would you? And, it would have to be "unnoticed" by someone with root permissions, or it can't be mounted at all (or written to, either). You don't let anyone other than the administrator(s) have root, do you? And you don't do day-to-day work as root, do you? But I will concede that doing that approximately silly thing shouldn't hang the system. I'd probably vote that the driver should test for write protect, and the mount(2) call should act as though "MT_RDONLY" had been specified. Either that, or fail with a EPERM or ENODEV. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001140144.SAA07443>