moduleload

Moduleload is the process of loading a software module into a running system so its functionality becomes available without restarting the host. A module is a self-contained unit that may include code, data, and metadata describing its dependencies and configuration. Moduleload can refer to different layers of software, from kernel drivers to user-space plugins and libraries.

In operating systems, moduleload commonly describes dynamic loading of components. In Linux, kernel modules (often with a .ko extension) are loaded into the running kernel using tools such as insmod or modprobe. Modprobe is preferred because it resolves module dependencies and can trigger related setup tasks. Kernel modules enable features such as device drivers or file systems and can be unloaded when no longer needed. In Windows, kernel-mode drivers are loaded by the system, while user-mode libraries are typically loaded through the dynamic linker/loader at runtime.

In user-space, moduleload overlaps with dynamic linking. Programs may load shared libraries (.so on Linux, .dll on Windows) at runtime using mechanisms like dlopen, enabling plugin architectures or optional functionality without recompiling. Dynamic linker behavior, symbol resolution, and dependency handling govern these loads.

Environment module systems, widely used in high-performance computing, provide a standardized interface for activating software stacks. The module command (often module load) adjusts environment variables such as PATH and LD_LIBRARY_PATH to expose a chosen software version. Some tooling or scripts may refer to this action as moduleload, describing the act of loading a software module into the user environment.

Security, compatibility, and dependency management are important considerations in moduleload. Proper versioning and careful unloading help minimize conflicts and maintain reproducible environments. See also modprobe, dlopen, and environment module systems.