What is "kernel module" loading (e.g. via "insmod" or "modprobe"), and how does "modprobe" differ from "insmod"?
Correct! Well done.
Incorrect.
The correct answer is A) Kernel modules are code loaded into the running kernel to add functionality, like drivers, without rebooting; "insmod" loads a module directly without resolving dependencies, while "modprobe" resolves and loads dependents first via a dependency database
Correct Answer
Kernel modules are code loaded into the running kernel to add functionality, like drivers, without rebooting; "insmod" loads a module directly without resolving dependencies, while "modprobe" resolves and loads dependents first via a dependency database
"modprobe" is generally preferred over "insmod" because it automatically handles module dependencies (loading prerequisite modules first) using data generated by "depmod", reducing the chance of a module failing to load due to missing dependencies.