Linux Kernel Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
Line 17: Line 17:


Commands: [[kmod]], [[kmod|lsmod]], [[kmod|rmmod]] [[kmod|modprobe]]
Commands: [[kmod]], [[kmod|lsmod]], [[kmod|rmmod]] [[kmod|modprobe]]
==Loading Modules at Boot==
Kernel modules can be loaded at boot by systemd-modules-load.service by creating a <''name''>.conf file in /etc/modules-load.d/ directory. The name of the file should be descriptive for the modules that are loaded by it. The content of the file should consist in comments and module names:
<syntaxhighlight lang='text'>
# Load modules required by GlusterFS at boot
dm_snapshot
dm_mirror
dm_thin_pool
</syntaxhighlight>

Latest revision as of 01:05, 11 December 2019

Internal

Overview

Runtime Configuration

Kernel Runtime Configuration

Kernel Interrupt Handler

Kernel Module

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/kernel_administration_guide/chap-documentation-kernel_administration_guide-working_with_kernel_modules

The Linux kernel is monolithic by design, but can be compiled with optional or additional modules required by specific use cases. This allows extending kernel's capabilities through the use of dynamically-loaded kernel modules. A kernel module can provide functionality such as a device driver, support for a specific filesystem, etc. Kernel modules can take parameters that customize their behavior.

Commands: kmod, lsmod, rmmod modprobe

Loading Modules at Boot

Kernel modules can be loaded at boot by systemd-modules-load.service by creating a <name>.conf file in /etc/modules-load.d/ directory. The name of the file should be descriptive for the modules that are loaded by it. The content of the file should consist in comments and module names:

# Load modules required by GlusterFS at boot
dm_snapshot
dm_mirror
dm_thin_pool