Date: Sun, 14 Oct 2001 16:19:58 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: "Gary W. Swearingen" <swear@blarg.net> Cc: Mike Meyer <mwm@mired.org>, questions@FreeBSD.ORG Subject: Re: cvsup Message-ID: <20011014161958.E309@blossom.cjclark.org> In-Reply-To: <6tzo6tnb66.o6t@localhost.localdomain>; from swear@blarg.net on Sun, Oct 14, 2001 at 02:50:41PM -0700 References: <15304.58886.215474.233433@guru.mired.org> <s6r8s6rhfy.8s6@localhost.localdomain> <15305.46606.130325.710925@guru.mired.org> <6tzo6tnb66.o6t@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 14, 2001 at 02:50:41PM -0700, Gary W. Swearingen wrote:
> Mike Meyer <mwm@mired.org> writes:
>
> > The two build processes don't touch the the running system in any
> > way. installkernel already saves the old kernel and modules as
> > kernel.old and modules.old.
>
> Which reminds me of something else I wondered about. When I select an
> old kernel from the boot prompt, shouldn't I do something to select
> the old modules to go with it? It seems I'd have to use the "load"
> boot command to load each and every module I need or will need, since
> the old kernel doesn't know where to find the old modules. Or does it?
> I don't recall reading about that.
You can set the path to the modules at the boot prompt with the
'module_path' variable.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011014161958.E309>