Linux admin notes - kernel modules

Linux-related notes Linux user notes Shell, admin, and both: Shell - command line and bash notes · shell login - profiles and scripts ·· find and xargs and parallel · screen and tmux ·· Shell and process nitty gritty ·· Isolating shell environments ·· Shell flow control notes Linux admin - disk and filesystem · Linux networking · Init systems and service management (upstart notes, systemd notes) · users and permissions · Debugging · security enhanced linux · PAM notes · health and statistics · Machine Check Events · kernel modules · YP notes · unsorted and muck · Automounters and permissions Logging and graphing - Logging · RRDtool and munin notes Network admin - Firewalling and other packet stuff · Remote desktops - XDMCP notes

Modules are can be used as kernel code, loaded and unloaded at runtime.

Ideally you'll never have to deal with them in general admin; if they're necessary and present they will often be loaded automatically.

Some people who compile kernels prefer to compile any and all drivers as modules instead of baking them into the kernel, so that you can reload and replace them without rebooting.

See also

• https://wiki.archlinux.org/index.php/Kernel_modules

DKMS

Dynamic Kernel Module Support generates kernel modules from sources outside the kernel tree.

...but is transparent to you.

For example, if you install something that relies on a kernel module (e.g. ZFS, NVidia drivers), it will build the modules for you.

When you install a new module, it will compile all currently installed kernel modules for it