From owner-freebsd-current  Sat Feb  1 18:39:27 2003
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 60B5B37B401; Sat,  1 Feb 2003 18:39:26 -0800 (PST)
Received: from www.reppep.com (www.reppep.com [66.92.104.200])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BE1F543F3F; Sat,  1 Feb 2003 18:39:25 -0800 (PST)
	(envelope-from pepper@reppep.com)
Received: from [66.92.104.201] (g4.reppep.com [66.92.104.201])
	by www.reppep.com (Postfix) with ESMTP
	id 77ABAFDCE; Sat,  1 Feb 2003 21:39:25 -0500 (EST)
Mime-Version: 1.0
X-Sender: pepper@mail.reppep.com
Message-Id: <p06000204ba610362224e@[66.92.104.201]>
In-Reply-To: <6349.1043582467@critter.freebsd.dk>
References: <6349.1043582467@critter.freebsd.dk>
Date: Sat, 1 Feb 2003 21:34:16 -0500
To: phk@freebsd.org
From: Chris Pepper <pepper@reppep.com>
Subject: Re: cvs commit: src/sbin/disklabel disklabel.8 disklabel.c
Cc: Ruslan Ermilov <ru@freebsd.org>, current@freebsd.org,
	docs@freebsd.org, Robert Nordier <rnordier@FreeBSD.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

At 1:01 PM +0100 2003/01/26, phk@freebsd.org wrote:
>In message <20030126114000.GA58366@sunbay.com>, Ruslan Ermilov writes:

>Welcome to the club if people who was bitten by the poor design
>choices in the BSD disklabel.
>
>  >Now the
>>question.  Where is the code in the kernel that prevents swapping
>>and/or writing to a disklabel portion of a physically first
>  >partition on the disk?

	This reminds me of a related suggestion / request. boot0cfg 
should be smarter, and require confirmation (unless forced) before 
overwrite a disklabel with an MBR (boot0cfg -b /dev/ad0s2g or 
similar). I believe overwriting a disklabel is much more likely to be 
pilot error, as in my case, than an deliberate choice.

	boot0cfg.8 says:

>      On PCs, a boot manager typically occupies sector 0 of a disk, which is
>      known as the Master Boot Record (MBR).  The MBR contains both code (to
>      which control is passed by the PC BIOS) and data (an embedded table of
>      defined slices).


						Regards,


						Chris Pepper
-- 
Chris Pepper:               <http://www.reppep.com/~pepper/>
Rockefeller University:     <http://www.rockefeller.edu/>

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