Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 May 2005 11:26:17 -0500
From:      "Conrad J. Sabatier" <conrads@cox.net>
To:        des@des.no (Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?=)
Cc:        =?ISO-8859-1?Q?S?= =?ISO-8859-1?Q?=F8ren?= Schmidt <sos@freebsd.org>
Subject:   Re: cvs commit: src/sys/dev/ata ata-queue.c
Message-ID:  <20050512112617.482321e9@dolphin.local.net>
In-Reply-To: <86wtq47j97.fsf@xps.des.no>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 May 2005 13:53:40 +0200, des@des.no (Dag-Erling Sm=F8rgrav)
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).
>=20
> 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.

--=20
Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050512112617.482321e9>