From owner-cvs-all Sun Jan 26 22:32:29 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F20337B405 for ; Sun, 26 Jan 2003 22:32:28 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F89243F5B for ; Sun, 26 Jan 2003 22:32:23 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 84331 invoked by uid 1000); 27 Jan 2003 06:32:20 -0000 Date: Sun, 26 Jan 2003 22:32:20 -0800 (PST) From: Nate Lawson To: phk@freebsd.org Cc: cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sbin/disklabel disklabel.c In-Reply-To: <11536.1043620366@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 26 Jan 2003 phk@freebsd.org wrote: > Robert Watson writes: > >We've always had a problem with ioctl's operating on storage devices > >regardless of the open mode (and permitted access modes) for the devidce > >nodes. > > And it ain't going to get any better as we get more weird "disks" > in the GEOM framwork. I'm not sure why boot block/disk label writes can't be done as ordinary writes and semantic checking performed by whichever GEOM layer thinks it knows best about that portion of a disk. What is wrong with that approach? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message