Use a single-font-style macro (".B", ".I") for a single argument.
The output from "nroff" and "groff" is unchanged.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man7/namespaces.7 | 26 ++++++++++-----------
man7/netlink.7 | 10 ++++----
man7/numa.7 | 4 ++--
man7/packet.7 | 48 +++++++++++++++++++--------------------
man7/persistent-keyring.7 | 10 ++++----
man7/pid_namespaces.7 | 26 ++++++++++-----------
man7/pipe.7 | 16 ++++++-------
man7/pkeys.7 | 10 ++++----
man7/pty.7 | 2 +-
9 files changed, 76 insertions(+), 76 deletions(-)
diff --git a/man7/namespaces.7 b/man7/namespaces.7
index 1c3903474..9781df0d0 100644
--- a/man7/namespaces.7
+++ b/man7/namespaces.7
@@ -80,7 +80,7 @@ The
system call allows the calling process to join an existing namespace.
The namespace to join is specified via a file descriptor that refers to
one of the
-.IR /proc/[pid]/ns
+.I /proc/[pid]/ns
files described below.
.TP
.BR unshare (2)
@@ -108,7 +108,7 @@ Creation of new namespaces using
and
.BR unshare (2)
in most cases requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability, since, in the new namespace,
the creator will have the power to change global resources
that are visible to other processes that are subsequently created in,
@@ -120,7 +120,7 @@ no privilege is required to create a user namespace.
.\"
.SS The /proc/[pid]/ns/ directory
Each process has a
-.IR /proc/[pid]/ns/
+.I /proc/[pid]/ns/
.\" See commit 6b4e306aa3dc94a0545eb9279475b1ab6209a31f
subdirectory containing one entry for each namespace that
supports being manipulated by
@@ -166,7 +166,7 @@ Since Linux 3.8,
they appear as symbolic links.
If two processes are in the same namespace,
then the device IDs and inode numbers of their
-.IR /proc/[pid]/ns/xxx
+.I /proc/[pid]/ns/xxx
symbolic links will be the same; an application can check this using the
.I stat.st_dev
and
@@ -245,31 +245,31 @@ directory (which is present since Linux 4.9) expose limits
on the number of namespaces of various types that can be created.
The files are as follows:
.TP
-.IR max_cgroup_namespaces
+.I max_cgroup_namespaces
The value in this file defines a per-user limit on the number of
cgroup namespaces that may be created in the user namespace.
.TP
-.IR max_ipc_namespaces
+.I max_ipc_namespaces
The value in this file defines a per-user limit on the number of
ipc namespaces that may be created in the user namespace.
.TP
-.IR max_mnt_namespaces
+.I max_mnt_namespaces
The value in this file defines a per-user limit on the number of
mount namespaces that may be created in the user namespace.
.TP
-.IR max_net_namespaces
+.I max_net_namespaces
The value in this file defines a per-user limit on the number of
network namespaces that may be created in the user namespace.
.TP
-.IR max_pid_namespaces
+.I max_pid_namespaces
The value in this file defines a per-user limit on the number of
pid namespaces that may be created in the user namespace.
.TP
-.IR max_user_namespaces
+.I max_user_namespaces
The value in this file defines a per-user limit on the number of
user namespaces that may be created in the user namespace.
.TP
-.IR max_uts_namespaces
+.I max_uts_namespaces
The value in this file defines a per-user limit on the number of
uts namespaces that may be created in the user namespace.
.PP
@@ -432,7 +432,7 @@ a namespace into existence even though it has no member processes.
These factors include the following:
.IP * 3
An open file descriptor or a bind mount exists for the corresponding
-.IR /proc/[pid]/ns/*
+.I /proc/[pid]/ns/*
file.
.IP *
The namespace is hierarchical (i.e., a PID or user namespace),
@@ -442,7 +442,7 @@ It is a user namespace that owns one or more nonuser namespaces.
.IP *
It is a PID namespace,
and there is a process that refers to the namespace via a
-.IR /proc/[pid]/ns/pid_for_children
+.I /proc/[pid]/ns/pid_for_children
symbolic link.
.IP *
It is an IPC namespace, and a corresponding mount of an
diff --git a/man7/netlink.7 b/man7/netlink.7
index 952aa7065..e3d00fbca 100644
--- a/man7/netlink.7
+++ b/man7/netlink.7
@@ -43,7 +43,7 @@ and raw sockets.
selects the kernel module or netlink group to communicate with.
The currently assigned netlink families are:
.TP
-.BR NETLINK_ROUTE
+.B NETLINK_ROUTE
Receives routing and link updates and may be used to modify the routing
tables (both IPv4 and IPv6), IP addresses, link parameters,
neighbor setups, queueing disciplines, traffic classes and
@@ -53,7 +53,7 @@ packet classifiers (see
.BR NETLINK_W1 " (Linux 2.6.13 to 2.16.17)"
Messages from 1-wire subsystem.
.TP
-.BR NETLINK_USERSOCK
+.B NETLINK_USERSOCK
Reserved for user-mode socket protocols.
.TP
.BR NETLINK_FIREWALL " (up to and including Linux 3.4)"
@@ -65,7 +65,7 @@ kernel module.
After a long period of being declared obsolete (in favor of the more advanced
.I nfnetlink_queue
feature),
-.BR NETLINK_FIREWALL
+.B NETLINK_FIREWALL
was removed in Linux 3.5.
.TP
.BR NETLINK_INET_DIAG " (since Linux 2.6.14)"
@@ -81,7 +81,7 @@ A synonym for
.BR NETLINK_NFLOG " (up to and including Linux 3.16)"
Netfilter/iptables ULOG.
.TP
-.BR NETLINK_XFRM
+.B NETLINK_XFRM
.\" FIXME More details on NETLINK_XFRM needed.
IPsec.
.TP
@@ -387,7 +387,7 @@ As at Linux 3.0, the
.BR NETLINK_GENERIC ,
.BR NETLINK_ROUTE ,
and
-.BR NETLINK_SELINUX
+.B NETLINK_SELINUX
groups allow other users to receive messages.
No groups allow other users to send messages.
.PP
diff --git a/man7/numa.7 b/man7/numa.7
index b6d81029d..2b7d2802f 100644
--- a/man7/numa.7
+++ b/man7/numa.7
@@ -123,7 +123,7 @@ Number of dirty pages.
.TP
.I mapped=<pages>
Total number of mapped pages, if different from
-.IR dirty
+.I dirty
and
.I anon
pages.
@@ -152,7 +152,7 @@ The Linux NUMA system calls and
.I /proc
interface are available only
if the kernel was configured and built with the
-.BR CONFIG_NUMA
+.B CONFIG_NUMA
option.
.SS Library support
Link with \fI\-lnuma\fP
diff --git a/man7/packet.7 b/man7/packet.7
index b624d47d1..9e2db6cfd 100644
--- a/man7/packet.7
+++ b/man7/packet.7
@@ -34,7 +34,7 @@ for raw packets including the link-level header or
.B SOCK_DGRAM
for cooked packets with the link-level header removed.
The link-level header information is available in a common format in a
-.IR sockaddr_ll
+.I sockaddr_ll
structure.
.I protocol
is the IEEE 802.3 protocol number in network byte order.
@@ -88,7 +88,7 @@ specifying an address in a
.I struct sockaddr_ll
to bind the packet socket to an interface.
Fields used for binding are
-.IR sll_family
+.I sll_family
(should be
.BR AF_PACKET ),
.IR sll_protocol ,
@@ -187,10 +187,10 @@ Packet socket options are configured by calling
with level
.BR SOL_PACKET .
.TP
-.BR PACKET_ADD_MEMBERSHIP
+.B PACKET_ADD_MEMBERSHIP
.PD 0
.TP
-.BR PACKET_DROP_MEMBERSHIP
+.B PACKET_DROP_MEMBERSHIP
.PD
Packet sockets can be used to configure physical-layer multicasting
and promiscuous mode.
@@ -297,20 +297,20 @@ modulo the number of sockets in the group, where a flow hash is a hash
over network-layer address and optional transport-layer port fields.
.IP *
The load-balance mode
-.BR PACKET_FANOUT_LB
+.B PACKET_FANOUT_LB
implements a round-robin algorithm.
.IP *
-.BR PACKET_FANOUT_CPU
+.B PACKET_FANOUT_CPU
selects the socket based on the CPU that the packet arrived on.
.IP *
-.BR PACKET_FANOUT_ROLLOVER
+.B PACKET_FANOUT_ROLLOVER
processes all data on a single socket, moving to the next when one
becomes backlogged.
.IP *
-.BR PACKET_FANOUT_RND
+.B PACKET_FANOUT_RND
selects the socket using a pseudo-random number generator.
.IP *
-.BR PACKET_FANOUT_QM
+.B PACKET_FANOUT_QM
.\" commit 2d36097d26b5991d71a2cf4a20c1a158f0f1bfcd
(available since Linux 3.14)
selects the socket using the recorded queue_mapping of the received skb.
@@ -326,7 +326,7 @@ preserve order even in this case.
Fanout mode and options are communicated in the second 16 bits of the
integer option value.
The flag
-.BR PACKET_FANOUT_FLAG_ROLLOVER
+.B PACKET_FANOUT_FLAG_ROLLOVER
enables the roll over mechanism as a backup strategy: if the
original fanout algorithm selects a backlogged socket, the packet
rolls over to the next available one.
@@ -336,7 +336,7 @@ When a malformed packet is encountered on a transmit ring,
the default is to reset its
.I tp_status
to
-.BR TP_STATUS_WRONG_FORMAT
+.B TP_STATUS_WRONG_FORMAT
and abort the transmission immediately.
The malformed packet blocks itself and subsequently enqueued packets from
being sent.
@@ -347,7 +347,7 @@ reset to
and the transmission process restarted via
.BR send (2).
However, if
-.BR PACKET_LOSS
+.B PACKET_LOSS
is set, any malformed packet will be skipped, its
.I tp_status
reset to
@@ -359,7 +359,7 @@ By default, a packet receive ring writes packets immediately following the
metadata structure and alignment padding.
This integer option reserves additional headroom.
.TP
-.BR PACKET_RX_RING
+.B PACKET_RX_RING
Create a memory-mapped ring buffer for asynchronous packet reception.
The packet socket reserves a contiguous region of application address
space, lays it out into an array of packet slots and copies packets
@@ -393,7 +393,7 @@ ownership to the application.
During normal operation, the new
.I tp_status
value has at least the
-.BR TP_STATUS_USER
+.B TP_STATUS_USER
bit set to signal that a received packet has been stored.
When the application has finished processing a packet, it transfers
ownership of the slot back to the socket by setting
@@ -403,10 +403,10 @@ equal to
.IP
Packet sockets implement multiple variants of the packet ring.
The implementation details are described in
-.IR Documentation/networking/packet_mmap.txt
+.I Documentation/networking/packet_mmap.txt
in the Linux kernel source tree.
.TP
-.BR PACKET_STATISTICS
+.B PACKET_STATISTICS
Retrieve packet socket statistics in the form of a structure
.IP
.in +4n
@@ -429,19 +429,19 @@ By default, this is a software generated timestamp generated when the
packet is copied into the ring.
This integer option selects the type of timestamp.
Besides the default, it support the two hardware formats described in
-.IR Documentation/networking/timestamping.txt
+.I Documentation/networking/timestamping.txt
in the Linux kernel source tree.
.TP
.BR PACKET_TX_RING " (since Linux 2.6.31)"
.\" commit 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1
Create a memory-mapped ring buffer for packet transmission.
This option is similar to
-.BR PACKET_RX_RING
+.B PACKET_RX_RING
and takes the same arguments.
The application writes packets into slots with
.I tp_status
equal to
-.BR TP_STATUS_AVAILABLE
+.B TP_STATUS_AVAILABLE
and schedules them for transmission by changing
.I tp_status
to
@@ -464,13 +464,13 @@ On successful transmission, the socket resets
to
.BR TP_STATUS_AVAILABLE .
It immediately aborts the transmission on error unless
-.BR PACKET_LOSS
+.B PACKET_LOSS
is set.
.TP
.BR PACKET_VERSION " (with " PACKET_RX_RING "; since Linux 2.6.27)"
.\" commit bbd6ef87c544d88c30e4b762b1b61ef267a7d279
By default,
-.BR PACKET_RX_RING
+.B PACKET_RX_RING
creates a packet receive ring of variant
.BR TPACKET_V1 .
To create another variant, configure the desired variant by setting this
@@ -646,10 +646,10 @@ The
include file for physical-layer protocols.
.PP
The Linux kernel source tree.
-.IR /Documentation/networking/filter.txt
+.I /Documentation/networking/filter.txt
describes how to apply Berkeley Packet Filters to packet sockets.
-.IR /tools/testing/selftests/net/psock_tpacket.c
+.I /tools/testing/selftests/net/psock_tpacket.c
contains example source code for all available versions of
-.BR PACKET_RX_RING
+.B PACKET_RX_RING
and
.BR PACKET_TX_RING .
diff --git a/man7/persistent-keyring.7 b/man7/persistent-keyring.7
index 48e219b0c..5aa854fd3 100644
--- a/man7/persistent-keyring.7
+++ b/man7/persistent-keyring.7
@@ -94,22 +94,22 @@ function for manipulating persistent keyrings.
operation.)
This operation allows the calling thread to get the persistent keyring
corresponding to its own UID or, if the thread has the
-.BR CAP_SETUID
+.B CAP_SETUID
capability, the persistent keyring corresponding to some other UID
in the same user namespace.
.SH NOTES
Each user namespace owns a keyring called
-.IR .persistent_register
+.I .persistent_register
that contains links to all of the persistent keys in that namespace.
(The
-.IR .persistent_register
+.I .persistent_register
keyring can be seen when reading the contents of the
-.IR /proc/keys
+.I /proc/keys
file for the UID 0 in the namespace.)
The
.BR keyctl_get_persistent (3)
operation looks for a key with a name of the form
-.IR _persistent.<UID>
+.I _persistent.<UID>
in that keyring,
creates the key if it does not exist, and links it into the keyring.
.SH SEE ALSO
diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index eaed8787b..817b2c481 100644
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -57,11 +57,11 @@ The first process created in a new namespace
(i.e., the process created using
.BR clone (2)
with the
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
flag, or the first child created by a process after a call to
.BR unshare (2)
using the
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
flag) has the PID 1, and is the "init" process for the namespace (see
.BR init (1)).
This process becomes the parent of any child processes that are orphaned
@@ -70,7 +70,7 @@ because a process that resides in this PID namespace terminated
.PP
If the "init" process of a PID namespace terminates,
the kernel terminates all of the processes in the namespace via a
-.BR SIGKILL
+.B SIGKILL
signal.
This behavior reflects the fact that the "init" process
is essential for the correct operation of a PID namespace.
@@ -198,7 +198,7 @@ That is to say, processes may not enter any ancestor namespaces
Changing PID namespaces is a one-way operation.
.PP
The
-.BR NS_GET_PARENT
+.B NS_GET_PARENT
.BR ioctl (2)
operation can be used to discover the parental relationship
between PID namespaces; see
@@ -213,11 +213,11 @@ that specify a PID namespace file descriptor
and calls to
.BR unshare (2)
with the
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
flag cause children subsequently created
by the caller to be placed in a different PID namespace from the caller.
(Since Linux 4.12, that PID namespace is shown via the
-.IR /proc/[pid]/ns/pid_for_children
+.I /proc/[pid]/ns/pid_for_children
file, as described in
.BR namespaces (7).)
These calls do not, however,
@@ -241,7 +241,7 @@ with the
.B CLONE_NEWPID
flag only once.
After it has performed this operation, its
-.IR /proc/PID/ns/pid_for_children
+.I /proc/PID/ns/pid_for_children
symbolic link will be empty until the first child is created in the namespace.
.\"
.\" ============================================================
@@ -269,7 +269,7 @@ rather than the "init" process in the child's own PID namespace.
.\"
.SS Compatibility of CLONE_NEWPID with other CLONE_* flags
In current versions of Linux,
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
can't be combined with
.BR CLONE_THREAD .
Threads are required to be in the same PID namespace such that
@@ -293,15 +293,15 @@ would defeat that.
.\" 8382fcac1b813ad0a4e68a838fc7ae93fa39eda0
.\" when CLONE_NEWPID|CLONE_VM was disallowed
In earlier versions of Linux,
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
was additionally disallowed (failing with the error
.BR EINVAL )
in combination with
-.BR CLONE_SIGHAND
+.B CLONE_SIGHAND
.\" (restriction lifted in faf00da544045fdc1454f3b9e6d7f65c841de302)
(before Linux 4.3) as well as
.\" (restriction lifted in e79f525e99b04390ca4d2366309545a836c03bf1)
-.BR CLONE_VM
+.B CLONE_VM
(before Linux 3.12).
The changes that lifted these restrictions have also been ported to
earlier stable kernels.
@@ -326,9 +326,9 @@ so that tools such as
.BR ps (1)
work correctly.
If a new mount namespace is simultaneously created by including
-.BR CLONE_NEWNS
+.B CLONE_NEWNS
in the
-.IR flags
+.I flags
argument of
.BR clone (2)
or
diff --git a/man7/pipe.7 b/man7/pipe.7
index 21c8fa79b..bb6ed7c5f 100644
--- a/man7/pipe.7
+++ b/man7/pipe.7
@@ -137,9 +137,9 @@ Since Linux 2.6.11, the pipe capacity is 16 pages
Since Linux 2.6.35, the default pipe capacity is 16 pages,
but the capacity can be queried and set using the
.BR fcntl (2)
-.BR F_GETPIPE_SZ
+.B F_GETPIPE_SZ
and
-.BR F_SETPIPE_SZ
+.B F_SETPIPE_SZ
operations.
See
.BR fcntl (2)
@@ -167,7 +167,7 @@ On Linux, the following files control how much memory can be used for pipes:
.\" commit b492e95be0ae672922f4734acf3f5d35c30be948
An upper limit, in pages, on the capacity that an unprivileged user
(one without the
-.BR CAP_SYS_RESOURCE
+.B CAP_SYS_RESOURCE
capability)
can set for a pipe.
.IP
@@ -238,9 +238,9 @@ The default value for this file is 16384,
which permits creating up to 1024 pipes with the default capacity.
.PP
Before Linux 4.9, some bugs affected the handling of the
-.IR pipe-user-pages-soft
+.I pipe-user-pages-soft
and
-.IR pipe-user-pages-hard
+.I pipe-user-pages-hard
limits; see BUGS.
.\"
.SS PIPE_BUF
@@ -342,12 +342,12 @@ Portable applications should avoid reliance on
bidirectional pipe semantics.
.SS BUGS
Before Linux 4.9, some bugs affected the handling of the
-.IR pipe-user-pages-soft
+.I pipe-user-pages-soft
and
-.IR pipe-user-pages-hard
+.I pipe-user-pages-hard
limits when using the
.BR fcntl (2)
-.BR F_SETPIPE_SZ
+.B F_SETPIPE_SZ
operation to change a pipe's capacity:
.\" These bugs where remedied by a series of patches, in particular,
.\" commit b0b91d18e2e97b741b294af9333824ecc3fadfd8 and
diff --git a/man7/pkeys.7 b/man7/pkeys.7
index 63be26ee8..b1de0d244 100644
--- a/man7/pkeys.7
+++ b/man7/pkeys.7
@@ -44,7 +44,7 @@ access, or all access to a tagged page.
Protection keys work in conjunction with the existing
.BR PROT_READ /
.BR PROT_WRITE /
-.BR PROT_EXEC
+.B PROT_EXEC
permissions passed to system calls such as
.BR mprotect (2)
and
@@ -54,7 +54,7 @@ mechanisms.
.PP
If a process performs an access that violates pkey
restrictions, it receives a
-.BR SIGSEGV
+.B SIGSEGV
signal.
See
.BR sigaction (2)
@@ -92,7 +92,7 @@ called on them because it would have processor or memory performance
implications to perform the additional checks needed to disallow it.
Implementation of the necessary checks is left up to applications.
Applications may implement these checks by searching the
-.IR /proc/[pid]/smaps
+.I /proc/[pid]/smaps
file for memory regions with the pkey assigned.
Further details can be found in
.BR proc (5).
@@ -118,7 +118,7 @@ instruction.
Details of how to do this can be found in the Intel Software
Developers Manual.
The kernel performs this enumeration and exposes the information in
-.IR /proc/cpuinfo
+.I /proc/cpuinfo
under the "flags" field.
The string "pku" in this field indicates hardware support for protection
keys and the string "ospke" indicates that the kernel contains and has
@@ -160,7 +160,7 @@ and
.PP
The Linux pkey system calls are available only if the kernel was
configured and built with the
-.BR CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS
+.B CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS
option.
.SH EXAMPLE
.PP
diff --git a/man7/pty.7 b/man7/pty.7
index d221c41a7..77fbba003 100644
--- a/man7/pty.7
+++ b/man7/pty.7
@@ -158,7 +158,7 @@ operations
.BR TIOCSTART ,
.BR TIOCUCNTL ,
and
-.BR TIOCREMOTE
+.B TIOCREMOTE
have not been implemented under Linux.
.SH SEE ALSO
.BR ioctl_tty (2),
--
2.20.1
