In Bug 490988 it was requested to add a config file to modules-load.d when installing virtualbox-modules so that the modules get autoloaded on system start. Can we maybe hide this behind a USE flag? For example "systemd" as, if I understand 490988 correctly the config was meant for systemd – I'm on OpenRC, those modules are getting auto loaded for me and I'd like to remove this functionality from my system. Reproducible: Always Steps to Reproduce: 1. Install virtualbox-modules 2. Restart the system 3. Check lsmod output
The config is meant to load the modules for both systemd & openrc systems. Most people who install virtualbox-modules do want them autoloaded. If you do not, then you should place an empty file with the same filename into /etc/modules-load.d/ .
A bit of a hack, would prefer a USE flag to control that file (like symlink for the kernel sources), but I'll take it. Thanks for quick response.
But this isn't a hack, this is how modules-load.d is supposed to work. Similar to how udev rules.d works. FYI: CONFIGURATION DIRECTORIES AND PRECEDENCE Configuration files are read from directories in /etc/, /run/, and /usr/lib/, in order of precedence. Each configuration file in these configuration directories shall be named in the style of filename.conf. Files in /etc/ override files with the same name in /run/ and /usr/lib/. Files in /run/ override files with the same name in /usr/lib/. Packages should install their configuration files in /usr/lib/. Files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. It is recommended to prefix all filenames with a two-digit number and a dash, to simplify the ordering of the files. If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in the configuration directory in /etc/, with the same filename as the vendor configuration file. If the vendor configuration file is included in the initrd image, the image has to be regenerated.
