Date: Tue, 11 Aug 2009 14:49:51 +0200 From: Nick Hibma <nick@van-laarhoven.org> To: freebsd-embedded@freebsd.org Cc: freebsd-current@freebsd.org, Paul Schenkeveld <fb-embedded@psconsult.nl> Subject: Re: [NanoBSD] Can't use boot0cfg for changing the booting slice Message-ID: <200908111449.51779.nick@van-laarhoven.org> In-Reply-To: <20090807205817.GA82868@psconsult.nl> References: <3131aa530908070809l2ac13931xf65981db6eeb83e8@mail.gmail.com> <20090807.104414.221852486.imp@bsdimp.com> <20090807205817.GA82868@psconsult.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> > : > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200908111449.51779.nick>