Loading kernel modules with systemd or modprobe?
by berndbausch from LinuxQuestions.org on (#4T7JY)
I don't want this to become a systemd flamefest and am not interested in opinions about the general merits or downsides of systemd.
I can persist the loading of kernel modules with files in /etc/modprobe.d. Alternatively, I can ask systemd to take care of module loading. One downside of the systemd approach seems to be that it doesn't allow setting module parameters.
So my question is: What is the benefit of systemd-modules-load.servicecompared to the traditional approach of adding modules to the modprobe config directory?
I can persist the loading of kernel modules with files in /etc/modprobe.d. Alternatively, I can ask systemd to take care of module loading. One downside of the systemd approach seems to be that it doesn't allow setting module parameters.
So my question is: What is the benefit of systemd-modules-load.servicecompared to the traditional approach of adding modules to the modprobe config directory?