Asciidoc: Re-add empty lines to man pages

disk-utils/cfdisk.8.adoc

@@ -76,6 +76,7 @@ The commands for *cfdisk* can be entered by pressing the corresponding key (pres
 
 *n*::
   Create a new partition from free space. *cfdisk* then prompts you for the size of the partition you want to create. The default size is equal to the entire available free space at the current position. +
+  {nbsp} +
   The size may be followed by a multiplicative suffix: KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB").
 
 *q*::
@@ -83,6 +84,7 @@ The commands for *cfdisk* can be entered by pressing the corresponding key (pres
 
 *r*::
   Reduce or enlarge the current partition. *cfdisk* then prompts you for the new size of the partition. The default size is the current size. A partition marked as free space or marked as unusable cannot be resized. +
+  {nbsp} +
   *Note that reducing the size of a partition might destroy data on that partition.*
 
 *s*::
@@ -93,11 +95,14 @@ The commands for *cfdisk* can be entered by pressing the corresponding key (pres
 
 *u*::
   Dump the current in-memory partition table to an sfdisk-compatible script file. +
+  {nbsp} +
   The script files are compatible between *cfdisk*, *fdisk*(8) *sfdisk*(8) and other libfdisk applications. For more details see *sfdisk*(8). +
+  {nbsp} +
   It is also possible to load an sfdisk-script into *cfdisk* if there is no partition table on the device or when you start *cfdisk* with the *--zero* command-line option.
 
 *W*::
   Write the partition table to disk (you must enter an uppercase W). Since this might destroy data on the disk, you must either confirm or deny the write by entering `yes' or `no'. If you enter `yes', *cfdisk* will write the partition table to disk and then tell the kernel to re-read the partition table from the disk. +
+  {nbsp} +
   The re-reading of the partition table does not always work. In such a case you need to inform the kernel about any new partitions by using *partprobe*(8) or *partx*(8), or by rebooting the system.
 
 *x*::

disk-utils/fdisk.8.adoc

@@ -53,6 +53,7 @@ Note that *partx*(8) provides a rich interface for scripts to print disk layouts
 
 *-l*, *--list*::
   List the partition tables for the specified devices and then exit. +
+  {nbsp} +
   If no devices are given, the devices mentioned in _/proc/partitions_ (if this file exists) are used. Devices are always listed in the order in which they are specified on the command-line, or by the kernel listed in _/proc/partitions_.
 
 *-x*, *--list-details*::
@@ -66,6 +67,7 @@ Note that *partx*(8) provides a rich interface for scripts to print disk layouts
 
 *-o*, *--output* _list_::
   Specify which output columns to print. Use *--help* to get a list of all supported columns. +
+  {nbsp} +
   The default list of columns may be extended if _list_ is specified in the format _+list_ (e.g., *-o +UUID*).
 
 *-s*, *--getsz*::

disk-utils/fsck.8.adoc

@@ -57,8 +57,11 @@ Please see the filesystem-specific checker manual pages for further details.
 
 *-r* [****__fd__]::
   Report certain statistics for each fsck when it completes. These statistics include the exit status, the maximum run set size (in kilobytes), the elapsed all-clock time and the user and system CPU time used by the fsck run. For example: +
+  {nbsp} +
   */dev/sda1: status 0, rss 92828, real 4.002804, user 2.677592, sys 0.86186* +
+  {nbsp} +
   GUI front-ends may specify a file descriptor _fd_, in which case the progress bar information will be sent to that file descriptor in a machine parsable format. For example: +
+  {nbsp} +
   */dev/sda1 0 92828 4.002804 2.677592 0.86186*
 
 *-s*::
@@ -66,16 +69,24 @@ Please see the filesystem-specific checker manual pages for further details.
 
 *-t* _fslist_::
   Specifies the type(s) of filesystem to be checked. When the *-A* flag is specified, only filesystems that match _fslist_ are checked. The _fslist_ parameter is a comma-separated list of filesystems and options specifiers. All of the filesystems in this comma-separated list may be prefixed by a negation operator '*no*' or '*!*', which requests that only those filesystems not listed in _fslist_ will be checked. If none of the filesystems in _fslist_ is prefixed by a negation operator, then only those listed filesystems will be checked. +
+  {nbsp} +
   Options specifiers may be included in the comma-separated _fslist_. They must have the format **opts=**__fs-option__. If an options specifier is present, then only filesystems which contain _fs-option_ in their mount options field of _/etc/fstab_ will be checked. If the options specifier is prefixed by a negation operator, then only those filesystems that do not have _fs-option_ in their mount options field of _/etc/fstab_ will be checked. +
+  {nbsp} +
   For example, if *opts=ro* appears in _fslist_, then only filesystems listed in _/etc/fstab_ with the *ro* option will be checked. +
+  {nbsp} +
   For compatibility with Mandrake distributions whose boot scripts depend upon an unauthorized UI change to the *fsck* program, if a filesystem type of *loop* is found in _fslist_, it is treated as if *opts=loop* were specified as an argument to the *-t* option. +
+  {nbsp} +
   Normally, the filesystem type is deduced by searching for _filesys_ in the _/etc/fstab_ file and using the corresponding entry. If the type cannot be deduced, and there is only a single filesystem given as an argument to the *-t* option, *fsck* will use the specified filesystem type. If this type is not available, then the default filesystem type (currently ext2) is used.
 
 *-A*::
   Walk through the _/etc/fstab_ file and try to check all filesystems in one run. This option is typically used from the _/etc/rc_ system initialization file, instead of multiple commands for checking a single filesystem. +
+  {nbsp} +
   The root filesystem will be checked first unless the *-P* option is specified (see below). After that, filesystems will be checked in the order specified by the _fs_passno_ (the sixth) field in the _/etc/fstab_ file. Filesystems with a _fs_passno_ value of 0 are skipped and are not checked at all. Filesystems with a _fs_passno_ value of greater than zero will be checked in order, with filesystems with the lowest _fs_passno_ number being checked first. If there are multiple filesystems with the same pass number, *fsck* will attempt to check them in parallel, although it will avoid running multiple filesystem checks on the same physical disk. +
+  {nbsp} +
   *fsck* does not check stacked devices (RAIDs, dm-crypt, ...) in parallel with any other device. See below for *FSCK_FORCE_ALL_PARALLEL* setting. The _/sys_ filesystem is used to determine dependencies between devices. +
+  {nbsp} +
   Hence, a very common configuration in _/etc/fstab_ files is to set the root filesystem to have a _fs_passno_ value of 1 and to set all other filesystems to have a _fs_passno_ value of 2. This will allow *fsck* to automatically run filesystem checkers in parallel if it is advantageous to do so. System administrators might choose not to use this configuration if they need to avoid multiple filesystem checks running in parallel for some reason - for example, if the machine in question is short on memory so that excessive paging is a concern. +
+  {nbsp} +
   *fsck* normally does not check whether the device actually exists before calling a filesystem specific checker. Therefore non-existing devices may cause the system to enter filesystem repair mode during boot if the filesystem specific checker returns a fatal error. The _/etc/fstab_ mount option *nofail* may be used to have *fsck* skip non-existing devices. *fsck* also skips non-existing devices that have the special filesystem type *auto*.
 
 *-C* [****__fd__]::

disk-utils/mkswap.8.adoc

@@ -42,6 +42,7 @@ However, *mkswap* refuses to erase the first block on a device with a disk label
 
 *-f*, *--force*::
   Go ahead even if the command is stupid. This allows the creation of a swap area larger than the file or partition it resides on. +
+  {nbsp} +
   Also, without this option, *mkswap* will refuse to erase the first block on a device with a partition table.
 
 *-L*, *--label* _label_::

disk-utils/partx.8.adoc

@@ -55,6 +55,7 @@ This will see sda3 as a whole-disk rather than as a partition.
 
 *-n*, *--nr* __M__**:**_N_::
   Specify the range of partitions. For backward compatibility also the format __M__**-**_N_ is supported. The range may contain negative numbers, for example *--nr -1:-1* means the last partition, and *--nr -2:-1* means the last two partitions. Supported range specifications are: +
+  {nbsp} +
   _M_;;
     Specifies just one partition (e.g. *--nr 3*).
   __M__**:**;;

disk-utils/sfdisk.8.adoc

@@ -52,12 +52,16 @@ The commands are mutually exclusive.
 
 [*-N* _partition-number_] __device__::
   The default *sfdisk* command is to read the specification for the desired partitioning of _device_ from standard input, and then create a partition table according to the specification. See below for the description of the input format. If standard input is a terminal, then *sfdisk* starts an interactive session. +
+  {nbsp} +
   If the option *-N* is specified, then the changes are applied to the partition addressed by _partition-number_. The unspecified fields of the partition are not modified. +
+  {nbsp} +
   Note that it's possible to address an unused partition with *-N*. For example, an MBR always contains 4 partitions, but the number of used partitions may be smaller. In this case *sfdisk* follows the default values from the partition table and does not use built-in defaults for the unused partition given with *-N*. See also *--append*.
 
 *-A*, *--activate* __device__ [__partition-number__...]::
   Switch on the bootable flag for the specified partitions and switch off the bootable flag on all unspecified partitions. The special placeholder '-' may be used instead of the partition numbers to switch off the bootable flag on all partitions. +
+  {nbsp} +
   The activation command is supported for MBR and PMBR only. If a GPT label is detected, then *sfdisk* prints warning and automatically enters PMBR. +
+  {nbsp} +
   If no _partition-number_ is specified, then list the partitions with an enabled flag.
 
 *--delete* _device_ [__partition-number__...]::
@@ -80,6 +84,7 @@ The commands are mutually exclusive.
 
 *--part-attrs* _device partition-number_ [__attributes__]::
   Change the GPT partition attribute bits. If _attributes_ is not specified, then print the current partition settings. The _attributes_ argument is a comma- or space-delimited list of bits numbers or bit names. For example, the string "RequiredPartition,50,51" sets three bits. The currently supported attribute bits are: +
+  {nbsp} +
   *Bit 0 (RequiredPartition)*;;
     If this bit is set, the partition is required for the platform to function. The creator of the partition indicates that deletion or modification of the contents can result in loss of platform features or failure for the platform to boot or operate. The system cannot function normally if this partition is removed, and it should be considered part of the hardware of the system.
   *Bit 1 (NoBlockIOProtocol)*;;
@@ -96,6 +101,7 @@ The commands are mutually exclusive.
 
 *--part-type* _device partition-number_ [__type__]::
   Change the partition type. If _type_ is not specified, then print the current partition type. +
+  {nbsp} +
   The _type_ argument is hexadecimal for MBR, GUID for GPT, type alias (e.g. "linux") or type shortcut (e.g. 'L'). For backward compatibility the options *-c* and *--id* have the same meaning as this one.
 
 *--part-uuid* _device partition-number_ [__uuid__]::
@@ -118,6 +124,7 @@ The commands are mutually exclusive.
 
 *--relocate* _oper_ _device_::
   Relocate partition table header. This command is currently supported for GPT header only. The argument _oper_ can be: +
+  {nbsp} +
   *gpt-bak-std*;;
     Move GPT backup header to the standard location at the end of the device.
   *gpt-bak-mini*;;
@@ -127,6 +134,7 @@ The commands are mutually exclusive.
 
 *-a*, *--append*::
   Don't create a new partition table, but only append the specified partitions. +
+  {nbsp} +
   Note that unused partition maybe be re-used in this case although it is not the last partition in the partition table. See also *-N* to specify entry in the partition table.
 
 *-b*, *--backup*::
@@ -158,10 +166,15 @@ The commands are mutually exclusive.
 
 *--move-data*[**=**__path__]::
   Move data after partition relocation, for example when moving the beginning of a partition to another place on the disk. The size of the partition has to remain the same, the new and old location may overlap. This option requires option *-N* in order to be processed on one specific partition only. +
+  {nbsp} +
   The optional _path_ specifies log file name. The log file contains information about all read/write operations on the partition data. The word "@default" as a _path_ forces sfdisk to use _~/sfdisk-<devname>.move_ for the log. The log is optional since v2.35. +
+  {nbsp} +
   Note that this operation is risky and not atomic. *Don't forget to backup your data!* +
+  {nbsp} +
   See also *--move-use-fsync*. +
+  {nbsp} +
   In the example below, the first command creates a 100MiB free area before the first partition and moves the data it contains (e.g., a filesystem), the next command creates a new partition from the free space (at offset 2048), and the last command reorders partitions to match disk order (the original sdc1 will become sdc2). +
+  {nbsp} +
   *echo '+100M,' | sfdisk --move-data /dev/sdc -N 1* *echo '2048,' | sfdisk /dev/sdc --append* *sfdisk /dev/sdc --reorder*
 
 *--move-use-fsync*::
@@ -169,6 +182,7 @@ The commands are mutually exclusive.
 
 *-o*, *--output* _list_::
   Specify which output columns to print. Use *--help* to get a list of all supported columns. +
+  {nbsp} +
   The default list of columns may be extended if _list_ is specified in the format _+list_ (e.g., *-o +UUID*).
 
 *-q*, *--quiet*::

login-utils/login.1.adoc

@@ -43,6 +43,7 @@ If the file _.hushlogin_ exists, then a "quiet" login is performed. This disable
 
 *-h*::
   Used by other servers (such as *telnetd*(8) to pass the name of the remote host to *login* so that it can be placed in utmp and wtmp. Only the superuser is allowed use this option. +
+  {nbsp} +
   Note that the *-h* option has an impact on the *PAM service* *name*. The standard service name is _login_, but with the *-h* option, the name is _remote_. It is necessary to create proper PAM config files (for example, _/etc/pam.d/login_ and _/etc/pam.d/remote_).
 
 *-H*::

login-utils/lslogins.1.adoc

@@ -47,6 +47,7 @@ Mandatory arguments to long options are mandatory for short options too.
 
 *-g*, **--groups**=_groups_::
   Only show data of users belonging to _groups_. More than one group may be specified; the list has to be comma-separated. Unknown group names are ignored. +
+  {nbsp} +
   Note that relation between user and group may be invisible for primary group if the user is not explicitly specify as group member (e.g., in _/etc/group_). If the command *lslogins* scans for groups than it uses groups database only, and user database with primary GID is not used at all.
 
 *-h*, *--help*::

login-utils/runuser.1.adoc

@@ -43,6 +43,7 @@ Note that *runuser* in all cases use PAM (pam_getenvlist()) to do the final envi
 
 *-*, *-l*, *--login*::
   Start the shell as a login shell with an environment similar to a real login: +
+  {nbsp} +
   * clears all the environment variables except for *TERM* and variables specified by *--whitelist-environment* 
   * initializes the environment variables *HOME*, *SHELL*, *USER*, *LOGNAME*, and *PATH*
   * changes to the target user's home directory
@@ -50,6 +51,7 @@ Note that *runuser* in all cases use PAM (pam_getenvlist()) to do the final envi
 
 *-P*, *--pty*::
   Create a pseudo-terminal for the session. The independent terminal provides better security as the user does not share a terminal with the original session. This can be used to avoid TIOCSTI ioctl terminal injection and other security attacks against terminal file descriptors. The entire session can also be moved to the background (e.g., *runuser --pty -u username -- command &*). If the pseudo-terminal is enabled, then *runuser* works as a proxy between the sessions (copy stdin and stdout). +
+  {nbsp} +
   This feature is mostly designed for interactive sessions. If the standard input is not a terminal, but for example a pipe (e.g., *echo "date" | runuser --pty -u user*), then the ECHO flag for the pseudo-terminal is disabled to avoid messy output.
 
 *-m*, *-p*, *--preserve-environment*::
@@ -57,10 +59,12 @@ Note that *runuser* in all cases use PAM (pam_getenvlist()) to do the final envi
 
 *-s*, *--shell*=_shell_::
   Run the specified _shell_ instead of the default. The shell to run is selected according to the following rules, in order: +
+  {nbsp} +
   * the shell specified with *--shell*
   * the shell specified in the environment variable *SHELL* if the *--preserve-environment* option is used
   * the shell listed in the passwd entry of the target user
   * /bin/sh +
+  {nbsp} +
   If the target user has a restricted shell (i.e., not listed in _/etc/shells_), then the *--shell* option and the *SHELL* environment variables are ignored unless the calling user is root.
 
 **--session-command=**__command__::

login-utils/su.1.adoc

@@ -43,6 +43,7 @@ Note that *su* in all cases uses PAM (*pam_getenvlist*(3)) to do the final envir
 
 *-*, *-l*, *--login*::
   Start the shell as a login shell with an environment similar to a real login: +
+  {nbsp} +
   * clears all the environment variables except *TERM* and variables specified by *--whitelist-environment*
   * initializes the environment variables *HOME*, *SHELL*, *USER*, *LOGNAME*, and *PATH*
   * changes to the target user's home directory
@@ -53,14 +54,17 @@ Note that *su* in all cases uses PAM (*pam_getenvlist*(3)) to do the final envir
 
 *-P*, *--pty*::
   Create a pseudo-terminal for the session. The independent terminal provides better security as the user does not share a terminal with the original session. This can be used to avoid TIOCSTI ioctl terminal injection and other security attacks against terminal file descriptors. The entire session can also be moved to the background (e.g., "su --pty - username -c application &"). If the pseudo-terminal is enabled, then *su* works as a proxy between the sessions (copy stdin and stdout). +
+  {nbsp} +
   This feature is mostly designed for interactive sessions. If the standard input is not a terminal, but for example a pipe (e.g., echo "date" | su --pty), then the ECHO flag for the pseudo-terminal is disabled to avoid messy output.
 
 *-s*, **--shell**=__shell__::
   Run the specified _shell_ instead of the default. The shell to run is selected according to the following rules, in order: +
+  {nbsp} +
   * the shell specified with *--shell*
   * the shell specified in the environment variable *SHELL*, if the *--preserve-environment* option is used
   * the shell listed in the passwd entry of the target user
   * /bin/sh +
+  {nbsp} +
   If the target user has a restricted shell (i.e., not listed in /etc/shells), the *--shell* option and the *SHELL* environment variables are ignored unless the calling user is root.
 
 **--session-command=**__command__::

login-utils/sulogin.8.adoc

@@ -49,6 +49,7 @@ When the user exits from the single-user shell, or presses control-D at the prom
 
 *-e*, *--force*::
   If the default method of obtaining the root password from the system via *getpwnam*(3) fails, then examine _/etc/passwd_ and _/etc/shadow_ to get the password. If these files are damaged or nonexistent, or when root account is locked by '!' or '+++*+++' at the begin of the password then *sulogin* will *start a root shell without asking for a password*. +
+  {nbsp} +
   Only use the *-e* option if you are sure the console is physically protected against unauthorized access.
 
 *-p*, *--login-shell*::

misc-utils/blkid.8.adoc

@@ -64,36 +64,47 @@ The _size_ and _offset_ arguments may be followed by the multiplicative suffixes
 
 *-l*, *--list-one*::
   Look up only one device that matches the search parameter specified with the *--match-token* option. If there are multiple devices that match the specified search parameter, then the device with the highest priority is returned, and/or the first device found at a given priority (but see below note about udev). Device types in order of decreasing priority are: Device Mapper, EVMS, LVM, MD, and finally regular block devices. If this option is not specified, *blkid* will print all of the devices that match the search parameter. +
+  {nbsp} +
   This option forces *blkid* to use udev when used for LABEL or UUID tokens in *--match-token*. The goal is to provide output consistent with other utils (like *mount*(8), etc.) on systems where the same tag is used for multiple devices.
 
 *-L*, *--label* _label_::
   Look up the device that uses this filesystem _label_; this is equal to **--list-one --output device --match-token LABEL=**__label__. This lookup method is able to reliably use /dev/disk/by-label udev symlinks (dependent on a setting in _/etc/blkid.conf_). Avoid using the symlinks directly; it is not reliable to use the symlinks without verification. The *--label* option works on systems with and without udev. +
+  {nbsp} +
   Unfortunately, the original *blkid*(8) from e2fsprogs uses the *-L* option as a synonym for *-o list*. For better portability, use **-l -o device -t LABEL=**__label__ and *-o list* in your scripts rather than the *-L* option.
 
 *-n*, *--match-types* _list_::
   Restrict the probing functions to the specified (comma-separated) _list_ of superblock types (names). The list items may be prefixed with "no" to specify the types which should be ignored. For example: +
+  {nbsp} +
   *blkid --probe --match-types vfat,ext3,ext4 /dev/sda1* +
+  {nbsp} +
   probes for vfat, ext3 and ext4 filesystems, and +
+  {nbsp} +
   *blkid --probe --match-types nominix /dev/sda1* +
+  {nbsp} +
   probes for all supported formats except minix filesystems. This option is only useful together with *--probe*.
 
 *-o*, *--output* _format_::
   Use the specified output format. Note that the order of variables and devices is not fixed. See also option *-s*. The _format_ parameter may be: +
+  {nbsp} +
   *full*;;
     print all tags (the default)
   *value*;;
     print the value of the tags
   *list*;;
     print the devices in a user-friendly format; this output format is unsupported for low-level probing (*--probe* or *--info*). +
+    {nbsp} +
     This output format is *DEPRECATED* in favour of the *lsblk*(8) command.
   *device*;;
     print the device name only; this output format is always enabled for the *--label* and *--uuid* options
   *udev*;;
     print key="value" pairs for easy import into the udev environment; the keys are prefixed by ID_FS_ or ID_PART_ prefixes. The value may be modified to be safe for udev environment; allowed is plain ASCII, hex-escaping and valid UTF-8, everything else (including whitespaces) is replaced with '+++_+++'. The keys with __ENC_ postfix use hex-escaping for unsafe chars. +
+    {nbsp} +
     The udev output returns the ID_FS_AMBIVALENT tag if more superblocks are detected, and ID_PART_ENTRY_* tags are always returned for all partitions including empty partitions. +
+    {nbsp} +
     This output format is *DEPRECATED*.
   *export*;;
     print key=value pairs for easy import into the environment; this output format is automatically enabled when I/O Limits (*--info* option) are requested. +
+    {nbsp} +
     The non-printing characters are encoded by ^ and M- notation and all potentially unsafe characters are escaped.
 
 *-O*, *--offset* _offset_::
@@ -101,6 +112,7 @@ The _size_ and _offset_ arguments may be followed by the multiplicative suffixes
 
 *-p*, *--probe*::
   Switch to low-level superblock probing mode (bypassing the cache). +
+  {nbsp} +
   Note that low-level probing also returns information about partition table type (PTTYPE tag) and partitions (PART_ENTRY_* tags). The tag names produced by low-level probing are based on names used internally by libblkid and it may be different than when executed without *--probe* (for example PART_ENTRY_UUID= vs PARTUUID=). See also *--no-part-details*.
 
 *-s*, *--match-tag* _tag_::
@@ -114,9 +126,13 @@ The _size_ and _offset_ arguments may be followed by the multiplicative suffixes
 
 *-u*, *--usages* _list_::
   Restrict the probing functions to the specified (comma-separated) _list_ of "usage" types. Supported usage types are: filesystem, raid, crypto and other. The list items may be prefixed with "no" to specify the usage types which should be ignored. For example: +
+  {nbsp} +
   *blkid --probe --usages filesystem,other /dev/sda1* +
+  {nbsp} +
   probes for all filesystem and other (e.g., swap) formats, and +
+  {nbsp} +
   *blkid --probe --usages noraid /dev/sda1* +
+  {nbsp} +
   probes for all supported formats except RAIDs. This option is only useful together with *--probe*.
 
 *-U*, *--uuid* _uuid_::

misc-utils/cal.1.adoc

@@ -90,10 +90,12 @@ Optionally, either the proleptic Gregorian calendar or the Julian calendar may b
 
 *-j*, *--julian*::
   Use day-of-year numbering for all calendars. These are also called ordinal days. Ordinal days range from 1 to 366. This option does not switch from the Gregorian to the Julian calendar system, that is controlled by the *--reform* option. +
+  {nbsp} +
   Sometimes Gregorian calendars using ordinal dates are referred to as Julian calendars. This can be confusing due to the many date related conventions that use Julian in their name: (ordinal) julian date, julian (calendar) date, (astronomical) julian date, (modified) julian date, and more. This option is named julian, because ordinal days are identified as julian by the POSIX standard. However, be aware that *cal* also uses the Julian calendar system. See *DESCRIPTION* above.
 
 *--reform* _val_::
   This option sets the adoption date of the Gregorian calendar reform. Calendar dates previous to reform use the Julian calendar system. Calendar dates after reform use the Gregorian calendar system. The argument _val_ can be: +
+  {nbsp} +
   * _1752_ - sets 3 September 1752 as the reform date (default). This is when the Gregorian calendar reform was adopted by the British Empire.
   * _gregorian_ - display Gregorian calendars exclusively. This special placeholder sets the reform date below the smallest year that *cal* can use; meaning all calendar output uses the Gregorian calendar system. This is called the proleptic Gregorian calendar, because dates prior to the calendar system's creation use extrapolated values.
   * _iso_ - alias of _gregorian_. The ISO 8601 standard for the representation of dates and times in information interchange requires using the proleptic Gregorian calendar.
@@ -126,7 +128,9 @@ See *­DESCRIPTION* above.
 
 *Single string parameter (e.g., 'cal tomorrow' or 'cal August')*::
   Specifies _timestamp_ or a _month name_ (or abbreviated name) according to the current locales. +
+  {nbsp} +
   The special placeholders are accepted when parsing timestamp, "now" may be used to refer to the current time, "today", "yesterday", "tomorrow" refer to of the current day, the day before or the next day, respectively. +
+  {nbsp} +
   The relative date specifications are also accepted, in this case "+" is evaluated to the current time plus the specified time span. Correspondingly, a time span that is prefixed with "-" is evaluated to the current time minus the specified time span, for example '+2days'. Instead of prefixing the time span with "+" or "-", it may also be suffixed with a space and the word "left" or "ago" (for example '1 week ago').
 
 *Two parameters (e.g., 'cal 11 2020')*::

misc-utils/findmnt.8.adoc

@@ -89,6 +89,7 @@ The command prints all mounted filesystems in the tree-like format by default.
 
 *-o*, *--output* _list_::
   Define output columns. See the *--help* output to get a list of the currently supported columns. The *TARGET* column contains tree formatting if the *--list* or *--raw* options are not specified. +
+  {nbsp} +
   The default list of columns may be extended if _list_ is specified in the format _+list_ (e.g., *findmnt -o +PROPAGATION*).
 
 *--output-all*::
@@ -99,8 +100,11 @@ The command prints all mounted filesystems in the tree-like format by default.
 
 *-p*, *--poll*[_=list_]::
   Monitor changes in the _/proc/self/mountinfo_ file. Supported actions are: mount, umount, remount and move. More than one action may be specified in a comma-separated list. All actions are monitored by default. +
+  {nbsp} +
   The time for which *--poll* will block can be restricted with the *--timeout* or *--first-only* options. +
+  {nbsp} +
   The standard columns always use the new version of the information from the mountinfo file, except the umount action which is based on the original information cached by findmnt8. The poll mode allows using extra columns: +
+  {nbsp} +
   *ACTION*;;
     mount, umount, move or remount action name; this column is enabled by default
   *OLD-TARGET*;;

misc-utils/kill.1.adoc

@@ -37,6 +37,7 @@ The list of processes to be signaled can be a mixture of names and PIDs.
 
 _pid_::
   Each _pid_ can be expressed in one of the following ways: +
+  {nbsp} +
   _n_;;
     where _n_ is larger than 0. The process with PID _n_ is signaled.
   *0*;;
@@ -67,8 +68,11 @@ _name_::
   Send the signal using *sigqueue*(3) rather than *kill*(2). The _value_ argument is an integer that is sent along with the signal. If the receiving process has installed a handler for this signal using the *SA_SIGINFO* flag to *sigaction*(2), then it can obtain this data via the _si_sigval_ field of the `siginfo_t` structure.
 *--timeout* _milliseconds signal_::
   Send a signal defined in the usual way to a process, followed by an additional signal after a specified delay. The *--timeout* option causes *kill* to wait for a period defined in _milliseconds_ before sending a follow-up _signal_ to the process. This feature is implemented using the Linux kernel PID file descriptor feature in order to guarantee that the follow-up signal is sent to the same process or not sent if the process no longer exists. +
+  {nbsp} +
   Note that the operating system may re-use PIDs and implementing an equivalent feature in a shell using *kill* and *sleep* would be subject to races whereby the follow-up signal might be sent to a different process that used a recycled PID. +
+  {nbsp} +
   The *--timeout* option can be specified multiple times: the signals are sent sequentially with the specified timeouts. The *--timeout* option can be combined with the *--queue* option. +
+  {nbsp} +
   As an example, the following command sends the signals QUIT, TERM and KILL in sequence and waits for 1000 milliseconds between sending the signals: +
 ....
 kill --verbose --timeout 1000 TERM --timeout 1000 KILL \

misc-utils/logger.1.adoc

@@ -57,6 +57,7 @@ When the optional _message_ argument is present, it is written to the log. If it
 
 *-d*, *--udp*::
   Use datagrams (UDP) only. By default the connection is tried to the syslog port defined in _/etc/services_, which is often 514. +
+  {nbsp} +
   See also *--server* and *--socket* to specify where to connect.
 
 *-e*, *--skip-empty*::
@@ -70,10 +71,12 @@ When the optional _message_ argument is present, it is written to the log. If it
 
 *--id*[**=**__id__]::
   Log the PID of the logger process with each line. When the optional argument _id_ is specified, then it is used instead of the logger command's PID. The use of *--id=$$* (PPID) is recommended in scripts that send several messages. +
+  {nbsp} +
   Note that the system logging infrastructure (for example *systemd* when listening on _/dev/log_) may follow local socket credentials to overwrite the PID specified in the message. *logger*(1) is able to set those socket credentials to the given _id_, but only if you have root permissions and a process with the specified PID exists, otherwise the socket credentials are not modified and the problem is silently ignored.
 
 *--journald*[**=**__file__]::
   Write a systemd journal entry. The entry is read from the given _file_, when specified, otherwise from standard input. Each line must begin with a field that is accepted by journald; see *systemd.journal-fields*(7) for details. The use of a MESSAGE_ID field is generally a good idea, as it makes finding entries easy. Examples: +
+  {nbsp} +
 ____
     logger --journald <<end
     MESSAGE_ID=67feb6ffbaf24c5cbec13c008dd72309
@@ -84,8 +87,8 @@ ____
 
     logger --journald=entry.txt
 ____
-
 Notice that *--journald* will ignore values of other options, such as priority. If priority is needed it must be within input, and use PRIORITY field. The simple execution of *journalctl*(1) will display MESSAGE field. Use *journalctl --output json-pretty* to see rest of the fields. +
+{nbsp} +
 To include newlines in MESSAGE, specify MESSAGE several times. This is handled as a special case, other fields will be stored as an array in the journal if they appear multiple times.
 
 *--msgid* _msgid_::
@@ -108,7 +111,9 @@ To include newlines in MESSAGE, specify MESSAGE several times. This is handled a
 
 *--prio-prefix*::
   Look for a syslog prefix on every line read from standard input. This prefix is a decimal number within angle brackets that encodes both the facility and the level. The number is constructed by multiplying the facility by 8 and then adding the level. For example, *local0.info*, meaning facility=16 and level=6, becomes *<134>*. +
+  {nbsp} +
   If the prefix contains no facility, the facility defaults to what is specified by the *-p* option. Similarly, if no prefix is provided, the line is logged using the _priority_ given with *-p*. +
+  {nbsp} +
   This option doesn't affect a command-line message.
 
 *--rfc3164*::
@@ -116,9 +121,13 @@ To include newlines in MESSAGE, specify MESSAGE several times. This is handled a
 
 *--rfc5424*[**=**__without__]::
   Use the link:https://tools.ietf.org/html/rfc5424[RFC 5424] syslog protocol to submit messages to a remote server. The optional _without_ argument can be a comma-separated list of the following values: *notq*, *notime*, *nohost*. +
+  {nbsp} +
   The *notq* value suppresses the time-quality structured data from the submitted message. The time-quality information shows whether the local clock was synchronized plus the maximum number of microseconds the timestamp might be off. The time quality is also automatically suppressed when *--sd-id timeQuality* is specified. +
+  {nbsp} +
   The *notime* value (which implies *notq*) suppresses the complete sender timestamp that is in ISO-8601 format, including microseconds and timezone. +
+  {nbsp} +
   The *nohost* value suppresses *gethostname*(2) information from the message header. +
+  {nbsp} +
   The RFC 5424 protocol has been the default for *logger* since version 2.26.
 
 *-s*, *--stderr*::
@@ -126,6 +135,7 @@ To include newlines in MESSAGE, specify MESSAGE several times. This is handled a
 
 *--sd-id* _name_[**@**__digits__]::
   Specifies a structured data element ID for an RFC 5424 message header. The option has to be used before *--sd-param* to introduce a new element. The number of structured data elements is unlimited. The ID (_name_ plus possibly **@**__digits__) is case-sensitive and uniquely identifies the type and purpose of the element. The same ID must not exist more than once in a message. The **@**__digits__ part is required for user-defined non-standardized IDs. +
+  {nbsp} +
   *logger* currently generates the *timeQuality* standardized element only. RFC 5424 also describes the elements *origin* (with parameters ip, enterpriseId, software and swVersion) and *meta* (with parameters sequenceId, sysUpTime and language). These element IDs may be specified without the **@**__digits__ suffix.
 
 *--sd-param* _name_=_value_::
@@ -143,15 +153,19 @@ produces: +
 
 *-S*, *--size* _size_::
   Sets the maximum permitted message size to _size_. The default is 1KiB characters, which is the limit traditionally used and specified in RFC 3164. With RFC 5424, this limit has become flexible. A good assumption is that RFC 5424 receivers can at least process 4KiB messages. +
+  {nbsp} +
   Most receivers accept messages larger than 1KiB over any type of syslog protocol. As such, the *--size* option affects logger in all cases (not only when *--rfc5424* was used). +
+  {nbsp} +
   Note: the message-size limit limits the overall message size, including the syslog header. Header sizes vary depending on the selected options and the hostname length. As a rule of thumb, headers are usually not longer than 50 to 80 characters. When selecting a maximum message size, it is important to ensure that the receiver supports the max size as well, otherwise messages may become truncated. Again, as a rule of thumb two to four KiB message size should generally be OK, whereas anything larger should be verified to work.
 
 *--socket-errors*[**=**__mode__]::
   Print errors about Unix socket connections. The _mode_ can be a value of *off*, *on*, or *auto*. When the mode is auto logger will detect if the init process is systemd, and if so assumption is made _/dev/log_ can be used early at boot. Other init systems lack of _/dev/log_ will not cause errors that is identical with messaging using *openlog*(3) system call. The *logger*(1) before version 2.26 used openlog, and hence was unable to detected loss of messages sent to Unix sockets. +
+  {nbsp} +
   The default mode is *auto*. When errors are not enabled lost messages are not communicated and will result to successful exit status of *logger*(1) invocation.
 
 *-T*, *--tcp*::
   Use stream (TCP) only. By default the connection is tried to the _syslog-conn_ port defined in _/etc/services_, which is often _601_. +
+  {nbsp} +
   See also *--server* and *--socket* to specify where to connect.
 
 *-t*, *--tag* _tag_::

misc-utils/look.1.adoc

@@ -60,6 +60,7 @@ If _file_ is not specified, the file _/usr/share/dict/words_ is used, only alpha
 
 *-d*, *--alphanum*::
   Use normal dictionary character set and order, i.e., only blanks and alphanumeric characters are compared. This is on by default if no file is specified. +
+  {nbsp} +
   Note that blanks have been added to dictionary character set for compatibility with *sort -d* command since version 2.28.
 
 *-f*, *--ignore-case*::

misc-utils/lsblk.8.adoc

@@ -41,6 +41,7 @@ The relationship between block devices and filesystems is not always one-to-one.
 
 *-E*, *--dedup* _column_::
   Use _column_ as a de-duplication key to de-duplicate output tree. If the key is not available for the device, or the device is a partition and parental whole-disk device provides the same key than the device is always printed. +
+  {nbsp} +
   The usual use case is to de-duplicate output on system multi-path devices, for example by *-E WWN*.
 
 -e*, *--exclude* _list_::
@@ -75,6 +76,7 @@ The relationship between block devices and filesystems is not always one-to-one.
 
 *-o*, *--output* _list_::
   Specify which output columns to print. Use *--help* to get a list of all supported columns. The columns may affect tree-like output. The default is to use tree for the column 'NAME' (see also *--tree*). +
+  {nbsp} +
   The default list of columns may be extended if _list_ is specified in the format _+list_ (e.g., *lsblk -o +UUID*).
 
 *-O*, *--output-all*::
@@ -100,6 +102,7 @@ The relationship between block devices and filesystems is not always one-to-one.
 
 *-t*, *--topology*::
   Output info about block-device topology. This option is equivalent to +
+  {nbsp} +
   *-o NAME,ALIGNMENT,MIN-IO,OPT-IO,PHY-SEC,LOG-SEC,ROTA,SCHED,RQ-SIZE,RA,WSAME*.
 
 *-V*, *--version*::

misc-utils/lslocks.8.adoc

@@ -45,6 +45,7 @@ Note that lslocks also lists OFD (Open File Description) locks, these locks are
 
 *-o*, *--output* _list_::
   Specify which output columns to print. Use *--help* to get a list of all supported columns. +
+  {nbsp} +
   The default list of columns may be extended if _list_ is specified in the format _+list_ (e.g., *lslocks -o +BLOCKER*).
 
 *--output-all*::

misc-utils/mcookie.1.adoc

@@ -32,6 +32,7 @@ The "random" number generated is actually the MD5 message digest of random infor
 
 *-m*, *--max-size* _number_::
   Read from _file_ only this _number_ of bytes. This option is meant to be used when reading additional randomness from a file or device. +
+  {nbsp} +
   The _number_ argument may be followed by the multiplicative suffixes KiB=1024, MiB=1024*1024, and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB") or the suffixes KB=1000, MB=1000*1000, and so on for GB, TB, PB, EB, ZB and YB.
 
 *-v*, *--verbose*::

misc-utils/wipefs.8.adoc

@@ -65,6 +65,7 @@ Note that by default *wipefs* does not erase nested partition tables on non-whol
 
 *-o*, *--offset* _offset_::
   Specify the location (in bytes) of the signature which should be erased from the device. The _offset_ number may include a "0x" prefix; then the number will be interpreted as a hex value. It is possible to specify multiple *-o* options. +
+  {nbsp} +
   The _offset_ argument may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB"), or the suffixes KB (=1000), MB (=1000*1000), and so on for GB, TB, PB, EB, ZB and YB.
 
 *-p*, *--parsable*::

schedutils/ionice.1.adoc

@@ -32,7 +32,9 @@ As of this writing, a process can be in one of three scheduling classes:
 
 *Best-effort*::
   This is the effective scheduling class for any process that has not asked for a specific I/O priority. This class takes a priority argument from _0-7_, with a lower number being higher priority. Programs running at the same best-effort priority are served in a round-robin fashion. +
+  {nbsp} +
   Note that before kernel 2.6.26 a process that has not asked for an I/O priority formally uses "*none*" as scheduling class, but the I/O scheduler will treat such processes as if it were in the best-effort class. The priority within the best-effort class will be dynamically derived from the CPU nice level of the process: io_priority = (cpu_nice + 20) / 5. +
+  {nbsp} +
   For kernels after 2.6.26 with the CFQ I/O scheduler, a process that has not asked for an I/O priority inherits its CPU scheduling class. The I/O priority is derived from the CPU nice level of the process (same as before kernel 2.6.26).
 
 *Realtime*::

sys-utils/dmesg.1.adoc

@@ -60,7 +60,9 @@ The *--clear*, *--read-clear*, *--console-on*, *--console-off*, and *--console-l
 
 *-f*, *--facility* _list_::
   Restrict output to the given (comma-separated) _list_ of facilities. For example: +
+  {nbsp} +
   *dmesg --facility=daemon* +
+  {nbsp} +
   will print messages from system daemons only. For all supported facilities see the *--help* output.
 
 *-H*, *--human*::
@@ -74,11 +76,14 @@ The *--clear*, *--read-clear*, *--console-on*, *--console-off*, and *--console-l
 
 *-l*, *--level* _list_::
   Restrict output to the given (comma-separated) _list_ of levels. For example: +
+  {nbsp} +
   *dmesg --level=err,warn* +
+  {nbsp} +
   will print error and warning messages only. For all supported levels see the *--help* output.
 
 *-n*, *--console-level* _level_::
   Set the _level_ at which printing of messages is done to the console. The _level_ is a level number or abbreviation of the level name. For all supported levels see the *--help* output. +
+  {nbsp} +
   For example, *-n 1* or *-n emerg* prevents all messages, except emergency (panic) messages, from appearing on the console. All levels of messages are still written to _/proc/kmsg_, so *syslogd*(8) can still be used to control exactly where kernel messages appear. When the *-n* option is used, *dmesg* will _not_ print or clear the kernel ring buffer.
 
 *--noescape*::
@@ -91,8 +96,8 @@ The *--clear*, *--read-clear*, *--console-on*, *--console-off*, and *--console-l
   Add facility, level or timestamp information to each line of a multi-line message.
 
 *-r*, *--raw*::
-  Print the raw message buffer, i.e., do not strip the log-level prefixes, but all unprintable characters are still escaped (see also *--noescape*).
-  +
+  Print the raw message buffer, i.e., do not strip the log-level prefixes, but all unprintable characters are still escaped (see also *--noescape*). +
+  {nbsp} +
   Note that the real raw format depends on the method how *dmesg* reads kernel messages. The _/dev/kmsg_ device uses a different format than *syslog*(2). For backward compatibility, *dmesg* returns data always in the *syslog*(2) format. It is possible to read the real raw data from _/dev/kmsg_ by, for example, the command 'dd if=/dev/kmsg iflag=nonblock'.
 
 *-S*, *--syslog*::
@@ -102,8 +107,8 @@ The *--clear*, *--read-clear*, *--console-on*, *--console-off*, and *--console-l
   Use a buffer of _size_ to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default, then this option can be used to view the entire buffer.
 
 *-T*, *--ctime*::
-  Print human-readable timestamps.
-  +
+  Print human-readable timestamps. +
+  {nbsp} +
   *Be aware that the timestamp could be inaccurate!* The *time* source used for the logs is *not updated after* system *SUSPEND*/*RESUME*. Timestamps are adjusted according to current delta between boottime and monotonic clocks, this works only for messages printed after last resume.
 
 *--since* _time_::
@@ -117,6 +122,7 @@ The *--clear*, *--read-clear*, *--console-on*, *--console-off*, and *--console-l
 
 *--time-format* _format_::
   Print timestamps using the given _format_, which can be *ctime*, *reltime*, *delta* or *iso*. The first three formats are aliases of the time-format-specific options. The *iso* format is a *dmesg* implementation of the ISO-8601 timestamp format. The purpose of this format is to make the comparing of timestamps between two systems, and any other parsing, easy. The definition of the *iso* timestamp is: YYYY-MM-DD<T>HH:MM:SS,<microseconds><-+><timezone offset from UTC>. +
+  {nbsp} +
   The *iso* format has the same issue as *ctime*: the time may be inaccurate when a system is suspended and resumed.
 
 *-u*, *--userspace*;;

sys-utils/fallocate.1.adoc

@@ -31,12 +31,16 @@ The options *--collapse-range*, *--dig-holes*, *--punch-hole*, and *--zero-range
 
 *-c*, *--collapse-range*::
   Removes a byte range from a file, without leaving a hole. The byte range to be collapsed starts at _offset_ and continues for _length_ bytes. At the completion of the operation, the contents of the file starting at the location __offset__+_length_ will be appended at the location _offset_, and the file will be _length_ bytes smaller. The option *--keep-size* may not be specified for the collapse-range operation. +
+  {nbsp} +
   Available since Linux 3.15 for ext4 (only for extent-based files) and XFS. +
+  {nbsp} +
   A filesystem may place limitations on the granularity of the operation, in order to ensure efficient implementation. Typically, offset and len must be a multiple of the filesystem logical block size, which varies according to the filesystem type and configuration. If a filesystem has such a requirement, the operation will fail with the error EINVAL if this requirement is violated.
 
 *-d*, *--dig-holes*::
   Detect and dig holes. This makes the file sparse in-place, without using extra disk space. The minimum size of the hole depends on filesystem I/O block size (usually 4096 bytes). Also, when using this option, *--keep-size* is implied. If no range is specified by *--offset* and *--length*, then the entire file is analyzed for holes. +
+  {nbsp} +
   You can think of this option as doing a "*cp --sparse*" and then renaming the destination file to the original, without the need for extra disk space. +
+  {nbsp} +
   See *--punch-hole* for a list of supported filesystems.
 
 *-i*, *--insert-range*::
@@ -53,6 +57,7 @@ The options *--collapse-range*, *--dig-holes*, *--punch-hole*, and *--zero-range
 
 *-p*, *--punch-hole*::
   Deallocates space (i.e., creates a hole) in the byte range starting at _offset_ and continuing for _length_ bytes. Within the specified range, partial filesystem blocks are zeroed, and whole filesystem blocks are removed from the file. After a successful call, subsequent reads from this range will return zeroes. This option may not be specified at the same time as the *--zero-range* option. Also, when using this option, *--keep-size* is implied. +
+  {nbsp} +
   Supported for XFS (since Linux 2.6.38), ext4 (since Linux 3.0), Btrfs (since Linux 3.7), tmpfs (since Linux 3.5) and gfs2 (since Linux 4.16).
 
 *-v*, *--verbose*::
@@ -63,8 +68,11 @@ The options *--collapse-range*, *--dig-holes*, *--punch-hole*, and *--zero-range
 
 *-z*, *--zero-range*::
   Zeroes space in the byte range starting at _offset_ and continuing for _length_ bytes. Within the specified range, blocks are preallocated for the regions that span the holes in the file. After a successful call, subsequent reads from this range will return zeroes. +
+  {nbsp} +
   Zeroing is done within the filesystem preferably by converting the range into unwritten extents. This approach means that the specified range will not be physically zeroed out on the device (except for partial blocks at the either end of the range), and I/O is (otherwise) required only to update metadata. +
+  {nbsp} +
   Option *--keep-size* can be specified to prevent file length modification. +
+  {nbsp} +
   Available since Linux 3.14 for ext4 (only for extent-based files) and XFS.
 
 *-V*, *--version*::

sys-utils/fsfreeze.8.adoc

@@ -29,6 +29,7 @@ Note that access-time updates are also suspended if the filesystem is mounted wi
 
 *-f*, *--freeze*::
   This option requests the specified a filesystem to be frozen from new modifications. When this is selected, all ongoing transactions in the filesystem are allowed to complete, new write system calls are halted, other calls which modify the filesystem are halted, and all dirty data, metadata, and log information are written to disk. Any process attempting to write to the frozen filesystem will block waiting for the filesystem to be unfrozen. +
+  {nbsp} +
   Note that even after freezing, the on-disk filesystem can contain information on files that are still in the process of unlinking. These files will not be unlinked until the filesystem is unfrozen or a clean mount of the snapshot is complete.
 
 *-u*, *--unfreeze*::

sys-utils/fstrim.8.adoc

@@ -43,13 +43,15 @@ The _offset_, _length_, and _minimum-size_ arguments may be followed by the mult
   The number of bytes (after the starting point) to search for free blocks to discard. If the specified value extends past the end of the filesystem, *fstrim* will stop at the filesystem size boundary. The default value extends to the end of the filesystem.
 
 *-I, --listed-in* _list_::
-  Specifies a colon-separated list of files in fstab or kernel mountinfo format. All missing or empty files are silently ignored. The evaluation of the _list_ stops after first non-empty file. For example: *--listed-in /etc/fstab:/proc/self/mountinfo*.
+  Specifies a colon-separated list of files in fstab or kernel mountinfo format. All missing or empty files are silently ignored. The evaluation of the _list_ stops after first non-empty file. For example: 
+  *--listed-in /etc/fstab:/proc/self/mountinfo*.
 
 *-m, --minimum* _minimum-size_::
   Minimum contiguous free range to discard, in bytes. (This value is internally rounded up to a multiple of the filesystem block size.) Free ranges smaller than this will be ignored and fstrim will adjust the minimum if it's smaller than the device's minimum, and report that (fstrim_range.minlen) back to userspace. By increasing this value, the fstrim operation will complete more quickly for filesystems with badly fragmented freespace, although not all blocks will be discarded. The default value is zero, discarding every free block.
 
 *-v, --verbose*::
   Verbose execution. With this option *fstrim* will output the number of bytes passed from the filesystem down the block stack to the device for potential discard. This number is a maximum discard amount from the storage device's perspective, because _FITRIM_ ioctl called repeated will keep sending the same sectors for discard repeatedly. +
+  {nbsp} +
   *fstrim* will report the same potential discard bytes each time, but only sectors which had been written to between the discards would actually be discarded by the storage device. Further, the kernel block layer reserves the right to adjust the discard ranges to fit raid stripe geometry, non-trim capable devices in a LVM setup, etc. These reductions would not be reflected in fstrim_range.len (the *--length* option).
   
 *--quiet-unsupported*::

sys-utils/hwclock.8.adoc

@@ -35,30 +35,46 @@ Add or subtract time from the Hardware Clock to account for systematic drift sin
 
 *--getepoch*; *--setepoch*::
   These functions are for Alpha machines only, and are only available through the Linux kernel RTC driver. +
+  {nbsp} +
   They are used to read and set the kernel's Hardware Clock epoch value. Epoch is the number of years into AD to which a zero year value in the Hardware Clock refers. For example, if the machine's BIOS sets the year counter in the Hardware Clock to contain the number of full years since 1952, then the kernel's Hardware Clock epoch value must be 1952. +
+  {nbsp} +
   The *­--setepoch* function requires using the *­--epoch* option to specify the year. For example: +
+  {nbsp} +
   **hwclock --setepoch --epoch=1952** +
+  {nbsp} +
   The RTC driver attempts to guess the correct epoch value, so setting it may not be required. +
+  {nbsp} +
   This epoch value is used whenever *­hwclock* reads or sets the Hardware Clock on an Alpha machine. For ISA machines the kernel uses the fixed Hardware Clock epoch of 1900.
 
 *--predict*::
   Predict what the Hardware Clock will read in the future based upon the time given by the *--date* option and the information in _{ADJTIME_PATH}_. This is useful, for example, to account for drift when setting a Hardware Clock wakeup (aka alarm). See *­rtcwake*(8). +
+  {nbsp} +
   Do not use this function if the Hardware Clock is being modified by anything other than the current operating system's *­hwclock* command, such as ­'11 minute mode' or from dual-booting another OS.
 
 *-r*, *--show*; *--get*::
   Read the Hardware Clock and print its time to standard output in the *ISO 8601* format. The time shown is always in local time, even if you keep your Hardware Clock in UTC. See the *­--localtime* option. +
+  {nbsp} +
   Showing the Hardware Clock time is the default when no function is specified. +
+  {nbsp} +
   The *--get* function also applies drift correction to the time read, based upon the information in _{ADJTIME_PATH}_. Do not use this function if the Hardware Clock is being modified by anything other than the current operating system's *­hwclock* command, such as ­'11 minute mode' or from dual-booting another OS.
 
 *-s*, *--hctosys*::
   Set the System Clock from the Hardware Clock. The time read from the Hardware Clock is compensated to account for systematic drift before using it to set the System Clock. See the discussion below, under *The Adjust Function*. +
+  {nbsp} +
   The System Clock must be kept in the UTC timescale for date-time applications to work correctly in conjunction with the timezone configured for the system. If the Hardware Clock is kept in local time then the time read from it must be shifted to the UTC timescale before using it to set the System Clock. The *­--hctosys* function does this based upon the information in the _{ADJTIME_PATH}_ file or the command line arguments *­--localtime* and *--utc*. Note: no daylight saving adjustment is made. See the discussion below, under *LOCAL vs UTC*. +
+  {nbsp} +
   The kernel also keeps a timezone value, the *­--hctosys* function sets it to the timezone configured for the system. The system timezone is configured by the TZ environment variable or the _­/etc/localtime_ file, as *­tzset*(3) would interpret them. The obsolete _tz_dsttime_ field of the kernel's timezone value is set to zero. (For details on what this field used to mean, see *­settimeofday*(2).) +
+  {nbsp} +
   When used in a startup script, making the *­--hctosys* function the first caller of *­settimeofday*(2) from boot, it will set the NTP ­'11 minute mode' timescale via the _­persistent_clock_is_local_ kernel variable. If the Hardware Clock's timescale configuration is changed then a reboot is required to inform the kernel. See the discussion below, under *Automatic Hardware Clock Synchronization by the Kernel*. +
+  {nbsp} +
   This is a good function to use in one of the system startup scripts before the file systems are mounted read/write. +
+  {nbsp} +
   This function should never be used on a running system. Jumping system time will cause problems, such as corrupted filesystem timestamps. Also, if something has changed the Hardware Clock, like NTP's ­'11 minute mode', then *­--hctosys* will set the time incorrectly by including drift compensation. +
+  {nbsp} +
   Drift compensation can be inhibited by setting the drift factor in _{ADJTIME_PATH}_ to zero. This setting will be persistent as long as the *­--update-drift* option is not used with *­--systohc* at shutdown (or anywhere else). Another way to inhibit this is by using the *­--noadjfile* option when calling the *­--hctosys* function. A third method is to delete the _{ADJTIME_PATH}_ file. *Hwclock* will then default to using the UTC timescale for the Hardware Clock. If the Hardware Clock is ticking local time it will need to be defined in the file. This can be done by calling *hwclock --localtime --adjust*; when the file is not present this command will not actually adjust the Clock, but it will create the file with local time configured, and a drift factor of zero. +
+  {nbsp} +
   A condition under which inhibiting *hwclock*'s drift correction may be desired is when dual-booting multiple operating systems. If while this instance of Linux is stopped, another OS changes the Hardware Clock's value, then when this instance is started again the drift correction applied will be incorrect. +
+  {nbsp} +
   For *hwclock*'s drift correction to work properly it is imperative that nothing changes the Hardware Clock while its Linux instance is not running.
 
 *--set*::
@@ -66,12 +82,14 @@ Add or subtract time from the Hardware Clock to account for systematic drift sin
 
 *--systz*::
   This is an alternate to the *­--hctosys* function that does not read the Hardware Clock nor set the System Clock; consequently there is not any drift correction. It is intended to be used in a startup script on systems with kernels above version 2.6 where you know the System Clock has been set from the Hardware Clock by the kernel during boot. +
+  {nbsp} +
   It does the following things that are detailed above in the *­--hctosys* function: +
+  {nbsp} +
   * Corrects the System Clock timescale to UTC as needed. Only instead of accomplishing this by setting the System Clock, *hwclock* simply informs the kernel and it handles the change.
   * Sets the kernel's NTP ­'11 minute mode' timescale.
-  * Sets the kernel's timezone.
-
-The first two are only available on the first call of ­*settimeofday*(2) after boot. Consequently this option only makes sense when used in a startup script. If the Hardware Clocks timescale configuration is changed then a reboot would be required to inform the kernel.
+  * Sets the kernel's timezone. +
+  {nbsp} +
+  The first two are only available on the first call of ­*settimeofday*(2) after boot. Consequently this option only makes sense when used in a startup script. If the Hardware Clocks timescale configuration is changed then a reboot would be required to inform the kernel.
 
 *-w*, *--systohc*::
   Set the Hardware Clock from the System Clock, and update the timestamps in _{ADJTIME_PATH}_. With the *­--update-drift* option also (re)calculate the drift factor. Try it without the option if *­--systohc* fails. See *­--update-drift* below.
@@ -89,12 +107,15 @@ The first two are only available on the first call of ­*settimeofday*(2) after
 
 **­--date=**__date_string__::
   This option must be used with the *--set* or *­--predict* functions, otherwise it is ignored. +
+  {nbsp} +
   *hwclock --set --date='16:45'* +
   *hwclock --predict --date='2525-08-14 07:11:05'* +
+  {nbsp} +
   The argument must be in local time, even if you keep your Hardware Clock in UTC. See the *­--localtime* option. Therefore, the argument should not include any timezone information. It also should not be a relative time like "+5 minutes", because *­hwclock*'s precision depends upon correlation between the argument's value and when the enter key is pressed. Fractional seconds are silently dropped. This option is capable of understanding many time and date formats, but the previous parameters should be observed.
 
 **­--delay=**__seconds__::
   This option can be used to overwrite the internally used delay when setting the clock time. The default is 0.5 (500ms) for rtc_cmos, for another RTC types the delay is 0. If RTC type is impossible to determine (from sysfs) then it defaults also to 0.5 to be backwardly compatible. +
+  {nbsp} +
   The 500ms default is based on commonly used MC146818A-compatible (x86) hardware clock. This Hardware Clock can only be set to any integer time plus one half second. The integer time is required because there is no interface to set or get a fractional second. The additional half second delay is because the Hardware Clock updates to the following second precisely 500 ms after setting the new time. Unfortunately, this behavior is hardware specific and in same cases another delay is required.
 
 *-D*, *--debug*::
@@ -111,8 +132,11 @@ The first two are only available on the first call of ­*settimeofday*(2) after
 
 *-l*, *--localtime*; *-u*, *--utc*::
   Indicate which timescale the Hardware Clock is set to. +
+  {nbsp} +
   The Hardware Clock may be configured to use either the UTC or the local timescale, but nothing in the clock itself says which alternative is being used. The *­--localtime* or *--utc* options give this information to the *­hwclock* command. If you specify the wrong one (or specify neither and take a wrong default), both setting and reading the Hardware Clock will be incorrect. +
+  {nbsp} +
   If you specify neither *--utc* nor *­--localtime* then the one last given with a set function (*--set*, *­--systohc*, or *­--adjust*), as recorded in _{ADJTIME_PATH}_, will be used. If the adjtime file doesn't exist, the default is UTC. +
+  {nbsp} +
   Note: daylight saving time changes may be inconsistent when the Hardware Clock is kept in local time. See the discussion below, under *LOCAL vs UTC*.
 
 *--noadjfile*::
@@ -123,8 +147,11 @@ The first two are only available on the first call of ­*settimeofday*(2) after
 
 *--update-drift*::
   Update the Hardware Clock's drift factor in _{ADJTIME_PATH}_. It can only be used with *--set* or *­--systohc*. +
+  {nbsp} +
   A minimum four hour period between settings is required. This is to avoid invalid calculations. The longer the period, the more precise the resulting drift factor will be. +
+  {nbsp} +
   This option was added in v2.26, because it is typical for systems to call *­hwclock --systohc* at shutdown; with the old behaviour this would automatically (re)calculate the drift factor which caused several problems: +
+  {nbsp} +
   * When using NTP with an ­'11 minute mode' kernel the drift factor would be clobbered to near zero.
   * It would not allow the use of 'cold' drift correction. With most configurations using 'cold' drift will yield favorable results. Cold, means when the machine is turned off which can have a significant impact on the drift factor.
   * (Re)calculating drift factor on every shutdown delivers suboptimal results. For example, if ephemeral conditions cause the machine to be abnormally hot the drift factor calculation would be out of range.

sys-utils/ipcrm.1.adoc

@@ -35,6 +35,7 @@ The details of the removes are described in *shmctl*(2), *msgctl*(2), and *semct
 
 *-a*, *--all* [*shm*] [*msg*] [*sem*]::
   Remove all resources. When an option argument is provided, the removal is performed only for the specified resource types. +
+  {nbsp} +
   _Warning!_ Do not use *-a* if you are unsure how the software using the resources might react to missing objects. Some programs create these resources at startup and may not have any code to deal with an unexpected disappearance.
 
 *-M*, *--shmem-key* _shmkey_::

sys-utils/lscpu.1.adoc

@@ -66,13 +66,13 @@ Note that topology elements (core, socket, etc.) use a sequential unique ID star
 
 *POLARIZATION*::
   This column contains data for Linux instances that run on virtual hardware with a hypervisor that can switch the CPU dispatching mode (polarization). The polarization can be: +
-  
+  {nbsp} +
   *horizontal*;;
-    The workload is spread across all available CPUs.
+  The workload is spread across all available CPUs.
   *vertical*;;
-    The workload is concentrated on few CPUs. +
-+
-For vertical polarization, the column also shows the degree of concentration, high, medium, or low. This column contains data only if your hardware system and hypervisor support CPU polarization.
+  The workload is concentrated on few CPUs. +
+  {nbsp} +
+  For vertical polarization, the column also shows the degree of concentration, high, medium, or low. This column contains data only if your hardware system and hypervisor support CPU polarization.
 
 *MAXMHZ*::
   Maximum megahertz value for the CPU. Useful when *lscpu* is used as hardware inventory information gathering tool. Notice that the megahertz value is dynamic, and driven by CPU governor depending on current resource need.
@@ -93,8 +93,11 @@ For vertical polarization, the column also shows the degree of concentration, hi
 
 *-C*, *--caches*[=_list_]::
   Display details about CPU caches. For details about available information see *--help* output. +
+  {nbsp} +
   If the _list_ argument is omitted, all columns for which data is available are included in the command output. +
+  {nbsp} +
   When specifying the _list_ argument, the string of option, equal sign (=), and _list_ must not contain any blanks or other whitespace. Examples: '*-C=NAME,ONE-SIZE*' or '*--caches=NAME,ONE-SIZE*'. +
+  {nbsp} +
   The default list of columns may be extended if list is specified in the format +list (e.g., lscpu -C=+ALLOC-POLICY).
 
 *-c*, *--offline*::
@@ -102,8 +105,11 @@ For vertical polarization, the column also shows the degree of concentration, hi
 
 *-e*, *--extended*[=_list_]::
   Display the CPU information in human-readable format. +
+  {nbsp} +
   If the _list_ argument is omitted, all columns for which data is available are included in the command output. +
+  {nbsp} +
   When specifying the _list_ argument, the string of option, equal sign (=), and _list_ must not contain any blanks or other whitespace. Examples: '*-e=cpu,node*' or '*--extended=cpu,node*'. +
+  {nbsp} +
   The default list of columns may be extended if list is specified in the format +list (e.g., lscpu -e=+MHZ).
 
 *-h*, *--help*::
@@ -114,8 +120,11 @@ For vertical polarization, the column also shows the degree of concentration, hi
 
 *-p*, *--parse*[=_list_]::
   Optimize the command output for easy parsing. +
+  {nbsp} +
   If the _list_ argument is omitted, the command output is compatible with earlier versions of *lscpu*. In this compatible format, two commas are used to separate CPU cache columns. If no CPU caches are identified the cache column is omitted. If the _list_ argument is used, cache columns are separated with a colon (:). +
+  {nbsp} +
   When specifying the _list_ argument, the string of option, equal sign (=), and _list_ must not contain any blanks or other whitespace. Examples: '*-p=cpu,node*' or '*--parse=cpu,node*'. +
+  {nbsp} +
   The default list of columns may be extended if list is specified in the format +list (e.g., lscpu -p=+MHZ).
 
 *-s*, *--sysroot* _directory_::
@@ -126,6 +135,7 @@ For vertical polarization, the column also shows the degree of concentration, hi
 
 *-y*, *--physical*::
   Display physical IDs for all columns with topology elements (core, socket, etc.). Other than logical IDs, which are assigned by *lscpu*, physical IDs are platform-specific values that are provided by the kernel. Physical IDs are not necessarily unique and they might not be arranged sequentially. If the kernel could not retrieve a physical ID for an element *lscpu* prints the dash (-) character. +
+  {nbsp} +
   The CPU logical numbers are not affected by this option.
 
 *-V*, *--version*::

sys-utils/lsns.8.adoc

@@ -41,6 +41,7 @@ Note that *lsns* reads information directly from the _/proc_ filesystem and for
 
 *-o*, *--output* _list_::
   Specify which output columns to print. Use *--help* to get a list of all supported columns. +
+  {nbsp} +
   The default list of columns may be extended if _list_ is specified in the format **+**__list__ (e.g., *lsns -o +PATH*).
 
 *--output-all*::

sys-utils/mount.8.adoc

@@ -106,6 +106,7 @@ LABEL=__label__::
   Human readable filesystem identifier. See also *-L*.
 UUID=__uuid__::
   Filesystem universally unique identifier. The format of the UUID is usually a series of hex digits separated by hyphens. See also *-U*. +
+  {nbsp} +
   Note that *mount* uses UUIDs as strings. The UUIDs from the command line or from *fstab*(5) are not converted to internal binary representation. The string representation of the UUID should be based on lower case characters.
 PARTLABEL=__label__::
   Human readable partition identifier. This identifier is independent on filesystem and does not change by mkfs or mkswap operations It's supported for example for GUID Partition Tables (GPT).
@@ -295,8 +296,11 @@ Command-line options available for the *mount* command are:
 
 *-a*, *--all*::
   Mount all filesystems (of the given types) mentioned in _fstab_ (except for those whose line contains the *noauto* keyword). The filesystems are mounted following their order in _fstab_. The *mount* command compares filesystem source, target (and fs root for bind mount or btrfs) to detect already mounted filesystems. The kernel table with already mounted filesystems is cached during *mount --all*. This means that all duplicated _fstab_ entries will be mounted. +
+  {nbsp} +
   The option *--all* is possible to use for remount operation too. In this case all filters (*-t* and *-O*) are applied to the table of already mounted filesystems. +
+  {nbsp} +
   Since version 2.35 is possible to use the command line option *-o* to alter mount options from _fstab_ (see also *--options-mode*). +
+  {nbsp} +
   Note that it is a bad practice to use *mount -a* for _fstab_ checking. The recommended solution is *findmnt --verify*.
 
 *-B*, *--bind*::
@@ -304,6 +308,7 @@ Command-line options available for the *mount* command are:
 
 *-c*, *--no-canonicalize*::
   Don't canonicalize paths. The *mount* command canonicalizes all paths (from the command line or _fstab_) by default. This option can be used together with the *-f* flag for already canonicalized absolute paths. The option is designed for mount helpers which call *mount -i*. It is strongly recommended to not use this command-line option for normal mount operations. +
+  {nbsp} +
   Note that *mount* does not pass this option to the **/sbin/mount.**__type__ helpers.
 
 *-F*, *--fork*::
@@ -329,21 +334,31 @@ Command-line options available for the *mount* command are:
 
 *-N*, *--namespace* _ns_::
   Perform the mount operation in the mount namespace specified by _ns_. _ns_ is either PID of process running in that namespace or special file representing that namespace. +
+  {nbsp} +
   *mount* switches to the mount namespace when it reads _/etc/fstab_, writes _/etc/mtab: (or writes to _/run/mount_) and calls the *mount*(2) system call, otherwise it runs in the original mount namespace. This means that the target namespace does not have to contain any libraries or other requirements necessary to execute the *mount*(2) call. +
+  {nbsp} +
   See *mount_namespaces*(7) for more information.
 
 *-O*, *--test-opts* _opts_::
   Limit the set of filesystems to which the *-a* option applies. In this regard it is like the *-t* option except that *-O* is useless without *-a*. For example, the command +
+  {nbsp} +
   *mount -a -O no_netdev* +
+  {nbsp} +
   mounts all filesystems except those which have the option _netdev_ specified in the options field in the _/etc/fstab_ file. +
+  {nbsp} +
   It is different from *-t* in that each option is matched exactly; a leading *no* at the beginning of one option does not negate the rest. +
+  {nbsp} +
   The *-t* and *-O* options are cumulative in effect; that is, the command +
+  {nbsp} +
   *mount -a -t ext2 -O  _netdev* +
+  {nbsp} +
   mounts all ext2 filesystems with the _netdev option, not all filesystems that are either ext2 or have the _netdev option specified.
 
 *-o*, *--options* _opts_::
   Use the specified mount options. The _opts_ argument is a comma-separated list. For example: +
+  {nbsp} +
   *mount LABEL=mydisk -o noatime,nodev,nosuid* +
+  {nbsp} +
   For more details, see the *FILESYSTEM-INDEPENDENT MOUNT OPTIONS* and *FILESYSTEM-SPECIFIC MOUNT OPTIONS* sections.
 
 *--options-mode* _mode_::
@@ -360,6 +375,7 @@ Command-line options available for the *mount* command are:
 
 *-r*, *--read-only*::
   Mount the filesystem read-only. A synonym is *-o ro*. +
+  {nbsp} +
   Note that, depending on the filesystem type, state and kernel behavior, the system may still write to the device. For example, ext3 and ext4 will replay the journal if the filesystem is dirty. To prevent this kind of write access, you may want to mount an ext3 or ext4 filesystem with the *ro,noload* mount options or set the block device itself to read-only mode, see the *blockdev*(8) command.
 
 *-s*::
@@ -373,22 +389,33 @@ Command-line options available for the *mount* command are:
 
 *--target-prefix* _directory_::
   Prepend the specified directory to all mount targets. This option can be used to follow _fstab_, but mount operations are done in another place, for example: +
+  {nbsp} +
   *mount --all --target-prefix /chroot -o X-mount.mkdir* +
+  {nbsp} +
   mounts all from system _fstab_ to `/chroot`, all missing mountpoint are created (due to X-mount.mkdir). See also *--fstab* to use an alternative _fstab_.
 
 *-T*, *--fstab* _path_::
   Specifies an alternative _fstab_ file. If _path_ is a directory, then the files in the directory are sorted by *strverscmp*(3); files that start with "." or without an _.fstab_ extension are ignored. The option can be specified more than once. This option is mostly designed for initramfs or chroot scripts where additional configuration is specified beyond standard system configuration. +
+  {nbsp} +
   Note that *mount* does not pass the option *--fstab* to the **/sbin/mount.**__type__ helpers, meaning that the alternative _fstab_ files will be invisible for the helpers. This is no problem for normal mounts, but user (non-root) mounts always require _fstab_ to verify the user's rights.
 
 *-t*, *--types* _fstype_::
   The argument following the *-t* is used to indicate the filesystem type. The filesystem types which are currently supported depend on the running kernel. See _/proc/filesystems_ and _/lib/modules/$(uname -r)/kernel/fs_ for a complete list of the filesystems. The most common are ext2, ext3, ext4, xfs, btrfs, vfat, sysfs, proc, nfs and cifs. +
+  {nbsp} +
   The programs *mount* and *umount*(8) support filesystem subtypes. The subtype is defined by a '.subtype' suffix. For example 'fuse.sshfs'. It's recommended to use subtype notation rather than add any prefix to the mount source (for example 'sshfs#example.com' is deprecated). +
+  {nbsp} +
   If no *-t* option is given, or if the *auto* type is specified, *mount* will try to guess the desired type. *mount* uses the *libblkid*(3) library for guessing the filesystem type; if that does not turn up anything that looks familiar, *mount* will try to read the file _/etc/filesystems_, or, if that does not exist, _/proc/filesystems_. All of the filesystem types listed there will be tried, except for those that are labeled "nodev" (e.g. _devpts_, _proc_ and _nfs_). If _/etc/filesystems_ ends in a line with a single +++*+++, mount will read _/proc/filesystems_ afterwards. While trying, all filesystem types will be mounted with the mount option *silent*. +
+  {nbsp} +
   The *auto* type may be useful for user-mounted floppies. Creating a file _/etc/filesystems_ can be useful to change the probe order (e.g., to try vfat before msdos or ext3 before ext2) or if you use a kernel module autoloader. +
+  {nbsp} +
   More than one type may be specified in a comma-separated list, for the *-t* option as well as in an _/etc/fstab_ entry. The list of filesystem types for the *-t* option can be prefixed with *no* to specify the filesystem types on which no action should be taken. The prefix *no* has no effect when specified in an _/etc/fstab_ entry. +
+  {nbsp} +
   The prefix *no* can be meaningful with the *-a* option. For example, the command +
+  {nbsp} +
   *mount -a -t nomsdos,smbfs* +
+  {nbsp} +
   mounts all filesystems except those of type _msdos_ and _smbfs_. +
+  {nbsp} +
   For most types all the *mount* program has to do is issue a simple *mount*(2) system call, and no detailed knowledge of the filesystem type is required. For a few types however (like nfs, nfs4, cifs, smbfs, ncpfs) an ad hoc code is necessary. The nfs, nfs4, cifs, smbfs, and ncpfs filesystems have a separate mount program. In order to make it possible to treat all types in a uniform way, *mount* will execute the program **/sbin/mount.**__type__ (if that exists) when called with type _type_. Since different versions of the *smbmount* program have different calling conventions, */sbin/mount.smbfs* may have to be a shell script that sets up the desired call.
 
 *-U*, *--uuid* _uuid_::
@@ -399,7 +426,9 @@ Command-line options available for the *mount* command are:
 
 *-w*, *--rw*, *--read-write*::
   Mount the filesystem read/write. Read-write is the kernel default and the *mount* default is to try read-only if the previous mount syscall with read-write flags on write-protected devices of filesystems failed. +
+  {nbsp} +
   A synonym is *-o rw*. +
+  {nbsp} +
   Note that specifying *-w* on the command line forces *mount* to never try read-only mount on write-protected devices or already mounted read-only filesystems.
 
 *-V*, *--version*::
@@ -433,19 +462,30 @@ The following options apply to any filesystem that is being mounted (but not eve
 
 **context=**__context__, **fscontext=**__context__, **defcontext=**__context__, and **­rootcontext=**__context__::
   The *context=* option is useful when mounting filesystems that do not support extended attributes, such as a floppy or hard disk formatted with VFAT, or systems that are not normally running under SELinux, such as an ext3 or ext4 formatted disk from a non-SELinux workstation. You can also use *context=* on filesystems you do not trust, such as a floppy. It also helps in compatibility with xattr-supporting filesystems on earlier 2.4.<x> kernel versions. Even where xattrs are supported, you can save time not having to label every file by assigning the entire disk one security context. +
+  {nbsp} +
   A commonly used option for removable media is *­context="system_u:object_r:removable_t*. +
+  {nbsp} +
   Two other options are *fscontext=* and *defcontext=*, both of which are mutually exclusive of the *context=* option. This means you can use fscontext and defcontext with each other, but neither can be used with context. +
+  {nbsp} +
   The *fscontext=* option works for all filesystems, regardless of their xattr support. The fscontext option sets the overarching filesystem label to a specific security context. This filesystem label is separate from the individual labels on the files. It represents the entire filesystem for certain kinds of permission checks, such as during mount or file creation. Individual file labels are still obtained from the xattrs on the files themselves. The context option actually sets the aggregate context that fscontext provides, in addition to supplying the same label for individual files. +
+  {nbsp} +
   You can set the default security context for unlabeled files using *defcontext=* option. This overrides the value set for unlabeled files in the policy and requires a filesystem that supports xattr labeling. +
+  {nbsp} +
   The *rootcontext=* option allows you to explicitly label the root inode of a FS being mounted before that FS or inode becomes visible to userspace. This was found to be useful for things like stateless Linux. +
+  {nbsp} +
   Note that the kernel rejects any remount request that includes the context option, *even* when unchanged from the current context. +
+  {nbsp} +
   *Warning: the* _context_ *value might contain commas*, in which case the value has to be properly quoted, otherwise mount8 will interpret the comma as a separator between mount options. Don't forget that the shell strips off quotes and thus *double quoting is required*. For example: +
+  {nbsp} +
   mount -t tmpfs none /mnt -o \ +
+  {nbsp} +
   'context="system_u:object_r:tmp_t:s0:c127,c456",noexec' +
+  {nbsp} +
   For more details, see *selinux*(8).
 
 *defaults*::
   Use the default options: *rw*, *suid*, *dev*, *exec*, *auto*, *nouser*, and *async*. +
+  {nbsp} +
   Note that the real set of all default mount options depends on the kernel and filesystem type. See the beginning of this section for more details.
 
 *dev*::
@@ -492,6 +532,7 @@ The following options apply to any filesystem that is being mounted (but not eve
 
 *relatime*::
   Update inode access times relative to modify or change time. Access time is only updated if the previous access time was earlier than the current modify or change time. (Similar to *­noatime*, but it doesn't break *mutt*(1) or other applications that need to know if a file has been read since the last time it was modified.) +
+  {nbsp} +
   Since Linux 2.6.30, the kernel defaults to the behavior provided by this option (unless *­noatime* was specified), and the *­strictatime* option is required to obtain traditional semantics. In addition, since Linux 2.6.30, the file's last access time is always updated if it is more than 1 day old.
 
 *norelatime*::
@@ -505,8 +546,11 @@ The following options apply to any filesystem that is being mounted (but not eve
 
 *lazytime*::
   Only update times (atime, mtime, ctime) on the in-memory version of the file inode. +
+  {nbsp} +
   This mount option significantly reduces writes to the inode table for workloads that perform frequent random writes to preallocated files. +
+  {nbsp} +
   The on-disk timestamps are updated only when: +
+  {nbsp} +
     * the inode needs to be updated for some change unrelated to file timestamps
     * the application employs *fsync*(2), *syncfs*(2), or *sync*(2)
     * an undeleted inode is evicted from memory
@@ -532,14 +576,23 @@ The following options apply to any filesystem that is being mounted (but not eve
 
 *remount*::
   Attempt to remount an already-mounted filesystem. This is commonly used to change the mount flags for a filesystem, especially to make a readonly filesystem writable. It does not change device or mount point. +
+  {nbsp} +
   The remount operation together with the *bind* flag has special semantics. See above, the subsection *Bind mounts*. +
+  {nbsp} +
   The remount functionality follows the standard way the *mount* command works with options from _fstab_. This means that *mount* does not read _fstab_ (or _mtab_) only when both _device_ and _dir_ are specified. +
-   *mount -o remount,rw /dev/foo /dir* +
+  {nbsp} +
+  *mount -o remount,rw /dev/foo /dir* +
+  {nbsp} +
   After this call all old mount options are replaced and arbitrary stuff from _fstab_ (or _mtab_) is ignored, except the loop= option which is internally generated and maintained by the mount command. +
-   *mount -o remount,rw /dir* +
+  {nbsp} +
+  *mount -o remount,rw /dir* +
+  {nbsp} +
   After this call, mount reads _fstab_ and merges these options with the options from the command line (*-o*). If no mountpoint is found in _fstab_, then a remount with unspecified source is allowed. +
+  {nbsp} +
   *mount* allows the use of *--all* to remount all already mounted filesystems which match a specified filter (*-O* and *-t*). For example: +
-   *mount --all -o remount,ro -t vfat* +
+  {nbsp} +
+  *mount --all -o remount,ro -t vfat* +
+  {nbsp} +
   remounts all already mounted vfat filesystems in read-only mode. Each of the filesystems is remounted by *mount -o remount,ro /dir* semantic. This means the *mount* command reads _fstab_ or _mtab_ and merges these options with the options from the command line.
 
 *ro*::
@@ -565,6 +618,7 @@ The following options apply to any filesystem that is being mounted (but not eve
 
 *x-**::
   The same as *X-** options, but stored permanently in user space. This means the options are also available for *umount*(8) or other operations. Note that maintaining mount options in user space is tricky, because it's necessary use libmount-based tools and there is no guarantee that the options will be always available (for example after a move mount operation or in unshared namespace). +
+  {nbsp} +
   Note that before util-linux v2.30 the x-* options have not been maintained by libmount and stored in user space (functionality was the same as for X-* now), but due to the growing number of use-cases (in initrd, systemd etc.) the functionality has been extended to keep existing _fstab_ configurations usable without a change.
 
 *X-mount.mkdir*[=_mode_]::
@@ -663,14 +717,20 @@ The devpts filesystem is a pseudo filesystem, traditionally mounted on _/dev/pts
 
 *newinstance*::
   Create a private instance of the devpts filesystem, such that indices of pseudo terminals allocated in this new instance are independent of indices created in other instances of devpts. +
+  {nbsp} +
   All mounts of devpts without this *newinstance* option share the same set of pseudo terminal indices (i.e., legacy mode). Each mount of devpts with the *newinstance* option has a private set of pseudo terminal indices. +
+  {nbsp} +
   This option is mainly used to support containers in the Linux kernel. It is implemented in Linux kernel versions starting with 2.6.29. Further, this mount option is valid only if *CONFIG_DEVPTS_MULTIPLE_INSTANCES* is enabled in the kernel configuration. +
+  {nbsp} +
   To use this option effectively, _/dev/ptmx_ must be a symbolic link to _pts/ptmx_. See _Documentation/filesystems/devpts.txt_ in the Linux kernel source tree for details.
 
 **ptmxmode=**__value__::
   Set the mode for the new _ptmx_ device node in the devpts filesystem. +
+  {nbsp} +
   With the support for multiple instances of devpts (see *newinstance* option above), each instance has a private _ptmx_ node in the root of the devpts filesystem (typically _/dev/pts/ptmx_). +
+  {nbsp} +
   For compatibility with older versions of the kernel, the default mode of the new _ptmx_ node is 0000. **ptmxmode=**__value__ specifies a more useful mode for the _ptmx_ node and is highly recommended when the *newinstance* option is specified. +
+  {nbsp} +
   This option is only implemented in Linux kernel versions starting with 2.6.29. Further, this option is valid only if *CONFIG_DEVPTS_MULTIPLE_INSTANCES* is enabled in the kernel configuration.
 
 === Mount options for fat
@@ -694,6 +754,7 @@ The devpts filesystem is a pseudo filesystem, traditionally mounted on _/dev/pts
 
 **allow_utime=**__value__::
   This option controls the permission check of mtime/atime. +
+  {nbsp} +
   * *20*
     If current process is in group of file's group ID, you can change timestamp.
   * *2*
@@ -705,6 +766,7 @@ Normally *utime*(2) checks that the current process is owner of the file, or tha
 
 **check=**__value__::
   Three different levels of pickiness can be chosen: +
+  {nbsp} +
   * *r*[*elaxed*]
     Upper and lower case are accepted and equivalent, long name parts are truncated (e.g. _verylongname.foobar_ becomes _verylong.foo_), leading and embedded spaces are accepted in each name part (name and extension).
   * *n*[*ormal*]
@@ -744,8 +806,11 @@ Normally *utime*(2) checks that the current process is owner of the file, or tha
 
 *nfs=*{**stale_rw**|*nostale_ro*}::
   Enable this only if you want to export the FAT filesystem over NFS. +
+  {nbsp} +
   *stale_rw*: This option maintains an index (cache) of directory inodes which is used by the nfs-related code to improve look-ups. Full file operations (read/write) over NFS are supported but with cache eviction at NFS server, this could result in spurious *ESTALE* errors. +
+  {nbsp} +
   *nostale_ro*: This option bases the inode number and file handle on the on-disk location of a file in the FAT directory entry. This ensures that *ESTALE* will not be returned after a file is evicted from the inode cache. However, it means that operations such as rename, create and unlink could cause file handles that previously pointed at one file to point at a different file, potentially causing data corruption. For this reason, this option also mounts the filesystem readonly +
+  {nbsp} +
   To maintain backward compatibility, *-o nfs* is also accepted, defaulting to *stale_rw*.
 
 *tz=UTC*::
@@ -759,6 +824,7 @@ Normally *utime*(2) checks that the current process is owner of the file, or tha
 
 *rodir*::
   FAT has the *ATTR_RO* (read-only) attribute. On Windows, the *ATTR_RO* of the directory will just be ignored, and is used only by applications as a flag (e.g. it's set for the customized folder). +
+  {nbsp} +
   If you want to use *ATTR_RO* as read-only flag even for the directory, set this option.
 
 *showexec*::
@@ -948,6 +1014,7 @@ Reiserfs is a journaling filesystem.
 
 *hash=*{**rupasov**|**tea**|**r5**|*detect*}::
   Choose which hash function reiserfs will use to find files within directories. +
+  {nbsp} +
   * *rupasov*
     A hash invented by Yury Yu. Rupasov. It is fast and preserves locality, mapping lexicographically close file names to close hash values. This option should not be used, as it causes a high probability of hash collisions.
   * *tea*
@@ -1044,6 +1111,7 @@ UDF is the "Universal Disk Format" filesystem defined by OSTA, the Optical Stora
 
 *bs=*::
   Set the block size. Default value prior to kernel version 2.6.30 was 2048. Since 2.6.30 and prior to 4.11 it was logical device block size with fallback to 2048. Since 4.11 it is logical block size with fallback to any valid block size between logical device block size and 4096. +
+  {nbsp} +
   For other details see the mkudffs8 2.0+ manpage, sections *COMPATIBILITY* and *BLOCK SIZE*.
 
 *unhide*::
@@ -1111,6 +1179,7 @@ UDF is the "Universal Disk Format" filesystem defined by OSTA, the Optical Stora
 
 **ufstype=**__value__::
   UFS is a filesystem widely used in different operating systems. The problem are differences among implementations. Features of some implementations are undocumented, so its hard to recognize the type of ufs automatically. That's why the user must specify the type of ufs by mount option. Possible values are: +
+  {nbsp} +
   * *old*
     Old format of ufs, this is the default, read only. (Don't forget to give the *-r* option.)
   * *44bsd*
@@ -1134,6 +1203,7 @@ UDF is the "Universal Disk Format" filesystem defined by OSTA, the Optical Stora
 
 **onerror=**__value__::
   Set behavior on error: +
+  {nbsp} +
   * *panic*
     If an error is encountered, cause a kernel panic.
   * [**lock**|**umount**|*repair*]
@@ -1161,6 +1231,7 @@ First of all, the mount options for _fat_ are recognized. The *dotsOK* option is
 
 **shortname=**__mode__::
   Defines the behavior for creation and display of filenames which fit into 8.3 characters. If a long name for a file exists, it will always be the preferred one for display. There are four __mode__s: +
+  {nbsp} +
   * *lower*
     Force the short name to lower case upon display; store a long name when the short name is not all upper case.
   * *win95*
@@ -1284,6 +1355,7 @@ Since util-linux v2.29, *mount* re-uses the loop device rather than initializing
 
 *64*::
   some mount succeeded +
+  {nbsp} +
   The command *mount -a* returns 0 (all succeeded), 32 (all failed), or 64 (some failed, some succeeded).
 
 == EXTERNAL HELPERS

sys-utils/nsenter.1.adoc

@@ -49,10 +49,12 @@ Various of the options below that relate to namespaces take an optional _file_ a
 
 *-a*, *--all*::
   Enter all namespaces of the target process by the default _/proc/[pid]/ns/+++*+++_ namespace paths. The default paths to the target process namespaces may be overwritten by namespace specific options (e.g., *--all --mount*=[_path_]). +
+  {nbsp} +
   The user namespace will be ignored if the same as the caller's current user namespace. It prevents a caller that has dropped capabilities from regaining those capabilities via a call to setns(). See *setns*(2) for more details.
 
 *-t*, *--target* _PID_::
   Specify a target process to get contexts from. The paths to the contexts specified by _pid_ are: +
+  {nbsp} +
 ____
   /proc/_pid_/ns/mnt;;
     the mount namespace

sys-utils/rtcwake.8.adoc

@@ -36,18 +36,19 @@ The suspend setup may be interrupted by active hardware; for example wireless US
   Read the clock mode (whether the hardware clock is set to UTC or local time) from the _adjtime_ file, where *hwclock*(8) stores that information. This is the default.
 
 *--date* _timestamp_::
-  Set the wakeup time to the value of the timestamp. Format of the timestamp can be any of the following: +
-  [cols=",",]
-  |===
-  |YYYYMMDDhhmmss |
-  |YYYY-MM-DD hh:mm:ss |
-  |YYYY-MM-DD hh:mm |(seconds will be set to 00)
-  |YYYY-MM-DD |(time will be set to 00:00:00)
-  |hh:mm:ss |(date will be set to today)
-  |hh:mm |(date will be set to today, seconds to 00)
-  |tomorrow |(time is set to 00:00:00)
-  |+5min |
-  |===
+  Set the wakeup time to the value of the timestamp. Format of the timestamp can be any of the following:
+
+[cols=",",]
+|===
+|YYYYMMDDhhmmss |
+|YYYY-MM-DD hh:mm:ss |
+|YYYY-MM-DD hh:mm |(seconds will be set to 00)
+|YYYY-MM-DD |(time will be set to 00:00:00)
+|hh:mm:ss |(date will be set to today)
+|hh:mm |(date will be set to today, seconds to 00)
+|tomorrow |(time is set to 00:00:00)
+|+5min |
+|===
 
 *-d*, *--device* _device_::
   Use the specified _device_ instead of *rtc0* as realtime clock. This option is only relevant if your system has more than one RTC. You may specify *rtc1*, *rtc2*, ... here.

sys-utils/setpriv.1.adoc

@@ -34,11 +34,15 @@ In comparison to *su*(1) and *runuser*(1), *setpriv* neither uses PAM, nor does
 *--ambient-caps* (*+*|*-*)_cap_...::
 *--bounding-set* (*+*|*-*)_cap_...::
   Set the inheritable capabilities, ambient capabilities or the capability bounding set. See *capabilities*(7). The argument is a comma-separated list of **+**__cap__ and **-**__cap__ entries, which add or remove an entry respectively. _cap_ can either be a human-readable name as seen in *capabilities*(7) without the _cap__ prefix or of the format *cap_N*, where _N_ is the internal capability index used by Linux. *+all* and *-all* can be used to add or remove all caps. +
+  {nbsp} +
   The set of capabilities starts out as the current inheritable set for *--inh-caps*, the current ambient set for *--ambient-caps* and the current bounding set for *--bounding-set*. +
+  {nbsp} +
   Note the following restrictions (detailed in *capabilities*(7)) regarding modifications to these capability sets: +
+  {nbsp} +
   * A capability can be added to the inheritable set only if it is currently present in the bounding set.
   * A capability can be added to the ambient set only if it is currently present in both the permitted and inheritable sets.
   * Notwithstanding the syntax offered by *setpriv*, the kernel does not permit capabilities to be added to the bounding set. +
+  {nbsp} +
   If you drop a capability from the bounding set without also dropping it from the inheritable set, you are likely to become confused. Do not do that.
 
 *--keep-groups*::
@@ -52,15 +56,19 @@ In comparison to *su*(1) and *runuser*(1), *setpriv* neither uses PAM, nor does
 
 *--no-new-privs*::
   Set the _no_new_privs_ bit. With this bit set, *execve*(2) will not grant new privileges. For example, the set-user-ID and set-group-ID bits as well as file capabilities will be disabled. (Executing binaries with these bits set will still work, but they will not gain privileges. Certain LSMs, especially AppArmor, may result in failures to execute certain programs.) This bit is inherited by child processes and cannot be unset. See *prctl*(2) and _Documentation/prctl/no_new_privs.txt_ in the Linux kernel source. +
+  {nbsp} +
   The _no_new_privs_ bit is supported since Linux 3.5.
 
 *--rgid* _gid_, *--egid* _gid_, *--regid* _gid_::
   Set the real, effective, or both GIDs. The _gid_ argument can be given as a textual group name. +
+  {nbsp} +
   For safety, you must specify one of *--clear-groups*, *--groups*, *--keep-groups*, or *--init-groups* if you set any primary _gid_.
 
 *--ruid* _uid_, *--euid* _uid_, *--reuid* _uid_::
   Set the real, effective, or both UIDs. The _uid_ argument can be given as a textual login name. +
+  {nbsp} +
   Setting a _uid_ or _gid_ does not change capabilities, although the exec call at the end might change capabilities. This means that, if you are root, you probably want to do something like: +
+  {nbsp} +
   *setpriv --reuid=1000 --regid=1000 --inh-caps=-all*
 
 *--securebits* (**+**|*-*)__securebit__...::
@@ -77,6 +85,7 @@ In comparison to *su*(1) and *runuser*(1), *setpriv* neither uses PAM, nor does
 
 *--reset-env*::
   Clears all the environment variables except *TERM*; initializes the environment variables *HOME*, *SHELL*, *USER*, *LOGNAME* according to the user's passwd entry; sets *PATH* to _/usr/local/bin:/bin:/usr/bin_ for a regular user and to _/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin_ for root. +
+  {nbsp} +
   The environment variable *PATH* may be different on systems where _/bin_ and _/sbin_ are merged into _/usr_. The environment variable *SHELL* defaults to */bin/sh* if none is given in the user's passwd entry.
 
 *-V*, *--version*::

sys-utils/swapon.8.adoc

@@ -52,7 +52,9 @@ If no policy is selected, the default behavior is to enable both discard types.
 
 *-o*, *--options* _opts_::
   Specify swap options by an fstab-compatible comma-separated string. For example: +
+  {nbsp} +
   *swapon -o pri=1,discard=pages,nofail /dev/sda2* +
+  {nbsp} +
   The _opts_ string is evaluated last and overrides all other command line options.
 
 *-p*, *--priority* _priority_::
@@ -109,7 +111,9 @@ If no policy is selected, the default behavior is to enable both discard types.
 
 *64*::
   some swapoff succeeded on *--all* +
+  {nbsp} +
   The command *swapoff --all* returns 0 (all succeeded), 32 (all failed), or 64 (some failed, some succeeded). +
+  {nbsp} +
   The old versions before v2.36 has no documented exit status, 0 means success in all versions.
 
 == ENVIRONMENT

sys-utils/tunelp.8.adoc

@@ -21,6 +21,7 @@ tunelp - set various parameters for the lp device
 
 *-i*, *--irq* _argument_::
   specifies the IRQ to use for the parallel port in question. If this is set to something non-zero, *-t* and *-c* have no effect. If your port does not use interrupts, this option will make printing stop. The command *tunelp -i 0* restores non-interrupt driven (polling) action, and your printer should work again. If your parallel port does support interrupts, interrupt-driven printing should be somewhat faster and efficient, and will probably be desirable. +
+  {nbsp} +
   NOTE: This option will have no effect with kernel 2.1.131 or later since the irq is handled by the parport driver. You can change the parport irq for example via _/proc/parport/*/irq_. Read _/usr/src/linux/Documentation/admin-guide/parport.rst_ for more details on parport.
 
 *-t*, *--time* _milliseconds_::
@@ -28,6 +29,7 @@ tunelp - set various parameters for the lp device
 
 *-c*, *--chars* _characters_::
   is the number of times to try to output a character to the printer before sleeping for *-t* _TIME_. It is the number of times around a loop that tries to send a character to the printer. 120 appears to be a good value for most printers in polling mode. 1000 is the default, because there are some printers that become jerky otherwise, but you _must_ set this to `1' to handle the maximal CPU efficiency if you are using interrupts. If you have a very fast printer, a value of 10 might make more sense even if in polling mode. If you have a _really_ old printer, you can increase this further. +
+  {nbsp} +
   Setting *-t* _TIME_ to 0 is equivalent to setting *-c* _CHARS_ to infinity.
 
 *-w*, *--wait* _milliseconds_::
@@ -41,6 +43,7 @@ tunelp - set various parameters for the lp device
 
 *-C*, *--careful* _<on|off>_::
   This option adds extra ("careful") error checking. When this option is on, the printer driver will ensure that the printer is on-line and not reporting any out of paper or other errors before sending data. This is particularly useful for printers that normally appear to accept data when turned off. +
+  {nbsp} +
   *NOTE*: This option is obsolete because it's the default in 2.1.131 kernel or later.
 
 *-s*, *--status*::

sys-utils/umount.8.adoc

@@ -58,7 +58,9 @@ Note that a filesystem cannot be unmounted when it is 'busy' - for example, when
 
 *-c*, *--no-canonicalize*::
   Do not canonicalize paths. The paths canonicalization is based on *stat*(2) and *readlink*(2) system calls. These system calls may hang in some cases (for example on NFS if server is not available). The option has to be used with canonical path to the mount point. +
+  {nbsp} +
   This option is silently ignored by *umount* for non-root users. +
+  {nbsp} +
   For more details about this option see the *mount*(8) man page. Note that *umount* does not pass this option to the **/sbin/umount.**__type__ helpers.
 
 *-d*, *--detach-loop*::
@@ -69,6 +71,7 @@ Note that a filesystem cannot be unmounted when it is 'busy' - for example, when
 
 *-f*, *--force*::
   Force an unmount (in case of an unreachable NFS system). +
+  {nbsp} +
   Note that this option does not guarantee that umount command does not hang. It's strongly recommended to use absolute paths without symlinks to avoid unwanted readlink and stat system calls on unreachable NFS in *umount*.
 
 *-i*, *--internal-only*::
@@ -76,11 +79,14 @@ Note that a filesystem cannot be unmounted when it is 'busy' - for example, when
 
 *-l*, *--lazy*::
   Lazy unmount. Detach the filesystem from the file hierarchy now, and clean up all references to this filesystem as soon as it is not busy anymore. +
+  {nbsp} +
   A system reboot would be expected in near future if you're going to use this option for network filesystem or local filesystem with submounts. The recommended use-case for *umount -l* is to prevent hangs on shutdown due to an unreachable network share where a normal umount will hang due to a downed server or a network partition. Remounts of the share will not be possible.
 
 *-N*, *--namespace* _ns_::
   Perform umount in the mount namespace specified by _ns_. _ns_ is either PID of process running in that namespace or special file representing that namespace. +
+  {nbsp} +
   *umount* switches to the namespace when it reads _/etc/fstab_, writes _/etc/mtab_ (or writes to _/run/mount_) and calls *umount*(2) system call, otherwise it runs in the original namespace. It means that the target mount namespace does not have to contain any libraries or other requirements necessary to execute *umount*(2) command. +
+  {nbsp} +
   See *mount_namespaces*(7) for more information.
 
 *-n*, *--no-mtab*::

sys-utils/unshare.1.adoc

@@ -25,6 +25,7 @@ The following types of namespaces can be created with *unshare*:
 
 *mount namespace*::
   Mounting and unmounting filesystems will not affect the rest of the system, except for filesystems which are explicitly marked as shared (with *mount --make-shared*; see _/proc/self/mountinfo_ or *findmnt -o+PROPAGATION* for the *shared* flags). For further details, see *mount_namespaces*(7). +
+  {nbsp} +
   *unshare* since util-linux version 2.27 automatically sets propagation to *private* in a new mount namespace to make sure that the new namespace is really unshared. It's possible to disable this feature with option *--propagation unchanged*. Note that *private* is the kernel default.
 
 *UTS namespace*::
@@ -61,6 +62,7 @@ The following types of namespaces can be created with *unshare*:
 
 *-p*, *--pid*[**=**__file__]::
   Unshare the PID namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. (Creation of a persistent PID namespace will fail if the *--fork* option is not also specified.) +
+  {nbsp} +
   See also the *--fork* and *--mount-proc* options.
 
 *-u*, *--uts*[**=**__file__]::
@@ -104,6 +106,7 @@ The following types of namespaces can be created with *unshare*:
 
 **--setgroups allow**|*deny*::
   Allow or deny the *setgroups*(2) system call in a user namespace. +
+  {nbsp} +
   To be able to call *setgroups*(2), the calling process must at least have *CAP_SETGID*. But since Linux 3.19 a further restriction applies: the kernel gives permission to call ­*setgroups*(2) only after the GID map (**/proc/**__pid__*/gid_map*) has been set. The GID map is writable by root when ­*setgroups*(2) is enabled (i.e., *allow*, the default), and the GID map becomes writable by unprivileged processes when ­*setgroups*(2) is permanently disabled (with *deny*).
 
 *-R*, **--root=**__dir__::

sys-utils/zramctl.8.adoc

@@ -60,6 +60,7 @@ Note that _zramdev_ node specified on command line has to already exist. The com
 
 *-s*, *--size* _size_::
   Create a zram device of the specified _size_. Zram devices are aligned to memory pages; when the requested _size_ is not a multiple of the page size, it will be rounded up to the next multiple. When not otherwise specified, the unit of the _size_ parameter is bytes. +
+  {nbsp} +
   The _size_ argument may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB") or the suffixes KB (=1000), MB (=1000*1000), and so on for GB, TB, PB, EB, ZB and YB.
 
 *-t*, *--streams* _number_::

term-utils/agetty.8.adoc

@@ -35,61 +35,70 @@ This program does not use the _/etc/gettydefs_ (System V) or _/etc/gettytab_ (Su
 
 _port_::
   A path name relative to the `/dev` directory. If a "-" is specified, *agetty* assumes that its standard input is already connected to a tty port and that a connection to a remote user has already been established. +
+  {nbsp} +
   Under System V, a "-" _port_ argument should be preceded by a "--".
 
 _baud_rate_,...::
   A comma-separated list of one or more baud rates. Each time *agetty* receives a BREAK character it advances through the list, which is treated as if it were circular. +
+  {nbsp} +
   Baud rates should be specified in descending order, so that the null character (Ctrl-@) can also be used for baud-rate switching. +
+  {nbsp} +
   This argument is optional and unnecessary for *virtual terminals*. +
+  {nbsp} +
   The default for *serial terminals* is keep the current baud rate (see *--keep-baud*) and if unsuccessful then default to '9600'.
 
 _term_::
   The value to be used for the *TERM* environment variable. This overrides whatever *init*(1) may have set, and is inherited by login and the shell. +
+  {nbsp} +
   The default is 'vt100', or 'linux' for Linux on a virtual terminal, or 'hurd' for GNU Hurd on a virtual terminal.
 
 == OPTIONS
 
--8, --8bits::
+*-8*, *--8bits*::
   Assume that the tty is 8-bit clean, hence disable parity detection.
 
--a, --autologin _username_::
+*-a*, *--autologin* _username_::
   Automatically log in the specified user without asking for a username or password. Using this option causes an *-f* _username_ option and argument to be added to the */bin/login* command line. See *--login-options*, which can be used to modify this option's behavior. +
+  {nbsp} +
   Note that *--autologin* may affect the way in which *getty* initializes the serial line, because on auto-login *agetty* does not read from the line and it has no opportunity optimize the line setting.
 
--c, --noreset::
+*-c*, *--noreset*::
   Do not reset terminal cflags (control modes). See *termios*(3) for more details.
 
--E, --remote::
-  Typically the login1 command is given a remote hostname when called by something such as telnetd8. This option allows *agetty* to pass what it is using for a hostname to *login*(1) for use in *utmp*(5). See *--host*, *login*(1), and *utmp*(5). +
+*-E*, *--remote*::
+  Typically the *login*(1) command is given a remote hostname when called by something such as *telnetd*(8). This option allows *agetty* to pass what it is using for a hostname to *login*(1) for use in *utmp*(5). See *--host*, *login*(1), and *utmp*(5). +
+  {nbsp} +
   If the *--host* _fakehost_ option is given, then an *-h* _fakehost_ option and argument are added to the _/bin/login_ command line. +
+  {nbsp} +
   If the *--nohostname* option is given, then an *-H* option is added to the */bin/login* command line. +
+  {nbsp} +
   See *--login-options*.
 
--f, --issue-file _path_::
+*-f*, *--issue-file* _path_::
   Specifies a ":" delimited list of files and directories to be displayed instead of _/etc/issue_ (or other). All specified files and directories are displayed, missing or empty files are silently ignored. If the specified path is a directory then display all files with .issue file extension in version-sort order from the directory. This allows custom messages to be displayed on different terminals. The *--noissue* option will override this option.
 
---show-issue::
+*--show-issue*::
   Display the current issue file (or other) on the current terminal and exit. Use this option to review the current setting, it is not designed for any other purpose. Note that output may use some default or incomplete information as proper output depends on terminal and agetty command line.
 
--h, --flow-control::
+*-h, --flow-control*::
   Enable hardware (RTS/CTS) flow control. It is left up to the application to disable software (XON/XOFF) flow protocol where appropriate.
 
--H, --host _fakehost_::
+*-H*, *--host* _fakehost_::
   Write the specified _fakehost_ into the utmp file. Normally, no login host is given, since *agetty* is used for local hardwired connections and consoles. However, this option can be useful for identifying terminal concentrators and the like.
 
--i, --noissue::
+*-i*, *--noissue*::
   Do not display the contents of _/etc/issue_ (or other) before writing the login prompt. Terminals or communications hardware may become confused when receiving lots of text at the wrong baud rate; dial-up scripts may fail if the login prompt is preceded by too much text.
 
--I, --init-string _initstring_::
+*-I*, *--init-string* _initstring_::
   Set an initial string to be sent to the tty or modem before sending anything else. This may be used to initialize a modem. Non-printable characters may be sent by writing their octal code preceded by a backslash (\). For example, to send a linefeed character (ASCII 10, octal 012), write \12.
 
--J, --noclear::
+*-J*, *--noclear*::
   Do not clear the screen before prompting for the login name. By default the screen is cleared.
 
--l, --login-program _login_program_::
+*-l*, *--login-program* _login_program_::
   Invoke the specified _login_program_ instead of /bin/login. This allows the use of a non-standard login program. Such a program could, for example, ask for a dial-up password or use a different password file. See *--login-options*.
 
--L, --local-line[=__mode__]::
+*-L*, *--local-line*[=__mode__]::
   Control the CLOCAL line flag. The optional _mode_ argument is 'auto', 'always' or 'never'. If the _mode_ argument is omitted, then the default is 'always'. If the *--local-line* option is not given at all, then the default is 'auto'.
 
 ____
@@ -101,77 +110,81 @@ _auto_::
   The *agetty* default. Does not modify the CLOCAL setting and follows the setting enabled by the kernel.
 ____
 
--m, --extract-baud::
+*-m*, *--extract-baud*::
   Try to extract the baud rate from the CONNECT status message produced by Hayes(tm)-compatible modems. These status messages are of the form: "<junk><speed><junk>". *agetty* assumes that the modem emits its status message at the same speed as specified with (the first) _baud_rate_ value on the command line. +
+  {nbsp} +
   Since the *--extract-baud* feature may fail on heavily-loaded systems, you still should enable BREAK processing by enumerating all expected baud rates on the command line.
 
---list-speeds::
+*--list-speeds*::
   Display supported baud rates. These are determined at compilation time.
 
--n, --skip-login::
+*-n*, *--skip-login*::
   Do not prompt the user for a login name. This can be used in connection with the *--login-program* option to invoke a non-standard login process such as a BBS system. Note that with the *--skip-login* option, *agetty* gets no input from the user who logs in and therefore will not be able to figure out parity, character size, and newline processing of the connection. It defaults to space parity, 7 bit characters, and ASCII CR (13) end-of-line character. Beware that the program that *agetty* starts (usually /bin/login) is run as root.
 
--N, --nonewline::
+*-N*, *--nonewline*::
   Do not print a newline before writing out _/etc/issue_.
 
--o, --login-options _login_options_::
+*-o*, *--login-options* _login_options_::
   Options and arguments that are passed to *login*(1). Where \u is replaced by the login name. For example: +
+  {nbsp} +
   *--login-options '-h darkstar -- \u'* +
+  {nbsp} +
   See *--autologin*, *--login-program* and *--remote*. +
+  {nbsp} +
   Please read the SECURITY NOTICE below before using this option.
 
--p, --login-pause::
+*-p*, *--login-pause*::
   Wait for any key before dropping to the login prompt. Can be combined with *--autologin* to save memory by lazily spawning shells.
 
--r, --chroot _directory_::
+*-r*, *--chroot* _directory_::
   Change root to the specified directory.
 
--R, --hangup::
+*-R*, *--hangup*::
   Call *vhangup*(2) to do a virtual hangup of the specified terminal.
 
--s, --keep-baud::
+*-s*, *--keep-baud*::
   Try to keep the existing baud rate. The baud rates from the command line are used when *agetty* receives a BREAK character. If another baud rates specified then the original baud rate is also saved to the end of the wanted baud rates list. This can be used to return to the original baud rate after unexpected BREAKs.
 
--t, --timeout _timeout_::
+*-t*, *--timeout* _timeout_::
   Terminate if no user name could be read within _timeout_ seconds. Use of this option with hardwired terminal lines is not recommended.
 
--U, --detect-case::
+*-U*, *--detect-case*::
   Turn on support for detecting an uppercase-only terminal. This setting will detect a login name containing only capitals as indicating an uppercase-only terminal and turn on some upper-to-lower case conversions. Note that this has no support for any Unicode characters.
 
--w, --wait-cr::
+*-w*, *--wait-cr*::
   Wait for the user or the modem to send a carriage-return or a linefeed character before sending the _/etc/issue_ file (or others) and the login prompt. This is useful with the *--init-string* option.
 
---nohints::
+*--nohints*::
   Do not print hints about Num, Caps and Scroll Locks.
 
---nohostname::
+*--nohostname*::
   By default the hostname will be printed. With this option enabled, no hostname at all will be shown.
 
---long-hostname::
+*--long-hostname*::
   By default the hostname is only printed until the first dot. With this option enabled, the fully qualified hostname by *gethostname*(3P) or (if not found) by *getaddrinfo*(3) is shown.
 
---erase-chars _string_::
+*--erase-chars* _string_::
   This option specifies additional characters that should be interpreted as a backspace ("ignore the previous character") when the user types the login name. The default additional ´erase´ has been ´#´, but since util-linux 2.23 no additional erase characters are enabled by default.
 
---kill-chars _string_::
+*--kill-chars* _string_::
   This option specifies additional characters that should be interpreted as a kill ("ignore all previous characters") when the user types the login name. The default additional ´kill´ has been ´@´, but since util-linux 2.23 no additional kill characters are enabled by default.
 
---chdir _directory_::
+*--chdir* _directory_::
   Change directory before the login.
 
---delay _number_::
+*--delay* _number_::
   Sleep seconds before open tty.
 
---nice _number_::
+*--nice* _number_::
   Run login with this priority.
 
---reload::
+*--reload*::
   Ask all running agetty instances to reload and update their displayed prompts, if the user has not yet commenced logging in. After doing so the command will exit. This feature might be unsupported on systems without Linux *inotify*(7).
 
---version::
+*--version*::
   Display version information and exit.
 
---help::
+*--help*::
   Display help text and exit.
 
 == EXAMPLE

term-utils/script.1.adoc

@@ -69,7 +69,9 @@ Below, the _size_ argument may be followed by the multiplicative suffixes KiB (=
 
 *-E*, *--echo* _when_::
   This option controls the *ECHO* flag for the slave end of the session's pseudoterminal. The supported modes are _always_, _never_, or _auto_. +
+  {nbsp} +
   The default is _auto_ -- in this case, *ECHO* enabled for the pseudoterminal slave; if the current standard input is a terminal, *ECHO* is disabled for it to prevent double echo; if the current standard input is not a terminal (for example pipe: *echo date | script*) then keeping *ECHO* enabled for the pseudoterminal slave enables the standard input data to be viewed on screen while being recorded to session log simultaneously. +
+  {nbsp} +
   Note that 'never' mode affects content of the session output log, because users input is not repeated on output.
 
 *-e*, *--return*::
@@ -86,6 +88,7 @@ Below, the _size_ argument may be followed by the multiplicative suffixes KiB (=
 
 *-I*, *--log-in* _file_::
   Log input to the _file_. The log output is disabled if only *--log-in* specified. +
+  {nbsp} +
   Use this logging functionality carefully as it logs all input, including input when terminal has disabled echo flag (for example, password inputs).
 
 *-O*, *--log-out* _file_::
@@ -95,7 +98,7 @@ Below, the _size_ argument may be followed by the multiplicative suffixes KiB (=
   Log timing information to the _file_. Two timing file formats are supported now. The classic format is used when only one stream (input or output) logging is enabled. The multi-stream format is used on *--log-io* or when *--log-in* and *--log-out* are used together. See also *--logging-format*.
 
 *-m*, *--logging-format* _format_::
-  Force use of _advanced_ or _classic_ format. The default is the classic format to log only output and the advanced format when input as well as output logging is requested. +
+  Force use of _advanced_ or _classic_ format. The default is the classic format to log only output and the advanced format when input as well as output logging is requested.
   
 
 *Classic format*:::

term-utils/setterm.1.adoc

@@ -47,7 +47,9 @@ The optional arguments require '=' (equals sign) and not space between the optio
 
 *--blank*[=0-60|force|poke]::
   Sets the interval of inactivity, in minutes, after which the screen will be automatically blanked (using APM if available). Without an argument, it gets the blank status (returns which vt was blanked, or zero for an unblanked vt). Virtual consoles only. +
+  {nbsp} +
   The *force* argument keeps the screen blank even if a key is pressed. +
+  {nbsp} +
   The *poke* argument unblanks the screen.
 
 *--bfreq*[=_number_]::
@@ -103,6 +105,7 @@ The optional arguments require '=' (equals sign) and not space between the optio
 
 *--msglevel* 0-8::
   Sets the console logging level for kernel *printk()* messages. All messages strictly more important than this will be printed, so a logging level of *0* has the same effect as *--msg on* and a logging level of *8* will print all kernel messages. *klogd*(8) may be a more convenient interface to the logging of kernel messages. +
+  {nbsp} +
   Virtual consoles only.
 
 *--powerdown*[=0-60]::
@@ -110,6 +113,7 @@ The optional arguments require '=' (equals sign) and not space between the optio
 
 *--powersave* _mode_::
   Valid values for _mode_ are: +
+  {nbsp} +
   *vsync|on*;;
     Puts the monitor into VESA vsync suspend mode.
   *hsync*;;

text-utils/column.1.adoc

@@ -98,6 +98,7 @@ The argument _columns_ for *--table-** options is a comma separated list of the
 
 *-E, --table-noextreme* _columns_::
   Specify columns where is possible to ignore unusually long (longer than average) cells when calculate column width. The option has impact to the width calculation and table formatting, but the printed text is not affected. +
+  {nbsp} +
   The option is used for the last visible column by default.
 
 *-e, --table-header-repeat*::

text-utils/pg.1.adoc

@@ -46,6 +46,7 @@ If input comes from a pipe, *pg* stores the data in a buffer file while reading,
 
 *-n*::
   Without this option, commands must be terminated by a newline character. +
+  {nbsp} +
   With this option, *pg* advances once a command letter is entered.
 
 *-p* _string_::