Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Mar 2012 21:28:07 +0000
From:      Chris Rees <crees@freebsd.org>
To:        rank1seeker@gmail.com
Cc:        hackers@freebsd.org
Subject:   Re: Active slice, only for a next boot
Message-ID:  <CADLo838yKmA7BH8pngnPUTHVBK=c0K5Cq6ZjgPNnEETto6opsQ@mail.gmail.com>
In-Reply-To: <20120326.181050.391.3@DOMY-PC>
References:  <20120325.184917.751.1@DOMY-PC> <201203261018.53717.jhb@freebsd.org> <20120326.181050.391.3@DOMY-PC>

next in thread | previous in thread | raw e-mail | index | archive | help
On 26 March 2012 18:10,  <rank1seeker@gmail.com> wrote:
> ----- 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 "exploi=
ted".
>> >
>> > It's '-o noupdate' already does a major task, of keeping main slice ac=
tive.
>> > Now all we need is a flag, through which we specify slice to boot (rep=
lacing
>> 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 =3D> nextboot).
>
> I.e;
> =A0 =A0# 'boot0cfg -s 4 -o noupdate -n 3'
>
> Would, set the default/main boot selection to slice 4 and =A0'-o noupdate=
' =A0ensures it remains that way, while '-n 3' would auto press/choose slic=
e 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.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838yKmA7BH8pngnPUTHVBK=c0K5Cq6ZjgPNnEETto6opsQ>