39fb794ebc
Currently there's more-or-less an assumption that a kernel is installed, so module blacklists are simply echoed into the modprobe blacklist. This may not be the case with some ongoing container work. Although we don't need to blacklist modules for containers, it also doesn't hurt. Move the debootstrap element to the new modprobe element, and allow it to create the blacklist directory. Change-Id: I0f057caf473951df56a2af9633e3a5b53e0809b1 |
||
---|---|---|
.. | ||
extra-data.d | ||
install.d | ||
README.rst |
======== modprobe ======== Allows to configure specific modprobe options on the image. It contains the following functionalities: 1. Ability to blacklist specific modules using modprobe.d/blacklist.conf. In order to use set DIB_MODPROBE_BLACKLIST to the name of your module. To disable multiple modules you can set DIB_MODPROBE_BLACKLIST to a list of string separated by spaces. Example: export DIB_MODPROBE_BLACKLIST="igb" 2. Ability to copy specific files into /etc/modprobe.d directory, so it allows to configure settings with freedom. To achieve that, the files to be copied needs to be placed inside an specific modprobe.d directory of the element.