From owner-freebsd-i386@FreeBSD.ORG Fri Feb 29 02:30:03 2008 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36FE21065673 for ; Fri, 29 Feb 2008 02:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 227FB8FC16 for ; Fri, 29 Feb 2008 02:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m1T2U2kM038436 for ; Fri, 29 Feb 2008 02:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m1T2U2s6038425; Fri, 29 Feb 2008 02:30:02 GMT (envelope-from gnats) Date: Fri, 29 Feb 2008 02:30:02 GMT Message-Id: <200802290230.m1T2U2s6038425@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: linimon@lonesome.com (Mark Linimon) Cc: Subject: Re: i386/121124: FreeBSD 6.3 installation deletes MBR partition X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Feb 2008 02:30:03 -0000 The following reply was made to PR i386/121124; it has been noted by GNATS. From: linimon@lonesome.com (Mark Linimon) To: bug-followup@FreeBSD.org Cc: Subject: Re: i386/121124: FreeBSD 6.3 installation deletes MBR partition Date: Thu, 28 Feb 2008 20:26:23 -0600 ----- Forwarded message from Dan Strick ----- My best guess is that sysinstall checked the MBR partition table for sanity and decided to "fix" an overlap by arbitrarily deleting one of the overlapping partitions. That was the wrong thing to do since none of the overlapping partitions was involved in the FreeBSD installation. What other operating systems do with their slices is their business. Generating a warning message was plausible. Making gratuitous changes to the partition table was not. I believe it is common sense for an MBR partition table editor to change only those partitions that it is explicitly told to modify. Sysinstall was not told to modify either of the overlapping slices and should have left them strictly alone. Dan Strick ----- End forwarded message -----