Date: Mon, 9 Aug 2004 10:56:59 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/boot/common help.common src/sys/boot/forth loader.conf Message-ID: <20040809175658.GH991@funkthat.com> In-Reply-To: <20040809174927.GA20807@orion.daedalusnetworks.priv> References: <200408061506.i76F66sl018247@repoman.freebsd.org> <20040809124153.GN628@darkness.comp.waw.pl> <20040809173814.GG991@funkthat.com> <20040809174927.GA20807@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
Giorgos Keramidas wrote this message on Mon, Aug 09, 2004 at 20:49 +0300:
> > Hit [Enter] to boot immediately, or any other key for command prompt.
> > Booting [/boot/kernel/kernel]...
>
> I don't know if this is related, but...
>
> I've also noticed that /boot/kernel is added twice at module_path.
> My boot loader-foo is non-existent but it always seemed sufficient
> to just use:
>
> set module_path=/boot/kernel.old
> set bootfile=/boot/kernel.old/kernel
>
> to recover from broken/buggy kernel builds, so I never asked.
>
> Does this mean that now module_path will include the current kernel path
> only once?
Yes, my commit fixes the problem of /boot/kernel being added twice (or
/boot/kernel being added even though you didn't load that kernel). Just
update your /boot/defaults/loader.conf, and you should then be able to
remove your hacked module_path line.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040809175658.GH991>