modprobe to load the
8021q.ko module on a server. I expected to have to do this every time the server rebooted until I made it persistent. However, to my surprise, it was loaded automatically when I rebooted.
I was not convinced this was going to happen on every reboot so I started looking at just how to make it persistent. In my searches I found docs stating that each module needed an
/etc/sysconfig/modules/<module_name>.module file with the appropriate config options. My assumption was that if it was made persistent, then the
modprobe command must have added the file for me. It wasn't there, though.
Then, through a little more searching I found this in the CentOS 5 documentation:
This approach is not necessary for network and SCSI interfaces because they have their own specific mechanisms.
I'm dealing with RHEL 6 but it appears to still be relevant even though the general module loading mechanism has changed a little (
/etc/sysconfig/modules/<module_name>.module on RHEL/CentOS 6 vs
/etc/modprobe.conf on RHEL/CentOS 5).
So now I'm left wondering what those specific network and SCSI mechanisms are. Where do I look to see and ensure that modules are loading persistently?