I red the introduction of them and found that, they both deal with module loading during boot time.

So, what's the difference of these two different configuation ways?


Distributions which use SysV init scripts where systemd is not available used to load modules on init listed in /etc/modules or /etc/modules.conf (from the kmod job).
In distributions where systemd is available systemd-modules-load.service reads files from:

  • /etc/modules-load.d/*.conf
  • /run/modules-load.d/*.conf
  • /usr/lib/modules-load.d/*.conf

to load kernel modules during boot in a static list.

  • In Ubuntu doc, as said, Ubuntu uses /etc/modules to config loadable modules. And it didn't mention the /etc/modules.conf file. Is the doc out-dated or that's the way Ubuntu uses? – nn0p Mar 12 '15 at 10:24
  • Different distributions use different way to implement this. In Ubuntu this is /etc/modules. – taliezin Mar 12 '15 at 10:42
  • @nn0p so in basic there is no difference. Just in the way how it is handled. – taliezin Mar 12 '15 at 11:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.