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>
---
man4/mem.4 | 8 ++++----
man4/mouse.4 | 2 +-
man4/null.4 | 10 +++++-----
man4/pts.4 | 2 +-
man4/random.4 | 22 +++++++++++-----------
man4/rtc.4 | 2 +-
man4/sk98lin.4 | 2 +-
man4/smartpqi.4 | 2 +-
man4/st.4 | 26 +++++++++++++-------------
man4/vcs.4 | 2 +-
10 files changed, 39 insertions(+), 39 deletions(-)
diff --git a/man4/mem.4 b/man4/mem.4
index 6ff0121ae..341e9be17 100644
--- a/man4/mem.4
+++ b/man4/mem.4
@@ -27,13 +27,13 @@
.SH NAME
mem, kmem, port \- system memory, kernel memory and system ports
.SH DESCRIPTION
-.IR /dev/mem
+.I /dev/mem
is a character device file
that is an image of the main memory of the computer.
It may be used, for example, to examine (and even patch) the system.
.PP
Byte addresses in
-.IR /dev/mem
+.I /dev/mem
are interpreted as physical memory addresses.
References to nonexistent locations cause errors to be returned.
.PP
@@ -57,7 +57,7 @@ chown root:kmem /dev/mem
.in
.PP
The file
-.IR /dev/kmem
+.I /dev/kmem
is the same as
.IR /dev/mem ,
except that the kernel virtual memory
@@ -75,7 +75,7 @@ chown root:kmem /dev/kmem
.EE
.in
.PP
-.IR /dev/port
+.I /dev/port
is similar to
.IR /dev/mem ,
but the I/O ports are accessed.
diff --git a/man4/mouse.4 b/man4/mouse.4
index 1805c2935..47e405315 100644
--- a/man4/mouse.4
+++ b/man4/mouse.4
@@ -83,7 +83,7 @@ protocol uses 1 start bit, 7 data bits, no parity
and one stop bit at the speed of 1200 bits/sec.
Data is sent to RxD in 3-byte packets.
The
-.IR dx
+.I dx
and
.I dy
movements are sent as
diff --git a/man4/null.4 b/man4/null.4
index 871d7ea4e..b08daea72 100644
--- a/man4/null.4
+++ b/man4/null.4
@@ -28,17 +28,17 @@
null, zero \- data sink
.SH DESCRIPTION
Data written to the
-.IR /dev/null
+.I /dev/null
and
-.IR /dev/zero
+.I /dev/zero
special files is discarded.
.PP
Reads from
-.IR /dev/null
+.I /dev/null
always return end of file (i.e.,
.BR read (2)
returns 0), whereas reads from
-.IR /dev/zero
+.I /dev/zero
always return bytes containing zero (\(aq\e0\(aq characters).
.PP
These devices are typically created by:
@@ -61,7 +61,7 @@ programs will act strangely.
Since Linux 2.6.31,
.\" commit 2b83868723d090078ac0e2120e06a1cc94dbaef0
reads from
-.IR /dev/zero
+.I /dev/zero
are interruptible by signals.
(This change was made to help with bad latencies for large reads from
.IR /dev/zero .)
diff --git a/man4/pts.4 b/man4/pts.4
index fa3ea60c0..1fd8adf61 100644
--- a/man4/pts.4
+++ b/man4/pts.4
@@ -23,7 +23,7 @@ and a pseudoterminal slave (PTS) device is created in the
.I /dev/pts
directory.
Each file descriptor obtained by opening
-.IR /dev/ptmx
+.I /dev/ptmx
is an independent PTM with its own associated PTS, whose path can
be found by passing the file descriptor to
.BR ptsname (3).
diff --git a/man4/random.4 b/man4/random.4
index 5f0d52472..f8d3b69c0 100644
--- a/man4/random.4
+++ b/man4/random.4
@@ -53,7 +53,7 @@ Reads from this device do not block (i.e., the CPU is not yielded),
but can incur an appreciable delay when requesting large amounts of data.
.PP
When read during early boot time,
-.IR /dev/urandom
+.I /dev/urandom
may return data prior to the entropy pool being initialized.
.\" This is a real problem; see
.\" commit 9b4d008787f864f17d008c9c15bbe8a0f7e2fc24
@@ -76,7 +76,7 @@ If
is called for
.I /dev/random
with the
-.BR O_NONBLOCK
+.B O_NONBLOCK
flag, a subsequent
.BR read (2)
will not block if the requested number of bytes is not available.
@@ -108,12 +108,12 @@ Since Linux 3.16,
a
.BR read (2)
from
-.IR /dev/urandom
+.I /dev/urandom
will return at most 32\ MB.
A
.BR read (2)
from
-.IR /dev/random
+.I /dev/random
will return at most 512 bytes
.\" SEC_XFER_SIZE in drivers/char/random.c
(340 bytes on Linux kernels before version 2.6.12).
@@ -126,9 +126,9 @@ read from both files, but it will not make reads from
\fI/dev/random\fP faster.
.SS Usage
The
-.IR /dev/random
+.I /dev/random
interface is considered a legacy interface, and
-.IR /dev/urandom
+.I /dev/urandom
is preferred and sufficient in all use cases, with the exception of
applications which require randomness during early boot time; for
these applications,
@@ -208,7 +208,7 @@ dd if=/dev/urandom of=$random_seed count=1 bs=$bytes
.in
.PP
In the above examples, we assume Linux 2.6.0 or later, where
-.IR /proc/sys/kernel/random/poolsize
+.I /proc/sys/kernel/random/poolsize
returns the size of the entropy pool in bits (see below).
.\"
.SS /proc interfaces
@@ -277,21 +277,21 @@ The
capability is required for all requests except
.BR RNDGETENTCNT .
.TP
-.BR RNDGETENTCNT
+.B RNDGETENTCNT
Retrieve the entropy count of the input pool, the contents will be the same
as the
.I entropy_avail
file under proc.
The result will be stored in the int pointed to by the argument.
.TP
-.BR RNDADDTOENTCNT
+.B RNDADDTOENTCNT
Increment or decrement the entropy count of the input pool
by the value pointed to by the argument.
.TP
-.BR RNDGETPOOL
+.B RNDGETPOOL
Removed in Linux 2.6.9.
.TP
-.BR RNDADDENTROPY
+.B RNDADDENTROPY
Add some additional entropy to the input pool,
incrementing the entropy count.
This differs from writing to \fI/dev/random\fP or \fI/dev/urandom\fP,
diff --git a/man4/rtc.4 b/man4/rtc.4
index 823bbda36..30a4ce474 100644
--- a/man4/rtc.4
+++ b/man4/rtc.4
@@ -296,7 +296,7 @@ argument.
.IR /dev/rtc ", " /dev/rtc0 ", " /dev/rtc1 ", etc."
RTC special character device files.
.TP
-.IR /proc/driver/rtc
+.I /proc/driver/rtc
status of the (first) RTC.
.SH NOTES
When the kernel's system time is synchronized with an external
diff --git a/man4/sk98lin.4 b/man4/sk98lin.4
index 33b77478c..f2efaa3db 100644
--- a/man4/sk98lin.4
+++ b/man4/sk98lin.4
@@ -545,7 +545,7 @@ configured to use the Spanning Tree protocol.
.I DualNet
In this mode, ports A and B are used as separate devices.
If you have a dual port adapter, port A will be configured as
-.IR eth[x]
+.I eth[x]
and port B as
.IR eth[x+1] .
Both ports can be used independently with distinct IP addresses.
diff --git a/man4/smartpqi.4 b/man4/smartpqi.4
index cf7c43034..ac6c9ac17 100644
--- a/man4/smartpqi.4
+++ b/man4/smartpqi.4
@@ -144,7 +144,7 @@ attribute is a read/write attribute.
This attribute will cause the driver to perform a specific action in the
unlikely event that a controller lockup has been detected.
See
-.BR OPTIONS
+.B OPTIONS
above
for an explanation of the
.I lockup_action
diff --git a/man4/st.4 b/man4/st.4
index 0a5e0963e..cbec33841 100644
--- a/man4/st.4
+++ b/man4/st.4
@@ -56,7 +56,7 @@ two sets of four numbers: the principal (auto-rewind) minor device numbers,
and the \(lqno-rewind\(rq device numbers,
.RI ( n " + 128)."
Devices opened using the principal device number will be sent a
-.BR REWIND
+.B REWIND
command when they are closed.
Devices opened using the \(lqno-rewind\(rq device number will not.
(Note that using an auto-rewind device for positioning the tape with,
@@ -349,7 +349,7 @@ the rest of the tape contains partition 1.
The physical ordering of partitions depends on the drive.
This command is not allowed for a drive unless the partition support
is enabled for the drive (see
-.BR MT_ST_CAN_PARTITIONS
+.B MT_ST_CAN_PARTITIONS
below).
.TP
.B MTNOP
@@ -378,7 +378,7 @@ command (device-specific address)
or a Tandberg-compatible SCSI-1 drive (Tandberg, Archive
Viper, Wangtek, ...).
The block number should be one that was previously returned by
-.BR MTIOCPOS
+.B MTIOCPOS
if device-specific addresses are used.
.TP
.B MTSETBLK
@@ -434,17 +434,17 @@ The buffering modes are:
.RS 12
.IP 0 4
The drive will not report
-.BR GOOD
+.B GOOD
status on write commands until the data
blocks are actually written to the medium.
.IP 1
The drive may report
-.BR GOOD
+.B GOOD
status on write commands as soon as all the
data has been transferred to the drive's internal buffer.
.IP 2
The drive may report
-.BR GOOD
+.B GOOD
status on write commands as soon as (a) all
the data has been transferred to the drive's internal buffer, and
(b) all buffered data from different initiators has been successfully
@@ -454,7 +454,7 @@ written to the medium.
To control the write threshold the value in
.I mt_count
must include the constant
-.BR MT_ST_WRITE_THRESHOLD
+.B MT_ST_WRITE_THRESHOLD
bitwise ORed with a block count in the low 28 bits.
The block count refers to 1024-byte blocks, not the physical block
size on the tape.
@@ -469,17 +469,17 @@ must include one of the constants
.BR MT_ST_SETBOOLEANS ,
.BR MT_ST_CLEARBOOLEANS ,
or
-.BR MT_ST_DEFBOOLEANS
+.B MT_ST_DEFBOOLEANS
bitwise ORed with
whatever combination of the following options is desired.
Using
-.BR MT_ST_BOOLEANS
+.B MT_ST_BOOLEANS
the options can be set to the values
defined in the corresponding bits.
With
-.BR MT_ST_SETBOOLEANS
+.B MT_ST_SETBOOLEANS
the options can be selectively set and with
-.BR MT_ST_DEFBOOLEANS
+.B MT_ST_DEFBOOLEANS
selectively cleared.
.IP ""
The default options for a tape device are set with
@@ -788,7 +788,7 @@ Implemented in kernels since 2.4.19 and 2.5.43.
The only field defined in
.I mt_erreg
is the recovered error count in the low 16 bits (as defined by
-.BR MT_ST_SOFTERR_SHIFT
+.B MT_ST_SOFTERR_SHIFT
and
.BR MT_ST_SOFTERR_MASK .
Due to inconsistencies in the way drives report recovered errors, this
@@ -797,7 +797,7 @@ soft errors but this can be changed with a SCSI MODE SELECT command).
.IP \fImt_fileno\fP
reports the current file number (zero-based).
This value is set to \-1 when the file number is unknown (e.g., after
-.BR MTBSS
+.B MTBSS
or
.BR MTSEEK ).
.IP \fImt_blkno\fP
diff --git a/man4/vcs.4 b/man4/vcs.4
index f695b956c..4b5e6a2ac 100644
--- a/man4/vcs.4
+++ b/man4/vcs.4
@@ -40,7 +40,7 @@ displayed virtual console terminal.
are character devices for virtual console
terminals, they have major number 7 and minor number 1 to 63, usually
mode 0644 and owner root.tty.
-.IR /dev/vcsa[0\-63]
+.I /dev/vcsa[0\-63]
are the same, but
using
.IR "unsigned short" s
--
2.20.1
