From owner-freebsd-stable Thu Jan 13 21: 5:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 7AAA5151B6 for ; Thu, 13 Jan 2000 21:05:10 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA47046; Fri, 14 Jan 2000 16:05:02 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA07620; Fri, 14 Jan 2000 16:05:01 +1100 (EST) Message-Id: <200001140505.QAA07620@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Agent Drek Cc: "Forrest W. Christian" , "Chad R. Larson" , Colin , freebsd-stable@FreeBSD.ORG Subject: Re: access floppy rw to lock system In-reply-to: Your message of Thu, 13 Jan 2000 23:26:51 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jan 2000 16:05:01 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > |Exactly. If it's read-only media, it should fail when being mounted > |read-write, or default to ro. Even this is not enough. PC floppy hardware doesn't have a "lock media" function, so you can get the same panic by changing a floppy for a write-protected one while it is mounted. I suspect that this hardware-induced inability to usefully cover all the bases, along with some more fundamental structural changes that are happening in -CURRENT, are why this hasn't been solved more gracefully for -STABLE yet. Until then: "Don't do that!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message