aboutsummaryrefslogtreecommitdiffstats
path: root/man7
diff options
context:
space:
mode:
Diffstat (limited to 'man7')
-rw-r--r--man7/bootparam.72
-rw-r--r--man7/capabilities.74
-rw-r--r--man7/cgroups.74
-rw-r--r--man7/cpuset.74
-rw-r--r--man7/fanotify.74
-rw-r--r--man7/inotify.72
-rw-r--r--man7/ip.74
-rw-r--r--man7/keyrings.72
-rw-r--r--man7/locale.72
-rw-r--r--man7/man-pages.78
-rw-r--r--man7/man.78
-rw-r--r--man7/numa.72
-rw-r--r--man7/packet.74
-rw-r--r--man7/path_resolution.78
-rw-r--r--man7/pid_namespaces.74
-rw-r--r--man7/spufs.72
-rw-r--r--man7/symlink.76
-rw-r--r--man7/tcp.72
-rw-r--r--man7/time_namespaces.74
-rw-r--r--man7/udplite.72
-rw-r--r--man7/unicode.74
-rw-r--r--man7/uri.74
-rw-r--r--man7/user-keyring.74
-rw-r--r--man7/user-session-keyring.74
-rw-r--r--man7/user_namespaces.78
-rw-r--r--man7/utf-8.74
-rw-r--r--man7/vdso.78
-rw-r--r--man7/x25.72
-rw-r--r--man7/xattr.72
29 files changed, 59 insertions, 59 deletions
diff --git a/man7/bootparam.7 b/man7/bootparam.7
index 7a8f24dcfd..b9ca2ac265 100644
--- a/man7/bootparam.7
+++ b/man7/bootparam.7
@@ -299,7 +299,7 @@ will clear the counters.
.SS Boot arguments for ramdisk use
(Only if the kernel was compiled with
.BR CONFIG_BLK_DEV_RAM .)
-In general it is a bad idea to use a ramdisk under Linux\(emthe
+In general it is a bad idea to use a ramdisk under Linux\[em]the
system will use available memory more efficiently itself.
But while booting,
it is often useful to load the floppy contents into a
diff --git a/man7/capabilities.7 b/man7/capabilities.7
index cb0725d25a..7c4268adfe 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -1290,9 +1290,9 @@ a process with UID 0 (root) executes a program and
when a set-user-ID-root program is executed.
.PP
After having performed any changes to the process effective ID that
-were triggered by the set-user-ID mode bit of the binary\(eme.g.,
+were triggered by the set-user-ID mode bit of the binary\[em]e.g.,
switching the effective user ID to 0 (root) because
-a set-user-ID-root program was executed\(emthe
+a set-user-ID-root program was executed\[em]the
kernel calculates the file capability sets as follows:
.IP (1) 5
If the real or effective user ID of the process is 0 (root),
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index 3206bc5d32..cd68ff77d7 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -840,7 +840,7 @@ other children.
The "no internal processes" rule is in fact more subtle than stated above.
More precisely, the rule is that a (nonroot) cgroup can't both
(1) have member processes, and
-(2) distribute resources into child cgroups\(emthat is, have a nonempty
+(2) distribute resources into child cgroups\[em]that is, have a nonempty
.I cgroup.subtree_control
file.
Thus, it
@@ -1632,7 +1632,7 @@ cgroup,
.IR x ,
can revert to the type
.I domain
-if the above conditions no longer hold true\(emthat is, if all
+if the above conditions no longer hold true\[em]that is, if all
.I threaded
child cgroups of
.I x
diff --git a/man7/cpuset.7 b/man7/cpuset.7
index 4d3132dc26..57a21f62ce 100644
--- a/man7/cpuset.7
+++ b/man7/cpuset.7
@@ -531,8 +531,8 @@ single read, instead of having to read and accumulate results
for a period of time.
.IP \(bu
Because this meter is per-cpuset rather than per-process,
-the batch scheduler can obtain the key information\(emmemory
-pressure in a cpuset\(emwith a single read, rather than having to
+the batch scheduler can obtain the key information\[em]memory
+pressure in a cpuset\[em]with a single read, rather than having to
query and accumulate results over all the (dynamically changing)
set of processes in the cpuset.
.PP
diff --git a/man7/fanotify.7 b/man7/fanotify.7
index 01872057e4..43580d347c 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -1236,8 +1236,8 @@ a command-line argument
and waits until an event of type
.B FAN_CREATE
has occurred.
-The event mask indicates which type of filesystem object\(emeither
-a file or a directory\(emwas created.
+The event mask indicates which type of filesystem object\[em]either
+a file or a directory\[em]was created.
Once all events have been read from the buffer and processed accordingly,
the program simply terminates.
.PP
diff --git a/man7/inotify.7 b/man7/inotify.7
index f755548f87..265b73f524 100644
--- a/man7/inotify.7
+++ b/man7/inotify.7
@@ -185,7 +185,7 @@ File was accessed (e.g.,
.BR execve (2)).
.TP
.BR IN_ATTRIB " (*)"
-Metadata changed\(emfor example, permissions (e.g.,
+Metadata changed\[em]for example, permissions (e.g.,
.BR chmod (2)),
timestamps (e.g.,
.BR utimensat (2)),
diff --git a/man7/ip.7 b/man7/ip.7
index f69af1b322..2b689b22f8 100644
--- a/man7/ip.7
+++ b/man7/ip.7
@@ -399,7 +399,7 @@ structure similar to
.BR IP_ADD_MEMBERSHIP .
.TP
.BR IP_DROP_SOURCE_MEMBERSHIP " (since Linux 2.4.22 / 2.5.68)"
-Leave a source-specific group\(emthat is, stop receiving data from
+Leave a source-specific group\[em]that is, stop receiving data from
a given multicast group that come from a given source.
If the application has subscribed to multiple sources within
the same group, data from the remaining sources will still be delivered.
@@ -1143,7 +1143,7 @@ IP forwarding can be also set on a per-interface basis.
.IR ip_local_port_range " (since Linux 2.2)"
.\" Precisely: since Linux 2.1.68
This file contains two integers that define the default local port range
-allocated to sockets that are not explicitly bound to a port number\(emthat
+allocated to sockets that are not explicitly bound to a port number\[em]that
is, the range used for
.IR "ephemeral ports" .
An ephemeral port is allocated to a socket in the following circumstances:
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 7851277558..772abd4eda 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -68,7 +68,7 @@ Much as files do,
each key has an owning user ID, an owning group ID, and a security label.
Each key also has a set of permissions,
though there are more than for a normal UNIX file,
-and there is an additional category\(empossessor\(embeyond the usual user,
+and there is an additional category\[em]possessor\[em]beyond the usual user,
group, and other (see
.IR Possession ,
below).
diff --git a/man7/locale.7 b/man7/locale.7
index b6567e8fdd..02fdd57f48 100644
--- a/man7/locale.7
+++ b/man7/locale.7
@@ -163,7 +163,7 @@ elements, which return strings such as "Herr" and "Frau"
.TP
.B LC_NUMERIC
This category determines the formatting rules used for nonmonetary
-numeric values\(emfor example,
+numeric values\[em]for example,
the thousands separator and the radix character
(a period in most English-speaking countries,
but a comma in many other regions).
diff --git a/man7/man-pages.7 b/man7/man-pages.7
index e5b1112832..51b0b1d422 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -463,8 +463,8 @@ Hyphenation of individual page names can be prevented
by preceding words with the string "\e%".
.IP
Given the distributed, autonomous nature of FOSS projects
-and their documentation, it is sometimes necessary\(emand in many cases
-desirable\(emthat the SEE ALSO section includes references to
+and their documentation, it is sometimes necessary\[em]and in many cases
+desirable\[em]that the SEE ALSO section includes references to
manual pages provided by other projects.
.SH FORMATTING AND WORDING CONVENTIONS
The following subsections note some details for preferred formatting and
@@ -993,8 +993,8 @@ parenthetical asides (e.g., like this one).
Always include periods in such abbreviations, as shown here.
In addition, "e.g." and "i.e." should always be followed by a comma.
.SS Em-dashes
-The way to write an em-dash\(emthe glyph that appears
-at either end of this subphrase\(emin *roff is with the macro "\e[em]".
+The way to write an em-dash\[em]the glyph that appears
+at either end of this subphrase\[em]in *roff is with the macro "\e[em]".
(On an ASCII terminal, an em-dash typically renders as two hyphens,
but in other typographical contexts it renders as a long dash.)
Em-dashes should be written
diff --git a/man7/man.7 b/man7/man.7
index fcabbf1fae..65b2c9a669 100644
--- a/man7/man.7
+++ b/man7/man.7
@@ -483,15 +483,15 @@ The Sun macro
.B TX
is not implemented.
.\" .SH AUTHORS
-.\" .IP \(em 3m
+.\" .IP \[em] 3m
.\" James Clark (jjc@jclark.com) wrote the implementation of the macro package.
-.\" .IP \(em
+.\" .IP \[em]
.\" Rickard E. Faith (faith@cs.unc.edu) wrote the initial version of
.\" this manual page.
-.\" .IP \(em
+.\" .IP \[em]
.\" Jens Schweikhardt (schweikh@noc.fdn.de) wrote the Linux Man-Page Mini-HOWTO
.\" (which influenced this manual page).
-.\" .IP \(em
+.\" .IP \[em]
.\" David A. Wheeler (dwheeler@ida.org) heavily modified this
.\" manual page, such as adding detailed information on sections and macros.
.SH SEE ALSO
diff --git a/man7/numa.7 b/man7/numa.7
index 81fd51c6fd..f5a314b565 100644
--- a/man7/numa.7
+++ b/man7/numa.7
@@ -37,7 +37,7 @@ This file displays information about a process's
NUMA memory policy and allocation.
.PP
Each line contains information about a memory range used by the process,
-displaying\(emamong other information\(emthe effective memory policy for
+displaying\[em]among other information\[em]the effective memory policy for
that memory range and on which nodes the pages have been allocated.
.PP
.I numa_maps
diff --git a/man7/packet.7 b/man7/packet.7
index c427619988..4bfd55d9f8 100644
--- a/man7/packet.7
+++ b/man7/packet.7
@@ -492,9 +492,9 @@ By default, packets sent through packet sockets pass through the kernel's
qdisc (traffic control) layer, which is fine for the vast majority of use
cases.
For traffic generator appliances using packet sockets
-that intend to brute-force flood the network\(emfor example,
+that intend to brute-force flood the network\[em]for example,
to test devices under load in a similar
-fashion to pktgen\(emthis layer can be bypassed by setting
+fashion to pktgen\[em]this layer can be bypassed by setting
this integer option to 1.
A side effect is that packet buffering in the qdisc layer is avoided,
which will lead to increased drops when network
diff --git a/man7/path_resolution.7 b/man7/path_resolution.7
index ec9524d289..74edb6b5f1 100644
--- a/man7/path_resolution.7
+++ b/man7/path_resolution.7
@@ -22,7 +22,7 @@ with the
flag set.
.PP
A process may get an entirely private mount namespace in case
-it\(emor one of its ancestors\(emwas started by an invocation of the
+it\[em]or one of its ancestors\[em]was started by an invocation of the
.BR clone (2)
system call that had the
.B CLONE_NEWNS
@@ -31,7 +31,7 @@ This handles the \[aq]/\[aq] part of the pathname.
.PP
If the pathname does not start with the \[aq]/\[aq] character, the starting
lookup directory of the resolution process is the current working directory of
-the process \(em or in the case of
+the process \[em] or in the case of
.BR openat (2)-style
system calls, the
.I dfd
@@ -125,9 +125,9 @@ The lookup of the final component of the pathname goes just like
that of all other components, as described in the previous step,
with two differences: (i) the final component need not be a
directory (at least as far as the path resolution process is
-concerned\(emit may have to be a directory, or a nondirectory, because of
+concerned\[em]it may have to be a directory, or a nondirectory, because of
the requirements of the specific system call), and (ii) it
-is not necessarily an error if the component is not found\(emmaybe
+is not necessarily an error if the component is not found\[em]maybe
we are just creating it.
The details on the treatment
of the final entry are described in the manual pages of the specific
diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index 05415d88a7..d329854854 100644
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -82,8 +82,8 @@ and prevents other members of the PID namespace from
accidentally killing the "init" process.
.PP
Likewise, a process in an ancestor namespace
-can\(emsubject to the usual permission checks described in
-.BR kill (2)\(emsend
+can\[em]subject to the usual permission checks described in
+.BR kill (2)\[em]send
signals to the "init" process of a child PID namespace only
if the "init" process has established a handler for that signal.
(Within the handler, the
diff --git a/man7/spufs.7 b/man7/spufs.7
index 2fd2d13d07..39fdf583a0 100644
--- a/man7/spufs.7
+++ b/man7/spufs.7
@@ -291,7 +291,7 @@ whenever space is available for writing.
.TP
.IR /mbox_stat ", " /ibox_stat ", " /wbox_stat
These are read-only files that contain the length of the current
-queue of each mailbox\(emthat is, how many words can be read from
+queue of each mailbox\[em]that is, how many words can be read from
.IR mbox " or " ibox
or how many words can be written to
.I wbox
diff --git a/man7/symlink.7 b/man7/symlink.7
index ac758142a4..1ddc03976d 100644
--- a/man7/symlink.7
+++ b/man7/symlink.7
@@ -297,11 +297,11 @@ which performs a tree traversal, is not.
(The latter is described in the third area, below.)
.PP
If it is explicitly intended that the command operate on the symbolic
-link instead of following the symbolic link\(emfor example, it is desired that
+link instead of following the symbolic link\[em]for example, it is desired that
.I "chown slink"
change the ownership of the file that
.I slink
-is, whether it is a symbolic link or not\(emthen the
+is, whether it is a symbolic link or not\[em]then the
.I \-h
option should be used.
In the above example,
@@ -331,7 +331,7 @@ The
command is also an exception to this rule.
For compatibility with historic systems (when
.BR ls (1)
-is not doing a tree walk\(emthat is,
+is not doing a tree walk\[em]that is,
.I \-R
option is not specified),
the
diff --git a/man7/tcp.7 b/man7/tcp.7
index 1d8a26818e..557660293d 100644
--- a/man7/tcp.7
+++ b/man7/tcp.7
@@ -1498,7 +1498,7 @@ level
socket option.
When this option is enabled, all incoming
errors are immediately passed to the user program.
-Use this option with care \(em it makes TCP less tolerant to routing
+Use this option with care \[em] it makes TCP less tolerant to routing
changes and other normal network conditions.
.SH ERRORS
.TP
diff --git a/man7/time_namespaces.7 b/man7/time_namespaces.7
index a8006e4056..1316bff091 100644
--- a/man7/time_namespaces.7
+++ b/man7/time_namespaces.7
@@ -14,8 +14,8 @@ Time namespaces virtualize the values of two system clocks:
.B CLOCK_MONOTONIC_COARSE
and
.BR CLOCK_MONOTONIC_RAW ),
-a nonsettable clock that represents monotonic time since\(emas
-described by POSIX\(em"some unspecified point in the past".
+a nonsettable clock that represents monotonic time since\[em]as
+described by POSIX\[em]"some unspecified point in the past".
.IP \(bu
.B CLOCK_BOOTTIME
(and likewise
diff --git a/man7/udplite.7 b/man7/udplite.7
index db5a901038..6e23303405 100644
--- a/man7/udplite.7
+++ b/man7/udplite.7
@@ -33,7 +33,7 @@ If this option is not set, the only difference from UDP is
in using a different IP protocol identifier (IANA number 136).
.PP
The UDP-Lite implementation is a full extension of
-.BR udp (7)\(emthat
+.BR udp (7)\[em]that
is, it shares the same API and API behavior, and in addition
offers two socket options to control the checksum coverage.
.SS Address format
diff --git a/man7/unicode.7 b/man7/unicode.7
index 2e1a605e1e..1811de9898 100644
--- a/man7/unicode.7
+++ b/man7/unicode.7
@@ -196,8 +196,8 @@ and plane 16 (Supplementary Private Use Area-B, range
0x100000 to 0x10fffd).
.SS Literature
.IP \(bu 3
-Information technology \(em Universal Multiple-Octet Coded Character
-Set (UCS) \(em Part 1: Architecture and Basic Multilingual Plane.
+Information technology \[em] Universal Multiple-Octet Coded Character
+Set (UCS) \[em] Part 1: Architecture and Basic Multilingual Plane.
International Standard ISO/IEC 10646-1, International Organization
for Standardization, Geneva, 2000.
.IP
diff --git a/man7/uri.7 b/man7/uri.7
index 2767d9f12d..7528f771f6 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -523,8 +523,8 @@ the HTML 4.01 specification (section B.2) and
IETF RFC\~3986 (last paragraph of section 2.5)
recommend the following approach:
.IP (1) 5
-translate the character sequences into UTF-8 (IETF RFC\~3629)\(emsee
-.BR utf\-8 (7)\(emand
+translate the character sequences into UTF-8 (IETF RFC\~3629)\[em]see
+.BR utf\-8 (7)\[em]and
then
.IP (2)
use the URI escaping mechanism, that is,
diff --git a/man7/user-keyring.7 b/man7/user-keyring.7
index a6e29c9dbd..f384774fd3 100644
--- a/man7/user-keyring.7
+++ b/man7/user-keyring.7
@@ -60,9 +60,9 @@ excepting that the keyring is destroyed when the UID record is destroyed when
the last process pinning it exits.
.PP
If it is necessary for a key associated with a user to exist beyond the UID
-record being garbage collected\(emfor example, for use by a
+record being garbage collected\[em]for example, for use by a
.BR cron (8)
-script\(emthen the
+script\[em]then the
.BR persistent\-keyring (7)
should be used instead.
.PP
diff --git a/man7/user-session-keyring.7 b/man7/user-session-keyring.7
index bd0ba3d232..edecb84aaf 100644
--- a/man7/user-session-keyring.7
+++ b/man7/user-session-keyring.7
@@ -66,8 +66,8 @@ If a user session keyring does not exist when it is accessed,
it will be created.
.PP
Rather than relying on the user session keyring,
-it is strongly recommended\(emespecially if the process
-is running as root\(emthat a
+it is strongly recommended\[em]especially if the process
+is running as root\[em]that a
.BR session\-keyring (7)
be set explicitly, for example by
.BR pam_keyinit (8).
diff --git a/man7/user_namespaces.7 b/man7/user_namespaces.7
index 8946350081..d968769dcf 100644
--- a/man7/user_namespaces.7
+++ b/man7/user_namespaces.7
@@ -35,8 +35,8 @@ but is unprivileged for operations outside the namespace.
.\"
.SS Nested namespaces, namespace membership
User namespaces can be nested;
-that is, each user namespace\(emexcept the initial ("root")
-namespace\(emhas a parent user namespace,
+that is, each user namespace\[em]except the initial ("root")
+namespace\[em]has a parent user namespace,
and can have zero or more child user namespaces.
The parent user namespace is the user namespace
of the process that creates the user namespace via a call to
@@ -431,11 +431,11 @@ that created this user namespace.
The length of the range of user IDs that is mapped between the two
user namespaces.
.PP
-System calls that return user IDs (group IDs)\(emfor example,
+System calls that return user IDs (group IDs)\[em]for example,
.BR getuid (2),
.BR getgid (2),
and the credential fields in the structure returned by
-.BR stat (2)\(emreturn
+.BR stat (2)\[em]return
the user ID (group ID) mapped into the caller's user namespace.
.PP
When a process accesses a file, its user and group IDs
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index 797481cacc..abdf6244ce 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -15,7 +15,7 @@ The Unicode 3.0 character set occupies a 16-bit code space.
The most obvious
Unicode encoding (known as UCS-2)
consists of a sequence of 16-bit words.
-Such strings can contain\(emas part of many 16-bit characters\(embytes
+Such strings can contain\[em]as part of many 16-bit characters\[em]bytes
such as \[aq]\e0\[aq] or \[aq]/\[aq], which have a
special meaning in filenames and other C library function arguments.
In addition, the majority of UNIX tools expect ASCII files and can't
@@ -25,7 +25,7 @@ UCS-2 is not a suitable external encoding of Unicode
in filenames, text files, environment variables, and so on.
The ISO 10646 Universal Character Set (UCS),
a superset of Unicode, occupies an even larger code
-space\(em31\ bits\(emand the obvious
+space\[em]31\ bits\[em]and the obvious
UCS-4 encoding for it (a sequence of 32-bit words) has the same problems.
.PP
The UTF-8 encoding of Unicode and UCS
diff --git a/man7/vdso.7 b/man7/vdso.7
index 2cb3b96361..9bfac91b13 100644
--- a/man7/vdso.7
+++ b/man7/vdso.7
@@ -69,9 +69,9 @@ One frequently used system call is
This system call is called both directly by user-space applications
as well as indirectly by
the C library.
-Think timestamps or timing loops or polling\(emall of these
+Think timestamps or timing loops or polling\[em]all of these
frequently need to know what time it is right now.
-This information is also not secret\(emany application in any
+This information is also not secret\[em]any application in any
privilege mode (root or any unprivileged user) will get the same answer.
Thus the kernel arranges for the information required to answer
this question to be placed in memory the process can access.
@@ -252,7 +252,7 @@ a fixed location in memory.
User-space applications then call directly into that region.
There is no provision for backward compatibility
beyond sniffing raw opcodes,
-but as this is an embedded CPU, it can get away with things\(emsome of the
+but as this is an embedded CPU, it can get away with things\[em]some of the
object formats it runs aren't even ELF based (they're bFLT/FLAT).
.PP
For information on this code page,
@@ -588,7 +588,7 @@ __vdso_time LINUX_2.6
.ft P
\}
.SS History
-The vDSO was originally just a single function\(emthe vsyscall.
+The vDSO was originally just a single function\[em]the vsyscall.
In older kernels, you might see that name
in a process's memory map rather than "vdso".
Over time, people realized that this mechanism
diff --git a/man7/x25.7 b/man7/x25.7
index 9cebe7cf2b..446d314cf5 100644
--- a/man7/x25.7
+++ b/man7/x25.7
@@ -29,7 +29,7 @@ X25 sockets can also be used for communication
without an intermediate X.25 network (X.25 DTE-DTE mode) as described
in ISO-8208.
.PP
-Message boundaries are preserved \(em a
+Message boundaries are preserved \[em] a
.BR read (2)
from a socket will
retrieve the same chunk of data as output with the corresponding
diff --git a/man7/xattr.7 b/man7/xattr.7
index b5057270c4..51fe4c8d72 100644
--- a/man7/xattr.7
+++ b/man7/xattr.7
@@ -21,7 +21,7 @@ associated with all inodes in the system (i.e., the
.BR stat (2)
data).
They are often used to provide additional functionality
-to a filesystem\(emfor example, additional security features such as
+to a filesystem\[em]for example, additional security features such as
Access Control Lists (ACLs) may be implemented using extended attributes.
.PP
Users with search access to a file or directory may use