From: Mario Blättermann Date: Tue, 16 Mar 2021 18:35:37 +0000 (+0100) Subject: Asciidoc: Remove already imported *roff man pages X-Git-Tag: v2.37-rc1~34^2~50 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b366e6fc6b6292ae0b2b55ca0ad1ff8fcb2f331f;p=thirdparty%2Futil-linux.git Asciidoc: Remove already imported *roff man pages --- diff --git a/lib/terminal-colors.d.5 b/lib/terminal-colors.d.5 deleted file mode 100644 index 4e06f8dd4a..0000000000 --- a/lib/terminal-colors.d.5 +++ /dev/null @@ -1,192 +0,0 @@ -.\" terminal-colors.d.5 -- -.\" Copyright 2014 Ondrej Oprala -.\" Copyright (C) 2014 Karel Zak -.\" 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 . diff --git a/libblkid/libblkid.3 b/libblkid/libblkid.3 deleted file mode 100644 index 7fa1539b81..0000000000 --- a/libblkid/libblkid.3 +++ /dev/null @@ -1,80 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid.3 b/libuuid/man/uuid.3 deleted file mode 100644 index 1dbe29b37b..0000000000 --- a/libuuid/man/uuid.3 +++ /dev/null @@ -1,66 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_clear.3 b/libuuid/man/uuid_clear.3 deleted file mode 100644 index be6b24917f..0000000000 --- a/libuuid/man/uuid_clear.3 +++ /dev/null @@ -1,62 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_compare.3 b/libuuid/man/uuid_compare.3 deleted file mode 100644 index f659c0ccce..0000000000 --- a/libuuid/man/uuid_compare.3 +++ /dev/null @@ -1,68 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_copy.3 b/libuuid/man/uuid_copy.3 deleted file mode 100644 index 71b00b9add..0000000000 --- a/libuuid/man/uuid_copy.3 +++ /dev/null @@ -1,64 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_generate.3 b/libuuid/man/uuid_generate.3 deleted file mode 100644 index dccecd6589..0000000000 --- a/libuuid/man/uuid_generate.3 +++ /dev/null @@ -1,139 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_is_null.3 b/libuuid/man/uuid_is_null.3 deleted file mode 100644 index f802228b5a..0000000000 --- a/libuuid/man/uuid_is_null.3 +++ /dev/null @@ -1,64 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_parse.3 b/libuuid/man/uuid_parse.3 deleted file mode 100644 index a7dff5ce0a..0000000000 --- a/libuuid/man/uuid_parse.3 +++ /dev/null @@ -1,86 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_time.3 b/libuuid/man/uuid_time.3 deleted file mode 100644 index 132635d28f..0000000000 --- a/libuuid/man/uuid_time.3 +++ /dev/null @@ -1,78 +0,0 @@ -.\" 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 -.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/. diff --git a/libuuid/man/uuid_unparse.3 b/libuuid/man/uuid_unparse.3 deleted file mode 100644 index 1573c230c6..0000000000 --- a/libuuid/man/uuid_unparse.3 +++ /dev/null @@ -1,81 +0,0 @@ -.\" 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 -.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/. diff --git a/schedutils/chrt.1 b/schedutils/chrt.1 deleted file mode 100644 index ef1006de9f..0000000000 --- a/schedutils/chrt.1 +++ /dev/null @@ -1,191 +0,0 @@ -.\" chrt(1) manpage -.\" -.\" Copyright (C) 2004 Robert Love -.\" Copyright (C) 2015 Karel Zak -.\" -.\" 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/. diff --git a/schedutils/ionice.1 b/schedutils/ionice.1 deleted file mode 100644 index bbb6b7e95f..0000000000 --- a/schedutils/ionice.1 +++ /dev/null @@ -1,141 +0,0 @@ -.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 -Karel Zak -.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/. diff --git a/schedutils/taskset.1 b/schedutils/taskset.1 deleted file mode 100644 index 71e7874e1a..0000000000 --- a/schedutils/taskset.1 +++ /dev/null @@ -1,139 +0,0 @@ -.\" 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/. diff --git a/schedutils/uclampset.1 b/schedutils/uclampset.1 deleted file mode 100644 index d877ac6b9c..0000000000 --- a/schedutils/uclampset.1 +++ /dev/null @@ -1,174 +0,0 @@ -.\" uclampset(1) manpage -.\" -.\" Copyright (C) 2020-2021 Qais Yousef -.\" 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/. diff --git a/sys-utils/adjtime_config.5 b/sys-utils/adjtime_config.5 deleted file mode 100644 index 8085b49e04..0000000000 --- a/sys-utils/adjtime_config.5 +++ /dev/null @@ -1,64 +0,0 @@ -.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/. diff --git a/sys-utils/blkdiscard.8 b/sys-utils/blkdiscard.8 deleted file mode 100644 index d39e855223..0000000000 --- a/sys-utils/blkdiscard.8 +++ /dev/null @@ -1,90 +0,0 @@ -.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 . diff --git a/sys-utils/blkzone.8 b/sys-utils/blkzone.8 deleted file mode 100644 index 958677e1bf..0000000000 --- a/sys-utils/blkzone.8 +++ /dev/null @@ -1,141 +0,0 @@ -.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 -Karel Zak -.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 . diff --git a/sys-utils/chcpu.8 b/sys-utils/chcpu.8 deleted file mode 100644 index 41b2d09512..0000000000 --- a/sys-utils/chcpu.8 +++ /dev/null @@ -1,104 +0,0 @@ -.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 . diff --git a/sys-utils/chmem.8 b/sys-utils/chmem.8 deleted file mode 100644 index 0727ceca1e..0000000000 --- a/sys-utils/chmem.8 +++ /dev/null @@ -1,114 +0,0 @@ -.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 [m|M|g|G]. With m or M, specifies the memory -size in MiB (1024 x 1024 bytes). With g or G, 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-0x as shown in the output of the -\fBlsmem\fP command. is the hexadecimal address of the first byte and -is the hexadecimal address of the last byte in the memory range. -. -.IP "\(hy" 2 -Specify \fIBLOCKRANGE\fP in the form - or as shown in the -output of the \fBlsmem\fP command. is the number of the first memory block -and 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 . diff --git a/sys-utils/choom.1 b/sys-utils/choom.1 deleted file mode 100644 index ce2b8b5399..0000000000 --- a/sys-utils/choom.1 +++ /dev/null @@ -1,83 +0,0 @@ -.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 -.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 . diff --git a/sys-utils/ctrlaltdel.8 b/sys-utils/ctrlaltdel.8 deleted file mode 100644 index 3f6657ee72..0000000000 --- a/sys-utils/ctrlaltdel.8 +++ /dev/null @@ -1,58 +0,0 @@ -.\" 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 . diff --git a/sys-utils/dmesg.1 b/sys-utils/dmesg.1 deleted file mode 100644 index b38766826c..0000000000 --- a/sys-utils/dmesg.1 +++ /dev/null @@ -1,274 +0,0 @@ -.\" 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 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-DDHH:MM:SS,<-+>. -.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 . diff --git a/sys-utils/eject.1 b/sys-utils/eject.1 deleted file mode 100644 index 313f9fd180..0000000000 --- a/sys-utils/eject.1 +++ /dev/null @@ -1,196 +0,0 @@ -.\" Copyright (C) 1994-2005 Jeff Tranter (tranter@pobox.com) -.\" Copyright (C) 2012 Karel Zak -.\" -.\" 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 . diff --git a/sys-utils/fallocate.1 b/sys-utils/fallocate.1 deleted file mode 100644 index 9e214c7362..0000000000 --- a/sys-utils/fallocate.1 +++ /dev/null @@ -1,191 +0,0 @@ -.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 . diff --git a/sys-utils/flock.1 b/sys-utils/flock.1 deleted file mode 100644 index 9d7a56fe15..0000000000 --- a/sys-utils/flock.1 +++ /dev/null @@ -1,206 +0,0 @@ -.\" ----------------------------------------------------------------------- -.\" -.\" 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 . diff --git a/sys-utils/fsfreeze.8 b/sys-utils/fsfreeze.8 deleted file mode 100644 index cbde489ad1..0000000000 --- a/sys-utils/fsfreeze.8 +++ /dev/null @@ -1,87 +0,0 @@ -.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/. diff --git a/sys-utils/fstab.5 b/sys-utils/fstab.5 deleted file mode 100644 index 2bee712d66..0000000000 --- a/sys-utils/fstab.5 +++ /dev/null @@ -1,251 +0,0 @@ -.\" 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 :, 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=