Date: Sat, 13 Aug 2011 13:10:50 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Alexander Best <arundel@freebsd.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: [rfc] replacing /boot/kernel.old with a unique directory name Message-ID: <22EB0C13-A184-446F-A031-A2817CB3BE7D@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 Aug 13, 2011, at 12:51 PM, Alexander Best <arundel@freebsd.org> wrote:
> hi there,
>=20
> i just had the following idea: how about instead of copying the current ke=
rnel
> to /boot/kernel.old and then installing the new one under /boot/kernel as t=
he
> results of target installkernel, we create a unique directory name for the=
old
> kernel?
>=20
> something like /boot/kernel-r${revision}-${/dev/random}?
>=20
> that would let people not only boot the previous kernel, but all kernels t=
hat
> have been replaced by target installkernel. this would make tracking issue=
s,
> which have been introduced by a certain commit much easier, imho.
>=20
> i don't think implementing this logic would be that difficult. the only pr=
oblem
> i see is with ${/dev/random} in the case where people are running a kernel=
> without /dev/{u}random support.
Why not just use INSTKERNNAME?
-Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22EB0C13-A184-446F-A031-A2817CB3BE7D>