From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 19:12:05 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 6A05D16A4CE for ; Thu, 19 Aug 2004 19:12:05 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A40743D5A for ; Thu, 19 Aug 2004 19:12:04 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from gothmog.gr (patr530-a070.otenet.gr [212.205.215.70]) i7JJC0bE004203; Thu, 19 Aug 2004 22:12:01 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id i7JJAioI000910; Thu, 19 Aug 2004 22:10:44 +0300 (EEST) (envelope-from keramida@linux.gr) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id i7JJAi2m000909; Thu, 19 Aug 2004 22:10:44 +0300 (EEST) (envelope-from keramida@linux.gr) Date: Thu, 19 Aug 2004 22:10:44 +0300 From: Giorgos Keramidas To: Antony Mawer Message-ID: <20040819191044.GB670@gothmog.gr> References: <20040819141310.GA756@gicco.homeip.net> <19666.1092926344@critter.freebsd.dk> <20040819161000.GB843@gicco.homeip.net> <20040819164751.GB4004@orion.daedalusnetworks.priv> <4124F3A0.2030509@mawer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4124F3A0.2030509@mawer.org> 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 19:12:05 -0000 On 2004-08-20 04:38, Antony Mawer wrote: > 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! :-) I know very few things about the way this patch works too, but I did some tests using userlevel tools earlier tonight. I've emailed PHK with some comments and I'm sure if what you propose can be done he's the best person to actually do it ;-)