Fix redundant formatting macros

2007-09-20 16:26:31 +00:00 · 2007-09-20 16:26:31 +00:00 · 0daa9e92d0
parent c11b1abf2e
commit 0daa9e92d0
203 changed files with 702 additions and 702 deletions
--- a/man1/intro.1
+++ b/man1/intro.1
@ -109,7 +109,7 @@ drwxr-xr-x   2 aeb       1024 Aug  6 23:51 bin
 .BI "% " "rm tel1"
 .BI "% " "grep maja tel2"
 maja    0501-1136285
-.BI "% "
+.B "% "
 .fi
 .RE
 and here typing Control-D ended the session.
--- a/man1/ldd.1
+++ b/man1/ldd.1
@ -12,7 +12,7 @@
 ldd \- print shared library dependencies
 .SH SYNOPSIS
 .B ldd
-.RB [OPTION]...
+.R [OPTION]...
 FILE...
 .SH DESCRIPTION
 .B ldd
--- a/man1/time.1
+++ b/man1/time.1
@ -82,7 +82,7 @@ useful information, not only about time used, but also on other
 resources like memory, I/O and IPC calls (where available).
 The output is formatted using a format string that can be specified
 using the \-f option or the
-.BR TIME
+.B TIME
 environment variable.
 .LP
 The default format string is
@ -241,7 +241,7 @@ GNU time version 1.7 is not yet localized.
 Thus, it does not implement the POSIX requirements.
 .LP
 The environment variable
-.BR TIME
+.B TIME
 was badly chosen.
 It is not unusual for systems like
 .BR autoconf (1)
--- a/man2/accept.2
+++ b/man2/accept.2
@ -148,7 +148,7 @@ the network errors defined for the protocol after
 .BR accept ()
 and treat
 them like
-.BR EAGAIN
+.B EAGAIN
 by retrying.
 In case of TCP/IP these are
 .BR ENETDOWN ,
@ -244,9 +244,9 @@ first appeared in 4.2BSD), POSIX.1-2001.
 On Linux, the new socket returned by
 .BR accept ()
 does \fInot\fP inherit file status flags such as
-.BR O_NONBLOCK
+.B O_NONBLOCK
 and
-.BR O_ASYNC
+.B O_ASYNC
 from the listening socket.
 This behavior differs from the canonical BSD sockets implementation.
 .\" Some testing seems to show that Tru64 5.1 and HP-UX 11 also
--- a/man2/alloc_hugepages.2
+++ b/man2/alloc_hugepages.2
@ -104,7 +104,7 @@ is
 then a new huge page segment is created when none
 with the given key existed.
 If this flag is not set, then
-.BR ENOENT
+.B ENOENT
 is returned when no segment with the given key exists.
 .IR
 .SH "RETURN VALUE"
--- a/man2/cacheflush.2
+++ b/man2/cacheflush.2
@ -37,7 +37,7 @@ user addresses in the range
 .I addr
 to
 .IR (addr+nbytes-1) .
-.IR cache
+.I cache
 may be one of:
 .TP
 .B ICACHE
--- a/man2/chmod.2
+++ b/man2/chmod.2
@ -53,7 +53,7 @@ or referenced by
 is changed.

 Modes are specified by
-.IR or'ing
+.I or'ing
 the following:
 .RS
 .TP 1.0i
--- a/man2/clone.2
+++ b/man2/clone.2
@ -63,7 +63,7 @@ It is actually a library function layered on top of the underlying
 system call, hereinafter referred to as
 .BR sys_clone .
 A description of
-.BR sys_clone
+.B sys_clone
 is given towards the end of this page.

 Unlike
--- a/man2/connect.2
+++ b/man2/connect.2
@ -82,7 +82,7 @@ system call connects the socket referred to by the file descriptor
 to the address specified by
 .IR serv_addr .
 The
-.IR addrlen
+.I addrlen
 argument specifies the size of
 .IR serv_addr .
 The format of the address in
--- a/man2/epoll_ctl.2
+++ b/man2/epoll_ctl.2
@ -32,11 +32,11 @@ Control an
 descriptor,
 .IR epfd ,
 by requesting that the operation
-.IR op
+.I op
 be performed on the target file descriptor,
 .IR fd .
 The
-.IR event
+.I event
 describes the object linked to the file descriptor
 .IR fd .
 The
@ -126,7 +126,7 @@ The
 interface supports all file descriptors that support
 .BR poll (2).
 Valid values for the
-.IR op
+.I op
 parameter are :
 .RS
 .TP
@ -156,7 +156,7 @@ from the
 file descriptor,
 .IR epfd .
 The
-.IR event
+.I event
 is ignored and can be NULL (but see BUGS below).
 .RE
 .SH "RETURN VALUE"
@ -181,17 +181,17 @@ is not a valid file descriptor.
 was
 .BR EPOLL_CTL_ADD ,
 and the supplied file descriptor
-.IR fd
+.I fd
 is already in
 .IR epfd .
 .TP
 .B EINVAL
-.IR epfd
+.I epfd
 is not an
 .B epoll
 file descriptor,
 or
-.IR fd
+.I fd
 is the same as
 .IR epfd ,
 or the requested operation
@ -201,11 +201,11 @@ is not supported by this interface.
 .B ENOENT
 .I op
 was
-.BR EPOLL_CTL_MOD
+.B EPOLL_CTL_MOD
 or
 .BR EPOLL_CTL_DEL ,
 and
-.IR fd
+.I fd
 is not in
 .IR epfd .
 .TP
--- a/man2/epoll_wait.2
+++ b/man2/epoll_wait.2
@ -156,7 +156,7 @@ requested events occurred or the
 expired.
 .TP
 .B EINVAL
-.IR epfd
+.I epfd
 is not an
 .B epoll
 file descriptor, or
--- a/man2/execve.2
+++ b/man2/execve.2
@ -82,7 +82,7 @@ after a successful
 If the set-user-ID bit is set on the program file pointed to by
 \fIfilename\fP,
 and the underlying file system is not mounted
