From owner-freebsd-hackers Tue Jul 18 11:36:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA04143 for hackers-outgoing; Tue, 18 Jul 1995 11:36:34 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA04121 for ; Tue, 18 Jul 1995 11:36:27 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA21989; Wed, 19 Jul 1995 04:30:36 +1000 Date: Wed, 19 Jul 1995 04:30:36 +1000 From: Bruce Evans Message-Id: <199507181830.EAA21989@godzilla.zeta.org.au> To: imp@village.org, rgrimes@gndrsh.aac.dev.com Subject: Re: A problem with disklabel & "use entire disk" on 2.0.5R. Cc: freebsd-hackers@freebsd.org Sender: hackers-owner@freebsd.org Precedence: bulk >> Is there some way to write a valid partion table to BSD only disks? >> Wouldn't that solve the problem, or am I dreaming... >Problem is that boot1 lives in sector 0 in this case, so anytime you >install new boot blocks you end up with a 50K not quite right bogus >partition table from the boot1 code. >Newfs needs fixed to deal with the fact it _must_ preserve the existing >partition table if installing boot code to physical sector 0 of the disk. A partition that covers the whole disk must have offset 0 and cover the MBR. Such partitions can reasonably be considered as invalid. Preserving them would make no difference to FreeBSD and might not stop foreign fdisks and installs from nuking them. Bruce