Use a single-font-style macro (".B", ".I") for a single argument.
Remove unneeded quotation marks (").
The output from "nroff" and "groff" is unchanged, except for the font
style of an option.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man7/math_error.7 | 2 +-
man7/mount_namespaces.7 | 128 ++++++++++++++++++++--------------------
man7/mq_overview.7 | 16 ++---
3 files changed, 73 insertions(+), 73 deletions(-)
diff --git a/man7/math_error.7 b/man7/math_error.7
index d4f8ca5f1..1a07a2318 100644
--- a/man7/math_error.7
+++ b/man7/math_error.7
@@ -38,7 +38,7 @@ most library functions indicate this fact by returning a special value
(e.g., \-1 or NULL).
Because they typically return a floating-point number,
the mathematical functions declared in
-.IR <math.h>
+.I <math.h>
indicate an error using other mechanisms.
There are two error-reporting mechanisms:
the older one sets
diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7
index 781817d5f..d2c094925 100644
--- a/man7/mount_namespaces.7
+++ b/man7/mount_namespaces.7
@@ -39,11 +39,11 @@ The views provided by the
.IR /proc/[pid]/mounts ,
.IR /proc/[pid]/mountinfo ,
and
-.IR /proc/[pid]/mountstats
+.I /proc/[pid]/mountstats
files (all described in
.BR proc (5))
correspond to the mount namespace in which the process with the PID
-.IR [pid]
+.I [pid]
resides.
(All of the processes that reside in the same mount namespace
will see the same view in these files.)
@@ -53,7 +53,7 @@ When a process creates a new mount namespace using
or
.BR unshare (2)
with the
-.BR CLONE_NEWNS
+.B CLONE_NEWNS
flag, the mount point list for the new namespace is a
.I copy
of the caller's mount point list.
@@ -144,7 +144,7 @@ This feature allows for automatic, controlled propagation of mount and unmount
.I events
between namespaces
(or, more precisely, between the members of a
-.IR "peer group"
+.I peer group
that are propagating events to one another).
.PP
Each mount point is marked (via
@@ -152,7 +152,7 @@ Each mount point is marked (via
as having one of the following
.IR "propagation types" :
.TP
-.BR MS_SHARED
+.B MS_SHARED
This mount point shares events with members of a peer group.
Mount and unmount events immediately under this mount point will propagate
to the other mount points that are members of the peer group.
@@ -162,11 +162,11 @@ under all of the other mount points in the peer group.
Conversely, mount and unmount events that take place under
peer mount points will propagate to this mount point.
.TP
-.BR MS_PRIVATE
+.B MS_PRIVATE
This mount point is private; it does not have a peer group.
Mount and unmount events do not propagate into or out of this mount point.
.TP
-.BR MS_SLAVE
+.B MS_SLAVE
Mount and unmount events propagate into this mount point from
a (master) shared peer group.
Mount and unmount events under this mount point do not propagate to any peer.
@@ -176,21 +176,21 @@ while at the same time sharing mount and unmount events
with a peer group of which it is a member.
(More precisely, one peer group can be the slave of another peer group.)
.TP
-.BR MS_UNBINDABLE
+.B MS_UNBINDABLE
This is like a private mount,
and in addition this mount can't be bind mounted.
Attempts to bind mount this mount
.RB ( mount (2)
with the
-.BR MS_BIND
+.B MS_BIND
flag) will fail.
.IP
When a recursive bind mount
.RB ( mount (2)
with the
-.BR MS_BIND
+.B MS_BIND
and
-.BR MS_REC
+.B MS_REC
flags) is performed on a directory subtree,
any bind mounts within the subtree are automatically pruned
(i.e., not replicated)
@@ -217,7 +217,7 @@ the propagation type that is in effect for the
of the mount point.
.PP
Members are added to a
-.IR "peer group"
+.I peer group
when a mount point is marked as shared and either:
.IP * 3
the mount point is replicated during the creation of a new mount namespace; or
@@ -265,23 +265,23 @@ This mount is a slave to shared peer group
This mount is a slave and receives propagation from shared peer group
.IR X .
This tag will always appear in conjunction with a
-.IR master:X
+.I master:X
tag.
Here,
-.IR X
+.I X
is the closest dominant peer group under the process's root directory.
If
-.IR X
+.I X
is the immediate master of the mount,
or if there is no dominant peer group under the same root,
then only the
-.IR master:X
+.I master:X
field is present and not the
-.IR propagate_from:X
+.I propagate_from:X
field.
For further details, see below.
.TP
-.IR unbindable
+.I unbindable
This is an unbindable mount.
.PP
If none of the above tags is present, then this is a private mount.
@@ -302,18 +302,18 @@ sh1# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP
.in
.PP
From the
-.IR /proc/self/mountinfo
+.I /proc/self/mountinfo
output, we see that
-.IR /mntS
+.I /mntS
is a shared mount in peer group 1, and that
-.IR /mntP
+.I /mntP
has no optional tags, indicating that it is a private mount.
The first two fields in each record in this file are the unique
ID for this mount, and the mount ID of the parent mount.
We can further inspect this file to see that the parent mount point of
-.IR /mntS
+.I /mntS
and
-.IR /mntP
+.I /mntP
is the root directory,
.IR / ,
which is mounted as private:
@@ -343,7 +343,7 @@ mount points.
These new mount points maintain the same propagation types,
but have unique mount IDs.
(The
-.IR \-\-propagation\ unchanged
+.B \-\-propagation\ unchanged
option prevents
.BR unshare (1)
from marking all mounts as private when creating a new mount namespace,
@@ -351,9 +351,9 @@ from marking all mounts as private when creating a new mount namespace,
which it does by default.)
.PP
In the second terminal, we then create submounts under each of
-.IR /mntS
+.I /mntS
and
-.IR /mntP
+.I /mntP
and inspect the set-up:
.PP
.in +4n
@@ -371,17 +371,17 @@ sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP
.in
.PP
From the above, it can be seen that
-.IR /mntS/a
+.I /mntS/a
was created as shared (inheriting this setting from its parent mount) and
-.IR /mntP/b
+.I /mntP/b
was created as a private mount.
.PP
Returning to the first terminal and inspecting the set-up,
we see that the new mount created under the shared mount point
-.IR /mntS
+.I /mntS
propagated to its peer mount (in the initial mount namespace),
but the new mount created under the private mount point
-.IR /mntP
+.I /mntP
did not propagate:
.PP
.in +4n
@@ -440,12 +440,12 @@ sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP
.in
.PP
From the above output, we see that
-.IR /mntY
+.I /mntY
is now a slave mount that is receiving propagation events from
the shared peer group with the ID 2.
.PP
Continuing in the new namespace, we create submounts under each of
-.IR /mntX
+.I /mntX
and
.IR /mntY :
.PP
@@ -460,10 +460,10 @@ sh2# \fBmount /dev/sda5 /mntY/b\fP
.PP
When we inspect the state of the mount points in the new mount namespace,
we see that
-.IR /mntX/a
+.I /mntX/a
was created as a new shared mount
(inheriting the "shared" setting from its parent mount) and
-.IR /mntY/b
+.I /mntY/b
was created as a private mount:
.PP
.in +4n
@@ -478,11 +478,11 @@ sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP
.PP
Returning to the first terminal (in the initial mount namespace),
we see that the mount
-.IR /mntX/a
+.I /mntX/a
propagated to the peer (the shared
.IR /mntX ),
but the mount
-.IR /mntY/b
+.I /mntY/b
was not propagated:
.PP
.in +4n
@@ -495,7 +495,7 @@ sh1# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP
.in
.PP
Now we create a new mount point under
-.IR /mntY
+.I /mntY
in the first shell:
.PP
.in +4n
@@ -585,11 +585,11 @@ we start to see the explosion problem:
Under
.IR /home/henry ,
we have not only recursively added the
-.IR /mntX
+.I /mntX
and
-.IR /mntY
+.I /mntY
mounts, but also the recursive mounts of those directories under
-.IR /home/cecilia
+.I /home/cecilia
that were created in the previous step.
Upon repeating the step for a third user,
it becomes obvious that the explosion is exponential in nature:
@@ -686,7 +686,7 @@ under each user's directory:
.SS Propagation type transitions
The following table shows the effect that applying a new propagation type
(i.e.,
-.IR "mount \-\-make\-xxxx")
+.IR "mount \-\-make\-xxxx" )
has on the existing propagation type of a mount point.
The rows correspond to existing propagation types,
and the columns are the new propagation settings.
@@ -730,7 +730,7 @@ is a subdirectory path under the mount point
The propagation type of the resulting mount,
.IR B/b ,
depends on the propagation types of the mount points
-.IR A
+.I A
and
.IR B ,
and is summarized in the following table.
@@ -770,7 +770,7 @@ is a subdirectory path under the mount point
The propagation type of the resulting mount,
.IR B/b ,
depends on the propagation types of the mount points
-.IR A
+.I A
and
.IR B ,
and is summarized in the following table.
@@ -836,7 +836,7 @@ and do not have submounts under them are unmounted.
The
.I propagate_from:X
tag is shown in the optional fields of a
-.IR /proc/[pid]/mountinfo
+.I /proc/[pid]/mountinfo
record in cases where a process can't see a slave's immediate master
(i.e., the pathname of the master is not reachable from
the filesystem root directory)
@@ -852,18 +852,18 @@ and
Then the
.BR chroot (1)
command is used to make the
-.IR /tmp/etc
+.I /tmp/etc
mount point unreachable from the root directory,
creating a situation where the master of
-.IR /mnt/tmp/etc
+.I /mnt/tmp/etc
is not reachable from the (new) root directory of the process.
.PP
First, we bind mount the root directory onto
-.IR /mnt
+.I /mnt
and then bind mount
-.IR /proc
+.I /proc
at
-.IR /mnt/proc
+.I /mnt/proc
so that after the later
.BR chroot (1)
the
@@ -880,7 +880,7 @@ in the chroot-ed environment.
.in
.PP
Next, we ensure that the
-.IR /mnt
+.I /mnt
mount is a shared mount in a new peer group (with no peers):
.PP
.in +4n
@@ -894,7 +894,7 @@ mount is a shared mount in a new peer group (with no peers):
.in
.PP
Next, we bind mount
-.IR /mnt/etc
+.I /mnt/etc
onto
.IR /tmp/etc :
.PP
@@ -911,11 +911,11 @@ onto
.PP
Initially, these two mount points are in the same peer group,
but we then make the
-.IR /tmp/etc
+.I /tmp/etc
a slave of
.IR /mnt/etc ,
and then make
-.IR /tmp/etc
+.I /tmp/etc
shared as well,
so that it can propagate events to the next slave in the chain:
.PP
@@ -931,12 +931,12 @@ so that it can propagate events to the next slave in the chain:
.in
.PP
Then we bind mount
-.IR /tmp/etc
+.I /tmp/etc
onto
.IR /mnt/tmp/etc .
Again, the two mount points are initially in the same peer group,
but we then make
-.IR /mnt/tmp/etc
+.I /mnt/tmp/etc
a slave of
.IR /tmp/etc :
.PP
@@ -954,7 +954,7 @@ a slave of
.in
.PP
From the above, we see that
-.IR /mnt
+.I /mnt
is the master of the slave
.IR /tmp/etc ,
which in turn is the master of the slave
@@ -963,7 +963,7 @@ which in turn is the master of the slave
We then
.BR chroot (1)
to the
-.IR /mnt
+.I /mnt
directory, which renders the mount with ID 267 unreachable
from the (new) root directory:
.PP
@@ -988,11 +988,11 @@ we see the following:
Above, we see that the mount with ID 273
is a slave whose master is the peer group 105.
The mount point for that master is unreachable, and so a
-.IR propagate_from
+.I propagate_from
tag is displayed, indicating that the closest dominant peer group
(i.e., the nearest reachable mount in the slave chain)
is the peer group with the ID 102 (corresponding to the
-.IR /mnt
+.I /mnt
mount point before the
.BR chroot (1)
was performed.
@@ -1017,12 +1017,12 @@ But see also NOTES.
Notwithstanding the fact that the default propagation type
for new mount points is in many cases
.BR MS_PRIVATE ,
-.BR MS_SHARED
+.B MS_SHARED
is typically more useful.
For this reason,
.BR systemd (1)
automatically remounts all mount points as
-.BR MS_SHARED
+.B MS_SHARED
on system startup.
Thus, on most modern systems, the default propagation type is in practice
.BR MS_SHARED .
@@ -1034,7 +1034,7 @@ the goal is commonly to provide full isolation of the mount points
in the new namespace,
.BR unshare (1)
(since
-.IR util-linux
+.I util-linux
version 2.27) in turn reverses the step performed by
.BR systemd (1),
by making all mount points private in the new namespace.
@@ -1045,7 +1045,7 @@ performs the equivalent of the following in the new mount namespace:
mount \-\-make\-rprivate /
.PP
To prevent this, one can use the
-.IR "\-\-propagation\ unchanged"
+.B \-\-propagation\ unchanged
option to
.BR unshare (1).
.PP
@@ -1067,5 +1067,5 @@ see
.BR user_namespaces (7),
.BR findmnt (8)
.PP
-.IR Documentation/filesystems/sharedsubtree.txt
+.I Documentation/filesystems/sharedsubtree.txt
in the kernel source tree.
diff --git a/man7/mq_overview.7 b/man7/mq_overview.7
index d87d21f4c..fb4b680f9 100644
--- a/man7/mq_overview.7
+++ b/man7/mq_overview.7
@@ -44,7 +44,7 @@ which is used to refer to the open message queue in later calls.
Each message queue is identified by a name of the form
.IR /somename ;
that is, a null-terminated string of up to
-.BI NAME_MAX
+.B NAME_MAX
(i.e., 255) characters consisting of an initial slash,
followed by one or more characters, none of which are slashes.
Two processes can operate on the same queue by passing the same name to
@@ -154,7 +154,7 @@ The minimum and maximum are as for
A new queue's default
.I mq_maxmsg
value will be the smaller of
-.IR msg_default
+.I msg_default
and
.IR msg_max .
Up until Linux 2.6.28, the default
@@ -182,19 +182,19 @@ The
limit is ignored for privileged processes
.RB ( CAP_SYS_RESOURCE ),
but the
-.BR HARD_MSGMAX
+.B HARD_MSGMAX
ceiling is nevertheless imposed.
.IP
The definition of
-.BR HARD_MSGMAX
+.B HARD_MSGMAX
has changed across kernel versions:
.RS
.IP * 3
Up to Linux 2.6.32:
-.IR "131072\ /\ sizeof(void\ *)"
+.I 131072\ /\ sizeof(void\ *)
.IP *
Linux 2.6.33 to 3.4:
-.IR "(32768\ *\ sizeof(void\ *) / 4)"
+.I (32768\ *\ sizeof(void\ *) / 4)
.IP *
Since Linux 3.5:
.\" commit 5b5c4d1a1440e94994c73dddbad7be0676cd8b9a
@@ -213,7 +213,7 @@ The default value for this file is 8192 (bytes).
The minimum and maximum are as for
.IR /proc/sys/fs/mqueue/msgsize_max .
If
-.IR msgsize_default
+.I msgsize_default
exceeds
.IR msgsize_max ,
a new queue's default
@@ -258,7 +258,7 @@ The
limit is ignored for privileged process
.RB ( CAP_SYS_RESOURCE ),
but, since Linux 3.5, the
-.BR HARD_MSGSIZEMAX
+.B HARD_MSGSIZEMAX
ceiling is enforced for privileged processes.
.TP
.I /proc/sys/fs/mqueue/queues_max
--
2.20.1
