On Aug 13, 2011, at 1:15 PM, Alexander Best <arundel_at_freebsd.org> wrote: > On Sat Aug 13 11, Garrett Cooper wrote: >> On Aug 13, 2011, at 12:51 PM, Alexander Best <arundel_at_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. >> >> Why not just use INSTKERNNAME? > > 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 when working with svn and multiple KERNCONFs. -GarrettReceived on Sat Aug 13 2011 - 18:30:36 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:16 UTC