Re: [rfc] replacing /boot/kernel.old with a unique directory name

On Aug 13, 2011, at 1:15 PM, Alexander Best <[e-mail]> wrote:

> On Sat Aug 13 11, Garrett Cooper wrote:
>> On Aug 13, 2011, at 12:51 PM, Alexander Best <[e-mail]> 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=
_______________________________________________
[e-mail] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[e-mail]"