+++ /dev/null
-.\" terminal-colors.d.5 --
-.\" Copyright 2014 Ondrej Oprala <ooprala@redhat.com>
-.\" Copyright (C) 2014 Karel Zak <kzak@redhat.com>
-.\" Copyright 2014 Red Hat, Inc.
-.\" May be distributed under the GNU General Public License
-.TH "TERMINAL_COLORS.D" "5" "January 2014" "util-linux" "terminal-colors.d"
-.SH NAME
-terminal-colors.d \- Configure output colorization for various utilities
-.SH SYNOPSIS
-/etc/terminal-colors\&.d/[[\fIname\fR][@\fIterm\fR]\&.][\fItype\fR]
-.SH DESCRIPTION
-Files in this directory determine the default behavior for utilities
-when coloring output.
-
-The
-.I name
-is a utility name. The name is optional and when none is specified then the
-file is used for all unspecified utilities.
-
-The
-.I term
-is a terminal identifier (the TERM environment variable).
-The terminal identifier is optional and when none is specified then the file
-is used for all unspecified terminals.
-
-The
-.I type
-is a file type. Supported file types are:
-.TP
-.B disable
-Turns off output colorization for all compatible utilities.
-.TP
-.B enable
-Turns on output colorization; any matching
-.B disable
-files are ignored.
-.TP
-.B scheme
-Specifies colors used for output. The file format may be specific to the utility,
-the default format is described below.
-.PP
-If there are more files that match for a utility, then the file with the more
-specific filename wins. For example, the filename "@xterm.scheme" has less
-priority than "dmesg@xterm.scheme". The lowest priority are those files without a
-utility name and terminal identifier (e.g., "disable").
-
-The user-specific
-.I $XDG_CONFIG_HOME/terminal-colors.d
-or
-.I $HOME/.config/terminal-colors.d
-overrides the global setting.
-
-.SH DEFAULT SCHEME FILES FORMAT
-The following statement is recognized:
-
-.RS
-.br
-.B "name color-sequence"
-.br
-.RE
-
-The
-.B name
-is a logical name of color sequence (for example "error"). The names are
-specific to the utilities. For more details always see the COLORS section
-in the man page for the utility.
-
-The
-.B color-sequence
-is a color name, ASCII color sequences or escape sequences.
-
-.SS Color names
-black, blink, blue, bold, brown, cyan, darkgray, gray, green, halfbright,
-lightblue, lightcyan, lightgray, lightgreen, lightmagenta, lightred, magenta,
-red, reset, reverse, and yellow.
-
-.SS ANSI color sequences
-The color sequences are composed of sequences of numbers
-separated by semicolons. The most common codes are:
-.sp
-.RS
-.TS
-l l.
- 0 to restore default color
- 1 for brighter colors
- 4 for underlined text
- 5 for flashing text
-30 for black foreground
-31 for red foreground
-32 for green foreground
-33 for yellow (or brown) foreground
-34 for blue foreground
-35 for purple foreground
-36 for cyan foreground
-37 for white (or gray) foreground
-40 for black background
-41 for red background
-42 for green background
-43 for yellow (or brown) background
-44 for blue background
-45 for purple background
-46 for cyan background
-47 for white (or gray) background
-.TE
-.RE
-.SS Escape sequences
-To specify control or blank characters in the color sequences,
-C-style \e-escaped notation can be used:
-.sp
-.RS
-.TS
-lb l.
-\ea Bell (ASCII 7)
-\eb Backspace (ASCII 8)
-\ee Escape (ASCII 27)
-\ef Form feed (ASCII 12)
-\en Newline (ASCII 10)
-\er Carriage Return (ASCII 13)
-\et Tab (ASCII 9)
-\ev Vertical Tab (ASCII 11)
-\e? Delete (ASCII 127)
-\e_ Space
-\e\e Backslash (\e)
-\e\(ha Caret (\(ha)
-\e# Hash mark (#)
-.TE
-.RE
-.sp
-Please note that escapes are necessary to enter a space, backslash,
-caret, or any control character anywhere in the string, as well as a
-hash mark as the first character.
-
-For example, to use a red background for alert messages in the output of
-.BR dmesg (1),
-use:
-
-.RS
-.br
-.B "echo 'alert 37;41' >> /etc/terminal-colors.d/dmesg.scheme"
-.br
-.RE
-
-.SS Comments
-Lines where the first non-blank character is a # (hash) are ignored.
-Any other use of the hash character is not interpreted as introducing
-a comment.
-
-.SH ENVIRONMENT
-.IP TERMINAL_COLORS_DEBUG=all
-enables debug output.
-
-.SH FILES
-.I $XDG_CONFIG_HOME/terminal-colors.d
-.br
-.I $HOME/.config/terminal-colors.d
-.br
-.I /etc/terminal-colors.d
-
-.SH EXAMPLE
-Disable colors for all compatible utilities:
-.RS
-.br
-.B "touch /etc/terminal-colors.d/disable"
-.br
-.RE
-
-Disable colors for all compatible utils on a vt100 terminal:
-.RS
-.br
-.B "touch /etc/terminal-colors.d/@vt100.disable"
-.br
-.RE
-
-Disable colors for all compatible utils except dmesg(1):
-.RS
-.br
-.B "touch /etc/terminal-colors.d/disable"
-.sp
-.B "touch /etc/terminal-colors.d/dmesg.enable"
-.br
-.RE
-
-.SH COMPATIBILITY
-The terminal-colors.d functionality is currently supported by all util-linux
-utilities which provides colorized output. For more details always see the
-COLORS section in the man page for the utility.
-
-.SH AVAILABILITY
-terminal-colors.d is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 2001 Andreas Dilger (adilger@turbolinux.com)
-.\"
-.\" This man page was created for libblkid.so.1.0 from e2fsprogs-1.24.
-.\"
-.\" This file may be copied under the terms of the GNU Lesser General Public
-.\" License.
-.\"
-.\" Created Wed Sep 14 12:02:12 2001, Andreas Dilger
-.TH LIBBLKID 3 "May 2009" "util-linux" "Programmer's Manual"
-.SH NAME
-libblkid \- block device identification library
-.SH SYNOPSIS
-.B #include <blkid.h>
-.sp
-.B cc
-.I file.c
-.B \-lblkid
-.SH DESCRIPTION
-The
-.B libblkid
-library is used to identify block devices (disks) as to their content (e.g.,
-filesystem type) as well as extracting additional information such as
-filesystem labels/volume names, unique identifiers/serial numbers.
-A common use is to allow use of LABEL= and UUID= tags instead of hard-coding
-specific block device names into configuration files.
-.P
-The low-level part of the library also allows the extraction
-of information about
-partitions and block device topology.
-.P
-The high-level part of the library keeps information about block devices in a
-cache file and is verified to still be valid before being returned to the user
-(if the user has read permission on the raw block device, otherwise not).
-The cache file also allows unprivileged users (normally anyone other
-than root, or those not in the "disk" group) to locate devices by label/id.
-The standard location of the cache file can be overridden by the
-environment variable BLKID_FILE.
-.P
-In situations where one is getting information about a single known device, it
-does not impact performance whether the cache is used or not (unless you are
-not able to read the block device directly).
-.P
-The high-level part of the library supports two methods to evaluate LABEL/UUID.
-It reads information directly from a block device or read information from
-/dev/disk/by-* udev symlinks. The udev is preferred method by default.
-.P
-If you are dealing with
-multiple devices, use of the cache is highly recommended (even if empty) as
-devices will be scanned at most one time and the on-disk cache will be
-updated if possible.
-.P
-In some cases (modular kernels), block devices are not even visible until
-after they are accessed the first time, so it is critical that there is
-some way to locate these devices without enumerating only visible devices,
-so the use of the cache file is
-.B required
-in this situation.
-.SH CONFIGURATION FILE
-The standard location of the
-.I /etc/blkid.conf
-config file can be overridden by the environment variable BLKID_CONF. For more
-details about the config file see
-.BR blkid (8)
-man page.
-.SH AUTHORS
-.B libblkid
-was written by Andreas Dilger for the ext2 filesystem utilities, with input
-from Ted Ts'o. The library was subsequently heavily modified by Ted Ts'o.
-
-The low-level probing code was rewritten by Karel Zak.
-.SH COPYING
-.B libblkid
-is available under the terms of the GNU Library General Public License (LGPL),
-version 2 (or at your discretion any later version).
-.SH SEE ALSO
-.BR blkid (8),
-.BR findfs (8)
-.SH AVAILABILITY
-libblkid is part of the util-linux package since version 2.15 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid \- DCE compatible Universally Unique Identifier library
-.SH SYNOPSIS
-.B #include <uuid.h>
-.SH DESCRIPTION
-The UUID library is used to generate unique identifiers for objects
-that may be accessible beyond the local system. This library
-generates UUIDs compatible with those created by the Open Software
-Foundation (OSF) Distributed Computing Environment (DCE) utility
-.BR uuidgen .
-.sp
-The UUIDs generated by this library can be reasonably expected to be
-unique within a system, and unique across all systems. They could
-be used, for instance, to generate unique HTTP cookies across multiple
-web servers without communication between the servers, and without fear
-of a name clash.
-.SH CONFORMING TO
-This library generates UUIDs compatible with OSF DCE 1.1, and hash based UUIDs
-V3 and V5 compatible with RFC-4122.
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3),
-.BR uuid_time (3),
-.BR uuid_unparse (3)
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_CLEAR 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_clear \- reset value of UUID variable to the NULL value
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "void uuid_clear(uuid_t " uu );
-.fi
-.SH DESCRIPTION
-The
-.B uuid_clear
-function sets the value of the supplied uuid variable
-.I uu
-to the NULL value.
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3),
-.BR uuid_unparse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_COMPARE 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_compare \- compare whether two UUIDs are the same
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "int uuid_compare(uuid_t " uu1 ", uuid_t " uu2)
-.fi
-.SH DESCRIPTION
-The
-.B uuid_compare
-function compares the two supplied uuid variables
-.IR uu1 " and " uu2
-to each other.
-.SH RETURN VALUE
-Returns an integer less than, equal to, or greater than zero if
-.I uu1
-is found, respectively, to be lexicographically less than, equal, or
-greater than
-.IR uu2 .
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3),
-.BR uuid_unparse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_COPY 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_copy \- copy a UUID value
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "void uuid_copy(uuid_t " dst ", uuid_t " src);
-.fi
-.SH DESCRIPTION
-The
-.B uuid_copy
-function copies the UUID variable
-.IR src " to " dst .
-.SH RETURN VALUE
-The copied UUID is returned in the location pointed to by
-.IR dst .
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_generate (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3),
-.BR uuid_unparse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_GENERATE 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_generate, uuid_generate_random, uuid_generate_time,
-uuid_generate_time_safe \- create a new unique UUID value
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "void uuid_generate(uuid_t " out );
-.BI "void uuid_generate_random(uuid_t " out );
-.BI "void uuid_generate_time(uuid_t " out );
-.BI "int uuid_generate_time_safe(uuid_t " out );
-.BI "void uuid_generate_md5(uuid_t " out ", const uuid_t " ns ", const char " *name ", size_t " len );
-.BI "void uuid_generate_sha1(uuid_t " out ", const uuid_t " ns ", const char " *name ", size_t " len );
-.fi
-.SH DESCRIPTION
-The
-.B uuid_generate
-function creates a new universally unique identifier (UUID). The uuid will
-be generated based on high-quality randomness from
-.IR getrandom(2) ,
-.IR /dev/urandom ,
-or
-.IR /dev/random
-if available. If it is not available, then
-.B uuid_generate
-will use an alternative algorithm which uses the current time, the
-local ethernet MAC address (if available), and random data generated
-using a pseudo-random generator.
-.sp
-The
-.B uuid_generate_random
-function forces the use of the all-random UUID format, even if
-a high-quality random number generator
-is not available, in which case a pseudo-random
-generator will be substituted. Note that the use of a pseudo-random
-generator may compromise the uniqueness of UUIDs
-generated in this fashion.
-.sp
-The
-.B uuid_generate_time
-function forces the use of the alternative algorithm which uses the
-current time and the local ethernet MAC address (if available).
-This algorithm used to be the default one used to generate UUIDs, but
-because of the use of the ethernet MAC address, it can leak
-information about when and where the UUID was generated. This can cause
-privacy problems in some applications, so the
-.B uuid_generate
-function only uses this algorithm if a high-quality source of
-randomness is not available. To guarantee uniqueness of UUIDs generated
-by concurrently running processes, the uuid library uses a global
-clock state counter (if the process has permissions to gain exclusive access
-to this file) and/or the
-.B uuidd
-daemon, if it is running already or can be spawned by the process (if
-installed and the process has enough permissions to run it). If neither of
-these two synchronization mechanisms can be used, it is theoretically possible
-that two concurrently running processes obtain the same UUID(s). To tell
-whether the UUID has been generated in a safe manner, use
-.BR uuid_generate_time_safe .
-.sp
-The
-.B uuid_generate_time_safe
-function is similar to
-.BR uuid_generate_time ,
-except that it returns a value which denotes whether any of the synchronization
-mechanisms (see above) has been used.
-.sp
-The UUID is 16 bytes (128 bits) long, which gives approximately 3.4x10^38
-unique values (there are approximately 10^80 elementary particles in
-the universe according to Carl Sagan's
-.IR Cosmos ).
-The new UUID can reasonably be considered unique among all UUIDs created
-on the local system, and among UUIDs created on other systems in the past
-and in the future.
-.sp
-The
-.B uuid_generate_md5
-and
-.B uuid_generate_sha1
-functions generate an MD5 and SHA1 hashed (predictable) UUID based on a
-well-known UUID providing the namespace and an arbitrary binary string. The UUIDs
-conform to V3 and V5 UUIDs per RFC-4122.
-.SH RETURN VALUE
-The newly created UUID is returned in the memory location pointed to by
-.IR out .
-.B uuid_generate_time_safe
-returns zero if the UUID has been generated in a safe manner, \-1 otherwise.
-.SH CONFORMING TO
-This library generates UUIDs compatible with OSF DCE 1.1, and hash based UUIDs
-V3 and V5 compatible with RFC-4122.
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.BR uuidgen (1),
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3),
-.BR uuid_time (3),
-.BR uuid_unparse (3),
-.BR uuidd (8)
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_IS_NULL 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_is_null \- compare the value of the UUID to the NULL value
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "int uuid_is_null(uuid_t " uu );
-.fi
-.SH DESCRIPTION
-The
-.B uuid_is_null
-function compares the value of the supplied UUID variable
-.I uu
-to the NULL value. If the value is equal to the NULL UUID, 1 is returned,
-otherwise 0 is returned.
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_time (3),
-.BR uuid_parse (3),
-.BR uuid_unparse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_PARSE 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_parse \- convert an input UUID string into binary representation
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "int uuid_parse(char *" in ", uuid_t " uu );
-.sp
-.BI "int uuid_parse_range(char *" in_start ", char *" in_end ", uuid_t " uu );
-.fi
-.SH DESCRIPTION
-The
-.B uuid_parse
-function converts the UUID string given by
-.I in
-into the binary representation. The input UUID is a string of the form
-1b4e28ba\-2fa1\-11d2\-883f\-b9a761bde3fb (in
-.BR printf (3)
-format "%08x\-%04x\-%04x\-%04x\-%012x", 36 bytes plus the trailing '\e0').
-.PP
-The
-.B uuid_parse_range
-function works like
-.B uuid_parse
-but parses only range in string specified by
-.I in_start
-and
-.I in_end
-pointers.
-.SH RETURN VALUE
-Upon successfully parsing the input string, 0 is returned, and the UUID is
-stored in the location pointed to by
-.IR uu ,
-otherwise \-1 is returned.
-.SH CONFORMING TO
-This library parses UUIDs compatible with OSF DCE 1.1, and hash based UUIDs V3
-and V5 compatible with RFC-4122.
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_is_null (3),
-.BR uuid_time (3),
-.BR uuid_unparse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_TIME 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_time \- extract the time at which the UUID was created
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "time_t uuid_time(uuid_t " uu ", struct timeval *" ret_tv )
-.fi
-.SH DESCRIPTION
-The
-.B uuid_time
-function extracts the time at which the supplied time-based UUID
-.I uu
-was created. Note that the UUID creation time is only encoded within
-certain types of UUIDs. This function can only reasonably expect to
-extract the creation time for UUIDs created with the
-.BR uuid_generate_time (3)
-and
-.BR uuid_generate_time_safe (3)
-functions. It may or may not work with UUIDs created by other mechanisms.
-.SH RETURN VALUE
-The time at which the UUID was created, in seconds since January 1, 1970 GMT
-(the epoch), is returned (see
-.BR time "(2))."
-The time at which the UUID was created, in seconds and microseconds since
-the epoch, is also stored in the location pointed to by
-.I ret_tv
-(see
-.BR gettimeofday "(2))."
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3),
-.BR uuid_unparse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 1999 Andreas Dilger (adilger@enel.ucalgary.ca)
-.\"
-.\" %Begin-Header%
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, and the entire permission notice in its entirety,
-.\" including the disclaimer of warranties.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. The name of the author may not be used to endorse or promote
-.\" products derived from this software without specific prior
-.\" written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
-.\" WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE
-.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\" %End-Header%
-.\"
-.\" Created Wed Mar 10 17:42:12 1999, Andreas Dilger
-.TH UUID_UNPARSE 3 "May 2009" "util-linux" "Libuuid API"
-.SH NAME
-uuid_unparse \- convert a UUID from binary representation to a string
-.SH SYNOPSIS
-.nf
-.B #include <uuid.h>
-.sp
-.BI "void uuid_unparse(uuid_t " uu ", char *" out );
-.BI "void uuid_unparse_upper(uuid_t " uu ", char *" out );
-.BI "void uuid_unparse_lower(uuid_t " uu ", char *" out );
-.fi
-.SH DESCRIPTION
-The
-.B uuid_unparse
-function converts the supplied UUID
-.I uu
-from the binary representation into a 36-byte string (plus trailing '\e0')
-of the form 1b4e28ba\-2fa1\-11d2\-883f\-0016d3cca427 and stores this
-value in the character string pointed to by
-.IR out .
-The case of the hex digits returned by
-.B uuid_unparse
-may be upper or lower case, and is
-dependent on the system-dependent local default.
-.PP
-If the case of the
-hex digits is important then the functions
-.B uuid_unparse_upper
-and
-.B uuid_unparse_lower
-may be used.
-.SH CONFORMING TO
-This library unparses UUIDs compatible with OSF DCE 1.1.
-.SH AUTHORS
-Theodore Y.\& Ts'o
-.SH SEE ALSO
-.na
-.BR uuid (3),
-.BR uuid_clear (3),
-.BR uuid_compare (3),
-.BR uuid_copy (3),
-.BR uuid_generate (3),
-.BR uuid_time (3),
-.BR uuid_is_null (3),
-.BR uuid_parse (3)
-.ad
-.SH AVAILABILITY
-.B libuuid
-is part of the util-linux package since version 2.15.1 and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" chrt(1) manpage
-.\"
-.\" Copyright (C) 2004 Robert Love
-.\" Copyright (C) 2015 Karel Zak <kzak@redhat.com>
-.\"
-.\" This is free documentation; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public License,
-.\" version 2, as published by the Free Software Foundation.
-.\"
-.\" The GNU General Public License's references to "object code"
-.\" and "executables" are to be interpreted as the output of any
-.\" document formatting or typesetting system, including
-.\" intermediate and printed output.
-.\"
-.\" This manual is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-.\"
-.TH CHRT 1 "January 2016" "util-linux" "User Commands"
-.SH NAME
-chrt \- manipulate the real-time attributes of a process
-.SH SYNOPSIS
-.B chrt
-[options]
-.IR priority\ command\ [ argument ...]
-.br
-.B chrt
-[options]
-.B \-p
-.RI [ priority ]\ pid
-.SH DESCRIPTION
-.B chrt
-sets or retrieves the real-time scheduling attributes of an existing \fIpid\fR,
-or runs \fIcommand\fR with the given attributes.
-
-.SH POLICIES
-.TP
-\fB\-o\fR, \fB\-\-other\fR
-Set scheduling policy to \fBSCHED_OTHER\fR (time-sharing scheduling).
-This is the default Linux scheduling policy.
-.TP
-\fB\-f\fR, \fB\-\-fifo\fR
-Set scheduling policy to \fBSCHED_FIFO\fR (first in-first out).
-.TP
-\fB\-r\fR, \fB\-\-rr\fR
-Set scheduling policy to \fBSCHED_RR\fR (round-robin scheduling).
-When no policy is defined, the
-.B SCHED_RR
-is used as the default.
-.TP
-\fB\-b\fR, \fB\-\-batch\fR
-Set scheduling policy to \fBSCHED_BATCH\fR (scheduling batch processes).
-Linux-specific, supported since 2.6.16. The priority argument has to be set to zero.
-.TP
-\fB\-i\fR, \fB\-\-idle\fR
-Set scheduling policy to \fBSCHED_IDLE\fR (scheduling very low priority jobs).
-Linux-specific, supported since 2.6.23. The priority argument has to be set to zero.
-.TP
-.BR \-d ,\ \-\-deadline
-Set scheduling policy to \fBSCHED_DEADLINE\fR (sporadic task model deadline scheduling).
-Linux-specific, supported since 3.14. The priority argument has to be set to zero.
-See also \fB\-\-sched\-runtime\fR, \fB\-\-sched\-deadline\fR and
-\fB\-\-sched\-period\fR. The relation between the options required by the kernel is
-runtime <= deadline <= period.
-.B chrt
-copies \fIperiod\fR to \fIdeadline\fR if \fB\-\-sched\-deadline\fR is not specified and
-\fIdeadline\fR to \fIruntime\fR if \fB\-\-sched\-runtime\fR is not specified.
-It means that at least \fB\-\-sched\-period\fR has to be specified. See
-.BR sched (7)
-for more details.
-
-.SH SCHEDULING OPTIONS
-.TP
-\fB\-T\fR, \fB\-\-sched\-runtime\fR \fInanoseconds\fR
-Specifies runtime parameter for SCHED_DEADLINE policy (Linux-specific).
-.TP
-\fB\-P\fR, \fB\-\-sched\-period\fR \fInanoseconds\fR
-Specifies period parameter for SCHED_DEADLINE policy (Linux-specific).
-.TP
-\fB\-D\fR, \fB\-\-sched\-deadline\fR \fInanoseconds\fR
-Specifies deadline parameter for SCHED_DEADLINE policy (Linux-specific).
-.TP
-\fB\-R\fR, \fB\-\-reset-on-fork\fR
-Use
-.B SCHED_RESET_ON_FORK
-or
-.B SCHED_FLAG_RESET_ON_FORK
-flag. Linux-specific, supported since 2.6.31.
-
-Each thread has a reset-on-fork scheduling flag. When this flag is set, children created by
-.BR fork (2)
-do not inherit privileged scheduling policies. After the reset-on-fork flag has been enabled,
-it can be reset only if the thread has the
-.BR CAP_SYS_NICE
-capability. This flag is disabled in child processes created by
-.BR fork (2).
-
-More precisely, if the reset-on-fork flag is set,
-the following rules apply for subsequently created children:
-.RS
-.IP * 3
-If the calling thread has a scheduling policy of
-.B SCHED_FIFO
-or
-.BR SCHED_RR ,
-the policy is reset to
-.BR SCHED_OTHER
-in child processes.
-.IP *
-If the calling process has a negative nice value,
-the nice value is reset to zero in child processes.
-.RE
-
-
-
-.SH OPTIONS
-.TP
-.BR \-a ,\ \-\-all-tasks
-Set or retrieve the scheduling attributes of all the tasks (threads) for a
-given PID.
-.TP
-.BR \-m ,\ \-\-max
-Show minimum and maximum valid priorities, then exit.
-.TP
-.BR \-p ,\ \-\-pid
-Operate on an existing PID and do not launch a new task.
-.TP
-.BR \-v ,\ \-\-verbose
-Show status information.
-.TP
-.BR \-V ,\ \-\-version
-Display version information and exit.
-.TP
-.BR \-h ,\ \-\-help
-Display help text and exit.
-.SH USAGE
-.TP
-The default behavior is to run a new command:
-.B chrt
-.I priority
-.IR command\ [ arguments ]
-.TP
-You can also retrieve the real-time attributes of an existing task:
-.B chrt \-p
-.I pid
-.TP
-Or set them:
-.B chrt \-r \-p
-.I priority pid
-.SH PERMISSIONS
-A user must possess
-.B CAP_SYS_NICE
-to change the scheduling attributes of a process. Any user can retrieve the
-scheduling information.
-
-.SH NOTES
-Only
-.BR SCHED_FIFO ,
-.B SCHED_OTHER
-and
-.B SCHED_RR
-are part of POSIX 1003.1b Process Scheduling. The other scheduling attributes
-may be ignored on some systems.
-.P
-Linux' default scheduling policy is
-.BR SCHED_OTHER .
-.SH AUTHORS
-.UR rml@tech9.net
-Robert Love
-.UE
-.br
-.UR kzak@redhat.com
-Karel Zak
-.UE
-.SH SEE ALSO
-.BR nice (1),
-.BR renice (1),
-.BR taskset (1),
-.BR sched (7)
-.sp
-See
-.BR sched_setscheduler (2)
-for a description of the Linux scheduling scheme.
-.SH AVAILABILITY
-The chrt command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH IONICE 1 "July 2011" "util-linux" "User Commands"
-.SH NAME
-ionice \- set or get process I/O scheduling class and priority
-.SH SYNOPSIS
-.B ionice
-.RB [ \-c
-.IR class ]
-.RB [ \-n
-.IR level ]
-.RB [ \-t ]
-.B \-p
-.IR PID ...
-.br
-.B ionice
-.RB [ \-c
-.IR class ]
-.RB [ \-n
-.IR level ]
-.RB [ \-t ]
-.B \-P
-.IR PGID ...
-.br
-.B ionice
-.RB [ \-c
-.IR class ]
-.RB [ \-n
-.IR level ]
-.RB [ \-t ]
-.B \-u
-.IR UID ...
-.br
-.B ionice
-.RB [ \-c
-.IR class ]
-.RB [ \-n
-.IR level ]
-.RB [ \-t ]
-.IR "command " [ argument ...]
-.SH DESCRIPTION
-This program sets or gets the I/O scheduling class and priority for a program.
-If no arguments or just \fB\-p\fR is given, \fBionice\fR will query the current
-I/O scheduling class and priority for that process.
-
-When \fIcommand\fR is given,
-.B ionice
-will run this command with the given arguments.
-If no \fIclass\fR is specified, then
-.I command
-will be executed with the "best-effort" scheduling class. The default
-priority level is 4.
-
-As of this writing, a process can be in one of three scheduling classes:
-.IP "\fBIdle\fP"
-A program running with idle I/O priority will only get disk time when no other
-program has asked for disk I/O for a defined grace period. The impact of an
-idle I/O process on normal system activity should be zero. This scheduling
-class does not take a priority argument. Presently, this scheduling class
-is permitted for an ordinary user (since kernel 2.6.25).
-.IP "\fBBest-effort\fP"
-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 \fI0-7\fR, with a lower
-number being higher priority. Programs running at the same best-effort
-priority are served in a round-robin fashion.
-
-Note that before kernel 2.6.26 a process that has not asked for an I/O priority
-formally uses "\fBnone\fP" 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.
-
-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).
-
-.IP "\fBRealtime\fP"
-The RT scheduling class is given first access to the disk, regardless of
-what else is going on in the system. Thus the RT class needs to be used with
-some care, as it can starve other processes. As with the best-effort class,
-8 priority levels are defined denoting how big a time slice a given process
-will receive on each scheduling window. This scheduling class is not
-permitted for an ordinary (i.e., non-root) user.
-.SH OPTIONS
-.TP
-.BR \-c , " \-\-class " \fIclass\fR
-Specify the name or number of the scheduling class to use; \fI0\fR for none,
-\fI1\fR for realtime, \fI2\fR for best-effort, \fI3\fR for idle.
-.TP
-.BR \-n , " \-\-classdata " \fIlevel\fR
-Specify the scheduling class data. This only has an effect if the class
-accepts an argument. For realtime and best-effort, \fI0-7\fR are valid data
-(priority levels), and \fI0\fR represents the highest priority level.
-.TP
-.BR \-p , " \-\-pid " \fIPID\fR...
-Specify the process IDs of running processes for which to get or set the
-scheduling parameters.
-.TP
-.BR \-P , " \-\-pgid " \fIPGID\fR...
-Specify the process group IDs of running processes for which to get or set the
-scheduling parameters.
-.TP
-.BR \-t , " \-\-ignore"
-Ignore failure to set the requested priority. If \fIcommand\fR was specified,
-run it even in case it was not possible to set the desired scheduling priority,
-which can happen due to insufficient privileges or an old kernel version.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.TP
-.BR \-u , " \-\-uid " \fIUID\fR...
-Specify the user IDs of running processes for which to get or set the
-scheduling parameters.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.SH NOTES
-Linux supports I/O scheduling priorities and classes since 2.6.13 with the CFQ
-I/O scheduler.
-.SH EXAMPLES
-.TP 7
-# \fBionice\fP \-c 3 \-p 89
-.TP 7
-Sets process with PID 89 as an idle I/O process.
-.TP 7
-# \fBionice\fP \-c 2 \-n 0 bash
-.TP 7
-Runs 'bash' as a best-effort program with highest priority.
-.TP 7
-# \fBionice\fP \-p 89 91
-.TP 7
-Prints the class and priority of the processes with PID 89 and 91.
-.SH AUTHORS
-.nf
-Jens Axboe <jens@axboe.dk>
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.BR ioprio_set (2)
-.SH AVAILABILITY
-The ionice command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" taskset(1) manpage
-.\"
-.\" Copyright (C) 2004 Robert Love
-.\"
-.\" This is free documentation; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public License,
-.\" version 2, as published by the Free Software Foundation.
-.\"
-.\" The GNU General Public License's references to "object code"
-.\" and "executables" are to be interpreted as the output of any
-.\" document formatting or typesetting system, including
-.\" intermediate and printed output.
-.\"
-.\" This manual is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-.\"
-.TH TASKSET 1 "August 2014" "util-linux" "User Commands"
-.SH NAME
-taskset \- set or retrieve a process's CPU affinity
-.SH SYNOPSIS
-.B taskset
-[options]
-.IR mask\ command\ [ argument ...]
-.br
-.B taskset
-[options]
-.B \-p
-.RI [ mask ]\ pid
-.SH DESCRIPTION
-.B taskset
-is used to set or retrieve the CPU affinity of a running process given its
-\fIpid\fR, or to launch a new \fIcommand\fR with a given CPU affinity.
-CPU affinity is a
-scheduler property that "bonds" a process to a given set of CPUs on the system.
-The Linux scheduler will honor the given CPU affinity and the process will not
-run on any other CPUs. Note that the Linux scheduler also supports natural
-CPU affinity: the scheduler attempts to keep processes on the same CPU as long
-as practical for performance reasons. Therefore, forcing a specific CPU
-affinity is useful only in certain applications.
-.sp
-The CPU affinity is represented as a bitmask, with the lowest order bit
-corresponding to the first logical CPU and the highest order bit corresponding
-to the last logical CPU. Not all CPUs may exist on a given system but a mask
-may specify more CPUs than are present. A retrieved mask will reflect only the
-bits that correspond to CPUs physically on the system. If an invalid mask is
-given (i.e., one that corresponds to no valid CPUs on the current system) an
-error is returned. The masks may be specified in hexadecimal (with or without
-a leading "0x"), or as a CPU list with the
-.B \-\-cpu\-list
-option. For example,
-.RS 4
-.TP 12
-.B 0x00000001
-is processor #0,
-.TP
-.B 0x00000003
-is processors #0 and #1,
-.TP
-.B 0xFFFFFFFF
-is processors #0 through #31,
-.TP
-.B 32
-is processors #1, #4, and #5,
-.TP
-.B \-\-cpu\-list\ 0-2,6
-is processors #0, #1, #2, and #6.
-.TP
-.B \-\-cpu\-list\ 0-10:2
-is processors #0, #2, #4, #6, #8 and #10. The suffix ":N" specifies stride in
-the range, for example 0-10:3 is interpreted as 0,3,6,9 list.
-.RE
-.PP
-When
-.B taskset
-returns, it is guaranteed that the given program has been scheduled to a legal
-CPU.
-.SH OPTIONS
-.TP
-.BR \-a ,\ \-\-all\-tasks
-Set or retrieve the CPU affinity of all the tasks (threads) for a given PID.
-.TP
-.BR \-c ,\ \-\-cpu\-list
-Interpret \fImask\fR as numerical list of processors instead of a bitmask.
-Numbers are separated by commas and may include ranges. For example:
-.BR 0,5,8-11 .
-.TP
-.BR \-p ,\ \-\-pid
-Operate on an existing PID and do not launch a new task.
-.TP
-.BR \-V ,\ \-\-version
-Display version information and exit.
-.TP
-.BR \-h ,\ \-\-help
-Display help text and exit.
-.SH USAGE
-.TP
-The default behavior is to run a new command with a given affinity mask:
-.B taskset
-.I mask
-.IR command\ [ arguments ]
-.TP
-You can also retrieve the CPU affinity of an existing task:
-.B taskset \-p
-.I pid
-.TP
-Or set it:
-.B taskset \-p
-.I mask pid
-.SH PERMISSIONS
-A user can change the CPU affinity of a process belonging to the same user.
-A user must possess
-.B CAP_SYS_NICE
-to change the CPU affinity of a process belonging to another user.
-A user can retrieve the affinity mask of any process.
-.SH AUTHORS
-Written by Robert M. Love.
-.SH COPYRIGHT
-Copyright \(co 2004 Robert M. Love.
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-.SH SEE ALSO
-.BR chrt (1),
-.BR nice (1),
-.BR renice (1),
-.BR sched_getaffinity (2),
-.BR sched_setaffinity (2)
-.sp
-See
-.BR sched (7)
-for a description of the Linux scheduling scheme.
-.SH AVAILABILITY
-The taskset command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" uclampset(1) manpage
-.\"
-.\" Copyright (C) 2020-2021 Qais Yousef <qais.yousef@arm.com>
-.\" Copyright (C) 2020-2021 Arm Ltd
-.\"
-.\" This is free documentation; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public License,
-.\" version 2, as published by the Free Software Foundation.
-.\"
-.\" The GNU General Public License's references to "object code"
-.\" and "executables" are to be interpreted as the output of any
-.\" document formatting or typesetting system, including
-.\" intermediate and printed output.
-.\"
-.\" This manual is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-.\"
-.TH UCLAMPSET 1 "August 2020" "util-linux" "User Commands"
-.SH NAME
-uclampset \- manipulate the utilization clamping attributes of the system or
-a process.
-.SH SYNOPSIS
-.B uclampset
-[options]
-.RI [ -m\ uclamp_min ]\ [ -M\ uclamp_max ]\ command\ [ argument ...]
-.br
-.B uclampset
-[options]
-.RI [ -m\ uclamp_min ]\ [ -M\ uclamp_max ]
-.B \-p
-.RI pid
-.SH DESCRIPTION
-.B uclampset
-sets or retrieves the utilization clamping attributes of an existing \fIpid\fR,
-or runs \fIcommand\fR with the given attributes.
-
-Utilization clamping is a new feature added in v5.3. It gives a hint to the
-scheduler about the allowed range of utilization the task should be operating
-at.
-
-The utilization of the task affects frequency selection and task placement.
-Only schedutil cpufreq governor understands handling util clamp hints at the
-time of writing. Consult your kernel docs for further info about other
-cpufreq governors support.
-
-If you're running on asymmetric heterogeneous system like Arm's big.LITTLE.
-Utilization clamping can help bias task placement. If the task is boosted such
-that
-.B util_min
-value is higher than the little cores' capacity, then the scheduler will do its
-best to place it on a big core.
-
-Similarly, if
-.B util_max
-is smaller than or equal the capacity of the little cores, then the scheduler
-can still choose to place it there even if the actual utilization of the task
-is at max.
-
-Setting a task's
-.B uclamp_min
-to a none zero value will effectively boost the task as when it runs it'll
-always start from this utilization value.
-
-By setting a task's
-.B uclamp_max
-below 1024, this will effectively cap the task as when it runs it'll never be
-able to go above this utilization value.
-
-The full utilization range is: [0:1024].
-The special value -1 is used to reset to system's default.
-
-.SH OPTIONS
-.TP
-.B \-m
-Set util_min value.
-.TP
-.B \-M
-Set util_max value.
-.TP
-.BR \-a ,\ \-\-all-tasks
-Set or retrieve the utilization clamping attributes of all the tasks (threads)
-for a given PID.
-.TP
-.BR \-p ,\ \-\-pid
-Operate on an existing PID and do not launch a new task.
-.TP
-.BR \-s ,\ \-\-system
-Set or retrieve the system-wide utilization clamping attributes.
-.TP
-.BR \-R ,\ \-\-reset-on-fork
-Set
-.B SCHED_FLAG_RESET_ON_FORK
-flag
-.TP
-.BR \-v ,\ \-\-verbose
-Show status information.
-.TP
-.BR \-V ,\ \-\-version
-Display version information and exit.
-.TP
-.BR \-h ,\ \-\-help
-Display help text and exit.
-.SH USAGE
-.TP
-The default behavior is to run a new command:
-.B uclampset
-.I [-m\ uclamp_min]
-.I [-M\ uclamp_max]
-.IR command\ [ arguments ]
-.TP
-You can also retrieve the utilization clamping attributes of an existing task:
-.B uclampset \-p
-.I pid
-.TP
-Or set them:
-.B uclampset \-p
-.I pid
-.I [-m\ uclamp_min]
-.I [-M\ uclamp_max]
-.TP
-Or control the system-wide attributes:
-.B uclampset \-s
-.I [-m\ uclamp_min]
-.I [-M\ uclamp_max]
-.SH PERMISSIONS
-A user must possess
-.B CAP_SYS_NICE
-to change the scheduling attributes of a process. Any user can retrieve the
-scheduling information.
-
-.SH NOTES
-The system wide utilization clamp attributes are there to control the _allowed_
-range the tasks can use. By default both
-.B uclamp_min
-and
-.B uclamp_max
-are set to 1024. This means users can set the utilization clamp values for
-their task across the full range [0:1024].
-
-.TP
-For example:
-.B uclampset \-s
-.I -m\ 512
-.I -M\ 700
-.PP
-will prevent any task from being boosted higher than 512. And all tasks in the
-systems are capped to a utilization of 700. Effectively rendering the maximum
-performance of the system to 700.
-
-Consult your kernel docs for the exact expected behavior on that kernel.
-.SH AUTHORS
-.UR qais.yousef@arm.com
-Qais Yousef
-.UE
-.SH SEE ALSO
-.BR nice (1),
-.BR renice (1),
-.BR taskset (1),
-.BR sched (7)
-.sp
-See
-.BR sched_setscheduler (2)
-and
-.BR sched_setattr (2)
-for a description of the Linux scheduling scheme.
-.SH AVAILABILITY
-The uclampset command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH ADJTIME_CONFIG 5 "August 2018" "util-linux" "File Formats"
-.SH NAME
-adjtime \- information about hardware clock setting and drift factor
-.SH SYNOPSIS
-.I /etc/adjtime
-.SH DESCRIPTION
-The file
-.I /etc/adjtime
-contains descriptive information about the hardware mode clock setting and clock drift factor.
-The file is read and write by hwclock; and read by programs like rtcwake to get RTC time mode.
-.PP
-The file is usually located in /etc, but tools like
-.BR hwclock (8)
-or
-.BR rtcwake (8)
-can use alternative location by command line options if write access to
-/etc is unwanted. The default clock mode is "UTC" if the file is missing.
-.PP
-The Hardware Clock is usually not very accurate. However, much of its inaccuracy is completely predictable - it gains
-or loses the same amount of time every day. This is called systematic drift. The util hwclock keeps the file /etc/adjtime,
-that keeps some historical information.
-For more details see "\fBThe Adjust Function\fR" and "\fBThe Adjtime File\fR" sections from
-.BR hwclock (8)
-man page.
-.PP
-.
-The format of the adjtime file is, in ASCII.
-.sp
-.SS First line
-Three numbers, separated by blanks:
-.TP
-.B "drift factor"
-the systematic drift rate in seconds per day (floating point decimal)
-.TP
-.B last adjust time
-the resulting number of seconds since 1969 UTC of most recent adjustment or calibration (decimal integer)
-.TP
-.B "adjustment status"
-zero (for compatibility with clock(8)) as a floating point decimal
-
-.SS Second line
-.TP
-.B "last calibration time"
-The resulting number of seconds since 1969 UTC of most recent calibration.
-Zero if there has been no calibration yet or it is known that any previous
-calibration is moot (for example, because the Hardware Clock has been found,
-since that calibration, not to contain a valid time). This is a decimal
-integer.
-
-.SS Third line
-.TP
-.B "clock mode"
-Supported values are "UTC" or "LOCAL". Tells whether the Hardware Clock is set
-to Coordinated Universal Time or local time. You can always override this
-value with options on the hwclock command line.
-
-.SH FILES
-.I /etc/adjtime
-.SH SEE ALSO
-.BR hwclock (8),
-.BR rtcwake (8)
-.SH AVAILABILITY
-This man page is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH BLKDISCARD 8 "July 2014" "util-linux" "System Administration"
-.SH NAME
-blkdiscard \- discard sectors on a device
-.SH SYNOPSIS
-.B blkdiscard
-[options]
-.RB [ \-o
-.IR offset ]
-.RB [ \-l
-.IR length ]
-.I device
-.SH DESCRIPTION
-.B blkdiscard
-is used to discard device sectors. This is useful for solid-state
-drivers (SSDs) and thinly-provisioned storage. Unlike
-.BR fstrim (8),
-this command is used directly on the block device.
-.PP
-By default,
-.B blkdiscard
-will discard all blocks on the device. Options may be used to modify
-this behavior based on range or size, as explained below.
-.PP
-The
-.I device
-argument is the pathname of the block device.
-.PP
-.B WARNING: All data in the discarded region on the device will be lost!
-.SH OPTIONS
-The
-.I offset
-and
-.I length
-arguments 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.
-.TP
-.BR \-f , " \-\-force"
-Disable all checking. Since v2.36 the block device is open in exclusive mode (O_EXCL)
-by default to avoid collision with mounted filesystem or another kernel subsystem.
-The force option disables the exclusive access mode.
-.TP
-.BR \-o , " \-\-offset \fIoffset"
-Byte offset into the device from which to start discarding. The provided value
-must be aligned to the device sector size. The default value is zero.
-.TP
-.BR \-l , " \-\-length \fIlength"
-The number of bytes to discard (counting from the starting point). The provided value
-must be aligned to the device sector size. If the specified value extends past
-the end of the device,
-.B blkdiscard
-will stop at the device size boundary. The default value extends to the end
-of the device.
-.TP
-.BR \-p , " \-\-step \fIlength"
-The number of bytes to discard within one iteration. The default is to discard
-all by one ioctl call.
-.TP
-.BR \-s , " \-\-secure"
-Perform a secure discard. A secure discard is the same as a regular discard
-except that all copies of the discarded blocks that were possibly created by
-garbage collection must also be erased. This requires support from the device.
-.TP
-.BR \-z , " \-\-zeroout"
-Zero-fill rather than discard.
-.TP
-.BR \-v , " \-\-verbose"
-Display the aligned values of
-.I offset
-and
-.IR length .
-If the \fB\-\-step\fR option is specified, it prints the discard progress every second.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH AUTHORS
-.MT lczerner@redhat.com
-Lukas Czerner
-.ME
-.SH SEE ALSO
-.BR fstrim (8)
-.SH AVAILABILITY
-The blkdiscard command is part of the util-linux package and is available
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH BLKZONE 8 "February 2017" "util-linux" "System Administration"
-.SH NAME
-blkzone \- run zone command on a device
-.SH SYNOPSIS
-.B blkzone
-.I command
-[options]
-.I device
-.SH DESCRIPTION
-.B blkzone
-is used to run zone command on device that support the Zoned Block Commands
-(ZBC) or Zoned-device ATA Commands (ZAC). The zones to operate on can be
-specified using the offset, count and length options.
-.PP
-The
-.I device
-argument is the pathname of the block device.
-.SH COMMANDS
-.SS report
-The command \fBblkzone report\fP is used to report device zone information.
-.PP
-By default, the command will report all zones from the start of the
-block device. Options may be used to modify this behavior, changing the
-starting zone or the size of the report, as explained below.
-
-.B Report output
-.TS
-tab(:);
-l l.
-start:Zone start sector
-len:Zone length in number of sectors
-cap:Zone capacity in number of sectors
-wptr:Zone write pointer position
-reset:Reset write pointer recommended
-non-seq:Non-sequential write resources active
-cond:Zone condition
-type:Zone type
-.TE
-
-.B Zone conditions
-.TS
-tab(:);
-l l.
-cl:Closed
-nw:Not write pointer
-em:Empty
-fu:Full
-oe:Explicitly opened
-oi:Implicitly opened
-ol:Offline
-ro:Read only
-x?:Reserved conditions (should not be reported)
-.TE
-
-.SS capacity
-The command \fBblkzone capacity\fP is used to report device capacity information.
-.PP
-By default, the command will report the sum, in number of sectors, of all
-zone capacities on the device. Options may be used to modify this behavior,
-changing the starting zone or the size of the report, as explained below.
-
-.SS reset
-The command \fBblkzone reset\fP is used to reset one or more zones. Unlike
-.BR sg_reset_wp (8),
-this command operates from the block layer and can reset a range of zones.
-
-.SS open
-The command \fBblkzone open\fP is used to explicitly open one or more zones.
-Unlike
-.BR sg_zone (8),
-open action, this command operates from the block layer and can open a range
-of zones.
-
-.SS close
-The command \fBblkzone close\fP is used to close one or more zones. Unlike
-.BR sg_zone (8),
-close action, this command operates from the block layer and can close a range
-of zones.
-
-.SS finish
-The command \fBblkzone finish\fP is used to finish (transition to full condition)
-one or more zones. Unlike
-.BR sg_zone (8),
-finish action, this command operates from the block layer and can finish a range
-of zones.
-
-.PP
-By default, the reset, open, close and finish commands will operate from the zone
-at device sector 0 and operate on all zones. Options may be used to modify this
-behavior as explained below.
-
-.SH OPTIONS
-The
-.I offset
-and
-.I length
-option arguments 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.
-Additionally, the 0x prefix can be used to specify \fIoffset\fR and
-\fIlength\fR in hex.
-.TP
-.BR \-o , " \-\-offset "\fIsector\fP
-The starting zone specified as a sector offset. The provided offset in sector
-units (512 bytes) should match the start of a zone. The default value is zero.
-.TP
-.BR \-l , " \-\-length "\fIsectors\fP
-The maximum number of sectors the command should operate on. The default value
-is the number of sectors remaining after \fIoffset\fR. This option cannot be
-used together with the option \fB\-\-count\fP.
-.TP
-.BR \-c , " \-\-count "\fIcount\fP
-The maximum number of zones the command should operate on. The default value
-is the number of zones starting from \fIoffset\fR. This option cannot be
-used together with the option \fB\-\-length\fP.
-.TP
-.BR \-f , " \-\-force"
-Enforce commands to change zone status on block devices used by the system.
-.TP
-.BR \-v , " \-\-verbose"
-Display the number of zones returned in the report or the range of sectors
-reset.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH AUTHORS
-.nf
-Shaun Tancheff <shaun@tancheff.com>
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.BR sg_rep_zones (8)
-.SH AVAILABILITY
-The blkzone command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH CHCPU 8 "July 2014" "util-linux" "System Administration"
-.SH NAME
-chcpu \- configure CPUs
-.SH SYNOPSIS
-.B chcpu
-.BR \-c | \-d | \-e | \-g
-.I cpu-list
-.br
-.B chcpu \-p
-.I mode
-.br
-.B chcpu
-.BR \-r | \-h | \-V
-.SH DESCRIPTION
-.B chcpu
-can modify the state of CPUs. It can enable or disable CPUs, scan for new
-CPUs, change the CPU dispatching
-.I mode
-of the underlying hypervisor, and request CPUs from the hypervisor
-(configure) or return CPUs to the hypervisor (deconfigure).
-.PP
-Some options have a
-.I cpu-list
-argument. Use this argument to specify a comma-separated list of CPUs. The
-list can contain individual CPU addresses or ranges of addresses. For
-example,
-.B 0,5,7,9-11
-makes the command applicable to the CPUs with the addresses 0, 5, 7, 9, 10,
-and 11.
-.SH OPTIONS
-.TP
-.BR \-c , " \-\-configure " \fIcpu-list\fP
-Configure the specified CPUs. Configuring a CPU means that the hypervisor
-takes a CPU from the CPU pool and assigns it to the virtual hardware on which
-your kernel runs.
-.TP
-.BR \-d , " \-\-disable " \fIcpu-list\fP
-Disable the specified CPUs. Disabling a CPU means that the kernel sets it
-offline.
-.TP
-.BR \-e , " \-\-enable " \fIcpu-list\fP
-Enable the specified CPUs. Enabling a CPU means that the kernel sets it
-online. A CPU must be configured, see \fB\-c\fR, before it can be enabled.
-.TP
-.BR \-g , " \-\-deconfigure " \fIcpu-list\fP
-Deconfigure the specified CPUs. Deconfiguring a CPU means that the
-hypervisor removes the CPU from the virtual hardware on which the Linux
-instance runs and returns it to the CPU pool. A CPU must be offline, see
-\fB\-d\fR, before it can be deconfigured.
-.TP
-.BR \-p , " \-\-dispatch " \fImode\fP
-Set the CPU dispatching
-.I mode
-(polarization). This option has an effect only if your hardware architecture
-and hypervisor support CPU polarization. Available
-.I modes
-are:
-.RS 14
-.TP 12
-.PD 0
-.B horizontal
-The workload is spread across all available CPUs.
-.TP 12
-.B vertical
-The workload is concentrated on few CPUs.
-.RE
-.PD 1
-.TP
-.BR \-r , " \-\-rescan"
-Trigger a rescan of CPUs. After a rescan, the Linux kernel recognizes
-the new CPUs. Use this option on systems that do not
-automatically detect newly attached CPUs.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-
-.SH EXIT STATUS
-.B chcpu
-has the following exit status values:
-.TP
-.B 0
-success
-.TP
-.B 1
-failure
-.TP
-.B 64
-partial success
-.SH AUTHORS
-.MT heiko.carstens@de.ibm.com
-Heiko Carstens
-.ME
-.SH COPYRIGHT
-Copyright IBM Corp. 2011
-.SH SEE ALSO
-.BR lscpu (1)
-.SH AVAILABILITY
-The chcpu command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH CHMEM 8 "October 2016" "util-linux" "System Administration"
-.SH NAME
-chmem \- configure memory
-.SH SYNOPSIS
-.B chmem
-.RB [ \-h "] [" \-V "] [" \-v "] [" \-e | \-d "]"
-[\fISIZE\fP|\fIRANGE\fP|\fB\-b\fP \fIBLOCKRANGE\fP]
-[-z ZONE]
-.SH DESCRIPTION
-The chmem command sets a particular size or range of memory online or offline.
-.
-.IP "\(hy" 2
-Specify \fISIZE\fP as <size>[m|M|g|G]. With m or M, <size> specifies the memory
-size in MiB (1024 x 1024 bytes). With g or G, <size> specifies the memory size
-in GiB (1024 x 1024 x 1024 bytes). The default unit is MiB.
-.
-.IP "\(hy" 2
-Specify \fIRANGE\fP in the form 0x<start>-0x<end> as shown in the output of the
-\fBlsmem\fP command. <start> is the hexadecimal address of the first byte and <end>
-is the hexadecimal address of the last byte in the memory range.
-.
-.IP "\(hy" 2
-Specify \fIBLOCKRANGE\fP in the form <first>-<last> or <block> as shown in the
-output of the \fBlsmem\fP command. <first> is the number of the first memory block
-and <last> is the number of the last memory block in the memory
-range. Alternatively a single block can be specified. \fIBLOCKRANGE\fP requires
-the \fB\-\-blocks\fP option.
-.
-.IP "\(hy" 2
-Specify \fIZONE\fP as the name of a memory zone, as shown in the output of the
-\fBlsmem \-o +ZONES\fP command. The output shows one or more valid memory zones
-for each memory range. If multiple zones are shown, then the memory range
-currently belongs to the first zone. By default, chmem will set memory online
-to the zone Movable, if this is among the valid zones. This default can be
-changed by specifying the \fB\-\-zone\fP option with another valid zone.
-For memory ballooning, it is recommended to select the zone Movable for memory
-online and offline, if possible. Memory in this zone is much more likely to be
-able to be offlined again, but it cannot be used for arbitrary kernel
-allocations, only for migratable pages (e.g., anonymous and page cache pages).
-Use the \fB\-\-help\fR option to see all available zones.
-.
-.PP
-\fISIZE\fP and \fIRANGE\fP must be aligned to the Linux memory block size, as
-shown in the output of the \fBlsmem\fP command.
-
-Setting memory online can fail for various reasons. On virtualized systems it
-can fail if the hypervisor does not have enough memory left, for example
-because memory was overcommitted. Setting memory offline can fail if Linux
-cannot free the memory. If only part of the requested memory can be set online
-or offline, a message tells you how much memory was set online or offline
-instead of the requested amount.
-
-When setting memory online \fBchmem\fP starts with the lowest memory block
-numbers. When setting memory offline \fBchmem\fP starts with the highest memory
-block numbers.
-.SH OPTIONS
-.TP
-.BR \-b ", " \-\-blocks
-Use a \fIBLOCKRANGE\fP parameter instead of \fIRANGE\fP or \fISIZE\fP for the
-\fB\-\-enable\fP and \fB\-\-disable\fP options.
-.TP
-.BR \-d ", " \-\-disable
-Set the specified \fIRANGE\fP, \fISIZE\fP, or \fIBLOCKRANGE\fP of memory offline.
-.TP
-.BR \-e ", " \-\-enable
-Set the specified \fIRANGE\fP, \fISIZE\fP, or \fIBLOCKRANGE\fP of memory online.
-.TP
-.BR \-z ", " \-\-zone
-Select the memory \fIZONE\fP where to set the specified \fIRANGE\fP, \fISIZE\fP,
-or \fIBLOCKRANGE\fP of memory online or offline. By default, memory will be set
-online to the zone Movable, if possible.
-.TP
-.BR \-h ", " \-\-help
-Print a short help text, then exit.
-.TP
-.BR \-v ", " \-\-verbose
-Verbose mode. Causes \fBchmem\fP to print debugging messages about it's
-progress.
-.TP
-.BR \-V ", " \-\-version
-Print the version number, then exit.
-.SH EXIT STATUS
-.B chmem
-has the following exit status values:
-.TP
-.B 0
-success
-.TP
-.B 1
-failure
-.TP
-.B 64
-partial success
-.SH EXAMPLE
-.TP
-.B chmem \-\-enable 1024
-This command requests 1024 MiB of memory to be set online.
-.TP
-.B chmem \-e 2g
-This command requests 2 GiB of memory to be set online.
-.TP
-.B chmem \-\-disable 0x00000000e4000000-0x00000000f3ffffff
-This command requests the memory range starting with 0x00000000e4000000
-and ending with 0x00000000f3ffffff to be set offline.
-.TP
-.B chmem \-b \-d 10
-This command requests the memory block number 10 to be set offline.
-.SH SEE ALSO
-.BR lsmem (1)
-.SH AVAILABILITY
-The \fBchmem\fP command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH CHOOM 1 "April 2018" "util-linux" "User Commands"
-.SH NAME
-choom \- display and adjust OOM-killer score.
-.SH SYNOPSIS
-.B choom
-.B \-p
-.I pid
-.sp
-.B choom
-.B \-p
-.I pid
-.B \-n
-.I number
-.sp
-.B choom
-.B \-n
-.I number
-.B [\-\-]
-.IR command\ [ argument ...]
-
-.SH DESCRIPTION
-The \fBchoom\fP command displays and adjusts Out-Of-Memory killer score setting.
-
-.SH OPTIONS
-.TP
-.BR \-p ", " \-\-pid " \fIpid\fP"
-Specifies process ID.
-.TP
-.BR \-n , " \-\-adjust " \fIvalue\fP
-Specify the adjust score value.
-.TP
-.BR \-h ", " \-\-help
-Display help text and exit.
-.TP
-.BR \-V ", " \-\-version
-Display version information and exit.
-.SH NOTES
-Linux kernel uses the badness heuristic to select which process gets killed in
-out of memory conditions.
-
-The badness heuristic assigns a value to each candidate task ranging from 0
-(never kill) to 1000 (always kill) to determine which process is targeted. The
-units are roughly a proportion along that range of allowed memory the process
-may allocate from based on an estimation of its current memory and swap use.
-For example, if a task is using all allowed memory, its badness score will be
-1000. If it is using half of its allowed memory, its score will be 500.
-
-There is an additional factor included in the badness score: the current memory
-and swap usage is discounted by 3% for root processes.
-
-The amount of "allowed" memory depends on the context in which the oom killer
-was called. If it is due to the memory assigned to the allocating task's cpuset
-being exhausted, the allowed memory represents the set of mems assigned to that
-cpuset. If it is due to a mempolicy's node(s) being exhausted, the allowed
-memory represents the set of mempolicy nodes. If it is due to a memory
-limit (or swap limit) being reached, the allowed memory is that configured
-limit. Finally, if it is due to the entire system being out of memory, the
-allowed memory represents all allocatable resources.
-
-The adjust score value is added to the badness score before it is used to
-determine which task to kill. Acceptable values range from -1000 to +1000.
-This allows userspace to polarize the preference for oom killing either by
-always preferring a certain task or completely disabling it. The lowest
-possible value, -1000, is equivalent to disabling oom killing entirely for that
-task since it will always report a badness score of 0.
-
-Setting an adjust score value of +500, for example, is roughly equivalent to
-allowing the remainder of tasks sharing the same system, cpuset, mempolicy, or
-memory controller resources to use at least 50% more memory. A value of -500,
-on the other hand, would be roughly equivalent to discounting 50% of the task's
-allowed memory from being considered as scoring against the task.
-
-.SH AUTHORS
-.nf
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.BR proc (5)
-.SH AVAILABILITY
-The \fBchoom\fP command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 1992, 1993 Rickard E. Faith (faith@cs.unc.edu)
-.\" May be distributed under the GNU General Public License
-.TH CTRLALTDEL 8 "October 2015" "util-linux" "System Administration"
-.SH NAME
-ctrlaltdel \- set the function of the Ctrl-Alt-Del combination
-.SH SYNOPSIS
-.BR "ctrlaltdel hard" | soft
-.SH DESCRIPTION
-Based on examination of the
-.I linux/kernel/reboot.c
-code, it is clear that there are two supported functions that the
-Ctrl-Alt-Del sequence can perform.
-.TP
-.B hard
-Immediately reboot the computer without calling
-.BR sync (2)
-and without any other preparation. This is the default.
-.TP
-.B soft
-Make the kernel send the SIGINT (interrupt) signal to the
-.B init
-process (this is always the process with PID 1). If this option is used,
-the
-.BR init (8)
-program must support this feature. Since there are now several
-.BR init (8)
-programs in the Linux community, please consult the documentation for the
-version that you are currently using.
-.PP
-When the command is run without any argument, it will display the current
-setting.
-.PP
-The function of
-.B ctrlaltdel
-is usually set in the
-.I /etc/rc.local
-file.
-.SH OPTIONS
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.SH FILES
-.I /etc/rc.local
-.SH AUTHORS
-.UR poe@daimi.aau.dk
-Peter Orbaek
-.UE
-.SH SEE ALSO
-.BR init (8),
-.BR systemd (1)
-.SH AVAILABILITY
-The ctrlaltdel command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 1993 Rickard E. Faith (faith@cs.unc.edu)
-.\" May be distributed under the GNU General Public License
-.TH DMESG "1" "July 2012" "util-linux" "User Commands"
-.SH NAME
-dmesg \- print or control the kernel ring buffer
-.SH SYNOPSIS
-.B dmesg
-[options]
-.sp
-.B dmesg \-\-clear
-.br
-.BR "dmesg \-\-read\-clear " [options]
-.br
-.BI "dmesg \-\-console\-level " level
-.br
-.B dmesg \-\-console\-on
-.br
-.B dmesg \-\-console\-off
-.SH DESCRIPTION
-.B dmesg
-is used to examine or control the kernel ring buffer.
-.PP
-The default action is to display all messages from the kernel ring buffer.
-.SH OPTIONS
-The
-.BR \-\-clear ,
-.BR \-\-read\-clear ,
-.BR \-\-console\-on ,
-.BR \-\-console\-off ,
-and
-.B \-\-console\-level
-options are mutually exclusive.
-.IP "\fB\-C\fR, \fB\-\-clear\fR"
-Clear the ring buffer.
-.IP "\fB\-c\fR, \fB\-\-read\-clear\fR"
-Clear the ring buffer after first printing its contents.
-.IP "\fB\-D\fR, \fB\-\-console\-off\fR"
-Disable the printing of messages to the console.
-.IP "\fB\-d\fR, \fB\-\-show\-delta\fR"
-Display the timestamp and the time delta spent between messages. If used
-together with
-.B \-\-notime
-then only the time delta without the timestamp is printed.
-.IP "\fB\-E\fR, \fB\-\-console\-on\fR"
-Enable printing messages to the console.
-.IP "\fB\-e\fR, \fB\-\-reltime\fR"
-Display the local time and the delta in human-readable format. Be aware that
-conversion to the local time could be inaccurate (see \fB\-T\fR for more
-details).
-.IP "\fB\-F\fR, \fB\-\-file \fIfile\fR"
-Read the syslog messages from the given
-.IR file .
-Note that \fB\-F\fR does not support messages in kmsg format. The old syslog format is supported only.
-.IP "\fB\-f\fR, \fB\-\-facility \fIlist\fR"
-Restrict output to the given (comma-separated)
-.I list
-of facilities. For example:
-.PP
-.RS 14
-.B dmesg \-\-facility=daemon
-.RE
-.IP
-will print messages from system daemons only. For all supported facilities
-see the
-.B \-\-help
-output.
-.IP "\fB\-H\fR, \fB\-\-human\fR"
-Enable human-readable output. See also \fB\-\-color\fR, \fB\-\-reltime\fR
-and \fB\-\-nopager\fR.
-.IP "\fB\-k\fR, \fB\-\-kernel\fR"
-Print kernel messages.
-.IP "\fB\-L\fR, \fB\-\-color\fR[=\fIwhen\fR]"
-Colorize the output. The optional argument \fIwhen\fP
-can be \fBauto\fR, \fBnever\fR or \fBalways\fR. If the \fIwhen\fR argument is omitted,
-it defaults to \fBauto\fR. The colors can be disabled; for the current built-in default
-see the \fB\-\-help\fR output. See also the \fBCOLORS\fR section below.
-.IP "\fB\-l\fR, \fB\-\-level \fIlist\fR"
-Restrict output to the given (comma-separated)
-.I list
-of levels. For example:
-.PP
-.RS 14
-.B dmesg \-\-level=err,warn
-.RE
-.IP
-will print error and warning messages only. For all supported levels see the
-.B \-\-help
-output.
-.IP "\fB\-n\fR, \fB\-\-console\-level \fIlevel\fR"
-Set the
-.I level
-at which printing of messages is done to the console. The
-.I level
-is a level number or abbreviation of the level name. For all supported
-levels see the
-.B \-\-help
-output.
-.sp
-For example,
-.B \-n 1
-or
-.B \-n emerg
-prevents all messages, except emergency (panic) messages, from appearing on
-the console. All levels of messages are still written to
-.IR /proc/kmsg ,
-so
-.BR syslogd (8)
-can still be used to control exactly where kernel messages appear. When the
-.B \-n
-option is used,
-.B dmesg
-will
-.I not
-print or clear the kernel ring buffer.
-.IP "\fB\-\-noescape\fR"
-The unprintable and potentially unsafe characters (e.g., broken multi-byte
-sequences, terminal controlling chars, etc.) are escaped in format \\x<hex> for
-security reason by default. This option disables this feature at all. It's
-usable for example for debugging purpose together with \fB\-\-raw\fR. Be
-careful and don't use it by default.
-.IP "\fB\-P\fR, \fB\-\-nopager\fR"
-Do not pipe output into a pager. A pager is enabled by default for \fB\-\-human\fR output.
-.IP "\fB\-p\fR, \fB\-\-force\-prefix\fR"
-Add facility, level or timestamp information to each line of a multi-line message.
-.IP "\fB\-r\fR, \fB\-\-raw\fR"
-Print the raw message buffer, i.e., do not strip the log-level prefixes, but
-all unprintable characters are still escaped (see also \fB\-\-noescape\fR).
-
-Note that the real raw format depends on the method how
-.BR dmesg (1)
-reads kernel messages. The /dev/kmsg device uses a different format than
-.BR syslog (2).
-For backward compatibility,
-.BR dmesg (1)
-returns data always in the
-.BR 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'.
-.IP "\fB\-S\fR, \fB\-\-syslog\fR"
-Force \fBdmesg\fR to use the
-.BR syslog (2)
-kernel interface to read kernel messages. The default is to use /dev/kmsg rather
-than
-.BR syslog (2)
-since kernel 3.5.0.
-.IP "\fB\-s\fR, \fB\-\-buffer\-size \fIsize\fR"
-Use a buffer of
-.I 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.
-.IP "\fB\-T\fR, \fB\-\-ctime\fR"
-Print human-readable timestamps.
-.IP
-.B Be aware that the timestamp could be inaccurate!
-The
-.B time
-source used for the logs is
-.B not updated after
-system
-.BR SUSPEND / RESUME .
-Timestamps are adjusted according to current delta between boottime and monotonic
-clocks, this works only for messages printed after last resume.
-.IP "\fB\-\-since \fItime\fR"
-Display record since the specified time. The time is possible to specify in absolute way
-as well as by relative notation (e.g. '1 hour ago'). Be aware that the timestamp could
-be inaccurate and see \fB\-\-ctime\fR for more details.
-.IP "\fB\-\-until \fItime\fR"
-Display record until the specified time. The time is possible to specify in absolute way
-as well as by relative notation (e.g. '1 hour ago'). Be aware that the timestamp could
-be inaccurate and see \fB\-\-ctime\fR for more details.
-.IP "\fB\-t\fR, \fB\-\-notime\fR"
-Do not print kernel's timestamps.
-.IP "\fB\-\-time\-format\fR \fIformat\fR"
-Print timestamps using the given \fIformat\fR, which can be
-.BR ctime ,
-.BR reltime ,
-.B delta
-or
-.BR iso .
-The first three formats are aliases of the time-format-specific options.
-The
-.B iso
-format is a
-.B 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 \fBiso\fR timestamp is:
-YYYY-MM-DD<T>HH:MM:SS,<microseconds><-+><timezone offset from UTC>.
-.IP
-The
-.B iso
-format has the same issue as
-.BR ctime :
-the time may be inaccurate when a system is suspended and resumed.
-.TP
-.BR \-u , " \-\-userspace"
-Print userspace messages.
-.TP
-.BR \-w , " \-\-follow"
-Wait for new messages. This feature is supported only on systems with
-a readable /dev/kmsg (since kernel 3.5.0).
-.TP
-.BR \-W , " \-\-follow-new"
-Wait and print only new messages.
-.TP
-.BR \-x , " \-\-decode"
-Decode facility and level (priority) numbers to human-readable prefixes.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH COLORS
-Implicit coloring can be disabled by an empty file \fI/etc/terminal-colors.d/dmesg.disable\fR.
-See
-.BR terminal-colors.d (5)
-for more details about colorization configuration.
-.PP
-The logical color names supported by
-.B dmesg
-are:
-.TP
-.B subsys
-The message sub-system prefix (e.g., "ACPI:").
-.TP
-.B time
-The message timestamp.
-.TP
-.B timebreak
-The message timestamp in short ctime format in \fB\-\-reltime\fR
-or \fB\-\-human\fR output.
-.TP
-.B alert
-The text of the message with the alert log priority.
-.TP
-.B crit
-The text of the message with the critical log priority.
-.TP
-.B err
-The text of the message with the error log priority.
-.TP
-.B warn
-The text of the message with the warning log priority.
-.TP
-.B segfault
-The text of the message that inform about segmentation fault.
-.SH EXIT STATUS
-.B dmesg
-can fail reporting permission denied error. This is usually caused by
-.B dmesg_restrict
-kernel setting, please see
-.BR syslog (2)
-for more details.
-.SH AUTHORS
-.MT kzak@redhat.com
-Karel Zak
-.ME
-
-.B dmesg
-was originally written by
-.MT tytso@athena.mit.edu
-Theodore Ts'o
-.ME
-.SH SEE ALSO
-.BR terminal-colors.d (5),
-.BR syslogd (8)
-.SH AVAILABILITY
-The dmesg command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright (C) 1994-2005 Jeff Tranter (tranter@pobox.com)
-.\" Copyright (C) 2012 Karel Zak <kzak@redhat.com>
-.\"
-.\" It may be distributed under the GNU Public License, version 2, or
-.\" any higher version. See section COPYING of the GNU Public license
-.\" for conditions under which this file may be redistributed.
-.TH EJECT 1 "April 2012" "Linux" "User Commands"
-.SH NAME
-eject \- eject removable media
-.SH SYNOPSIS
-.B eject
-[options]
-.IR device | mountpoint
-.SH DESCRIPTION
-.B eject
-allows removable media (typically a CD-ROM, floppy disk, tape, JAZ, ZIP or USB
-disk) to be ejected under software control. The command can also control some
-multi-disc CD-ROM changers, the auto-eject feature supported by some devices,
-and close the disc tray of some CD-ROM drives.
-.PP
-The device corresponding to \fIdevice\fP or \fImountpoint\fP is ejected. If no
-name is specified, the default name \fB/dev/cdrom\fR is used. The device may be
-addressed by device name (e.g., 'sda'), device path (e.g., '/dev/sda'),
-UUID=\fIuuid\fR or LABEL=\fIlabel\fR tags.
-.PP
-There are four different methods of ejecting, depending on whether the device
-is a CD-ROM, SCSI device, removable floppy, or tape. By default \fBeject\fR tries
-all four methods in order until it succeeds.
-.PP
-If a device partition is specified, the whole-disk device is used.
-.PP
-If the device or a device partition is currently mounted, it is unmounted
-before ejecting. The eject is processed on exclusive open block device
-file descriptor if \fB\-\-no\-unmount\fP or \fB\-\-force\fP are not specified.
-
-.SH OPTIONS
-.TP
-.BR \-a , " \-\-auto on" | off
-This option controls the auto-eject mode, supported by some devices. When
-enabled, the drive automatically ejects when the device is closed.
-.TP
-.BR \-c , " \-\-changerslot " \fIslot
-With this option a CD slot can be selected from an ATAPI/IDE CD-ROM changer.
-The CD-ROM drive cannot be in use (mounted data CD or playing a music CD) for
-a change request to work. Please also note that the first slot of the changer
-is referred to as 0, not 1.
-.TP
-.BR \-d , " \-\-default"
-List the default device name.
-.TP
-.BR \-F , " \-\-force"
-Force eject, don't check device type, don't open device with exclusive lock.
-The successful result may be false positive on non hot-pluggable devices.
-.TP
-.BR \-f , " \-\-floppy"
-This option specifies that the drive should be ejected using a removable floppy
-disk eject command.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.TP
-.BR \-i , " \-\-manualeject on" | off
-This option controls locking of the hardware eject button. When enabled, the
-drive will not be ejected when the button is pressed. This is useful when you
-are carrying a laptop in a bag or case and don't want it to eject if the button
-is inadvertently pressed.
-.TP
-.BR \-M , " \-\-no\-partitions\-unmount"
-The option tells eject to not try to unmount other partitions on partitioned
-devices. If another partition is still mounted, the program will not attempt
-to eject the media. It will attempt to unmount only the device or mountpoint
-given on the command line.
-.TP
-.BR \-m , " \-\-no\-unmount"
-The option tells eject to not try to unmount at all. If this option is not
-specified than
-.B eject
-opens the device with O_EXCL flag to be sure that the device is not used (since
-v2.35).
-.TP
-.BR \-n , " \-\-noop"
-With this option the selected device is displayed but no action is performed.
-.TP
-.BR \-p , " \-\-proc"
-This option allows you to use /proc/mounts instead /etc/mtab. It also passes the
-\fB\-n\fR option to \fBumount\fR(8).
-.TP
-.BR \-q , " \-\-tape"
-This option specifies that the drive should be ejected using a tape drive
-offline command.
-.TP
-.BR \-r , " \-\-cdrom"
-This option specifies that the drive should be ejected using a CDROM eject
-command.
-.TP
-.BR \-s , " \-\-scsi"
-This option specifies that the drive should be ejected using SCSI commands.
-.TP
-.BR \-T , " \-\-traytoggle"
-With this option the drive is given a CD-ROM tray close command if it's opened,
-and a CD-ROM tray eject command if it's closed. Not all devices support this
-command, because it uses the above CD-ROM tray close command.
-.TP
-.BR \-t , " \-\-trayclose"
-With this option the drive is given a CD-ROM tray close command. Not all
-devices support this command.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-v , " \-\-verbose"
-Run in verbose mode; more information is displayed about what the command is
-doing.
-.TP
-.BR \-X , " \-\-listspeed"
-With this option the CD-ROM drive will be probed to detect the available
-speeds. The output is a list of speeds which can be used as an argument of the
-\fB\-x\fR option. This only works with Linux 2.6.13 or higher, on previous versions
-solely the maximum speed will be reported. Also note that some drives may not
-correctly report the speed and therefore this option does not work with them.
-.TP
-.BR \-x , " \-\-cdspeed " \fIspeed
-With this option the drive is given a CD-ROM select speed command. The
-.I speed
-argument is a number indicating the desired speed (e.g., 8 for 8X speed), or 0
-for maximum data rate. Not all devices support this command and you can only
-specify speeds that the drive is capable of. Every time the media is changed
-this option is cleared. This option can be used alone, or with the
-\fB\-t\fR and \fB\-c\fR options.
-.SH EXIT STATUS
-Returns 0 if operation was successful, 1 if operation failed or command syntax
-was not valid.
-.SH NOTES
-.B eject
-only works with devices that support one or more of the four methods of
-ejecting. This includes most CD-ROM drives (IDE, SCSI, and proprietary), some
-SCSI tape drives, JAZ drives, ZIP drives (parallel port, SCSI, and IDE
-versions), and LS120 removable floppies. Users have also reported success with
-floppy drives on Sun SPARC and Apple Macintosh systems. If
-.B eject
-does not work, it is most likely a limitation of the kernel driver for the
-device and not the
-.B eject
-program itself.
-.PP
-The \fB\-r\fR, \fB\-s\fR, \fB\-f\fR, and \fB\-q\fR options allow controlling
-which methods are used to
-eject. More than one method can be specified. If none of these options are
-specified, it tries all four (this works fine in most cases).
-.PP
-.B eject
-may not always be able to determine if the device is mounted (e.g., if it has
-several names). If the device name is a symbolic link,
-.B eject
-will follow the link and use the device that it points to.
-.PP
-If
-.B eject
-determines that the device can have multiple partitions, it will attempt to
-unmount all mounted partitions of the device before ejecting (see also
-\fB--no-partitions-unmount\fR). If an unmount fails, the program will not
-attempt to eject the media.
-.PP
-You can eject an audio CD. Some CD-ROM drives will refuse to open the tray if
-the drive is empty. Some devices do not support the tray close command.
-.PP
-If the auto-eject feature is enabled, then the drive will always be ejected
-after running this command. Not all Linux kernel CD-ROM drivers support the
-auto-eject mode. There is no way to find out the state of the auto-eject mode.
-.PP
-You need appropriate privileges to access the device files. Running as root is
-required to eject some devices (e.g., SCSI devices).
-.SH AUTHORS
-.MT tranter@\:pobox.com
-Jeff Tranter
-.ME
-- original author.
-.br
-.MT kzak@\:redhat.com
-Karel Zak
-.ME
-and
-.MT mluscon@\:redhat.com
-Michal Luscon
-.ME
-- util-linux version.
-.SH SEE ALSO
-.BR findmnt (8),
-.BR lsblk (8),
-.BR mount (8),
-.BR umount (8)
-.SH AVAILABILITY
-The eject command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH FALLOCATE 1 "April 2014" "util-linux" "User Commands"
-.SH NAME
-fallocate \- preallocate or deallocate space to a file
-.SH SYNOPSIS
-.B fallocate
-.RB [ \-c | \-p | \-z ]
-.RB [ \-o
-.IR offset ]
-.B \-l
-.I length
-.RB [ \-n ]
-.I filename
-.PP
-.B fallocate \-d
-.RB [ \-o
-.IR offset ]
-.RB [ \-l
-.IR length ]
-.I filename
-.PP
-.B fallocate \-x
-.RB [ \-o
-.IR offset ]
-.B \-l
-.I length
-.I filename
-.SH DESCRIPTION
-.B fallocate
-is used to manipulate the allocated disk space for a file,
-either to deallocate or preallocate it.
-For filesystems which support the fallocate system call,
-preallocation is done quickly by allocating blocks and marking them as
-uninitialized, requiring no IO to the data blocks.
-This is much faster than creating a file by filling it with zeroes.
-.PP
-The exit status returned by
-.B fallocate
-is 0 on success and 1 on failure.
-.SH OPTIONS
-The
-.I length
-and
-.I offset
-arguments 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.
-.PP
-The options
-.BR \-\-collapse\-range ", " \-\-dig\-holes ", " \-\-punch\-hole ,
-and
-.B \-\-zero\-range
-are mutually exclusive.
-.TP
-.BR \-c ", " \-\-collapse\-range
-Removes a byte range from a file, without leaving a hole.
-The byte range to be collapsed starts at
-.I offset
-and continues for
-.I length
-bytes.
-At the completion of the operation,
-the contents of the file starting at the location
-.IR offset + length
-will be appended at the location
-.IR offset ,
-and the file will be
-.I length
-bytes smaller.
-The option
-.B \-\-keep\-size
-may not be specified for the collapse-range operation.
-.sp
-Available since Linux 3.15 for ext4 (only for extent-based files) and XFS.
-.sp
-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.
-.TP
-.BR \-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,
-.B \-\-keep\-size
-is implied. If no range is specified by
-.B \-\-offset
-and
-.BR \-\-length ,
-then the entire file is analyzed for holes.
-.sp
-You can think of this option as doing a
-.RB """" "cp \-\-sparse" """"
-and then renaming the destination file to the original,
-without the need for extra disk space.
-.sp
-See \fB\-\-punch\-hole\fP for a list of supported filesystems.
-.TP
-.BR \-i ", " \-\-insert\-range
-Insert a hole of
-.I length
-bytes from
-.IR offset ,
-shifting existing data.
-.TP
-.BR \-l ", " "\-\-length " \fIlength
-Specifies the length of the range, in bytes.
-.TP
-.BR \-n ", " \-\-keep\-size
-Do not modify the apparent length of the file. This may effectively allocate
-blocks past EOF, which can be removed with a truncate.
-.TP
-.BR \-o ", " "\-\-offset " \fIoffset
-Specifies the beginning offset of the range, in bytes.
-.TP
-.BR \-p ", " \-\-punch\-hole
-Deallocates space (i.e., creates a hole) in the byte range starting at
-.I offset
-and continuing for
-.I 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
-.B \-\-zero\-range
-option.
-Also, when using this option,
-.B \-\-keep\-size
-is implied.
-.sp
-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).
-.TP
-.BR \-v ", " \-\-verbose
-Enable verbose mode.
-.TP
-.BR \-x ", " \-\-posix
-Enable POSIX operation mode.
-In that mode allocation operation always completes,
-but it may take longer time when fast allocation is not supported by
-the underlying filesystem.
-.TP
-.BR \-z ", " \-\-zero\-range
-Zeroes space in the byte range starting at
-.I offset
-and continuing for
-.I 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.
-.sp
-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.
-.sp
-Option \fB\-\-keep\-size\fP can be specified to prevent file length
-modification.
-.sp
-Available since Linux 3.14 for ext4 (only for extent-based files) and XFS.
-.TP
-.BR \-V ", " \-\-version
-Display version information and exit.
-.TP
-.BR \-h ", " \-\-help
-Display help text and exit.
-.SH AUTHORS
-.MT sandeen@redhat.com
-Eric Sandeen
-.ME
-.br
-.MT kzak@redhat.com
-Karel Zak
-.ME
-.SH SEE ALSO
-.BR truncate (1),
-.BR fallocate (2),
-.BR posix_fallocate (3)
-.SH AVAILABILITY
-The fallocate command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" -----------------------------------------------------------------------
-.\"
-.\" Copyright 2003-2006 H. Peter Anvin - All Rights Reserved
-.\"
-.\" Permission is hereby granted, free of charge, to any person
-.\" obtaining a copy of this software and associated documentation
-.\" files (the "Software"), to deal in the Software without
-.\" restriction, including without limitation the rights to use,
-.\" copy, modify, merge, publish, distribute, sublicense, and/or
-.\" sell copies of the Software, and to permit persons to whom
-.\" the Software is furnished to do so, subject to the following
-.\" conditions:
-.\"
-.\" The above copyright notice and this permission notice shall
-.\" be included in all copies or substantial portions of the Software.
-.\"
-.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-.\" EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-.\" OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-.\" NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-.\" HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-.\" WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-.\" FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-.\" OTHER DEALINGS IN THE SOFTWARE.
-.\"
-.\" -----------------------------------------------------------------------
-.TH FLOCK 1 "July 2014" "util-linux" "User Commands"
-.SH NAME
-flock \- manage locks from shell scripts
-.SH SYNOPSIS
-.B flock
-[options]
-.IR file | "directory command " [ arguments ]
-.br
-.B flock
-[options]
-.IR file | directory
-.BI \-c " command"
-.br
-.B flock
-.RI [options] " number"
-.SH DESCRIPTION
-This utility manages
-.BR flock (2)
-locks from within shell scripts or from the command line.
-.PP
-The first and second of the above forms wrap the lock around the execution of a
-.IR command ,
-in a manner similar to
-.BR su (1)
-or
-.BR newgrp (1).
-They lock a specified \fIfile\fR or \fIdirectory\fR, which is created (assuming
-appropriate permissions) if it does not already exist. By default, if the
-lock cannot be immediately acquired,
-.B flock
-waits until the lock is available.
-.PP
-The third form uses an open file by its file descriptor \fInumber\fR.
-See the examples below for how that can be used.
-.SH OPTIONS
-.TP
-.BR \-c , " \-\-command " \fIcommand
-Pass a single \fIcommand\fR, without arguments, to the shell with
-.BR \-c .
-.TP
-.BR \-E , " \-\-conflict\-exit\-code " \fInumber
-The exit status used when the \fB\-n\fP option is in use, and the
-conflicting lock exists, or the \fB\-w\fP option is in use,
-and the timeout is reached. The default value is \fB1\fR.
-The \fInumber\fR has to be in the range of 0 to 255.
-.TP
-.BR \-F , " \-\-no\-fork"
-Do not fork before executing
-.IR command .
-Upon execution the flock process is replaced by
-.I command
-which continues to hold the lock. This option is incompatible with
-\fB\-\-close\fR as there would otherwise be nothing left to hold the lock.
-.TP
-.BR \-e , " \-x" , " \-\-exclusive"
-Obtain an exclusive lock, sometimes called a write lock. This is the
-default.
-.TP
-.BR \-n , " \-\-nb" , " \-\-nonblock"
-Fail rather than wait if the lock cannot be
-immediately acquired.
-See the
-.B \-E
-option for the exit status used.
-.TP
-.BR \-o , " \-\-close"
-Close the file descriptor on which the lock is held before executing
-.IR command .
-This is useful if
-.I command
-spawns a child process which should not be holding the lock.
-.TP
-.BR \-s , " \-\-shared"
-Obtain a shared lock, sometimes called a read lock.
-.TP
-.BR \-u , " \-\-unlock"
-Drop a lock. This is usually not required, since a lock is automatically
-dropped when the file is closed. However, it may be required in special
-cases, for example if the enclosed command group may have forked a background
-process which should not be holding the lock.
-.TP
-.BR \-w , " \-\-wait" , " \-\-timeout " \fIseconds
-Fail if the lock cannot be acquired within
-.IR seconds .
-Decimal fractional values are allowed.
-See the
-.B \-E
-option for the exit status used. The zero number of
-.I seconds
-is interpreted as \fB\-\-nonblock\fR.
-.TP
-.B \-\-verbose
-Report how long it took to acquire the lock, or why the lock could not be
-obtained.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH EXIT STATUS
-The command uses
-.B sysexits.h
-exit status values for everything, except when using either of the options
-.B \-n
-or
-.B \-w
-which report a failure to acquire the lock with an exit status given by the
-.B \-E
-option, or 1 by default. The exit status given by
-.B \-E has to be in the range of 0 to 255.
-.PP
-When using the \fIcommand\fR variant, and executing the child worked, then
-the exit status is that of the child command.
-.SH EXAMPLES
-Note that "shell> " in examples is a command line prompt.
-.TP
-shell1> flock /tmp \-c cat
-.TQ
-shell2> flock \-w .007 /tmp \-c echo; /bin/echo $?
-Set exclusive lock to directory /tmp and the second command will fail.
-.TP
-shell1> flock \-s /tmp \-c cat
-.TQ
-shell2> flock \-s \-w .007 /tmp \-c echo; /bin/echo $?
-Set shared lock to directory /tmp and the second command will not fail.
-Notice that attempting to get exclusive lock with second command would fail.
-.TP
-shell> flock \-x local-lock-file echo 'a b c'
-Grab the exclusive lock "local-lock-file" before running echo with 'a b c'.
-.TP
-(
-.TQ
- flock \-n 9 || exit 1
-.TQ
- # ... commands executed under lock ...
-.TQ
-) 9>/var/lock/mylockfile
-The form is convenient inside shell scripts. The mode used to open the file
-doesn't matter to
-.BR flock ;
-using
-.I >
-or
-.I >>
-allows the lockfile to be created if it does not already exist, however,
-write permission is required. Using
-.I <
-requires that the file already exists but only read permission is required.
-.TP
-[ "${FLOCKER}" != "$0" ] && exec env FLOCKER="$0" flock \-en "$0" "$0" "$@" || :
-This is useful boilerplate code for shell scripts. Put it at the top of the
-shell script you want to lock and it'll automatically lock itself on the first
-run. If the env var $FLOCKER is not set to the shell script that is being run,
-then execute flock and grab an exclusive non-blocking lock (using the script
-itself as the lock file) before re-execing itself with the right arguments. It
-also sets the FLOCKER env var to the right value so it doesn't run again.
-.TP
-shell> exec 4<>/var/lock/mylockfile
-.TQ
-shell> flock -n 4
-This form is convenient for locking a file without spawning a subprocess.
-The shell opens the lock file for reading and writing as file descriptor 4,
-then flock is used to lock the descriptor.
-.SH AUTHORS
-.UR hpa@zytor.com
-H. Peter Anvin
-.UE
-.SH COPYRIGHT
-Copyright \(co 2003\-2006 H. Peter Anvin.
-.br
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-.SH SEE ALSO
-.BR flock (2)
-.SH AVAILABILITY
-The flock command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH FSFREEZE 8 "July 2014" "util-linux" "System Administration"
-.SH NAME
-fsfreeze \- suspend access to a filesystem (Ext3/4, ReiserFS, JFS, XFS)
-.SH SYNOPSIS
-.B fsfreeze
-.BR \--freeze | \--unfreeze
-.I mountpoint
-
-.SH DESCRIPTION
-.B fsfreeze
-suspends or resumes access to a filesystem.
-.PP
-.B fsfreeze
-halts any new access to the filesystem and creates a stable image on disk.
-.B fsfreeze
-is intended to be used with hardware RAID devices that support the creation
-of snapshots.
-.PP
-.B fsfreeze
-is unnecessary for
-.B device-mapper
-devices. The device-mapper (and LVM) automatically freezes a filesystem
-on the device when a snapshot creation is requested.
-For more details see the
-.BR dmsetup (8)
-man page.
-.PP
-The
-.I mountpoint
-argument is the pathname of the directory where the filesystem
-is mounted.
-The filesystem must be mounted to be frozen (see
-.BR mount (8)).
-.PP
-Note that access-time updates are also suspended if the filesystem is mounted with
-the traditional atime behavior (mount option \fBstrictatime\fR, for more details see
-.BR mount (8)).
-
-.SH OPTIONS
-.TP
-.BR \-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.
-.sp
-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.
-.TP
-.BR \-u , " \-\-unfreeze"
-This option is used to un-freeze the filesystem and allow operations to
-continue. Any filesystem modifications that were blocked by the freeze are
-unblocked and allowed to complete.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH FILESYSTEM SUPPORT
-This command will work only if filesystem supports has support for freezing.
-List of these filesystems include (2016-12-18)
-.BR btrfs ,
-.BR ext2/3/4 ,
-.BR f2fs ,
-.BR jfs ,
-.BR nilfs2 ,
-.BR reiserfs ,
-and
-.BR xfs .
-Previous list may be incomplete, as more filesystems get support. If in
-doubt easiest way to know if a filesystem has support is create a small
-loopback mount and test freezing it.
-.SH NOTES
-This man page is based on
-.BR xfs_freeze (8).
-.SH AUTHORS
-Written by Hajime Taira.
-.SH SEE ALSO
-.BR mount (8)
-.SH AVAILABILITY
-The fsfreeze command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright (c) 1980, 1989, 1991 The Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)fstab.5 6.5 (Berkeley) 5/10/91
-.\"
-.TH FSTAB 5 "February 2015" "util-linux" "File Formats"
-.SH NAME
-fstab \- static information about the filesystems
-.SH SYNOPSIS
-.I /etc/fstab
-.SH DESCRIPTION
-The file
-.B fstab
-contains descriptive information about the filesystems the system can mount.
-.B fstab
-is only read by programs, and not written; it is the duty of the system
-administrator to properly create and maintain this file. The order of records in
-.B fstab
-is important because
-.BR fsck (8),
-.BR mount (8),
-and
-.BR umount (8)
-sequentially iterate through
-.B fstab
-doing their thing.
-
-Each filesystem is described on a separate line.
-Fields on each line are separated by tabs or spaces.
-Lines starting with '#' are comments. Blank lines are ignored.
-.PP
-The following is a typical example of an
-.B fstab
-entry:
-.sp
-.RS 7
-LABEL=t-home2 /home ext4 defaults,auto_da_alloc 0 2
-.RE
-
-.B The first field
-.RI ( fs_spec ).
-.RS
-This field describes the block special device, remote filesystem or filesystem
-image for loop device to be mounted or swap file or swap partition to be enabled.
-.LP
-For ordinary mounts, it will hold (a link to) a block special
-device node (as created by
-.BR mknod (2))
-for the device to be mounted, like `/dev/cdrom' or `/dev/sdb7'.
-For NFS mounts, this field is <host>:<dir>, e.g., `knuth.aeb.nl:/'.
-For filesystems with no storage, any string can be used, and will show up in
-.BR df (1)
-output, for example. Typical usage is `proc' for procfs; `mem', `none',
-or `tmpfs' for tmpfs. Other special filesystems, like udev and sysfs,
-are typically not listed in
-.BR fstab .
-.LP
-LABEL=<label> or UUID=<uuid> may be given instead of a device name.
-This is the recommended method, as device names are often a coincidence
-of hardware detection order, and can change when other disks are added or removed.
-For example, `LABEL=Boot' or `UUID=3e6be9de\%-8139\%-11d1\%-9106\%-a43f08d823a6'.
-(Use a filesystem-specific tool like
-.BR e2label (8),
-.BR xfs_admin (8),
-or
-.BR fatlabel (8)
-to set LABELs on filesystems).
-
-It's also possible to use PARTUUID= and PARTLABEL=. These partitions identifiers
-are supported for example for GUID Partition Table (GPT).
-
-See
-.BR mount (8),
-.BR blkid (8)
-or
-.BR lsblk (8)
-for more details about device identifiers.
-
-.LP
-Note that
-.BR mount (8)
-uses UUIDs as strings. The string representation of the UUID should be based on
-lower case characters.
-But when specifying the volume ID of FAT or NTFS file systems upper case
-characters are used (e.g UUID="A40D-85E7" or UUID="61DB7756DB7779B3").
-.RE
-
-.B The second field
-.RI ( fs_file ).
-.RS
-This field describes the mount point (target) for the filesystem. For swap partitions, this
-field should be specified as `none'. If the name of the mount point
-contains spaces or tabs these can be escaped as `\\040' and '\\011'
-respectively.
-.RE
-
-.B The third field
-.RI ( fs_vfstype ).
-.RS
-This field describes the type of the filesystem. Linux supports many
-filesystem types: ext4, xfs, btrfs, f2fs, vfat, ntfs, hfsplus,
-tmpfs, sysfs, proc, iso9660, udf, squashfs, nfs, cifs, and many more.
-For more details, see
-.BR mount (8).
-
-An entry
-.I swap
-denotes a file or partition to be used
-for swapping, cf.\&
-.BR swapon (8).
-An entry
-.I none
-is useful for bind or move mounts.
-
-More than one type may be specified in a comma-separated list.
-
-.BR mount (8)
-and
-.BR umount (8)
-support filesystem
-.IR subtypes .
-The subtype is defined by '.subtype' suffix. For
-example 'fuse.sshfs'. It's recommended to use subtype notation rather than add
-any prefix to the first fstab field (for example 'sshfs#example.com' is
-deprecated).
-.RE
-
-.B The fourth field
-.RI ( fs_mntops ).
-.RS
-This field describes the mount options associated with the filesystem.
-
-It is formatted as a comma-separated list of options.
-It contains at least the type of mount
-.RB ( ro
-or
-.BR rw ),
-plus any additional options appropriate to the filesystem
-type (including performance-tuning options).
-For details, see
-.BR mount (8)
-or
-.BR swapon (8).
-
-Basic filesystem-independent options are:
-.TP
-.B defaults
-use default options: rw, suid, dev, exec, auto, nouser, and async.
-.TP
-.B noauto
-do not mount when "mount \-a" is given (e.g., at boot time)
-.TP
-.B user
-allow a user to mount
-.TP
-.B owner
-allow device owner to mount
-.TP
-.B comment
-or
-.B x-<name>
-for use by fstab-maintaining programs
-.TP
-.B nofail
-do not report errors for this device if it does not exist.
-.RE
-
-.B The fifth field
-.RI ( fs_freq ).
-.RS
-This field is used by
-.BR dump (8)
-to determine which filesystems need to be dumped.
-Defaults to zero (don't dump) if not present.
-.RE
-
-.B The sixth field
-.RI ( fs_passno ).
-.RS
-This field is used by
-.BR fsck (8)
-to determine the order in which filesystem checks are done at
-boot time. The root filesystem should be specified with a
-.I fs_passno
-of 1. Other filesystems should have a
-.I fs_passno
-of 2. Filesystems within a drive will be checked sequentially, but
-filesystems on different drives will be checked at the same time to utilize
-parallelism available in the hardware.
-Defaults to zero (don't fsck) if not present.
-.RE
-
-.SH FILES
-.IR /etc/fstab ,
-.I <fstab.h>
-
-.SH NOTES
-The proper way to read records from
-.B fstab
-is to use the routines
-.BR getmntent (3)
-or
-.BR libmount .
-
-The keyword
-.B ignore
-as a filesystem type (3rd field) is no longer supported by the pure
-libmount based mount utility (since util-linux v2.22).
-.SH HISTORY
-The ancestor of this
-.B fstab
-file format appeared in 4.0BSD.
-.\" But without comment convention, and options and vfs_type.
-.SH SEE ALSO
-.BR getmntent (3),
-.BR fs (5),
-.BR findmnt (8),
-.BR mount (8),
-.BR swapon (8)
-.\" Instead there was a type rw/ro/rq/sw/xx, where xx is the present 'ignore'.
-.SH AVAILABILITY
-This man page is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH FSTRIM 8 "May 2019" "util-linux" "System Administration"
-.SH NAME
-fstrim \- discard unused blocks on a mounted filesystem
-.SH SYNOPSIS
-.B fstrim
-.RB [ \-Aa ]
-.RB [ \-o
-.IR offset ]
-.RB [ \-l
-.IR length ]
-.RB [ \-m
-.IR minimum-size ]
-.RB [ \-v ]
-.I mountpoint
-
-.SH DESCRIPTION
-.B fstrim
-is used on a mounted filesystem to discard (or "trim") blocks which are not in
-use by the filesystem. This is useful for solid-state drives (SSDs) and
-thinly-provisioned storage.
-.PP
-By default,
-.B fstrim
-will discard all unused blocks in the filesystem. Options may be used to
-modify this behavior based on range or size, as explained below.
-.PP
-The
-.I mountpoint
-argument is the pathname of the directory where the filesystem
-is mounted.
-.PP
-Running
-.B fstrim
-frequently, or even using
-.BR "mount \-o discard" ,
-might negatively affect the lifetime of poor-quality SSD devices. For most
-desktop and server systems a sufficient trimming frequency is once a week.
-Note that not all
-devices support a queued trim, so each trim command incurs a performance penalty
-on whatever else might be trying to use the disk at the time.
-
-.SH OPTIONS
-The \fIoffset\fR, \fIlength\fR, and \fIminimum-size\fR arguments 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.
-
-.IP "\fB\-A, \-\-fstab\fP"
-Trim all mounted filesystems mentioned in \fI/etc/fstab\fR on devices that support the
-discard operation. The root filesystem is determined from kernel command line if missing
-in the file.
-The other supplied options, like \fB\-\-offset\fR, \fB\-\-length\fR and
-\fB-\-minimum\fR, are applied to all these devices.
-Errors from filesystems that do not support the discard operation,
-read-only devices and read-only filesystems are silently ignored.
-.IP "\fB\-a, \-\-all\fP"
-Trim all mounted filesystems on devices that support the discard operation.
-The other supplied options, like \fB\-\-offset\fR, \fB\-\-length\fR and
-\fB-\-minimum\fR, are applied to all these devices.
-Errors from filesystems that do not support the discard operation,
-read-only devices and read-only filesystems are silently ignored.
-.IP "\fB\-n, \-\-dry\-run\fP"
-This option does everything apart from actually call FITRIM ioctl.
-.IP "\fB\-o, \-\-offset\fP \fIoffset\fP"
-Byte offset in the filesystem from which to begin searching for free blocks
-to discard. The default value is zero, starting at the beginning of the
-filesystem.
-.IP "\fB\-l, \-\-length\fP \fIlength\fP"
-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,
-.B fstrim
-will stop at the filesystem size boundary. The default value extends to
-the end of the filesystem.
-.IP "\fB\-I, \-\-listed\-in\fP \fIlist\fP"
-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
-\fIlist\fP stops after first non-empty file. For example: \fB--listed-in /etc/fstab:/proc/self/mountinfo\fR.
-.IP "\fB\-m, \-\-minimum\fP \fIminimum-size\fP"
-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.
-.IP "\fB\-v, \-\-verbose\fP"
-Verbose execution. With this option
-.B 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
-.I FITRIM
-ioctl called repeated will keep sending the same sectors for discard repeatedly.
-.sp
-.B 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
-.B \-\-length
-option).
-.TP
-.B \-\-quiet\-unsupported
-Suppress error messages if trim operation (ioctl) is unsupported. This option
-is meant to be used in systemd service file or in cron scripts to hide warnings
-that are result of known problems,
-such as NTFS driver
-reporting
-.I Bad file descriptor
-when device is mounted read-only, or lack of file system support for ioctl
-FITRIM call.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-
-.SH EXIT STATUS
-.IP 0
-success
-.IP 1
-failure
-.IP 32
-all failed
-.IP 64
-some filesystem discards have succeeded, some failed
-.PP
-The command
-.B fstrim \-\-all
-returns 0 (all succeeded), 32 (all failed) or 64 (some failed, some succeeded).
-
-.SH AUTHORS
-.nf
-Lukas Czerner <lczerner@redhat.com>
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.BR blkdiscard (8),
-.BR mount (8)
-.SH AVAILABILITY
-The fstrim command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" hwclock.8.in -- man page for util-linux' hwclock
-.\"
-.\" 2015-01-07 J William Piggott
-.\" Authored new section: DATE-TIME CONFIGURATION.
-.\" Subsections: Keeping Time..., LOCAL vs UTC, POSIX vs 'RIGHT'.
-.\"
-.TH HWCLOCK 8 "July 2017" "util-linux" "System Administration"
-.SH NAME
-hwclock \- time clocks utility
-.SH SYNOPSIS
-.B hwclock
-.RI [ function ]
-.RI [ option ...]
-.
-.SH DESCRIPTION
-.B hwclock
-is an administration tool for the time clocks. It can: display the
-Hardware Clock time; set the Hardware Clock to a specified time; set the
-Hardware Clock from the System Clock; set the System Clock from the
-Hardware Clock; compensate for Hardware Clock drift; correct the System
-Clock timescale; set the kernel's timezone, NTP timescale, and epoch
-(Alpha only); and predict future
-Hardware Clock values based on its drift rate.
-.PP
-Since v2.26 important changes were made to the
-.B \-\-hctosys
-function and the
-.B \-\-directisa
-option, and a new option
-.B \-\-update\-drift
-was added. See their respective descriptions below.
-.
-.SH FUNCTIONS
-The following functions are mutually exclusive, only one can be given at
-a time. If none is given, the default is \fB\-\-show\fR.
-.TP
-.B \-a, \-\-adjust
-Add or subtract time from the Hardware Clock to account for systematic
-drift since the last time the clock was set or adjusted. See the
-discussion below, under
-.BR "The Adjust Function" .
-.
-.TP
-.B \-\-getepoch
-.TQ
-.B \-\-setepoch
-These functions are for Alpha machines only, and are only available
-through the Linux kernel RTC driver.
-.sp
-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.
-.sp
-The \fB\%\-\-setepoch\fR function requires using the
-.B \%\-\-epoch
-option to specify the year. For example:
-.RS
-.IP "" 4
-.B hwclock\ \-\-setepoch\ \-\-epoch=1952
-.PP
-The RTC driver attempts to guess the correct epoch value, so setting it
-may not be required.
-.PP
-This epoch value is used whenever
-.B \%hwclock
-reads or sets the Hardware Clock on an Alpha machine. For ISA machines
-the kernel uses the fixed Hardware Clock epoch of 1900.
-.RE
-.
-.TP
-.B \-\-predict
-Predict what the Hardware Clock will read in the future based upon the
-time given by the
-.B \-\-date
-option and the information in
-.IR @ADJTIME_PATH@ .
-This is useful, for example, to account for drift when setting a
-Hardware Clock wakeup (aka alarm). See
-.BR \%rtcwake (8).
-.sp
-Do not use this function if the Hardware Clock is being modified by
-anything other than the current operating system's
-.B \%hwclock
-command, such as \%'11\ minute\ mode' or from dual-booting another OS.
-.
-.TP
-.BR \-r , \ \-\-show
-.TQ
-.B \-\-get
-.br
-Read the Hardware Clock and print its time to standard output in the
-.B ISO 8601
-format.
-The time shown is always in local time, even if you keep your Hardware Clock
-in UTC. See the
-.B \%\-\-localtime
-option.
-.sp
-Showing the Hardware Clock time is the default when no function is specified.
-.sp
-The
-.B \-\-get
-function also applies drift correction to the time read, based upon the
-information in
-.IR @ADJTIME_PATH@ .
-Do not use this function if the Hardware Clock is being modified by
-anything other than the current operating system's
-.B \%hwclock
-command, such as \%'11\ minute\ mode' or from dual-booting another OS.
-.
-.TP
-.BR \-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
-.BR "The Adjust Function" .
-.sp
-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
-.B \%\-\-hctosys
-function does this based upon the information in the
-.I @ADJTIME_PATH@
-file or the command line arguments
-.BR \%\-\-localtime " and " \-\-utc .
-Note: no daylight saving adjustment is made. See the discussion below, under
-.BR "LOCAL vs UTC" .
-.sp
-The kernel also keeps a timezone value, the
-.B \%\-\-hctosys
-function sets it to the timezone configured for the system. The system
-timezone is configured by the TZ environment variable or the
-.I \%/etc/localtime
-file, as
-.BR \%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
-.BR \%settimeofday (2).)
-.sp
-When used in a startup script, making the
-.B \%\-\-hctosys
-function the first caller of
-.BR \%settimeofday (2)
-from boot, it will set the NTP \%'11\ minute\ mode' timescale via the
-.I \%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
-.BR "Automatic Hardware Clock Synchronization by the Kernel" .
-.sp
-This is a good function to use in one of the system startup scripts before the
-file systems are mounted read/write.
-.sp
-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
-.B \%\-\-hctosys
-will set the time incorrectly by including drift compensation.
-.sp
-Drift compensation can be inhibited by setting the drift factor in
-.I @ADJTIME_PATH@
-to zero. This setting will be persistent as long as the
-.BR \%\-\-update\-drift " option is not used with " \%\-\-systohc
-at shutdown (or anywhere else). Another way to inhibit this is by using the
-.BR \%\-\-noadjfile " option when calling the " \%\-\-hctosys
-function. A third method is to delete the
-.IR @ADJTIME_PATH@ " file."
-.B 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
-.BR 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.
-.sp
-A condition under which inhibiting
-.BR 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.
-.sp
-.RB "For " hwclock 's
-drift correction to work properly it is imperative that nothing changes
-the Hardware Clock while its Linux instance is not running.
-.
-.TP
-.B \-\-set
-Set the Hardware Clock to the time given by the
-.B \-\-date
-option, and update the timestamps in
-.IR @ADJTIME_PATH@ .
-With the
-.B \%\-\-update-drift
-option also (re)calculate the drift factor. Try it without the option if
-.BR \%\-\-set " fails. See " \%\-\-update-drift " below."
-.
-.TP
-.B \-\-systz
-This is an alternate to the
-.B \%\-\-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.
-.sp
-It does the following things that are detailed above in the
-.BR \%\-\-hctosys " function:"
-.RS
-.IP \(bu 2
-Corrects the System Clock timescale to UTC as needed. Only instead of
-accomplishing this by setting the System Clock,
-.B hwclock
-simply informs the kernel and it handles the change.
-.IP \(bu 2
-Sets the kernel's NTP \%'11\ minute\ mode' timescale.
-.IP \(bu 2
-Sets the kernel's timezone.
-.PP
-The first two are only available on the first call of
-.BR \%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.
-.RE
-.
-.TP
-.BR \-w , \ \-\-systohc
-Set the Hardware Clock from the System Clock, and update the timestamps in
-.IR @ADJTIME_PATH@ .
-With the
-.B \%\-\-update-drift
-option also (re)calculate the drift factor. Try it without the option if
-.BR \%\-\-systohc " fails. See " \%\-\-update-drift " below."
-.
-.TP
-.BR \-V , \ \-\-version
-Display version information and exit.
-.
-.TP
-.BR \-h , \ \-\-help
-Display help text and exit.
-.
-.SH OPTIONS
-.
-.TP
-.BI \-\-adjfile= filename
-.RI "Override the default " @ADJTIME_PATH@ " file path."
-.
-.TP
-.BI \%\-\-date= date_string
-This option must be used with the
-.B \-\-set
-or
-.B \%\-\-predict
-functions, otherwise it is ignored.
-.RS
-.IP "" 4
-.B "hwclock\ \-\-set\ \-\-date='16:45'"
-.IP "" 4
-.B "hwclock\ \-\-predict\ \-\-date='2525-08-14\ 07:11:05'"
-.PP
-The argument must be in local time, even if you keep your Hardware Clock in
-UTC. See the
-.B \%\-\-localtime
-option. Therefore, the argument should not include any timezone information.
-It also should not be a relative time like "+5 minutes", because
-.BR \%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.
-.RE
-.
-.TP
-.BI \%\-\-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.
-.RS
-.PP
-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.
-.RE
-.
-.TP
-.BR \-D ", " \-\-debug
-.RB Use\ \-\-verbose .
-.RB The\ \%\-\-debug\ option
-has been deprecated and may be repurposed or removed in a future release.
-.
-.TP
-.B \-\-directisa
-This option is meaningful for ISA compatible machines in the x86 and
-x86_64 family. For other machines, it has no effect. This option tells
-.B \%hwclock
-to use explicit I/O instructions to access the Hardware Clock.
-Without this option,
-.B \%hwclock
-will use the rtc device file, which it assumes to be driven by the Linux
-RTC device driver. As of v2.26 it will no longer automatically use
-directisa when the rtc driver is unavailable; this was causing an unsafe
-condition that could allow two processes to access the Hardware Clock at
-the same time. Direct hardware access from userspace should only be
-used for testing, troubleshooting, and as a last resort when all other
-methods fail. See the
-.BR \-\-rtc " option."
-.
-.TP
-.BI \-\-epoch= year
-This option is required when using the
-.BR \%\-\-setepoch \ function.
-.RI "The minimum " year
-value is 1900. The maximum is system dependent
-.RB ( ULONG_MAX\ -\ 1 ).
-.
-.TP
-.BR \-f , \ \-\-rtc=\fIfilename\fR
-.RB "Override " \%hwclock 's
-default rtc device file name. Otherwise it will
-use the first one found in this order:
-.in +4
-.br
-.I /dev/rtc0
-.br
-.I /dev/rtc
-.br
-.I /dev/misc/rtc
-.br
-.in
-.RB "For " IA-64:
-.in +4
-.br
-.I /dev/efirtc
-.br
-.I /dev/misc/efirtc
-.in
-.
-.TP
-.BR \-l , \ \-\-localtime
-.TQ
-.BR \-u ", " \-\-utc
-Indicate which timescale the Hardware Clock is set to.
-.sp
-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
-.BR \%\-\-localtime " or " \-\-utc
-options give this information to the
-.B \%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.
-.sp
-If you specify neither
-.BR \-\-utc " nor " \%\-\-localtime
-then the one last given with a set function
-.RB ( \-\-set ", " \%\-\-systohc ", or " \%\-\-adjust ),
-as recorded in
-.IR @ADJTIME_PATH@ ,
-will be used. If the adjtime file doesn't exist, the default is UTC.
-.sp
-Note: daylight saving time changes may be inconsistent when the
-Hardware Clock is kept in local time. See the discussion below, under
-.BR "LOCAL vs UTC" .
-.
-.TP
-.B \-\-noadjfile
-Disable the facilities provided by
-.IR @ADJTIME_PATH@ .
-.B \%hwclock
-will not read nor write to that file with this option. Either
-.BR \-\-utc " or " \%\-\-localtime
-must be specified when using this option.
-.
-.TP
-.B \-\-test
-Do not actually change anything on the system, that is, the Clocks or
-.I @ADJTIME_PATH@
-.RB ( \%\-\-verbose
-is implicit with this option).
-.
-.TP
-.B \-\-update\-drift
-Update the Hardware Clock's drift factor in
-.IR @ADJTIME_PATH@ .
-It can only be used with
-.BR \-\-set " or " \%\-\-systohc ,
-.sp
-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.
-.sp
-This option was added in v2.26, because
-it is typical for systems to call
-.B \%hwclock\ \-\-systohc
-at shutdown; with the old behaviour this would automatically
-(re)calculate the drift factor which caused several problems:
-.RS
-.IP \(bu 2
-When using NTP with an \%'11\ minute\ mode' kernel the drift factor
-would be clobbered to near zero.
-.IP \(bu 2
-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.
-.IP \(bu 2
-(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.
-.IP \(bu 2
-Significantly increased system shutdown times (as of v2.31 when not
-using
-.B \%\-\-update\-drift
-the RTC is not read).
-.PP
-.RB "Having " \%hwclock
-calculate the drift factor is a good starting point, but for optimal
-results it will likely need to be adjusted by directly editing the
-.I @ADJTIME_PATH@
-file. For most configurations once a machine's optimal drift factor is
-crafted it should not need to be changed. Therefore, the old behavior to
-automatically (re)calculate drift was changed and now requires this
-option to be used. See the discussion below, under
-.BR "The Adjust Function" .
-.PP
-This option requires reading the Hardware Clock before setting it. If
-it cannot be read, then this option will cause the set functions to fail.
-This can happen, for example, if the Hardware Clock is corrupted by a
-power failure. In that case, the clock must first be set without this
-option. Despite it not working, the resulting drift correction factor
-would be invalid anyway.
-.RE
-.
-.TP
-.BR \-v ", " \-\-verbose
-Display more details about what
-.B \%hwclock
-is doing internally.
-.
-.SH NOTES
-.
-.SS Clocks in a Linux System
-There are two types of date-time clocks:
-.PP
-.B The Hardware Clock:
-This clock is an independent hardware device, with its own power domain
-(battery, capacitor, etc), that operates when the machine is powered off,
-or even unplugged.
-.PP
-On an ISA compatible system, this clock is specified as part of the ISA
-standard. A control program can read or set this clock only to a whole
-second, but it can also detect the edges of the 1 second clock ticks, so
-the clock actually has virtually infinite precision.
-.PP
-This clock is commonly called the hardware clock, the real time clock,
-the RTC, the BIOS clock, and the CMOS clock. Hardware Clock, in its
-capitalized form, was coined for use by
-.BR \%hwclock .
-The Linux kernel also refers to it as the persistent clock.
-.PP
-Some non-ISA systems have a few real time clocks with
-only one of them having its own power domain.
-A very low power external I2C or SPI clock chip might be used with a
-backup battery as the hardware clock to initialize a more functional
-integrated real-time clock which is used for most other purposes.
-.PP
-.B The System Clock:
-This clock is part of the Linux kernel and is driven by
-a timer interrupt. (On an ISA machine, the timer interrupt is part of
-the ISA standard.) It has meaning only while Linux is running on the
-machine. The System Time is the number of seconds since 00:00:00
-January 1, 1970 UTC (or more succinctly, the number of seconds since
-1969 UTC). The System Time is not an integer, though. It has virtually
-infinite precision.
-.PP
-The System Time is the time that matters. The Hardware Clock's basic
-purpose is to keep time when Linux is not running so that the System
-Clock can be initialized from it at boot. Note that in DOS, for which
-ISA was designed, the Hardware Clock is the only real time clock.
-.PP
-It is important that the System Time not have any discontinuities such as
-would happen if you used the
-.BR \%date (1)
-program to set it while the system is running. You can, however, do whatever
-you want to the Hardware Clock while the system is running, and the next
-time Linux starts up, it will do so with the adjusted time from the Hardware
-Clock. Note: currently this is not possible on most systems because
-.B \%hwclock\ \-\-systohc
-is called at shutdown.
-.PP
-The Linux kernel's timezone is set by
-.BR hwclock .
-But don't be misled -- almost nobody cares what timezone the kernel
-thinks it is in. Instead, programs that care about the timezone
-(perhaps because they want to display a local time for you) almost
-always use a more traditional method of determining the timezone: They
-use the TZ environment variable or the
-.I \%/etc/localtime
-file, as explained in the man page for
-.BR \%tzset (3).
-However, some programs and fringe parts of the Linux kernel such as filesystems
-use the kernel's timezone value. An example is the vfat filesystem. If the
-kernel timezone value is wrong, the vfat filesystem will report and set the
-wrong timestamps on files. Another example is the kernel's NTP \%'11\ minute\ mode'.
-If the kernel's timezone value and/or the
-.I \%persistent_clock_is_local
-variable are wrong, then the Hardware Clock will be set incorrectly
-by \%'11\ minute\ mode'. See the discussion below, under
-.BR "Automatic Hardware Clock Synchronization by the Kernel" .
-.PP
-.B \%hwclock
-sets the kernel's timezone to the value indicated by TZ or
-.IR \%/etc/localtime " with the"
-.BR \%\-\-hctosys " or " \%\-\-systz " functions."
-.PP
-The kernel's timezone value actually consists of two parts: 1) a field
-tz_minuteswest indicating how many minutes local time (not adjusted
-for DST) lags behind UTC, and 2) a field tz_dsttime indicating
-the type of Daylight Savings Time (DST) convention that is in effect
-in the locality at the present time.
-This second field is not used under Linux and is always zero.
-See also
-.BR \%settimeofday (2).
-.
-.SS Hardware Clock Access Methods
-.B \%hwclock
-uses many different ways to get and set Hardware Clock values. The most
-normal way is to do I/O to the rtc device special file, which is
-presumed to be driven by the rtc device driver. Also, Linux systems
-using the rtc framework with udev, are capable of supporting multiple
-Hardware Clocks. This may bring about the need to override the default
-rtc device by specifying one with the
-.BR \-\-rtc " option."
-.PP
-However, this method is not always available as older systems do not
-have an rtc driver. On these systems, the method of accessing the
-Hardware Clock depends on the system hardware.
-.PP
-On an ISA compatible system,
-.B \%hwclock
-can directly access the "CMOS memory" registers that
-constitute the clock, by doing I/O to Ports 0x70 and 0x71. It does
-this with actual I/O instructions and consequently can only do it if
-running with superuser effective userid. This method may be used by
-specifying the
-.BR \%\-\-directisa " option."
-.PP
-This is a really poor method of accessing the clock, for all the
-reasons that userspace programs are generally not supposed to do
-direct I/O and disable interrupts.
-.B \%hwclock
-provides it for testing, troubleshooting, and because it may be the
-only method available on ISA systems which do not have a working rtc
-device driver.
-.SS The Adjust Function
-The Hardware Clock is usually not very accurate. However, much of its
-inaccuracy is completely predictable - it gains or loses the same amount
-of time every day. This is called systematic drift.
-.BR \%hwclock "'s " \%\-\-adjust
-function lets you apply systematic drift corrections to the
-Hardware Clock.
-.PP
-It works like this:
-.BR \%hwclock " keeps a file,"
-.IR @ADJTIME_PATH@ ,
-that keeps some historical information. This is called the adjtime file.
-.PP
-Suppose you start with no adjtime file. You issue a
-.B \%hwclock\ \-\-set
-command to set the Hardware Clock to the true current time.
-.B \%hwclock
-creates the adjtime file and records in it the current time as the
-last time the clock was calibrated.
-Five days later, the clock has gained 10 seconds, so you issue a
-.B \%hwclock\ \-\-set\ \-\-update\-drift
-command to set it back 10 seconds.
-.B \%hwclock
-updates the adjtime file to show the current time as the last time the
-clock was calibrated, and records 2 seconds per day as the systematic
-drift rate. 24 hours go by, and then you issue a
-.B \%hwclock\ \-\-adjust
-command.
-.B \%hwclock
-consults the adjtime file and sees that the clock gains 2 seconds per
-day when left alone and that it has been left alone for exactly one
-day. So it subtracts 2 seconds from the Hardware Clock. It then
-records the current time as the last time the clock was adjusted.
-Another 24 hours go by and you issue another
-.BR \%hwclock\ \-\-adjust .
-.B \%hwclock
-does the same thing: subtracts 2 seconds and updates the adjtime file
-with the current time as the last time the clock was adjusted.
-.PP
-When you use the
-.BR \%\-\-update\-drift " option with " \-\-set " or " \%\-\-systohc ,
-the systematic drift rate is (re)calculated by comparing the fully drift
-corrected current Hardware Clock time with the new set time, from that
-it derives the 24 hour drift rate based on the last calibrated timestamp
-from the adjtime file. This updated drift factor is then saved in
-.IR @ADJTIME_PATH@ .
-.PP
-A small amount of error creeps in when
-the Hardware Clock is set, so
-.B \%\-\-adjust
-refrains from making any adjustment that is less
-than 1 second. Later on, when you request an adjustment again, the accumulated
-drift will be more than 1 second and
-.B \%\-\-adjust
-will make the adjustment including any fractional amount.
-.PP
-.B \%hwclock\ \-\-hctosys
-also uses the adjtime file data to compensate the value read from the Hardware
-Clock before using it to set the System Clock. It does not share the 1 second
-limitation of
-.BR \%\-\-adjust ,
-and will correct sub-second drift values immediately. It does not
-change the Hardware Clock time nor the adjtime file. This may eliminate
-the need to use
-.BR \%\-\-adjust ,
-unless something else on the system needs the Hardware Clock to be
-compensated.
-.
-.SS The Adjtime File
-While named for its historical purpose of controlling adjustments only,
-it actually contains other information used by
-.B hwclock
-from one invocation to the next.
-.PP
-The format of the adjtime file is, in ASCII:
-.PP
-Line 1: Three numbers, separated by blanks: 1) the systematic drift rate
-in seconds per day, floating point decimal; 2) the resulting number of
-seconds since 1969 UTC of most recent adjustment or calibration,
-decimal integer; 3) zero (for compatibility with
-.BR \%clock (8))
-as a floating point decimal.
-.PP
-Line 2: One number: the resulting number of seconds since 1969 UTC of most
-recent calibration. Zero if there has been no calibration yet or it
-is known that any previous calibration is moot (for example, because
-the Hardware Clock has been found, since that calibration, not to
-contain a valid time). This is a decimal integer.
-.PP
-Line 3: "UTC" or "LOCAL". Tells whether the Hardware Clock is set to
-Coordinated Universal Time or local time. You can always override this
-value with options on the
-.B \%hwclock
-command line.
-.PP
-You can use an adjtime file that was previously used with the
-.BR \%clock "(8) program with " \%hwclock .
-.
-.SS Automatic Hardware Clock Synchronization by the Kernel
-You should be aware of another way that the Hardware Clock is kept
-synchronized in some systems. The Linux kernel has a mode wherein it
-copies the System Time to the Hardware Clock every 11 minutes. This mode
-is a compile time option, so not all kernels will have this capability.
-This is a good mode to use when you are using something sophisticated
-like NTP to keep your System Clock synchronized. (NTP is a way to keep
-your System Time synchronized either to a time server somewhere on the
-network or to a radio clock hooked up to your system. See RFC 1305.)
-.PP
-If the kernel is compiled with the \%'11\ minute\ mode' option it will
-be active when the kernel's clock discipline is in a synchronized state.
-When in this state, bit 6 (the bit that is set in the mask 0x0040)
-of the kernel's
-.I \%time_status
-variable is unset. This value is output as the 'status' line of the
-.BR \%adjtimex\ --print " or " \%ntptime " commands."
-.PP
-It takes an outside influence, like the NTP daemon
-to put the kernel's clock discipline into a synchronized state, and
-therefore turn on \%'11\ minute\ mode'.
-It can be turned off by running anything that sets the System Clock the old
-fashioned way, including
-.BR "\%hwclock\ \-\-hctosys" .
-However, if the NTP daemon is still running, it will turn \%'11\ minute\ mode'
-back on again the next time it synchronizes the System Clock.
-.PP
-If your system runs with \%'11\ minute\ mode' on, it may need to use either
-.BR \%\-\-hctosys " or " \%\-\-systz
-in a startup script, especially if the Hardware Clock is configured to use
-the local timescale. Unless the kernel is informed of what timescale the
-Hardware Clock is using, it may clobber it with the wrong one. The kernel
-uses UTC by default.
-.PP
-The first userspace command to set the System Clock informs the
-kernel what timescale the Hardware Clock is using. This happens via the
-.I \%persistent_clock_is_local
-kernel variable. If
-.BR \%\-\-hctosys " or " \%\-\-systz
-is the first, it will set this variable according to the adjtime file or the
-appropriate command-line argument. Note that when using this capability and the
-Hardware Clock timescale configuration is changed, then a reboot is required to
-notify the kernel.
-.PP
-.B \%hwclock\ \-\-adjust
-should not be used with NTP \%'11\ minute\ mode'.
-.
-.SS ISA Hardware Clock Century value
-There is some sort of standard that defines CMOS memory Byte 50 on an ISA
-machine as an indicator of what century it is.
-.B \%hwclock
-does not use or set that byte because there are some machines that
-don't define the byte that way, and it really isn't necessary anyway,
-since the year-of-century does a good job of implying which century it
-is.
-.PP
-If you have a bona fide use for a CMOS century byte, contact the
-.B \%hwclock
-maintainer; an option may be appropriate.
-.PP
-Note that this section is only relevant when you are using the "direct
-ISA" method of accessing the Hardware Clock.
-ACPI provides a standard way to access century values, when they
-are supported by the hardware.
-.
-.SH DATE-TIME CONFIGURATION
-.in +4
-.SS Keeping Time without External Synchronization
-.in
-.PP
-This discussion is based on the following conditions:
-.IP \(bu 2
-Nothing is running that alters the date-time clocks, such as NTP daemon or a cron job."
-.IP \(bu 2
-The system timezone is configured for the correct local time. See below, under
-.BR "POSIX vs 'RIGHT'" .
-.IP \(bu 2
-Early during startup the following are called, in this order:
-.br
-.BI \%adjtimex\ \-\-tick \ value\ \-\-frequency \ value
-.br
-.B \%hwclock\ \-\-hctosys
-.IP \(bu 2
-During shutdown the following is called:
-.br
-.B \%hwclock\ \-\-systohc
-.PP
-.in +4
-.BR * " Systems without " adjtimex " may use " ntptime .
-.in
-.PP
-Whether maintaining precision time with NTP daemon
-or not, it makes sense to configure the system to keep reasonably good
-date-time on its own.
-.PP
-The first step in making that happen is having a clear understanding of
-the big picture. There are two completely separate hardware devices
-running at their own speed and drifting away from the 'correct' time at
-their own rates. The methods and software for drift correction are
-different for each of them. However, most systems are configured to
-exchange values between these two clocks at startup and shutdown. Now
-the individual device's time keeping errors are transferred back and
-forth between each other. Attempt to configure drift correction for only
-one of them, and the other's drift will be overlaid upon it.
-.PP
-This problem can be avoided when configuring drift correction for the
-System Clock by simply not shutting down the machine. This, plus the
-fact that all of
-.BR \%hwclock 's
-precision (including calculating drift factors) depends upon the System
-Clock's rate being correct, means that configuration of the System Clock
-should be done first.
-.PP
-The System Clock drift is corrected with the
-.BR \%adjtimex "(8) command's " \-\-tick " and " \%\-\-frequency
-options. These two work together: tick is the coarse adjustment and
-frequency is the fine adjustment. (For systems that do not have an
-.BR \%adjtimex " package,"
-.BI \%ntptime\ \-f\ ppm
-may be used instead.)
-.PP
-Some Linux distributions attempt to automatically calculate the System
-Clock drift with
-.BR \%adjtimex 's
-compare operation. Trying to correct one
-drifting clock by using another drifting clock as a reference is akin to
-a dog trying to catch its own tail. Success may happen eventually, but
-great effort and frustration will likely precede it. This automation may
-yield an improvement over no configuration, but expecting optimum
-results would be in error. A better choice for manual configuration
-would be
-.BR \%adjtimex 's " \-\-log " options.
-.PP
-It may be more effective to simply track the System Clock drift with
-.BR \%sntp ", or " \%date\ \-Ins
-and a precision timepiece, and then calculate the correction manually.
-.PP
-After setting the tick and frequency values, continue to test and refine the
-adjustments until the System Clock keeps good time. See
-.BR \%adjtimex (2)
-for more information and the example demonstrating manual drift
-calculations.
-.PP
-Once the System Clock is ticking smoothly, move on to the Hardware Clock.
-.PP
-As a rule, cold drift will work best for most use cases. This should be
-true even for 24/7 machines whose normal downtime consists of a reboot.
-In that case the drift factor value makes little difference. But on the
-rare occasion that the machine is shut down for an extended period, then
-cold drift should yield better results.
-.PP
-.B Steps to calculate cold drift:
-.IP 1 2
-.B "Ensure that NTP daemon will not be launched at startup."
-.IP 2 2
-.RI The " System Clock " "time must be correct at shutdown!"
-.IP 3 2
-Shut down the system.
-.IP 4 2
-Let an extended period pass without changing the Hardware Clock.
-.IP 5 2
-Start the system.
-.IP 6 2
-.RB "Immediately use " hwclock " to set the correct time, adding the"
-.BR \%\-\-update\-drift " option."
-.PP
-Note: if step 6 uses
-.BR \%\-\-systohc ,
-then the System Clock must be set correctly (step 6a) just before doing so.
-.PP
-.RB "Having " hwclock
-calculate the drift factor is a good starting point, but for optimal
-results it will likely need to be adjusted by directly editing the
-.I @ADJTIME_PATH@
-file. Continue to test and refine the drift factor until the Hardware
-Clock is corrected properly at startup. To check this, first make sure
-that the System Time is correct before shutdown and then use
-.BR \%sntp ", or " \%date\ \-Ins
-and a precision timepiece, immediately after startup.
-.SS LOCAL vs UTC
-Keeping the Hardware Clock in a local timescale causes inconsistent
-daylight saving time results:
-.IP \(bu 2
-If Linux is running during a daylight saving time change, the time
-written to the Hardware Clock will be adjusted for the change.
-.IP \(bu 2
-If Linux is NOT running during a daylight saving time change, the time
-read from the Hardware Clock will NOT be adjusted for the change.
-.PP
-The Hardware Clock on an ISA compatible system keeps only a date and time,
-it has no concept of timezone nor daylight saving. Therefore, when
-.B hwclock
-is told that it is in local time, it assumes it is in the 'correct'
-local time and makes no adjustments to the time read from it.
-.PP
-Linux handles daylight saving time changes transparently only when the
-Hardware Clock is kept in the UTC timescale. Doing so is made easy for
-system administrators as
-.B \%hwclock
-uses local time for its output and as the argument to the
-.BR \%\-\-date " option."
-.PP
-POSIX systems, like Linux, are designed to have the System Clock operate
-in the UTC timescale. The Hardware Clock's purpose is to initialize the
-System Clock, so also keeping it in UTC makes sense.
-.PP
-Linux does, however, attempt to accommodate the Hardware Clock being in
-the local timescale. This is primarily for dual-booting with older
-versions of MS Windows. From Windows 7 on, the RealTimeIsUniversal
-registry key is supposed to be working properly so that its Hardware
-Clock can be kept in UTC.
-.
-.SS POSIX vs 'RIGHT'
-A discussion on date-time configuration would be incomplete without
-addressing timezones, this is mostly well covered by
-.BR tzset (3).
-One area that seems to have no documentation is the 'right'
-directory of the Time Zone Database, sometimes called tz or zoneinfo.
-.PP
-There are two separate databases in the zoneinfo system, posix
-and 'right'. 'Right' (now named zoneinfo\-leaps) includes leap seconds and posix
-does not. To use the 'right' database the System Clock must be set to
-\%(UTC\ +\ leap seconds), which is equivalent to \%(TAI\ \-\ 10). This
-allows calculating the
-exact number of seconds between two dates that cross a leap second
-epoch. The System Clock is then converted to the correct civil time,
-including UTC, by using the 'right' timezone files which subtract the
-leap seconds. Note: this configuration is considered experimental and is
-known to have issues.
-.PP
-To configure a system to use a particular database all of the files
-located in its directory must be copied to the root of
-.IR \%/usr/share/zoneinfo .
-Files are never used directly from the posix or 'right' subdirectories, e.g.,
-.RI \%TZ=' right/Europe/Dublin '.
-This habit was becoming so common that the upstream zoneinfo project
-restructured the system's file tree by moving the posix and 'right'
-subdirectories out of the zoneinfo directory and into sibling directories:
-.PP
-.in +2
-.I /usr/share/zoneinfo
-.br
-.I /usr/share/zoneinfo\-posix
-.br
-.I /usr/share/zoneinfo\-leaps
-.PP
-Unfortunately, some Linux distributions are changing it back to the old
-tree structure in their packages. So the problem of system
-administrators reaching into the 'right' subdirectory persists. This
-causes the system timezone to be configured to include leap seconds
-while the zoneinfo database is still configured to exclude them. Then
-when an application such as a World Clock needs the South_Pole timezone
-file; or an email MTA, or
-.B hwclock
-needs the UTC timezone file; they fetch it from the root of
-.I \%/usr/share/zoneinfo
-, because that is what they are supposed to do. Those files exclude leap
-seconds, but the System Clock now includes them, causing an incorrect
-time conversion.
-.PP
-Attempting to mix and match files from these separate databases will not
-work, because they each require the System Clock to use a different
-timescale. The zoneinfo database must be configured to use either posix
-or 'right', as described above, or by assigning a database path to the
-.SB TZDIR
-environment variable.
-.SH EXIT STATUS
-One of the following exit values will be returned:
-.TP
-.BR EXIT_SUCCESS " ('0' on POSIX systems)"
-Successful program execution.
-.TP
-.BR EXIT_FAILURE " ('1' on POSIX systems)"
-The operation failed or the command syntax was not valid.
-.SH ENVIRONMENT
-.TP
-.B TZ
-If this variable is set its value takes precedence over the system
-configured timezone.
-.TP
-.B TZDIR
-If this variable is set its value takes precedence over the system
-configured timezone database directory path.
-.SH FILES
-.TP
-.I @ADJTIME_PATH@
-The configuration and state file for hwclock.
-.TP
-.I /etc/localtime
-The system timezone file.
-.TP
-.I /usr/share/zoneinfo/
-The system timezone database directory.
-.PP
-Device files
-.B hwclock
-may try for Hardware Clock access:
-.br
-.I /dev/rtc0
-.br
-.I /dev/rtc
-.br
-.I /dev/misc/rtc
-.br
-.I /dev/efirtc
-.br
-.I /dev/misc/efirtc
-.SH "SEE ALSO"
-.BR date (1),
-.BR adjtimex (8),
-.BR gettimeofday (2),
-.BR settimeofday (2),
-.BR crontab (1p),
-.BR tzset (3)
-.
-.SH AUTHORS
-Written by Bryan Henderson, September 1996 (bryanh@giraffe-data.com),
-based on work done on the
-.BR \%clock (8)
-program by Charles Hedrick, Rob Hooft, and Harald Koenig.
-See the source code for complete history and credits.
-.
-.SH AVAILABILITY
-The hwclock command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 2008 Hayden A. James (hayden.james@gmail.com)
-.\" May be distributed under the GNU General Public License
-.TH IPCMK "1" "July 2014" "util-linux" "User Commands"
-.SH NAME
-ipcmk \- make various IPC resources
-.SH SYNOPSIS
-.B ipcmk
-[options]
-.SH DESCRIPTION
-.B ipcmk
-allows you to create System V inter-process communication (IPC) objects:
-shared memory segments, message queues,
-and semaphore arrays.
-.SH OPTIONS
-.TP
-Resources can be specified with these options:
-.TP
-.BR \-M , " \-\-shmem " \fIsize
-Create a shared memory segment of
-.I size
-bytes.
-The \fIsize\fR argument may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, etc. (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, etc.
-.TP
-.BR \-Q , " \-\-queue"
-Create a message queue.
-.TP
-.BR \-S , " \-\-semaphore " \fInumber
-Create a semaphore array with
-.I number
-of elements.
-.PP
-Other options are:
-.TP
-.BR \-p , " \-\-mode " \fImode
-Access permissions for the resource. Default is 0644.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH AUTHORS
-.MT hayden.james@gmail.com
-Hayden A. James
-.ME
-.SH SEE ALSO
-.BR ipcrm (1),
-.BR ipcs (1),
-.BR sysvipc (7)
-.SH AVAILABILITY
-The ipcmk command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 2002 Andre C. Mazzone (linuxdev@karagee.com)
-.\" May be distributed under the GNU General Public License
-.TH IPCRM "1" "July 2014" "util-linux" "User Commands"
-.SH NAME
-ipcrm \- remove certain IPC resources
-.SH SYNOPSIS
-.B ipcrm
-[options]
-.sp
-.B ipcrm
-.RB { shm | msg | sem }
-.IR id ...
-.SH DESCRIPTION
-.B ipcrm
-removes System V inter-process communication (IPC) objects
-and associated data structures from the system.
-In order to delete such objects, you must be superuser, or
-the creator or owner of the object.
-.PP
-System V IPC objects are of three types: shared memory,
-message queues, and semaphores.
-Deletion of a message queue or semaphore object is immediate
-(regardless of whether any process still holds an IPC
-identifier for the object).
-A shared memory object is only removed
-after all currently attached processes have detached
-.RB ( shmdt (2))
-the object from their virtual address space.
-.PP
-Two syntax styles are supported. The old Linux historical syntax specifies
-a three-letter keyword indicating which class of object is to be deleted,
-followed by one or more IPC identifiers for objects of this type.
-.PP
-The SUS-compliant syntax allows the specification of
-zero or more objects of all three types in a single command line,
-with objects specified either by key or by identifier (see below).
-Both keys and identifiers may be specified in decimal, hexadecimal
-(specified with an initial '0x' or '0X'), or octal (specified with
-an initial '0').
-.PP
-The details of the removes are described in
-.BR shmctl (2),
-.BR msgctl (2),
-and
-.BR semctl (2).
-The identifiers and keys can be found by using
-.BR ipcs (1).
-.SH OPTIONS
-.TP
-\fB\-a\fR, \fB\-\-all\fR [\fBshm\fR] [\fBmsg\fR] [\fBsem\fR]
-Remove all resources. When an option argument is provided, the removal is
-performed only for the specified resource types. \fIWarning!\fR Do not use
-.B \-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.
-.TP
-.BR \-M , " \-\-shmem\-key " \fIshmkey
-Remove the shared memory segment created with
-.I shmkey
-after the last detach is performed.
-.TP
-.BR \-m , " \-\-shmem\-id " \fIshmid
-Remove the shared memory segment identified by
-.I shmid
-after the last detach is performed.
-.TP
-.BR \-Q , " \-\-queue\-key " \fImsgkey
-Remove the message queue created with
-.IR msgkey .
-.TP
-.BR \-q , " \-\-queue\-id " \fImsgid
-Remove the message queue identified by
-.IR msgid .
-.TP
-.BR \-S , " \-\-semaphore\-key " \fIsemkey
-Remove the semaphore created with
-.IR semkey .
-.TP
-.BR \-s , " \-\-semaphore\-id " \fIsemid
-Remove the semaphore identified by
-.IR semid .
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH NOTES
-In its first Linux implementation, \fBipcrm\fR used the deprecated syntax
-shown in the second line of the
-.BR SYNOPSIS .
-Functionality present in other *nix implementations of \fBipcrm\fR has since
-been added, namely the ability to delete resources by key (not just
-identifier), and to respect the same command-line syntax. For backward
-compatibility the previous syntax is still supported.
-.\" .SH AUTHORS
-.\" Andre C. Mazzone (linuxdev@karagee.com)
-.\" .br
-.\" Krishna Balasubramanian (balasub@cis.ohio-state.edu)
-.SH SEE ALSO
-.nh
-.BR ipcmk (1),
-.BR ipcs (1),
-.BR msgctl (2),
-.BR msgget (2),
-.BR semctl (2),
-.BR semget (2),
-.BR shmctl (2),
-.BR shmdt (2),
-.BR shmget (2),
-.BR ftok (3),
-.BR sysvipc (7)
-.SH AVAILABILITY
-The ipcrm command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 1993 Rickard E. Faith (faith@cs.unc.edu)
-.\" May be distributed under the GNU General Public License
-.TH IPCS "1" "July 2014" "util-linux" "User Commands"
-.SH NAME
-ipcs \- show information on IPC facilities
-.SH SYNOPSIS
-.B ipcs
-[options]
-.SH DESCRIPTION
-.B ipcs
-shows information on System V inter-process communication facilities.
-By default it shows information about all three resources:
-shared memory segments, message queues, and semaphore arrays.
-.SH OPTIONS
-.TP
-\fB\-i\fR, \fB\-\-id\fR \fIid\fR
-Show full details on just the one resource element identified by
-.IR id .
-This option needs to be combined with one of the three resource options:
-.BR \-m ,
-.BR \-q " or"
-.BR \-s .
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.SS "Resource options"
-.TP
-\fB\-m\fR, \fB\-\-shmems\fR
-Write information about active shared memory segments.
-.TP
-\fB\-q\fR, \fB\-\-queues\fR
-Write information about active message queues.
-.TP
-\fB\-s\fR, \fB\-\-semaphores\fR
-Write information about active semaphore sets.
-.TP
-\fB\-a\fR, \fB\-\-all\fR
-Write information about all three resources (default).
-.SS "Output formats"
-Of these options only one takes effect: the last one specified.
-.TP
-\fB\-c\fR, \fB\-\-creator\fR
-Show creator and owner.
-.TP
-\fB\-l\fR, \fB\-\-limits\fR
-Show resource limits.
-.TP
-\fB\-p\fR, \fB\-\-pid\fR
-Show PIDs of creator and last operator.
-.TP
-\fB\-t\fR, \fB\-\-time\fR
-Write time information. The time of the last control operation that changed
-the access permissions for all facilities, the time of the last
-.BR msgsnd (2)
-and
-.BR msgrcv (2)
-operations on message queues, the time of the last
-.BR shmat (2)
-and
-.BR shmdt (2)
-operations on shared memory, and the time of the last
-.BR semop (2)
-operation on semaphores.
-.TP
-\fB\-u\fR, \fB\-\-summary\fR
-Show status summary.
-.SS "Representation"
-These affect only the \fB\-l\fR (\fB\-\-limits\fR) option.
-.TP
-\fB\-b\fR, \fB\-\-bytes\fR
-Print sizes in bytes.
-.TP
-.B \-\-human
-Print sizes in human-readable format.
-.SH CONFORMING TO
-The Linux ipcs utility is not fully compatible to the POSIX ipcs utility.
-The Linux version does not support the POSIX
-.BR \-a ,
-.B \-b
-and
-.B \-o
-options, but does support the
-.B \-l
-and
-.B \-u
-options not defined by POSIX. A portable application shall not use the
-.BR \-a ,
-.BR \-b ,
-.BR \-o ,
-.BR \-l ,
-and
-.B \-u
-options.
-.SH NOTES
-The current implementation of
-.B ipcs
-obtains information about available IPC resources by parsing the files in
-.IR /proc/sysvipc .
-Before util-linux version v2.23, an alternate mechanism was used: the
-.B IPC_STAT
-command of
-.BR msgctl (2),
-.BR semctl (2),
-and
-.BR shmctl (2).
-This mechanism is also used in later util-linux versions in the case where
-.I /proc
-is unavailable.
-A limitation of the
-.B IPC_STAT
-mechanism is that it can only be used to retrieve information about
-IPC resources for which the user has read permission.
-.SH AUTHORS
-.UR balasub@cis.ohio-state.edu
-Krishna Balasubramanian
-.UE
-.SH SEE ALSO
-.BR ipcmk (1),
-.BR ipcrm (1),
-.BR msgrcv (2),
-.BR msgsnd (2),
-.BR semget (2),
-.BR semop (2),
-.BR shmat (2),
-.BR shmdt (2),
-.BR shmget (2),
-.BR sysvipc (7)
-.SH AVAILABILITY
-The ipcs command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH IRQTOP "1" "February 2020" "util-linux" "User Commands"
-.SH NAME
-irqtop \- utility to display kernel interrupt information
-.SH SYNOPSIS
-.B irqtop
-[options]
-.SH DESCRIPTION
-Display kernel interrupt counter information in
-.BR top (1)
-style view.
-.PP
-The default output is subject to change. So whenever possible, you should
-avoid using default outputs in your scripts. Always explicitly define
-expected columns by using
-.BR \-\-output .
-.SH OPTIONS
-.TP
-.BR \-o , " \-\-output " \fIlist\fP
-Specify which output columns to print. Use
-.B \-\-help
-to get a list of all supported columns. The default list of columns may be
-extended if list is specified in the format
-.IR +list .
-.TP
-.BR \-d , " \-\-delay " \fIseconds\fP
-Update interrupt output every
-.I seconds
-intervals.
-.TP
-.BR \-s , " \-\-sort " \fIcolumn\fP
-Specify sort criteria by column name. See
-.B \-\-help
-output to get column names. The sort criteria may be changes in interactive
-mode.
-.TP
-.BR \-S , " \-\-softirq "
-Show softirqs information.
-.TP
-.BR \-V ", " \-\-version
-Display version information and exit.
-.TP
-.BR \-h ,\ \-\-help
-Display help text and exit.
-.SH INTERACTIVE MODE KEY COMMANDS
-.PD 0
-.TP
-.B i
-sort by short irq name or number field
-.TP
-.B t
-sort by total count of interrupts (the default)
-.TP
-.B d
-sort by delta count of interrupts
-.TP
-.B n
-sort by long descriptive name field
-.TP
-.B q Q
-stop updates and exit program
-.PD 1
-.SH AUTHORS
-.MT pizhenwei@\:bytedance.com
-Zhenwei Pi
-.ME
-.br
-.MT kerolasa@\:iki.fi
-Sami Kerola
-.ME
-.br
-.MT kzak@\:redhat.com
-Karel Zak
-.ME
-.SH AVAILABILITY
-The irqtop command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 2008 Tilman Schmidt (tilman@imap.cc)
-.\" May be distributed under the GNU General Public License version 2 or later
-.TH LDATTACH 8 "July 2014" "util-linux" "System Administration"
-.SH NAME
-ldattach \- attach a line discipline to a serial line
-.SH SYNOPSIS
-.B ldattach
-.RB [ \-1278denoVh ]
-.RB [ \-i
-.IR iflag ]
-.RB [ \-s
-.IR speed ]
-.I ldisc device
-.SH DESCRIPTION
-The
-.B ldattach
-daemon opens the specified
-.I device
-file
-(which should refer to a serial device)
-and attaches the line discipline
-.I ldisc
-to it for processing of the sent and/or received data.
-It then goes into the background keeping the device open so that the
-line discipline stays loaded.
-.sp
-The line discipline
-.I ldisc
-may be specified either by name
-or by number.
-.sp
-In order to detach the line discipline,
-.BR kill (1)
-the
-.B ldattach
-process.
-.sp
-With no arguments,
-.B ldattach
-prints usage information.
-.SH LINE DISCIPLINES
-Depending on the kernel release, the following line disciplines are supported:
-.TP
-.BR TTY ( 0 )
-The default line discipline,
-providing transparent operation (raw mode)
-as well as the habitual terminal line editing capabilities (cooked mode).
-.TP
-.BR SLIP ( 1 )
-Serial Line IP (SLIP) protocol processor
-for transmitting TCP/IP packets over serial lines.
-.TP
-.BR MOUSE ( 2 )
-Device driver for RS232 connected pointing devices (serial mice).
-.TP
-.BR PPP ( 3 )
-Point to Point Protocol (PPP) processor
-for transmitting network packets over serial lines.
-.TP
-.BR STRIP ( 4 )
-.TP
-.BR AX25 ( 5 )
-.TP
-.BR X25 ( 6 )
-Line driver for transmitting X.25 packets over asynchronous serial lines.
-.TP
-.BR 6PACK ( 7 )
-.TP
-.BR R3964 ( 9 )
-Driver for Simatic R3964 module.
-.TP
-.BR IRDA ( 11 )
-Linux IrDa (infrared data transmission) driver -
-see http://irda.sourceforge.net/
-.TP
-.BR HDLC ( 13 )
-Synchronous HDLC driver.
-.TP
-.BR SYNC_PPP ( 14 )
-Synchronous PPP driver.
-.TP
-.BR HCI ( 15 )
-Bluetooth HCI UART driver.
-.TP
-.BR GIGASET_M101 ( 16 )
-Driver for Siemens Gigaset M101 serial DECT adapter.
-.TP
-.BR PPS ( 18 )
-Driver for serial line Pulse Per Second (PPS) source.
-.TP
-.BR GSM0710 ( 21 )
-Driver for GSM 07.10 multiplexing protocol modem (CMUX).
-.SH OPTIONS
-.TP
-.BR \-1 , " \-\-onestopbit"
-Set the number of stop bits of the serial line to one.
-.TP
-.BR \-2 , " \-\-twostopbits"
-Set the number of stop bits of the serial line to two.
-.TP
-.BR \-7 , " \-\-sevenbits"
-Set the character size of the serial line to 7 bits.
-.TP
-.BR \-8 , " \-\-eightbits"
-Set the character size of the serial line to 8 bits.
-.TP
-.BR \-d , " \-\-debug"
-Keep
-.B ldattach
-in the foreground so that it can be interrupted or debugged,
-and to print verbose messages about its progress to standard error output.
-.TP
-.BR \-e , " \-\-evenparity"
-Set the parity of the serial line to even.
-.TP
-.BR \-i , " \-\-iflag " [ \- ] \fIvalue\fR...
-Set the specified bits in the c_iflag word of the serial line.
-The given \fIvalue\fP may be a number or a symbolic name.
-If \fIvalue\fP is prefixed by a minus sign, the specified bits are cleared
-instead. Several comma-separated values may be given in order to
-set and clear multiple bits.
-.TP
-.BR \-n , " \-\-noparity"
-Set the parity of the serial line to none.
-.TP
-.BR \-o , " \-\-oddparity"
-Set the parity of the serial line to odd.
-.TP
-.BR \-s , " \-\-speed " \fIvalue
-Set the speed (the baud rate) of the serial line to the specified \fIvalue\fR.
-.TP
-.BR \-c , " \-\-intro\-command " \fIstring
-Define an intro command that is sent through the serial line before the invocation
-of ldattach. E.g. in conjunction with line discipline GSM0710, the command
-\'AT+CMUX=0\\r\' is commonly suitable to switch the modem into the CMUX mode.
-.TP
-.BR \-p , " \-\-pause " \fIvalue
-Sleep for \fIvalue\fR seconds before the invocation of ldattach. Default is one second.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH AUTHORS
-.nf
-Tilman Schmidt (tilman@imap.cc)
-.fi
-.SH SEE ALSO
-.BR inputattach (1),
-.BR ttys (4)
-.SH AVAILABILITY
-The ldattach command is part of the util-linux package
-and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH LOSETUP 8 "November 2015" "util-linux" "System Administration"
-.SH NAME
-losetup \- set up and control loop devices
-.SH SYNOPSIS
-.ad l
-Get info:
-.sp
-.in +5
-.B losetup
-[\fIloopdev\fP]
-.sp
-.B losetup \-l
-.RB [ \-a ]
-.sp
-.B losetup \-j
-.I file
-.RB [ \-o
-.IR offset ]
-.sp
-.in -5
-Detach a loop device:
-.sp
-.in +5
-.B "losetup \-d"
-.IR loopdev ...
-.sp
-.in -5
-Detach all associated loop devices:
-.sp
-.in +5
-.B "losetup \-D"
-.sp
-.in -5
-Set up a loop device:
-.sp
-.in +5
-.B losetup
-.RB [ \-o
-.IR offset ]
-.RB [ \-\-sizelimit
-.IR size ]
-.RB [ \-\-sector\-size
-.IR size ]
-.in +8
-.RB [ \-Pr ]
-.RB [ \-\-show ] " \-f" | \fIloopdev\fP
-.I file
-.sp
-.in -13
-Resize a loop device:
-.sp
-.in +5
-.B "losetup \-c"
-.I loopdev
-.in -5
-.ad b
-.SH DESCRIPTION
-.B losetup
-is used to associate loop devices with regular files or block devices,
-to detach loop devices, and to query the status of a loop device. If only the
-\fIloopdev\fP argument is given, the status of the corresponding loop
-device is shown. If no option is given, all loop devices are shown.
-.sp
-Note that the old output format (i.e., \fBlosetup \-a\fR) with comma-delimited
-strings is deprecated in favour of the \fB\-\-list\fR output format.
-.sp
-It's possible to create more independent loop devices for the same backing
-file.
-.B This setup may be dangerous, can cause data loss, corruption and overwrites.
-Use \fB\-\-nooverlap\fR with \fB\-\-find\fR during setup to avoid this problem.
-.sp
-The loop device setup is not an atomic operation when used with \fB\-\-find\fP, and
-.B losetup
-does not protect this operation by any lock. The number of attempts is
-internally restricted to a maximum of 16. It is recommended to use for example
-.BR flock (1)
-to avoid a collision in heavily parallel use cases.
-
-.SH OPTIONS
-The \fIsize\fR and \fIoffset\fR
-arguments 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.
-
-.TP
-.BR \-a , " \-\-all"
-Show the status of all loop devices. Note that not all information is accessible
-for non-root users. See also \fB\-\-list\fR. The old output format (as printed
-without \fB\-\-list)\fR is deprecated.
-.TP
-.BR \-d , " \-\-detach " \fIloopdev\fR...
-Detach the file or device associated with the specified loop device(s). Note
-that since Linux v3.7 kernel uses "lazy device destruction". The detach
-operation does not return EBUSY error anymore if device is actively used by
-system, but it is marked by autoclear flag and destroyed later.
-.TP
-.BR \-D , " \-\-detach\-all"
-Detach all associated loop devices.
-.TP
-.BR \-f , " \-\-find " "\fR[\fIfile\fR]"
-Find the first unused loop device. If a \fIfile\fR argument is present, use
-the found device as loop device. Otherwise, just print its name.
-.IP "\fB\-\-show\fP"
-Display the name of the assigned loop device if the \fB\-f\fP option and a
-\fIfile\fP argument are present.
-.TP
-.BR \-L , " \-\-nooverlap"
-Check for conflicts between loop devices to avoid situation when the same
-backing file is shared between more loop devices. If the file is already used
-by another device then re-use the device rather than a new one. The option
-makes sense only with \fB\-\-find\fP.
-.TP
-.BR \-j , " \-\-associated " \fIfile\fR " \fR[\fB\-o \fIoffset\fR]"
-Show the status of all loop devices associated with the given \fIfile\fR.
-.TP
-.BR \-o , " \-\-offset " \fIoffset
-The data start is moved \fIoffset\fP bytes into the specified file or device. The \fIoffset\fP
-may be followed by the multiplicative suffixes; see above.
-.IP "\fB\-\-sizelimit \fIsize\fP"
-The data end is set to no more than \fIsize\fP bytes after the data start. The \fIsize\fP
-may be followed by the multiplicative suffixes; see above.
-.TP
-.BR \-b , " \-\-sector-size " \fIsize
-Set the logical sector size of the loop device in bytes (since Linux 4.14). The
-option may be used when create a new loop device as well as stand-alone command
-to modify sector size of the already existing loop device.
-.TP
-.BR \-c , " \-\-set\-capacity " \fIloopdev
-Force the loop driver to reread the size of the file associated with the
-specified loop device.
-.TP
-.BR \-P , " \-\-partscan"
-Force the kernel to scan the partition table on a newly created loop device. Note that the
-partition table parsing depends on sector sizes. The default is sector size is 512 bytes,
-otherwise you need to use the option \fB\-\-sector\-size\fR together with \fB\-\-partscan\fR.
-.TP
-.BR \-r , " \-\-read\-only"
-Set up a read-only loop device.
-.TP
-.BR \-\-direct\-io [ =on | off ]
-Enable or disable direct I/O for the backing file. The optional argument
-can be either \fBon\fR or \fBoff\fR. If the argument is omitted, it defaults
-to \fBoff\fR.
-.TP
-.BR \-v , " \-\-verbose"
-Verbose mode.
-.TP
-.BR \-l , " \-\-list"
-If a loop device or the \fB\-a\fR option is specified, print the default columns
-for either the specified loop device or all loop devices; the default is to
-print info about all devices. See also \fB\-\-output\fP, \fB\-\-noheadings\fP,
-\fB\-\-raw\fP, and \fB\-\-json\fP.
-.TP
-.BR \-O , " \-\-output " \fIcolumn\fR[,\fIcolumn\fR]...
-Specify the columns that are to be printed for the \fB\-\-list\fP output.
-Use \fB\-\-help\fR to get a list of all supported columns.
-.TP
-.B \-\-output\-all
-Output all available columns.
-.TP
-.BR \-n , " \-\-noheadings"
-Don't print headings for \fB\-\-list\fP output format.
-.IP "\fB\-\-raw\fP"
-Use the raw \fB\-\-list\fP output format.
-.TP
-.BR \-J , " \-\-json"
-Use JSON format for \fB\-\-list\fP output.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-
-.SH ENCRYPTION
-.B Cryptoloop is no longer supported in favor of dm-crypt.
-.B For more details see cryptsetup(8).
-
-.SH EXIT STATUS
-.B losetup
-returns 0 on success, nonzero on failure. When
-.B losetup
-displays the status of a loop device, it returns 1 if the device
-is not configured and 2 if an error occurred which prevented
-determining the status of the device.
-.SH NOTES
-Since version 2.37
-.B losetup
-uses LOOP_CONFIGURE ioctl to setup a new loop device by one ioctl call. The
-old versions use LOOP_SET_FD and LOOP_SET_STATUS64 ioctls to do the same.
-
-.SH ENVIRONMENT
-.IP LOOPDEV_DEBUG=all
-enables debug output.
-
-.SH FILES
-.TP
-.I /dev/loop[0..N]
-loop block devices
-.TP
-.I /dev/loop-control
-loop control device
-.SH EXAMPLE
-The following commands can be used as an example of using the loop device.
-.nf
-.IP
-# dd if=/dev/zero of=\(ti/file.img bs=1024k count=10
-# losetup \-\-find \-\-show \(ti/file.img
-/dev/loop0
-# mkfs \-t ext2 /dev/loop0
-# mount /dev/loop0 /mnt
- ...
-# umount /dev/loop0
-# losetup \-\-detach /dev/loop0
-.fi
-.SH AUTHORS
-Karel Zak <kzak@redhat.com>, based on the original version from
-Theodore Ts'o <tytso@athena.mit.edu>
-.SH AVAILABILITY
-The losetup command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH LSCPU 1 "March 2019" "util-linux" "User Commands"
-.SH NAME
-lscpu \- display information about the CPU architecture
-.SH SYNOPSIS
-.B lscpu
-[options]
-.SH DESCRIPTION
-.B lscpu
-gathers CPU architecture information from sysfs, /proc/cpuinfo and any
-applicable architecture-specific libraries (e.g.\& librtas on Powerpc). The
-command output can be optimized for parsing or for easy readability by humans.
-The information includes, for example, the number of CPUs, threads, cores,
-sockets, and Non-Uniform Memory Access (NUMA) nodes. There is also information
-about the CPU caches and cache sharing, family, model, bogoMIPS, byte order,
-and stepping.
-.sp
-The default output formatting on terminal is subject to change and maybe
-optimized for better readability. The output for non-terminals (e.g., pipes)
-is never affected by this optimization and it is always in "Field: data\\n"
-format. Use for example \fBlscpu | less\fP to see the default output without
-optimizations.
-.sp
-In virtualized environments, the CPU architecture information displayed
-reflects the configuration of the guest operating system which is
-typically different from the physical (host) system. On architectures that
-support retrieving physical topology information,
-.B lscpu
-also displays the number of physical sockets, chips, cores in the host system.
-.sp
-Options that result in an output table have a \fIlist\fP argument. Use this
-argument to customize the command output. Specify a comma-separated list of
-column labels to limit the output table to only the specified columns, arranged
-in the specified order. See \fBCOLUMNS\fP for a list of valid column labels. The
-column labels are not case sensitive.
-.sp
-Not all columns are supported on all architectures. If an unsupported column is
-specified, \fBlscpu\fP prints the column but does not provide any data for it.
-.sp
-The cache sizes are reported as summary from all CPUs. The versions before
-v2.34 reported per-core sizes, but this output was confusing due to complicated
-CPUs topology and the way how caches are shared between CPUs. For more details
-about caches see \fB\-\-cache\fP. Since version v2.37 \fBlscpu\fP follows
-cache IDs as provided by Linux kernel and it does not always start from zero.
-.SS COLUMNS
-Note that topology elements (core, socket, etc.) use a sequential unique ID
-starting from zero, but CPU logical numbers follow the kernel where there is
-no guarantee of sequential numbering.
-.TP
-.B CPU
-The logical CPU number of a CPU as used by the Linux kernel.
-.TP
-.B CORE
-The logical core number. A core can contain several CPUs.
-.TP
-.B SOCKET
-The logical socket number. A socket can contain several cores.
-.TP
-.B CLUSTER
-The logical cluster number. A cluster can contain several cores.
-.TP
-.B BOOK
-The logical book number. A book can contain several sockets.
-.TP
-.B DRAWER
-The logical drawer number. A drawer can contain several books.
-.TP
-.B NODE
-The logical NUMA node number. A node can contain several drawers.
-.TP
-.B CACHE
-Information about how caches are shared between CPUs.
-.TP
-.B ADDRESS
-The physical address of a CPU.
-.TP
-.B ONLINE
-Indicator that shows whether the Linux instance currently makes use of the CPU.
-.TP
-.B CONFIGURED
-Indicator that shows if the hypervisor has allocated the CPU to the virtual
-hardware on which the Linux instance runs. CPUs that are configured can be set
-online by the Linux instance.
-This column contains data only if your hardware system and hypervisor support
-dynamic CPU resource allocation.
-.TP
-.B 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:
-.RS
-.TP 12
-.B horizontal\fP
-The workload is spread across all available CPUs.
-.TP 12
-.B vertical
-The workload is concentrated on few CPUs.
-.P
-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.
-.RE
-.TP
-.B MAXMHZ
-Maximum megahertz value for the CPU. Useful when \fBlscpu\fP 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.
-.TP
-.B MINMHZ
-Minimum megahertz value for the CPU.
-.SH OPTIONS
-.TP
-.BR \-a , " \-\-all"
-Include lines for online and offline CPUs in the output (default for \fB\-e\fR).
-This option may only be specified together with option \fB\-e\fR or \fB\-p\fR.
-.TP
-.BR \-B , " \-\-bytes"
-Print the sizes in bytes rather than in a human-readable format.
-.TP
-.BR \-b , " \-\-online"
-Limit the output to online CPUs (default for \fB\-p\fR).
-This option may only be specified together with option \fB\-e\fR or \fB\-p\fR.
-.TP
-.BR \-C , " \-\-caches" [=\fIlist\fP]
-Display details about CPU caches. For details about available information see \fB\-\-help\fR
-output.
-
-If the \fIlist\fP argument is omitted, all columns for which data is available
-are included in the command output.
-
-When specifying the \fIlist\fP argument, the string of option, equal sign (=), and
-\fIlist\fP must not contain any blanks or other whitespace.
-Examples: '\fB\-C=NAME,ONE-SIZE\fP' or '\fB\-\-caches=NAME,ONE-SIZE\fP'.
-.TP
-.BR \-c , " \-\-offline"
-Limit the output to offline CPUs.
-This option may only be specified together with option \fB\-e\fR or \fB\-p\fR.
-.TP
-.BR \-e , " \-\-extended" [=\fIlist\fP]
-Display the CPU information in human-readable format.
-
-If the \fIlist\fP argument is omitted, all columns for which data is available
-are included in the command output.
-
-When specifying the \fIlist\fP argument, the string of option, equal sign (=), and
-\fIlist\fP must not contain any blanks or other whitespace.
-Examples: '\fB\-e=cpu,node\fP' or '\fB\-\-extended=cpu,node\fP'.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.TP
-.BR \-J , " \-\-json"
-Use JSON output format for the default summary or extended output (see \fB\-\-extended\fP).
-.TP
-.BR \-p , " \-\-parse" [=\fIlist\fP]
-Optimize the command output for easy parsing.
-
-If the \fIlist\fP argument is omitted, the command output is compatible with earlier
-versions of \fBlscpu\fP. In this compatible format, two commas are used to separate
-CPU cache columns. If no CPU caches are identified the cache column is omitted.
-.br
-If the \fIlist\fP argument is used, cache columns are separated with a colon (:).
-
-When specifying the \fIlist\fP argument, the string of option, equal sign (=), and
-\fIlist\fP must not contain any blanks or other whitespace.
-Examples: '\fB\-p=cpu,node\fP' or '\fB\-\-parse=cpu,node\fP'.
-.TP
-.BR \-s , " \-\-sysroot " \fIdirectory\fP
-Gather CPU data for a Linux instance other than the instance from which the
-\fBlscpu\fP command is issued. The specified \fIdirectory\fP is the system root
-of the Linux instance to be inspected.
-.TP
-.BR \-x , " \-\-hex"
-Use hexadecimal masks for CPU sets (for example "ff"). The default is to print
-the sets in list format (for example 0,1). Note that before version 2.30 the mask
-has been printed with 0x prefix.
-.TP
-.BR \-y , " \-\-physical"
-Display physical IDs for all columns with topology elements (core, socket, etc.).
-Other than logical IDs, which are assigned by \fBlscpu\fP, 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 \fBlscpu\fP prints
-the dash (-) character.
-
-The CPU logical numbers are not affected by this option.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.B \-\-output\-all
-Output all available columns. This option must be combined with either
-.BR \-\-extended ", " \-\-parse " or " \-\-caches .
-.SH BUGS
-The basic overview of CPU family, model, etc. is always based on the first
-CPU only.
-
-Sometimes in Xen Dom0 the kernel reports wrong data.
-
-On virtual hardware the number of cores per socket, etc. can be wrong.
-.SH AUTHORS
-.nf
-Cai Qian <qcai@redhat.com>
-Karel Zak <kzak@redhat.com>
-Heiko Carstens <heiko.carstens@de.ibm.com>
-.fi
-.SH SEE ALSO
-.BR chcpu (8)
-.SH AVAILABILITY
-The lscpu command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright 2015 Ondrej Oprala(ooprala@redhat.com)
-.\" May be distributed under the GNU General Public License
-.TH LSIPC "1" "November 2015" "util-linux" "User Commands"
-.SH NAME
-lsipc \- show information on IPC facilities currently employed in the system
-.SH SYNOPSIS
-.B lsipc
-[options]
-.SH DESCRIPTION
-.B lsipc
-shows information on the System V inter-process communication facilities
-for which the calling process has read access.
-.SH OPTIONS
-.TP
-\fB\-i\fR, \fB\-\-id\fR \fIid\fR
-Show full details on just the one resource element identified by
-.IR id .
-This option needs to be combined with one of the three resource options:
-.BR \-m ,
-.BR \-q " or"
-.BR \-s .
-It is possible to override the default output format for this option with the
-\fB\-\-list\fR, \fB\-\-raw\fR, \fB\-\-json\fR or \fB\-\-export\fR option.
-.TP
-\fB\-g\fR, \fB\-\-global\fR
-Show system-wide usage and limits of IPC resources.
-This option may be combined with one of the three resource options:
-.BR \-m ,
-.BR \-q " or"
-.BR \-s .
-The default is to show information about all resources.
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.SS "Resource options"
-.TP
-\fB\-m\fR, \fB\-\-shmems\fR
-Write information about active shared memory segments.
-.TP
-\fB\-q\fR, \fB\-\-queues\fR
-Write information about active message queues.
-.TP
-\fB\-s\fR, \fB\-\-semaphores\fR
-Write information about active semaphore sets.
-.SS "Output formatting"
-.TP
-\fB\-c\fR, \fB\-\-creator\fR
-Show creator and owner.
-.TP
-\fB\-e\fR, \fB\-\-export\fR
-Produce output in the form of key="value" pairs. All potentially unsafe value
-characters are hex-escaped (\\x<code>). The key (variable name) will be
-modified to contain only characters allowed for a shell variable identifiers,
-for example, USE_PCT instead of USE%.
-.TP
-\fB\-J\fR, \fB\-\-json\fR
-Use the JSON output format.
-.TP
-\fB\-l\fR, \fB\-\-list\fR
-Use the list output format. This is the default, except when \fB\-\-id\fR
-is used.
-.TP
-\fB\-n\fR, \fB\-\-newline\fR
-Display each piece of information on a separate line.
-.TP
-\fB\-\-noheadings\fR
-Do not print a header line.
-.TP
-\fB\-\-notruncate\fR
-Don't truncate output.
-.TP
-\fB\-o\fR, \fB\-\-output \fIlist\fP
-Specify which output columns to print. Use
-.B \-\-help
-to get a list of all supported columns.
-.TP
-\fB\-b\fR, \fB\-\-bytes\fR
-Print size in bytes rather than in human readable format.
-.TP
-\fB\-r\fR, \fB\-\-raw\fR
-Raw output (no columnation).
-.TP
-\fB\-t\fR, \fB\-\-time\fR
-Write time information. The time of the last control operation that changed
-the access permissions for all facilities, the time of the last
-.BR msgsnd (2)
-and
-.BR msgrcv (2)
-operations on message queues, the time of the last
-.BR shmat (2)
-and
-.BR shmdt (2)
-operations on shared memory, and the time of the last
-.BR semop (2)
-operation on semaphores.
-.TP
-\fB\-\-time\-format\fR \fItype\fP
-Display dates in short, full or iso format. The default is short, this time
-format is designed to be space efficient and human readable.
-.TP
-\fB\-P\fR, \fB\-\-numeric\-perms\fR
-Print numeric permissions in PERMS column.
-
-.SH EXIT STATUS
-.TP
-0
-if OK,
-.TP
-1
-if incorrect arguments specified,
-.TP
-2
-if a serious error occurs.
-.SH HISTORY
-The \fBlsipc\fP utility is inspired by the \fBipcs\fP utility.
-.SH AUTHORS
-.MT ooprala@redhat.com
-Ondrej Oprala
-.ME
-.br
-.MT kzak@redhat.com
-Karel Zak
-.ME
-
-.SH SEE ALSO
-.BR ipcmk (1),
-.BR ipcrm (1),
-.BR msgrcv (2),
-.BR msgsnd (2),
-.BR semget (2),
-.BR semop (2),
-.BR shmat (2),
-.BR shmdt (2),
-.BR shmget (2),
-.BR sysvipc (7)
-.SH AVAILABILITY
-The lsipc command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH IRQTOP "1" "February 2020" "util-linux" "User Commands"
-.SH NAME
-lsirq \- utility to display kernel interrupt information
-.SH SYNOPSIS
-.B lsirq
-[options]
-.SH DESCRIPTION
-Display kernel interrupt counter information.
-.PP
-The default output is subject to change. So whenever possible, you should
-avoid using default outputs in your scripts. Always explicitly define
-expected columns by using
-.BR \-\-output .
-.SH OPTIONS
-.TP
-.BR \-n ", " \-\-noheadings
-Don't print headings.
-.TP
-.BR \-o , " \-\-output " \fIlist\fP
-Specify which output columns to print. Use
-.B \-\-help
-to get a list of all supported columns. The default list of columns may be
-extended if list is specified in the format
-.IR +list .
-.TP
-.BR \-s , " \-\-sort " \fIcolumn\fP
-Specify sort criteria by column name. See
-.B \-\-help
-output to get column names.
-.TP
-.BR \-J ", " \-\-json
-Use JSON output format.
-.TP
-.BR \-P ", " \-\-pairs
-Produce output in the form of key="value" pairs. All potentially unsafe characters
-are hex-escaped (\\x<code>).
-.TP
-.BR \-S , " \-\-softirq "
-Show softirqs information.
-.TP
-.BR \-V ", " \-\-version
-Display version information and exit.
-.TP
-.BR \-h ,\ \-\-help
-Display help text and exit.
-.SH AUTHORS
-.MT pizhenwei@\:bytedance.com
-Zhenwei Pi
-.ME
-.br
-.MT kerolasa@\:iki.fi
-Sami Kerola
-.ME
-.br
-.MT kzak@\:redhat.com
-Karel Zak
-.ME
-.SH AVAILABILITY
-The lsirq command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH LSMEM 1 "October 2016" "util-linux" "User Commands"
-.SH NAME
-lsmem \- list the ranges of available memory with their online status
-.SH SYNOPSIS
-.B lsmem
-[options]
-.SH DESCRIPTION
-The \fBlsmem\fP command lists the ranges of available memory with their online
-status. The listed memory blocks correspond to the memory block representation
-in sysfs. The command also shows the memory block size and the amount of memory
-in online and offline state.
-
-The default output compatible with original implementation from s390-tools, but
-it's strongly recommended to avoid using default outputs in your scripts.
-Always explicitly define expected columns by using the \fB\-\-output\fR option
-together with a columns list in environments where a stable output is required.
-
-The \fBlsmem\fP command lists a new memory range always when the current memory
-block distinguish from the previous block by some output column. This default
-behavior is possible to override by the \fB\-\-split\fR option (e.g., \fBlsmem
-\-\-split=ZONES\fR). The special word "none" may be used to ignore all
-differences between memory blocks and to create as large as possible continuous
-ranges. The opposite semantic is \fB\-\-all\fR to list individual memory
-blocks.
-
-Note that some output columns may provide inaccurate information if a split policy
-forces \fBlsmem\fP to ignore differences in some attributes. For example if you
-merge removable and non-removable memory blocks to the one range than all
-the range will be marked as non-removable on \fBlsmem\fP output.
-
-Not all columns are supported on all systems. If an unsupported column is
-specified, \fBlsmem\fP prints the column but does not provide any data for it.
-
-Use the \fB\-\-help\fR option to see the columns description.
-
-.SH OPTIONS
-.TP
-.BR \-a ", " \-\-all
-List each individual memory block, instead of combining memory blocks with
-similar attributes.
-.TP
-.BR \-b , " \-\-bytes"
-Print the SIZE column in bytes rather than in a human-readable format.
-.TP
-.BR \-h ", " \-\-help
-Display help text and exit.
-.TP
-.BR \-J , " \-\-json"
-Use JSON output format.
-.TP
-.BR \-n , " \-\-noheadings"
-Do not print a header line.
-.TP
-.BR \-o , " \-\-output " \fIlist\fP
-Specify which output columns to print. Use \fB\-\-help\fR
-to get a list of all supported columns.
-The default list of columns may be extended if \fIlist\fP is
-specified in the format \fB+\fIlist\fP (e.g., \fBlsmem \-o +NODE\fP).
-.TP
-.B \-\-output\-all
-Output all available columns.
-.TP
-.BR \-P , " \-\-pairs"
-Produce output in the form of key="value" pairs. All potentially unsafe value
-characters are hex-escaped (\\x<code>).
-.TP
-.BR \-r , " \-\-raw"
-Produce output in raw format. All potentially unsafe characters are hex-escaped
-(\\x<code>).
-.TP
-.BR \-S , " \-\-split " \fIlist\fP
-Specify which columns (attributes) use to split memory blocks to ranges. The
-supported columns are STATE, REMOVABLE, NODE and ZONES, or "none".
-The other columns are
-silently ignored. For more details see DESCRIPTION above.
-.TP
-.BR \-s , " \-\-sysroot " \fIdirectory\fP
-Gather memory data for a Linux instance other than the instance from which the
-\fBlsmem\fP command is issued. The specified \fIdirectory\fP is the system
-root of the Linux instance to be inspected.
-.TP
-.BR \-V ", " \-\-version
-Display version information and exit.
-.TP
-\fB\-\-summary\fR[=\fIwhen\fR]
-This option controls summary lines output. The optional argument \fIwhen\fP can be
-\fBnever\fR, \fBalways\fR or \fBonly\fR. If the \fIwhen\fR argument is
-omitted, it defaults to \fB"only"\fR. The summary output is suppressed for
-\fB\-\-raw\fR, \fB\-\-pairs\fR and \fB\-\-json\fR.
-.SH AUTHORS
-.B lsmem
-was originally written by Gerald Schaefer for s390-tools in Perl. The C version
-for util-linux was written by Clemens von Mann, Heiko Carstens and Karel Zak.
-.SH SEE ALSO
-.BR chmem (8)
-.SH AVAILABILITY
-The \fBlsmem\fP command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Man page for the lsns command.
-.\" Copyright 2015 Karel Zak <kzak@redhat.com>
-.\" May be distributed under the GNU General Public License
-
-.TH LSNS 8 "December 2015" "util-linux" "System Administration"
-.SH NAME
-lsns \- list namespaces
-.SH SYNOPSIS
-.B lsns
-[options]
-.RI [ namespace ]
-
-.SH DESCRIPTION
-.B lsns
-lists information about all the currently accessible namespaces or about the
-given \fInamespace\fP. The \fInamespace\fP identifier is an inode number.
-
-The default output is subject to change. So whenever possible, you should
-avoid using default outputs in your scripts. Always explicitly define expected
-columns by using the \fB\-\-output\fR option together with a columns list in
-environments where a stable output is required.
-
-The \fBNSFS\fP column, printed when \fBnet\fP is specified for the
-\fB\-\-type\fP option, is special; it uses multi-line cells. Use the option
-\fB\-\-nowrap\fR to switch to ","-separated single-line representation.
-
-Note that \fBlsns\fR reads information directly from the /proc filesystem and
-for non-root users it may return incomplete information. The current /proc
-filesystem may be unshared and affected by a PID namespace
-(see \fBunshare \-\-mount\-proc\fP for more details).
-.B lsns
-is not able to see persistent namespaces without processes where the namespace
-instance is held by a bind mount to /proc/\fIpid\fR/ns/\fItype\fR.
-
-.SH OPTIONS
-.TP
-.BR \-J , " \-\-json"
-Use JSON output format.
-.TP
-.BR \-l , " \-\-list"
-Use list output format.
-.TP
-.BR \-n , " \-\-noheadings"
-Do not print a header line.
-.TP
-.BR \-o , " \-\-output " \fIlist\fP
-Specify which output columns to print. Use \fB\-\-help\fR
-to get a list of all supported columns.
-
-The default list of columns may be extended if \fIlist\fP is
-specified in the format \fB+\fIlist\fP (e.g., \fBlsns \-o +PATH\fP).
-.TP
-.B \-\-output\-all
-Output all available columns.
-.TP
-.BR \-p , " \-\-task " \fIpid\fP
-Display only the namespaces held by the process with this \fIpid\fR.
-.TP
-.BR \-r , " \-\-raw"
-Use the raw output format.
-.TP
-.BR \-t , " \-\-type " \fItype\fP
-Display the specified \fItype\fP of namespaces only. The supported types are
-\fBmnt\fP, \fBnet\fP, \fBipc\fP, \fBuser\fP, \fBpid\fP, \fButs\fP,
-\fBcgroup\fP and \fBtime\fP. This option may be given more than once.
-.TP
-.BR \-u , " \-\-notruncate"
-Do not truncate text in columns.
-.TP
-.BR \-W , " \-\-nowrap"
-Do not use multi-line text in columns.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-
-.SH AUTHORS
-.nf
-Karel Zak <kzak@redhat.com>
-.fi
-
-.SH SEE ALSO
-.BR nsenter (1),
-.BR unshare (1),
-.BR clone (2),
-.BR namespaces (7)
-
-.SH AVAILABILITY
-The lsns command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright (c) 1996-2004 Andries Brouwer
-.\" Copyright (C) 2006-2012 Karel Zak <kzak@redhat.com>
-.\"
-.\" This page is somewhat derived from a page that was
-.\" (c) 1980, 1989, 1991 The Regents of the University of California
-.\" and had been heavily modified by Rik Faith and myself.
-.\" (Probably no BSD text remains.)
-.\" Fragments of text were written by Werner Almesberger, Remy Card,
-.\" Stephen Tweedie and Eric Youngdale.
-.\"
-.\" This is free documentation; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public License as
-.\" published by the Free Software Foundation; either version 2 of
-.\" the License, or (at your option) any later version.
-.\"
-.\" The GNU General Public License's references to "object code"
-.\" and "executables" are to be interpreted as the output of any
-.\" document formatting or typesetting system, including
-.\" intermediate and printed output.
-.\"
-.\" This manual is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-.\"
-.TH MOUNT 8 "August 2015" "util-linux" "System Administration"
-.SH NAME
-mount \- mount a filesystem
-.SH SYNOPSIS
-.B mount
-.RB [ \-h | \-V ]
-.LP
-.B mount
-.RB [ \-l ]
-.RB [ \-t
-.IR fstype ]
-.LP
-.B mount \-a
-.RB [ \-fFnrsvw ]
-.RB [ \-t
-.IR fstype ]
-.RB [ \-O
-.IR optlist ]
-.LP
-.B mount
-.RB [ \-fnrsvw ]
-.RB [ \-o
-.IR options ]
-.IR device | mountpoint
-.LP
-.B mount
-.RB [ \-fnrsvw ]
-.RB [ \-t
-.IB fstype ]
-.RB [ \-o
-.IR options ]
-.I device mountpoint
-.LP
-.B mount
-.BR \-\-bind | \-\-rbind | \-\-move
-.I olddir newdir
-.LP
-.B mount
-.BR \-\-make\- { shared | slave | private | unbindable | rshared | \
-rslave | rprivate | runbindable }
-.I mountpoint
-.SH DESCRIPTION
-All files accessible in a Unix system are arranged in one big
-tree, the file hierarchy, rooted at
-.IR / .
-These files can be spread out over several devices. The
-.B mount
-command serves to attach the filesystem found on some device
-to the big file tree. Conversely, the
-.BR umount (8)
-command will detach it again. The filesystem is used to control how data is
-stored on the device or provided in a virtual way by network or other services.
-
-The standard form of the
-.B mount
-command is:
-.RS
-
-.BI "mount \-t" " type device dir"
-
-.RE
-This tells the kernel to attach the filesystem found on
-.I device
-(which is of type
-.IR type )
-at the directory
-.IR dir .
-The option \fB\-t \fItype\fR is optional. The
-.B mount
-command is usually able to detect a filesystem. The root permissions are necessary
-to mount a filesystem by default. See section "Non-superuser mounts" below for more details.
-The previous contents (if any) and owner and mode of
-.I dir
-become invisible, and as long as this filesystem remains mounted,
-the pathname
-.I dir
-refers to the root of the filesystem on
-.IR device .
-
-If only the directory or the device is given, for example:
-.RS
-.sp
-.B mount /dir
-.sp
-.RE
-then \fBmount\fR looks for a mountpoint (and if not found then for a device) in the
-.I /etc/fstab
-file. It's possible to use the
-.B \-\-target
-or
-.B \-\-source
-options to avoid ambiguous interpretation of the given argument.
-For example:
-.RS
-.sp
-.B mount \-\-target /mountpoint
-.sp
-.RE
-
-The same filesystem may be mounted more than once, and in some cases (e.g.,
-network filesystems) the same filesystem may be mounted on the same
-mountpoint multiple times. The
-.B mount
-command does not implement any policy to
-control this behavior. All behavior is controlled by the kernel and it is usually
-specific to the filesystem driver. The exception is \fB\-\-all\fR, in this case
-already mounted filesystems are ignored (see \fB\-\-all\fR below for more details).
-
-.SS Listing the mounts
-The listing mode is maintained for backward compatibility only.
-
-For more robust and customizable output use
-.BR findmnt (8),
-\fBespecially in your scripts\fP. Note that control characters in the
-mountpoint name are replaced with '?'.
-
-The following command lists all mounted filesystems (of type
-.IR type ):
-.RS
-.sp
-.BR "mount " [ \-l "] [" "\-t \fItype\/\fP" ]
-.sp
-.RE
-The option \fB\-l\fR adds labels to this listing. See below.
-
-.SS Indicating the device and filesystem
-Most devices are indicated by a filename (of a block special device), like
-.IR /dev/sda1 ,
-but there are other possibilities. For example, in the case of an NFS mount,
-.I device
-may look like
-.IR knuth.cwi.nl:/dir .
-.PP
-The device names of disk partitions are unstable; hardware reconfiguration,
-and adding or removing a device can cause changes in names.
-This is the reason why it's
-strongly recommended to use filesystem or partition identifiers like UUID or
-LABEL. Currently supported identifiers (tags):
-.RS
-.TP
-LABEL=\fIlabel\fR
-Human readable filesystem identifier. See also \fB\-L\fR.
-.TP
-UUID=\fIuuid\fR
-Filesystem universally unique identifier. The format of the UUID is usually a
-series of hex digits separated by hyphens. See also \fB\-U\fR.
-.sp
-Note that
-.BR mount (8)
-uses UUIDs as strings. The UUIDs from the command line or from
-.BR fstab (5)
-are not converted to internal binary representation. The string representation
-of the UUID should be based on lower case characters.
-.TP
-PARTLABEL=\fIlabel\fR
-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).
-.TP
-PARTUUID=\fIuuid\fR
-Partition universally unique 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).
-.TP
-ID=\fIid\fR
-Hardware block device ID as generated by udevd. This identifier is usually
-based on WWN (unique storage identifier) and assigned by the hardware
-manufacturer. See \fBls /dev/disk/by-id\fR for more details, this directory
-and running udevd is required. This identifier is not recommended for generic
-use as the identifier is not strictly defined and it depends on udev, udev rules
-and hardware.
-.RE
-.sp
-The command \fBlsblk \-\-fs\fR provides an overview of filesystems, LABELs and UUIDs
-on available block devices. The command \fBblkid \-p <device>\fR provides details about
-a filesystem on the specified device.
-
-Don't forget that there is no guarantee that UUIDs and labels are really
-unique, especially if you move, share or copy the device. Use
-.B "lsblk \-o +UUID,PARTUUID"
-to verify that the UUIDs are really unique in your system.
-
-The recommended setup is to use tags (e.g.\& \fBUUID=\fIuuid\fR) rather than
-.I /dev/disk/by-{label,uuid,id,partuuid,partlabel}
-udev symlinks in the
-.I /etc/fstab
-file. Tags are
-more readable, robust and portable. The
-.BR mount (8)
-command internally uses udev
-symlinks, so the use of symlinks in
-.I /etc/fstab
-has no advantage over tags.
-For more details see
-.BR libblkid (3).
-
-The
-.I proc
-filesystem is not associated with a special device, and when
-mounting it, an arbitrary keyword\(emfor example,
-.IR proc \(emcan
-be used instead of a device specification.
-(The customary choice
-.I none
-is less fortunate: the error message `none already mounted' from
-.B mount
-can be confusing.)
-
-.SS The files /etc/fstab, /etc/mtab and /proc/mounts
-The file
-.I /etc/fstab
-(see
-.BR fstab (5)),
-may contain lines describing what devices are usually
-mounted where, using which options. The default location of the
-.BR fstab (5)
-file can be overridden with the
-.BI \-\-fstab " path"
-command-line option (see below for more details).
-.LP
-The command
-.RS
-.sp
-.B mount \-a
-.RB [ \-t
-.IR type ]
-.RB [ \-O
-.IR optlist ]
-.sp
-.RE
-(usually given in a bootscript) causes all filesystems mentioned in
-.I fstab
-(of the proper type and/or having or not having the proper options)
-to be mounted as indicated, except for those whose line contains the
-.B noauto
-keyword. Adding the
-.B \-F
-option will make \fBmount\fR fork, so that the
-filesystems are mounted in parallel.
-.LP
-When mounting a filesystem mentioned in
-.I fstab
-or
-.IR mtab ,
-it suffices to specify on the command line only the device, or only the mount point.
-.sp
-The programs
-.B mount
-and
-.B umount
-traditionally maintained a list of currently mounted filesystems in the file
-.IR /etc/mtab .
-The support for regular classic
-.I /etc/mtab
-is completely disabled at compile time by default, because on current Linux
-systems it is better to make
-.I /etc/mtab
-a symlink to
-.I /proc/mounts
-instead. The regular
-.I mtab
-file maintained in userspace cannot reliably
-work with namespaces, containers and other advanced Linux features.
-If the regular
-.I mtab
-support is enabled, then it's possible to
-use the file as well as the symlink.
-.sp
-If no arguments are given to
-.BR mount ,
-the list of mounted filesystems is printed.
-.sp
-If you want to override mount options from
-.IR /etc/fstab ,
-you have to use the \fB\-o\fR option:
-.RS
-.sp
-.BI mount " device" \fR| "dir " \-o " options"
-.sp
-.RE
-and then the mount options from the command line will be appended to
-the list of options from
-.IR /etc/fstab .
-This default behaviour can be changed using the
-\fB\-\-options\-mode\fR
-command-line option.
-The usual behavior is that the last option wins if there are conflicting
-ones.
-.sp
-The
-.B mount
-program does not read the
-.I /etc/fstab
-file if both
-.I device
-(or LABEL, UUID, ID, PARTUUID or PARTLABEL) and
-.I dir
-are specified. For example, to mount device
-.BR foo " at " /dir :
-.RS
-.sp
-.B "mount /dev/foo /dir"
-.sp
-.RE
-This default behaviour can be changed by using the
-\fB\-\-options\-source\-force\fR command-line option
-to always read configuration from
-.IR fstab .
-For non-root users
-.B mount
-always reads the
-.I fstab
-configuration.
-
-.SS Non-superuser mounts
-Normally, only the superuser can mount filesystems.
-However, when
-.I fstab
-contains the
-.B user
-option on a line, anybody can mount the corresponding filesystem.
-.LP
-Thus, given a line
-.RS
-.sp
-.B "/dev/cdrom /cd iso9660 ro,user,noauto,unhide"
-.sp
-.RE
-any user can mount the iso9660 filesystem found on an inserted CDROM
-using the command:
-.PP
-.RS
-.B "mount /cd"
-.sp
-.RE
-Note that \fBmount\fR is very strict about non-root users and all paths
-specified on command line are verified before
-.I fstab
-is parsed or a helper
-program is executed. It's strongly recommended to use a valid mountpoint to
-specify filesystem, otherwise \fBmount\fR may fail. For example it's a bad idea
-to use NFS or CIFS source on command line.
-.PP
-Since util-linux 2.35, \fBmount\fR does not exit when user permissions are
-inadequate according to libmount's internal security rules.
-Instead, it drops suid permissions
-and continues as regular non-root user. This behavior supports use-cases where
-root permissions are not necessary (e.g., fuse filesystems, user namespaces,
-etc).
-.PP
-For more details, see
-.BR fstab (5).
-Only the user that mounted a filesystem can unmount it again.
-If any user should be able to unmount it, then use
-.B users
-instead of
-.B user
-in the
-.I fstab
-line.
-The
-.B owner
-option is similar to the
-.B user
-option, with the restriction that the user must be the owner
-of the special file. This may be useful e.g.\& for
-.I /dev/fd
-if a login script makes the console user owner of this device.
-The
-.B group
-option is similar, with the restriction that the user must be a
-member of the group of the special file.
-
-.SS Bind mount operation
-Remount part of the file hierarchy somewhere else. The call is:
-
-.RS
-.br
-.B mount \-\-bind
-.I olddir newdir
-.RE
-
-or by using this
-.I fstab
-entry:
-
-.RS
-.br
-.BI / olddir
-.BI / newdir
-.B none bind
-.RE
-
-After this call the same contents are accessible in two places.
-
-It is important to understand that "bind" does not create any second-class
-or special node in the kernel VFS. The "bind" is just another operation to
-attach a filesystem. There is nowhere stored information that the filesystem
-has been attached by a "bind" operation. The \fIolddir\fR and \fInewdir\fR are
-independent and the \fIolddir\fR may be unmounted.
-
-One can also remount a single file (on a single file). It's also
-possible to use a bind mount to create a mountpoint from a regular
-directory, for example:
-
-.RS
-.br
-.B mount \-\-bind foo foo
-.RE
-
-The bind mount call attaches only (part of) a single filesystem, not possible
-submounts. The entire file hierarchy including submounts can be attached
-a second place by using:
-
-.RS
-.br
-.B mount \-\-rbind
-.I olddir newdir
-.RE
-
-Note that the filesystem mount options maintained by the kernel will remain the same as those
-on the original mount point. The userspace mount options (e.g., _netdev) will not be copied
-by
-.B mount
-and it's necessary to explicitly specify the options on the
-.B mount
-command line.
-
-Since util-linux 2.27
-.BR mount (8)
-permits changing the mount options by passing the
-relevant options along with
-.BR \-\-bind .
-For example:
-
-.RS
-.br
-.B mount \-o bind,ro foo foo
-.RE
-
-This feature is not supported by the Linux kernel; it is implemented in userspace
-by an additional \fBmount\fR(2) remounting system call.
-This solution is not atomic.
-
-The alternative (classic) way to create a read-only bind mount is to use the remount
-operation, for example:
-
-.RS
-.br
-.B mount \-\-bind
-.I olddir newdir
-.br
-.B mount \-o remount,bind,ro
-.I olddir newdir
-.RE
-
-Note that a read-only bind will create a read-only mountpoint (VFS entry),
-but the original filesystem superblock will still be writable, meaning that the
-.I olddir
-will be writable, but the
-.I newdir
-will be read-only.
-
-It's also possible to change nosuid, nodev, noexec, noatime, nodiratime and
-relatime VFS entry flags via a "remount,bind" operation.
-The other flags (for example
-filesystem-specific flags) are silently ignored. It's impossible to change mount
-options recursively (for example with \fB\-o rbind,ro\fR).
-
-Since util-linux 2.31,
-.B mount
-ignores the \fBbind\fR flag from
-.I /etc/fstab
-on a
-.B remount
-operation
-(if "\-o remount" is specified on command line).
-This is necessary to fully control
-mount options on remount by command line. In previous versions the bind
-flag has been always applied and it was impossible to re-define mount options
-without interaction with the bind semantic. This
-.BR mount (8)
-behavior does not affect situations when "remount,bind" is specified in the
-.I /etc/fstab
-file.
-
-.SS The move operation
-Move a
-.B mounted tree
-to another place (atomically). The call is:
-
-.RS
-.br
-.B mount \-\-move
-.I olddir newdir
-.RE
-
-This will cause the contents which previously appeared under
-.I olddir
-to now be accessible under
-.IR newdir .
-The physical location of the files is not changed.
-Note that
-.I olddir
-has to be a mountpoint.
-
-Note also that moving a mount residing under a shared mount is invalid and
-unsupported. Use
-.B findmnt \-o TARGET,PROPAGATION
-to see the current propagation flags.
-
-.SS Shared subtree operations
-Since Linux 2.6.15 it is possible to mark a mount and its submounts as shared,
-private, slave or unbindable. A shared mount provides the ability to create mirrors
-of that mount such that mounts and unmounts within any of the mirrors propagate
-to the other mirror. A slave mount receives propagation from its master, but
-not vice versa. A private mount carries no propagation abilities. An
-unbindable mount is a private mount which cannot be cloned through a bind
-operation. The detailed semantics are documented in
-.I Documentation/filesystems/sharedsubtree.txt
-file in the kernel source tree; see also
-.BR mount_namespaces (7).
-
-Supported operations are:
-
-.RS
-.nf
-.BI "mount \-\-make\-shared " mountpoint
-.BI "mount \-\-make\-slave " mountpoint
-.BI "mount \-\-make\-private " mountpoint
-.BI "mount \-\-make\-unbindable " mountpoint
-.fi
-.RE
-
-The following commands allow one to recursively change the type of all the
-mounts under a given mountpoint.
-
-.RS
-.nf
-.BI "mount \-\-make\-rshared " mountpoint
-.BI "mount \-\-make\-rslave " mountpoint
-.BI "mount \-\-make\-rprivate " mountpoint
-.BI "mount \-\-make\-runbindable " mountpoint
-.fi
-.RE
-
-.BR mount (8)
-.B does not read
-.BR fstab (5)
-when a \fB\-\-make-\fR* operation is requested. All necessary information has to be
-specified on the command line.
-
-Note that the Linux kernel does not allow changing multiple propagation flags
-with a single
-.BR mount (2)
-system call, and the flags cannot be mixed with other mount options and operations.
-
-Since util-linux 2.23 the \fBmount\fR command can be used to do more propagation
-(topology) changes by one mount(8) call and do it also together with other
-mount operations. This feature is EXPERIMENTAL. The propagation flags are applied
-by additional \fBmount\fR(2) system calls when the preceding mount operations
-were successful. Note that this use case is not atomic. It is possible to
-specify the propagation flags in
-.BR fstab (5)
-as mount options
-.RB ( private ,
-.BR slave ,
-.BR shared ,
-.BR unbindable ,
-.BR rprivate ,
-.BR rslave ,
-.BR rshared ,
-.BR runbindable ).
-
-For example:
-
-.RS
-.nf
-.B mount \-\-make\-private \-\-make\-unbindable /dev/sda1 /foo
-.fi
-.RE
-
-is the same as:
-
-.RS
-.nf
-.B mount /dev/sda1 /foo
-.B mount \-\-make\-private /foo
-.B mount \-\-make\-unbindable /foo
-.fi
-.RE
-
-.SH COMMAND-LINE OPTIONS
-The full set of mount options used by an invocation of
-.B mount
-is determined by first extracting the
-mount options for the filesystem from the
-.I fstab
-table, then applying any options specified by the
-.B \-o
-argument, and finally applying a
-.BR \-r " or " \-w
-option, when present.
-
-The \fBmount\fR command does not pass all command-line options to the
-\fB/sbin/mount.\fIsuffix\fR mount helpers. The interface between \fBmount\fR
-and the mount helpers is described below in the section \fBEXTERNAL HELPERS\fR.
-.sp
-Command-line options available for the
-.B mount
-command are:
-.TP
-.BR \-a , " \-\-all"
-Mount all filesystems (of the given types) mentioned in
-.I fstab
-(except for those whose line contains the
-.B noauto
-keyword). The filesystems are mounted following their order in
-.IR fstab .
-The
-.B 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 \fBmount \-\-all\fR. This means
-that all duplicated
-.I fstab
-entries will be mounted.
-.sp
-The option \fB\-\-all\fR is possible to use for remount operation too. In this
-case all filters (\fB\-t\fR and \fB\-O\fR) are applied to the table of already
-mounted filesystems.
-.sp
-Since version 2.35 is possible to use the command line option \fB\-o\fR to
-alter mount options from
-.I fstab
-(see also \fB\-\-options\-mode\fR).
-.sp
-Note that it is a bad practice to use \fBmount \-a\fR for
-.I fstab
-checking. The recommended solution is \fBfindmnt \-\-verify\fR.
-.TP
-.BR \-B , " \-\-bind"
-Remount a subtree somewhere else (so that its contents are available
-in both places). See above, under \fBBind mounts\fR.
-.TP
-.BR \-c , " \-\-no\-canonicalize"
-Don't canonicalize paths. The
-.B mount
-command canonicalizes all paths
-(from the command line or
-.IR fstab )
-by default. This option can be used
-together with the
-.B \-f
-flag for already canonicalized absolute paths. The option is designed for mount
-helpers which call \fBmount \-i\fR. It is strongly recommended to not use this
-command-line option for normal mount operations.
-.sp
-Note that \fBmount\fR(8) does not pass this option to the
-\fB/sbin/mount.\fItype\fR helpers.
-.TP
-.BR \-F , " \-\-fork"
-(Used in conjunction with
-.BR \-a .)
-Fork off a new incarnation of \fBmount\fR for each device.
-This will do the mounts on different devices or different NFS servers
-in parallel.
-This has the advantage that it is faster; also NFS timeouts proceed in
-parallel.
-A disadvantage is that the order of the mount operations is undefined.
-Thus, you cannot use this option if you want to mount both
-.I /usr
-and
-.IR /usr/spool .
-.IP "\fB\-f, \-\-fake\fP"
-Causes everything to be done except for the actual system call; if it's not
-obvious, this ``fakes'' mounting the filesystem. This option is useful in
-conjunction with the
-.B \-v
-flag to determine what the
-.B mount
-command is trying to do. It can also be used to add entries for devices
-that were mounted earlier with the \fB\-n\fR option. The \fB\-f\fR option
-checks for an existing record in
-.I /etc/mtab
-and fails when the record already
-exists (with a regular non-fake mount, this check is done by the kernel).
-.IP "\fB\-i, \-\-internal\-only\fP"
-Don't call the \fB/sbin/mount.\fIfilesystem\fR helper even if it exists.
-.TP
-.BR \-L , " \-\-label " \fIlabel
-Mount the partition that has the specified
-.IR label .
-.TP
-.BR \-l , " \-\-show\-labels"
-Add the labels in the mount output. \fBmount\fR must have
-permission to read the disk device (e.g.\& be set-user-ID root) for this to work.
-One can set such a label for ext2, ext3 or ext4 using the
-.BR e2label (8)
-utility, or for XFS using
-.BR xfs_admin (8),
-or for reiserfs using
-.BR reiserfstune (8).
-.TP
-.BR \-M , " \-\-move"
-Move a subtree to some other place. See above, the subsection
-\fBThe move operation\fR.
-.TP
-.BR \-n , " \-\-no\-mtab"
-Mount without writing in
-.IR /etc/mtab .
-This is necessary for example when
-.I /etc
-is on a read-only filesystem.
-.TP
-.BR \-N , " \-\-namespace " \fIns
-Perform the mount operation in the mount namespace specified by \fIns\fR.
-\fIns\fR is either PID of process running in that namespace
-or special file representing that namespace.
-.sp
-.BR mount (8)
-switches to the mount namespace when it reads
-.IR /etc/fstab ,
-writes
-.I /etc/mtab
-(or writes to
-.IR /run/mount )
-and calls the
-.BR 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
-.BR mount (2)
-call.
-.sp
-See \fBmount_namespaces\fR(7) for more information.
-.TP
-.BR \-O , " \-\-test\-opts " \fIopts
-Limit the set of filesystems to which the
-.B \-a
-option applies. In this regard it is like the
-.B \-t
-option except that
-.B \-O
-is useless without
-.BR \-a .
-For example, the command:
-.RS
-.RS
-.sp
-.B "mount \-a \-O no_netdev"
-.sp
-.RE
-mounts all filesystems except those which have the option
-.I _netdev
-specified in the options field in the
-.I /etc/fstab
-file.
-
-It is different from
-.B \-t
-in that each option is matched exactly; a leading
-.B no
-at the beginning of one option does not negate the rest.
-
-The
-.B \-t
-and
-.B \-O
-options are cumulative in effect; that is, the command
-.RS
-.sp
-.B "mount \-a \-t ext2 \-O _netdev"
-.sp
-.RE
-mounts all ext2 filesystems with the _netdev option, not all filesystems
-that are either ext2 or have the _netdev option specified.
-.RE
-.TP
-.BR \-o , " \-\-options " \fIopts
-Use the specified mount options. The \fIopts\fR argument is
-a comma-separated list. For example:
-.RS
-.RS
-.sp
-.B "mount LABEL=mydisk \-o noatime,nodev,nosuid"
-.sp
-.RE
-
-For more details, see the
-.B FILESYSTEM-INDEPENDENT MOUNT OPTIONS
-and
-.B FILESYSTEM-SPECIFIC MOUNT OPTIONS
-sections.
-.RE
-
-.TP
-.BR "\-\-options\-mode " \fImode
-Controls how to combine options from
-.IR fstab / mtab
-with options from the command line.
-\fImode\fR can be one of
-.BR ignore ", " append ", " prepend " or " replace .
-For example, \fBappend\fR means that options from
-.I fstab
-are appended to options from the command line.
-The default value is \fBprepend\fR -- it means command line options are evaluated after
-.I fstab
-options.
-Note that the last option wins if there are conflicting ones.
-
-.TP
-.BR "\-\-options\-source " \fIsource
-Source of default options.
-\fIsource\fR is a comma-separated list of
-.BR fstab ", " mtab " and " disable .
-\fBdisable\fR disables
-.BR fstab " and " mtab
-and disables \fB\-\-options\-source\-force\fR.
-The default value is \fBfstab,mtab\fR.
-
-.TP
-.B \-\-options\-source\-force
-Use options from
-.IR fstab / mtab
-even if both \fIdevice\fR and \fIdir\fR are specified.
-
-.TP
-.BR \-R , " \-\-rbind"
-Remount a subtree and all possible submounts somewhere else (so that its
-contents are available in both places). See above, the subsection
-\fBBind mounts\fR.
-.TP
-.BR \-r , " \-\-read\-only"
-Mount the filesystem read-only. A synonym is
-.BR "\-o ro" .
-.sp
-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 \fBro,noload\fR mount
-options or set the block device itself to read-only mode, see the
-.BR blockdev (8)
-command.
-.TP
-.B \-s
-Tolerate sloppy mount options rather than failing. This will ignore mount
-options not supported by a filesystem type. Not all filesystems support this
-option. Currently it's supported by the \fBmount.nfs\fR mount helper only.
-.TP
-.BI \-\-source " device"
-If only one argument for the mount command is given, then the argument might be
-interpreted as the target (mountpoint) or source (device).
-This option allows you to
-explicitly define that the argument is the mount source.
-.TP
-.BI \-\-target " directory"
-If only one argument for the mount command is given, then the argument might be
-interpreted as the target (mountpoint) or source (device).
-This option allows you to
-explicitly define that the argument is the mount target.
-.TP
-.BI \-\-target\-prefix " directory"
-Prepend the specified directory to all mount targets.
-This option can be used to follow
-.IR fstab ,
-but mount operations are done in another place, for example:
-.RS
-.RS
-.sp
-.B "mount \-\-all \-\-target\-prefix /chroot \-o X\-mount.mkdir"
-.sp
-.RE
-mounts all from system
-.I fstab
-to
-.IR /chroot ,
-all missing mountpoint are created
-(due to X-mount.mkdir). See also \fB\-\-fstab\fP to use an alternative
-.IR fstab .
-.RE
-.TP
-.BR \-T , " \-\-fstab " \fIpath
-Specifies an alternative
-.I fstab
-file.
-If \fIpath\fP is a directory, then the files
-in the directory are sorted by
-.BR strverscmp (3);
-files that start with "."\& or without an
-.I \&.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.
-.sp
-Note that \fBmount\fR(8) does not pass the option \fB\-\-fstab\fP to the
-\fB/sbin/mount.\fItype\fR helpers, meaning that the alternative
-.I fstab
-files will be
-invisible for the helpers. This is no problem for normal mounts, but user
-(non-root) mounts always require
-.I fstab
-to verify the user's rights.
-.TP
-.BR \-t , " \-\-types " \fIfstype
-The argument following the
-.B \-t
-is used to indicate the filesystem type. The filesystem types which are
-currently supported depend on the running kernel. See
-.I /proc/filesystems
-and
-.I /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.
-.sp
-The programs
-.B mount
-and
-.B umount
-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).
-
-If no
-.B \-t
-option is given, or if the
-.B auto
-type is specified,
-.B mount
-will try to guess the desired type.
-Mount uses the blkid library for guessing the filesystem
-type; if that does not turn up anything that looks familiar,
-.B mount
-will try to read the file
-.IR /etc/filesystems ,
-or, if that does not exist,
-.IR /proc/filesystems .
-All of the filesystem types listed there will be tried,
-except for those that are labeled "nodev" (e.g.\&
-.IR devpts ,
-.I proc
-and
-.IR nfs ).
-If
-.I /etc/filesystems
-ends in a line with a single *, mount will read
-.I /proc/filesystems
-afterwards. While trying, all filesystem types will be
-mounted with the mount option \fBsilent\fR.
-.sp
-The
-.B auto
-type may be useful for user-mounted floppies.
-Creating a file
-.I /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.
-.sp
-More than one type may be specified in a comma-separated
-list, for the
-.B \-t
-option as well as in an
-.I /etc/fstab
-entry. The list of filesystem types for the
-.B \-t
-option can be prefixed with
-.B no
-to specify the filesystem types on which no action should be taken.
-The prefix
-.B no
-has no effect when specified in an
-.I /etc/fstab
-entry.
-.sp
-The prefix
-.B no
-can be meaningful with the
-.B \-a
-option. For example, the command
-.RS
-.RS
-.sp
-.B "mount \-a \-t nomsdos,smbfs"
-.sp
-.RE
-mounts all filesystems except those of type
-.I msdos
-and
-.IR smbfs .
-.sp
-For most types all the
-.B mount
-program has to do is issue a simple
-.BR 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, \fBmount\fR will execute the program
-.BI /sbin/mount. type
-(if that exists) when called with type
-.IR type .
-Since different versions of the
-.B smbmount
-program have different calling conventions,
-.B /sbin/mount.smbfs
-may have to be a shell script that sets up the desired call.
-.RE
-.TP
-.BR \-U , " \-\-uuid " \fIuuid
-Mount the partition that has the specified
-.IR uuid .
-.TP
-.BR \-v , " \-\-verbose"
-Verbose mode.
-.TP
-.BR \-w , " \-\-rw" , " \-\-read\-write"
-Mount the filesystem read/write. Read-write is the kernel default and the
-.B mount
-default is to try read-only if the previous mount syscall with read-write flags
-on write-protected devices of filesystems failed.
-.sp
-A synonym is
-.BR "\-o rw" .
-
-Note that specifying \fB\-w\fR on the command line forces \fBmount\fR to never
-try read-only mount on write-protected devices or already mounted read-only
-filesystems.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-
-.SH FILESYSTEM-INDEPENDENT MOUNT OPTIONS
-Some of these options are only useful when they appear in the
-.I /etc/fstab
-file.
-
-Some of these options could be enabled or disabled by default
-in the system kernel. To check the current setting see the options
-in
-.IR /proc/mounts .
-Note that filesystems also have per-filesystem
-specific default mount options (see for example \fBtune2fs \-l\fP
-output for extN filesystems).
-
-The following options apply to any filesystem that is being
-mounted (but not every filesystem actually honors them \(en e.g.\&, the
-.B sync
-option today has an effect only for ext2, ext3, ext4, fat, vfat, ufs and xfs):
-
-.TP
-.B async
-All I/O to the filesystem should be done asynchronously. (See also the
-.B sync
-option.)
-.TP
-.B atime
-Do not use the \fBnoatime\fR feature, so the inode access time is controlled
-by kernel defaults. See also the descriptions of the \fB\%relatime\fR and
-.B strictatime
-mount options.
-.TP
-.B noatime
-Do not update inode access times on this filesystem (e.g.\& for faster
-access on the news spool to speed up news servers). This works for all
-inode types (directories too), so it implies \fB\%nodiratime\fR.
-.TP
-.B auto
-Can be mounted with the
-.B \-a
-option.
-.TP
-.B noauto
-Can only be mounted explicitly (i.e., the
-.B \-a
-option will not cause the filesystem to be mounted).
-.TP
-.na
-.BR context=\fIcontext ", " fscontext=\fIcontext ", " defcontext=\fIcontext ", and " \%rootcontext=\fIcontext
-.ad
-The
-.B 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
-.B 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.
-
-A commonly used option for removable media is
-.BR \%context="system_u:object_r:removable_t" .
-
-Two other options are
-.B fscontext=
-and
-.BR defcontext= ,
-both of which are mutually exclusive of the
-.B context=
-option. This means you
-can use fscontext and defcontext with each other, but neither can be used with
-context.
-
-The
-.B 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.
-
-You can set the default security context for unlabeled files using
-.B defcontext=
-option. This overrides the value set for unlabeled files in the policy and requires a
-filesystem that supports xattr labeling.
-
-The
-.B 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.
-
-Note that the kernel rejects any remount request that includes the context
-option, \fBeven\fP when unchanged from the current context.
-
-.BR "Warning: the \fIcontext\fP value might contain commas" ,
-in which case the value has to be properly quoted, otherwise
-.BR mount (8)
-will interpret the comma as a separator between mount options. Don't forget that
-the shell strips off quotes and thus
-.BR "double quoting is required" .
-For example:
-.RS
-.RS
-.sp
-.nf
-.B mount \-t tmpfs none /mnt \-o \e
-.B \ \ 'context="system_u:object_r:tmp_t:s0:c127,c456",noexec'
-.fi
-.sp
-.RE
-For more details, see
-.BR selinux (8).
-.RE
-
-.TP
-.B defaults
-Use the default options:
-.BR rw ", " suid ", " dev ", " exec ", " auto ", " nouser ", and " async .
-
-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.
-.TP
-.B dev
-Interpret character or block special devices on the filesystem.
-.TP
-.B nodev
-Do not interpret character or block special devices on the filesystem.
-.TP
-.B diratime
-Update directory inode access times on this filesystem. This is the default.
-(This option is ignored when \fBnoatime\fR is set.)
-.TP
-.B nodiratime
-Do not update directory inode access times on this filesystem.
-(This option is implied when \fBnoatime\fR is set.)
-.TP
-.B dirsync
-All directory updates within the filesystem should be done synchronously.
-This affects the following system calls: creat, link, unlink, symlink,
-mkdir, rmdir, mknod and rename.
-.TP
-.B exec
-Permit execution of binaries.
-.TP
-.B noexec
-Do not permit direct execution of any binaries on the mounted filesystem.
-.TP
-.B group
-Allow an ordinary user to mount the filesystem if one
-of that user's groups matches the group of the device.
-This option implies the options
-.BR nosuid " and " nodev
-(unless overridden by subsequent options, as in the option line
-.BR group,dev,suid ).
-.TP
-.B iversion
-Every time the inode is modified, the i_version field will be incremented.
-.TP
-.B noiversion
-Do not increment the i_version inode field.
-.TP
-.B mand
-Allow mandatory locks on this filesystem. See
-.BR fcntl (2).
-.TP
-.B nomand
-Do not allow mandatory locks on this filesystem.
-.TP
-.B _netdev
-The filesystem resides on a device that requires network access
-(used to prevent the system from attempting to mount these filesystems
-until the network has been enabled on the system).
-.TP
-.B nofail
-Do not report errors for this device if it does not exist.
-.TP
-.B 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 \fB\%noatime\fR, but it doesn't
-break \fBmutt\fR or other applications that need to know if a file has been
-read since the last time it was modified.)
-
-Since Linux 2.6.30, the kernel defaults to the behavior provided by this
-option (unless
-.B \%noatime
-was specified), and the
-.B \%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.
-.TP
-.B norelatime
-Do not use the
-.B relatime
-feature. See also the
-.B strictatime
-mount option.
-.TP
-.B strictatime
-Allows to explicitly request full atime updates. This makes it
-possible for the kernel to default to
-.B \%relatime
-or
-.B \%noatime
-but still allow userspace to override it. For more details about the default
-system mount options see
-.IR /proc/mounts .
-.TP
-.B nostrictatime
-Use the kernel's default behavior for inode access time updates.
-.TP
-.B lazytime
-Only update times (atime, mtime, ctime) on the in-memory version of the file inode.
-
-This mount option significantly reduces writes to the inode table for
-workloads that perform frequent random writes to preallocated files.
-
-The on-disk timestamps are updated only when:
-.RS
-.IP - 2
-the inode needs to be updated for some change unrelated to file timestamps
-.IP -
-the application employs
-.BR fsync (2),
-.BR syncfs (2),
-or
-.BR sync (2)
-.IP -
-an undeleted inode is evicted from memory
-.IP -
-more than 24 hours have passed since the inode was written to disk.
-.RE
-.sp
-.TP
-.B nolazytime
-Do not use the lazytime feature.
-.TP
-.B suid
-Honor set-user-ID and set-group-ID bits or file capabilities when
-executing programs from this filesystem.
-.TP
-.B nosuid
-Do not honor set-user-ID and set-group-ID bits or file capabilities when
-executing programs from this filesystem.
-.TP
-.B silent
-Turn on the silent flag.
-.TP
-.B loud
-Turn off the silent flag.
-.TP
-.B owner
-Allow an ordinary user to mount the filesystem if that
-user is the owner of the device.
-This option implies the options
-.BR nosuid " and " nodev
-(unless overridden by subsequent options, as in the option line
-.BR owner,dev,suid ).
-.TP
-.B 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.
-
-The remount operation together with the
-.B bind
-flag has special semantics. See above, the subsection \fBBind mounts\fR.
-
-The remount functionality follows the standard way the
-.B mount
-command works
-with options from
-.IR fstab .
-This means that \fBmount\fR does not read
-.I fstab
-(or
-.IR mtab )
-only when both
-.I device
-and
-.I dir
-are specified.
-.sp
-.in +4
-.B "mount \-o remount,rw /dev/foo /dir"
-.in
-.sp
-After this call all old mount options are replaced and arbitrary stuff from
-.I fstab
-(or
-.IR mtab )
-is ignored, except the loop= option which is internally
-generated and maintained by the mount command.
-.sp
-.in +4
-.B "mount \-o remount,rw /dir"
-.in
-.sp
-After this call, mount reads
-.I fstab
-and merges these options with
-the options from the command line (\fB\-o\fR).
-If no mountpoint is found in
-.IR fstab ,
-then a remount with unspecified source is
-allowed.
-.sp
-.B mount
-allows the use of \fB\-\-all\fR to remount all already mounted filesystems
-which match a specified filter (\fB\-O\fR and \fB\-t\fR). For example:
-.sp
-.in +4
-.B "mount \-\-all \-o remount,ro \-t vfat"
-.in
-.sp
-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
-.B mount
-command reads
-.I fstab
-or
-.I mtab
-and merges these options with the options
-from the command line.
-.TP
-.B ro
-Mount the filesystem read-only.
-.TP
-.B rw
-Mount the filesystem read-write.
-.TP
-.B sync
-All I/O to the filesystem should be done synchronously. In the case of
-media with a limited number of write cycles
-(e.g.\& some flash drives), \fBsync\fR may cause life-cycle shortening.
-.TP
-.B user
-Allow an ordinary user to mount the filesystem.
-The name of the mounting user is written to the
-.I mtab
-file (or to the private
-libmount file in
-.I /run/mount
-on systems without a regular
-.IR mtab )
-so that this
-same user can unmount the filesystem again.
-This option implies the options
-.BR noexec ", " nosuid ", and " nodev
-(unless overridden by subsequent options, as in the option line
-.BR user,exec,dev,suid ).
-.TP
-.B nouser
-Forbid an ordinary user to mount the filesystem.
-This is the default; it does not imply any other options.
-.TP
-.B users
-Allow any user to mount and to unmount the filesystem, even
-when some other ordinary user mounted it.
-This option implies the options
-.BR noexec ", " nosuid ", and " nodev
-(unless overridden by subsequent options, as in the option line
-.BR users,exec,dev,suid ).
-.TP
-.B X-*
-All options prefixed with "X-" are interpreted as comments or as userspace
-application-specific options.
-These options are not stored in user space (e.g.,
-.I mtab
-file),
-nor sent to the mount.\fItype\fR helpers nor to the
-.BR mount (2)
-system call. The suggested format is \fBX-\fIappname\fR.\fIoption\fR.
-.TP
-.B x-*
-The same as \fBX-*\fR options, but stored permanently in user space.
-This means the options are also available for
-.B umount
-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).
-
-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
-.I fstab
-configurations usable
-without a change.
-.TP
-.BR X-mount.mkdir [ = \fImode\fR ]
-Allow to make a target directory (mountpoint) if it does not exit yet.
-The optional argument
-.I mode
-specifies the filesystem access mode used for
-.BR mkdir (2)
-in octal notation. The default mode is 0755. This functionality is supported
-only for root users or when mount executed without suid permissions. The option
-is also supported as x-mount.mkdir, this notation is deprecated since v2.30.
-.TP
-.B nosymfollow
-Do not follow symlinks when resolving paths. Symlinks can still be created,
-and
-.BR readlink (1),
-.BR readlink (2),
-.BR realpath (1)
-and
-.BR realpath (3)
-all still work properly.
-
-.SH FILESYSTEM-SPECIFIC MOUNT OPTIONS
-This section lists options that are specific to particular filesystems.
-Where possible, you should first consult filesystem-specific manual pages
-for details.
-Some of those pages are listed in the following table.
-.TS
-lb lb
-l l.
-Filesystem(s) Manual page
-btrfs \fBbtrfs\fP(5)
-cifs \fBmount.cifs\fP(8)
-ext2, ext3, ext4 \fBext4\fP(5)
-fuse \fBfuse\fP(8)
-nfs \fBnfs\fP(5)
-tmpfs \fBtmpfs\fP(5)
-xfs \fBxfs\fP(5)
-.TE
-.PP
-Note that some of the pages listed above might be available only
-after you install the respective userland tools.
-.PP
-The following options apply only to certain filesystems.
-We sort them by filesystem.
-All options follow the
-.B \-o
-flag.
-.PP
-What options are supported depends a bit on the running kernel.
-Further information may be available in filesystem-specific
-files in the kernel source subdirectory
-.IR Documentation/filesystems .
-.\"
-.SS "Mount options for adfs"
-.TP
-\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
-Set the owner and group of the files in the filesystem (default: uid=gid=0).
-.TP
-\fBownmask=\fP\,\fIvalue\fP and \fBothmask=\fP\,\fIvalue\fP
-Set the permission mask for ADFS 'owner' permissions and 'other' permissions,
-respectively (default: 0700 and 0077, respectively).
-See also
-.IR /usr/src/linux/Documentation/filesystems/adfs.rst .
-
-.SS "Mount options for affs"
-.TP
-\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
-Set the owner and group of the root of the filesystem (default: uid=gid=0,
-but with option
-.B uid
-or
-.B gid
-without specified value, the UID and GID of the current process are taken).
-.TP
-\fBsetuid=\fP\,\fIvalue\fP and \fBsetgid=\fP\,\fIvalue\fP
-Set the owner and group of all files.
-.TP
-.BI mode= value
-Set the mode of all files to
-.IR value " & 0777"
-disregarding the original permissions.
-Add search permission to directories that have read permission.
-The value is given in octal.
-.TP
-.B protect
-Do not allow any changes to the protection bits on the filesystem.
-.TP
-.B usemp
-Set UID and GID of the root of the filesystem to the UID and GID
-of the mount point upon the first sync or umount, and then
-clear this option. Strange...
-.TP
-.B verbose
-Print an informational message for each successful mount.
-.TP
-.BI prefix= string
-Prefix used before volume name, when following a link.
-.TP
-.BI volume= string
-Prefix (of length at most 30) used before '/' when following a symbolic link.
-.TP
-.BI reserved= value
-(Default: 2.) Number of unused blocks at the start of the device.
-.TP
-.BI root= value
-Give explicitly the location of the root block.
-.TP
-.BI bs= value
-Give blocksize. Allowed values are 512, 1024, 2048, 4096.
-.TP
-.BR grpquota | noquota | quota | usrquota
-These options are accepted but ignored.
-(However, quota utilities may react to such strings in
-.IR /etc/fstab .)
-
-.SS "Mount options for debugfs"
-The debugfs filesystem is a pseudo filesystem, traditionally mounted on
-.IR /sys/kernel/debug .
-.\" or just /debug
-.\" present since 2.6.11
-As of kernel version 3.4, debugfs has the following options:
-.TP
-.BI uid= n ", gid=" n
-Set the owner and group of the mountpoint.
-.TP
-.BI mode= value
-Sets the mode of the mountpoint.
-
-.SS "Mount options for devpts"
-The devpts filesystem is a pseudo filesystem, traditionally mounted on
-.IR /dev/pts .
-In order to acquire a pseudo terminal, a process opens
-.IR /dev/ptmx ;
-the number of the pseudo terminal is then made available to the process
-and the pseudo terminal slave can be accessed as
-.IR /dev/pts/ <number>.
-.TP
-\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
-This sets the owner or the group of newly created pseudo terminals to
-the specified values. When nothing is specified, they will
-be set to the UID and GID of the creating process.
-For example, if there is a tty group with GID 5, then
-.B gid=5
-will cause newly created pseudo terminals to belong to the tty group.
-.TP
-.BI mode= value
-Set the mode of newly created pseudo terminals to the specified value.
-The default is 0600.
-A value of
-.B mode=620
-and
-.B gid=5
-makes "mesg y" the default on newly created pseudo terminals.
-.TP
-\fBnewinstance
-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.
-
-All mounts of devpts without this
-.B newinstance
-option share the same set of pseudo terminal indices (i.e., legacy mode).
-Each mount of devpts with the
-.B newinstance
-option has a private set of pseudo terminal indices.
-
-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.
-
-To use this option effectively,
-.I /dev/ptmx
-must be a symbolic link to
-.IR pts/ptmx .
-See
-.I Documentation/filesystems/devpts.txt
-in the Linux kernel source tree for details.
-.TP
-.BI ptmxmode= value
-
-Set the mode for the new
-.I ptmx
-device node in the devpts filesystem.
-
-With the support for multiple instances of devpts (see
-.B newinstance
-option above), each instance has a private
-.I ptmx
-node in the root of the devpts filesystem (typically
-.IR /dev/pts/ptmx ).
-
-For compatibility with older versions of the kernel, the
-default mode of the new
-.I ptmx
-node is 0000.
-.BI ptmxmode= value
-specifies a more useful mode for the
-.I ptmx
-node and is highly recommended when the
-.B newinstance
-option is specified.
-
-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.
-
-.SS "Mount options for fat"
-(Note:
-.I fat
-is not a separate filesystem, but a common part of the
-.IR msdos ,
-.I umsdos
-and
-.I vfat
-filesystems.)
-.TP
-.BR blocksize= { 512 | 1024 | 2048 }
-Set blocksize (default 512). This option is obsolete.
-.TP
-\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
-Set the owner and group of all files.
-(Default: the UID and GID of the current process.)
-.TP
-.BI umask= value
-Set the umask (the bitmask of the permissions that are
-.B not
-present). The default is the umask of the current process.
-The value is given in octal.
-.TP
-.BI dmask= value
-Set the umask applied to directories only.
-The default is the umask of the current process.
-The value is given in octal.
-.TP
-.BI fmask= value
-Set the umask applied to regular files only.
-The default is the umask of the current process.
-The value is given in octal.
-.TP
-.BI allow_utime= value
-This option controls the permission check of mtime/atime.
-.RS
-.TP
-.B 20
-If current process is in group of file's group ID, you can change timestamp.
-.TP
-.B 2
-Other users can change timestamp.
-.PP
-The default is set from `dmask' option. (If the directory is writable,
-.BR utime (2)
-is also allowed. I.e.\& \s+3\(ti\s0dmask & 022)
-
-Normally
-.BR utime (2)
-checks that the current process is owner of the file, or that it has the
-.B CAP_FOWNER
-capability. But FAT filesystems don't have UID/GID on disk, so the
-normal check is too inflexible. With this option you can relax it.
-.RE
-.TP
-.BI check= value
-Three different levels of pickiness can be chosen:
-.RS
-.TP
-.BR r [ elaxed ]
-Upper and lower case are accepted and equivalent, long name parts are
-truncated (e.g.\&
-.I verylongname.foobar
-becomes
-.IR verylong.foo ),
-leading and embedded spaces are accepted in each name part (name and extension).
-.TP
-.BR n [ ormal ]
-Like "relaxed", but many special characters (*, ?, <, spaces, etc.) are
-rejected. This is the default.
-.TP
-.BR s [ trict ]
-Like "normal", but names that contain long parts or special characters
-that are sometimes used on Linux but are not accepted by MS-DOS
-(+, =, etc.) are rejected.
-.RE
-.TP
-.BI codepage= value
-Sets the codepage for converting to shortname characters on FAT
-and VFAT filesystems. By default, codepage 437 is used.
-.TP
-.BI conv= mode
-This option is obsolete and may fail or be ignored.
-.TP
-.BI cvf_format= module
-Forces the driver to use the CVF (Compressed Volume File) module
-.RI cvf_ module
-instead of auto-detection. If the kernel supports kmod, the
-cvf_format=xxx option also controls on-demand CVF module loading.
-This option is obsolete.
-.TP
-.BI cvf_option= option
-Option passed to the CVF module. This option is obsolete.
-.TP
-.B debug
-Turn on the
-.I debug
-flag. A version string and a list of filesystem parameters will be
-printed (these data are also printed if the parameters appear to be
-inconsistent).
-.TP
-.B discard
-If set, causes discard/TRIM commands to be issued to the block device
-when blocks are freed. This is useful for SSD devices and
-sparse/thinly-provisioned LUNs.
-.TP
-.B dos1xfloppy
-If set, use a fallback default BIOS Parameter Block configuration, determined
-by backing device size. These static parameters match defaults assumed by DOS
-1.x for 160 kiB, 180 kiB, 320 kiB, and 360 kiB floppies and floppy images.
-.TP
-.BR errors= { panic | continue | remount-ro }
-Specify FAT behavior on critical errors: panic, continue without doing
-anything, or remount the partition in read-only mode (default behavior).
-.TP
-.BR fat= { 12 | 16 | 32 }
-Specify a 12, 16 or 32 bit fat. This overrides
-the automatic FAT type detection routine. Use with caution!
-.TP
-.BI iocharset= value
-Character set to use for converting between 8 bit characters
-and 16 bit Unicode characters. The default is iso8859-1.
-Long filenames are stored on disk in Unicode format.
-.TP
-.BR nfs= { stale_rw | nostale_ro }
-Enable this only if you want to export the FAT filesystem over NFS.
-
-.BR 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
-.B ESTALE
-errors.
-
-.BR 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
-.B 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.
-
-To maintain backward compatibility, '\-o nfs' is also accepted,
-defaulting to
-.BR stale_rw .
-.TP
-.B tz=UTC
-This option disables the conversion of timestamps
-between local time (as used by Windows on FAT) and UTC
-(which Linux uses internally). This is particularly
-useful when mounting devices (like digital cameras)
-that are set to UTC in order to avoid the pitfalls of
-local time.
-.TP
-.BI time_offset= minutes
-Set offset for conversion of timestamps from local time used by FAT to UTC.
-I.e.,
-.I minutes
-will be subtracted from each timestamp to convert it to UTC used
-internally by Linux. This is useful when the time zone set in the kernel via
-.BR settimeofday (2)
-is not the time zone used by the filesystem. Note
-that this option still does not provide correct time stamps in all cases in
-presence of DST - time stamps in a different DST setting will be off by one
-hour.
-.TP
-.B quiet
-Turn on the
-.I quiet
-flag. Attempts to chown or chmod files do not return errors,
-although they fail. Use with caution!
-.TP
-.B 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).
-
-If you want to use ATTR_RO as read-only flag even for the directory, set this
-option.
-.TP
-.B showexec
-If set, the execute permission bits of the file will be allowed only if
-the extension part of the name is \&.EXE, \&.COM, or \&.BAT. Not set by default.
-.TP
-.B sys_immutable
-If set, ATTR_SYS attribute on FAT is handled as IMMUTABLE flag on Linux.
-Not set by default.
-.TP
-.B flush
-If set, the filesystem will try to flush to disk more early than normal.
-Not set by default.
-.TP
-.B usefree
-Use the "free clusters" value stored on FSINFO. It'll
-be used to determine number of free clusters without
-scanning disk. But it's not used by default, because
-recent Windows don't update it correctly in some
-case. If you are sure the "free clusters" on FSINFO is
-correct, by this option you can avoid scanning disk.
-.TP
-.BR dots ", " nodots ", " dotsOK= [ yes | no ]
-Various misguided attempts to force Unix or DOS conventions
-onto a FAT filesystem.
-
-.SS "Mount options for hfs"
-.TP
-.BI creator= cccc ", type=" cccc
-Set the creator/type values as shown by the MacOS finder
-used for creating new files. Default values: '????'.
-.TP
-.BI uid= n ", gid=" n
-Set the owner and group of all files.
-(Default: the UID and GID of the current process.)
-.TP
-.BI dir_umask= n ", file_umask=" n ", umask=" n
-Set the umask used for all directories, all regular files, or all
-files and directories. Defaults to the umask of the current process.
-.TP
-.BI session= n
-Select the CDROM session to mount.
-Defaults to leaving that decision to the CDROM driver.
-This option will fail with anything but a CDROM as underlying device.
-.TP
-.BI part= n
-Select partition number n from the device.
-Only makes sense for CDROMs.
-Defaults to not parsing the partition table at all.
-.TP
-.B quiet
-Don't complain about invalid mount options.
-
-.SS "Mount options for hpfs"
-.TP
-\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
-Set the owner and group of all files. (Default: the UID and GID
-of the current process.)
-.TP
-.BI umask= value
-Set the umask (the bitmask of the permissions that are
-.B not
-present). The default is the umask of the current process.
-The value is given in octal.
-.TP
-.BR case= { lower | asis }
-Convert all files names to lower case, or leave them.
-(Default:
-.BR case=lower .)
-.TP
-.BI conv= mode
-This option is obsolete and may fail or being ignored.
-.TP
-.B nocheck
-Do not abort mounting when certain consistency checks fail.
-
-.SS "Mount options for iso9660"
-ISO 9660 is a standard describing a filesystem structure to be used
-on CD-ROMs. (This filesystem type is also seen on some DVDs. See also the
-.I udf
-filesystem.)
-
-Normal
-.I iso9660
-filenames appear in an 8.3 format (i.e., DOS-like restrictions on filename
-length), and in addition all characters are in upper case. Also there is
-no field for file ownership, protection, number of links, provision for
-block/character devices, etc.
-
-Rock Ridge is an extension to iso9660 that provides all of these UNIX-like
-features. Basically there are extensions to each directory record that
-supply all of the additional information, and when Rock Ridge is in use,
-the filesystem is indistinguishable from a normal UNIX filesystem (except
-that it is read-only, of course).
-.TP
-.B norock
-Disable the use of Rock Ridge extensions, even if available. Cf.\&
-.BR map .
-.TP
-.B nojoliet
-Disable the use of Microsoft Joliet extensions, even if available. Cf.\&
-.BR map .
-.TP
-.BR check= { r [ elaxed ]| s [ trict ]}
-With
-.BR check=relaxed ,
-a filename is first converted to lower case before doing the lookup.
-This is probably only meaningful together with
-.B norock
-and
-.BR map=normal .
-(Default:
-.BR check=strict .)
-.TP
-\fBuid=\fP\,\fIvalue\fP and \fBgid=\fP\,\fIvalue\fP
-Give all files in the filesystem the indicated user or group id,
-possibly overriding the information found in the Rock Ridge extensions.
-(Default:
-.BR uid=0,gid=0 .)
-.TP
-.BR map= { n [ ormal ]| o [ ff ]| a [ corn ]}
-For non-Rock Ridge volumes, normal name translation maps upper
-to lower case ASCII, drops a trailing `;1', and converts `;' to `.'.
-With
-.B map=off
-no name translation is done. See
-.BR norock .
-(Default:
-.BR map=normal .)
-.B map=acorn
-is like
-.B map=normal
-but also apply Acorn extensions if present.
-.TP
-.BI mode= value
-For non-Rock Ridge volumes, give all files the indicated mode.
-(Default: read and execute permission for everybody.)
-Octal mode values require a leading 0.
-.TP
-.B unhide
-Also show hidden and associated files.
-(If the ordinary files and the associated or hidden files have
-the same filenames, this may make the ordinary files inaccessible.)
-.TP
-.BR block= { 512 | 1024 | 2048 }
-Set the block size to the indicated value.
-(Default:
-.BR block=1024 .)
-.TP
-.BI conv= mode
-This option is obsolete and may fail or being ignored.
-.TP
-.B cruft
-If the high byte of the file length contains other garbage,
-set this mount option to ignore the high order bits of the file length.
-This implies that a file cannot be larger than 16\ MB.
-.TP
-.BI session= x
-Select number of session on multisession CD.
-.TP
-.BI sbsector= xxx
-Session begins from sector xxx.
-.LP
-The following options are the same as for vfat and specifying them only makes
-sense when using discs encoded using Microsoft's Joliet extensions.
-.TP
-.BI iocharset= value
-Character set to use for converting 16 bit Unicode characters on CD
-to 8 bit characters. The default is iso8859-1.
-.TP
-.B utf8
-Convert 16 bit Unicode characters on CD to UTF-8.
-
-.SS "Mount options for jfs"
-.TP
-.BI iocharset= name
-Character set to use for converting from Unicode to ASCII. The default is
-to do no conversion. Use
-.B iocharset=utf8
-for UTF8 translations. This requires CONFIG_NLS_UTF8 to be set in
-the kernel
-.I ".config"
-file.
-.TP
-.BI resize= value
-Resize the volume to
-.I value
-blocks. JFS only supports growing a volume, not shrinking it. This option
-is only valid during a remount, when the volume is mounted read-write. The
-.B resize
-keyword with no value will grow the volume to the full size of the partition.
-.TP
-.B nointegrity
-Do not write to the journal. The primary use of this option is to allow
-for higher performance when restoring a volume from backup media. The
-integrity of the volume is not guaranteed if the system abnormally ends.
-.TP
-.B integrity
-Default. Commit metadata changes to the journal. Use this option to remount
-a volume where the
-.B nointegrity
-option was previously specified in order to restore normal behavior.
-.TP
-.BR errors= { continue | remount-ro | panic }
-Define the behavior when an error is encountered.
-(Either ignore errors and just mark the filesystem erroneous and continue,
-or remount the filesystem read-only, or panic and halt the system.)
-.TP
-.BR noquota | quota | usrquota | grpquota
-These options are accepted but ignored.
-
-.SS "Mount options for msdos"
-See mount options for fat.
-If the
-.I msdos
-filesystem detects an inconsistency, it reports an error and sets the file
-system read-only. The filesystem can be made writable again by remounting
-it.
-
-.SS "Mount options for ncpfs"
-Just like
-.IR nfs ", the " ncpfs
-implementation expects a binary argument (a
-.IR "struct ncp_mount_data" )
-to the mount system call. This argument is constructed by
-.BR ncpmount (8)
-and the current version of
-.B mount
-(2.12) does not know anything about ncpfs.
-
-.SS "Mount options for ntfs"
-.TP
-.BI iocharset= name
-Character set to use when returning file names.
-Unlike VFAT, NTFS suppresses names that contain
-nonconvertible characters. Deprecated.
-.TP
-.BI nls= name
-New name for the option earlier called
-.IR iocharset .
-.TP
-.B utf8
-Use UTF-8 for converting file names.
-.TP
-.BR uni_xlate= { 0 | 1 | 2 }
-For 0 (or `no' or `false'), do not use escape sequences
-for unknown Unicode characters.
-For 1 (or `yes' or `true') or 2, use vfat-style 4-byte escape sequences
-starting with ":". Here 2 give a little-endian encoding
-and 1 a byteswapped bigendian encoding.
-.TP
-.B posix=[0|1]
-If enabled (posix=1), the filesystem distinguishes between
-upper and lower case. The 8.3 alias names are presented as
-hard links instead of being suppressed. This option is obsolete.
-.TP
-\fBuid=\fP\,\fIvalue\fP, \fBgid=\fP\,\fIvalue\fP and \fBumask=\fP\,\fIvalue\fP
-Set the file permission on the filesystem.
-The umask value is given in octal.
-By default, the files are owned by root and not readable by somebody else.
-
-.SS "Mount options for overlay"
-Since Linux 3.18 the overlay pseudo filesystem implements a union mount for
-other filesystems.
-
-An overlay filesystem combines two filesystems - an \fBupper\fR filesystem and
-a \fBlower\fR filesystem. When a name exists in both filesystems, the object
-in the upper filesystem is visible while the object in the lower filesystem is
-either hidden or, in the case of directories, merged with the upper object.
-
-The lower filesystem can be any filesystem supported by Linux and does not need
-to be writable. The lower filesystem can even be another overlayfs. The upper
-filesystem will normally be writable and if it is it must support the creation
-of trusted.* extended attributes, and must provide a valid d_type in readdir
-responses, so NFS is not suitable.
-
-A read-only overlay of two read-only filesystems may use any filesystem type.
-The options \fBlowerdir\fR and \fBupperdir\fR are combined into a merged
-directory by using:
-
-.RS
-.br
-.nf
-.B "mount \-t overlay overlay \e"
-.B " \-olowerdir=/lower,upperdir=/upper,workdir=/work /merged"
-.fi
-.br
-.RE
-
-.TP
-.BI lowerdir= directory
-Any filesystem, does not need to be on a writable filesystem.
-.TP
-.BI upperdir= directory
-The upperdir is normally on a writable filesystem.
-.TP
-.BI workdir= directory
-The workdir needs to be an empty directory on the same filesystem as upperdir.
-
-.SS "Mount options for reiserfs"
-Reiserfs is a journaling filesystem.
-.TP
-.B conv
-Instructs version 3.6 reiserfs software to mount a version 3.5 filesystem,
-using the 3.6 format for newly created objects. This filesystem will no
-longer be compatible with reiserfs 3.5 tools.
-.TP
-.BR hash= { rupasov | tea | r5 | detect }
-Choose which hash function reiserfs will use to find files within directories.
-.RS
-.TP
-.B 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.
-.TP
-.B tea
-A Davis-Meyer function implemented by Jeremy Fitzhardinge.
-It uses hash permuting bits in the name. It gets high randomness
-and, therefore, low probability of hash collisions at some CPU cost.
-This may be used if EHASHCOLLISION errors are experienced with the r5 hash.
-.TP
-.B r5
-A modified version of the rupasov hash. It is used by default and is
-the best choice unless the filesystem has huge directories and
-unusual file-name patterns.
-.TP
-.B detect
-Instructs
-.I mount
-to detect which hash function is in use by examining
-the filesystem being mounted, and to write this information into
-the reiserfs superblock. This is only useful on the first mount of
-an old format filesystem.
-.RE
-.TP
-.B hashed_relocation
-Tunes the block allocator. This may provide performance improvements
-in some situations.
-.TP
-.B no_unhashed_relocation
-Tunes the block allocator. This may provide performance improvements
-in some situations.
-.TP
-.B noborder
-Disable the border allocator algorithm invented by Yury Yu.\& Rupasov.
-This may provide performance improvements in some situations.
-.TP
-.B nolog
-Disable journaling. This will provide slight performance improvements in
-some situations at the cost of losing reiserfs's fast recovery from crashes.
-Even with this option turned on, reiserfs still performs all journaling
-operations, save for actual writes into its journaling area. Implementation
-of
-.I nolog
-is a work in progress.
-.TP
-.B notail
-By default, reiserfs stores small files and `file tails' directly into its
-tree. This confuses some utilities such as
-.BR LILO (8).
-This option is used to disable packing of files into the tree.
-.TP
-.B replayonly
-Replay the transactions which are in the journal, but do not actually
-mount the filesystem. Mainly used by
-.IR reiserfsck .
-.TP
-.BI resize= number
-A remount option which permits online expansion of reiserfs partitions.
-Instructs reiserfs to assume that the device has
-.I number
-blocks.
-This option is designed for use with devices which are under logical
-volume management (LVM).
-There is a special
-.I resizer
-utility which can be obtained from
-.IR ftp://ftp.namesys.com/pub/reiserfsprogs .
-.TP
-.B user_xattr
-Enable Extended User Attributes. See the
-.BR attr (1)
-manual page.
-.TP
-.B acl
-Enable POSIX Access Control Lists. See the
-.BR acl (5)
-manual page.
-.TP
-.BR barrier=none " / " barrier=flush
-This disables / enables the use of write barriers in the journaling code.
-barrier=none disables, barrier=flush enables (default). This also requires an
-IO stack which can support barriers, and if reiserfs gets an error on a barrier
-write, it will disable barriers again with a warning. Write barriers enforce
-proper on-disk ordering of journal commits, making volatile disk write caches
-safe to use, at some performance penalty. If your disks are battery-backed in
-one way or another, disabling barriers may safely improve performance.
-
-.SS "Mount options for ubifs"
-UBIFS is a flash filesystem which works on top of UBI volumes. Note that
-\fBatime\fR is not supported and is always turned off.
-.TP
-The device name may be specified as
-.PP
-.RS
-.B ubiX_Y
-UBI device number
-.BR X ,
-volume number
-.B Y
-.TP
-.B ubiY
-UBI device number
-.BR 0 ,
-volume number
-.B Y
-.TP
-.B ubiX:NAME
-UBI device number
-.BR X ,
-volume with name
-.B NAME
-.TP
-.B ubi:NAME
-UBI device number
-.BR 0 ,
-volume with name
-.B NAME
-.RE
-.PP
-Alternative
-.B !
-separator may be used instead of
-.BR : .
-.TP
-The following mount options are available:
-.TP
-.B bulk_read
-Enable bulk-read. VFS read-ahead is disabled because it slows down the filesystem. Bulk-Read is an internal optimization. Some flashes may read faster if
-the data are read at one go, rather than at several read requests. For
-example, OneNAND can do "read-while-load" if it reads more than one NAND page.
-.TP
-.B no_bulk_read
-Do not bulk-read. This is the default.
-.TP
-.B chk_data_crc
-Check data CRC-32 checksums. This is the default.
-.TP
-.BR no_chk_data_crc .
-Do not check data CRC-32 checksums. With this option, the filesystem does not
-check CRC-32 checksum for data, but it does check it for the internal indexing
-information. This option only affects reading, not writing. CRC-32 is always
-calculated when writing the data.
-.TP
-.BR compr= { none | lzo | zlib }
-Select the default compressor which is used when new files are written. It is
-still possible to read compressed files if mounted with the
-.B none
-option.
-
-.SS "Mount options for udf"
-UDF is the "Universal Disk Format" filesystem defined by OSTA, the Optical
-Storage Technology Association, and is often used for DVD-ROM, frequently
-in the form of a hybrid UDF/ISO-9660 filesystem. It is, however,
-perfectly usable by itself on disk drives, flash drives and other block devices.
-See also
-.IR iso9660 .
-.TP
-.B uid=
-Make all files in the filesystem belong to the given user.
-uid=forget can be specified independently of (or usually in
-addition to) uid=<user> and results in UDF
-not storing uids to the media. In fact the recorded uid
-is the 32-bit overflow uid \-1 as defined by the UDF standard.
-The value is given as either <user> which is a valid user name or the corresponding
-decimal user id, or the special string "forget".
-.TP
-.B gid=
-Make all files in the filesystem belong to the given group.
-gid=forget can be specified independently of (or usually in
-addition to) gid=<group> and results in UDF
-not storing gids to the media. In fact the recorded gid
-is the 32-bit overflow gid \-1 as defined by the UDF standard.
-The value is given as either <group> which is a valid group name or the corresponding
-decimal group id, or the special string "forget".
-.TP
-.B umask=
-Mask out the given permissions from all inodes read from the filesystem.
-The value is given in octal.
-.TP
-.B mode=
-If mode= is set the permissions of all non-directory inodes read from the
-filesystem will be set to the given mode. The value is given in octal.
-.TP
-.B dmode=
-If dmode= is set the permissions of all directory inodes read from the
-filesystem will be set to the given dmode. The value is given in octal.
-.TP
-.B 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.
-
-For other details see the \fBmkudffs\fP(8) 2.0+ manpage, sections
-\fBCOMPATIBILITY\fP and \fBBLOCK SIZE\fP.
-.TP
-.B unhide
-Show otherwise hidden files.
-.TP
-.B undelete
-Show deleted files in lists.
-.TP
-.B adinicb
-Embed data in the inode. (default)
-.TP
-.B noadinicb
-Don't embed data in the inode.
-.TP
-.B shortad
-Use short UDF address descriptors.
-.TP
-.B longad
-Use long UDF address descriptors. (default)
-.TP
-.B nostrict
-Unset strict conformance.
-.TP
-.B iocharset=
-Set the NLS character set. This requires kernel compiled with CONFIG_UDF_NLS option.
-.TP
-.B utf8
-Set the UTF-8 character set.
-.SS Mount options for debugging and disaster recovery
-.TP
-.B novrs
-Ignore the Volume Recognition Sequence and attempt to mount anyway.
-.TP
-.B session=
-Select the session number for multi-session recorded optical media. (default= last session)
-.TP
-.B anchor=
-Override standard anchor location. (default= 256)
-.TP
-.B lastblock=
-Set the last block of the filesystem.
-.SS Unused historical mount options that may be encountered and should be removed
-.TP
-.B uid=ignore
-Ignored, use uid=<user> instead.
-.TP
-.B gid=ignore
-Ignored, use gid=<group> instead.
-.TP
-.B volume=
-Unimplemented and ignored.
-.TP
-.B partition=
-Unimplemented and ignored.
-.TP
-.B fileset=
-Unimplemented and ignored.
-.TP
-.B rootdir=
-Unimplemented and ignored.
-
-.SS "Mount options for ufs"
-.TP
-.BI 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:
-.RS
-.TP
-.B old
-Old format of ufs, this is the default, read only.
-(Don't forget to give the \-r option.)
-.TP
-.B 44bsd
-For filesystems created by a BSD-like system (NetBSD, FreeBSD, OpenBSD).
-.TP
-.B ufs2
-Used in FreeBSD 5.x supported as read-write.
-.TP
-.B 5xbsd
-Synonym for ufs2.
-.TP
-.B sun
-For filesystems created by SunOS or Solaris on Sparc.
-.TP
-.B sunx86
-For filesystems created by Solaris on x86.
-.TP
-.B hp
-For filesystems created by HP-UX, read-only.
-.TP
-.B nextstep
-For filesystems created by NeXTStep (on NeXT station) (currently read only).
-.TP
-.B nextstep-cd
-For NextStep CDROMs (block_size == 2048), read-only.
-.TP
-.B openstep
-For filesystems created by OpenStep (currently read only).
-The same filesystem type is also used by Mac OS X.
-.RE
-
-.TP
-.BI onerror= value
-Set behavior on error:
-.RS
-.TP
-.B panic
-If an error is encountered, cause a kernel panic.
-.TP
-.RB [ lock | umount | repair ]
-These mount options don't do anything at present;
-when an error is encountered only a console message is printed.
-.RE
-
-.SS "Mount options for umsdos"
-See mount options for msdos.
-The
-.B dotsOK
-option is explicitly killed by
-.IR umsdos .
-
-.SS "Mount options for vfat"
-First of all, the mount options for
-.I fat
-are recognized.
-The
-.B dotsOK
-option is explicitly killed by
-.IR vfat .
-Furthermore, there are
-.TP
-.B uni_xlate
-Translate unhandled Unicode characters to special escaped sequences.
-This lets you backup and restore filenames that are created with any
-Unicode characters. Without this option, a '?' is used when no
-translation is possible. The escape character is ':' because it is
-otherwise invalid on the vfat filesystem. The escape sequence
-that gets used, where u is the Unicode character,
-is: ':', (u & 0x3f), ((u>>6) & 0x3f), (u>>12).
-.TP
-.B posix
-Allow two files with names that only differ in case.
-This option is obsolete.
-.TP
-.B nonumtail
-First try to make a short name without sequence number,
-before trying
-.IR name\s+3\(ti\s0num.ext .
-.TP
-.B utf8
-UTF8 is the filesystem safe 8-bit encoding of Unicode that is used by the
-console. It can be enabled for the filesystem with this option or disabled
-with utf8=0, utf8=no or utf8=false. If `uni_xlate' gets set, UTF8 gets
-disabled.
-.TP
-.BI 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 \fImode\fRs:
-.RS
-.TP
-.B lower
-Force the short name to lower case upon display; store a long name when
-the short name is not all upper case.
-.TP
-.B win95
-Force the short name to upper case upon display; store a long name when
-the short name is not all upper case.
-.TP
-.B winnt
-Display the short name as is; store a long name when the short name is
-not all lower case or all upper case.
-.TP
-.B mixed
-Display the short name as is; store a long name when the short name is not
-all upper case. This mode is the default since Linux 2.6.32.
-.RE
-
-.SS "Mount options for usbfs"
-.TP
-\fBdevuid=\fP\,\fIuid\fP and \fBdevgid=\fP\,\fIgid\fP and \fBdevmode=\fP\,\fImode\fP
-Set the owner and group and mode of the device files in the usbfs filesystem
-(default: uid=gid=0, mode=0644). The mode is given in octal.
-.TP
-\fBbusuid=\fP\,\fIuid\fP and \fBbusgid=\fP\,\fIgid\fP and \fBbusmode=\fP\,\fImode\fP
-Set the owner and group and mode of the bus directories in the usbfs
-filesystem (default: uid=gid=0, mode=0555). The mode is given in octal.
-.TP
-\fBlistuid=\fP\,\fIuid\fP and \fBlistgid=\fP\,\fIgid\fP and \fBlistmode=\fP\,\fImode\fP
-Set the owner and group and mode of the file
-.I devices
-(default: uid=gid=0, mode=0444). The mode is given in octal.
-
-.SH DM-VERITY SUPPORT (experimental)
-The device-mapper verity target provides read-only transparent integrity
-checking of block devices using kernel crypto API. The
-.B mount
-command can open
-the dm-verity device and do the integrity verification before on the device
-filesystem is mounted. Requires libcryptsetup with in libmount (optionally via dlopen).
-If libcryptsetup supports extracting the root hash of an already mounted device,
-existing devices will be automatically reused in case of a match.
-Mount options for dm-verity:
-.TP
-\fBverity.hashdevice=\fP\,\fIpath\fP
-Path to the hash tree device associated with the source volume to pass to dm-verity.
-.TP
-\fBverity.roothash=\fP\,\fIhex\fP
-Hex-encoded hash of the root of
-.I verity.hashdevice
-Mutually exclusive with
-.I verity.roothashfile.
-.TP
-\fBverity.roothashfile=\fP\,\fIpath\fP
-Path to file containing the hex-encoded hash of the root of
-.I verity.hashdevice.
-Mutually exclusive with
-.I verity.roothash.
-.TP
-\fBverity.hashoffset=\fP\,\fIoffset\fP
-If the hash tree device is embedded in the source volume,
-.I offset
-(default: 0) is used by dm-verity to get to the tree.
-.TP
-\fBverity.fecdevice=\fP\,\fIpath\fP
-Path to the Forward Error Correction (FEC) device associated with the source volume to pass to dm-verity.
-Optional. Requires kernel built with CONFIG_DM_VERITY_FEC.
-.TP
-\fBverity.fecoffset=\fP\,\fIoffset\fP
-If the FEC device is embedded in the source volume,
-.I offset
-(default: 0) is used by dm-verity to get to the FEC area. Optional.
-.TP
-\fBverity.fecroots=\fP\,\fIvalue\fP
-Parity bytes for FEC (default: 2). Optional.
-.TP
-\fBverity.roothashsig=\fP\,\fIpath\fP
-Path to pkcs7 signature of root hash hex string. Requires crypt_activate_by_signed_key() from cryptsetup and
-kernel built with CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG. For device reuse, signatures have to be either used by all
-mounts of a device or by none. Optional.
-.PP
-Supported since util-linux v2.35.
-.PP
-For example commands:
-.sp
-.RS
-.nf
-.B mksquashfs /etc /tmp/etc.squashfs
-.B dd if=/dev/zero of=/tmp/etc.hash bs=1M count=10
-.B veritysetup format /tmp/etc.squashfs /tmp/etc.hash
-.B openssl smime \-sign \-in <hash> \-nocerts \-inkey private.key \e
-.B \-signer private.crt \-noattr \-binary \-outform der \-out /tmp/etc.p7
-.B mount \-o verity.hashdevice=/tmp/etc.hash,verity.roothash=<hash>,\e
-.B verity.roothashsig=/tmp/etc.p7 /tmp/etc.squashfs /mnt
-.fi
-.RE
-.sp
-create squashfs image from /etc directory, verity hash device
-and mount verified filesystem image to /mnt.
-The kernel will verify that the root hash is signed by a key from the kernel keyring if roothashsig is used.
-
-.SH LOOP-DEVICE SUPPORT
-One further possible type is a mount via the loop device. For example,
-the command
-.RS
-.sp
-.B "mount /tmp/disk.img /mnt \-t vfat \-o loop=/dev/loop3"
-.sp
-.RE
-will set up the loop device
-.I /dev/loop3
-to correspond to the file
-.IR /tmp/disk.img ,
-and then mount this device on
-.IR /mnt .
-
-If no explicit loop device is mentioned
-(but just an option `\fB\-o loop\fP' is given), then
-.B mount
-will try to find some unused loop device and use that, for example
-.RS
-.sp
-.B "mount /tmp/disk.img /mnt \-o loop"
-.sp
-.RE
-The
-.B mount
-command
-.B automatically
-creates a loop device from a regular file if a filesystem type is
-not specified or the filesystem is known for libblkid, for example:
-.RS
-.sp
-.B "mount /tmp/disk.img /mnt"
-.sp
-.B "mount \-t ext4 /tmp/disk.img /mnt"
-.sp
-.RE
-This type of mount knows about three options, namely
-.BR loop ", " offset " and " sizelimit ,
-that are really options to
-.BR \%losetup (8).
-(These options can be used in addition to those specific
-to the filesystem type.)
-
-Since Linux 2.6.25 auto-destruction of loop devices is supported,
-meaning that any loop device allocated by
-.B mount
-will be freed by
-.B umount
-independently of
-.IR /etc/mtab .
-
-You can also free a loop device by hand, using
-.BR "losetup \-d " or " umount \-d" .
-
-Since util-linux v2.29,
-.B mount
-re-uses the loop device rather than
-initializing a new device if the same backing file is already used for some loop
-device with the same offset and sizelimit. This is necessary to avoid
-a filesystem corruption.
-
-.SH EXIT STATUS
-.B mount
-has the following exit status values (the bits can be ORed):
-.TP
-.B 0
-success
-.TP
-.B 1
-incorrect invocation or permissions
-.TP
-.B 2
-system error (out of memory, cannot fork, no more loop devices)
-.TP
-.B 4
-internal
-.B mount
-bug
-.TP
-.B 8
-user interrupt
-.TP
-.B 16
-problems writing or locking /etc/mtab
-.TP
-.B 32
-mount failure
-.TP
-.B 64
-some mount succeeded
-
-The command \fBmount \-a\fR returns 0 (all succeeded), 32 (all failed), or 64 (some
-failed, some succeeded).
-
-.SH EXTERNAL HELPERS
-The syntax of external mount helpers is:
-.sp
-.in +4
-.BI /sbin/mount. suffix
-.I spec dir
-.RB [ \-sfnv ]
-.RB [ \-N
-.IR namespace ]
-.RB [ \-o
-.IR options ]
-.RB [ \-t
-.IR type \fB. subtype ]
-.in
-.sp
-where the \fIsuffix\fR is the filesystem type and the \fB\-sfnvoN\fR options have
-the same meaning as the normal mount options. The \fB\-t\fR option is used for
-filesystems with subtypes support (for example
-.BR "/sbin/mount.fuse \-t fuse.sshfs" ).
-
-The command \fBmount\fR does not pass the mount options
-.BR unbindable ,
-.BR runbindable ,
-.BR private ,
-.BR rprivate ,
-.BR slave ,
-.BR rslave ,
-.BR shared ,
-.BR rshared ,
-.BR auto ,
-.BR noauto ,
-.BR comment ,
-.BR x-* ,
-.BR loop ,
-.B offset
-and
-.B sizelimit
-to the mount.<suffix> helpers. All other options are used in a
-comma-separated list as an argument to the \fB\-o\fR option.
-
-.SH ENVIRONMENT
-.IP LIBMOUNT_FSTAB=<path>
-overrides the default location of the
-.I fstab
-file (ignored for suid)
-.IP LIBMOUNT_MTAB=<path>
-overrides the default location of the
-.I mtab
-file (ignored for suid)
-.IP LIBMOUNT_DEBUG=all
-enables libmount debug output
-.IP LIBBLKID_DEBUG=all
-enables libblkid debug output
-.IP LOOPDEV_DEBUG=all
-enables loop device setup debug output
-.SH FILES
-See also "\fBThe files /etc/fstab, /etc/mtab and /proc/mounts\fR" section above.
-.TP 18n
-.I /etc/fstab
-filesystem table
-.TP
-.I /run/mount
-libmount private runtime directory
-.TP
-.I /etc/mtab
-table of mounted filesystems or symlink to
-.I /proc/mounts
-.TP
-.I /etc/mtab\s+3\(ti\s0
-lock file (unused on systems with
-.I mtab
-symlink)
-.TP
-.I /etc/mtab.tmp
-temporary file (unused on systems with
-.I mtab
-symlink)
-.TP
-.I /etc/filesystems
-a list of filesystem types to try
-.SH HISTORY
-A
-.B mount
-command existed in Version 5 AT&T UNIX.
-.SH BUGS
-It is possible for a corrupted filesystem to cause a crash.
-.PP
-Some Linux filesystems don't support
-.BR "\-o sync " and " \-o dirsync"
-(the ext2, ext3, ext4, fat and vfat filesystems
-.I do
-support synchronous updates (a la BSD) when mounted with the
-.B sync
-option).
-.PP
-The
-.B "\-o remount"
-may not be able to change mount parameters (all
-.IR ext2fs -specific
-parameters, except
-.BR sb ,
-are changeable with a remount, for example, but you can't change
-.B gid
-or
-.B umask
-for the
-.IR fatfs ).
-.PP
-It is possible that the files
-.I /etc/mtab
-and
-.I /proc/mounts
-don't match on systems with a regular
-.I mtab
-file. The first file is based only on
-the mount command options, but the content of the second file also depends on
-the kernel and others settings (e.g.\& on a remote NFS server -- in certain cases
-the mount command may report unreliable information about an NFS mount point
-and the
-.I /proc/mount
-file usually contains more reliable information.) This is
-another reason to replace the
-.I mtab
-file with a symlink to the
-.I /proc/mounts
-file.
-.PP
-Checking files on NFS filesystems referenced by file descriptors (i.e.\& the
-.B fcntl
-and
-.B ioctl
-families of functions) may lead to inconsistent results due to the lack of
-a consistency check in the kernel even if the
-.B noac
-mount option is used.
-.PP
-The
-.B loop
-option with the
-.B offset
-or
-.B sizelimit
-options used may fail when using older kernels if the
-.B mount
-command can't confirm that the size of the block device has been configured
-as requested. This situation can be worked around by using
-the
-.B losetup
-command manually before calling
-.B mount
-with the configured loop device.
-.SH AUTHORS
-.nf
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.na
-.BR lsblk (1),
-.BR mount (2),
-.BR umount (2),
-.BR filesystems (5),
-.BR fstab (5),
-.BR nfs (5),
-.BR xfs (5),
-.BR mount_namespaces (7)
-.BR xattr (7)
-.BR e2label (8),
-.BR findmnt (8),
-.BR losetup (8),
-.BR mke2fs (8),
-.BR mountd (8),
-.BR nfsd (8),
-.BR swapon (8),
-.BR tune2fs (8),
-.BR umount (8),
-.BR xfs_admin (8)
-.ad
-.SH AVAILABILITY
-The mount command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH MOUNTPOINT 1 "August 2019" "util-linux" "User Commands"
-.SH NAME
-mountpoint \- see if a directory or file is a mountpoint
-.SH SYNOPSIS
-.B mountpoint
-.RB [ \-d | \-q ]
-.I directory
-|
-.I file
-.sp
-.B mountpoint
-.B \-x
-.I device
-
-.SH DESCRIPTION
-.B mountpoint
-checks whether the given
-.I directory
-or
-.I file
-is mentioned in the /proc/self/mountinfo file.
-.SH OPTIONS
-.TP
-.BR \-d , " \-\-fs\-devno"
-Show the major/minor numbers of the device that is mounted on the given
-directory.
-.TP
-.BR \-q , " \-\-quiet"
-Be quiet - don't print anything.
-.TP
-.B "\-\-nofollow"
-Do not follow symbolic link if it the last element of the
-.I directory
-path.
-.TP
-.BR \-x , " \-\-devno"
-Show the major/minor numbers of the given blockdevice on standard output.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH EXIT STATUS
-Zero if the directory or file is a mountpoint, non-zero if not.
-.SH ENVIRONMENT
-.IP LIBMOUNT_DEBUG=all
-enables libmount debug output.
-.SH NOTES
-The util-linux
-.B mountpoint
-implementation was written from scratch for libmount. The original version
-for sysvinit suite was written by Miquel van Smoorenburg.
-
-.SH AUTHORS
-Karel Zak <kzak@redhat.com>
-.SH SEE ALSO
-.BR mount (8)
-.SH AVAILABILITY
-The mountpoint command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH NSENTER 1 "June 2013" "util-linux" "User Commands"
-.SH NAME
-nsenter \- run program in different namespaces
-.SH SYNOPSIS
-.B nsenter
-[options]
-.RI [ program
-.RI [ arguments ]]
-.SH DESCRIPTION
-The
-.B nsenter
-command executes
-.I program
-in the namespace(s) that are specified in the command-line options
-(described below).
-If \fIprogram\fP is not given, then ``${SHELL}'' is run (default: /bin\:/sh).
-.PP
-Enterable namespaces are:
-.TP
-.B mount namespace
-Mounting and unmounting filesystems will not affect the rest of the system,
-except for filesystems which are explicitly marked as shared (with
-\fBmount --make-\:shared\fP; see \fI/proc\:/self\:/mountinfo\fP for the
-\fBshared\fP flag).
-For further details, see
-.BR mount_namespaces (7)
-and the discussion of the
-.B CLONE_NEWNS
-flag in
-.BR clone (2).
-.TP
-.B UTS namespace
-Setting hostname or domainname will not affect the rest of the system.
-For further details, see
-.BR uts_namespaces (7).
-.TP
-.B IPC namespace
-The process will have an independent namespace for POSIX message queues
-as well as System V message queues,
-semaphore sets and shared memory segments.
-For further details, see
-.BR ipc_namespaces (7).
-.TP
-.B network namespace
-The process will have independent IPv4 and IPv6 stacks, IP routing tables,
-firewall rules, the
-.I /proc\:/net
-and
-.I /sys\:/class\:/net
-directory trees, sockets, etc.
-For further details, see
-.BR network_namespaces (7).
-.TP
-.B PID namespace
-Children will have a set of PID to process mappings separate from the
-.B nsenter
-process.
-.B nsenter
-will fork by default if changing the PID namespace, so that the new program
-and its children share the same PID namespace and are visible to each other.
-If \fB\-\-no\-fork\fP is used, the new program will be exec'ed without forking.
-For further details, see
-.BR pid_namespaces (7).
-.TP
-.B user namespace
-The process will have a distinct set of UIDs, GIDs and capabilities.
-For further details, see
-.BR user_namespaces (7).
-.TP
-.B cgroup namespace
-The process will have a virtualized view of \fI/proc\:/self\:/cgroup\fP, and new
-cgroup mounts will be rooted at the namespace cgroup root.
-For further details, see
-.BR cgroup_namespaces (7).
-.TP
-.B time namespace
-The process can have a distinct view of
-.B CLOCK_MONOTONIC
-and/or
-.B CLOCK_BOOTTIME
-which can be changed using \fI/proc/self/timens_offsets\fP.
-For further details, see
-.BR time_namespaces (7).
-.SH OPTIONS
-Various of the options below that relate to namespaces take an optional
-.I file
-argument.
-This should be one of the
-.I /proc/[pid]/ns/*
-files described in
-.BR namespaces (7),
-or the pathname of a bind mount that was created on one of those files.
-.TP
-\fB\-a\fR, \fB\-\-all\fR
-Enter all namespaces of the target process by the default
-.I /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]).
-
-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
-.BR setns (2)
-for more details.
-.TP
-\fB\-t\fR, \fB\-\-target\fR \fIpid\fP
-Specify a target process to get contexts from. The paths to the contexts
-specified by
-.I pid
-are:
-.RS
-.PD 0
-.IP "" 20
-.TP
-/proc/\fIpid\fR/ns/mnt
-the mount namespace
-.TP
-/proc/\fIpid\fR/ns/uts
-the UTS namespace
-.TP
-/proc/\fIpid\fR/ns/ipc
-the IPC namespace
-.TP
-/proc/\fIpid\fR/ns/net
-the network namespace
-.TP
-/proc/\fIpid\fR/ns/pid
-the PID namespace
-.TP
-/proc/\fIpid\fR/ns/user
-the user namespace
-.TP
-/proc/\fIpid\fR/ns/cgroup
-the cgroup namespace
-.TP
-/proc/\fIpid\fR/ns/time
-the time namespace
-.TP
-/proc/\fIpid\fR/root
-the root directory
-.TP
-/proc/\fIpid\fR/cwd
-the working directory respectively
-.PD
-.RE
-.TP
-\fB\-m\fR, \fB\-\-mount\fR[=\fIfile\fR]
-Enter the mount namespace. If no file is specified, enter the mount namespace
-of the target process.
-If
-.I file
-is specified, enter the mount namespace
-specified by
-.IR file .
-.TP
-\fB\-u\fR, \fB\-\-uts\fR[=\fIfile\fR]
-Enter the UTS namespace. If no file is specified, enter the UTS namespace of
-the target process.
-If
-.I file
-is specified, enter the UTS namespace specified by
-.IR file .
-.TP
-\fB\-i\fR, \fB\-\-ipc\fR[=\fIfile\fR]
-Enter the IPC namespace. If no file is specified, enter the IPC namespace of
-the target process.
-If
-.I file
-is specified, enter the IPC namespace specified by
-.IR file .
-.TP
-\fB\-n\fR, \fB\-\-net\fR[=\fIfile\fR]
-Enter the network namespace. If no file is specified, enter the network
-namespace of the target process.
-If
-.I file
-is specified, enter the network namespace specified by
-.IR file .
-.TP
-\fB\-p\fR, \fB\-\-pid\fR[=\fIfile\fR]
-Enter the PID namespace. If no file is specified, enter the PID namespace of
-the target process.
-If
-.I file
-is specified, enter the PID namespace specified by
-.IR file .
-.TP
-\fB\-U\fR, \fB\-\-user\fR[=\fIfile\fR]
-Enter the user namespace. If no file is specified, enter the user namespace of
-the target process.
-If
-.I file
-is specified, enter the user namespace specified by
-.IR file .
-See also the \fB\-\-setuid\fR and \fB\-\-setgid\fR options.
-.TP
-\fB\-C\fR, \fB\-\-cgroup\fR[=\fIfile\fR]
-Enter the cgroup namespace. If no file is specified, enter the cgroup namespace of
-the target process.
-If
-.I file
-is specified, enter the cgroup namespace specified by
-.IR file .
-.TP
-\fB\-T\fR, \fB\-\-time\fR[=\fIfile\fR]
-Enter the time namespace. If no file is specified, enter the time namespace of
-the target process.
-If
-.I file
-is specified, enter the time namespace specified by
-.IR file .
-.TP
-\fB\-G\fR, \fB\-\-setgid\fR \fIgid\fR
-Set the group ID which will be used in the entered namespace and drop
-supplementary groups.
-.BR nsenter (1)
-always sets GID for user namespaces, the default is 0.
-.TP
-\fB\-S\fR, \fB\-\-setuid\fR \fIuid\fR
-Set the user ID which will be used in the entered namespace.
-.BR nsenter (1)
-always sets UID for user namespaces, the default is 0.
-.TP
-\fB\-\-preserve\-credentials\fR
-Don't modify UID and GID when enter user namespace. The default is to
-drops supplementary groups and sets GID and UID to 0.
-.TP
-\fB\-r\fR, \fB\-\-root\fR[=\fIdirectory\fR]
-Set the root directory. If no directory is specified, set the root directory to
-the root directory of the target process. If directory is specified, set the
-root directory to the specified directory.
-.TP
-\fB\-w\fR, \fB\-\-wd\fR[=\fIdirectory\fR]
-Set the working directory. If no directory is specified, set the working
-directory to the working directory of the target process. If directory is
-specified, set the working directory to the specified directory.
-.TP
-\fB\-F\fR, \fB\-\-no\-fork\fR
-Do not fork before exec'ing the specified program. By default, when entering a
-PID namespace, \fBnsenter\fP calls \fBfork\fP before calling \fBexec\fP so that
-any children will also be in the newly entered PID namespace.
-.TP
-\fB\-Z\fR, \fB\-\-follow\-context\fR
-Set the SELinux security context used for executing a new process according to
-already running process specified by \fB\-\-target\fR PID. (The util-linux has
-to be compiled with SELinux support otherwise the option is unavailable.)
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.SH AUTHORS
-.UR biederm@xmission.com
-Eric Biederman
-.UE
-.br
-.UR kzak@redhat.com
-Karel Zak
-.UE
-.SH SEE ALSO
-.BR clone (2),
-.BR setns (2),
-.BR namespaces (7)
-.SH AVAILABILITY
-The nsenter command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH PIVOT_ROOT 8 "August 2011" "util-linux" "System Administration"
-.SH NAME
-pivot_root \- change the root filesystem
-.SH SYNOPSIS
-.B pivot_root
-.I new_root put_old
-.SH DESCRIPTION
-\fBpivot_root\fP moves the root file system of the current process to the
-directory \fIput_old\fP and makes \fInew_root\fP the new root file system.
-Since \fBpivot_root\fP(8) simply calls \fBpivot_root\fP(2), we refer to
-the man page of the latter for further details.
-
-Note that, depending on the implementation of \fBpivot_root\fP, root and
-cwd of the caller may or may not change. The following is a sequence for
-invoking \fBpivot_root\fP that works in either case, assuming that
-\fBpivot_root\fP and \fBchroot\fP are in the current \fBPATH\fP:
-.sp
-cd \fInew_root\fP
-.br
-pivot_root . \fIput_old\fP
-.br
-exec chroot . \fIcommand\fP
-.sp
-Note that \fBchroot\fP must be available under the old root and under the new
-root, because \fBpivot_root\fP may or may not have implicitly changed the
-root directory of the shell.
-
-Note that \fBexec chroot\fP changes the running executable, which is
-necessary if the old root directory should be unmounted afterwards.
-Also note that standard input, output, and error may still point to a
-device on the old root file system, keeping it busy. They can easily be
-changed when invoking \fBchroot\fP (see below; note the absence of
-leading slashes to make it work whether \fBpivot_root\fP has changed the
-shell's root or not).
-.SH OPTIONS
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.SH EXAMPLE
-Change the root file system to /dev/hda1 from an interactive shell:
-.sp
-.nf
-mount /dev/hda1 /new-root
-cd /new-root
-pivot_root . old-root
-exec chroot . sh <dev/console >dev/console 2>&1
-umount /old-root
-.fi
-.sp
-Mount the new root file system over NFS from 10.0.0.1:/my_root and run
-\fBinit\fP:
-.sp
-.nf
-ifconfig lo 127.0.0.1 up # for portmap
-# configure Ethernet or such
-portmap # for lockd (implicitly started by mount)
-mount \-o ro 10.0.0.1:/my_root /mnt
-killall portmap # portmap keeps old root busy
-cd /mnt
-pivot_root . old_root
-exec chroot . sh \-c 'umount /old_root; exec /sbin/init' \\
- <dev/console >dev/console 2>&1
-.fi
-.SH SEE ALSO
-.BR chroot (1),
-.BR pivot_root (2),
-.BR mount (8),
-.BR switch_root (8),
-.BR umount (8)
-.SH AVAILABILITY
-The pivot_root command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" prlimit.1 --
-.\" Copyright 2011 Davidlohr Bueso <dave@gnu.org>
-.\" May be distributed under the GNU General Public License
-
-.TH PRLIMIT 1 "July 2014" "util-linux" "User Commands"
-.SH NAME
-prlimit \- get and set process resource limits
-.SH SYNOPSIS
-.BR prlimit " [options]"
-.RB [ \-\-\fIresource\fR [ =\fIlimits\fR]
-.RB [ \-\-pid\ \fIPID\fR]
-
-.BR prlimit " [options]"
-.RB [ \-\-\fIresource\fR [ =\fIlimits\fR]
-.IR "command " [ argument ...]
-
-.SH DESCRIPTION
-Given a process ID and one or more resources, \fBprlimit\fP tries to retrieve
-and/or modify the limits.
-
-When \fIcommand\fR is given,
-.B prlimit
-will run this command with the given arguments.
-
-The \fIlimits\fP parameter is composed of a soft and a hard value, separated
-by a colon (:), in order to modify the existing values. If no \fIlimits\fR are
-given, \fBprlimit\fP will display the current values. If one of the values
-is not given, then the existing one will be used. To specify the unlimited or
-infinity limit (RLIM_INFINITY), the \-1 or 'unlimited' string can be passed.
-
-Because of the nature of limits, the soft limit must be lower or equal to the
-high limit (also called the ceiling). To see all available resource limits,
-refer to the RESOURCE OPTIONS section.
-
-.IP "\fIsoft\fP:\fIhard\fP Specify both limits."
-.IP "\fIsoft\fP: Specify only the soft limit."
-.IP ":\fIhard\fP Specify only the hard limit."
-.IP "\fIvalue\fP Specify both limits to the same value."
-
-.SH GENERAL OPTIONS
-.IP "\fB\-h, \-\-help\fP"
-Display help text and exit.
-.IP "\fB\-\-noheadings\fP"
-Do not print a header line.
-.IP "\fB\-o, \-\-output \fIlist\fP"
-Define the output columns to use. If no output arrangement is specified,
-then a default set is used.
-Use \fB\-\-help\fP to get a list of all supported columns.
-.IP "\fB\-p, \-\-pid\fP"
-Specify the process id; if none is given, the running process will be used.
-.IP "\fB\-\-raw\fP"
-Use the raw output format.
-.IP "\fB\-\-verbose\fP"
-Verbose mode.
-.IP "\fB\-V, \-\-version\fP"
-Display version information and exit.
-
-.SH RESOURCE OPTIONS
-.IP "\fB\-c, \-\-core\fP[=\fIlimits\fR]"
-Maximum size of a core file.
-.IP "\fB\-d, \-\-data\fP[=\fIlimits\fR]"
-Maximum data size.
-.IP "\fB\-e, \-\-nice\fP[=\fIlimits\fR]"
-Maximum nice priority allowed to raise.
-.IP "\fB\-f, \-\-fsize\fP[=\fIlimits\fR]"
-Maximum file size.
-.IP "\fB\-i, \-\-sigpending\fP[=\fIlimits\fR]"
-Maximum number of pending signals.
-.IP "\fB\-l, \-\-memlock\fP[=\fIlimits\fR]"
-Maximum locked-in-memory address space.
-.IP "\fB\-m, \-\-rss\fP[=\fIlimits\fR]"
-Maximum Resident Set Size (RSS).
-.IP "\fB\-n, \-\-nofile\fP[=\fIlimits\fR]"
-Maximum number of open files.
-.IP "\fB\-q, \-\-msgqueue\fP[=\fIlimits\fR]"
-Maximum number of bytes in POSIX message queues.
-.IP "\fB\-r, \-\-rtprio\fP[=\fIlimits\fR]"
-Maximum real-time priority.
-.IP "\fB\-s, \-\-stack\fP[=\fIlimits\fR]"
-Maximum size of the stack.
-.IP "\fB\-t, \-\-cpu\fP[=\fIlimits\fR]"
-CPU time, in seconds.
-.IP "\fB\-u, \-\-nproc\fP[=\fIlimits\fR]"
-Maximum number of processes.
-.IP "\fB\-v, \-\-as\fP[=\fIlimits\fR]"
-Address space limit.
-.IP "\fB\-x, \-\-locks\fP[=\fIlimits\fR]"
-Maximum number of file locks held.
-.IP "\fB\-y, \-\-rttime\fP[=\fIlimits\fR]"
-Timeout for real-time tasks.
-
-.SH NOTES
-The prlimit system call is supported since Linux 2.6.36, older kernels will
-break this program.
-
-.SH EXAMPLES
-.IP "\fBprlimit \-\-pid 13134\fP"
-Display limit values for all current resources.
-.IP "\fBprlimit \-\-pid 13134 \-\-rss \-\-nofile=1024:4095\fP"
-Display the limits of the RSS, and set the soft and hard limits for the number
-of open files to 1024 and 4095, respectively.
-.IP "\fBprlimit \-\-pid 13134 \-\-nproc=512:\fP"
-Modify only the soft limit for the number of processes.
-.IP "\fBprlimit \-\-pid $$ \-\-nproc=unlimited\fP"
-Set for the current process both the soft and ceiling values for the number of
-processes to unlimited.
-.IP "\fBprlimit \-\-cpu=10 sort \-u hugefile\fP"
-Set both the soft and hard CPU time limit to ten seconds and run 'sort'.
-
-.SH AUTHORS
-.nf
-Davidlohr Bueso <dave@gnu.org> - In memory of Dennis M. Ritchie.
-.fi
-.SH SEE ALSO
-.BR ulimit (1p),
-.BR prlimit (2)
-
-.SH AVAILABILITY
-The prlimit command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH READPROFILE "8" "October 2011" "util-linux" "System Administration"
-.SH NAME
-readprofile \- read kernel profiling information
-.SH SYNOPSIS
-.B readprofile
-[options]
-.SH VERSION
-This manpage documents version 2.0 of the program.
-.SH DESCRIPTION
-The
-.B readprofile
-command uses the
-.I /proc/profile
-information to print ascii data on standard output. The output is
-organized in three columns: the first is the number of clock ticks,
-the second is the name of the C function in the kernel where those
-many ticks occurred, and the third is the normalized `load' of the
-procedure, calculated as a ratio between the number of ticks and the
-length of the procedure. The output is filled with blanks to ease
-readability.
-.SH OPTIONS
-.TP
-\fB\-a\fR, \fB\-\-all\fR
-Print all symbols in the mapfile. By default the procedures with
-reported ticks are not printed.
-.TP
-\fB\-b\fR, \fB\-\-histbin\fR
-Print individual histogram-bin counts.
-.TP
-\fB\-i\fR, \fB\-\-info\fR
-Info. This makes
-.B readprofile
-only print the profiling step used by the kernel. The profiling step
-is the resolution of the profiling buffer, and is chosen during
-kernel configuration (through `make config'), or in the kernel's
-command line. If the
-.B \-t
-(terse) switch is used together with
-.B \-i
-only the decimal number is printed.
-.TP
-\fB\-m\fR, \fB\-\-mapfile\fR \fImapfile\fR
-Specify a mapfile, which by default is
-.IR /usr/src/linux/System.map .
-You should specify the map file on cmdline if your current kernel
-isn't the last one you compiled, or if you keep System.map elsewhere.
-If the name of the map file ends with `.gz' it is decompressed on the
-fly.
-.TP
-\fB\-M\fR, \fB\-\-multiplier\fR \fImultiplier\fR
-On some architectures it is possible to alter the frequency at which
-the kernel delivers profiling interrupts to each CPU. This option
-allows you to set the frequency, as a multiplier of the system clock
-frequency, HZ. Linux 2.6.16 dropped multiplier support for most systems.
-This option also resets the profiling buffer, and requires superuser
-privileges.
-.TP
-\fB\-p\fR, \fB\-\-profile\fR \fIpro-file\fR
-Specify a different profiling buffer, which by default is
-.IR /proc/profile .
-Using a different pro-file is useful if you want to `freeze' the
-kernel profiling at some time and read it later. The
-.I /proc/profile
-file can be copied using `cat' or `cp'. There is no more support for
-compressed profile buffers, like in
-.B readprofile-1.1,
-because the program needs to know the size of the buffer in advance.
-.TP
-\fB\-r\fR, \fB\-\-reset\fR
-Reset the profiling buffer. This can only be invoked by root,
-because
-.I /proc/profile
-is readable by everybody but writable only by the superuser.
-However, you can make
-.B readprofile
-set-user-ID 0, in order to reset the buffer without gaining privileges.
-.TP
-\fB\-s, \fB\-\-counters\fR
-Print individual counters within functions.
-.TP
-\fB\-v\fR, \fB\-\-verbose\fR
-Verbose. The output is organized in four columns and filled with
-blanks. The first column is the RAM address of a kernel function,
-the second is the name of the function, the third is the number of
-clock ticks and the last is the normalized load.
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.SH FILES
-.nf
-/proc/profile A binary snapshot of the profiling buffer.
-/usr/src/linux/System.map The symbol table for the kernel.
-/usr/src/linux/* The program being profiled :-)
-.fi
-.SH BUGS
-.B readprofile
-only works with a 1.3.x or newer kernel, because
-.I /proc/profile
-changed in the step from 1.2 to 1.3
-.LP
-This program only works with ELF kernels. The change for a.out
-kernels is trivial, and left as an exercise to the a.out user.
-.LP
-To enable profiling, the kernel must be rebooted, because no
-profiling module is available, and it wouldn't be easy to build. To
-enable profiling, you can specify "profile=2" (or another number) on
-the kernel commandline. The number you specify is the two-exponent
-used as profiling step.
-.LP
-Profiling is disabled when interrupts are inhibited. This means that
-many profiling ticks happen when interrupts are re-enabled. Watch
-out for misleading information.
-.SH EXAMPLE
-Browse the profiling buffer ordering by clock ticks:
-.nf
- readprofile | sort \-nr | less
-
-.fi
-Print the 20 most loaded procedures:
-.nf
- readprofile | sort \-nr +2 | head \-20
-
-.fi
-Print only filesystem profile:
-.nf
- readprofile | grep _ext2
-
-.fi
-Look at all the kernel information, with ram addresses:
-.nf
- readprofile \-av | less
-
-.fi
-Browse a `frozen' profile buffer for a non current kernel:
-.nf
- readprofile \-p \(ti/profile.freeze \-m /zImage.map.gz
-
-.fi
-Request profiling at 2kHz per CPU, and reset the profiling buffer:
-.nf
- sudo readprofile \-M 20
-.fi
-.SH AVAILABILITY
-The readprofile command is part of the util-linux package and is
-available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright (c) 1983, 1991, 1993
-.\" The Regents of the University of California. All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)renice.8 8.1 (Berkeley) 6/9/93
-.\"
-.TH RENICE "1" "July 2014" "util-linux" "User Commands"
-.SH NAME
-renice \- alter priority of running processes
-.SH SYNOPSIS
-.B renice
-.RB [ \-n ]
-.I priority
-.RB [ \-g | \-p | \-u ]
-.IR identifier ...
-.SH DESCRIPTION
-.B renice
-alters the scheduling priority of one or more running processes. The
-first argument is the \fIpriority\fR value to be used.
-The other arguments are interpreted as process IDs (by default),
-process group IDs, user IDs, or user names.
-.BR renice 'ing
-a process group causes all processes in the process group to have their
-scheduling priority altered.
-.BR renice 'ing
-a user causes all processes owned by the user to have their scheduling
-priority altered.
-.SH OPTIONS
-.TP
-.BR \-n , " \-\-priority " \fIpriority\fR
-Specify the scheduling
-.I priority
-to be used for the process, process group, or user. Use of the option
-.BR \-n " or " \-\-priority
-is optional, but when used it must be the first argument.
-.TP
-.BR \-g ", " \-\-pgrp
-Interpret the succeeding arguments as process group IDs.
-.TP
-.BR \-p ", " \-\-pid
-Interpret the succeeding arguments as process IDs
-(the default).
-.TP
-.BR \-u ", " \-\-user
-Interpret the succeeding arguments as usernames or UIDs.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH FILES
-.TP
-.I /etc/passwd
-to map user names to user IDs
-.SH NOTES
-Users other than the superuser may only alter the priority of processes they
-own. Furthermore, an unprivileged user can only
-.I increase
-the ``nice value'' (i.e., choose a lower priority)
-and such changes are irreversible unless (since Linux 2.6.12)
-the user has a suitable ``nice'' resource limit (see
-.BR ulimit (1p)
-and
-.BR getrlimit (2)).
-
-The superuser may alter the priority of any process and set the priority to any
-value in the range \-20 to 19.
-Useful priorities are: 19 (the affected processes will run only when nothing
-else in the system wants to), 0 (the ``base'' scheduling priority), anything
-negative (to make things go very fast).
-.SH HISTORY
-The
-.B renice
-command appeared in 4.0BSD.
-.SH EXAMPLES
-The following command would change the priority of the processes with
-PIDs 987 and 32, plus all processes owned by the users daemon and root:
-.TP
-.B " renice" +1 987 \-u daemon root \-p 32
-.SH SEE ALSO
-.BR nice (1),
-.BR chrt (1),
-.BR getpriority (2),
-.BR setpriority (2),
-.BR credentials (7),
-.BR sched (7)
-.SH AVAILABILITY
-The renice command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" -*- nroff -*-
-.TH RFKILL "8" "2017-07-06" "util-linux" "System Administration"
-.SH NAME
-rfkill \- tool for enabling and disabling wireless devices
-.SH SYNOPSIS
-.B rfkill
-.RI [ options ]
-.RI [ command ]
-.RI [ id|type \ ...]
-
-.SH DESCRIPTION
-.B rfkill
-lists, enabling and disabling wireless devices.
-
-The command "list" output format is deprecated and maintained for backward
-compatibility only. The new output format is the default when no command is
-specified or when the option \fB\-\-output\fR is used.
-
-The default output is subject to change. So whenever possible, you should
-avoid using default outputs in your scripts. Always explicitly define expected
-columns by using the \fB\-\-output\fR option together with a columns list in
-environments where a stable output is required.
-
-
-.SH OPTIONS
-.TP
-\fB\-J\fR, \fB\-\-json\fR
-Use JSON output format.
-.TP
-\fB\-n\fR, \fB\-\-noheadings\fR
-Do not print a header line.
-.TP
-\fB\-o\fR, \fB\-\-output\fR
-Specify which output columns to print. Use \-\-help to get a list of
-available columns.
-.TP
-.B \-\-output\-all
-Output all available columns.
-.TP
-\fB\-r\fR, \fB\-\-raw\fR
-Use the raw output format.
-.TP
-.B \-\-help
-Display help text and exit.
-.TP
-.B \-\-version
-Display version information and exit.
-.SH COMMANDS
-.TP
-.B help
-Display help text and exit.
-.TP
-.B event
-Listen for rfkill events and display them on stdout.
-.TP
-\fBlist \fR[\fIid\fR|\fItype\fR ...]
-List the current state of all available devices. The command output format is deprecated, see the section DESCRIPTION.
-It is a good idea to check with
-.B list
-command
-.IR id " or " type
-scope is appropriate before setting
-.BR block " or " unblock .
-Special
-.I all
-type string will match everything. Use of multiple
-.IR id " or " type
-arguments is supported.
-.TP
-\fBblock \fBid\fR|\fBtype\fR [...]
-Disable the corresponding device.
-.TP
-\fBunblock \fBid\fR|\fBtype\fR [...]
-Enable the corresponding device. If the device is hard\-blocked, for example
-via a hardware switch, it will remain unavailable though it is now
-soft\-unblocked.
-.SH EXAMPLE
-rfkill --output ID,TYPE
-.br
-rfkill block all
-.br
-rfkill unblock wlan
-.br
-rfkill block bluetooth uwb wimax wwan gps fm nfc
-.SH AUTHORS
-.B rfkill
-was originally written by
-.MT johannes@\:sipsolutions.\:net
-Johannes Berg
-.ME
-and
-.MT marcel@\:holtmann.\:org
-Marcel Holtmann
-.ME .
-The code has been later modified by
-.MT kerolasa@\:iki.\:fi
-Sami Kerola
-.ME
-and
-.MT kzak@\:redhat.\:com
-Karel Zak
-.ME
-for util-linux project.
-.PP
-This manual page was written by
-.MT linux@\:youmustbejoking.\:demon.\:co.uk
-Darren Salt
-.ME ,
-for the Debian project (and may be used by others).
-.SH SEE ALSO
-.BR powertop (8),
-.BR systemd-rfkill (8),
-.UR https://\:git.\:kernel.\:org/\:pub/\:scm/\:linux/\:kernel/\:git/\:torvalds/\:linux.git/\:tree/\:Documentation/\:driver-api/\:rfkill.rst
-Linux kernel documentation
-.UE
-.SH AVAILABILITY
-The rfkill command is part of the util\-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util\-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright (c) 2007, SUSE LINUX Products GmbH
-.\" Bernhard Walle <bwalle@suse.de>
-.\"
-.\" This program is free software; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public License
-.\" as published by the Free Software Foundation; either version 2
-.\" of the License, or (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
-.\" 02110-1301, USA.
-.\"
-.TH RTCWAKE 8 "June 2015" "util-linux" "System Administration"
-.SH NAME
-rtcwake \- enter a system sleep state until specified wakeup time
-.SH SYNOPSIS
-.B rtcwake
-[options]
-.RB [ \-d
-.IR device ]
-.RB [ \-m
-.IR standby_mode ]
-.RB { "\-s \fIseconds\fP" | "\-t \fItime_t\fP" }
-.SH DESCRIPTION
-This program is used to enter a system sleep state and to automatically
-wake from it at a specified time.
-.PP
-This uses cross-platform Linux interfaces to enter a system sleep state, and
-leave it no later than a specified time. It uses any RTC framework driver that
-supports standard driver model wakeup flags.
-.PP
-This is normally used like the old \fBapmsleep\fP utility, to wake from a suspend
-state like ACPI S1 (standby) or S3 (suspend-to-RAM). Most platforms can
-implement those without analogues of BIOS, APM, or ACPI.
-.PP
-On some systems, this can also be used like \fBnvram-wakeup\fP, waking from states
-like ACPI S4 (suspend to disk). Not all systems have persistent media that are
-appropriate for such suspend modes.
-.PP
-Note that alarm functionality depends on hardware; not every RTC is able to setup
-an alarm up to 24 hours in the future.
-.PP
-The suspend setup may be interrupted by active hardware; for example wireless USB
-input devices that continue to send events for some fraction of a second after the
-return key is pressed.
-.B rtcwake
-tries to avoid this problem and it waits to terminal to settle down before
-entering a system sleep.
-
-.SH OPTIONS
-.TP
-.BR \-A , " \-\-adjfile " \fIfile
-Specify an alternative path to the adjust file.
-.TP
-.BR \-a , " \-\-auto"
-Read the clock mode (whether the hardware clock is set to UTC or local time)
-from the \fIadjtime\fP file, where
-.BR hwclock (8)
-stores that information. This is the default.
-.TP
-.BR \-\-date " \fItimestamp"
-Set the wakeup time to the value of the timestamp. Format of the
-timestamp can be any of the following:
-.TS
-tab(|);
-l2 l.
-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
-.TE
-.TP
-.BR \-d , " \-\-device " \fIdevice
-Use the specified \fIdevice\fP instead of \fBrtc0\fP as realtime clock.
-This option is only relevant if your system has more than one RTC.
-You may specify \fBrtc1\fP, \fBrtc2\fP, ... here.
-.TP
-.BR \-l , " \-\-local"
-Assume that the hardware clock is set to local time, regardless of the
-contents of the \fIadjtime\fP file.
-.TP
-.B \-\-list\-modes
-List available \-\-mode option arguments.
-.TP
-.BR \-m , " \-\-mode " \fImode
-Go into the given standby state. Valid values for \fImode\fP are:
-.RS
-.TP
-.B standby
-ACPI state S1. This state offers minimal, though real, power savings, while
-providing a very low-latency transition back to a working system. This is the
-default mode.
-.TP
-.B freeze
-The processes are frozen, all the devices are suspended and all the processors
-idled. This state is a general state that does not need any platform-specific
-support, but it saves less power than Suspend-to-RAM, because the system is
-still in a running state. (Available since Linux 3.9.)
-.TP
-.B mem
-ACPI state S3 (Suspend-to-RAM). This state offers significant power savings as
-everything in the system is put into a low-power state, except for memory,
-which is placed in self-refresh mode to retain its contents.
-.TP
-.B disk
-ACPI state S4 (Suspend-to-disk). This state offers the greatest power savings,
-and can be used even in the absence of low-level platform support for power
-management. This state operates similarly to Suspend-to-RAM, but includes a
-final step of writing memory contents to disk.
-.TP
-.B off
-ACPI state S5 (Poweroff). This is done by calling '/sbin/shutdown'.
-Not officially supported by ACPI, but it usually works.
-.TP
-.B no
-Don't suspend, only set the RTC wakeup time.
-.TP
-.B on
-Don't suspend, but read the RTC device until an alarm time appears.
-This mode is useful for debugging.
-.TP
-.B disable
-Disable a previously set alarm.
-.TP
-.B show
-Print alarm information in format: "alarm: off|on <time>".
-The time is in ctime() output format, e.g., "alarm: on Tue Nov 16 04:48:45 2010".
-.RE
-.TP
-.BR \-n , " \-\-dry-run"
-This option does everything apart from actually setting up the alarm,
-suspending the system, or waiting for the alarm.
-.TP
-.BR \-s , " \-\-seconds " \fIseconds
-Set the wakeup time to \fIseconds\fP in the future from now.
-.TP
-.BR \-t , " \-\-time " \fItime_t
-Set the wakeup time to the absolute time \fItime_t\fP. \fItime_t\fP
-is the time in seconds since 1970-01-01, 00:00 UTC. Use the
-.BR date (1)
-tool to convert between human-readable time and \fItime_t\fP.
-.TP
-.BR \-u , " \-\-utc"
-Assume that the hardware clock is set to UTC (Universal Time Coordinated),
-regardless of the contents of the \fIadjtime\fP file.
-.TP
-.BR \-v , " \-\-verbose"
-Be verbose.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH NOTES
-Some PC systems can't currently exit sleep states such as \fBmem\fP
-using only the kernel code accessed by this driver.
-They need help from userspace code to make the framebuffer work again.
-.SH FILES
-.I @ADJTIME_PATH@
-.SH HISTORY
-The program was posted several times on LKML and other lists
-before appearing in kernel commit message for Linux 2.6 in the GIT
-commit 87ac84f42a7a580d0dd72ae31d6a5eb4bfe04c6d.
-.SH AUTHORS
-The program was written by David Brownell <dbrownell@users.sourceforge.net>
-and improved by Bernhard Walle <bwalle@suse.de>.
-.SH COPYRIGHT
-This is free software. You may redistribute copies of it under the terms
-of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
-There is NO WARRANTY, to the extent permitted by law.
-.SH "SEE ALSO"
-.BR hwclock (8),
-.BR date (1)
-.SH AVAILABILITY
-The rtcwake command is part of the util-linux package and is available from the
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH SETARCH 8 "December 2017" "util-linux" "System Administration"
-.SH NAME
-setarch \- change reported architecture in new program environment and/or set personality flags
-.SH SYNOPSIS
-.B setarch
-.RI [ arch ]
-[options]
-.RI [ program
-.RI [ argument ...]]
-.sp
-.B setarch
-.BR \-\-list | \-h | \-V
-.sp
-.B arch
-[options]
-.RI [ program
-.RI [ argument ...]]
-.SH DESCRIPTION
-.B setarch
-modifies execution domains and process personality flags.
-.PP
-The execution domains currently only affects the output of \fBuname \-m\fR.
-For example, on an AMD64 system, running \fBsetarch i386 \fIprogram\fR
-will cause \fIprogram\fR to see i686 instead of x86_64 as the machine type.
-It can also be used to set various personality options.
-The default \fIprogram\fR is \fB/bin/sh\fR.
-.PP
-Since version 2.33 the
-.I arch
-command line argument is optional and
-.B setarch
-may be used to change personality flags (ADDR_LIMIT_*, SHORT_INODE, etc) without
-modification of the execution domain.
-.SH OPTIONS
-.TP
-.B \-\-list
-List the architectures that \fBsetarch\fR knows about. Whether \fBsetarch\fR
-can actually set each of these architectures depends on the running kernel.
-.TP
-.B \-\-uname\-2.6
-Causes the \fIprogram\fR to see a kernel version number beginning with 2.6.
-Turns on UNAME26.
-.TP
-.BR \-v , " \-\-verbose"
-Be verbose.
-.TP
-\fB\-3\fR, \fB\-\-3gb\fR
-Specifies
-.I program
-should use a maximum of 3GB of address space. Supported on x86. Turns on
-ADDR_LIMIT_3GB.
-.TP
-\fB\-\-4gb\fR
-This option has no effect. It is retained for backward compatibility only,
-and may be removed in future releases.
-.TP
-\fB\-B\fR, \fB\-\-32bit\fR
-Limit the address space to 32 bits to emulate hardware. Supported on ARM
-and Alpha. Turns on ADDR_LIMIT_32BIT.
-.TP
-\fB\-F\fR, \fB\-\-fdpic\-funcptrs\fR
-Treat user-space function pointers to signal handlers as pointers to address
-descriptors. This option has no effect on architectures that do not support
-FDPIC ELF binaries. In kernel v4.14 support is limited to ARM, Blackfin,
-Fujitsu FR-V, and SuperH CPU architectures.
-.TP
-\fB\-I\fR, \fB\-\-short\-inode\fR
-Obsolete bug emulation flag. Turns on SHORT_INODE.
-.TP
-\fB\-L\fR, \fB\-\-addr\-compat\-layout\fR
-Provide legacy virtual address space layout. Use when the
-.I program
-binary does not have PT_GNU_STACK ELF header. Turns on
-ADDR_COMPAT_LAYOUT.
-.TP
-\fB\-R\fR, \fB\-\-addr\-no\-randomize\fR
-Disables randomization of the virtual address space. Turns on
-ADDR_NO_RANDOMIZE.
-.TP
-\fB\-S\fR, \fB\-\-whole\-seconds\fR
-Obsolete bug emulation flag. Turns on WHOLE_SECONDS.
-.TP
-\fB\-T\fR, \fB\-\-sticky\-timeouts\fR
-This makes
-.BR select (2),
-.BR pselect (2),
-and
-.BR ppoll (2)
-system calls preserve the timeout value instead of modifying it to reflect
-the amount of time not slept when interrupted by a signal handler. Use when
-.I program
-depends on this behavior. For more details see the timeout description in
-.BR select (2)
-manual page. Turns on STICKY_TIMEOUTS.
-.TP
-\fB\-X\fR, \fB\-\-read\-implies\-exec\fR
-If this is set then
-.BR mmap (3p)
-PROT_READ will also add the PROT_EXEC bit - as expected by legacy x86
-binaries. Notice that the ELF loader will automatically set this bit when
-it encounters a legacy binary. Turns on READ_IMPLIES_EXEC.
-.TP
-\fB\-Z\fR, \fB\-\-mmap\-page\-zero\fR
-SVr4 bug emulation that will set
-.BR mmap (3p)
-page zero as read-only. Use when
-.I program
-depends on this behavior, and the source code is not available to be fixed.
-Turns on MMAP_PAGE_ZERO.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH EXAMPLE
-setarch \-\-addr-no-randomize mytestprog
-.br
-setarch ppc32 rpmbuild \-\-target=ppc \-\-rebuild foo.src.rpm
-.br
-setarch ppc32 \-v \-vL3 rpmbuild \-\-target=ppc \-\-rebuild bar.src.rpm
-.br
-setarch ppc32 \-\-32bit rpmbuild \-\-target=ppc \-\-rebuild foo.src.rpm
-.SH AUTHORS
-.MT sopwith@redhat.com
-Elliot Lee
-.ME
-.br
-.MT jnovy@redhat.com
-Jindrich Novy
-.ME
-.br
-.MT kzak@redhat.com
-Karel Zak
-.ME
-.SH SEE ALSO
-.BR personality (2),
-.BR select (2)
-.SH AVAILABILITY
-The setarch command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH SETPRIV 1 "July 2014" "util-linux" "User Commands"
-.SH NAME
-setpriv \- run a program with different Linux privilege settings
-.SH SYNOPSIS
-.B setpriv
-[options]
-.I program
-.RI [ arguments ]
-.SH DESCRIPTION
-Sets or queries various Linux privilege settings that are inherited across
-.BR execve (2).
-.PP
-In comparison to
-.BR su (1)
-and
-.BR runuser (1),
-.B setpriv
-neither uses PAM, nor does it prompt for a password.
-It is a simple, non-set-user-ID wrapper around
-.BR execve (2),
-and can be used to drop privileges in the same way as
-.BR setuidgid (8)
-from
-.BR daemontools ,
-.BR chpst (8)
-from
-.BR runit ,
-or similar tools shipped by other service managers.
-.SH OPTIONS
-.TP
-.B \-\-clear\-groups
-Clear supplementary groups.
-.TP
-.BR \-d , " \-\-dump"
-Dump the current privilege state.
-This option can be specified more than once to show extra,
-mostly useless, information. Incompatible with all other options.
-.TP
-.B \-\-groups \fIgroup\fR...
-Set supplementary groups. The argument is a comma-separated list of GIDs or names.
-.TP
-.BR \-\-inh\-caps " (" + | \- ) \fIcap "... or " \-\-ambient-caps " (" + | \- ) \fIcap "... or " \-\-bounding\-set " (" + | \- ) \fIcap ...
-Set the inheritable capabilities, ambient capabilities or the capability bounding set. See
-.BR capabilities (7).
-The argument is a comma-separated list of
-.BI + cap
-and
-.BI \- cap
-entries, which add or remove an entry respectively. \fIcap\fR can either be a
-human-readable name as seen in
-.BR capabilities (7)
-without the \fIcap_\fR prefix or of the format
-.BR cap_N ,
-where \fIN\fR is the internal capability index used by Linux.
-.B +all
-and
-.B \-all
-can be used to add or remove all caps.
-.IP
-The set of capabilities starts out as
-the current inheritable set for
-.BR \-\-inh\-caps ,
-the current ambient set for
-.B \-\-ambient\-caps
-and the current bounding set for
-.BR \-\-bounding\-set .
-.IP
-Note the following restrictions (detailed in
-.BR capabilities (7))
-regarding modifications to these capability sets:
-.RS
-.IP * 2
-A capability can be added to the inheritable set only if it is
-currently present in the bounding set.
-.IP *
-A capability can be added to the ambient set only if it is currently
-present in both the permitted and inheritable sets.
-.IP *
-Notwithstanding the syntax offered by
-.BR setpriv ,
-the kernel does not permit capabilities to be added to the bounding set.
-.RE
-.IP
-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.
-.TP
-.B \-\-keep\-groups
-Preserve supplementary groups. Only useful in conjunction with
-.BR \-\-rgid ,
-.BR \-\-egid ", or"
-.BR \-\-regid .
-.TP
-.B \-\-init\-groups
-Initialize supplementary groups using
-.BR initgroups "(3)."
-Only useful in conjunction with
-.B \-\-ruid
-or
-.BR \-\-reuid .
-.TP
-.B \-\-list\-caps
-List all known capabilities. This option must be specified alone.
-.TP
-.B \-\-no\-new\-privs
-Set the
-.I no_new_privs
-bit. With this bit set,
-.BR 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
-.BR prctl (2)
-and
-.I Documentation/\:prctl/\:no_\:new_\:privs.txt
-in the Linux kernel source.
-.sp
-The
-.I no_new_privs
-bit is supported since Linux 3.5.
-.TP
-.BI \-\-rgid " gid\fR, " \-\-egid " gid\fR, " \-\-regid " gid"
-Set the real, effective, or both GIDs. The \fIgid\fR argument can be
-given as a textual group name.
-.sp
-For safety, you must specify one of
-.BR \-\-clear\-groups ,
-.BR \-\-groups ,
-.BR \-\-keep\-groups ", or"
-.B \-\-init\-groups
-if you set any primary
-.IR gid .
-.TP
-.BI \-\-ruid " uid\fR, " \-\-euid " uid\fR, " \-\-reuid " uid"
-Set the real, effective, or both UIDs. The \fIuid\fR argument can be
-given as a textual login name.
-.sp
-Setting a
-.I uid
-or
-.I 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:
-.sp
-.B " setpriv \-\-reuid=1000 \-\-regid=1000 \-\-inh\-caps=\-all"
-.TP
-.BR \-\-securebits " (" + | \- ) \fIsecurebit ...
-Set or clear securebits. The argument is a comma-separated list.
-The valid securebits are
-.IR noroot ,
-.IR noroot_locked ,
-.IR no_setuid_fixup ,
-.IR no_setuid_fixup_locked ,
-and
-.IR keep_caps_locked .
-.I keep_caps
-is cleared by
-.BR execve (2)
-and is therefore not allowed.
-.TP
-.BR "\-\-pdeathsig keep" | clear | <signal>
-Keep, clear or set the parent death signal. Some LSMs, most notably SELinux and
-AppArmor, clear the signal when the process' credentials change. Using
-\fB\-\-pdeathsig keep\fR will restore the parent death signal after changing
-credentials to remedy that situation.
-.TP
-.BI \-\-selinux\-label " label"
-Request a particular SELinux transition (using a transition on exec, not
-dyntrans). This will fail and cause
-.B setpriv
-to abort if SELinux is not in use, and the transition may be ignored or cause
-.BR execve (2)
-to fail at SELinux's whim. (In particular, this is unlikely to work in
-conjunction with
-.IR no_new_privs .)
-This is similar to
-.BR runcon (1).
-.TP
-.BI \-\-apparmor\-profile " profile"
-Request a particular AppArmor profile (using a transition on exec). This will
-fail and cause
-.B setpriv
-to abort if AppArmor is not in use, and the transition may be ignored or cause
-.BR execve (2)
-to fail at AppArmor's whim.
-.TP
-.B \-\-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 \fI/usr/local/bin:/bin:/usr/bin\fR for a regular user and to
-\fI/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin\fR for root.
-.sp
-The environment variable PATH may be different on systems where
-.I /bin
-and
-.I /sbin
-are merged into
-.IR /usr .
-The environment variable SHELL defaults to \fI/bin/sh\fR if none is given in the user's
-passwd entry.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH NOTES
-If applying any specified option fails,
-.I program
-will not be run and
-.B setpriv
-will return with exit status 127.
-.PP
-Be careful with this tool \-\- it may have unexpected security consequences.
-For example, setting
-.I no_new_privs
-and then execing a program that is
-SELinux\-confined (as this tool would do) may prevent the SELinux
-restrictions from taking effect.
-.SH EXAMPLES
-If you're looking for behaviour similar to
-.BR su (1)/ runuser "(1), or " sudo (8)
-(without the
-.B \-g
-option), try something like:
-.sp
-.B " setpriv \-\-reuid=1000 \-\-regid=1000 \-\-init\-groups"
-.PP
-If you want to mimic daemontools'
-.BR setuid (8),
-try:
-.sp
-.B " setpriv \-\-reuid=1000 \-\-regid=1000 \-\-clear\-groups"
-.SH AUTHORS
-.MT luto@amacapital.net
-Andy Lutomirski
-.ME
-.SH SEE ALSO
-.BR runuser (1),
-.BR su (1),
-.BR prctl (2),
-.BR capabilities (7)
-.SH AVAILABILITY
-The
-.B setpriv
-command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Rick Sladkey <jrs@world.std.com>
-.\" In the public domain.
-.TH SETSID 1 "July 2014" "util-linux" "User Commands"
-.SH NAME
-setsid \- run a program in a new session
-.SH SYNOPSIS
-.B setsid
-[options]
-.I program
-.RI [ arguments ]
-.SH DESCRIPTION
-.B setsid
-runs a program in a new session. The command calls
-.BR fork (2)
-if already a process group leader. Otherwise, it executes a program in the
-current process. This default behavior is possible to override by
-the \fB\-\-fork\fR option.
-.SH OPTIONS
-.TP
-.BR \-c , " \-\-ctty"
-Set the controlling terminal to the current one.
-.TP
-.BR \-f , " \-\-fork"
-Always create a new process.
-.TP
-.BR \-w , " \-\-wait"
-Wait for the execution of the program to end, and return the exit status of
-this program as the exit status of
-.BR setsid .
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH AUTHORS
-Rick Sladkey <jrs@world.std.com>
-.SH SEE ALSO
-.BR setsid (2)
-.SH AVAILABILITY
-The setsid command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright (c) 1980, 1991 Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)swapon.8 6.3 (Berkeley) 3/16/91
-.\"
-.TH SWAPON 8 "October 2014" "util-linux" "System Administration"
-.SH NAME
-swapon, swapoff \- enable/disable devices and files for paging and swapping
-.SH SYNOPSIS
-.B swapon
-[options]
-.RI [ specialfile ...]
-.br
-.B swapoff
-.RB [ \-va ]
-.RI [ specialfile ...]
-.SH DESCRIPTION
-.B swapon
-is used to specify devices on which paging and swapping are to take place.
-
-The device or file used is given by the
-.I specialfile
-parameter. It may be of the form
-.BI \-L " label"
-or
-.BI \-U " uuid"
-to indicate a device by label or uuid.
-
-Calls to
-.B swapon
-normally occur in the system boot scripts making all swap devices available, so
-that the paging and swapping activity is interleaved across several devices and
-files.
-
-.B swapoff
-disables swapping on the specified devices and files.
-When the
-.B \-a
-flag is given, swapping is disabled on all known swap devices and files
-(as found in
-.I /proc/swaps
-or
-.IR /etc/fstab ).
-
-.SH OPTIONS
-.TP
-.BR \-a , " \-\-all"
-All devices marked as ``swap'' in
-.I /etc/fstab
-are made available, except for those with the ``noauto'' option.
-Devices that are already being used as swap are silently skipped.
-.TP
-.BR \-d , " \-\-discard" [ =\fIpolicy\fR]
-Enable swap discards, if the swap backing device supports the discard or
-trim operation. This may improve performance on some Solid State Devices,
-but often it does not. The option allows one to select between two
-available swap discard policies:
-.B \-\-discard=once
-to perform a single-time discard operation for the whole swap area at swapon;
-or
-.B \-\-discard=pages
-to asynchronously discard freed swap pages before they are available for reuse.
-If no policy is selected, the default behavior is to enable both discard types.
-The
-.I /etc/fstab
-mount options
-.BR discard ,
-.BR discard=once ,
-or
-.B discard=pages
-may also be used to enable discard flags.
-.TP
-.BR \-e , " \-\-ifexists"
-Silently skip devices that do not exist.
-The
-.I /etc/fstab
-mount option
-.B nofail
-may also be used to skip non-existing device.
-
-.TP
-.BR \-f , " \-\-fixpgsz"
-Reinitialize (exec mkswap) the swap space if its page size does not
-match that of the current running kernel.
-.BR mkswap (8)
-initializes the whole device and does not check for bad blocks.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.TP
-.BI \-L " label"
-Use the partition that has the specified
-.IR label .
-(For this, access to
-.I /proc/partitions
-is needed.)
-.TP
-.BR \-o , " \-\-options " \fIopts\fP
-Specify swap options by an fstab-compatible comma-separated string.
-For example:
-.RS
-.RS
-.sp
-.B "swapon \-o pri=1,discard=pages,nofail /dev/sda2"
-.sp
-.RE
-The \fIopts\fP string is evaluated last and overrides all other
-command line options.
-.RE
-.TP
-.BR \-p , " \-\-priority " \fIpriority\fP
-Specify the priority of the swap device.
-.I priority
-is a value between \-1 and 32767. Higher numbers indicate
-higher priority. See
-.BR swapon (2)
-for a full description of swap priorities. Add
-.BI pri= value
-to the option field of
-.I /etc/fstab
-for use with
-.BR "swapon \-a" .
-When no priority is defined, it defaults to \-1.
-.TP
-.BR \-s , " \-\-summary"
-Display swap usage summary by device. Equivalent to "cat /proc/swaps".
-This output format is DEPRECATED in favour
-of \fB\-\-show\fR that provides better control on output data.
-.TP
-.BR \-\-show [ =\fIcolumn\fR ...]
-Display a definable table of swap areas. See the
-.B \-\-help
-output for a list of available columns.
-.TP
-.B \-\-output\-all
-Output all available columns.
-.TP
-.B \-\-noheadings
-Do not print headings when displaying
-.B \-\-show
-output.
-.TP
-.B \-\-raw
-Display
-.B \-\-show
-output without aligning table columns.
-.TP
-.B \-\-bytes
-Display swap size in bytes in
-.B \-\-show
-output instead of in user-friendly units.
-.TP
-.BI \-U " uuid"
-Use the partition that has the specified
-.IR uuid .
-.TP
-.BR \-v , " \-\-verbose"
-Be verbose.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.SH EXIT STATUS
-.B swapoff
-has the following exit status values since v2.36:
-.TP
-.B 0
-success
-.TP
-.B 2
-system has insufficient memory to stop swapping (OOM)
-.TP
-.B 4
-swapoff syscall failed for another reason
-.TP
-.B 8
-non-swapoff syscall system error (out of memory, ...)
-.TP
-.B 16
-usage or syntax error
-.TP
-.B 32
-all swapoff failed on \fB\-\-all\fR
-.TP
-.B 64
-some swapoff succeeded on \fB\-\-all\fR
-
-The command \fBswapoff \-\-all\fR returns 0 (all succeeded), 32 (all failed), or 64 (some
-failed, some succeeded).
-
-The old versions before v2.36 has no documented exit status, 0 means success in all versions.
-
-.SH ENVIRONMENT
-.IP LIBMOUNT_DEBUG=all
-enables libmount debug output.
-.IP LIBBLKID_DEBUG=all
-enables libblkid debug output.
-
-.SH FILES
-.I /dev/sd??
-standard paging devices
-.br
-.I /etc/fstab
-ascii filesystem description table
-.SH NOTES
-.SS Files with holes
-The swap file implementation in the kernel expects to be able to write to the
-file directly, without the assistance of the filesystem. This is a problem on
-files with holes or on copy-on-write files on filesystems like Btrfs.
-.sp
-Commands like
-.BR cp (1)
-or
-.BR truncate (1)
-create files with holes. These files will be rejected by swapon.
-.sp
-Preallocated files created by
-.BR fallocate (1)
-may be interpreted as files with holes too depending of the filesystem.
-Preallocated swap files are supported on XFS since Linux 4.18.
-.sp
-The most portable solution to create a swap file is to use
-.BR dd (1)
-and /dev/zero.
-.SS Btrfs
-Swap files on Btrfs are supported since Linux 5.0 on files with nocow attribute.
-See the
-.BR btrfs (5)
-manual page for more details.
-.SS NFS
-Swap over \fBNFS\fR may not work.
-.SS Suspend
-.B swapon
-automatically detects and rewrites a swap space signature with old software
-suspend data (e.g., S1SUSPEND, S2SUSPEND, ...). The problem is that if we don't
-do it, then we get data corruption the next time an attempt at unsuspending is
-made.
-.SH HISTORY
-The
-.B swapon
-command appeared in 4.0BSD.
-.SH SEE ALSO
-.BR swapoff (2),
-.BR swapon (2),
-.BR fstab (5),
-.BR init (8),
-.BR fallocate (1),
-.BR mkswap (8),
-.BR mount (8),
-.BR rc (8)
-.SH AVAILABILITY
-The swapon command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Karel Zak <kzak@redhat.com>
-.TH SWITCH_ROOT 8 "June 2009" "util-linux" "System Administration"
-.SH NAME
-switch_root \- switch to another filesystem as the root of the mount tree
-.SH SYNOPSIS
-.B switch_root
-.RB [ \-hV ]
-.LP
-.B switch_root
-.I newroot
-.I init
-.RI [ arg ...]
-.SH DESCRIPTION
-.B switch_root
-moves already mounted /proc, /dev, /sys and /run to
-.I newroot
-and makes
-.I newroot
-the new root filesystem and starts
-.I init
-process.
-
-.B WARNING: switch_root removes recursively all files and directories on the current root filesystem.
-
-.SH OPTIONS
-.IP "\fB\-h, \-\-help\fP"
-Display help text and exit.
-.IP "\fB\-V, \-\-version\fP"
-Display version information and exit.
-
-.SH EXIT STATUS
-.B switch_root
-returns 0 on success and 1 on failure.
-
-.SH NOTES
-switch_root will fail to function if
-.B newroot
-is not the root of a mount. If you want to switch root into a directory that
-does not meet this requirement then you can first use a bind-mounting trick to
-turn any directory into a mount point:
-.sp
-.nf
-.RS
-mount --bind $DIR $DIR
-.RE
-.fi
-
-.SH AUTHORS
-.nf
-Peter Jones <pjones@redhat.com>
-Jeremy Katz <katzj@redhat.com>
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.BR chroot (2),
-.BR init (8),
-.BR mkinitrd (8),
-.BR mount (8)
-.SH AVAILABILITY
-The switch_root command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright (C) 1992-1997 Michael K. Johnson <johnsonm@redhat.com>
-.\" Copyright (C) 1998 Andrea Arcangeli <andrea@e-mind.com>
-.\" It may be distributed under the terms of the GNU General Public License,
-.\" version 2, or any higher version. See section COPYING of the GNU General
-.\" Public license for conditions under which this file may be redistributed.
-.\"
-.TH TUNELP 8 "October 2011" "util-linux" "System Administration"
-.SH NAME
-tunelp \- set various parameters for the lp device
-.SH SYNOPSIS
-.B tunelp
-[options]
-.I device
-.SH DESCRIPTION
-\fBtunelp\fP sets several parameters for the /dev/lp\fI?\fP devices, for
-better performance (or for any performance at all, if your printer won't work
-without it...) Without parameters, it tells whether the device is using
-interrupts, and if so, which one. With parameters, it sets the device
-characteristics accordingly.
-.SH OPTIONS
-.TP
-\fB\-i\fR, \fB\-\-irq\fR \fIargument\fR
-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
-.B 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.
-.IP
-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
-.IR /proc/parport/*/irq .
-Read
-.I /usr/src/linux/Documentation/admin-guide/parport.rst
-for more details on parport.
-.TP
-\fB\-t\fR, \fB\-\-time\fR \fImilliseconds\fR
-is the amount of time in jiffies that the driver waits if the printer doesn't
-take a character for the number of tries dictated by the \-c parameter. 10
-is the default value. If you want fastest possible printing, and don't care
-about system load, you may set this to 0. If you don't care how fast your
-printer goes, or are printing text on a slow printer with a buffer, then 500
-(5 seconds) should be fine, and will give you very low system load. This
-value generally should be lower for printing graphics than text, by a factor
-of approximately 10, for best performance.
-.TP
-\fB\-c\fR, \fB\-\-chars\fR \fIcharacters\fR
-is the number of times to try to output a character to the printer before
-sleeping for \-t \fITIME\fP. 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 \fImust\fP 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 \fIreally\fP old printer, you can increase this further.
-.IP
-Setting \-t \fITIME\fP to 0 is equivalent to setting \-c \fICHARS\fP to
-infinity.
-.TP
-\fB\-w\fR, \fB\-\-wait\fR \fImilliseconds\fR
-is the number of usec we wait while playing with the strobe signal. While
-most printers appear to be able to deal with an extremely short strobe, some
-printers demand a longer one. Increasing this from the default 1 may make it
-possible to print with those printers. This may also make it possible to use
-longer cables. It's also possible to decrease this value to 0 if your
-printer is fast enough or your machine is slow enough.
-.TP
-\fB\-a\fR, \fB\-\-abort\fR \fI<on|off>\fR
-This is whether to abort on printer error - the default is not to. If you
-are sitting at your computer, you probably want to be able to see an error
-and fix it, and have the printer go on printing. On the other hand, if you
-aren't, you might rather that your printer spooler find out that the printer
-isn't ready, quit trying, and send you mail about it. The choice is yours.
-.TP
-\fB\-o\fR, \fB\-\-check\-status\fR \fI<on|off>\fR
-This option is much like \-a. It makes any
-.BR open (2)
-of this device check to see that the device is on-line and not reporting any
-out of paper or other errors. This is the correct setting for most versions
-of lpd.
-.TP
-\fB\-C\fR, \fB\-\-careful\fR \fI<on|off>\fR
-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.
-.IP
-NOTE: This option is obsolete because it's the default in 2.1.131 kernel or
-later.
-.TP
-\fB\-s\fR, \fB\-\-status\fR
-This option returns the current printer status, both as a decimal number from
-0..255, and as a list of active flags. When this option is specified, \-q
-off, turning off the display of the current IRQ, is implied.
-.TP
-\fB\-r\fR, \fB\-\-reset\fR
-This option resets the port. It requires a Linux kernel version of 1.1.80 or
-later.
-.TP
-\fB\-q\fR, \fB\-\-print\-irq\fR \fI<on|off>\fR
-This option sets printing the display of the current IRQ setting.
-.SH FILES
-.I /dev/lp?
-.br
-.I /proc/parport/*/*
-.SH NOTES
-.BR \-o ,
-.BR \-C ,
-and
-.B \-s
-all require a Linux kernel version of 1.1.76 or later.
-.PP
-.B \-C
-requires a Linux version prior to 2.1.131.
-.SH AVAILABILITY
-The tunelp command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright (c) 1996 Andries Brouwer
-.\" This page is somewhat derived from a page that was
-.\" (c) 1980, 1989, 1991 The Regents of the University of California
-.\" and had been heavily modified by Rik Faith and myself.
-.\"
-.\" This is free documentation; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public License as
-.\" published by the Free Software Foundation; either version 2 of
-.\" the License, or (at your option) any later version.
-.\"
-.\" The GNU General Public License's references to "object code"
-.\" and "executables" are to be interpreted as the output of any
-.\" document formatting or typesetting system, including
-.\" intermediate and printed output.
-.\"
-.\" This manual is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License along
-.\" with this program; if not, write to the Free Software Foundation, Inc.,
-.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-.\"
-.TH UMOUNT 8 "July 2014" "util-linux" "System Administration"
-.SH NAME
-umount \- unmount filesystems
-.SH SYNOPSIS
-.B umount \-a
-.RB [ \-dflnrv ]
-.RB [ \-t
-.IR fstype ]
-.RB [ \-O
-.IR option ...]
-.sp
-.B umount
-.RB [ \-dflnrv ]
-.RI { directory | device }...
-.sp
-.B umount
-.BR \-h | \-V
-
-.SH DESCRIPTION
-The
-.B umount
-command detaches the mentioned filesystem(s) from the file hierarchy. A
-filesystem is specified by giving the directory where it has been
-mounted. Giving the special device on which the filesystem lives may
-also work, but is obsolete, mainly because it will fail in case this
-device was mounted on more than one directory.
-.PP
-Note that a filesystem cannot be unmounted when it is 'busy' - for
-example, when there are open files on it, or when some process has its
-working directory there, or when a swap file on it is in use. The
-offending process could even be
-.B umount
-itself - it opens libc, and libc in its turn may open for example locale
-files. A lazy unmount avoids this problem, but it may introduce other
-issues. See \fB\-\-lazy\fR description below.
-.SH OPTIONS
-.TP
-.BR \-a , " \-\-all"
-All of the filesystems described in
-.I /proc/self/mountinfo
-(or in deprecated
-.IR /etc/mtab )
-are unmounted, except the proc, devfs, devpts, sysfs, rpc_pipefs and nfsd
-filesystems. This list of the filesystems may be replaced by \fB\-\-types\fR
-umount option.
-.TP
-.BR \-A , " \-\-all\-targets"
-Unmount all mountpoints in the current mount namespace
-for the specified filesystem.
-The filesystem can be specified by one of the mountpoints or the device name (or
-UUID, etc.). When this option is used together with \fB\-\-recursive\fR, then
-all nested mounts within the filesystem are recursively unmounted.
-This option is only supported on systems where
-.I /etc/mtab
-is a symlink
-to
-.IR /proc/mounts .
-.TP
-.BR \-c , " \-\-no\-canonicalize"
-Do not canonicalize paths. The paths canonicalization is based on
-.BR stat (2)
-and
-.BR 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.
-
-This option is silently ignored by
-.B umount
-for non-root users.
-
-For more details about this option see the
-.BR mount (8)
-man page. Note that \fBumount\fR does not pass this option to the
-.BI /sbin/umount. type
-helpers.
-.TP
-.BR \-d , " \-\-detach\-loop"
-When the unmounted device was a loop device, also free this loop
-device. This option is unnecessary for devices initialized by
-.BR mount (8),
-in this case "autoclear" functionality is enabled by default.
-.TP
-.B \-\-fake
-Causes everything to be done except for the actual system call or umount helper
-execution; this 'fakes' unmounting the filesystem. It can be used to remove
-entries from the deprecated
-.I /etc/mtab
-that were unmounted earlier with the
-.B \-n
-option.
-.TP
-.BR \-f , " \-\-force"
-Force an unmount (in case of an unreachable NFS system).
-
-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.
-.TP
-.BR \-i , " \-\-internal\-only"
-Do not call the \fB/sbin/umount.\fIfilesystem\fR helper even if it exists.
-By default such a helper program is called if it exists.
-.TP
-.BR \-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.
-
-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 \fBumount \-l\fR 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.
-
-.TP
-.BR \-N , " \-\-namespace " \fIns
-Perform umount in the mount namespace specified by \fIns\fR.
-\fIns\fR is either PID of process running in that namespace
-or special file representing that namespace.
-.sp
-.BR umount (8)
-switches to the namespace when it reads
-.IR /etc/fstab ,
-writes
-.I /etc/mtab
-(or writes to
-.IR /run/mount )
-and calls
-.BR 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
-.BR umount (2)
-command.
-.sp
-See \fBmount_namespaces\fR(7) for more information.
-.TP
-.BR \-n , " \-\-no\-mtab"
-Unmount without writing in
-.IR /etc/mtab .
-.TP
-.BR \-O , " \-\-test\-opts " \fIoption\fR...
-Unmount only the filesystems that have the specified option set in
-.IR /etc/fstab .
-More than one option may be specified in a comma-separated list.
-Each option can be prefixed with
-.B no
-to indicate that no action should be taken for this option.
-.TP
-.BR \-q , " \-\-quiet"
-Suppress "not mounted" error messages.
-.TP
-.BR \-R , " \-\-recursive"
-Recursively unmount each specified directory. Recursion for each directory will
-stop if any unmount operation in the chain fails for any reason. The relationship
-between mountpoints is determined by
-.I /proc/self/mountinfo
-entries. The filesystem
-must be specified by mountpoint path; a recursive unmount by device name (or UUID)
-is unsupported.
-.TP
-.BR \-r , " \-\-read\-only"
-When an unmount fails, try to remount the filesystem read-only.
-.TP
-.BR \-t , " \-\-types " \fItype\fR...
-Indicate that the actions should only be taken on filesystems of the
-specified
-.IR type .
-More than one type may be specified in a comma-separated list. The list
-of filesystem types can be prefixed with
-.B no
-to indicate that no action should be taken for all of the mentioned types.
-Note that
-.B umount
-reads information about mounted filesystems from kernel (/proc/mounts) and
-filesystem names may be different than filesystem names used in the
-.I /etc/fstab
-(e.g., "nfs4" vs. "nfs").
-.TP
-.BR \-v , " \-\-verbose"
-Verbose mode.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH NON-SUPERUSER UMOUNTS
-Normally, only the superuser can umount filesystems.
-However, when
-.I fstab
-contains the
-.B user
-option on a line, anybody can umount the corresponding filesystem. For more details see
-.BR mount (8)
-man page.
-.PP
-Since version 2.34 the \fBumount\fR command can be used to
-perform umount operation also
-for fuse filesystems if kernel mount table contains user's ID. In this case fstab
-user= mount option is not required.
-.PP
-Since version 2.35 \fBumount\fR command does not exit when user permissions are
-inadequate by internal libmount security rules. It drops suid permissions
-and continue as regular non-root user.
-This can be used to support use-cases where
-root permissions are not necessary (e.g., fuse filesystems, user namespaces,
-etc).
-.SH LOOP DEVICE
-The
-.B umount
-command will automatically detach loop device previously initialized by
-.BR mount (8)
-command independently of
-.IR /etc/mtab .
-
-In this case the device is initialized with "autoclear" flag (see
-.BR losetup (8)
-output for more details), otherwise it's necessary to use the option \fB \-\-detach\-loop\fR
-or call \fBlosetup \-d <device>\fR. The autoclear feature is supported since Linux 2.6.25.
-.SH EXTERNAL HELPERS
-The syntax of external unmount helpers is:
-.PP
-.RS
-.BI umount. suffix
-.RI { directory | device }
-.RB [ \-flnrv ]
-.RB [ \-N
-.IR namespace ]
-.RB [ \-t
-.IR type . subtype ]
-.RE
-.PP
-where \fIsuffix\fR is the filesystem type (or the value from a
-\fBuhelper=\fR or \fBhelper=\fR marker in the mtab file).
-The \fB\-t\fR option can be used for filesystems that
-have subtype support. For example:
-.PP
-.RS
-.B umount.fuse \-t fuse.sshfs
-.RE
-.PP
-A \fBuhelper=\fIsomething\fR marker (unprivileged helper) can appear in
-the \fI/etc/mtab\fR file when ordinary users need to be able to unmount
-a mountpoint that is not defined in \fI/etc/fstab\fR
-(for example for a device that was mounted by \fBudisks\fR(1)).
-.PP
-A \fBhelper=\fItype\fR marker in the mtab file will redirect
-all unmount requests
-to the \fB/sbin/umount.\fItype\fR helper independently of UID.
-.PP
-Note that \fI/etc/mtab\fR is currently deprecated and helper= and other
-userspace mount options are maintained by libmount.
-.SH ENVIRONMENT
-.IP LIBMOUNT_FSTAB=<path>
-overrides the default location of the fstab file (ignored for suid)
-.IP LIBMOUNT_MTAB=<path>
-overrides the default location of the mtab file (ignored for suid)
-.IP LIBMOUNT_DEBUG=all
-enables libmount debug output
-.SH FILES
-.TP
-.I /etc/mtab
-table of mounted filesystems (deprecated and usually replaced by
-symlink to
-.IR /proc/mounts )
-.TP
-.I /etc/fstab
-table of known filesystems
-.TP
-.I /proc/self/mountinfo
-table of mounted filesystems generated by kernel.
-.SH HISTORY
-A
-.B umount
-command appeared in Version 6 AT&T UNIX.
-.SH SEE ALSO
-.BR umount (2),
-.BR losetup (8),
-.BR mount_namespaces (7)
-.BR mount (8)
-.SH AVAILABILITY
-The umount command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH UNSHARE 1 "February 2016" "util-linux" "User Commands"
-.SH NAME
-unshare \- run program in new namespaces
-.SH SYNOPSIS
-.B unshare
-[options]
-.RI [ program
-.RI [ arguments ]]
-.SH DESCRIPTION
-The
-.B unshare
-command creates new namespaces
-(as specified by the command-line options described below)
-and then executes the specified \fIprogram\fR.
-If \fIprogram\fR is not given, then ``${SHELL}'' is
-run (default: /bin/sh).
-.PP
-By default, a new namespace persists only as long as it has member processes.
-A new namespace can be made persistent even when it has no member processes
-by bind mounting
-/proc/\fIpid\fR/ns/\fItype\fR files to a filesystem path.
-A namespace that has been made persistent in this way can subsequently
-be entered with
-.BR \%nsenter (1)
-even after the \fIprogram\fR terminates (except PID namespaces where
-a permanently running init process is required).
-Once a persistent \%namespace is no longer needed,
-it can be unpersisted by using
-.BR umount (8)
-to remove the bind mount.
-See the \fBEXAMPLES\fR section for more details.
-.PP
-.B unshare
-since util-linux version 2.36 uses /\fIproc/[pid]/ns/pid_for_children\fP and \fI/proc/[pid]/ns/time_for_children\fP
-files for persistent PID and TIME namespaces. This change requires Linux kernel 4.17 or newer.
-.PP
-The following types of namespaces can be created with
-.BR unshare :
-.TP
-.B mount namespace
-Mounting and unmounting filesystems will not affect the rest of the system,
-except for filesystems which are explicitly marked as
-shared (with \fBmount \-\-make-shared\fP; see \fI/proc/self/mountinfo\fP or
-\fBfindmnt \-o+PROPAGATION\fP for the \fBshared\fP flags).
-For further details, see
-.BR mount_namespaces (7).
-.IP
-.B unshare
-since util-linux version 2.27 automatically sets propagation to \fBprivate\fP
-in a new mount namespace to make sure that the new namespace is really
-unshared. It's possible to disable this feature with option
-\fB\-\-propagation unchanged\fP.
-Note that \fBprivate\fP is the kernel default.
-.TP
-.B UTS namespace
-Setting hostname or domainname will not affect the rest of the system.
-For further details, see
-.BR uts_namespaces (7).
-.TP
-.B IPC namespace
-The process will have an independent namespace for POSIX message queues
-as well as System V \%message queues,
-semaphore sets and shared memory segments.
-For further details, see
-.BR ipc_namespaces (7).
-.TP
-.B network namespace
-The process will have independent IPv4 and IPv6 stacks, IP routing tables,
-firewall rules, the \fI/proc/net\fP and \fI/sys/class/net\fP directory trees,
-sockets, etc.
-For further details, see
-.BR network_namespaces (7).
-.TP
-.B PID namespace
-Children will have a distinct set of PID-to-process mappings from their parent.
-For further details, see
-.BR pid_namespaces (7).
-.TP
-.B cgroup namespace
-The process will have a virtualized view of \fI/proc\:/self\:/cgroup\fP, and new
-cgroup mounts will be rooted at the namespace cgroup root.
-For further details, see
-.BR cgroup_namespaces (7).
-.TP
-.B user namespace
-The process will have a distinct set of UIDs, GIDs and capabilities.
-For further details, see
-.BR user_namespaces (7).
-.TP
-.B time namespace
-The process can have a distinct view of
-.B CLOCK_MONOTONIC
-and/or
-.B CLOCK_BOOTTIME
-which can be changed using \fI/proc/self/timens_offsets\fP.
-For further details, see
-.BR time_namespaces (7).
-.SH OPTIONS
-.TP
-.BR \-i , " \-\-ipc" [ =\fIfile ]
-Unshare the IPC namespace. If \fIfile\fP is specified, then a persistent
-namespace is created by a bind mount.
-.TP
-.BR \-m , " \-\-mount" [ =\fIfile ]
-Unshare the mount namespace. If \fIfile\fP is specified, then a persistent
-namespace is created by a bind mount.
-Note that \fIfile\fP must be located on a mount whose propagation type
-is not \fBshared\fP (or an error results).
-Use the command \fBfindmnt \-o+PROPAGATION\fP
-when not sure about the current setting. See also the examples below.
-.TP
-.BR \-n , " \-\-net" [ =\fIfile ]
-Unshare the network namespace. If \fIfile\fP is specified, then a persistent
-namespace is created by a bind mount.
-.TP
-.BR \-p , " \-\-pid" [ =\fIfile ]
-Unshare the PID namespace. If \fIfile\fP is specified, then a persistent
-namespace is created by a bind mount.
-(Creation of a persistent PID namespace will fail if the
-.B \-\-fork
-option is not also specified.)
-.IP
-See also the \fB\-\-fork\fP and
-\fB\-\-mount-proc\fP options.
-.TP
-.BR \-u , " \-\-uts" [ =\fIfile ]
-Unshare the UTS namespace. If \fIfile\fP is specified, then a persistent
-namespace is created by a bind mount.
-.TP
-.BR \-U , " \-\-user" [ =\fIfile ]
-Unshare the user namespace. If \fIfile\fP is specified, then a persistent
-namespace is created by a bind mount.
-.TP
-.BR \-C , " \-\-cgroup" [ =\fIfile ]
-Unshare the cgroup namespace. If \fIfile\fP is specified then persistent namespace is created
-by bind mount.
-.TP
-.BR \-T , " \-\-time" [ =\fIfile ]
-Unshare the time namespace. If \fIfile\fP is specified then a persistent
-namespace is created by a bind mount. The \fB\-\-monotonic\fP and
-\fB\-\-boottime\fP options can be used to specify the corresponding
-offset in the time namespace.
-.TP
-.BR \-f , " \-\-fork"
-Fork the specified \fIprogram\fR as a child process of \fBunshare\fR rather
-than running it directly. This is useful when creating a new PID namespace.
-Note that when \fBunshare\fR is waiting for the child process,
-then it ignores SIGINT and SIGTERM and does not forward any signals to the
-child. It is necessary to send signals to the child process.
-.TP
-.B \-\-keep\-caps
-When the \fB\-\-user\fP option is given, ensure that capabilities granted
-in the user namespace are preserved in the child process.
-.TP
-.BR \-\-kill\-child [ =\fIsigname ]
-When \fBunshare\fR terminates, have \fIsigname\fP be sent to the forked child process.
-Combined with \fB\-\-pid\fR this allows for an easy and reliable killing of the entire
-process tree below \fBunshare\fR.
-If not given, \fIsigname\fP defaults to \fBSIGKILL\fR.
-This option implies \fB\-\-fork\fR.
-.TP
-.BR \-\-mount\-proc [ =\fImountpoint ]
-Just before running the program, mount the proc filesystem at \fImountpoint\fP
-(default is /proc). This is useful when creating a new PID namespace. It also
-implies creating a new mount namespace since the /proc mount would otherwise
-mess up existing programs on the system. The new proc filesystem is explicitly
-mounted as private (with MS_PRIVATE|MS_REC).
-.TP
-.BI \-\-map\-user= uid|name
-Run the program only after the current effective user ID has been mapped to \fIuid\fP.
-If this option is specified multiple times, the last occurrence takes precedence.
-This option implies \fB\-\-user\fR.
-.TP
-.BI \-\-map\-group= gid|name
-Run the program only after the current effective group ID has been mapped to \fIgid\fP.
-If this option is specified multiple times, the last occurrence takes precedence.
-This option implies \fB\-\-setgroups=deny\fR and \fB\-\-user\fR.
-.TP
-.BR \-r , " \-\-map\-root\-user"
-Run the program only after the current effective user and group IDs have been mapped to
-the superuser UID and GID in the newly created user namespace. This makes it possible to
-conveniently gain capabilities needed to manage various aspects of the newly created
-namespaces (such as configuring interfaces in the network namespace or mounting filesystems in
-the mount namespace) even when run unprivileged. As a mere convenience feature, it does not support
-more sophisticated use cases, such as mapping multiple ranges of UIDs and GIDs.
-This option implies \fB\-\-setgroups=deny\fR and \fB\-\-user\fR.
-This option is equivalent to \fB\-\-map-user=0 \-\-map-group=0\fR.
-.TP
-.BR \-c , " \-\-map\-current\-user"
-Run the program only after the current effective user and group IDs have been mapped to
-the same UID and GID in the newly created user namespace. This option implies
-\fB\-\-setgroups=deny\fR and \fB\-\-user\fR.
-This option is equivalent to \fB\-\-map-user=$(id -ru) \-\-map-group=$(id -rg)\fR.
-.TP
-.BR "\-\-propagation private" | shared | slave | unchanged
-Recursively set the mount propagation flag in the new mount namespace. The default
-is to set the propagation to \fIprivate\fP. It is possible to disable this feature
-with the argument \fBunchanged\fR. The option is silently ignored when the mount
-namespace (\fB\-\-mount\fP) is not requested.
-.TP
-.BR "\-\-setgroups allow" | deny
-Allow or deny the
-.BR setgroups (2)
-system call in a user namespace.
-.sp
-To be able to call
-.BR 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
-.BR \%setgroups (2)
-only after the GID map (\fB/proc/\fIpid\fB/gid_map\fR) has been set.
-The GID map is writable by root when
-.BR \%setgroups (2)
-is enabled (i.e., \fBallow\fR, the default), and
-the GID map becomes writable by unprivileged processes when
-.BR \%setgroups (2)
-is permanently disabled (with \fBdeny\fR).
-.TP
-.BR \-R , " \-\-root=\fIdir"
-run the command with root directory set to \fIdir\fP.
-.TP
-.BR \-w , " \-\-wd=\fIdir"
-change working directory to \fIdir\fP.
-.TP
-.BR \-S , " \-\-setuid \fIuid"
-Set the user ID which will be used in the entered namespace.
-.TP
-.BR \-G , " \-\-setgid \fIgid"
-Set the group ID which will be used in the entered namespace and drop
-supplementary groups.
-.TP
-.BI \-\-monotonic " offset"
-Set the offset of
-.B CLOCK_MONOTONIC
-which will be used in the entered time namespace. This option requires
-unsharing a time namespace with \fB\-\-time\fP.
-.TP
-.BI \-\-boottime " offset"
-Set the offset of
-.B CLOCK_BOOTTIME
-which will be used in the entered time namespace. This option requires
-unsharing a time namespace with \fB\-\-time\fP.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH NOTES
-The proc and sysfs filesystems mounting as root in a user namespace have to be
-restricted so that a less privileged user can not get more access to sensitive
-files that a more privileged user made unavailable. In short the rule for proc
-and sysfs is as close to a bind mount as possible.
-.SH EXAMPLES
-The following command creates a PID namespace, using
-.B \-\-fork
-to ensure that the executed command is performed in a child process
-that (being the first process in the namespace) has PID 1.
-The
-.B \-\-mount-proc
-option ensures that a new mount namespace is also simultaneously created
-and that a new
-.BR proc (5)
-filesystem is mounted that contains information corresponding to the new
-PID namespace.
-When the
-.B readlink
-command terminates, the new namespaces are automatically torn down.
-.PP
-.in +4n
-.EX
-.B # unshare \-\-fork \-\-pid \-\-mount-proc readlink /proc/self
-1
-.EE
-.in
-.PP
-As an unprivileged user, create a new user namespace where the user's
-credentials are mapped to the root IDs inside the namespace:
-.PP
-.in +4n
-.EX
-.B $ id \-u; id \-g
-1000
-1000
-.B $ unshare \-\-user \-\-map-root-user \e
-.B " sh \-c \(aqwhoami; cat /proc/self/uid_map /proc/self/gid_map\(aq"
-root
- 0 1000 1
- 0 1000 1
-.EE
-.in
-.PP
-The first of the following commands creates a new persistent UTS namespace
-and modifies the hostname as seen in that namespace.
-The namespace is then entered with
-.BR nsenter (1)
-in order to display the modified hostname;
-this step demonstrates that the UTS namespace continues to exist
-even though the namespace had no member processes after the
-.B unshare
-command terminated.
-The namespace is then destroyed by removing the bind mount.
-.PP
-.in +4n
-.EX
-.B # touch /root/uts-ns
-.B # unshare \-\-uts=/root/uts-ns hostname FOO
-.B # nsenter \-\-uts=/root/uts-ns hostname
-FOO
-.B # umount /root/uts-ns
-.EE
-.in
-.PP
-The following commands
-establish a persistent mount namespace referenced by the bind mount
-.IR /root/namespaces/mnt .
-In order to ensure that the creation of that bind mount succeeds,
-the parent directory
-.RI ( /root/namespaces )
-is made a bind mount whose propagation type is not
-.BR shared .
-.PP
-.in +4n
-.EX
-.B # mount \-\-bind /root/namespaces /root/namespaces
-.B # mount \-\-make-private /root/namespaces
-.B # touch /root/namespaces/mnt
-.B # unshare \-\-mount=/root/namespaces/mnt
-.EE
-.in
-.PP
-The following commands demonstrate the use of the
-.B \-\-kill-child
-option when creating a PID namespace, in order to ensure that when
-.B unshare
-is killed, all of the processes within the PID namespace are killed.
-.PP
-.in +4n
-.EX
-.BR "# set +m " "# Don't print job status messages"
-.B # unshare \-\-pid \-\-fork \-\-mount\-proc \-\-kill\-child \-\- \e
-.B " bash \-\-norc \-c \(aq(sleep 555 &) && (ps a &) && sleep 999\(aq &"
-[1] 53456
-# PID TTY STAT TIME COMMAND
- 1 pts/3 S+ 0:00 sleep 999
- 3 pts/3 S+ 0:00 sleep 555
- 5 pts/3 R+ 0:00 ps a
-
-.BR "# ps h \-o 'comm' $! " "# Show that background job is unshare(1)"
-unshare
-.BR "# kill $! " "# Kill unshare(1)"
-.B # pidof sleep
-.EE
-.in
-.PP
-The
-.B pidof
-command prints no output, because the
-.B sleep
-processes have been killed.
-More precisely, when the
-.B sleep
-process that has PID 1 in the namespace (i.e., the namespace's init process)
-was killed, this caused all other processes in the namespace to be killed.
-By contrast, a similar series of commands where the
-.B \-\-kill\-child
-option is not used shows that when
-.B unshare
-terminates, the processes in the PID namespace are not killed:
-.PP
-.in +4n
-.EX
-.B # unshare \-\-pid \-\-fork \-\-mount\-proc \-\- \e
-.B " bash \-\-norc \-c \(aq(sleep 555 &) && (ps a &) && sleep 999\(aq &"
-[1] 53479
-# PID TTY STAT TIME COMMAND
- 1 pts/3 S+ 0:00 sleep 999
- 3 pts/3 S+ 0:00 sleep 555
- 5 pts/3 R+ 0:00 ps a
-
-.B # kill $!
-.B # pidof sleep
-53482 53480
-.EE
-.in
-.PP
-The following example demonstrates the creation of a time namespace
-where the boottime clock is set to a point several years in the past:
-.PP
-.in +4n
-.EX
-.BR "# uptime \-p " "# Show uptime in initial time namespace"
-up 21 hours, 30 minutes
-.B # unshare \-\-time \-\-fork \-\-boottime 300000000 uptime \-p
-up 9 years, 28 weeks, 1 day, 2 hours, 50 minutes
-.EE
-.in
-.SH AUTHORS
-.UR dottedmag@dottedmag.net
-Mikhail Gusarov
-.UE
-.br
-.UR kzak@redhat.com
-Karel Zak
-.UE
-.SH SEE ALSO
-.BR clone (2),
-.BR unshare (2),
-.BR namespaces (7),
-.BR mount (8)
-.SH AVAILABILITY
-The unshare command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" wdctl.8 --
-.\" Copyright (C) 2012 Karel Zak <kzak@redhat.com>
-.\" May be distributed under the GNU General Public License
-.TH WDCTL "8" "July 2014" "util-linux" "System Administration"
-.SH NAME
-wdctl \- show hardware watchdog status
-.SH SYNOPSIS
-.B wdctl
-[options]
-.RI [ device ...]
-.SH DESCRIPTION
-Show hardware watchdog status. The default device is
-.IR /dev/watchdog .
-If more than one device is specified then the output is separated by
-one blank line.
-.PP
-If the device is already used or user has no permissions to read from the device, then
-.B wdctl
-reads data from sysfs. In this case information about supported features (flags) might be missing.
-.PP
-Note that the number of supported watchdog features is hardware specific.
-.SH OPTIONS
-.TP
-.BR \-f , " \-\-flags " \fIlist
-Print only the specified flags.
-.TP
-.BR \-F , " \-\-noflags"
-Do not print information about flags.
-.TP
-.BR \-I , " \-\-noident"
-Do not print watchdog identity information.
-.TP
-.BR \-n , " \-\-noheadings"
-Do not print a header line for flags table.
-.IP "\fB\-o\fR, \fB\-\-output \fIlist\fP"
-Define the output columns to use in table of watchdog flags. If no
-output arrangement is specified, then a default set is used. Use
-.B \-\-help
-to get list of all supported columns.
-.TP
-.BR \-O , " \-\-oneline"
-Print all wanted information on one line in key="value" output format.
-.TP
-.BR \-r , " \-\-raw"
-Use the raw output format.
-.TP
-.BR \-s , " \-settimeout " \fIseconds
-Set the watchdog timeout in seconds.
-.TP
-.BR \-T , " \-\-notimeouts"
-Do not print watchdog timeouts.
-.IP "\fB\-x\fR, \fB\-\-flags\-only\fP"
-Same as \fB\-I \-T\fP.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH AUTHORS
-.MT kzak@\:redhat\:.com
-Karel Zak
-.ME
-.br
-.MT lennart@\:poettering\:.net
-Lennart Poettering
-.ME
-.SH AVAILABILITY
-The
-.B wdctl
-command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH ZRAMCTL 8 "July 2014" "util-linux" "System Administration"
-.SH NAME
-zramctl \- set up and control zram devices
-.SH SYNOPSIS
-.ad l
-Get info:
-.sp
-.in +5
-.BR zramctl " [options]"
-.sp
-.in -5
-Reset zram:
-.sp
-.in +5
-.B "zramctl \-r"
-.IR zramdev ...
-.sp
-.in -5
-Print name of first unused zram device:
-.sp
-.in +5
-.B "zramctl \-f"
-.sp
-.in -5
-Set up a zram device:
-.sp
-.in +5
-.B zramctl
-.RB [ \-f " | "\fIzramdev\fP ]
-.RB [ \-s
-.IR size ]
-.RB [ \-t
-.IR number ]
-.RB [ \-a
-.IR algorithm ]
-.sp
-.in -5
-.ad b
-.SH DESCRIPTION
-.B zramctl
-is used to quickly set up zram device parameters, to reset zram devices, and to
-query the status of used zram devices.
-.PP
-If no option is given, all non-zero size zram devices are shown.
-.PP
-Note that \fIzramdev\fP node specified on command line has to already exist. The command
-.B zramctl
-creates a new /dev/zram<N> nodes only when \fB\-\-find\fR option specified. It's possible
-(and common) that after system boot /dev/zram<N> nodes are not created yet.
-.SH OPTIONS
-.TP
-.BR \-a , " \-\-algorithm lzo" | lz4 | lz4hc | deflate | 842
-Set the compression algorithm to be used for compressing data in the zram device.
-.TP
-.BR \-f , " \-\-find"
-Find the first unused zram device. If a \fB\-\-size\fR argument is present, then
-initialize the device.
-.TP
-.BR \-n , " \-\-noheadings"
-Do not print a header line in status output.
-.TP
-.BR \-o , " \-\-output " \fIlist
-Define the status output columns to be used. If no output arrangement is
-specified, then a default set is used.
-Use \fB\-\-help\fP to get a list of all supported columns.
-.TP
-.B \-\-output\-all
-Output all available columns.
-.TP
-.B \-\-raw
-Use the raw format for status output.
-.TP
-.BR \-r , " \-\-reset"
-Reset the options of the specified zram device(s). Zram device settings
-can be changed only after a reset.
-.TP
-.BR \-s , " \-\-size " \fIsize
-Create a zram device of the specified \fIsize\fR.
-Zram devices are aligned to memory pages; when the requested \fIsize\fR 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 \fIsize\fR parameter is bytes.
-.IP
-The \fIsize\fR 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.
-.TP
-.BR \-t , " \-\-streams " \fInumber
-Set the maximum number of compression streams that can be used for the device.
-The default is one stream.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-
-.SH EXIT STATUS
-.B zramctl
-returns 0 on success, nonzero on failure.
-
-.SH FILES
-.TP
-.I /dev/zram[0..N]
-zram block devices
-
-.SH EXAMPLE
-The following commands set up a zram device with a size of one gigabyte
-and use it as swap device.
-.nf
-.IP
-# zramctl --find --size 1024M
-/dev/zram0
-# mkswap /dev/zram0
-# swapon /dev/zram0
- ...
-# swapoff /dev/zram0
-# zramctl --reset /dev/zram0
-.fi
-.SH AUTHORS
-.nf
-Timofey Titovets <nefelim4ag@gmail.com>
-Karel Zak <kzak@redhat.com>
-.fi
-.SH SEE ALSO
-.UR http://git.\:kernel.\:org\:/cgit\:/linux\:/kernel\:/git\:/torvalds\:/linux.git\:/tree\:/Documentation\:/admin-guide\:/blockdev\:/zram.rst
-Linux kernel documentation
-.UE .
-.SH AVAILABILITY
-The zramctl command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.TH AGETTY 8 "February 2016" "util-linux" "System Administration"
-.SH NAME
-agetty \- alternative Linux getty
-
-.SH SYNOPSIS
-.B agetty
-[options]
-.IR port " [" baud_rate "...] [" term ]
-
-.SH DESCRIPTION
-.ad
-\fBagetty\fP opens a tty port, prompts for a login name and invokes
-the /bin/login command. It is normally invoked by \fBinit\fP(8).
-
-\fBagetty\fP has several \fInon-standard\fP features that are useful
-for hardwired and for dial-in lines:
-.IP \(bu
-Adapts the tty settings to parity bits and to erase, kill,
-end-of-line and uppercase characters when it reads a login name.
-The program can handle 7-bit characters with even, odd, none or space
-parity, and 8-bit characters with no parity. The following special
-characters are recognized: Control-U (kill); DEL and
-backspace (erase); carriage return and line feed (end of line).
-See also the \fB\-\-erase\-chars\fP and \fB\-\-kill\-chars\fP options.
-.IP \(bu
-Optionally deduces the baud rate from the CONNECT messages produced by
-Hayes(tm)-compatible modems.
-.IP \(bu
-Optionally does not hang up when it is given an already opened line
-(useful for call-back applications).
-.IP \(bu
-Optionally does not display the contents of the \fI/etc/issue\fP file.
-.IP \(bu
-Optionally displays an alternative issue files or directories instead of \fI/etc/issue\fP or \fI/etc/issue.d\fP.
-.IP \(bu
-Optionally does not ask for a login name.
-.IP \(bu
-Optionally invokes a non-standard login program instead of
-\fI/bin/login\fP.
-.IP \(bu
-Optionally turns on hardware flow control.
-.IP \(bu
-Optionally forces the line to be local with no need for carrier detect.
-.PP
-This program does not use the \fI/etc/gettydefs\fP (System V) or
-\fI/etc/gettytab\fP (SunOS 4) files.
-.SH ARGUMENTS
-.na
-.nf
-.fi
-.ad
-.TP
-.I port
-A path name relative to the \fI/dev\fP directory. If a "\-" is
-specified, \fBagetty\fP assumes that its standard input is
-already connected to a tty port and that a connection to a
-remote user has already been established.
-.sp
-Under System V, a "\-" \fIport\fP argument should be preceded
-by a "\-\-".
-.TP
-.IR baud_rate ,...
-A comma-separated list of one or more baud rates. Each time
-\fBagetty\fP receives a BREAK character it advances through
-the list, which is treated as if it were circular.
-.sp
-Baud rates should be specified in descending order, so that the
-null character (Ctrl\-@) can also be used for baud-rate switching.
-.sp
-This argument is optional and unnecessary for \fBvirtual terminals\fP.
-.sp
-The default for \fBserial terminals\fP is keep the current baud rate
-(see \fB\-\-keep\-baud\fP) and if unsuccessful then default to '9600'.
-.TP
-.I term
-The value to be used for the TERM environment variable. This overrides
-whatever
-.BR init (1)
-may have set, and is inherited by login and the shell.
-.sp
-The default is 'vt100', or 'linux' for Linux on a virtual terminal,
-or 'hurd' for GNU Hurd on a virtual terminal.
-.SH OPTIONS
-.na
-.nf
-.fi
-.ad
-.TP
-\-8, \-\-8bits
-Assume that the tty is 8-bit clean, hence disable parity detection.
-.TP
-\-a, \-\-autologin \fIusername\fP
-Automatically log in the specified user without asking for a username or password.
-Using this option causes an \fB\-f \fIusername\fR option and argument to be
-added to the \fB/bin/login\fP command line. See \fB\-\-login\-options\fR, which
-can be used to modify this option's behavior.
-
-Note that \fB\-\-autologin\fP may affect the way in which
-.B getty
-initializes the
-serial line, because on auto-login
-.B agetty
-does not read from the line and it
-has no opportunity optimize the line setting.
-.TP
-\-c, \-\-noreset
-Do not reset terminal cflags (control modes). See \fBtermios\fP(3) for more
-details.
-.TP
-\-E, \-\-remote
-Typically the \fBlogin\fP(1) command is given a remote hostname when
-called by something such as \fBtelnetd\fP(8). This option allows \fBagetty\fP
-to pass what it is using for a hostname to \fBlogin\fP(1) for use
-in \fButmp\fP(5). See \fB\-\-host\fP, \fBlogin\fP(1), and \fButmp\fP(5).
-.IP
-If the \fB\-\-host\fP \fIfakehost\fP option is given, then an \fB\-h\fP
-\fIfakehost\fP option and argument are added to the \fB/bin/login\fP
-command line.
-.IP
-If the \fB\-\-nohostname\fR option is given, then an \fB\-H\fP option
-is added to the \fB/bin/login\fP command line.
-.IP
-See \fB\-\-login\-options\fR.
-.TP
-\-f, \-\-issue\-file \fIpath\fP
-Specifies a ":" delimited list of files and directories to be displayed instead
-of \fI/etc/issue\fP (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 \fB\-\-noissue\fP option will override this option.
-.TP
-\-\-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.
-.TP
-\-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.
-.TP
-\-H, \-\-host \fIfakehost\fP
-Write the specified \fIfakehost\fP into the utmp file. Normally,
-no login host is given, since \fBagetty\fP is used for local hardwired
-connections and consoles. However, this option can be useful for
-identifying terminal concentrators and the like.
-.TP
-\-i, \-\-noissue
-Do not display the contents of \fI/etc/issue\fP (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.
-.TP
-\-I, \-\-init\-string \fIinitstring\fP
-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 \\012.
-.TP
-\-J, \-\-noclear
-Do not clear the screen before prompting for the login name.
-By default the screen is cleared.
-.TP
-\-l, \-\-login\-program \fIlogin_program\fP
-Invoke the specified \fIlogin_program\fP 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
-\fB\-\-login\-options\fP.
-.TP
-\-L, \-\-local\-line[=\fImode\fP]
-Control the CLOCAL line flag. The optional \fImode\fP argument is 'auto', 'always' or 'never'.
-If the \fImode\fP argument is omitted, then the default is 'always'. If the
-\-\-local\-line option is not given at all, then the default is 'auto'.
-.PP
-.RS
-.PD 1
-.TP
-\fIalways\fR
-Forces the line to be a local line with no need for carrier detect. This
-can be useful when you have a locally attached terminal where the serial
-line does not set the carrier-detect signal.
-.TP
-\fInever\fR
-Explicitly clears the CLOCAL flag from the line setting and the
-carrier-detect signal is expected on the line.
-.TP
-\fIauto\fR
-The \fBagetty\fR default. Does not modify the CLOCAL setting and follows
-the setting enabled by the kernel.
-.PD
-.RE
-.TP
-\-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>".
-\fBagetty\fP assumes that the modem emits its status message at
-the same speed as specified with (the first) \fIbaud_rate\fP value
-on the command line.
-.sp
-Since the \fB\-\-extract\-baud\fP feature may fail on heavily-loaded
-systems, you still should enable BREAK processing by enumerating all
-expected baud rates on the command line.
-.TP
-\-\-list\-speeds
-Display supported baud rates. These are determined at compilation time.
-.TP
-\-n, \-\-skip\-login
-Do not prompt the user for a login name. This can be used in connection
-with the \fB\-\-login\-program\fP option to invoke a non-standard login
-process such as a BBS system. Note that with the \fB\-\-skip\-login\fR
-option, \fBagetty\fR 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 \fBagetty\fR starts (usually /bin/login) is run as root.
-.TP
-\-N, \-\-nonewline
-Do not print a newline before writing out /etc/issue.
-.TP
-\-o, \-\-login\-options "\fIlogin_options\fP"
-Options and arguments that are passed to \fBlogin\fP(1). Where \eu is
-replaced by the login name. For example:
-.RS
-.IP "" 4
-.B "\-\-login\-options '\-h darkstar \-\- \eu'"
-.PP
-See \fB\-\-autologin\fR, \fB\-\-login\-program\fR and \fB\-\-remote\fR.
-.PP
-Please read the SECURITY NOTICE below before using this option.
-.RE
-.TP
-\-p, \-\-login\-pause
-Wait for any key before dropping to the login prompt. Can be combined
-with \fB\-\-autologin\fP to save memory by lazily spawning shells.
-.TP
-\-r, \-\-chroot \fIdirectory\fP
-Change root to the specified directory.
-.TP
-\-R, \-\-hangup
-Call vhangup() to do a virtual hangup of the specified terminal.
-.TP
-\-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.
-.TP
-\-t, \-\-timeout \fItimeout\fP
-Terminate if no user name could be read within \fItimeout\fP seconds.
-Use of this option with hardwired terminal lines is not recommended.
-.TP
-\-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.
-.TP
-\-w, \-\-wait\-cr
-Wait for the user or the modem to send a carriage-return or a
-linefeed character before sending the \fI/etc/issue\fP file (or others)
-and the login prompt. This is useful with the \fB\-\-init\-string\fP
-option.
-.TP
-\-\-nohints
-Do not print hints about Num, Caps and Scroll Locks.
-.TP
-\-\-nohostname
-By default the hostname will be printed. With this option enabled,
-no hostname at all will be shown.
-.TP
-\-\-long\-hostname
-By default the hostname is only printed until the first dot. With
-this option enabled, the fully qualified hostname by \fBgethostname\fR(3P)
-or (if not found) by \fBgetaddrinfo\fR(3) is shown.
-.TP
-\-\-erase\-chars \fIstring\fP
-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.
-.TP
-\-\-kill\-chars \fIstring\fP
-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.
-.TP
-\-\-chdir \fIdirectory\fP
-Change directory before the login.
-.TP
-\-\-delay \fInumber\fP
-Sleep seconds before open tty.
-.TP
-\-\-nice \fInumber\fP
-Run login with this priority.
-.TP
-\-\-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
-.BR inotify (7).
-.TP
-\-\-version
-Display version information and exit.
-.TP
-\-\-help
-Display help text and exit.
-.SH EXAMPLE
-This section shows examples for the process field of an entry in the
-\fI/etc/inittab\fP file. You'll have to prepend appropriate values
-for the other fields. See \fIinittab(5)\fP for more details.
-
-For a hardwired line or a console tty:
-
-.RS
-.B /sbin/agetty\ 9600\ ttyS1
-.RE
-
-For a directly connected terminal without proper carrier-detect wiring
-(try this if your terminal just sleeps instead of giving you a password:
-prompt):
-
-.RS
-.B /sbin/agetty\ \-\-local\-line\ 9600\ ttyS1\ vt100
-.RE
-
-For an old-style dial-in line with a 9600/2400/1200 baud modem:
-
-.RS
-.B /sbin/agetty\ \-\-extract\-baud\ \-\-timeout\ 60\ ttyS1\ 9600,2400,1200
-.RE
-
-For a Hayes modem with a fixed 115200 bps interface to the machine
-(the example init string turns off modem echo and result codes, makes
-modem/computer DCD track modem/modem DCD, makes a DTR drop cause a
-disconnection, and turns on auto-answer after 1 ring):
-
-.ie n .RS 0
-.el .RS
-.B /sbin/agetty\ \-\-wait\-cr\ \-\-init\-string\ 'ATE0Q1&D2&C1S0=1\\015'\ 115200\ ttyS1
-.RE
-
-.SH SECURITY NOTICE
-If you use the \fB\-\-login\-program\fP and \fB\-\-login\-options\fP options,
-be aware that a malicious user may try to enter lognames with embedded options,
-which then get passed to the used login program. Agetty does check
-for a leading "\-" and makes sure the logname gets passed as one parameter
-(so embedded spaces will not create yet another parameter), but depending
-on how the login binary parses the command line that might not be sufficient.
-Check that the used login program cannot be abused this way.
-.PP
-Some programs use "\-\-" to indicate that the rest of the command line should
-not be interpreted as options. Use this feature if available by passing "\-\-"
-before the username gets passed by \\u.
-
-.SH ISSUE FILES
-The default issue file is \fI/etc/issue\fP. If the file exists, then
-.B agetty
-also
-checks for \fI/etc/issue.d\fP directory. The directory is optional extension to
-the default issue file and content of the directory is printed after
-\fI/etc/issue\fP content. If the \fI/etc/issue\fP does not exist, then the
-directory is ignored. All files \fBwith .issue extension\fP from the directory are
-printed in version-sort order. The directory can be used to maintain 3rd-party
-messages independently on the primary system \fI/etc/issue\fP file.
-
-Since version 2.35 additional locations for issue file and directory are
-supported. If the default \fI/etc/issue\fP does not exist, then
-.B agetty
-checks
-for \fI/run/issue\fP and \fI/run/issue.d\fP, thereafter for
-\fI/usr/lib/issue\fP and \fI/usr/lib/issue.d\fP. The directory /etc is
-expected for host specific configuration, /run is expected for generated stuff
-and /usr/lib for static distribution maintained configuration.
-
-The default path maybe overridden by \fB\-\-issue\-file\fP option. In this case
-specified path has to be file or directory and all the default issue file and
-directory locations are ignored.
-
-The issue file feature can be completely disabled by \fB\-\-noissue\fP option.
-
-It is possible to review the current issue file by \fBagetty \-\-show\-issue\fP
-on the current terminal.
-
-The issue files may contain certain escape codes to display the system name, date, time
-et cetera. All escape codes consist of a backslash (\\) immediately
-followed by one of the characters listed below.
-
-.TP
-4 or 4{\fIinterface\fR}
-Insert the IPv4 address of the specified network interface (for example: \\4{eth0}).
-If the \fIinterface\fR argument is not specified, then select the first fully
-configured (UP, non-LOCALBACK, RUNNING) interface. If not any configured
-interface is found, fall back to the IP address of the machine's hostname.
-.TP
-6 or 6{\fIinterface\fR}
-The same as \\4 but for IPv6.
-.TP
-b
-Insert the baudrate of the current line.
-.TP
-d
-Insert the current date.
-.TP
-e or e{\fIname\fR}
-Translate the human-readable \fIname\fP to an escape sequence and insert it
-(for example: \\e{red}Alert text.\\e{reset}). If the \fIname\fR argument is
-not specified, then insert \\033. The currently supported names are: black,
-blink, blue, bold, brown, cyan,
-darkgray, gray, green, halfbright, lightblue, lightcyan, lightgray, lightgreen,
-lightmagenta, lightred, magenta, red, reset, reverse, yellow and white. All unknown
-names are silently ignored.
-.TP
-s
-Insert the system name (the name of the operating system). Same as 'uname \-s'.
-See also the \\S escape code.
-.TP
-S or S{VARIABLE}
-Insert the VARIABLE data from \fI/etc/os-release\fP. If this file does not exist
-then fall back to \fI/usr/lib/os-release\fP. If the VARIABLE argument is not
-specified, then use PRETTY_NAME from the file or the system name (see \\s).
-This escape code can be used to keep \fI/etc/issue\fP distribution and release
-independent. Note that \\S{ANSI_COLOR} is converted to the real terminal
-escape sequence.
-.TP
-l
-Insert the name of the current tty line.
-.TP
-m
-Insert the architecture identifier of the machine. Same as 'uname \-m'.
-.TP
-n
-Insert the nodename of the machine, also known as the hostname. Same as 'uname \-n'.
-.TP
-o
-Insert the NIS domainname of the machine. Same as 'hostname \-d'.
-.TP
-O
-Insert the DNS domainname of the machine.
-.TP
-r
-Insert the release number of the OS. Same as 'uname \-r'.
-.TP
-t
-Insert the current time.
-.TP
-u
-Insert the number of current users logged in.
-.TP
-U
-Insert the string "1 user" or "<n> users" where <n> is the number of current
-users logged in.
-.TP
-v
-Insert the version of the OS, that is, the build-date and such.
-.PP
-An example. On my system, the following \fI/etc/issue\fP file:
-.sp
-.na
-.RS
-.nf
-This is \\n.\\o (\\s \\m \\r) \\t
-.fi
-.RE
-.PP
-displays as:
-.sp
-.RS
-.nf
-This is thingol.orcan.dk (Linux i386 1.1.9) 18:29:30
-.fi
-.RE
-
-.SH FILES
-.na
-.TP
-.I /var/run/utmp
-the system status file.
-.TP
-.I /etc/issue
-printed before the login prompt.
-.TP
-.I /etc/os-release /usr/lib/os-release
-operating system identification data.
-.TP
-.I /dev/console
-problem reports (if syslog(3) is not used).
-.TP
-.I /etc/inittab
-\fIinit\fP(8) configuration file for SysV-style init daemon.
-.SH BUGS
-.ad
-The baud-rate detection feature (the \fB\-\-extract\-baud\fP option) requires that
-\fBagetty\fP be scheduled soon enough after completion of a dial-in
-call (within 30 ms with modems that talk at 2400 baud). For robustness,
-always use the \fB\-\-extract\-baud\fP option in combination with a multiple baud
-rate command-line argument, so that BREAK processing is enabled.
-
-The text in the \fI/etc/issue\fP file (or other) and the login prompt
-are always output with 7-bit characters and space parity.
-
-The baud-rate detection feature (the \fB\-\-extract\-baud\fP option) requires that
-the modem emits its status message \fIafter\fP raising the DCD line.
-.SH DIAGNOSTICS
-.ad
-Depending on how the program was configured, all diagnostics are
-written to the console device or reported via the \fBsyslog\fR(3) facility.
-Error messages are produced if the \fIport\fP argument does not
-specify a terminal device; if there is no utmp entry for the
-current process (System V only); and so on.
-.SH AUTHORS
-.UR werner@suse.de
-Werner Fink
-.UE
-.br
-.UR kzak@redhat.com
-Karel Zak
-.UE
-.sp
-The original
-.B agetty
-for serial terminals was written by W.Z. Venema <wietse@wzv.win.tue.nl>
-and ported to Linux by Peter Orbaek <poe@daimi.aau.dk>.
-
-.SH AVAILABILITY
-The agetty command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util\-linux/.
+++ /dev/null
-.\" Copyright (c) 1987, 1990, 1993
-.\" The Regents of the University of California. All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)mesg.1 8.1 (Berkeley) 6/6/93
-.\"
-.TH MESG 1 "July 2014" "util-linux" "User Commands"
-.SH NAME
-mesg \- display (or do not display) messages from other users
-.SH SYNOPSIS
-.B mesg
-[option]
-.RB [ n | y ]
-.SH DESCRIPTION
-The
-.B mesg
-utility is invoked by a user to control write access others have to the
-terminal device associated with standard error output. If write access
-is allowed, then programs such as
-.BR talk (1)
-and
-.BR write (1)
-may display messages on the terminal.
-.PP
-Traditionally, write access is allowed by default. However, as users
-become more conscious of various security risks, there is a trend to remove
-write access by default, at least for the primary login shell. To make
-sure your ttys are set the way you want them to be set,
-.B mesg
-should be executed in your login scripts.
-.PP
-The
-.B mesg
-utility silently exits with error status 2 if not executed on terminal. In this
-case execute
-.B mesg
-is pointless. The command line option \fB\-\-verbose\fR forces
-mesg to print a warning in this situation. This behaviour has been introduced
-in version 2.33.
-.SH ARGUMENTS
-.TP
-.B n
-Disallow messages.
-.TP
-.B y
-Allow messages to be displayed.
-.PP
-If no arguments are given,
-.B mesg
-shows the current message status on standard error output.
-.SH OPTIONS
-.TP
-.BR \-v , " \-\-verbose"
-Explain what is being done.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH EXIT STATUS
-The
-.B mesg
-utility exits with one of the following values:
-.RS 4
-.TP
-.B "\ 0"
-Messages are allowed.
-.TP
-.B "\ 1"
-Messages are not allowed.
-.TP
-.B ">1"
-An error has occurred.
-.RE
-.SH FILES
-.I /dev/[pt]ty[pq]?
-.SH HISTORY
-A
-.B mesg
-command appeared in Version 6 AT&T UNIX.
-
-.SH SEE ALSO
-.BR login (1),
-.BR talk (1),
-.BR write (1),
-.BR wall (1),
-.BR xterm (1)
-.SH AVAILABILITY
-The mesg command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
+++ /dev/null
-.\" Copyright (c) 1980, 1990 Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)script.1 6.5 (Berkeley) 7/27/91
-.\"
-.TH SCRIPT "1" "October 2019" "util-linux" "User Commands"
-.SH NAME
-script \- make typescript of terminal session
-.SH SYNOPSIS
-.B script
-[options]
-.RI [ file ]
-.SH DESCRIPTION
-.B script
-makes a typescript of everything on your terminal session. The terminal
-data are stored in raw form to the log file and information about timing
-to another (optional) structured log file. The timing log file is necessary to replay
-the session later by
-.BR scriptreplay (1)
-and to store additional information about the session.
-.PP
-Since version 2.35,
-.B script
-supports multiple streams and allows the logging of input and output to separate
-files or all the one file. This version also supports new timing file
-which records additional information. The command
-.B scriptreplay \-\-summary
-then provides all the information.
-
-.PP
-If the argument
-.I file
-or option \fB\-\-log\-out\fR \fIfile\fR is given,
-.B script
-saves the dialogue in this
-.IR file .
-If no filename is given, the dialogue is saved in the file
-.IR typescript .
-.PP
-Note that logging input using \fB\-\-log\-in\fR or \fB\-\-log\-io\fR
-may record security-sensitive information
-as the log file contains all terminal session input
-(e.g., passwords)
-independently of the terminal echo flag setting.
-.SH OPTIONS
-Below, the \fIsize\fR 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.
-.TP
-\fB\-a\fR, \fB\-\-append\fR
-Append the output to
-.I file
-or to
-.IR typescript ,
-retaining the prior contents.
-.TP
-\fB\-c\fR, \fB\-\-command\fR \fIcommand\fR
-Run the
-.I command
-rather than an interactive shell. This makes it easy for a script to capture
-the output of a program that behaves differently when its stdout is not a
-tty.
-.TP
-\fB\-E\fR, \fB\-\-echo\fR \fIwhen\fR
-This option controls the ECHO flag for the slave end of the session's pseudoterminal.
-The supported modes are
-.IR always ,
-.IR never ,
-or
-.IR auto .
-.sp
-The default is
-.I 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:
-.BR "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.
-.sp
-Note that 'never' mode affects content of the session output log, because
-users input is not repeated on output.
-.TP
-\fB\-e\fR, \fB\-\-return\fR
-Return the exit status of the child process. Uses the same format as bash
-termination on signal termination
-(i.e., exit status is 128 + the signal number). The exit status of
-the child process is always stored in the type script file too.
-.TP
-\fB\-f\fR, \fB\-\-flush\fR
-Flush output after each write. This is nice for telecooperation: one person
-does `mkfifo foo; script \-f foo',
-and another can supervise in real-time what is
-being done using `cat foo'. Note that flush has an impact on performance; it's
-possible to use SIGUSR1 to flush logs on demand.
-.TP
-\fB\-\-force\fR
-Allow the default output file
-.I typescript
-to be a hard or symbolic link. The command will follow a symbolic link.
-.TP
-\fB\-B\fR, \fB\-\-log\-io\fR \fIfile\fR
-Log input and output to the same
-\fIfile\fR. Note, this option makes sense only if \fB\-\-log\-timing\fR is
-also specified, otherwise it's impossible to separate output and input streams from
-the log \fIfile\fR.
-.TP
-\fB\-I\fR, \fB\-\-log\-in\fR \fIfile\fR
-Log input to the \fIfile\fR. The log output is disabled if only \fB\-\-log\-in\fR
-specified.
-.sp
-Use this logging functionality carefully as it logs all input, including input
-when terminal has disabled echo flag (for example, password inputs).
-.TP
-\fB\-O\fR, \fB\-\-log\-out\fR \fIfile\fR
-Log output to the \fIfile\fR. The default is to log output to the file with
-name
-.I typescript
-if the option \fB\-\-log\-out\fR or \fB\-\-log\-in\fR is not given. The log
-output is disabled if only \fB\-\-log\-in\fR specified.
-.TP
-\fB\-T\fR, \fB\-\-log\-timing\fR \fIfile\fR
-Log timing information to the \fIfile\fR. 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 \fB\-\-log\-io\fR or when
-\fB\-\-log\-in\fR and \fB\-\-log\-out\fR are used together.
-See also \fB\-\-logging\-format\fR.
-.TP
-\fB\-m\fR, \fB\-\-logging\-format\fR \fIformat\fR
-Force use of
-.I advanced
-or
-.I 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.
-.sp
-.RS
-.B Classic format
-.PP
-The log contains two fields, separated by a space. The first
-field indicates how much time elapsed since the previous output. The second
-field indicates how many characters were output this time.
-.sp
-.B Advanced (multi-stream) format
-.PP
-The first field is an entry type identifier
-('I'nput, 'O'utput, 'H'eader, 'S'ignal).
-The socond field is how much time elapsed since the previous entry,
-and the rest of the entry is type-specific data.
-.RE
-.TP
-\fB\-o\fR, \fB\-\-output-limit\fR \fIsize\fR
-Limit the size of the typescript and timing files to
-.I size
-and stop the child process after this size is exceeded. The calculated
-file size does not include the start and done messages that the
-.B script
-command prepends and appends to the child process output.
-Due to buffering, the resulting output file might be larger than the specified value.
-.TP
-\fB\-q\fR, \fB\-\-quiet\fR
-Be quiet (do not write start and done messages to standard output).
-.TP
-\fB\-t\fR[\fIfile\fR], \fB\-\-timing\fR[=\fIfile\fR]
-Output timing data to standard error, or to
-.I file
-when given. This option is deprecated in favour of \fB\-\-log\-timing\fR where
-the \fIfile\fR argument is not optional.
-.TP
-\fB\-V\fR, \fB\-\-version\fR
-Display version information and exit.
-.TP
-\fB\-h\fR, \fB\-\-help\fR
-Display help text and exit.
-.SH SIGNALS
-Upon receiving
-.BR SIGUSR1 ,
-.B script
-immediately flushes the output files.
-.SH ENVIRONMENT
-The following environment variable is utilized by
-.BR script :
-.TP
-.B SHELL
-If the variable
-.B SHELL
-exists, the shell forked by
-.B script
-will be that shell. If
-.B SHELL
-is not set, the Bourne shell is assumed. (Most shells set this variable
-automatically).
-.SH NOTES
-The script ends when the forked shell exits (a
-.I control-D
-for the Bourne shell
-.RB ( sh (1p)),
-and
-.IR exit ,
-.I logout
-or
-.I control-d
-(if
-.I ignoreeof
-is not set) for the
-C-shell,
-.BR csh (1)).
-.PP
-Certain interactive commands, such as
-.BR vi (1),
-create garbage in the typescript file.
-.B script
-works best with commands that do not manipulate the screen, the results are
-meant to emulate a hardcopy terminal.
-.PP
-It is not recommended to run
-.B script
-in non-interactive shells. The inner shell of
-.B script
-is always interactive, and this could lead to unexpected results. If you use
-.B script
-in the shell initialization file, you have to avoid entering an infinite
-loop. You can use for example the \fB\%.profile\fR file, which is read
-by login shells only:
-.sp
-.na
-.RS
-.nf
-if test \-t 0 ; then
- script
- exit
-fi
-.fi
-.RE
-.ad
-.PP
-You should also avoid use of
-.B script
-in command pipes, as
-.B script
-can read more input than you would expect.
-.SH HISTORY
-The
-.B script
-command appeared in 3.0BSD.
-.SH BUGS
-.B script
-places
-.I everything
-in the log file, including linefeeds and backspaces. This is not what the
-naive user expects.
-.PP
-.B script
-is primarily designed for interactive terminal sessions. When stdin
-is not a terminal (for example: \fBecho foo | script\fR), then the session
-can hang, because the interactive shell within the script session misses EOF and
-.B script
-has no clue when to close the session. See the \fBNOTES\fR section for more information.
-.SH SEE ALSO
-.BR csh (1)
-(for the
-.I history
-mechanism),
-.BR scriptreplay (1),
-.BR scriptlive (1),
-.SH AVAILABILITY
-The script command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH SCRIPTLIVE 1 "October 2019" "util-linux" "User Commands"
-.SH NAME
-scriptlive \- re-run session typescripts, using timing information
-.SH SYNOPSIS
-.B scriptlive
-[options]
-.RB [ \-t ]
-.I timingfile
-.RB [ \-I|\-B ]
-.I typescript
-.SH DESCRIPTION
-This program re-runs a typescript,
-using stdin typescript and timing information to ensure that
-input happens in the same rhythm as it originally appeared when the script
-was recorded.
-.PP
-The \fBsession is executed\fR in a newly created pseudoterminal with
-the user's $SHELL
-(or defaults to /bin/bash).
-.PP
-.B Be careful!
-Do not forget that the typescript may contains arbitrary commands.
-It is recommended to use \fB"scriptreplay \-\-stream in \-\-log\-in typescript"\fR
-(or with
-.B \-\-log\-io
-instead of
-.BR \-\-log\-in\)
-to verify the typescript before it is executed by
-.BR scriptlive (1).
-.PP
-The timing information is what
-.BR script (1)
-outputs to file specified by
-.BR \-\-log\-timing .
-The typescript has to contain stdin information and it is what
-.BR script (1)
-outputs to file specified by
-.B \-\-log-in
-or
-.BR \-\-log\-io .
-
-.SH OPTIONS
-.TP
-.BR \-I , " \-\-log-in " \fIfile\fR
-File containing \fBscript\fR's terminal input.
-.TP
-.BR \-B , " \-\-log-io " \fIfile\fR
-File containing \fBscript\fR's terminal output and input.
-.TP
-.BR \-t , " \-\-timing " \fIfile\fR
-File containing \fBscript\fR's timing output. This option overrides old-style arguments.
-.TP
-.BR \-T , " \-\-log\-timing " \fIfile\fR
-Aliased to \fB\-t\fR, maintained for compatibility with
-.BR script (1)
-command-line options.
-.TP
-.BR \-d , " \-\-divisor " \fInumber\fR
-Speed up the replay displaying this
-.I number
-of times. The argument is a floating-point number. It's called divisor
-because it divides the timings by this factor. This option overrides old-style arguments.
-.TP
-.BR \-m , " \-\-maxdelay " \fInumber\fR
-Set the maximum delay between updates to
-.I number
-of seconds. The argument is a floating-point number. This can be used to
-avoid long pauses in the typescript replay.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH EXAMPLES
-.nf
-% script --log-timing file.tm --log-in script.in
-Script started, file is script.out
-% date
-<etc, etc>
-% exit
-Script done, file is script.out
-% scriptlive --log-timing file.tm --log-in script.in
-.fi
-.SH AUTHORS
-.MT kzak@\:redhat.com
-Karel Zak
-.ME .
-.SH COPYRIGHT
-Copyright \(co 2019 Karel Zak
-.PP
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
-PURPOSE.
-.PP
-Released under the GNU General Public License version 2 or later.
-.SH SEE ALSO
-.BR script (1),
-.BR scriptreplay (1)
-.SH AVAILABILITY
-The scriptlive command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.TH SCRIPTREPLAY 1 "October 2019" "util-linux" "User Commands"
-.SH NAME
-scriptreplay \- play back typescripts, using timing information
-.SH SYNOPSIS
-.B scriptreplay
-[options]
-.RB [ \-t ]
-.I timingfile
-.RI [ typescript
-.RI [ divisor ]]
-.SH DESCRIPTION
-This program replays a typescript, using timing information to ensure that
-output happens in the same rhythm as it originally appeared when the script
-was recorded.
-.PP
-The replay simply displays the information again; the programs
-that were run when the typescript was being recorded are \fBnot run again\fR.
-Since the same information is simply being displayed,
-.B scriptreplay
-is only guaranteed to work properly if run on the same type of
-terminal the typescript was recorded on. Otherwise, any escape characters
-in the typescript may be interpreted differently by the terminal to
-which
-.B scriptreplay
-is sending its output.
-.PP
-The timing information is what
-.BR script (1)
-outputs to file specified by
-.BR \-\-log-timing .
-.PP
-By default, the typescript to display is assumed to be named
-.IR typescript ,
-but other filenames may be specified, as the second parameter or with option
-.BR \-\-log\-out .
-.PP
-If the third parameter or
-.B \-\-divisor
-is specified, it is used as a speed-up multiplier.
-For example, a speed-up of 2 makes
-.B scriptreplay
-go twice as fast, and a speed-up of 0.1 makes it go ten times slower
-than the original session.
-.SH OPTIONS
-.TP
-.BR \-I , " \-\-log-in " \fIfile\fR
-File containing \fBscript\fR's terminal input.
-.TP
-.BR \-O , " \-\-log-out " \fIfile\fR
-File containing \fBscript\fR's terminal output.
-.TP
-.BR \-B , " \-\-log-io " \fIfile\fR
-File containing \fBscript\fR's terminal output and input.
-.TP
-.BR \-t , " \-\-timing " \fIfile\fR
-File containing \fBscript\fR's timing output. This option overrides old-style arguments.
-.TP
-.BR \-T , " \-\-log\-timing " \fIfile\fR
-This is an alias for \fB\-t\fR, maintained for compatibility with
-.BR script (1)
-command-line options.
-.TP
-.BR \-s , " \-\-typescript " \fIfile\fR
-File containing \fBscript\fR's terminal output. Deprecated alias to \fB\-\-log-out\fR.
-This option overrides old-style arguments.
-.TP
-.BR \-c , " \-\-cr\-mode " \fImode\fR
-Specifies how to use the CR (0x0D, carriage return) character from log files.
-The default mode is
-.IR auto ,
-in this case CR is replaced with line break for stdin log, because otherwise
-.B scriptreplay
-would overwrite the same line. The other modes are
-.I never
-and
-.IR always .
-.TP
-.BR \-d , " \-\-divisor " \fInumber\fR
-Speed up the replay displaying this
-.I number
-of times. The argument is a floating-point number. It's called divisor
-because it divides the timings by this factor. This option overrides old-style arguments.
-.TP
-.BR \-m , " \-\-maxdelay " \fInumber\fR
-Set the maximum delay between updates to
-.I number
-of seconds. The argument is a floating-point number. This can be used to
-avoid long pauses in the typescript replay.
-.TP
-.B \-\-summary
-Display details about the session recorded in the specified timing file
-and exit. The session has to be recorded using
-.I advanced
-format (see
-.BR script (1))
-option \fB\-\-logging\-format\fR for more details).
-.TP
-.BR \-x , " \-\-stream " \fItype\fR
-Forces
-.B scriptreplay
-to print only the specified stream. The supported stream types
-are
-.IR in ,
-.IR out ,
-.IR signal ,
-or
-.IR info .
-This option is recommended for multi-stream logs (e.g.,
-.BR \-\-log-io )
-in order to print only specified data.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH EXAMPLES
-.nf
-% script --log-timing file.tm --log-out script.out
-Script started, file is script.out
-% ls
-<etc, etc>
-% exit
-Script done, file is script.out
-% scriptreplay --log-timing file.tm --log-out script.out
-.fi
-.SH AUTHORS
-The original
-.B scriptreplay
-program was written by
-.MT joey@\:kitenet.net
-Joey Hess
-.ME .
-The program was re-written in C by
-.MT jay@\:gnu.org
-James Youngman
-.ME
-and
-.MT kzak@\:redhat.com
-Karel Zak
-.ME .
-.SH COPYRIGHT
-Copyright \(co 2008 James Youngman
-.br
-Copyright \(co 2008-2019 Karel Zak
-.PP
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
-PURPOSE.
-.PP
-Released under the GNU General Public License version 2 or later.
-.SH SEE ALSO
-.BR script (1),
-.BR scriptlive (1)
-.SH AVAILABILITY
-The scriptreplay command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright 1990 Gordon Irlam (gordoni@cs.ua.oz.au)
-.\" Copyright 1992 Rickard E. Faith (faith@cs.unc.edu)
-.\" Copyright 2000 Colin Watson (cjw44@cam.ac.uk)
-.\" Do not restrict distribution.
-.\" May be distributed under the GNU General Public License
-.\"
-.TH SETTERM 1 "May 2014" "util-linux" "User Commands"
-.SH NAME
-setterm \- set terminal attributes
-.SH SYNOPSIS
-.B setterm
-[options]
-.SH DESCRIPTION
-.B setterm
-writes to standard output a character string that will invoke the specified
-terminal capabilities. Where possible
-.I terminfo
-is consulted to find the string to use. Some options however (marked "virtual
-consoles only" below) do not correspond to a
-.BR terminfo (5)
-capability. In this case, if the terminal type is "con" or "linux" the string
-that invokes the specified capabilities on the PC Minix virtual console driver
-is output. Options that are not implemented by the terminal are ignored.
-.SH OPTIONS
-For boolean options
-.RB ( on " or " off ),
-the default is
-.BR on .
-.P
-Below, an
-.I 8-color
-can be
-.BR black ,
-.BR red ,
-.BR green ,
-.BR yellow ,
-.BR blue ,
-.BR magenta ,
-.BR cyan ,
-or
-.BR white .
-.P
-A
-.I 16-color
-can be an
-.IR 8-color ,
-or
-.BR grey ,
-or
-.B bright
-followed
-by
-.BR red ,
-.BR green ,
-.BR yellow ,
-.BR blue ,
-.BR magenta ,
-.BR cyan ,
-or
-.BR white .
-.P
-The various color options may be set independently, at least on virtual
-consoles, though the results of setting multiple modes (for example,
-.B \-\-underline
-and
-.BR \-\-half\-bright )
-are hardware-dependent.
-.PP
-The optional arguments require '=' (equals sign) and not space between the
-option and the argument. For example --option=argument.
-.TP
-\fB\-\-appcursorkeys\fP on|off
-Sets Cursor Key Application Mode on or off. When on, ESC O A, ESC O B, etc.
-will be sent for the cursor keys instead of ESC [ A, ESC [ B, etc. See the
-.I vi and Cursor-Keys
-section of the
-.I Text-Terminal-HOWTO
-for how this can cause problems for \fBvi\fR users.
-Virtual consoles only.
-.TP
-\fB\-\-append\fP \fIconsole_number\fP
-Like
-.BR \-\-dump ,
-but appends to the snapshot file instead of overwriting it. Only works if no
-.B \-\-dump
-options are given.
-.TP
-\fB\-\-background\fP \fI8-color\fP|default
-Sets the background text color.
-.TP
-\fB\-\-blank\fP[=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.
-.IP
-The
-.B force
-argument keeps the screen blank even if a key is pressed.
-.IP
-The
-.B poke
-argument unblanks the screen.
-.TP
-\fB\-\-bfreq\fP[=\fInumber\fP]
-Sets the bell frequency in Hertz. Without an argument, it defaults to
-.BR 0 .
-Virtual consoles only.
-.TP
-\fB\-\-blength\fP[=0-2000]
-Sets the bell duration in milliseconds. Without an argument, it defaults to
-.BR 0 .
-Virtual consoles only.
-.TP
-\fB\-\-blink\fP on|off
-Turns blink mode on or off. Except on a virtual console,
-.B \-\-blink off
-turns off all attributes (bold, half-brightness, blink, reverse).
-.TP
-\fB\-\-bold\fP on|off
-urns bold (extra bright) mode on or off. Except on a virtual console,
-.B \-\-bold off
-turns off all attributes (bold, half-brightness, blink, reverse).
-.TP
-\fB\-\-clear\fP[=all|rest]
-Without an argument or with the argument
-.BR all ,
-the entire screen is cleared and the cursor is set to the home position,
-just like
-.BR clear (1)
-does. With the argument
-.BR rest ,
-the screen is cleared from the current cursor position to the end.
-.TP
-\fB\-\-clrtabs\fP[=\fItab1 tab2 tab3\fP ...]
-Clears tab stops from the given horizontal cursor positions, in the range
-.BR 1-160 .
-Without arguments, it clears all tab stops.
-Virtual consoles only.
-.TP
-\fB\-\-cursor\fP on|off
-Turns the terminal's cursor on or off.
-.TP
-\fB\-\-default\fP
-Sets the terminal's rendering options to the default values.
-.TP
-\fB\-\-dump\fP[=\fIconsole_number\fP]
-Writes a snapshot of the virtual console with the given number
-to the file specified with the
-.B \-\-file
-option, overwriting its contents; the default is
-.IR screen.dump .
-Without an argument, it dumps the current virtual console. This overrides
-.BR \-\-append .
-.TP
-\fB\-\-file\fP \fIfilename\fP
-Sets the snapshot file name for any
-.B \-\-dump
-or
-.B \-\-append
-options on the same command line. If this option is not present, the default
-is
-.I screen.dump
-in the current directory. A path name that exceeds the system maximum will be
-truncated, see PATH_MAX from linux/limits.h for the value.
-.TP
-\fB\-\-foreground\fP \fI8-color\fP|default
-Sets the foreground text color.
-.TP
-\fB\-\-half\-bright\fP on|off
-Turns dim (half-brightness) mode on or off. Except on a virtual console,
-.B \-\-half\-bright off
-turns off all attributes (bold, half-brightness, blink, reverse).
-.TP
-\fB\-\-hbcolor\fP [bright] \fI16-color\fP
-Sets the color for half-bright characters.
-.TP
-\fB\-\-initialize\fP
-Displays the terminal initialization string, which typically sets the
-terminal's rendering options, and other attributes to the default values.
-.TP
-\fB\-\-inversescreen\fP on|off
-Swaps foreground and background colors for the whole screen.
-.TP
-\fB\-\-linewrap\fP on|off
-Makes the terminal continue on a new line when a line is full.
-.TP
-\fB\-\-msg\fP on|off
-Enables or disables the sending of kernel
-.BR printk ()
-messages to the console.
-Virtual consoles only.
-.TP
-\fB\-\-msglevel\fP 0-8
-Sets the console logging level for kernel
-.B printk()
-messages. All messages strictly more important than this will be printed, so a
-logging level of
-.B 0
-has the same effect as
-.B \-\-msg on
-and a logging level of
-.B 8
-will print all kernel messages.
-.BR klogd (8)
-may be a more convenient interface to the logging of kernel messages.
-.sp
-Virtual consoles only.
-.TP
-\fB\-\-powerdown\fP[=0-60]
-Sets the VESA powerdown interval in minutes. Without an argument, it defaults
-to
-.B 0
-(disable powerdown). If the console is blanked or the monitor is in suspend
-mode, then the monitor will go into vsync suspend mode or powerdown mode
-respectively after this period of time has elapsed.
-.TP
-\fB\-\-powersave\fP \fImode\fP
-Valid values for \fImode\fP are:
-.RS
-.TP
-.B vsync|on
-Puts the monitor into VESA vsync suspend mode.
-.TP
-.B hsync
-Puts the monitor into VESA hsync suspend mode.
-.TP
-.B powerdown
-Puts the monitor into VESA powerdown mode.
-.TP
-.B off
-Turns monitor VESA powersaving features.
-.RE
-.TP
-\fB\-\-regtabs\fP[=1-160]
-Clears all tab stops, then sets a regular tab stop pattern, with one tab every
-specified number of positions. Without an argument, it defaults to
-.BR 8 .
-Virtual consoles only.
-.TP
-\fB\-\-repeat\fP on|off
-Turns keyboard repeat on or off.
-Virtual consoles only.
-.TP
-\fB\-\-reset\fP
-Displays the terminal reset string, which typically resets the terminal to
-its power-on state.
-.TP
-\fB\-\-resize\fP
-Reset terminal size by assessing maximum row and column. This is useful
-when actual geometry and kernel terminal driver are not in sync. Most
-notable use case is with serial consoles, that do not use
-.BR ioctl (3p)
-but just byte streams and breaks.
-.TP
-\fB\-\-reverse\fP on|off
-Turns reverse video mode on or off. Except on a virtual console,
-.B \-\-reverse off
-turns off all attributes (bold, half-brightness, blink, reverse).
-.TP
-\fB\-\-store\fP
-Stores the terminal's current rendering options (foreground and background
-colors) as the values to be used at reset-to-default.
-Virtual consoles only.
-.TP
-\fB\-\-tabs\fP[=\fItab1 tab2 tab3\fP ...]
-Sets tab stops at the given horizontal cursor positions, in the range
-.BR 1-160 .
-Without arguments, it shows the current tab stop settings.
-.TP
-\fB\-\-term\fP \fIterminal_name\fP
-Overrides the TERM environment variable.
-.TP
-\fB\-\-ulcolor\fP [bright] \fI16-color\fP
-Sets the color for underlined characters.
-Virtual consoles only.
-.TP
-\fB\-\-underline\fP on|off
-Turns underline mode on or off.
-.TP
-\fB\-\-version\fP
-Displays version information and exits.
-.TP
-\fB\-\-help\fP
-Displays a help text and exits.
-.SH COMPATIBILITY
-Since version 2.25
-.B setterm
-has support for long options with two hyphens, for example
-.BR \-\-help ,
-beside the historical long options with a single hyphen, for example
-.BR \-help .
-In scripts it is better to use the backward-compatible single hyphen
-rather than the double hyphen. Currently there are no plans nor good
-reasons to discontinue single-hyphen compatibility.
-.SH BUGS
-Differences between the Minix and Linux versions are not documented.
-.SH SEE ALSO
-.BR stty (1),
-.BR tput (1),
-.BR tty (4),
-.BR terminfo (5)
-.SH AVAILABILITY
-The setterm command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright (c) 1989, 1990 The Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)wall.1 6.5 (Berkeley) 4/23/91
-.\"
-.TH WALL "1" "August 2013" "util-linux" "User Commands"
-.SH NAME
-wall \- write a message to all users
-.SH SYNOPSIS
-.B wall
-.RB [ \-n ]
-.RB [ \-t
-.IR timeout ]
-.RB [ \-g
-.IR group ]
-.RI [ message " | " file ]
-.SH DESCRIPTION
-.B wall
-displays a
-.IR message ,
-or the contents of a
-.IR file ,
-or otherwise its standard input, on the terminals of all currently logged
-in users. The command will wrap lines that are longer than 79 characters.
-Short lines are whitespace padded to have 79 characters. The command will
-always put a carriage return and new line at the end of each line.
-.PP
-Only the superuser can write on the terminals of users who have chosen to
-deny messages or are using a program which automatically denies messages.
-.PP
-Reading from a
-.I file
-is refused when the invoker is not superuser and the program is
-set-user-ID or set-group-ID.
-.SH OPTIONS
-.TP
-.BR \-n , " \-\-nobanner"
-Suppress the banner.
-.TP
-.BR \-t , " \-\-timeout " \fItimeout\fR
-Abandon the write attempt to the terminals after \fItimeout\fR seconds.
-This \fItimeout\fR must be a positive integer. The default value
-is 300 seconds, which is a legacy from the time when people ran terminals over
-modem lines.
-.TP
-.BR \-g , " \-\-group " \fIgroup\fR
-Limit printing message to members of group defined as a
-.I group
-argument. The argument can be group name or GID.
-.TP
-.BR \-V , " \-\-version"
-Display version information and exit.
-.TP
-.BR \-h , " \-\-help"
-Display help text and exit.
-.SH NOTES
-Some sessions, such as wdm, that have in the beginning of
-.BR utmp (5)
-ut_type data a ':' character will not get the message from
-.BR wall .
-This is done to avoid write errors.
-.SH HISTORY
-A
-.B wall
-command appeared in Version 7 AT&T UNIX.
-.SH SEE ALSO
-.BR mesg (1),
-.BR talk (1),
-.BR write (1),
-.BR shutdown (8)
-.SH AVAILABILITY
-The wall command is part of the util-linux package and is available from
-.UR https://\:www.kernel.org\:/pub\:/linux\:/utils\:/util-linux/
-Linux Kernel Archive
-.UE .
+++ /dev/null
-.\" Copyright (c) 1989, 1993
-.\" The Regents of the University of California. All rights reserved.
-.\"
-.\" This code is derived from software contributed to Berkeley by
-.\" Jef Poskanzer and Craig Leres of the Lawrence Berkeley Laboratory.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\" must display the following acknowledgement:
-.\" This product includes software developed by the University of
-.\" California, Berkeley and its contributors.
-.\" 4. Neither the name of the University nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" @(#)write.1 8.1 (Berkeley) 6/6/93
-.\"
-.TH WRITE 1 "March 1995" "util-linux" "User Commands"
-.SH NAME
-write \- send a message to another user
-.SH SYNOPSIS
-.B write
-.I user
-.RI [ ttyname ]
-.SH DESCRIPTION
-.B write
-allows you to communicate with other users, by copying lines from
-your terminal to theirs.
-.PP
-When you run the
-.B write
-command, the user you are writing to gets a message of the form:
-.PP
-.RS
-Message from yourname@yourhost on yourtty at hh:mm ...
-.RE
-.PP
-Any further lines you enter will be copied to the specified user's
-terminal. If the other user wants to reply, they must run
-.B write
-as well.
-.PP
-When you are done, type an end-of-file or interrupt character. The other
-user will see the message
-.B EOF
-indicating that the conversation is over.
-.PP
-You can prevent people (other than the superuser) from writing to you with
-the
-.BR mesg (1)
-command. Some commands, for example
-.BR nroff (1)
-and
-.BR pr (1),
-may automatically disallow writing, so that the output they produce
-isn't overwritten.
-.PP
-If the user you want to write to is logged in on more than one terminal,
-you can specify which terminal to write to by giving the terminal
-name as the second operand to the
-.B write
-command. Alternatively, you can let
-.B write
-select one of the terminals \- it will pick the one with the shortest idle
-time. This is so that if the user is logged in at work and also dialed up
-from home, the message will go to the right place.
-.PP
-The traditional protocol for writing to someone is that the string `\-o',
-either at the end of a line or on a line by itself, means that it's the
-other person's turn to talk. The string `oo' means that the person
-believes the conversation to be over.
-.SH HISTORY
-A
-.B write
-command appeared in Version 6 AT&T UNIX.
-.SH SEE ALSO
-.BR mesg (1),
-.BR talk (1),
-.BR who (1)
-.SH AVAILABILITY
-The write command is part of the util-linux package and is available from
-https://www.kernel.org/pub/linux/utils/util-linux/.
projects / thirdparty / util-linux.git / commitdiff
