site
contact
newsModule-loading options fixed
The BootManager, /usr/sbin/bootmanager, which is in all pups
going back many years, has three options for choosing which modules to
load at bootup. There is "blacklist", "add" and "preference".
The "blacklist" option manages a list of modules that are
blacklisted, that is, will not be loaded. This list is in variable
'SKIPLIST' in file /etc/rc.d/MODULESCONFIG, which is written to
/etc/modprobe.d/blacklist.conf by /etc/rc.d/rc.sysinit at bootup.
One qualification though, a blacklisted module can still be loaded
manually, using the 'modprobe' utility, and will also be loaded if it is
a dependency of another module that is loaded. Note, if you want to
absolutely blacklist a module, including the above two, a line like
this in a .conf file will do it: "install <module name>
/bin/false"
The "add" option is a list of modules that will be loaded, that would
not have done so automatically. This is variable 'ADDLIST' in
/etc/rc.d/MODULESCONFIG, and they are loaded by /etc/rc.d/rc.sysinit
The "preference" option is to give one module preference over
another, in the situation where two (or more) are contenders for the
same hardware. This was variable 'PREFLIST' in
/etc/rc.d/MODULESCONFIG, and was loaded by 'pup_event_backend_modprobe'.
However, this script has been removed, see earlier blog post:
http://bkhome.org/news/201802/revisiting-pupevent-first-changes.html
Also, variable 'PCI_OVERRIDES' is no longer supported, now removed. The "preference" option is removed from BootManager.
It's ok, the "preference" option is redundant anyway, blacklisting suffices.