Date: Sun, 15 May 2005 08:33:49 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: "Conrad J. Sabatier" <conrads@cox.net> Cc: S?ren Schmidt <sos@freebsd.org> Subject: Re: cvs commit: src/sys/dev/ata ata-queue.c Message-ID: <20050515053349.GA32205@gothmog.gr> In-Reply-To: <20050512112617.482321e9@dolphin.local.net> References: <200505111436.j4BEaQWP077515@repoman.freebsd.org> <20050511145558.7e030a62@dolphin.local.net> <42828A49.8000008@DeepCore.dk> <20050511231001.1ba1e2e3@dolphin.local.net> <86wtq47j97.fsf@xps.des.no> <20050512112617.482321e9@dolphin.local.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-05-12 11:26, "Conrad J. Sabatier" <conrads@cox.net> wrote: >On Thu, 12 May 2005 13:53:40 +0200, des@des.no (Dag-Erling Sm?rgrav) >wrote: >>"Conrad J. Sabatier" <conrads@cox.net> writes: >>> Small problem: my last good kernel got overwritten. Strange, but >>> one "make installkernel" did *not* move /boot/kernel to >>> /boot/kernel.old (I had previously manually moved /boot/kernel.old >>> to /boot/kernel after discovering that the new kernel wasn't working >>> properly, then the next installkernel failed to move it back to >>> kernel.old, for some reason). >> >> because your kern.bootfile still pointed at kernel.old. the makefiles >> only move kernel to kernel.old if it's the currently running kernel, >> iirc. you should always update kern.bootfile when you move or rename >> your currently running kernel, both for this reason and to get the >> module path right. > > A-ha! Thanks! I never knew that before. A probably "safer" way to keep known good kernels around is to copy them over to something that is neither kernel.old nor kernel. I usually keep a copy of a known good kernel in /boot/kernel.ok :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050515053349.GA32205>