Date: Sat, 13 Aug 2011 20:15:20 +0000 From: Alexander Best <arundel@freebsd.org> To: Garrett Cooper <yanegomi@gmail.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: [rfc] replacing /boot/kernel.old with a unique directory name Message-ID: <20110813201520.GA37846@freebsd.org> In-Reply-To: <22EB0C13-A184-446F-A031-A2817CB3BE7D@gmail.com> References: <20110813195127.GA34295@freebsd.org> <22EB0C13-A184-446F-A031-A2817CB3BE7D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat Aug 13 11, Garrett Cooper wrote: > On Aug 13, 2011, at 12:51 PM, Alexander Best <arundel@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? > -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110813201520.GA37846>