From owner-freebsd-embedded@FreeBSD.ORG Wed May 13 14:27:31 2009 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BE97106566B for ; Wed, 13 May 2009 14:27:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id F13768FC08 for ; Wed, 13 May 2009 14:27:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A5FEC46B0C; Wed, 13 May 2009 10:27:30 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 7B8C98A028; Wed, 13 May 2009 10:27:29 -0400 (EDT) From: John Baldwin To: freebsd-embedded@freebsd.org Date: Wed, 13 May 2009 10:03:16 -0400 User-Agent: KMail/1.9.7 References: <200904201535.21191.nick@van-laarhoven.org> <200905121445.27090.jhb@freebsd.org> <20090512221342.GA9393@psconsult.nl> In-Reply-To: <20090512221342.GA9393@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905131003.16938.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 13 May 2009 10:27:29 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Subject: Re: nanobsd boot slice selection does not work X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 14:27:31 -0000 On Tuesday 12 May 2009 6:13:42 pm Paul Schenkeveld wrote: > During reboot, boot0 suggests that slice 2 is default: > > 1 Seconds to automatic boot. Press Ctrl-P for entering Monitor. > > 1 FreeBSD > 2 FreeBSD > 5 Drive 1 > > Boot: 2 > > It looks like the kernel on ad0s1a gets loaded however. To be sure I > upgraded the kernel on ad0s2a with a newer one, still the same behaviour. Can you do boot0cfg -v after you have rebooted in this case? I want to see if the active flag is set to slice 2. > To summarize 7.2 boot0 behaviour: > > - Pressing [F]1 or [F]2 at the boot0 prompt selects slice 1 or 2 and > boots off that slice. If the update option is on, default_selection > is set in sector0, the active flage is set on the requested slice > and cleared from the other slice. Ok, so pressing the key always works? > - Boot0cfg -s N sets default_selection to N and does not affect the > active flag in MBR record. Right, the way this works at least in <= 7.1 is that boot0 changes the active flag based on 'default_selection' and then writes the new MBR back out to disk. > - Boot0 does not look at default_selection at all, the slice marked > active is booted, if no slice is marked active, slice 1 is booted. Well, boot1 does not look at default_selection at all. I think boot0 is still honoring it, but what happens is that boot0 loads boot1 from slice 2, but that boot1 doesn't find the active flag set, so it uses the first FreeBSD slice (slice 1) to load boot2, the loader, and the kernel. -- John Baldwin