The modprobe command is used to load (or remove) modules from the kernel, and I’m wondering if it shouldn’t be insmod to load them. Then I looked them up and they are different, although both can be used to load modules to and from the intranet.

If modprobe makes an error during loading, it unloads the entire group of modules. modprobe looks for modules at /lib/modules/<uname -r>, but does not load the exclusions configured in /etc/modprobe.conf and /etc/modprobe.d/.

Of course, the modprobe dependency analysis is not done in a vacuum, but is generated by depmod.


The command ldconfig is used to find a DLL in a specified location and load it into system memory (kernel space or user space?). (No deeper). So, this command is usually run at system startup, so that after we upgrade or compile the new DLLs ourselves, we need to run ldconfig manually to get the new DLLs to take effect.

ldconfig finds the DLL in the following locations.

Some notes.