Date: Mon, 20 Aug 2012 08:11:17 -0400 From: Jerry <jerry@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Issue with kernel building Message-ID: <20120820081117.7039e739@scorpio> In-Reply-To: <k0rtla$9n3$1@ger.gmane.org> References: <DUB109-W1405A43C7DAF2745B9971C4C4BA0@phx.gbl> <k0rtla$9n3$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 19 Aug 2012 19:43:14 -0400
Michael Powell articulated:
{snip}
> Keep in mind whenever you install a new kernel your present kernel
> (and its matching modules) get moved to kernel.old. What this means
> is that the GENERIC you have with a base install will be moved to
> kernel.old and can be used in the event the new kernel won't boot.
> Realize this: after the next rebuild process this kernel.old will be
> replaced _again_. In which case you might now have 2 broken kernels
> with not an easy way to recover.
I inquired several years ago about the possibility of changing the
renaming format into something like: "kernel_##_YY-MM-DD.old". The "##"
would be incremented with each successive build on a given day. I
thought it would alleviate just the sort of problem you are referring
to and would make it easier to revert to a specific kernel if required.
I never received even a single response so I guess it was not a well
received concept.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
“I believe if life gives you lemons make lemonade… then find someone
that life gave vodka to and have a party.”
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120820081117.7039e739>