man: white space fixes

These were present in the original xml files and I opted to keep them
separate fix to make the transition/comparison easier.

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:10 +01:00 committed by Lucas De Marchi
parent 134bf30e74
commit f1e233c31e
4 changed files with 8 additions and 8 deletions

View File

@ -55,7 +55,7 @@ rather than the current kernel version (as returned by *uname -r*).
*-o* _outdir_, *--outdir* _outdir_
Set the output directory where *depmod* will store any generated file.
_ outdir_ serves as a root to that location, similar to how _basedir_ is
_outdir_ serves as a root to that location, similar to how _basedir_ is
used. Also this setting takes precedence and if used together with
_basedir_ it will result in the input being that directory, but the output
being the one set by _outdir_.

View File

@ -50,7 +50,7 @@ override _modulename_ _kernelversion_ _modulesubdirectory_
This command allows you to override which version of a specific module
will be used when more than one module sharing the same name is
processed by the *depmod* command. It is possible to specify one kernel
or all kernels using the \* wildcard. _ modulesubdirectory_ is the name
or all kernels using the \* wildcard. _modulesubdirectory_ is the name
of the subdirectory under @MODULE_DIRECTORY@ (or other module location)
where the target module is installed.

View File

@ -6,7 +6,7 @@ modprobe - Add and remove modules from the Linux Kernel
# SYNOPSIS
*modprobe* [*-v*] [*-V*] [*-C *_config-file_] [*-n*] [*-i*] [*-q*] [*-b*] [_modulename_]
*modprobe* [*-v*] [*-V*] [*-C* _config-file_] [*-n*] [*-i*] [*-q*] [*-b*] [_modulename_]
\ \ \ \ \ \ \ \ \ \[_module parameters_...]
*modprobe* [*-r*] [*-v*] [*-n*] [*-i*] [_modulename_...]
@ -19,10 +19,10 @@ modprobe - Add and remove modules from the Linux Kernel
*modprobe* intelligently adds or removes a module from the Linux kernel: note
that for convenience, there is no difference between \_ and - in module names
(automatic underscore conversion is performed). * modprobe* looks in the module
(automatic underscore conversion is performed). *modprobe* looks in the module
directory @DISTCONFDIR@/`uname -r` for all the modules and other files, except
for the optional configuration files in the /etc/modprobe.d directory (see
*modprobe.d*(5)). * modprobe* will also use module options specified on the
*modprobe.d*(5)). *modprobe* will also use module options specified on the
kernel command line in the form of <module>.<option> and blacklists in the form
of modprobe.blacklist=<module>.
@ -167,7 +167,7 @@ database.
itself. This produces a (possibly empty) set of module filenames, one
per line, each starting with "insmod" and is typically used by
distributions to determine which modules to include when generating
initrd/initramfs images. * Install* commands which apply are shown
initrd/initramfs images. *Install* commands which apply are shown
prefixed by "install". It does not run any of the install commands. Note
that *modinfo*(8) can be used to extract dependencies of a module from the
module itself, but knows nothing of aliases or install commands.

View File

@ -94,7 +94,7 @@ install _modulename_ _command..._
options _modulename_ _option..._
This command allows you to add options to the module _modulename_ (which
might be an alias) every time it is inserted into the kernel: whether
directly (using *modprobe* _ modulename_) or because the module being
directly (using *modprobe* _modulename_) or because the module being
inserted depends on this module.
All options are added together: they can come from an *option* for the
@ -106,7 +106,7 @@ remove _modulename_ _command..._
softdep _modulename_ pre: _modules..._ post: _modules..._
The *softdep* command allows you to specify soft, or optional, module
dependencies. _ modulename_ can be used without these optional modules
dependencies. _modulename_ can be used without these optional modules
installed, but usually with some features missing. For example, a driver
for a storage HBA might require another module be loaded in order to use
management features.