From owner-freebsd-questions@FreeBSD.ORG Sat Nov 3 16:54:31 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7838D90 for ; Sat, 3 Nov 2012 16:54:31 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3FDAD8FC0A for ; Sat, 3 Nov 2012 16:54:30 +0000 (UTC) Received: from mail1.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.13.6/8.13.6) with ESMTP id qA3GsLPS019663 for ; Sat, 3 Nov 2012 17:54:22 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail1.siemens.de (8.13.6/8.13.6) with ESMTP id qA3GsLro000548 for ; Sat, 3 Nov 2012 17:54:21 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.5/8.14.5) id qA3GsLPl014726; Date: Sat, 3 Nov 2012 17:54:21 +0100 From: Andre Albsmeier To: freebsd-questions@freebsd.org Subject: Booting 2nd(!) FreeBSD installation sitting on same disk Message-ID: <20121103165421.GA76199@bali> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2012 16:54:32 -0000 For various reasons I have to use this disk layout: One harddisk with MBR and 3 slices on a i386 box: Slice 1: Windows XP :-( Slice 2: FreeBSD 7.4-STABLE V1 Slice 3: FreeBSD 7.4-STABLE V2 The MBR is configured as: options=packet,noupdate,nosetdrv default_selection=F2 (Slice 2) When booting, I can choose between: F1 Win F2 FreeBSD F3 FreeBSD However, when pressing F3, the system of slice 2(!) is loaded. This is due to the fact that boot1 always loads the first active FreeBSD slice ;-(. I have two possibilities to actually boot slice 3: 1. Playing with currdev when loader(8) is loaded (or using loader.conf of slice 2). 2. Using boot0cfg to allow updating the MBR. 1. is not really fexible and 2. means that the system remembers which slice was booted last (something I do not want). Is there no chance to actually honour the fact that F3 was pressed and boot from slice 3 without updating the MBR before? Thanks, -Andre