From owner-freebsd-current@FreeBSD.ORG Tue Aug 11 13:05:35 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0C0D1065675; Tue, 11 Aug 2009 13:05:35 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from baranao.anywi.com (baranao.anywi.com [213.207.101.176]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4E58FC20; Tue, 11 Aug 2009 13:05:35 +0000 (UTC) Received: from hind.van-laarhoven.org (ip51cfcfde.direct-adsl.nl [81.207.207.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by baranao.anywi.com (Postfix) with ESMTPSA id 9858A3F41C; Tue, 11 Aug 2009 14:49:57 +0200 (CEST) From: Nick Hibma To: freebsd-embedded@freebsd.org Date: Tue, 11 Aug 2009 14:49:51 +0200 User-Agent: KMail/1.11.4 (FreeBSD/7.2-STABLE; KDE/4.2.4; i386; ; ) References: <3131aa530908070809l2ac13931xf65981db6eeb83e8@mail.gmail.com> <20090807.104414.221852486.imp@bsdimp.com> <20090807205817.GA82868@psconsult.nl> In-Reply-To: <20090807205817.GA82868@psconsult.nl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908111449.51779.nick@van-laarhoven.org> X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,J_CHICKENPOX_43, UNPARSEABLE_RELAY autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on baranao.anywi.com Cc: freebsd-current@freebsd.org, Paul Schenkeveld Subject: Re: [NanoBSD] Can't use boot0cfg for changing the booting slice X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 13:05:36 -0000 > > : > But, after the reboot my system still reboot from the slice 1 (but > > : > the boot loader show correctly that the default choice is now the > > : > 2)! Where is my problem ? > > : > > : Are you sure you're booting from slice 1? > > : Is fstab on slice 2 pointing to slice 1? > > > > Also, boot0cfg won't mark the slice as ACTIVE, just remember that was > > the last slice you booted from... To mark it active, you must use > > fdisk. If by 'active' you mean 'what mount reports root as' then I > > think John's suggestion is right on the money... Perhaps you could change the line in the update script from boot0cfg -s $oslice $NANO_DRIVE to boot0cfg -s $oslice $NANO_DRIVE echo "a $oslice" | fdisk -f /dev/stdin $NANO_DRIVE That's taken from our own version of the update script, but should fit in the NanoBSD update script. Nick