Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There is how the book I'm reading describe the insmod utility:

The program loads the module code and data into the kernel, which, in turn, performs a function similar to that of ld, in that it links any unresolved symbol in the module to the symbol table of the kernel. Unlike the linker, however, the kernel doesn’t modify the module’s disk file, but rather an in-memory copy.

It looks like it won't persist since it's in-memory, but I'm not sure.

share|improve this question

No, they won't. After rebooting, you begin from scratch.

Normally, for modules that you want loaded after every reboot, there's a configuration file listing modules to be auto-loaded at boot time.

Look at /etc/modules.

man modules:

   /etc/modules - kernel modules to load at boot time

   The  /etc/modules file contains the names of kernel modules that are to
   be loaded at boot time, one per line. Arguments can  be  given  in  the
   same line as the module name. Lines beginning with a '#' are ignored.
share|improve this answer

Modules manually loaded using insmod do not persist when your system is rebooted (for that behavior see the manpage for modules.confmodules, which essentially runs insmod automatically on reboot, but with a bit more intelligence).

ed: modules, not modules.conf (the latter is useful if you're writing a custom module with dependencies)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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