From owner-freebsd-stable Thu Jan 13 21:49:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 284DB14D68 for ; Thu, 13 Jan 2000 21:49:54 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id WAA08193; Thu, 13 Jan 2000 22:49:36 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001140549.WAA08193@freeway.dcfinc.com> Subject: Re: access floppy rw to lock system In-Reply-To: <200001140505.QAA07620@lightning.itga.com.au> from Gregory Bond at "Jan 14, 0 04:05:01 pm" To: gnb@itga.com.au (Gregory Bond) Date: Thu, 13 Jan 2000 22:49:36 -0700 (MST) Cc: drek@MonsterByMistake.Com, forrestc@iMach.com, cwass99@home.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Gregory Bond wrote: >> 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. But PC floppy hardware =does= have a "media changed" function. So, same deal. -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