Re: booting kernel.old uses /boot/modules, not modules.old
:
:If you try to install a module from e.g. /sys/dev/acpica5, the KLD goes
:to right under /boot, is this intended? $modules_path contains /boot,
:so KLDs installed that way should just work, but it also affects the
:traditional method:
:..
: $ cd /sys/config
: $ config -d /path/to/writable MYKERNEL
: $ make depend && make
: $ sudo make install
:
:This will install the kernel to /boot/kernel/kernel but all KLDs under /boot.
:This is because KLDs are now installed to ${DESTKERNDIR}, which defaults to
:/boot/${KERNEL}, but no .mk files included from within a module directory
:supplies the default value for ${KERNEL}.
No, that's a bug. It's supposed to install to a directory. Without
knowledge of which kernel the module is related to it winds up stuffing
it in /boot.
-Matt
Matthew Dillon
<dillon@backplane.com>
討論串 (同標題文章)
完整討論串 (本文為第 8 之 8 篇)：