From owner-freebsd-current  Tue Mar 30 13:39:31 1999
Delivered-To: freebsd-current@freebsd.org
Received: from misha.cisco.com (misha.cisco.com [171.69.206.50])
	by hub.freebsd.org (Postfix) with ESMTP id 0F19514C25
	for <current@freebsd.org>; Tue, 30 Mar 1999 13:39:29 -0800 (PST)
	(envelope-from mi@misha.cisco.com)
Received: (from mi@localhost)
	by misha.cisco.com (8.9.2/8.9.1) id QAA47485;
	Tue, 30 Mar 1999 16:38:27 -0500 (EST)
	(envelope-from mi)
From: Mikhail Teterin <mi@misha.cisco.com>
Message-Id: <199903302138.QAA47485@misha.cisco.com>
Subject: Re: mount of write protected fd's
In-Reply-To: <19990330223132.A4808@dva.in-berlin.de> from Boris Staeblow at "Mar 30, 1999 10:31:32 pm"
To: balu@dva.in-berlin.de (Boris Staeblow)
Date: Tue, 30 Mar 1999 16:38:27 -0500 (EST)
Cc: current@freebsd.org
Reply-To: mi@aldan.algebra.com
X-Mailer: ELM [version 2.4ME+ PL52 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Boris Staeblow once wrote:

> mount should detect that a fd is write-protected and mount it "ro"
> although no "mount -r" is given... Isn't it possible to detect the w/p
> status from the fd-controller?

Actually, the existing behavior is rather horrible. If you forget
to specify ro for a read-only floppy, mount will succeed, but the
kernel will keep complaining. It will also NOT let you umount the
damn thing (even with -f), until you take the floppy out and
write-enable it.  Which, sometimes, requires use of duct tape...

	-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message