Package: module-init-tools Version: 3.3-pre11-1 Severity: normal If you look up "module blacklist" or "modprobe blacklist" or "udev blacklist" in google, the results are various and mostly wrong, outdated, or distro-specific.
modprobe.conf(5)'s docuentation of the blacklist command is ok, but still leaves open the question of how to really blacklist a module so modprobe won't load it at all. Expecting a regular user to read the documentation of the install command and think of "install module /bin/true" as the way to turn off loading of a module is probably expecting too much of many users. It's even expecting too much of some developers; I did not make this connection on my first or second reading of the man page, and did not think of it until I saw it mentioned on the web[1]. Since module-init-tools has a FAQ, I thought it might help to document how to blacklist a module there. Something like: Q) How do I prevent udev or modprobe from loading a module? A) Putting this in a file in /etc/modprobe.d/ will guarantee that modprobe never loads a module (in this case the PC speaker driver), but it not necessarily the best approach in all circumstances: install pcspkr /bin/true If there are two modules that can both support the same device, and the wrong module is being used, the above won't help; it will prevent the wrong module from being loaded, but will not load the correct module. In this case, you should instead use the blacklist command: blacklist eepro100 This will prevent the older eepro100 module from being used, and allow the newer e100 module to be loaded instead. See the modprobe.conf(5) man page for details. If you add this you might also want to add a pointer to it to /etc/modprobe.d/blacklist -- see shy jo [1] http://www.beranger.org/index.php?page=3k&fullarticle=2256 Currently the 20th hit for "udev blacklist"
signature.asc
Description: Digital signature
