From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 18:38:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E124816A4E5 for ; Thu, 19 Aug 2004 18:38:26 +0000 (GMT) Received: from mail004.syd.optusnet.com.au (mail004.syd.optusnet.com.au [211.29.132.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43BCE43D48 for ; Thu, 19 Aug 2004 18:38:24 +0000 (GMT) (envelope-from fbsd@mawer.org) Received: from c211-30-90-140.belrs3.nsw.optusnet.com.au (c211-30-90-140.belrs3.nsw.optusnet.com.au [211.30.90.140]) i7JIcL810272 for ; Fri, 20 Aug 2004 04:38:22 +1000 Received: (qmail 89278 invoked from network); 19 Aug 2004 18:38:21 -0000 Received: from unknown (HELO ?10.1.1.1?) (unknown) by unknown with SMTP; 19 Aug 2004 18:38:21 -0000 Message-ID: <4124F3A0.2030509@mawer.org> Date: Fri, 20 Aug 2004 04:38:24 +1000 From: Antony Mawer User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgos Keramidas References: <20040819141310.GA756@gicco.homeip.net> <19666.1092926344@critter.freebsd.dk> <20040819161000.GB843@gicco.homeip.net> <20040819164751.GB4004@orion.daedalusnetworks.priv> In-Reply-To: <20040819164751.GB4004@orion.daedalusnetworks.priv> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 20 Aug 2004 12:25:33 +0000 cc: current@freebsd.org Subject: Re: [REVIEW/TEST] Rewritten floppy driver. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2004 18:38:28 -0000 Giorgos Keramidas wrote: >>If a writeprotected floppy can't be mounted writable it's >>sufficient. > > The patch prevents read-write mounts of read-only floppies: *snip* > : orion# mount -t ufs /dev/fd0 /mnt > : mount: /dev/fd0: Read-only file system Would a more optimal solution be to show a warning indicating that the disk was write-protected, and proceed to mount the filesystem read-only? This may be a ridiculous proposal - I don't know enough about the code in question to say - but it was just a thought! :-) Cheers Antony