man: modprobe.d: document the config file order handling

The modprobe.d configuration order/handling aligns with existing tools
such as sysctl.d, even though there is no mention in the manual.

Reorder the list in SYNOPSIS and add a bit of verbiage describing things.

Section is inspired by sysctl.d(5) and sysctl(8).

Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Signed-off-by: Lucas De Marchi <lucas.de.marchi@gmail.com>
This commit is contained in:
Emil Velikov 2024-07-08 14:43:19 +01:00 committed by Lucas De Marchi
parent e83e142ce7
commit 11d09ac414

View File

@ -6,25 +6,24 @@ modprobe.d - Configuration directory for modprobe
# SYNOPSIS
/lib/modprobe.d/\*.conf
@DISTCONFDIR@/modprobe.d/\*.conf
/usr/local/lib/modprobe.d/\*.conf
@SYSCONFDIR@/modprobe.d/\*.conf
/run/modprobe.d/\*.conf
/etc/modprobe.d/\*.conf
/usr/local/lib/modprobe.d/\*.conf
@DISTCONFDIR@/modprobe.d/\*.conf
/lib/modprobe.d/\*.conf
# DESCRIPTION
Because the *modprobe* command can add or remove more than one module, due to
modules having dependencies, we need a method of specifying what options are to
be used with those modules. All files underneath the /etc/modprobe.d directory
which end with the .conf extension specify those options as required. They can
also be used to create convenient aliases: alternate names for a module, or they
can override the normal *modprobe* behavior altogether for those with special
requirements (such as inserting more than one module).
be used with those modules. One can also use them to create convenient aliases:
alternate names for a module, or they can override the normal *modprobe*
behavior altogether for those with special requirements (such as inserting more
than one module).
Note that module and alias names (like other module names) can have - or \_ in
them: both are interchangeable throughout all the module commands as underscore
@ -35,6 +34,18 @@ lines and lines starting with '#' ignored (useful for adding comments). A '\\'
at the end of a line causes it to continue on the next line, which makes the
file a bit neater.
# CONFIGURATION DIRECTORIES AND PRECEDENCE
Configuration files are read from directories in listed in SYNOPSYS in that
order of precedence. Once a file of a given filename is loaded, any file of the
same name in subsequent directories is ignored.
All configuration files are sorted in lexicographic order, regardless of the
directory they reside in. Configuration files can either be completely replaced
(by having a new configuration file with the same name in a directory of higher
priority) or partially replaced (by having a configuration file that is ordered
later).
# COMMANDS
alias _wildcard_ _modulename_