module_path

[Wilkinson, Alex]

/usr/src/UPDATING:


20040806:
        Module loading has been fixed.  Some older installations will
        drop proper module_path initialization and modules will fail to
        load properly.  If you have a line in /boot/loader.rc that says:
        "initialize drop", do (i386 only):
                cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
                chown root:wheel /boot/loader.rc
                chmod 444 /boot/loader.rc


 - aW


0n Mon, Nov 22, 2004 at 06:41:00PM -0800, Gustavo A. Baratto wrote: 

> hello there,
> 
> Since I have seen it in the errata, here it goes:
> 
> I have upgraded from 5.1 to 5.3, and the newly installed 
> /boot/defaults/loader.conf has this set:
> module_path="/boot/modules"
> 
> so, whenever I try to load ipfw or ipf, or even use kldload, I get this 
> error:
> ---
> /etc/rc.d/ipfw start
> kldload: can't load ipfw: No such file or directory
> /etc/rc.d/ipfw: WARNING: unable to load firewall module.
> ---
> 
> # sysctl kern.module_path
> kern.module_path: /boot/modules
> 
> I know that I can override that by adding module_path="/boot/kernel" in 
> /boot/loader.conf, but I think the default file should be fixed to add at 
> least /boot/kernel, right?
> 
> cheers 
> 
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>