From owner-freebsd-qa@FreeBSD.ORG Sun Jun 25 09:30:26 2006 Return-Path: X-Original-To: freebsd-qa@hub.freebsd.org Delivered-To: freebsd-qa@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B5E916A405 for ; Sun, 25 Jun 2006 09:30:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 517DC43D5C for ; Sun, 25 Jun 2006 09:30:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5P9UO2o042031 for ; Sun, 25 Jun 2006 09:30:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5P9UO1W042030; Sun, 25 Jun 2006 09:30:24 GMT (envelope-from gnats) Date: Sun, 25 Jun 2006 09:30:24 GMT Message-Id: <200606250930.k5P9UO1W042030@freefall.freebsd.org> To: freebsd-qa@FreeBSD.org From: Heiner Cc: Subject: Re: bin/48341: [sysinstall] sysinstall deletes mbr although it X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Heiner List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jun 2006 09:30:26 -0000 The following reply was made to PR bin/48341; it has been noted by GNATS. From: Heiner To: John Baldwin , bug-followup@freebsd.org, h.eichmann@gmx.de Cc: Subject: Re: bin/48341: [sysinstall] sysinstall deletes mbr although it Date: Sun, 25 Jun 2006 11:26:58 +0200 On Monday 19 June 2006 21:18, John Baldwin wrote: > Please fix your mail server to actually honor what SPF says if you want > people to reply to your questions. The SPF record for FreeBSD.org is not > exclusive. Sorry, my mail provider seems to be black listed sometimes. Can't do anything against it ... > Hmm, this is because the menu is not about leaving the MBR completely > untouched (we couldn't add new slices if we did that!) but instead about > leaving the boot code in the MBR untouched. Note that the Active flag > isn't stored in the boot code, but in the partition table. When you > create the FreeBSD slice in the MBR during installation, it will have > the Active flag set. You can manually reset the Active flag on the That is right. But what are the options? Either I do not have a bootloader installed. Then "standard" is the correct choice. Or I have other OS installed and I would like to let the BSD boot manager handle it. Then "BootMgr" is a good choice. Or I would like let my favorite boot manager do the job. Then "None" is my choice. Unfortunately my favorite boot manager will not boot, as the active flag has been changed! I can not think on any situation, where this behaviour might be usefull! > Windows partition before exiting that stage of the disk editor and > things should work as expected. Would you be able to try that out and > verify that? I did. During the fdisk "Allocating Disk Space" of the installation I selected the windows partition and pressed 'S'. After the installation the windows partition was still active. So this is a good workaround. Heiner