From owner-freebsd-stable@FreeBSD.ORG Sat Apr 3 21:44:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 670B4106566C for ; Sat, 3 Apr 2010 21:44:51 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 21E268FC12 for ; Sat, 3 Apr 2010 21:44:50 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o33LioeL011953; Sat, 3 Apr 2010 15:44:50 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o33Liobf011950; Sat, 3 Apr 2010 15:44:50 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 3 Apr 2010 15:44:50 -0600 (MDT) From: Warren Block To: Jeremy Chadwick In-Reply-To: <20100403205856.GA20454@icarus.home.lan> Message-ID: References: <20100403174812.59c40c99.matheus@eternamente.info> <20100403205856.GA20454@icarus.home.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Sat, 03 Apr 2010 15:44:50 -0600 (MDT) Cc: freebsd-stable@freebsd.org Subject: Re: install touching mbr X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Apr 2010 21:44:51 -0000 On Sat, 3 Apr 2010, Jeremy Chadwick wrote: > On Sat, Apr 03, 2010 at 05:48:12PM -0300, Nenhum_de_Nos wrote: >> I just installed a 8.0R amd64 from memstick. when asked, I said to >> leave mbr untouched. when I rebooted, it was freebsd bootloader that >> was on control. this options is not what I think it should, or there >> is really a issue here ? > > I can confirm this behaviour. Someone may have broken something when > tinkering around in that part of sysinstall (since the Standard vs. > BootMgr options were moved around compared to previous releases). Not sure how to repeat the bug, but it's been there at least a few months: http://docs.freebsd.org/cgi/mid.cgi?alpine.BSF.2.00.0909262030060.13303 http://docs.freebsd.org/cgi/mid.cgi?58c737d70909262054k7c7b1402w4f9c902fdca2640c -Warren Block * Rapid City, South Dakota USA