From owner-freebsd-stable Sat Jan 15 13:56:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 42D8914E7E for ; Sat, 15 Jan 2000 13:56:30 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000115215413.YAF15357.mail.rdc3.on.home.com@tristan.net>; Sat, 15 Jan 2000 13:54:13 -0800 Content-Length: 1255 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001140144.SAA07443@freeway.dcfinc.com> Date: Sat, 15 Jan 2000 16:52:59 -0500 (EST) From: Colin To: "Chad R. Larson" Subject: Re: access floppy rw to lock system Cc: freebsd-stable@FreeBSD.ORG, drek@MonsterByMistake.Com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Jan-2000 Chad R. Larson wrote: > > 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? > Of course not ;) My point was if you inserted the floppy with the intent of writing to it (eg to create a set of boot disks to do another FreeBSD install ;)) and forgot to check the location of the tab your next step will be a reboot. > And, it would have to be "unnoticed" by someone with root > permissions, or it can't be mounted at all (or written to, either). > I didn't realize "root" access automagically bestowed an inability to make mistakes ;) I agree root needs to be paying a lot more attention than a normal user, but as my kid so eloquently puts it, "stuff happens" ;) > 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. > I guess, from this last bit, we basically agree that there is a problem here, we just don't view it's importance the same ;) cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message