Date: Sat, 28 May 2011 12:06:46 +0100 From: Chris Rees <utisoft@gmail.com> To: Julian Elischer <julian@freebsd.org> Cc: rank1seeker@gmail.com, hackers@freebsd.org Subject: Re: Active slice, only for a next boot Message-ID: <BANLkTinnZyGoi9RCZRX0JQNvBhHnQwEOSg@mail.gmail.com> In-Reply-To: <4DE0BA7C.8080707@freebsd.org> References: <20110527.124553.718.1@DEV> <20110527134754.GA94769@freebsd.org> <20110527.164723.750.2@DEV> <496B0C04-7777-458D-A116-27944A4006BB@bsdimp.com> <4DE0BA7C.8080707@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 May 2011 10:04, "Julian Elischer" <julian@freebsd.org> wrote: > > On 5/27/11 11:34 AM, Warner Losh wrote: >> >> On May 27, 2011, at 10:47 AM, rank1seeker@gmail.com wrote: >> >>> ----- Original Message ----- >>> From: Alexander Best<arundel@freebsd.org> >>> To: rank1seeker@gmail.com >>> Cc: hackers@freebsd.org >>> Date: Fri, 27 May 2011 13:47:54 +0000 >>> Subject: Re: Active slice, only for a next boot >>> >>>> On Fri May 27 11, rank1seeker@gmail.com wrote: >>>>> >>>>> Idea is ... >>>>> I have i.e; 3 slices, of which first is active. >>>>> Now I wana set slice 2 active, but only for a one/next boot. >>>>> Once slice 2 is booted and system is shutdown or rebooted, once again, >>> >>> first slice is active and booted, without user's intervention. >>>>> >>>>> Is this possible or should be implemented? > > > nextboot(8) USED to do this before it was broken by someone to "look into the filesystem" > for it's next boot hint which is obviously broken if you are trying to get to another filesystem > because the main one is broken. > Doesn't sound that useful to me- I think of the main use for nextboot being to try new kernels on a one-time basis. If you're rescuing a broken filesystem surely it's better to just set another slice active? Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinnZyGoi9RCZRX0JQNvBhHnQwEOSg>