Date: Mon, 26 Mar 2012 20:10:50 +0200 From: rank1seeker@gmail.com To: "John Baldwin" <jhb@freebsd.org>, hackers@freebsd.org Subject: Re: Active slice, only for a next boot Message-ID: <20120326.181050.391.3@DOMY-PC> In-Reply-To: <201203261018.53717.jhb@freebsd.org> References: <20120325.184917.751.1@DOMY-PC> <201203261018.53717.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: John Baldwin <jhb@freebsd.org>
To: freebsd-hackers@freebsd.org
Cc: rank1seeker@gmail.com, hackers@freebsd.org
Date: Mon, 26 Mar 2012 10:18:53 -0400
Subject: Re: Active slice, only for a next boot
> On Sunday, March 25, 2012 2:49:17 pm rank1seeker@gmail.com wrote:
> > After having a thought about this issue and also currently looking at a
> BootEasy boot manager ...
> > 'boot0cfg' is almost perfect for this task and should/could be "exploited".
> >
> > It's '-o noupdate' already does a major task, of keeping main slice active.
> > Now all we need is a flag, through which we specify slice to boot (replacing
> human presing button).
> > From that point on, existing code simply proceeds with received value.
> >
> > '-o noupdate' ensures next boot will bring up main/active slice.
>
> You mean like 'boot0cfg -s 4'?
>
> --
> John Baldwin
>
Yes, but new flag for that purpose ('-n' for example => nextboot).
I.e;
# 'boot0cfg -s 4 -o noupdate -n 3'
Would, set the default/main boot selection to slice 4 and '-o noupdate' ensures it remains that way, while '-n 3' would auto press/choose slice 3 in selection menu, as human would.
Well in that case, better to not show menu at all, thus only "blic" into slice 3.
At next boot it is at slice 4 again.
Domagoj Smolčić
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120326.181050.391.3>