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

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