Date: Sat, 13 Aug 2011 13:30:18 -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: <F72BB06A-FFCC-4364-A18B-4C94BA16DE22@gmail.com> In-Reply-To: <20110813201520.GA37846@freebsd.org> References: <20110813195127.GA34295@freebsd.org> <22EB0C13-A184-446F-A031-A2817CB3BE7D@gmail.com> <20110813201520.GA37846@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 13, 2011, at 1:15 PM, Alexander Best <arundel@freebsd.org> wrote:
> On Sat Aug 13 11, Garrett Cooper wrote:
>> On Aug 13, 2011, at 12:51 PM, Alexander Best <arundel@freebsd.org> wrote:=
>>=20
>>> hi there,
>>>=20
>>> i just had the following idea: how about instead of copying the current k=
ernel
>>> to /boot/kernel.old and then installing the new one under /boot/kernel a=
s the
>>> results of target installkernel, we create a unique directory name for t=
he 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=
that
>>> have been replaced by target installkernel. this would make tracking iss=
ues,
>>> 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 p=
roblem
>>> i see is with ${/dev/random} in the case where people are running a kern=
el
>>> without /dev/{u}random support.
>>=20
>> Why not just use INSTKERNNAME?
>=20
> hmm...won't setting INSTKERNNAME set the path to where the new kernel will=
be
> installed and not where the current kernel will be backup'ed?
It moves the old kernel to $INSTKERNNAME.old . That's usually good enough wh=
en working with svn and multiple KERNCONFs.
-Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F72BB06A-FFCC-4364-A18B-4C94BA16DE22>