cvs commit: src/sys/boot/common help.common src/sys/boot/forth loader.conf

[Giorgos Keramidas]

On 2004-08-09 10:38, John-Mark Gurney <gurney_j at resnet.uoregon.edu> wrote:
> Pawel Jakub Dawidek wrote this message on Mon, Aug 09, 2004 at 14:41 +0200:
> > If kernel name is given for the 'boot' command, '/boot/<kernname>' path is
> > probably added to kern.module_path, but for normal boot process it is not,
> > so kern.module_path is set only to "/boot/modules".
> > Some applications depend on this sysctl and they don't work properly now.
> > Please fix.
>
> Have you verified this is a problem?  On my test box that has:
> defaults/loader.conf:module_path="/boot/modules"        # Set the module search path
>
> and was booted:
> [...]
> /boot/kernel/accf_http.ko text=0xb84 data=0x150+0x4 syms=[0x4+0x310+0x4+0x334]
>
> 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?

- Giorgos