man2/*: ffix: change '-' to '\-' for options

Change '-' to '\-' for the prefix of names to indicate an option.

Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Bjarni Ingi Gislason 2020-07-01 22:08:50 +00:00 committed by Michael Kerrisk
parent 8ef1d3d11d
commit 2c1acf16da
9 changed files with 12 additions and 12 deletions

View File

@ -146,5 +146,5 @@ boot parameter.
.\".PP
.\" requires CONFIG_HUGETLB_PAGE (under "Processor type and features")
.\" and CONFIG_HUGETLBFS (under "Filesystems").
.\" mount -t hugetlbfs hugetlbfs /huge
.\" mount \-t hugetlbfs hugetlbfs /huge
.\" SHM_HUGETLB

View File

@ -203,9 +203,9 @@ and then listing the attributes with the example program.
.in +4n
.EX
$ \fBtouch /tmp/foo\fP
$ \fBsetfattr -n user.fred -v chocolate /tmp/foo\fP
$ \fBsetfattr -n user.frieda -v bar /tmp/foo\fP
$ \fBsetfattr -n user.empty /tmp/foo\fP
$ \fBsetfattr \-n user.fred \-v chocolate /tmp/foo\fP
$ \fBsetfattr \-n user.frieda \-v bar /tmp/foo\fP
$ \fBsetfattr \-n user.empty /tmp/foo\fP
$ \fB./listxattr /tmp/foo\fP
user.fred: chocolate
user.frieda: bar

View File

@ -66,9 +66,9 @@ The newly created directory will be owned by the effective user ID of the
process.
If the directory containing the file has the set-group-ID
bit set, or if the filesystem is mounted with BSD group semantics
.RI ( "mount -o bsdgroups"
.RI ( "mount \-o bsdgroups"
or, synonymously
.IR "mount -o grpid" ),
.IR "mount \-o grpid" ),
the new directory will inherit the group ownership from its parent;
otherwise it will be owned by the effective group ID of the process.
.PP

View File

@ -1192,7 +1192,7 @@ does not support
refers to a regular file that is too large to be opened.
The usual scenario here is that an application compiled
on a 32-bit platform without
.I -D_FILE_OFFSET_BITS=64
.I \-D_FILE_OFFSET_BITS=64
tried to open a file whose size exceeds
.I (1<<31)-1
bytes;

View File

@ -2270,7 +2270,7 @@ to the tracee after
returns.
This is an ordinary signal (similar to one which can be
generated by
.IR "kill -TRAP" ),
.IR "kill \-TRAP" ),
not a special kind of ptrace-stop.
Employing
.B PTRACE_GETSIGINFO

View File

@ -324,7 +324,7 @@ system has two cores, each with two CPUs:
.PP
.in +4n
.EX
$ \fBlscpu | egrep -i 'core.*:|socket'\fP
$ \fBlscpu | egrep \-i 'core.*:|socket'\fP
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1

View File

@ -940,7 +940,7 @@ numbers on this architecture:
.PP
.in +4n
.EX
$ \fBuname -m\fP
$ \fBuname \-m\fP
x86_64
$ \fBsyscall_nr() {
cat /usr/src/linux/arch/x86/syscalls/syscall_64.tbl | \e

View File

@ -432,7 +432,7 @@ or
.IR blkcnt_t .
This error can occur when, for example,
an application compiled on a 32-bit platform without
.I -D_FILE_OFFSET_BITS=64
.I \-D_FILE_OFFSET_BITS=64
calls
.BR stat ()
on a file whose size exceeds

View File

@ -474,7 +474,7 @@ new shell are in separate mount namespaces:
.EX
$ \fBreadlink /proc/$$/ns/mnt\fP
mnt:[4026531840]
$ \fBsudo ./unshare -m /bin/bash\fP
$ \fBsudo ./unshare \-m /bin/bash\fP
# \fBreadlink /proc/$$/ns/mnt\fP
mnt:[4026532325]
.EE