Active slice, only for a next boot
crees at freebsd.org
Mon Mar 26 21:28:39 UTC 2012
On 26 March 2012 18:10, <rank1seeker at gmail.com> wrote:
> ----- Original Message -----
> From: John Baldwin <jhb at freebsd.org>
> To: freebsd-hackers at freebsd.org
> Cc: rank1seeker at gmail.com, hackers at 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 at 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).
> # '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.
I'm afraid this sounds like a great way to make a very confusing
scenario, where you have to reboot twice to be sure of a consistent
boot sector, unless I've misunderstood you.
More information about the freebsd-hackers