Merge branch 'spelling' of https://github.com/jwilk-forks/util-linux
* 'spelling' of https://github.com/jwilk-forks/util-linux: Fix man page typos
This commit is contained in:
commit
1b0a420281
|
@ -25,7 +25,7 @@ is usually of the following form:
|
|||
.RE
|
||||
.fi
|
||||
|
||||
The device may be a block device or a image file of one, but this is not
|
||||
The device may be a block device or an image file of one, but this is not
|
||||
enforced. Expect not much fun on a character device :-).
|
||||
.PP
|
||||
The
|
||||
|
|
|
@ -38,7 +38,7 @@ sense for new devices.
|
|||
(since version 2.26)
|
||||
.B aligns the start and end of partitions
|
||||
to block-device I/O limits when relative sizes are specified, when the default
|
||||
values are used or when multiplicative suffixes (e.g MiB) are used for sizes.
|
||||
values are used or when multiplicative suffixes (e.g. MiB) are used for sizes.
|
||||
It is possible that partition size will be optimized (reduced or enlarged) due
|
||||
to alignment if the start offset is specified exactly in sectors and partition
|
||||
size relative or by multiplicative suffixes.
|
||||
|
|
|
@ -109,7 +109,7 @@ 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
|
||||
confirm to V3 and V5 UUIDs per RFC-4122.
|
||||
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 .
|
||||
|
|
|
@ -31,7 +31,7 @@
|
|||
.\" 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 an UUID from binary representation to a string
|
||||
uuid_unparse \- convert a UUID from binary representation to a string
|
||||
.SH SYNOPSIS
|
||||
.nf
|
||||
.B #include <uuid.h>
|
||||
|
|
|
@ -112,7 +112,7 @@ Create pseudo-terminal for the session. The independent terminal provides
|
|||
better security as user does not share terminal with the original
|
||||
session. This allow to avoid TIOCSTI ioctl terminal injection and another
|
||||
security attacks against terminal file descriptors. The all session is also
|
||||
possible to move to background (e.g. "su --pty - usename -c
|
||||
possible to move to background (e.g. "su --pty - username -c
|
||||
application &"). If the pseudo-terminal is enabled then su command works
|
||||
as a proxy between the sessions (copy stdin and stdout).
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
.\" The 3-Clause BSD License
|
||||
.TH UUIDPARSE "1" "2017-06-18" "util-linux" "User Commands"
|
||||
.SH NAME
|
||||
uuidparse \- an utility to parse unique identifiers
|
||||
uuidparse \- a utility to parse unique identifiers
|
||||
.SH SYNOPSIS
|
||||
.B uuidparse
|
||||
[options]
|
||||
|
|
|
@ -63,7 +63,7 @@ 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 a adjust score value of +500, for example, is roughly equivalent to
|
||||
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
|
||||
|
|
|
@ -1400,7 +1400,7 @@ independent of indices created in other instances of devpts.
|
|||
|
||||
All mounts of devpts without this
|
||||
.B newinstance
|
||||
option share the same set of pty indices (i.e legacy mode).
|
||||
option share the same set of pty indices (i.e. legacy mode).
|
||||
Each mount of devpts with the
|
||||
.B newinstance
|
||||
option has a private set of pty indices.
|
||||
|
@ -1503,7 +1503,7 @@ normal check is too inflexible. With this option you can relax it.
|
|||
.RE
|
||||
.TP
|
||||
.BI check= value
|
||||
Three different levels of pickyness can be chosen:
|
||||
Three different levels of pickiness can be chosen:
|
||||
.RS
|
||||
.TP
|
||||
.BR r [ elaxed ]
|
||||
|
@ -1714,7 +1714,7 @@ filesystem.)
|
|||
|
||||
Normal
|
||||
.I iso9660
|
||||
filenames appear in a 8.3 format (i.e., DOS-like restrictions on filename
|
||||
filenames appear in an 8.3 format (i.e., DOS-like restrictions on filename
|
||||
length), and in addition all characters are in upper case. Also there is
|
||||
no field for file ownership, protection, number of links, provision for
|
||||
block/character devices, etc.
|
||||
|
|
|
@ -111,7 +111,7 @@ Look at all the kernel information, with ram addresses:
|
|||
readprofile -av | less
|
||||
|
||||
.fi
|
||||
Browse a `freezed' profile buffer for a non current kernel:
|
||||
Browse a `frozen' profile buffer for a non current kernel:
|
||||
.nf
|
||||
readprofile -p ~/profile.freeze -m /zImage.map.gz
|
||||
|
||||
|
@ -123,7 +123,7 @@ Request profiling at 2kHz per CPU, and reset the profiling buffer:
|
|||
.SH BUGS
|
||||
.LP
|
||||
.B readprofile
|
||||
only works with an 1.3.x or newer kernel, because
|
||||
only works with a 1.3.x or newer kernel, because
|
||||
.I /proc/profile
|
||||
changed in the step from 1.2 to 1.3
|
||||
.LP
|
||||
|
|
|
@ -27,7 +27,7 @@ The default \fIprogram\fR is \fB/bin/sh\fR.
|
|||
.PP
|
||||
Since version 2.33 the
|
||||
.I arch
|
||||
comnand line argument is optional and
|
||||
command line argument is optional and
|
||||
.B setarch
|
||||
may be used to change personality flags (ADDR_LIMIT_*, SHORT_INODE, etc) without
|
||||
modification of the execution domain.
|
||||
|
|
|
@ -222,7 +222,7 @@ Swap over \fBNFS\fR may not work.
|
|||
.PP
|
||||
.B swapon
|
||||
automatically detects and rewrites a swap space signature with old software
|
||||
suspend data (e.g S1SUSPEND, S2SUSPEND, ...). The problem is that if we don't
|
||||
suspend data (e.g. S1SUSPEND, S2SUSPEND, ...). The problem is that if we don't
|
||||
do it, then we get data corruption the next time an attempt at unsuspending is
|
||||
made.
|
||||
|
||||
|
|
|
@ -56,7 +56,7 @@ offending process could even be
|
|||
.B umount
|
||||
itself - it opens libc, and libc in its turn may open for example locale
|
||||
files. A lazy unmount avoids this problem, but it may introduce another
|
||||
issues. See \fB\-\-lazy\fR description bellow.
|
||||
issues. See \fB\-\-lazy\fR description below.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.BR \-a , " \-\-all"
|
||||
|
|
|
@ -105,7 +105,7 @@ hide all unnamed columns (see --table-columns).
|
|||
.IP "\fB\-O, \-\-table-order\fP \fIcolumns\fP"
|
||||
Specify columns order on output.
|
||||
.IP "\fB\-n, \-\-table-name\fP \fIname\fP"
|
||||
Specify the table name used for JSON output. The defaout is "table".
|
||||
Specify the table name used for JSON output. The default is "table".
|
||||
.IP "\fB\-r, \-\-tree\fP \fIcolumn\fP"
|
||||
Specify column to use tree-like output. Note that the circular dependencies and
|
||||
another anomalies in child and parent relation are silently ignored.
|
||||
|
|
Loading…
Reference in New Issue