-.IR nosuid
+.I nosuid
 (the
 .B MS_NOSUID
 flag for
@ -177,7 +177,7 @@ flag is cleared.
 .IP * 4
 The process name, as set by
 .BR prctl (2)
-.BR PR_SET_NAME
+.B PR_SET_NAME
 (and displayed by
 .IR "ps \-o comm" ),
 is reset to the name of the new executable file.
@ -217,7 +217,7 @@ By default, file descriptors remain open across an
 .BR execve ().
 File descriptors that are marked close-on-exec are closed
 ; see the description of
-.BR FD_CLOEXEC
+.B FD_CLOEXEC
 in
 .BR fcntl (2).
 (If a file descriptor is closed, this will cause the release
@ -286,7 +286,7 @@ and environment
 .RI ( envp )
 strings that may be passed to a new program.
 POSIX.1 allows an implementation to advertise this limit using the
-.BR ARG_MAX
+.B ARG_MAX
 constant (either defined in
 .I <limits.h>
 or available at run time using the call
@ -307,7 +307,7 @@ resource limit (see
 For
 these architectures, the total size is limited to 1/4 of the allowed
 stack size, the limit per string is 32 pages (the kernel constant
-.BR MAX_ARG_STRLEN),
+.B MAX_ARG_STRLEN),
 and the maximum number of strings is 0x7FFFFFFF.
 (This change allows programs to have a much larger
 argument and/or environment list.
@ -466,7 +466,7 @@ and
 can be specified as NULL,
 which has the same effect as specifying these arguments
 as pointers to lists containing a single NULL pointer.
-.BR "Do not take advantage of this misfeature!"
+.B "Do not take advantage of this misfeature!"
 It is non-standard and non-portable:
 on most other Unix systems doing this will result in an error.
 .\" e.g., EFAULT on Solaris 8 and FreeBSD 6.1; but
--- a/man2/faccessat.2
+++ b/man2/faccessat.2
@ -47,7 +47,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR access (2)
@ -66,7 +66,7 @@ directory of the calling process (like
 .BR access (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/fchmodat.2
+++ b/man2/fchmodat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR chmod (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR chmod (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
@ -109,7 +109,7 @@ is relative and
 is a file descriptor referring to a file other than a directory.
 .TP
 .B ENOTSUP
-.IR flags
+.I flags
 specified
 .BR AT_SYMLINK_NOFOLLOW ,
 which is not supported.
--- a/man2/fchownat.2
+++ b/man2/fchownat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR chown (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR chown (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@ -145,7 +145,7 @@ On Linux this command can only change the
 .BR O_DIRECT ,
 .BR O_NOATIME ,
 and
-.BR O_NONBLOCK
+.B O_NONBLOCK
 flags.
 .\" FIXME . According to POSIX.1-2001, O_SYNC should also be modifiable
 .\" via fcntl(2), but currently Linux does not permit this
@ -351,7 +351,7 @@ or converted to a mode that is compatible with the access.
 If the
 .B O_NONBLOCK
 flag is enabled, then the system call fails with the error
-.BR EAGAIN
+.B EAGAIN
 or
 .BR EWOULDBLOCK .

@ -422,7 +422,7 @@ Sending a signal to the owner process (group) specified by
 is subject to the same permissions checks as are described for
 .BR kill (2),
 where the sending process is the one that employs
-.BR F_SETOWN
+.B F_SETOWN
 (but see BUGS below).
 .sp
 If the file descriptor
@ -916,7 +916,7 @@ Only the operations
 .BR F_SETLKW ,
 .BR F_GETOWN ,
 and
-.BR F_SETOWN
+.B F_SETOWN
 are specified in POSIX.1-2001.

 .BR F_GETSIG ,
@ -924,10 +924,10 @@ are specified in POSIX.1-2001.
 .BR F_NOTIFY ,
 .BR F_GETLEASE ,
 and
-.BR F_SETLEASE
+.B F_SETLEASE
 are Linux specific.
 (Define the
-.BR _GNU_SOURCE
+.B _GNU_SOURCE
 macro to obtain these definitions.)
 .\" .PP
 .\" SVr4 documents additional EIO, ENOLINK and EOVERFLOW error conditions.
--- a/man2/fork.2
+++ b/man2/fork.2
@ -168,9 +168,9 @@ It was not possible to create a new process because the caller's
 .B RLIMIT_NPROC
 resource limit was encountered.
 To exceed this limit, the process must have either the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
 or the
-.BR CAP_SYS_RESOURCE
+.B CAP_SYS_RESOURCE
 capability.
 .TP
 .B ENOMEM
--- a/man2/fstatat.2
+++ b/man2/fstatat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR stat (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR stat (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/futimesat.2
+++ b/man2/futimesat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR utimes (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR utimes (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/get_mempolicy.2
+++ b/man2/get_mempolicy.2
@ -47,7 +47,7 @@ The memory policy defines from which node memory is allocated for
 the process.

 If
-.IR flags
+.I flags
 is specified as 0,
 then information about the calling process's default policy
 (as set by
@ -75,7 +75,7 @@ argument is not NULL, then
 will store the policy mode of the requested NUMA policy in the location
 pointed to by this argument.
 If
-.IR nodemask
+.I nodemask
 is not NULL, then the nodemask associated with the policy will be stored
 in the location pointed to by this argument.
 .I maxnode
--- a/man2/gethostname.2
+++ b/man2/gethostname.2
@ -103,7 +103,7 @@ but not
 SUSv2 guarantees that `Host names are limited to 255 bytes'.
 POSIX.1-2001 guarantees that `Host names (not including
 the terminating null byte) are limited to
-.BR HOST_NAME_MAX
+.B HOST_NAME_MAX
 bytes'.
 .SS Glibc Notes
 The GNU C library implements
@ -129,7 +129,7 @@ Versions of glibc before 2.2
 handle the case where the length of the
 .I nodename
 was greater than or equal to
-.IR len
+.I len
 differently: nothing is copied into
 .I name
 and the function returns \-1 with
--- a/man2/getpagesize.2
+++ b/man2/getpagesize.2
@ -55,7 +55,7 @@ long sz = sysconf(_SC_PAGESIZE);
 .RE

 (most systems allow the synonym
-.BR _SC_PAGE_SIZE
+.B _SC_PAGE_SIZE
 for
 .BR _SC_PAGESIZE ),
 or
--- a/man2/getpriority.2
+++ b/man2/getpriority.2
@ -163,7 +163,7 @@ The nice value is preserved across
 .BR execve (2).

 The details on the condition for
-.BR EPERM
+.B EPERM
 depend on the system.
 The above description is what POSIX.1-2001 says, and seems to be followed on
 all System V-like systems.
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@ -346,7 +346,7 @@ points outside the accessible address space.
 is not valid;
 or, for
 .BR setrlimit ():
-.IR rlim->rlim_cur
+.I rlim->rlim_cur
 was greater than
 .IR rlim->rlim_max .
 .TP
@ -367,12 +367,12 @@ maximum
 .RB ( NR_OPEN ).
 .SH CONFORMING TO
 SVr4, 4.3BSD, POSIX.1-2001.
-.BR RLIMIT_MEMLOCK
+.B RLIMIT_MEMLOCK
 and
-.BR RLIMIT_NPROC
+.B RLIMIT_NPROC
 derive from BSD and are not specified in POSIX.1-2001;
 they are present on the BSDs and Linux, but on few other implementations.
-.BR RLIMIT_RSS
+.B RLIMIT_RSS
 derives from BSD and is not specified in POSIX.1-2001;
 it is nevertheless present on most implementations.
 .BR RLIMIT_MSGQUEUE ,
@ -425,7 +425,7 @@ Kernels before 2.4.22 did not diagnose the error
 for
 .BR setrlimit ()
 when
-.IR rlim->rlim_cur
+.I rlim->rlim_cur
 was greater than
 .IR rlim->rlim_max .
 .SH "SEE ALSO"
--- a/man2/getrusage.2
+++ b/man2/getrusage.2
@ -124,7 +124,7 @@ In linux 2.4 only the fields
 .IR ru_stime ,
 .IR ru_minflt ,
 and
-.IR ru_majflt
+.I ru_majflt
 are maintained.
 Since Linux 2.6,
 .I ru_nvcsw
--- a/man2/inotify_init.2
+++ b/man2/inotify_init.2
@ -31,7 +31,7 @@ inotify_init \- initialize an inotify instance
 .SH SYNOPSIS
 .B #include <sys/inotify.h>
 .sp
-.BI "int inotify_init(void);"
+.B "int inotify_init(void);"
 .SH DESCRIPTION
 .BR inotify_init ()
 initializes a new inotify instance and returns a file descriptor associated
--- a/man2/ioctl.2
+++ b/man2/ioctl.2
@ -133,7 +133,7 @@ Often the
 .BR open (2)
 call has unwanted side effects, that can be avoided under Linux
 by giving it the
-.BR O_NONBLOCK
+.B O_NONBLOCK
 flag.
 .SH "SEE ALSO"
 .BR execve (2),
--- a/man2/ioprio_set.2
+++ b/man2/ioprio_set.2
@ -107,9 +107,9 @@ value, which is returned as the result of the macro.
 .TP
 .BI IOPRIO_PRIO_CLASS( mask )
 Given
-.IR mask
+.I mask
 (an
-.IR ioprio
+.I ioprio
 value), this macro returns its I/O class component, that is,
 one of the values
 .BR IOPRIO_CLASS_RT ,
@ -119,9 +119,9 @@ or
 .TP
 .BI IOPRIO_PRIO_DATA( mask )
 Given
-.IR mask
+.I mask
 (an
-.IR ioprio
+.I ioprio
 value), this macro returns its priority
 .RI ( data )
 component.
--- a/man2/killpg.2
+++ b/man2/killpg.2
@ -116,7 +116,7 @@ A difference not mentioned by POSIX concerns the return
 value
 .BR EPERM :
 BSD documents that no signal is sent and
-.BR EPERM
+.B EPERM
 returned when the permission check failed for at least one target process,
 while POSIX documents
 .B EPERM
--- a/man2/linkat.2
+++ b/man2/linkat.2
@ -45,7 +45,7 @@ If the pathname given in
 .I oldpath
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR olddirfd
+.I olddirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR link (2)
@ -64,7 +64,7 @@ directory of the calling process (like
 .BR link (2)).

 If
-.IR oldpath
+.I oldpath
 is absolute, then
 .I olddirfd
 is ignored.
@ -122,7 +122,7 @@ is a file descriptor referring to a file other than a directory;
 or similar for
 .I newpath
 and
-.IR newdirfd
+.I newdirfd
 .SH VERSIONS
 .BR linkat ()
 was added to Linux in kernel 2.6.16.
--- a/man2/lookup_dcookie.2
+++ b/man2/lookup_dcookie.2
@ -75,7 +75,7 @@ The buffer was not large enough to hold the path of the directory entry.
 .SH VERSIONS
 Available since Linux 2.5.43.
 The
-.BR ENAMETOOLONG
+.B ENAMETOOLONG
 error return was added in 2.5.70.
 .SH "CONFORMING TO"
 .BR lookup_dcookie ()
--- a/man2/madvise.2
+++ b/man2/madvise.2
@ -156,7 +156,7 @@ The map exists, but the area maps something that isn't a file.
 .TP
 .B EINVAL
 The value
-.IR len
+.I len
 is negative,
 .\" .I len
 .\" is zero,
@ -196,7 +196,7 @@ for file access.
 .BR MADV_REMOVE ,
 .BR MADV_DONTFORK ,
 and
-.BR MADV_DOFORK
+.B MADV_DOFORK
 are Linux specific.
 .SH NOTES
 .SS "Linux Notes"
--- a/man2/mbind.2
+++ b/man2/mbind.2
@ -42,7 +42,7 @@ which consists of a policy mode and zero or more nodes,
 for the memory range starting with
 .I start
 and continuing for
-.IR len
+.I len
 bytes.
 The memory of a NUMA machine is divided into multiple nodes.
 The memory policy defines from which node memory is allocated.
@ -100,7 +100,7 @@ only has an effect for new allocations; if the pages inside
 the range have been already touched before setting the policy,
 then the policy has no effect.
 This default behavior may be overridden by the
-.BR MPOL_MF_MOVE
+.B MPOL_MF_MOVE
 and
 .B MPOL_MF_MOVE_ALL
 flags described below.
@ -213,7 +213,7 @@ range of memory via
 If
 .B MPOL_MF_STRICT
 is passed in
-.IR flags
+.I flags
 and
 .I policy
 is not
--- a/man2/mkdir.2
+++ b/man2/mkdir.2
@ -51,7 +51,7 @@ is set appropriately).
 .B EACCES
 The parent directory does not allow write permission to the process,
 or one of the directories in
-.IR pathname
+.I pathname
 did not allow search permission.
 (See also
 .BR path_resolution (7).)
@ -97,7 +97,7 @@ is not, in fact, a directory.
 .TP
 .B EPERM
 The filesystem containing
-.IR pathname
+.I pathname
 does not support the creation of directories.
 .TP
 .B EROFS
--- a/man2/mkdirat.2
+++ b/man2/mkdirat.2
@ -44,7 +44,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR mkdir (2)
@ -63,7 +63,7 @@ directory of the calling process (like
 .BR mkdir (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/mknod.2
+++ b/man2/mknod.2
@ -49,7 +49,7 @@ It should be a combination (using bitwise OR) of one of the file types
 listed below and the permissions for the new node.

 The permissions are modified by the process's
-.IR umask
+.I umask
 in the usual way: the permissions of the created node are
 .IR "(mode & ~umask)" .

@ -57,9 +57,9 @@ The file type must be one of
 .BR S_IFREG ,
 .BR S_IFCHR ,
 .BR S_IFBLK ,
-.BR S_IFIFO
+.B S_IFIFO
 or
-.BR S_IFSOCK
+.B S_IFSOCK
 .\" (S_IFSOCK since Linux 1.2.4)
 to specify a normal file (which will be created empty), character
 special file, block special file, FIFO (named pipe), or Unix domain socket,
@ -96,7 +96,7 @@ is set appropriately).
 .B EACCES
 The parent directory does not allow write permission to the process,
 or one of the directories in the path prefix of
-.IR pathname
+.I pathname
 did not allow search permission.
 (See also
 .BR path_resolution (7).)
--- a/man2/mknodat.2
+++ b/man2/mknodat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR mknod (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR mknod (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/mlock.2
+++ b/man2/mlock.2
@ -110,7 +110,7 @@ may fail if it would cause the number of locked bytes to exceed
 the permitted maximum (see below).
 In the same circumstances, stack growth may likewise fail:
 the kernel will deny stack expansion and deliver a
-.BR SIGSEGV
+.B SIGSEGV
 signal to the process.

 .BR munlockall ()
--- a/man2/mmap.2
+++ b/man2/mmap.2
@ -314,7 +314,7 @@ a write to the mapped region, and before a subsequent
 with the
 .B MS_SYNC
 or
-.BR MS_ASYNC
+.B MS_ASYNC
 flag, if one occurs.
 .SH "RETURN VALUE"
 On success,
@ -370,7 +370,7 @@ We don't like
 .IR start ,
 .IR length ,
 or
-.IR offset
+.I offset
 (e.g., they are too large, or not aligned on a page boundary).
 .TP
 .B EINVAL
@ -456,7 +456,7 @@ with a suitably adjusted value for
 .IR offset .

 On some hardware architectures (e.g., x86),
-.BR PROT_WRITE
+.B PROT_WRITE
 implies
 .BR PROT_READ .
 It is architecture dependent whether
--- a/man2/modify_ldt.2
+++ b/man2/modify_ldt.2
@ -101,7 +101,7 @@ or 0 (for writing).
 On failure,
 .BR modify_ldt ()
 returns \-1 and sets
-.IR errno
+.I errno
 to indicate the error.
 .SH ERRORS
 .TP
--- a/man2/mount.2
+++ b/man2/mount.2
@ -74,7 +74,7 @@ on the same mount point.
 .\" Multiple mounts on same mount point: since 2.3.99pre7.

 Values for the
-.IR filesystemtype
+.I filesystemtype
 argument supported by the kernel are listed in
 .I /proc/filesystems
 (like "minix", "ext2", "msdos", "proc", "nfs", "iso9660" etc.).
@ -82,7 +82,7 @@ Further types may become available when the appropriate modules
 are loaded.

 The
-.IR mountflags
+.I mountflags
 argument may have the magic number 0xC0ED (\fBMS_MGC_VAL\fP)
 in the top 16 bits (this was required in kernel versions prior to 2.4, but
 is no longer required and ignored if specified),
@ -189,7 +189,7 @@ can be changed:
 .BR MS_SYNCHRONOUS ,
 .BR MS_MANDLOCK ;
 before kernel 2.6.16, the following could also be changed:
-.BR MS_NOATIME
+.B MS_NOATIME
 and
 .BR MS_NODIRATIME ;
 and, additionally, before kernel 2.4, the following could also be changed:
@ -218,7 +218,7 @@ The
 flag is also settable on a per-mount-point basis.
 .PP
 The
-.IR data
+.I data
 argument is interpreted by the different file systems.
 Typically it is a string of comma-separated options
 understood by this file system.
@ -401,12 +401,12 @@ leaving only \fIumount(dir)\fP (since now devices can be mounted
 in more than one place, so specifying the device does not suffice).
 .LP
 The original
-.BR MS_SYNC
+.B MS_SYNC
 flag was renamed
-.BR MS_SYNCHRONOUS
+.B MS_SYNCHRONOUS
 in 1.1.69
 when a different
-.BR MS_SYNC
+.B MS_SYNC
 was added to \fI<mman.h>\fP.
 .LP
 Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program
--- a/man2/mprotect.2
+++ b/man2/mprotect.2
@ -125,7 +125,7 @@ has any effect different from
 .B PROT_READ
 is architecture and kernel version dependent.
 On some hardware architectures (e.g., x86),
-.BR PROT_WRITE
+.B PROT_WRITE
 implies
 .BR PROT_READ .

--- a/man2/mremap.2
+++ b/man2/mremap.2
@ -107,7 +107,7 @@ is unmapped.
 If
 .B MREMAP_FIXED
 is specified, then
-.BR MREMAP_MAYMOVE
+.B MREMAP_MAYMOVE
 must also be specified.
 .PP
 If the memory segment specified by
--- a/man2/msgctl.2
+++ b/man2/msgctl.2
@ -154,12 +154,12 @@ Returns information about system-wide message queue limits and
 parameters in the structure pointed to by
 .IR buf .
 This structure is of type
-.IR msginfo
+.I msginfo
 (thus, a cast is required),
 defined in
 .I <sys/msg.h>
 if the
-.BR _GNU_SOURCE
+.B _GNU_SOURCE
 feature test macro is defined:
 .nf
 .in +2n
@ -227,7 +227,7 @@ On success,
 .BR IPC_STAT ,
 .BR IPC_SET ,
 and
-.BR IPC_RMID
+.B IPC_RMID
 return 0.
 A successful
 .B IPC_INFO
@ -256,7 +256,7 @@ is set to one of the following:
 The argument
 .I cmd
 is equal to
-.BR IPC_STAT
+.B IPC_STAT
 or
 .BR MSG_STAT ,
 but the calling process does not have read permission on the message queue
@ -313,7 +313,7 @@ SVr4, POSIX.1-2001.
 .SH NOTES
 The
 .BR IPC_INFO ,
-.BR MSG_STAT
+.B MSG_STAT
 and
 .B MSG_INFO
 operations are used by the
@ -332,7 +332,7 @@ under Linux 2.4.
 To take advantage of this,
 a recompilation under glibc-2.1.91 or later should suffice.
 (The kernel distinguishes old and new calls by an
-.BR IPC_64
+.B IPC_64
 flag in
 .IR cmd .)
 .SH "SEE ALSO"
--- a/man2/msgget.2
+++ b/man2/msgget.2
@ -61,7 +61,7 @@ or
 isn't
 .BR IPC_PRIVATE ,
 no message queue with the given key
-.IR key
+.I key
 exists, and
 .B IPC_CREAT
 is specified in
@ -121,7 +121,7 @@ are set to the least significant 9 bits of
 .IR msg_qnum ,
 .IR msg_lspid ,
 .IR msg_lrpid ,
-.IR msg_stime
+.I msg_stime
 and
 .I msg_rtime
 are set to 0.
@ -152,7 +152,7 @@ A message queue exists for
 .IR key ,
 but the calling process does not have permission to access the queue,
 and does not have the
-.BR CAP_IPC_OWNER
+.B CAP_IPC_OWNER
 capability.
 .TP
 .B EEXIST
@ -206,13 +206,13 @@ dependent
 .IR /proc/sys/kernel/msgmni ).
 .SS "Linux Notes"
 Until version 2.3.20 Linux would return
-.BR EIDRM
+.B EIDRM
 for a
 .BR msgget ()
 on a message queue scheduled for deletion.
 .SH BUGS
 The name choice
-.BR IPC_PRIVATE
+.B IPC_PRIVATE
 was perhaps unfortunate, IPC_NEW
 would more clearly show its function.
 .SH "SEE ALSO"
--- a/man2/msgop.2
+++ b/man2/msgop.2
@ -168,15 +168,15 @@ argument.
 If the message text has length greater than
 .IR msgsz ,
 then the behavior depends on whether
-.BR MSG_NOERROR
+.B MSG_NOERROR
 is specified in
 .IR msgflg .
 If
-.BR MSG_NOERROR
+.B MSG_NOERROR
 is specified, then
 the message text will be truncated (and the truncated part will be
 lost); if
-.BR MSG_NOERROR
+.B MSG_NOERROR
 is not specified, then
 the message isn't removed from the queue and
 the system call fails returning \-1 with
@ -294,7 +294,7 @@ will be set to one among the following values:
 .B EACCES
 The calling process does not have write permission on the message queue,
 and does not have the
-.BR CAP_IPC_OWNER
+.B CAP_IPC_OWNER
 capability.
 .TP
 .B EAGAIN
@ -349,7 +349,7 @@ isn't specified in
 .B EACCES
 The calling process does not have read permission on the message queue,
 and does not have the
-.BR CAP_IPC_OWNER
+.B CAP_IPC_OWNER
 capability.
 .TP
 .B EAGAIN
--- a/man2/msync.2
+++ b/man2/msync.2
@ -72,13 +72,13 @@ On error, \-1 is returned, and
 is set appropriately.
 .SH ERRORS
 .TP
-.BR EBUSY
+.B EBUSY
 .B MS_INVALIDATE
 was specified in
 .IR flags ,
 and a memory lock exists for the specified address range.
 .TP
-.BR EINVAL
+.B EINVAL
 .I start
 is not a multiple of PAGESIZE; or any bit other than
 .BR MS_ASYNC " | " MS_INVALIDATE " | " MS_SYNC
--- a/man2/nanosleep.2
+++ b/man2/nanosleep.2
@ -50,7 +50,7 @@ In this case, it returns \-1, sets \fIerrno\fP to
 .BR EINTR ,
 and writes the
 remaining time into the structure pointed to by
-.IR rem
+.I rem
 unless
 .I rem
 is NULL.
@ -149,7 +149,7 @@ In Linux 2.4, if
 is stopped by a signal (e.g.,
 .BR SIGTSTP ),
 then the call fails with the error
-.BR EINTR
+.B EINTR
 after the process is resumed by a
 .B SIGCONT
 signal.
--- a/man2/nice.2
+++ b/man2/nice.2
@ -63,7 +63,7 @@ is set appropriately.
 .B EPERM
 The calling process attempted to increase its priority by
 supplying a negative
-.IR inc
+.I inc
 but has insufficient privileges.
 Under Linux the
 .B CAP_SYS_NICE
@ -77,7 +77,7 @@ SVr4, 4.3BSD, POSIX.1-2001.
 However, the Linux and (g)libc
 (earlier than glibc 2.2.4) return value is nonstandard, see below.
 SVr4 documents an additional
-.BR EINVAL
+.B EINVAL
 error code.
 .SH NOTES
 SUSv2 and POSIX.1-2001 specify that
--- a/man2/open.2
+++ b/man2/open.2
@ -52,7 +52,7 @@ open, creat \- open and possibly create a file or device
 .fi
 .SH DESCRIPTION
 Given a
-.IR pathname
+.I pathname
 for a file,
 .BR open ()
 returns a file descriptor, a small, non-negative integer
@ -151,7 +151,7 @@ Specifying this flag permits a program to avoid an additional
 .BR fcntl (2)
 .B F_SETFD
 operation to set the
-.BR FD_CLOEXEC
+.B FD_CLOEXEC
 flag.
 Additionally,
 use of this flag is essential in some multithreaded programs
@ -159,7 +159,7 @@ since using a separate
 .BR fcntl (2)
 .B F_SETFD
 operation to set the
-.BR FD_CLOEXEC
+.B FD_CLOEXEC
 flag does not suffice to avoid race conditions
 where one thread opens a file descriptor at the same
 time as another thread does a
@ -300,7 +300,7 @@ returned will cause the calling process to wait.
 For the handling of FIFOs (named pipes), see also
 .BR fifo (7).
 For a discussion of the effect of
-.BR O_NONBLOCK
+.B O_NONBLOCK
 in conjunction with mandatory file locks and with file leases, see
 .BR fcntl (2).
 .TP
@ -335,7 +335,7 @@ The argument
 specifies the permissions to use in case a new file is created.
 It is
 modified by the process's
-.IR umask
+.I umask
 in the usual way: the permissions of the created file are
 .IR "(mode & ~umask)" .
 Note that this mode only applies to future accesses of the
@ -423,7 +423,7 @@ already exists and
 were used.
 .TP
 .B EFAULT
-.IR pathname
+.I pathname
 points outside your accessible address space.
 .TP
 .B EFBIG
@ -459,7 +459,7 @@ was a symbolic link.
 The process already has the maximum number of files open.
 .TP
 .B ENAMETOOLONG
-.IR pathname
+.I pathname
 was too long.
 .TP
 .B ENFILE
@ -532,12 +532,12 @@ The
 .BR O_DIRECTORY ,
 .BR O_NOATIME ,
 and
-.BR O_NOFOLLOW
+.B O_NOFOLLOW
 flags are Linux specific.
 One may have to define the
 .B _GNU_SOURCE
 macro to get their definitions.
-.BR O_DIRECT
+.B O_DIRECT
 is not specified in POSIX; one has to define
 .B _GNU_SOURCE
 to get its definition.
--- a/man2/openat.2
+++ b/man2/openat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR open (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR open (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/prctl.2
+++ b/man2/prctl.2
@ -144,7 +144,7 @@ in \fIarg2\fP, which should be one of the following:
 .BR PR_ENDIAN_BIG ,
 .BR PR_ENDIAN_LITTLE ,
 or
-.BR PR_ENDIAN_PPC_LITTLE
+.B PR_ENDIAN_PPC_LITTLE
 (PowerPC pseudo little endian).
 .TP
 .B PR_SET_UNALIGN
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@ -118,7 +118,7 @@ be stopped.
 .TP
 .BR PTRACE_PEEKTEXT ", " PTRACE_PEEKDATA
 Reads a word at the location
-.IR addr
+.I addr
 in the child's memory, returning the word as the result of the
 .BR ptrace ()
 call.
@ -140,15 +140,15 @@ architecture.  (\fIdata\fP is ignored.)
 .TP
 .BR PTRACE_POKETEXT ", " PTRACE_POKEDATA
 Copies the word
-.IR data
+.I data
 to location
-.IR addr
+.I addr
 in the child's memory.
 As above, the two requests are currently equivalent.
 .TP
 .B PTRACE_POKEUSR
 Copies the word
-.IR data
+.I data
 to offset
 .I addr
 in the child's USER area.
@ -237,7 +237,7 @@ calls in all cases.
 If the child calls
 .BR clone (2)
 with the
-.BR CLONE_VFORK
+.B CLONE_VFORK
 flag,
 .B PTRACE_EVENT_VFORK
 will be delivered instead
@ -281,11 +281,11 @@ Retrieve a message (as an
 about the ptrace event
 that just happened, placing it in the location \fIdata\fP in the parent.
 For
-.BR PTRACE_EVENT_EXIT
+.B PTRACE_EVENT_EXIT
 this is the child's exit status.
 For
 .BR PTRACE_EVENT_FORK ,
-.BR PTRACE_EVENT_VFORK
+.B PTRACE_EVENT_VFORK
 and
 .B PTRACE_EVENT_CLONE
 this
@ -380,14 +380,14 @@ tracing.
 (\fIaddr\fP is ignored.)
 .SH "RETURN VALUE"
 On success,
-.BR PTRACE_PEEK*
+.B PTRACE_PEEK*
 requests return the requested data,
 while other requests return zero.
 On error, all requests return \-1, and
 .I errno
 is set appropriately.
 Since the value returned by a successful
-.BR PTRACE_PEEK*
+.B PTRACE_PEEK*
 request may be \-1, the caller must check
 .I errno
 after such requests to determine whether or not an error occurred.
@ -465,7 +465,7 @@ when it stops, and there is no way for the new parent to
 effectively simulate this notification.
 .LP
 When the parent receives an event with
-.BR PTRACE_EVENT_*
+.B PTRACE_EVENT_*
 set,
 the child is not in the normal signal delivery path.
 This means the parent cannot do
@ -474,7 +474,7 @@ with a signal or
 .BR ptrace (PTRACE_KILL).
 .BR kill (2)
 with a
-.BR SIGKILL
+.B SIGKILL
 signal can be used instead to kill the child process
 after receiving one of these messages.
 .LP
@ -495,13 +495,13 @@ present in Solaris 2 implements a superset of
 functionality in a more powerful and uniform way.
 .SH BUGS
 On hosts with 2.6 kernel headers,
-.BR PTRACE_SETOPTIONS
+.B PTRACE_SETOPTIONS
 is declared
 with a different value than the one for 2.4.
 This leads to applications compiled with such
 headers failing when run on 2.4 kernels.
 This can be worked around by redefining
-.BR PTRACE_SETOPTIONS
+.B PTRACE_SETOPTIONS
 to
 .BR PTRACE_OLDSETOPTIONS ,
 if that is defined.
--- a/man2/readlinkat.2
+++ b/man2/readlinkat.2
@ -46,7 +46,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR readlink (2)
@ -65,7 +65,7 @@ directory of the calling process (like
 .BR readlink (2)).

 If
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/readv.2
+++ b/man2/readv.2
@ -45,7 +45,7 @@ function reads
 buffers from the file associated with the file descriptor
 .I fd
 into the buffers described by
-.IR iov
+.I iov
 ("scatter input").
 .PP
 The
@ -55,7 +55,7 @@ function writes
 buffers of data described by
 .I iov
 to the file associated with the file descriptor
-.IR fd
+.I fd
 ("gather output").
 .PP
 The pointer
@ -165,7 +165,7 @@ the number of items that can be passed in
 An implementation can advertise its limit by defining
 .B IOV_MAX
 in
-.IR <limits.h>
+.I <limits.h>
 or at run time via the return value from
 .IR sysconf(_SC_IOV_MAX) .
 On Linux, the limit advertised by these mechanisms is 1024,
--- a/man2/reboot.2
+++ b/man2/reboot.2
@ -59,20 +59,20 @@ This system call will fail (with
 unless
 .I magic
 equals
-.BR LINUX_REBOOT_MAGIC1
+.B LINUX_REBOOT_MAGIC1
 (that is, 0xfee1dead) and
 .I magic2
 equals
-.BR LINUX_REBOOT_MAGIC2
+.B LINUX_REBOOT_MAGIC2
 (that is, 672274793).
 However, since 2.1.17 also
-.BR LINUX_REBOOT_MAGIC2A
+.B LINUX_REBOOT_MAGIC2A
 (that is, 85072278)
 and since 2.1.97 also
-.BR LINUX_REBOOT_MAGIC2B
+.B LINUX_REBOOT_MAGIC2B
 (that is, 369367448)
 and since 2.5.71 also
-.BR LINUX_REBOOT_MAGIC2C
+.B LINUX_REBOOT_MAGIC2C
 (that is, 537993216)
 are permitted as value for
 .IR magic2 .
--- a/man2/recv.2
+++ b/man2/recv.2
@ -127,7 +127,7 @@ one or more of the following values:
 .BR MSG_CMSG_CLOEXEC " (" recvmsg "() only; since Linux 2.6.23)"
 Set the close-on-exec flag for the file descriptor received
 via a Unix domain file descriptor using the
-.BR SCM_RIGHTS
+.B SCM_RIGHTS
 operation (described in
 .BR unix (7)).
 This flag is useful for the same reasons as the
--- a/man2/rename.2
+++ b/man2/rename.2
@ -123,7 +123,7 @@ it was open for reading) or is in use by the system
 (for example as mount point), while the system considers
 this an error.
 (Note that there is no requirement to return
-.BR EBUSY
+.B EBUSY
 in such
 cases \(em there is nothing wrong with doing the rename anyway \(em
 but it is allowed to return
@ -181,7 +181,7 @@ is a directory, and
 exists but is not a directory.
 .TP
 .BR ENOTEMPTY " or " EEXIST
-.IR newpath
+.I newpath
 is a non-empty directory, that is, contains entries other than "." and "..".
 .TP
 .BR EPERM " or " EACCES
@ -205,7 +205,7 @@ and the process is not privileged
 .B CAP_FOWNER
 capability);
 or the filesystem containing
-.IR pathname
+.I pathname
 does not support renaming of the type requested.
 .TP
 .B EROFS
--- a/man2/renameat.2
+++ b/man2/renameat.2
@ -45,7 +45,7 @@ If the pathname given in
 .I oldpath
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR olddirfd
+.I olddirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR rename (2)
@ -64,7 +64,7 @@ directory of the calling process (like
 .BR rename (2)).

 If
-.IR oldpath
+.I oldpath
 is absolute, then
 .I olddirfd
 is ignored.
@ -105,7 +105,7 @@ is a file descriptor referring to a file other than a directory;
 or similar for
 .I newpath
 and
-.IR newdirfd
+.I newdirfd
 .SH VERSIONS
 .BR renameat ()
 was added to Linux in kernel 2.6.16.
--- a/man2/rmdir.2
+++ b/man2/rmdir.2
@ -48,7 +48,7 @@ is set appropriately.
 Write access to the directory containing
 .I pathname
 was not allowed, or one of the directories in the path prefix of
-.IR pathname
+.I pathname
 did not allow search permission.
 (See also
 .BR path_resolution (7).
@ -99,7 +99,7 @@ contains entries other than
 or,
 .I pathname
 has
-.IR ..
+.I ..
 as its final component.
 .TP
 .B EPERM
@ -115,7 +115,7 @@ capability).
 .TP
 .B EPERM
 The filesystem containing
-.IR pathname
+.I pathname
 does not support the removal of directories.
 .TP
 .B EROFS
--- a/man2/sched_setaffinity.2
+++ b/man2/sched_setaffinity.2
@ -95,7 +95,7 @@ number that can be stored in a CPU set.

 .BR sched_setaffinity ()
 sets the CPU affinity mask of the process whose ID is
-.IR pid
+.I pid
 to the value specified by
 .IR mask .
 If
@ -117,7 +117,7 @@ then that process is migrated to one of the CPUs specified in

 .BR sched_getaffinity ()
 writes the affinity mask of the process whose ID is
-.IR pid
+.I pid
 into the
 .I cpu_set_t
 structure pointed to by
@ -161,7 +161,7 @@ needs an effective user ID equal to the user ID or effective user ID
 of the process identified by
 .IR pid ,
 or it must possess the
-.BR CAP_SYS_NICE
+.B CAP_SYS_NICE
 capability.
 .TP
 .B ESRCH
--- a/man2/sched_setscheduler.2
+++ b/man2/sched_setscheduler.2
@ -239,7 +239,7 @@ resource limit defines a ceiling on an unprivileged process's
 priority for the
 .B SCHED_RR
 and
-.BR SCHED_FIFO
+.B SCHED_FIFO
 policies.
 If an unprivileged process has a non-zero
 .B RLIMIT_RTPRIO
@ -369,13 +369,13 @@ kernel, the kernel configuration offers only the three preemption classes
 .BR CONFIG_PREEMPT_NONE ,
 .BR CONFIG_PREEMPT_VOLUNTARY ,
 and
-.BR CONFIG_PREEMPT_DESKTOP
+.B CONFIG_PREEMPT_DESKTOP
 which respectively provide no, some, and considerable
 reduction of the worst-case scheduling latency.

 With the patches applied or after their full inclusion into the mainline
 kernel, the additional configuration item
-.BR CONFIG_PREEMPT_RT
+.B CONFIG_PREEMPT_RT
 becomes available.
 If this is selected, Linux is transformed into a regular
 real-time operating system.
--- a/man2/semctl.2
+++ b/man2/semctl.2
@ -174,7 +174,7 @@ This structure is of type
 defined in
 .I <sys/sem.h>
 if the
-.BR _GNU_SOURCE
+.B _GNU_SOURCE
 feature test macro is defined:
 .nf
 .in +2n
@ -322,7 +322,7 @@ the semaphore set.
 Set the value of
 .B semval
 to
-.IB arg.val
+.I arg.val
 for the
 .IR semnum \-th
 semaphore of the set, updating also the
@ -408,9 +408,9 @@ capability.
 .TP
 .B EFAULT
 The address pointed to by
-.IB arg.buf
+.I arg.buf
 or
-.IB arg.array
+.I arg.array
 isn't accessible.
 .TP
 .B EIDRM
@ -463,7 +463,7 @@ SVr4, POSIX.1-2001.
 .SH NOTES
 The
 .BR IPC_INFO ,
-.BR SEM_STAT
+.B SEM_STAT
 and
 .B SEM_INFO
 operations are used by the
@ -481,7 +481,7 @@ under Linux 2.4.
 To take advantage of this,
 a recompilation under glibc-2.1.91 or later should suffice.
 (The kernel distinguishes old and new calls by an
-.BR IPC_64
+.B IPC_64
 flag in
 .IR cmd .)
 .PP
--- a/man2/semget.2
+++ b/man2/semget.2
@ -171,7 +171,7 @@ A semaphore set exists for
 .IR key ,
 but the calling process does not have permission to access the set,
 and does not have the
-.BR CAP_IPC_OWNER
+.B CAP_IPC_OWNER
 capability.
 .TP
 .B EEXIST
@ -188,7 +188,7 @@ and
 .\" The semaphore set is marked to be deleted.
 .TP
 .B EINVAL
-.IR nsems
+.I nsems
 is less than 0 or greater than the limit on the number
 of semaphores per semaphore set
 .RB ( SEMMSL ),
--- a/man2/semop.2
+++ b/man2/semop.2
@ -341,7 +341,7 @@ capability.
 .TP
 .B EAGAIN
 An operation could not proceed immediately and either
-.BR IPC_NOWAIT
+.B IPC_NOWAIT
 was specified in
 .I sem_flg
 or the time limit specified in
--- a/man2/set_mempolicy.2
+++ b/man2/set_mempolicy.2
@ -42,7 +42,7 @@ to the values specified by the
 .IR mode ,
 .I nodemask
 and
-.IR maxnode
+.I maxnode
 arguments.

 A NUMA machine has different
--- a/man2/setpgid.2
+++ b/man2/setpgid.2
@ -255,7 +255,7 @@ from the terminal;
 if a background process group tries to
 .BR read (2)
 from the terminal, then the group is send a
-.BR SIGTSTP
+.B SIGTSTP
 signal, which suspends it.
 The
 .BR tcgetpgrp (3)
--- a/man2/setresuid.2
+++ b/man2/setresuid.2
@ -72,7 +72,7 @@ is set appropriately.
 .I uid
 does not match the current UID and this call would
 bring that user ID over its
-.BR RLIMIT_NPROC
+.B RLIMIT_NPROC
 resource limit.
 .TP
 .B EPERM
--- a/man2/setuid.2
+++ b/man2/setuid.2
@ -78,7 +78,7 @@ The
 does not match the current uid and
 .I uid
 brings process over its
-.BR RLIMIT_NPROC
+.B RLIMIT_NPROC
 resource limit.
 .TP
 .B EPERM
--- a/man2/setxattr.2
+++ b/man2/setxattr.2
@ -128,7 +128,7 @@ If there is insufficient space remaining to store the extended attribute,
 is set to either
 .BR ENOSPC ,
 or
-.BR EDQUOT
+.B EDQUOT
 if quota enforcement was the cause.
 .PP
 If extended attributes are not supported by the filesystem, or are disabled,
--- a/man2/sgetmask.2
+++ b/man2/sgetmask.2
@ -22,7 +22,7 @@
 .SH NAME
 sgetmask, ssetmask \- manipulation of signal mask (obsolete)
 .SH SYNOPSIS
-.BI "long sgetmask(void);"
+.B "long sgetmask(void);"
 .sp
 .BI "long ssetmask(long " newmask );
 .SH DESCRIPTION
--- a/man2/shmctl.2
+++ b/man2/shmctl.2
@ -156,7 +156,7 @@ Returns information about system-wide shared memory limits and
 parameters in the structure pointed to by
 .IR buf .
 This structure is of type
-.IR shminfo
+.I shminfo
 (thus, a cast is required),
 defined in
 .I <sys/shm.h>
@ -237,7 +237,7 @@ Prevent swapping of the shared memory segment.
 The caller must fault in
 any pages that are required to be present after locking is enabled.
 If a segment has been locked, then the (non-standard)
-.BR SHM_LOCKED
+.B SHM_LOCKED
 flag of the
 .I shm_perm.mode
 field in the associated data structure retrieved by
@ -257,7 +257,7 @@ if its effective UID matches the owner or creator UID of the segment, and
 (for
 .BR SHM_LOCK )
 the amount of memory to be locked falls within the
-.BR RLIMIT_MEMLOCK
+.B RLIMIT_MEMLOCK
 resource limit (see
 .BR setrlimit (2)).
 .\" There was some weirdness in 2.6.9: SHM_LOCK and SHM_UNLOCK could
@ -293,7 +293,7 @@ is set appropriately.
 \fIshm_perm.mode\fP does not allow read access for
 .IR shmid ,
 and the calling process does not have the
-.BR CAP_IPC_OWNER
+.B CAP_IPC_OWNER
 capability.
 .TP
 .B EFAULT
@ -326,7 +326,7 @@ was specified and the size of the to-be-locked segment would mean
 that the total bytes in locked shared memory segments would exceed
 the limit for the real user ID of the calling process.
 This limit is defined by the
-.BR RLIMIT_MEMLOCK
+.B RLIMIT_MEMLOCK
 soft resource limit (see
 .BR setrlimit (2)).
 .TP
@ -356,7 +356,7 @@ was specified, but the process was not privileged
 .B CAP_IPC_LOCK
 capability).
 (Since Linux 2.6.9, this error can also occur if the
-.BR RLIMIT_MEMLOCK
+.B RLIMIT_MEMLOCK
 is 0 and the caller is not privileged.)
 .SH "CONFORMING TO"
 SVr4, POSIX.1-2001.
@ -366,7 +366,7 @@ SVr4, POSIX.1-2001.
 .SH NOTES
 The
 .BR IPC_INFO ,
-.BR SHM_STAT
+.B SHM_STAT
 and
 .B SHM_INFO
 operations are used by the
--- a/man2/shmget.2
+++ b/man2/shmget.2
@ -61,7 +61,7 @@ or
 isn't
 .BR IPC_PRIVATE ,
 no shared memory segment corresponding to
-.IR key
+.I key
 exists, and
 .B IPC_CREAT
 is specified in
@ -276,7 +276,7 @@ number of shared memory segments
 .RB ( SHMSEG ).
 .SS Linux Notes
 Until version 2.3.30 Linux would return
-.BR EIDRM
+.B EIDRM
 for a
 .BR shmget ()
 on a shared memory segment scheduled for deletion.
--- a/man2/sigaction.2
+++ b/man2/sigaction.2
@ -174,7 +174,7 @@ has been called.
 .B SA_ONESHOT
 is an obsolete, non-standard synonym for this flag.
 .TP
-.BR SA_ONSTACK
+.B SA_ONSTACK
 Call the signal handler on an alternate signal stack provided by
 .BR sigaltstack (2).
 If an alternate stack is not available, the default stack will be used.
@ -491,7 +491,7 @@ ignores a
 .BR SIGFPE ,
 .BR SIGILL ,
 or
-.BR SIGSEGV
+.B SIGSEGV
 signal that was not generated by
 .BR kill (2)
 or
--- a/man2/signal.2
+++ b/man2/signal.2
@ -49,7 +49,7 @@ See \fIPortability\fP below.

 .BR signal ()
 sets the disposition of the signal
-.IR signum
+.I signum
 to
 .IR handler ,
 which is either
--- a/man2/sigpending.2
+++ b/man2/sigpending.2
@ -44,7 +44,7 @@ returns 0 on success and \-1 on error.
 .SH ERRORS
 .TP
 .B EFAULT
-.IR set
+.I set
 points to memory which is not a valid part of the process address space.
 .SH "CONFORMING TO"
 POSIX.1-2001.
--- a/man2/sigprocmask.2
+++ b/man2/sigprocmask.2
@ -67,7 +67,7 @@ is NULL, then the signal mask is unchanged (i.e.,
 .I how
 is ignored),
 but the current value of the signal mask is nevertheless returned in
-.IR oldset
+.I oldset
 (it is not NULL).

 The use of
@ -94,7 +94,7 @@ If
 .BR SIGFPE ,
 .BR SIGILL ,
 or
-.BR SIGSEGV
+.B SIGSEGV
 are generated
 while they are blocked, the result is undefined,
 unless the signal was generated by the
--- a/man2/sigsuspend.2
+++ b/man2/sigsuspend.2
@ -85,7 +85,7 @@ signals by calling
 with the signal mask that was returned by
 .BR sigprocmask (2)
 (in the
-.IR oldset
+.I oldset
 argument).
 .PP
 See
--- a/man2/socketpair.2
+++ b/man2/socketpair.2
@ -96,7 +96,7 @@ non-BSD systems supporting clones of the BSD socket layer (including
 System V variants).
 .SH NOTES
 On Linux, the only supported domain for this call is
-.BR AF_UNIX
+.B AF_UNIX
 (or synonymously,
 .BR AF_LOCAL ).
 (Most implementations have the same restriction.)
--- a/man2/splice.2
+++ b/man2/splice.2
@ -70,7 +70,7 @@ must point to a buffer which specifies the starting
 offset from which bytes will be read from
 .IR fd_in ;
 in this case, the current file offset of
-.IR fd_in
+.I fd_in
 is not changed.
 Analogous statements apply for
 .I out_fd
@ -95,7 +95,7 @@ This makes the splice pipe operations non-blocking, but
 .BR splice ()
 may nevertheless block because the file descriptors that
 are spliced to/from may block (unless they have the
-.BR O_NONBLOCK
+.B O_NONBLOCK
 flag set).
 .TP
 .B SPLICE_F_MORE
--- a/man2/stat.2
+++ b/man2/stat.2
@ -139,7 +139,7 @@ field indicates the number of blocks allocated to the file, 512-byte units.
 when the file has holes.)

 The
-.IR st_blksize
+.I st_blksize
 field gives the "preferred" blocksize for efficient file system I/O.
 (Writing to a file in smaller chunks may cause
 an inefficient read-modify-rewrite.)
@ -336,7 +336,7 @@ POSIX does not describe the
 .BR S_IFDIR ,
 .BR S_IFCHR ,
 .BR S_IFIFO ,
-.BR S_ISVTX
+.B S_ISVTX
 bits, but instead demands the use of
 the macros
 .BR S_ISDIR (),
@ -437,7 +437,7 @@ structure have led to three successive versions of
 (slot
 .IR __NR_stat ),
 and
-.IR sys_stat64()
+.I sys_stat64()
 (new in kernel 2.4; slot
 .IR __NR_stat64 ).
 The glibc
--- a/man2/statvfs.2
+++ b/man2/statvfs.2
@ -171,7 +171,7 @@ respectively use the
 .IR f_frsize ,
 .IR f_frsize ,
 and
-.IR f_bsize
+.I f_bsize
 fields of the return value of
 .IR "statvfs(path,buf)" .
 .SH "SEE ALSO"
--- a/man2/symlink.2
+++ b/man2/symlink.2
@ -89,7 +89,7 @@ is set appropriately.
 Write access to the directory containing
 .I newpath
 is denied, or one of the directories in the path prefix of
-.IR newpath
+.I newpath
 did not allow search permission.
 (See also
 .BR path_resolution (7).)
@ -127,12 +127,12 @@ entry.
 .TP
 .B ENOTDIR
 A component used as a directory in
-.IR newpath
+.I newpath
 is not, in fact, a directory.
 .TP
 .B EPERM
 The filesystem containing
-.IR newpath
+.I newpath
 does not support the creation of symbolic links.
 .TP
 .B EROFS
--- a/man2/symlinkat.2
+++ b/man2/symlinkat.2
@ -45,7 +45,7 @@ If the pathname given in
 .I newpath
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR newdirfd
+.I newdirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR symlink (2)
@ -64,7 +64,7 @@ directory of the calling process (like
 .BR symlink (2)).

 If
-.IR newpath
+.I newpath
 is absolute, then
 .I newdirfd
 is ignored.
--- a/man2/syscalls.2
+++ b/man2/syscalls.2
@ -623,7 +623,7 @@ By now there are three different versions of
 (slot
 .IR __NR_stat ),
 and
-.IR sys_stat64()
+.I sys_stat64()
 (slot
 .IR __NR_stat64 ),
 with the last being the most current.
@ -639,7 +639,7 @@ Similarly, the defines
 .IR __NR_oldolduname ,
 .IR __NR_olduname ,
 and
-.IR __NR_uname
+.I __NR_uname
 refer to the routines
 .IR sys_olduname (),
 .IR sys_uname ()
@ -717,7 +717,7 @@ Thus, while other architectures have
 and
 .IR sys_mmap ()
 corresponding to
-.IR __NR_select
+.I __NR_select
 and
 .IR __NR_mmap ,
 on i386 one finds
@ -728,7 +728,7 @@ and
 parameter block) instead.
 These days passing five parameters
 is not a problem any more, and there is a
-.IR __NR__newselect
+.I __NR__newselect
 .\" (used by libc 6)
 that corresponds directly to
 .IR sys_select ()
--- a/man2/times.2
+++ b/man2/times.2
@ -47,7 +47,7 @@ times \- get process times
 stores the current process times in the
 .I "struct tms"
 that
-.IR buf
+.I buf
 points to.
 The
 .I struct tms
--- a/man2/unlink.2
+++ b/man2/unlink.2
@ -64,7 +64,7 @@ Write access to the directory containing
 .I pathname
 is not allowed for the process's effective UID, or one of the
 directories in
-.IR pathname
+.I pathname
 did not allow search permission.
 (See also
 .BR path_resolution (7).)
--- a/man2/unlinkat.2
+++ b/man2/unlinkat.2
@ -51,7 +51,7 @@ If the pathname given in
 .I pathname
 is relative, then it is interpreted relative to the directory
 referred to by the file descriptor
-.IR dirfd
+.I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
 .BR unlink (2)
@ -74,7 +74,7 @@ and
 .BR rmdir (2)).

 If the pathname given in
-.IR pathname
+.I pathname
 is absolute, then
 .I dirfd
 is ignored.
--- a/man2/wait.2
+++ b/man2/wait.2
@ -224,7 +224,7 @@ Only use this enclosed in #ifdef WCOREDUMP ... #endif.
 .BI WIFSTOPPED( status )
 returns true if the child process was stopped by delivery of a signal;
 this is only possible if the call was done using
-.BR WUNTRACED
+.B WUNTRACED
 or when the child is being traced (see
 .BR ptrace (2)).
 .TP
@ -371,12 +371,12 @@ Each of these calls sets
 to an appropriate value in the case of an error.
 .SH ERRORS
 .TP
-.BR ECHILD
+.B ECHILD
 (for
 .BR wait ())
 The calling process does not have any unwaited-for children.
 .TP
-.BR ECHILD
+.B ECHILD
 (for
 .BR waitpid ()
 or
@ -429,7 +429,7 @@ is set to
 or the
 .B SA_NOCLDWAIT
 flag is set for
-.BR SIGCHLD
+.B SIGCHLD
 (see
 .BR sigaction (2)),
 then children that terminate do not become zombies and a call to
--- a/man2/write.2
+++ b/man2/write.2
@ -48,7 +48,7 @@ write \- write to a file descriptor
 writes up to
 .I count
 bytes from the buffer pointed
-.IR buf
+.I buf
 to the file referred to by the file descriptor
 .IR fd .

--- a/man3/INFINITY.3
+++ b/man3/INFINITY.3
@ -60,7 +60,7 @@ See IEC 60559:1989.
 The macros
 .BR HUGE_VAL ,
 .BR HUGE_VALF ,
-.BR HUGE_VALL
+.B HUGE_VALL
 expand to constants of types \fIdouble\fP, \fIfloat\fP
 and \fIlong double\fP, respectively,
 that represent a large positive value, possibly plus infinity.
--- a/man3/__setfpucw.3
+++ b/man3/__setfpucw.3
@ -28,7 +28,7 @@ and the floating point environment, like
 .IR fegetenv ,
 .IR feholdexcept ,
 .IR fesetenv ,
-.IR feupdateenv
+.I feupdateenv
 and FPU exception handling, like
 .IR feclearexcept ,
 .IR fegetexceptflag ,
@ -41,7 +41,7 @@ and _FPU_SETCW macros from
 .I /usr/include/fpu_control.h
 can be used.
 .SH EXAMPLE
-.BR __setfpucw(0x1372)
+.B __setfpucw(0x1372)

 Set FPU control word on the i386 architecture to
 .br
@ -53,4 +53,4 @@ Set FPU control word on the i386 architecture to
 .SH "SEE ALSO"
 .BR feclearexcept (3)
 .br
-.IR /usr/include/i386/fpu_control.h
+.I /usr/include/i386/fpu_control.h
--- a/man3/aio_read.3
+++ b/man3/aio_read.3
@ -92,7 +92,7 @@ is not a valid file descriptor open for reading.
 One or more of
 .IR aio_offset ,
 .IR aio_reqprio ,
-.IR aio_nbytes
+.I aio_nbytes
 are invalid.
 .TP
 .B ENOSYS
--- a/man3/aio_return.3
+++ b/man3/aio_return.3
@ -45,7 +45,7 @@ the value that would have been returned in case of a synchronous
 .IR read ,
 .IR write ,
 or
-.IR fsync
+.I fsync
 request.
 Otherwise the return value is undefined.
 On error, the error value is returned.
--- a/man3/aio_write.3
+++ b/man3/aio_write.3
@ -101,7 +101,7 @@ but the starting position is at or beyond the maximum offset for this file.
 One or more of
 .IR aio_offset ,
 .IR aio_reqprio ,
-.IR aio_nbytes
+.I aio_nbytes
 are invalid.
 .TP
 .B ENOSYS
--- a/man3/argz_add.3
+++ b/man3/argz_add.3
@ -13,52 +13,52 @@ argz_next, argz_replace, argz_stringify \- functions to handle an argz list
 .sp
 .B "#include <argz.h>"
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_add(char **" argz ", size_t *" argz_len ", const char *" str );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_add_sep(char **" argz ", size_t *" argz_len ,
 .ti 20n
 .BI "const char *" str ", int " delim );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_append(char **" argz ", size_t *" argz_len ,
 .ti 20n
 .BI "const char *" buf ", size_t " buf_len );
 .sp
-.BI "size_t"
+.B "size_t"
 .BI "argz_count(const char *" argz ", size_t " argz_len );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_create(char * const " argv "[], char **" argz ,
 .ti 20n
 .BI "size_t *" argz_len );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_create_sep(const char *" str ", int " sep ", char **" argz ,
 .ti 20n
 .BI "size_t *" argz_len );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_delete(char **" argz ", size_t *" argz_len ", char *" entry );
 .sp
-.BI "void"
+.B "void"
 .BI "argz_extract(char *" argz ", size_t " argz_len ", char  **" argv );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_insert(char **" argz ", size_t *" argz_len ", char *" before ,
 .ti 20n
 .BI "const char *" entry );
 .sp
-.BI "char *"
+.B "char *"
 .BI "argz_next(char *" argz ", size_t " argz_len ", const char *" entry );
 .sp
-.BI "error_t"
+.B "error_t"
 .BI "argz_replace(char **" argz ", size_t *" argz_len ", const char *" str ,
 .ti 20n
 .BI "const char *" with ", unsigned int *" replace_count );
 .sp
-.BI "void"
+.B "void"
 .BI "argz_stringify(char *" argz ", size_t " len ", int " sep );
 .SH DESCRIPTION
 These functions are glibc-specific.
--- a/man3/backtrace.3
+++ b/man3/backtrace.3
@ -95,7 +95,7 @@ by
 .BR backtrace_symbols (),
 and must be freed by the caller.
 (The strings pointed to by
-.IR strings
+.I strings
 need not and should not be freed.)

 .BR backtrace_symbols_fd ()
--- a/man3/clearenv.3
+++ b/man3/clearenv.3
@ -28,7 +28,7 @@ clearenv \- clear the environment
 .nf
 .B #include <stdlib.h>
 .sp
-.BI "int clearenv(void);"
+.B "int clearenv(void);"
 .fi
 .sp
 .in -4n
--- a/man3/confstr.3
+++ b/man3/confstr.3
@ -118,7 +118,7 @@ is set to
 .BR EINVAL .
 .SH ERRORS
 .TP
-.BR EINVAL
+.B EINVAL
 If the value of
 .I name
 is invalid.
--- a/man3/dlopen.3
+++ b/man3/dlopen.3
@ -40,7 +40,7 @@ dynamic linking loader
 .sp
 .BI "void *dlopen(const char *" filename ", int " flag );
 .sp
-.BI "char *dlerror(void);"
+.B "char *dlerror(void);"
 .sp
 .BI "void *dlsym(void *" handle ", const char *" symbol );
 .sp
@ -89,7 +89,7 @@ contains a DT_RPATH tag, and does not contain a DT_RUNPATH tag,
 then the directories listed in the DT_RPATH tag are searched.
 .IP o
 If the environment variable
-.BR LD_LIBRARY_PATH
+.B LD_LIBRARY_PATH
 is defined to contain a colon-separated list of directories,
 then these are searched.
 (As a security measure this variable is ignored for set-user-ID and
@ -100,7 +100,7 @@ contains a DT_RUNPATH tag, then the directories listed in that tag
 are searched.
 .IP o
 The cache file
-.IR /etc/ld.so.cache
+.I /etc/ld.so.cache
 (maintained by
 .BR ldconfig (8))
 is checked to see whether it contains an entry for
@ -313,9 +313,9 @@ since the constructor/destructor routines will not be executed
 .\" void _fini(void) __attribute__((destructor));
 .LP
 Instead, libraries should export routines using the
-.BR __attribute__((constructor))
+.B __attribute__((constructor))
 and
-.BR __attribute__((destructor))
+.B __attribute__((destructor))
 function attributes.
 See the gcc info pages for information on these.
 Constructor routines are executed before
--- a/Show More
+++ b/Show More