Date: Sat, 13 Aug 2011 20:58:32 +0100 From: Chris Rees <crees@freebsd.org> To: Alexander Best <arundel@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: [rfc] replacing /boot/kernel.old with a unique directory name Message-ID: <CADLo83_NqbWrGcGT6R0PG8_kxRtxyR4hJoTqBiuu2i2gKT1URQ@mail.gmail.com> In-Reply-To: <20110813195127.GA34295@freebsd.org> References: <20110813195127.GA34295@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 August 2011 20:51, Alexander Best <arundel@freebsd.org> wrote:
> hi there,
>
> i just had the following idea: how about instead of copying the current kernel
> to /boot/kernel.old and then installing the new one under /boot/kernel as the
> results of target installkernel, we create a unique directory name for the old
> kernel?
>
> something like /boot/kernel-r${revision}-${/dev/random}?
>
> that would let people not only boot the previous kernel, but all kernels that
> have been replaced by target installkernel. this would make tracking issues,
> which have been introduced by a certain commit much easier, imho.
>
> i don't think implementing this logic would be that difficult. the only problem
> i see is with ${/dev/random} in the case where people are running a kernel
> without /dev/{u}random support.
>
> cheers.
> alex
mktemp?
Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_NqbWrGcGT6R0PG8_kxRtxyR4hJoTqBiuu2i2gKT1URQ>