Change itacised function names and page xrefs to bold

man2/arch_prctl.2

@@ -72,7 +72,7 @@ pointed to by the
 .I address 
 parameter.
 .SH NOTES
-.IR arch_prctl ()
+.BR arch_prctl ()
 is only supported on Linux/x86-64 for 64bit programs currently.
 
 The 64bit base changes when a new 32bit segment selector is loaded.
@@ -96,7 +96,7 @@ with the
 flag.
 
 No prototype for 
-.IR arch_prctl ()
+.BR arch_prctl ()
 in glibc 2.2. You have to declare it yourself for now.
 This will be fixed in future glibc versions.
 
@@ -118,7 +118,7 @@ is outside the process address space.
 .SH AUTHOR
 Man page written by Andi Kleen.
 .SH CONFORMANCE
-.IR arch_prctl ()
+.BR arch_prctl ()
 is a Linux/x86-64 extension and should not be used in programs intended to be portable.
 .SH "SEE ALSO"
 .BR mmap (2),

man2/capget.2

@@ -37,15 +37,15 @@ these functions (in particular the format of the
 types) is subject to change with each kernel revision.
 .sp
 The portable interfaces are
-.IR cap_set_proc (3)
+.BR cap_set_proc (3)
 and
-.IR cap_get_proc (3);
+.BR cap_get_proc (3);
 if possible you should use those interfaces in applications.
 If you wish to use the Linux extensions in applications, you should
 use the easier-to-use interfaces
-.IR capsetp (3)
+.BR capsetp (3)
 and 
-.IR capgetp (3).
+.BR capgetp (3).
 .SS "Current details"
 Now that you have been warned, some current kernel details.
 The structs are defined as follows.

man2/chroot.2

@@ -110,7 +110,7 @@ X/OPEN does not document EIO, ENOMEM or EFAULT error conditions.
 This interface is marked as legacy by X/OPEN.
 .SH NOTES
 FreeBSD has a stronger
-.IR jail ()
+.BR jail ()
 system call.
 .SH "SEE ALSO"
 .BR chdir (2),

man2/dup.2

@@ -117,7 +117,7 @@ like
 If
 .I newfd
 was open, any errors that would have been reported at
-.IR close ()
+.BR close ()
 time, are lost. A careful programmer will not use
 .BR dup2 ()
 without closing

man2/fcntl.2

@@ -365,7 +365,7 @@ Most commonly, the calling process specifies itself as the owner
 (that is,
 .I arg
 is specified as
-.IR getpid ()).
+.BR getpid ()).
 
 .\" From glibc.info:
 If you set the

man2/madvise.2

@@ -143,7 +143,7 @@ POSIX 1003.1-2001 describes
 .B posix_madvise
 with constants POSIX_MADV_NORMAL, etc.,
 with a behaviour close to that described here. There is a similar
-.IR posix_fadvise ()
+.BR posix_fadvise ()
 for file access.
 .SH "SEE ALSO"
 .BR getrlimit (2),

man2/mmap2.2

@@ -70,7 +70,7 @@ The function
 is available since Linux 2.3.31.
 It is Linux specific, and should be avoided in portable applications.
 See also the
-.IR mmap64 ()
+.BR mmap64 ()
 function that is part of the LFS (Large File Summit).
 .SH "SEE ALSO"
 .BR getpagesize (2),

man2/ptrace.2

@@ -222,7 +222,7 @@ functionality in a more powerful and uniform way.
 .SH "RETURN VALUE"
 On success, PTRACE_PEEK* requests return the requested data, while other requests
 return zero.  On error, all requests return \-1, and
-.IR errno (3)
+.I errno
 is set appropriately.  Since the value returned by a successful PTRACE_PEEK*
 request may be \-1, the caller must check
 .I errno

man2/socketpair.2

@@ -47,7 +47,7 @@ socketpair \- create a pair of connected sockets
 .BI "int socketpair(int " d ", int " type ", int " protocol ", int " sv [2]);
 .SH DESCRIPTION
 The
-.IR socketpair ()
+.BR socketpair ()
 call creates an unnamed pair of connected sockets in
 the specified domain
 .IR d ,

man2/statfs.2

@@ -191,7 +191,7 @@ containing an
 .B "unsigned long"
 .IR f_fsid .
 Linux, SunOS, HPUX, 4.4BSD have a system call
-.IR statfs ()
+.BR statfs ()
 that returns a
 .B "struct statfs"
 (defined in
@@ -222,7 +222,7 @@ when NFS-exported, and giving it out is a security concern.
 Under some OSes the
 .I fsid
 can be used as second parameter to the
-.IR sysfs ()
+.BR sysfs ()
 system call.
 .SH NOTES
 The kernel has system calls 
@@ -238,13 +238,13 @@ Some systems only have <sys/vfs.h>, other systems also have
 including the former is the best choice.
 
 LSB has deprecated the library calls
-.IR statfs ()
+.BR statfs ()
 and
-.IR fstatfs ()
+.BR fstatfs ()
 and tells us to use
-.IR statvfs ()
+.BR statvfs ()
 and
-.IR statvfs ()
+.BR statvfs ()
 instead.
 .SH "SEE ALSO"
 .BR path_resolution (2),

man2/uname.2

@@ -109,7 +109,7 @@ used length 9, the second one used 65, the third one also uses 65 but
 adds the \fIdomainname\fP field.
 .LP
 Part of the utsname information is also accessible via
-.IR sysctl ()
+.BR sysctl ()
 and via
 .IR /proc/sys/kernel/ { ostype ,
 .IR hostname ,

man2/unimplemented.2

@@ -39,27 +39,27 @@ to
 .BR ENOSYS .
 .SH NOTES
 Note that
-.IR ftime (3),
-.IR profil (3)
+.BR ftime (3),
+.BR profil (3)
 and
-.IR ulimit (3)
+.BR ulimit (3)
 are implemented as library functions.
 
 Some system calls, like
-.IR alloc_hugepages (2),
-.IR free_hugepages (2),
-.IR ioperm (2),
-.IR iopl (2),
+.BR alloc_hugepages (2),
+.BR free_hugepages (2),
+.BR ioperm (2),
+.BR iopl (2),
 and
-.IR vm86 (2)
+.BR vm86 (2)
 only exist on certain architectures.
 
 Some system calls, like
-.IR ipc (2),
-.IR create_module (2),
-.IR init_module (2),
+.BR ipc (2),
+.BR create_module (2),
+.BR init_module (2),
 and
-.IR delete_module (2)
+.BR delete_module (2)
 only exist when the Linux kernel was built with support for them.
 
 .SH "SEE ALSO"

man2/vfork.2

@@ -48,7 +48,7 @@ or returns from the function in which
 was called, or calls any other function before successfully calling
 .BR _exit ()
 or one of the
-.IR exec ()
+.BR exec ()
 family of functions.
 .SH ERRORS
 .TP
@@ -129,7 +129,7 @@ Formally speaking, the standard description given above does not allow
 one to use
 .BR vfork ()
 since a following
-.IR exec ()
+.BR exec ()
 might fail, and then what happens is undefined.
 
 Details of the signal handling are obscure and differ between systems.

man3/btree.3

@@ -44,18 +44,18 @@ btree \- btree database access method
 .fi
 .SH DESCRIPTION
 The routine
-.IR dbopen ()
+.BR dbopen ()
 is the library interface to database files.
 One of the supported file formats is btree files.
 The general description of the database access methods is in
-.IR dbopen (3),
+.BR dbopen (3),
 this manual page describes only the btree specific information.
 .PP
 The btree data structure is a sorted, balanced tree structure storing
 associated key/data pairs.
 .PP
 The btree access method specific data structure provided to
-.IR dbopen ()
+.BR dbopen ()
 is defined in the <db.h> include file as follows:
 .PP
 typedef struct {
@@ -90,7 +90,7 @@ R_DUP
 Permit duplicate keys in the tree, i.e. permit insertion if the key to be
 inserted already exists in the tree.
 The default behavior, as described in
-.IR dbopen (3),
+.BR dbopen (3),
 is to overwrite a matching key when inserting a new key or to fail if
 the R_NOOVERWRITE flag is specified.
 The R_DUP flag is overridden by the R_NOOVERWRITE flag, and if the
@@ -213,12 +213,12 @@ The
 access method routines may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR dbopen (3).
+.BR dbopen (3).
 .SH "SEE ALSO"
-.IR dbopen (3),
-.IR hash (3),
-.IR mpool (3),
-.IR recno (3)
+.BR dbopen (3),
+.BR hash (3),
+.BR mpool (3),
+.BR recno (3)
 .sp
 .IR "The Ubiquitous B-tree" ,
 Douglas Comer, ACM Comput. Surv. 11, 2 (June 1979), 121-138.

man3/catopen.3

@@ -115,7 +115,7 @@ and sets
 .I errno
 to indicate the error. The possible error values include all
 possible values for the
-.IR open ()
+.BR open ()
 call.
 .LP
 The function

man3/clearenv.3

@@ -66,10 +66,10 @@ will probably do.
 The DGUX and Tru64 manpages write: If
 .I environ
 has been modified by anything other than the
-.IR putenv (),
-.IR getenv (),
+.BR putenv (),
+.BR getenv (),
 or
-.IR clearenv ()
+.BR clearenv ()
 functions, then
 .BR clearenv ()
 will return an error and the process environment will remain unchanged.

man3/dbopen.3

@@ -58,10 +58,10 @@ The flat-file format is a byte stream file with fixed or variable length
 records.
 The formats and file format specific information are described in detail
 in their respective manual pages
-.IR btree (3),
-.IR hash (3)
+.BR btree (3),
+.BR hash (3)
 and
-.IR recno (3).
+.BR recno (3).
 .PP
 .BR dbopen ()
 opens
@@ -75,7 +75,7 @@ The
 and
 .I mode
 arguments are as specified to the
-.IR open (2)
+.BR open (2)
 routine, however, only the O_CREAT, O_EXCL, O_EXLOCK, O_NONBLOCK,
 O_RDONLY, O_RDWR, O_SHLOCK and O_TRUNC flags are meaningful.
 (Note, opening a database file O_WRONLY is not possible.)
@@ -189,9 +189,9 @@ with the same
 .I file
 name.
 This file descriptor may be safely used as an argument to the
-.IR fcntl (2)
+.BR fcntl (2)
 and
-.IR flock (2)
+.BR flock (2)
 locking functions.
 The file descriptor is not necessarily associated with any of the
 underlying files used by the access method.
@@ -365,7 +365,7 @@ recno file, not the recno file itself.
 (See the
 .I bfname
 field of the
-.IR recno (3)
+.BR recno (3)
 manual page for more information.)
 .RE
 .IP
@@ -404,9 +404,9 @@ The
 routine may fail and set
 .I errno
 for any of the errors specified for the library routines
-.IR open (2)
+.BR open (2)
 and
-.IR malloc (3)
+.BR malloc (3)
 or the following:
 .TP
 [EFTYPE]
@@ -424,12 +424,12 @@ The
 routines may fail and set
 .I errno
 for any of the errors specified for the library routines
-.IR close (2),
-.IR read (2),
-.IR write (2),
-.IR free (3),
+.BR close (2),
+.BR read (2),
+.BR write (2),
+.BR free (3),
 or
-.IR fsync (2).
+.BR fsync (2).
 .PP
 The
 .IR del ,
@@ -440,11 +440,11 @@ and
 routines may fail and set
 .I errno
 for any of the errors specified for the library routines
-.IR read (2),
-.IR write (2),
-.IR free (3)
+.BR read (2),
+.BR write (2),
+.BR free (3)
 or
-.IR malloc (3).
+.BR malloc (3).
 .PP
 The
 .I fd
@@ -457,12 +457,12 @@ The
 routines may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR fsync (2).
+.BR fsync (2).
 .SH "SEE ALSO"
-.IR btree (3),
-.IR hash (3),
-.IR mpool (3),
-.IR recno (3)
+.BR btree (3),
+.BR hash (3),
+.BR mpool (3),
+.BR recno (3)
 .sp
 .IR "LIBTP: Portable, Modular Transactions for UNIX" ,
 Margo Seltzer, Michael Olson, USENIX proceedings, Winter 1992.

man3/dprintf.3

@@ -49,9 +49,9 @@ instead of to a given stream.
 These functions are GNU extensions, not in C or POSIX.
 Clearly, the names were badly chosen.
 Many systems (like MacOS) have incompatible functions called
-.IR dprintf (),
+.BR dprintf (),
 usually some debugging version of
-.IR printf (),
+.BR printf (),
 perhaps with a prototype like
 
 .BI "void dprintf (int level, const char *" format ", ...);"
@@ -67,6 +67,6 @@ So, probably, it is better to avoid this function in programs
 intended to be portable.
 
 A better name would have been
-.IR fdprintf ().
+.BR fdprintf ().
 .SH "SEE ALSO"
 .BR printf (3)

man3/ecvt.3

@@ -64,7 +64,7 @@ The static string is overwritten by each call to \fBecvt\fP() or
 \fBfcvt\fP().
 .SH NOTES
 These functions are obsolete. Instead,
-.IR sprintf ()
+.BR sprintf ()
 is recommended.
 Linux libc4 and libc5 specified the type of
 .I ndigits

man3/ecvt_r.3

@@ -68,7 +68,7 @@ and
 These functions return 0 on success, and \-1 otherwise.
 .SH NOTES
 These functions are obsolete. Instead,
-.IR sprintf ()
+.BR sprintf ()
 is recommended.
 .SH "CONFORMING TO"
 These functions are GNU extensions.

man3/errno.3

@@ -330,7 +330,7 @@ where
 no longer needs to have the value it had upon return from
 .IR somecall ()
 (i.e., it may have been changed by the
-.IR printf ()).
+.BR printf ()).
 If the value of
 .I errno
 should be preserved across a library call, it must be saved:

man3/fenv.3

@@ -219,11 +219,11 @@ is defined.
 The C99 standard does not define a way to set individual bits in the
 floating point mask, e.g. to trap on specific flags.
 glibc 2.2 supports the functions
-.IR feenableexcept ()
+.BR feenableexcept ()
 and
-.IR fedisableexcept ()
+.BR fedisableexcept ()
 to set individual floating point traps, and
-.IR fegetexcept ()
+.BR fegetexcept ()
 to query the state.
 .sp
 .nf

man3/fmtmsg.3

@@ -176,22 +176,22 @@ severity-keyword,level,printstring
 .RE
 .sp
 then
-.IR fmtmsg ()
+.BR fmtmsg ()
 will also accept the indicated values for the level (in addition to
 the standard levels 0-4), and use the indicated printstring when
 such a level occurs.
 .LP
 The severity-keyword part is not used by
-.IR fmtmsg ()
+.BR fmtmsg ()
 but it has to be present.  
 The level part is a string representation of a number.  
 The numeric value must be a number greater than 4.
 This value must be used in the severity parameter of 
-.IR fmtmsg ()
+.BR fmtmsg ()
 to select this class.  It is not possible to overwrite
 any of the predefined classes.  The printstring
 is the string printed when a message of this class is processed by
-.IR fmtmsg ().
+.BR fmtmsg ().
 .SH "RETURN VALUES"
 The function can return 4 values:
 .TP 12n
@@ -209,16 +209,16 @@ Error writing to
 Error writing to the console.
 .SH "CONFORMING TO"
 The functions
-.IR fmtmsg ()
+.BR fmtmsg ()
 and
-.IR addseverity (),
+.BR addseverity (),
 and environment variables
 .B MSGVERB
 and
 .B SEV_LEVEL
 come from System V (XPG4-UNIX).
 The function
-.IR fmtmsg ()
+.BR fmtmsg ()
 and the environment variable
 .B MSGVERB
 are described in POSIX 1003.1-2001.

man3/fpurge.3

@@ -66,10 +66,10 @@ is not an open stream.
 .SH "CONFORMING TO"
 These functions are nonstandard and not portable.
 The function
-.IR fpurge ()
+.BR fpurge ()
 was introduced in 4.4BSD and is not available under Linux.
 The function
-.IR __fpurge ()
+.BR __fpurge ()
 was introduced in Solaris, and is present in glibc 2.1.95 and later.
 .SH NOTES
 Usually it is a mistake to want to discard input buffers.

man3/ftw.3

@@ -93,7 +93,7 @@ This \fIflags\fP argument is an OR of zero or more of the following flags:
 .TP
 .B FTW_CHDIR
 If set, do a
-.IR chdir ()
+.BR chdir ()
 to each directory before handling its contents.
 .TP
 .B FTW_DEPTH
@@ -142,25 +142,25 @@ the depth of the item relative to the starting point
 (which has depth 0).
 .SH NOTES
 The function
-.IR nftw ()
+.BR nftw ()
 and the use of FTW_SL with
-.IR ftw ()
+.BR ftw ()
 were introduced in XPG4v2.
 .LP
 On some systems
-.IR ftw ()
+.BR ftw ()
 will never use FTW_SL, on other systems FTW_SL occurs only
 for symbolic links that do not point to an existing file,
 and again on other systems
-.IR ftw ()
+.BR ftw ()
 will use FTW_SL for each symbolic link. For predictable control, use
-.IR nftw ().
+.BR nftw ().
 .LP
 Under Linux, libc4 and libc5 and glibc 2.0.6 will
 use FTW_F for all objects (files, symbolic links, fifos, etc)
 that can be stat'ed but are not a directory.
 The function
-.IR nftw ()
+.BR nftw ()
 is available since glibc 2.1.
 .SH "CONFORMING TO"
 AES, SVID2, SVID3, XPG2, XPG3, XPG4, XPG4v2.

man3/gcvt.3

@@ -42,7 +42,7 @@ terminated ASCII string and stores the result in \fIbuf\fP.  It produces
 F format or E format.
 .SH NOTES
 This function is obsolete. Instead,
-.IR sprintf ()
+.BR sprintf ()
 is recommended.
 .SH "RETURN VALUE"
 The \fBgcvt\fP() function returns the address of the string pointed to

man3/getfsent.3

@@ -106,7 +106,7 @@ function appeared in 4.0BSD; the other four functions appeared in 4.3BSD.
 .SH "CONFORMING TO"
 These functions are not in POSIX. Several operating systems have them,
 e.g., *BSD, SunOS, Digital Unix, AIX (which also has a
-.IR getfstype ()).
+.BR getfstype ()).
 HP-UX has functions of the same names, that however use a struct checklist
 instead of a struct fstab, and calls these functions obsolete, superseded by
 .BR getmntent (3).

man3/getumask.3

@@ -46,7 +46,7 @@ mode_t getumask(void) {
 .RE
 except that it is documented to be thread-safe (that is, shares
 a lock with the
-.IR umask ()
+.BR umask ()
 library call).
 .SH NOTES
 This function is documented but not implemented yet in glibc 2.2.5.

man3/gsignal.3

@@ -38,9 +38,9 @@ gsignal, ssignal \- software signal facility
 Don't use these functions under Linux.
 Due to a historical mistake, under Linux these functions are
 aliases for
-.IR raise ()
+.BR raise ()
 and
-.IR signal (),
+.BR signal (),
 respectively.
 .LP
 Elsewhere, on SYSV-like systems, these functions implement
@@ -75,9 +75,9 @@ These functions are available under AIX, DG-UX, HPUX, SCO, Solaris, Tru64.
 They are called obsolete under most of these systems, and are
 broken under Linux libc and glibc.
 Some systems also have
-.IR gsignal_r ()
+.BR gsignal_r ()
 and
-.IR ssignal_r ().
+.BR ssignal_r ().
 .SH "SEE ALSO"
 .BR kill (2),
 .BR signal (2),

man3/hash.3

@@ -48,7 +48,7 @@ The routine
 is the library interface to database files.
 One of the supported file formats is hash files.
 The general description of the database access methods is in
-.IR dbopen (3),
+.BR dbopen (3),
 this manual page describes only the hash specific information.
 .PP
 The hash data structure is an extensible, dynamic hashing scheme.
@@ -132,9 +132,9 @@ will attempt to determine if the hash function specified is the same as
 the one with which the database was created, and will fail if it is not.
 .PP
 Backward compatible interfaces to the routines described in
-.IR dbm (3),
+.BR dbm (3),
 and
-.IR ndbm (3)
+.BR ndbm (3)
 are provided, however these interfaces are not compatible with
 previous file formats.
 .SH ERRORS
@@ -143,12 +143,12 @@ The
 access method routines may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR dbopen (3).
+.BR dbopen (3).
 .SH "SEE ALSO"
-.IR btree (3),
-.IR dbopen (3),
-.IR mpool (3),
-.IR recno (3)
+.BR btree (3),
+.BR dbopen (3),
+.BR mpool (3),
+.BR recno (3)
 .sp
 .IR "Dynamic Hash Tables" ,
 Per-Ake Larson, Communications of the ACM, April 1988.

man3/inet_pton.3

@@ -79,7 +79,7 @@ bytes long.
 Certain legacy hex and octal formats of
 .B AF_INET
 addresses are not supported by
-.IR inet_pton (),
+.BR inet_pton (),
 which rejects them.
 .SH "RETURN VALUE"
 .BR inet_pton ()

man3/lseek64.3

@@ -53,11 +53,11 @@ For more details, return value, and errors, see
 .BR lseek (2).
 .PP
 Four interfaces are available:
-.IR lseek (),
-.IR lseek64 (),
-.IR llseek (),
+.BR lseek (),
+.BR lseek64 (),
+.BR llseek (),
 and the raw system call
-.IR _llseek ().
+.BR _llseek ().
 .SS lseek
 Prototype:
 .nf
@@ -68,9 +68,9 @@ Prototype:
 .fi
 .sp
 The library routine
-.IR lseek ()
+.BR lseek ()
 uses the type
-.BR off_t .
+.IR off_t .
 This is a 32-bit signed type on 32-bit architectures, unless one
 compiles with
 .nf
@@ -92,11 +92,11 @@ Prototype:
 .fi
 .sp
 The library routine
-.IR lseek64 ()
+.BR lseek64 ()
 uses a 64-bit type even when
-.B off_t
+.I off_t
 is a 32-bit type. Its prototype (and the type
-.BR off64_t )
+.IR off64_t )
 is available only when one compiles with
 .nf
 .sp
@@ -106,10 +106,10 @@ is available only when one compiles with
 .sp
 .fi
 The function
-.IR lseek64 ()
+.BR lseek64 ()
 .\" in glibc 2.0.94, not in 2.0.6
 is available since glibc 2.1, and is defined to be an alias for
-.IR llseek ().
+.BR llseek ().
 
 .SS llseek
 Prototype:
@@ -121,10 +121,10 @@ Prototype:
 .fi
 .sp
 The type
-.B loff_t
+.I loff_t
 is a 64-bit signed type.
 The library routine
-.IR llseek ()
+.BR llseek ()
 .\" in libc 5.0.9, not in 4.7.6
 is available in libc5 and glibc and works without special defines.
 Its prototype was given in

man3/malloc.3

@@ -122,7 +122,7 @@ or
 if the request fails. If
 .I size
 was equal to 0, either NULL or a pointer suitable to be passed to
-.IR free ()
+.BR free ()
 is returned.  If
 .BR realloc ()
 fails the original block is left untouched; it is not freed or moved.

man3/malloc_hook.3

@@ -30,10 +30,10 @@ __after_morecore_hook \- malloc debugging variables
 .BI "void (*__after_morecore_hook)(void);"
 .SH DESCRIPTION
 The GNU C library lets you modify the behavior of
-.IR malloc (),
-.IR realloc (),
+.BR malloc (),
+.BR realloc (),
 and
-.IR free ()
+.BR free ()
 by specifying appropriate hook functions.  You can use these hooks
 to help you debug programs that use dynamic memory allocation,
 for example.
@@ -58,20 +58,20 @@ The four functions pointed to by
 .BR __memalign_hook ,
 .BR __free_hook
 have a prototype like the functions
-.IR malloc (),
-.IR realloc (),
-.IR memalign (),
-.IR free (),
+.BR malloc (),
+.BR realloc (),
+.BR memalign (),
+.BR free (),
 respectively, except that they have a final argument
 .I caller
 that gives the address of the caller of
-.IR malloc (),
+.BR malloc (),
 etc.
 .LP
 The variable
 .B __after_morecore_hook
 points at a function that is called each time after
-.IR sbrk ()
+.BR sbrk ()
 was asked for more memory.
 .SH "EXAMPLE"
 Here is a short example of how to use these variables.

man3/mpool.3

@@ -72,7 +72,7 @@ of files.
 The buffers may be shared between processes.
 .PP
 The function
-.IR mpool_open ()
+.BR mpool_open ()
 initializes a memory pool.
 The
 .I key
@@ -104,7 +104,7 @@ buffers, but will be the largest value specified by any of the processes
 sharing the file.
 .PP
 The
-.IR mpool_filter ()
+.BR mpool_filter ()
 function is intended to make transparent input and output processing of the
 pages possible.
 If the
@@ -120,7 +120,7 @@ Both functions are called with the
 pointer, the page number and a pointer to the page to being read or written.
 .PP
 The function
-.IR mpool_new ()
+.BR mpool_new ()
 takes an MPOOL pointer and an address as arguments.
 If a new page can be allocated, a pointer to the page is returned and
 the page number is stored into the
@@ -129,21 +129,21 @@ address.
 Otherwise, NULL is returned and errno is set.
 .PP
 The function
-.IR mpool_get ()
+.BR mpool_get ()
 takes a MPOOL pointer and a page number as arguments.
 If the page exists, a pointer to the page is returned.
 Otherwise, NULL is returned and errno is set.
 The flags parameter is not currently used.
 .PP
 The function
-.IR mpool_put ()
+.BR mpool_put ()
 unpins the page referenced by
 .IR pgaddr .
 .I pgaddr
 must be an address previously returned by
-.IR mpool_get ()
+.BR mpool_get ()
 or
-.IR mpool_new ().
+.BR mpool_new ().
 The flag value is specified by
 .IR or 'ing
 any of the following values:
@@ -151,35 +151,35 @@ any of the following values:
 MPOOL_DIRTY
 The page has been modified and needs to be written to the backing file.
 .PP
-.IR mpool_put ()
+.BR mpool_put ()
 returns 0 on success and \-1 if an error occurs.
 .PP
 The function
-.IR mpool_sync ()
+.BR mpool_sync ()
 writes all modified pages associated with the MPOOL pointer to the
 backing file.
-.IR mpool_sync ()
+.BR mpool_sync ()
 returns 0 on success and \-1 if an error occurs.
 .PP
 The
-.IR mpool_close ()
+.BR mpool_close ()
 function free's up any allocated memory associated with the memory pool
 cookie.
 Modified pages are
 .B not
 written to the backing file.
-.IR mpool_close ()
+.BR mpool_close ()
 returns 0 on success and \-1 if an error occurs.
 .SH ERRORS
 The
-.IR mpool_open ()
+.BR mpool_open ()
 function may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR malloc (3).
+.BR malloc (3).
 .PP
 The
-.IR mpool_get ()
+.BR mpool_get ()
 function may fail and set
 .I errno
 for the following:
@@ -188,32 +188,32 @@ for the following:
 The requested record doesn't exist.
 .PP
 The
-.IR mpool_new ()
+.BR mpool_new ()
 and
-.IR mpool_get ()
+.BR mpool_get ()
 functions may fail and set
 .I errno
 for any of the errors specified for the library routines
-.IR read (2) ,
-.IR write (2) ,
+.BR read (2) ,
+.BR write (2) ,
 and
-.IR malloc (3).
+.BR malloc (3).
 .PP
 The
-.IR mpool_sync ()
+.BR mpool_sync ()
 function may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR write (2).
+.BR write (2).
 .PP
 The
-.IR mpool_close ()
+.BR mpool_close ()
 function may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR free (3).
+.BR free (3).
 .SH "SEE ALSO"
-.IR dbopen (3),
-.IR btree (3),
-.IR hash (3),
-.IR recno (3)
+.BR dbopen (3),
+.BR btree (3),
+.BR hash (3),
+.BR recno (3)

man3/mtrace.3

@@ -15,10 +15,10 @@ mtrace, muntrace \- malloc debugging
 The function
 .BR mtrace ()
 installs handlers for
-.IR malloc (),
-.IR realloc ()
+.BR malloc (),
+.BR realloc ()
 and
-.IR free ().
+.BR free ().
 The function
 .BR muntrace ()
 disables these handlers.

man3/nan.3

@@ -27,13 +27,13 @@ The call
 is equivalent to 
 .I strtod ("NAN(char-sequence)",NULL)
 and similarly calls to
-.IR nanf ()
+.BR nanf ()
 and
-.IR nanl ()
+.BR nanl ()
 are equivalent to analogous calls to
-.IR strtof ()
+.BR strtof ()
 and
-.IR strtold ().
+.BR strtold ().
 .PP
 The argument
 .I tagp

man3/posix_memalign.3

@@ -116,19 +116,19 @@ parameter is correct.
 POSIX requires that memory obtained from
 .BR posix_memalign ()
 can be freed using
-.IR free ().
+.BR free ().
 Some systems provide no way to reclaim memory allocated with
-.IR memalign ()
+.BR memalign ()
 or
-.IR valloc ()
+.BR valloc ()
 (because one can only pass to
-.IR free ()
+.BR free ()
 a pointer gotten from
-.IR malloc (),
+.BR malloc (),
 while e.g.
-.IR memalign ()
+.BR memalign ()
 would call
-.IR malloc ()
+.BR malloc ()
 and then align the obtained value).
 .\" Other systems allow passing the result of
 .\" .IR valloc ()
@@ -138,7 +138,7 @@ and then align the obtained value).
 .\" .IR realloc ().
 GNU libc allows memory obtained from any of these three routines to be
 reclaimed with
-.IR free ().
+.BR free ().
 
 GNU libc
 .BR malloc ()
@@ -147,38 +147,38 @@ needed if you require larger alignment values.
 
 .SH AVAILABILITY
 The functions
-.IR memalign ()
+.BR memalign ()
 and
-.IR valloc ()
+.BR valloc ()
 have been available in all Linux libc libraries.
 The function
-.IR posix_memalign ()
+.BR posix_memalign ()
 is available since glibc 2.1.91.
 
 .SH "CONFORMING TO"
 The function
-.IR valloc ()
+.BR valloc ()
 appeared in 3.0 BSD. It is documented as being obsolete in 4.3BSD,
 and as legacy in SUSv2. It no longer occurs in SUSv3.
 The function
-.IR memalign ()
+.BR memalign ()
 appears in SunOS 4.1.3 but not in 4.4BSD.
 The function
-.IR posix_memalign ()
+.BR posix_memalign ()
 comes from POSIX 1003.1d.
 
 .SH HEADERS
 Everybody agrees that
-.IR posix_memalign ()
+.BR posix_memalign ()
 is declared in <stdlib.h>. In order to declare it, glibc needs
 _GNU_SOURCE defined, or _XOPEN_SOURCE defined to a value not less than 600.
 
 Everybody agrees that
-.IR memalign ()
+.BR memalign ()
 is declared in <malloc.h>.
 
 According to SUSv2,
-.IR valloc ()
+.BR valloc ()
 is declared in <stdlib.h>.
 Libc4,5 and glibc declare it in <malloc.h> and perhaps also in <stdlib.h>
 (namely, if _GNU_SOURCE is defined, or _BSD_SOURCE is defined, or,

man3/printf.3

@@ -877,15 +877,15 @@ and
 .BR vsnprintf (),
 and the length modifier q.
 FreeBSD also has functions
-.IR asprintf ()
+.BR asprintf ()
 and
-.IR vasprintf (),
+.BR vasprintf (),
 that allocate a buffer large enough for
 .BR sprintf ().
 In glibc there are functions
-.I dprintf
+.BR dprintf ()
 and
-.I vdprintf
+.BR vdprintf ()
 that print to a file descriptor instead of a stream.
 .SH BUGS
 Because

man3/qecvt.3

@@ -57,7 +57,7 @@ and
 .BR gcvt (3).
 .SH NOTES
 These functions are obsolete. Instead,
-.IR sprintf ()
+.BR sprintf ()
 is recommended.
 .SH "CONFORMING TO"
 SysVr4.0. Not seen in most common Unix implementations,

man3/qsort.3

@@ -61,10 +61,10 @@ SVID 3, POSIX, 4.3BSD, ISO 9899
 Library routines suitable for use as the
 .I compar
 argument include
-.IR strcmp (),
-.IR alphasort (),
+.BR strcmp (),
+.BR alphasort (),
 and
-.IR versionsort ().
+.BR versionsort ().
 .SH EXAMPLE
 For an example of use, see the example on the
 .BR bsearch (3)

man3/realpath.3

@@ -121,15 +121,15 @@ impossible to determine a suitable size for the output buffer,
 According to POSIX a buffer of size PATH_MAX suffices, but
 PATH_MAX need not be a defined constant, and may have to be
 obtained using
-.IR pathconf ().
+.BR pathconf ().
 And asking
-.IR pathconf ()
+.BR pathconf ()
 does not really help, since on the one hand POSIX warns that
 the result of
-.IR pathconf ()
+.BR pathconf ()
 may be huge and unsuitable for mallocing memory. And on the other
 hand
-.IR pathconf ()
+.BR pathconf ()
 may return \-1 to signify that PATH_MAX is not bounded.
 .LP
 The libc4 and libc5 implementation contains a buffer overflow
@@ -144,7 +144,7 @@ In Linux this function appears in libc 4.5.21.
 In 4.4BSD and Solaris the limit on the pathname length is MAXPATHLEN
 (found in <sys/param.h>). The SUSv2 prescribes PATH_MAX and
 NAME_MAX, as found in <limits.h> or provided by the
-.IR pathconf ()
+.BR pathconf ()
 function. A typical source fragment would be
 .LP
 .RS

man3/recno.3

@@ -48,7 +48,7 @@ The routine
 is the library interface to database files.
 One of the supported file formats is record number files.
 The general description of the database access methods is in
-.IR dbopen (3),
+.BR dbopen (3),
 this manual page describes only the recno specific information.
 .PP
 The record number data structure is either variable or fixed-length
@@ -137,7 +137,7 @@ If
 is 0 (no page size is specified) a page size is chosen based on the
 underlying file system I/O block size.
 See
-.IR btree (3)
+.BR btree (3)
 for more information.
 .TP
 lorder
@@ -197,17 +197,17 @@ The
 access method routines may fail and set
 .I errno
 for any of the errors specified for the library routine
-.IR dbopen (3)
+.BR dbopen (3)
 or the following:
 .TP
 [EINVAL]
 An attempt was made to add a record to a fixed-length database that
 was too large to fit.
 .SH "SEE ALSO"
-.IR btree (3)
-.IR dbopen (3),
-.IR hash (3),
-.IR mpool (3),
+.BR btree (3)
+.BR dbopen (3),
+.BR hash (3),
+.BR mpool (3),
 .sp
 .IR "Document Processing in a Relational Database System" ,
 Michael Stonebraker, Heidi Stettner, Joseph Kalash, Antonin Guttman,

man3/remove.3

@@ -39,9 +39,9 @@ remove \- delete a name and possibly the file it refers to
 .BR remove ()
 deletes a name from the filesystem.
 It calls
-.IR unlink ()
+.BR unlink ()
 for files, and
-.IR rmdir ()
+.BR rmdir ()
 for directories.
 
 If the removed name was the

man3/syslog.3

@@ -259,13 +259,13 @@ A
 .BR syslog ()
 function call appeared in 4.2BSD.
 4.3BSD documents
-.IR openlog (),
-.IR syslog (),
-.IR closelog (),
+.BR openlog (),
+.BR syslog (),
+.BR closelog (),
 and
-.IR setlogmask ().
+.BR setlogmask ().
 4.3BSD-Reno also documents
-.IR vsyslog ().
+.BR vsyslog ().
 Of course early v* functions used the
 .I <varargs.h>
 mechanism, which is not compatible with

man3/tgamma.3

@@ -38,7 +38,7 @@ outside the poles:
 This function returns the value of the Gamma function for the
 argument \fIx\fP. It had to be called "true gamma function"
 since there is already a function
-.IR gamma ()
+.BR gamma ()
 that returns something else.
 .SH ERRORS
 In order to check for errors, set

man3/ualarm.3

@@ -85,16 +85,16 @@ Programs will be more portable if they never mention this type explicitly.
 .LP
 The interaction of this function with
 other timer functions such as
-.IR alarm (),
-.IR sleep (),
-.IR nanosleep (),
-.IR setitimer (),
-.IR timer_create (),
-.IR timer_delete (),
-.IR timer_getoverrun (),
-.IR timer_gettime (),
-.IR timer_settime (),
-.IR usleep ()
+.BR alarm (),
+.BR sleep (),
+.BR nanosleep (),
+.BR setitimer (),
+.BR timer_create (),
+.BR timer_delete (),
+.BR timer_getoverrun (),
+.BR timer_gettime (),
+.BR timer_settime (),
+.BR usleep ()
 is unspecified.
 .LP
 This function is obsolete. Use

man3/unlockpt.3

@@ -14,16 +14,16 @@ unlockpt \- unlock a pseudo-terminal master/slave pair
 .fi
 .SH DESCRIPTION
 The
-.IR unlockpt ()
+.BR unlockpt ()
 function unlocks the slave pseudo-terminal device
 (pty) corresponding to the master pty referred to by
 .IR fd .
 .PP
-.IR unlockpt ()
+.BR unlockpt ()
 should be called before opening the slave side of a pty.
 .SH "RETURN VALUE"
 When successful,
-.IR unlockpt ()
+.BR unlockpt ()
 returns 0. Otherwise, it returns \-1 and sets
 .I errno
 appropriately.
@@ -41,8 +41,8 @@ argument is not associated with a master pty.
 .SH "CONFORMING TO"
 POSIX 1003.1-2001.
 .SH "SEE ALSO"
-.IR grantpt (3),
+.BR grantpt (3),
 .BR posix_openpt (3),
-.IR ptsname (3),
+.BR ptsname (3),
 .BR pts (4),
 .BR pty (7)

man3/usleep.3

@@ -93,16 +93,16 @@ or both _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED are defined.
 .LP
 The interaction of this function with the SIGALRM signal, and with
 other timer functions such as
-.IR alarm (),
-.IR sleep (),
-.IR nanosleep (),
-.IR setitimer (),
-.IR timer_create (),
-.IR timer_delete (),
-.IR timer_getoverrun (),
-.IR timer_gettime (),
-.IR timer_settime (),
-.IR ualarm ()
+.BR alarm (),
+.BR sleep (),
+.BR nanosleep (),
+.BR setitimer (),
+.BR timer_create (),
+.BR timer_delete (),
+.BR timer_getoverrun (),
+.BR timer_gettime (),
+.BR timer_settime (),
+.BR ualarm ()
 is unspecified.
 .LP
 This function is obsolete. Use

man4/dsp56k.4

@@ -58,7 +58,7 @@ received in 8, 16, 24, or 32-bit quantities on the host side, but will
 always be seen as 24-bit quantities in the DSP56001.
 .PP
 The following
-.IR ioctl (2)
+.BR ioctl (2)
 calls are used to control the
 \fBdsp56k\fP device:
 .IP \fBDSP56K_UPLOAD\fP

man4/random.4

@@ -114,17 +114,17 @@ The file
 .I read_wakeup_threshold
 contains the number of bits of entropy required for waking up processes
 that sleep waiting for entropy from
-.BR /dev/random .
+.IR /dev/random .
 The default is 64.
 The file
 .I write_wakeup_threshold
 contains the number of bits of entropy below which we wake up
 processes that do a
-.IR select ()
+.BR select ()
 or
-.IR poll ()
+.BR poll ()
 for write access to
-.BR /dev/random .
+.IR /dev/random .
 These values can be changed by writing to the files.
 .LP
 The read-only files

man4/sd.4

@@ -119,7 +119,7 @@ The
 are also supported.  If the
 .BR ioctl (2)
 parameter is required, and it is NULL, then
-.IR ioctl ()
+.BR ioctl ()
 will return \-EINVAL.
 .SH FILES
 /dev/sd[a\-h]: the whole device

man4/tty_ioctl.4

@@ -13,7 +13,7 @@ tty ioctl \- ioctls for terminals and serial lines
 .sp
 .SH DESCRIPTION
 The
-.IR ioctl ()
+.BR ioctl ()
 call for terminals and serial ports accepts many possible command arguments.
 Most require a third argument, of varying type, here called \fIargp\fP
 or \fIarg\fP.
@@ -374,7 +374,7 @@ Get the tty_struct corresponding to
 
 .SH "RETURN VALUE"
 The
-.IR ioctl ()
+.BR ioctl ()
 system call returns 0 on success. On error it returns \-1 and sets
 .I errno
 appropriately.

man4/vcs.4

@@ -55,7 +55,7 @@ The devices for the first eight virtual consoles may be created by:
 .fi
 
 No
-.IR ioctl ()
+.BR ioctl ()
 requests are supported.  
 .SH EXAMPLES
 You may do a screendump on vt3 by switching to vt1 and typing 

man5/environ.5

@@ -150,10 +150,10 @@ to be used with \fBgethostbyname\fP(3).
 give time zone information used by
 .BR tzset (3)
 and through that by functions like
-.IR ctime (),
-.IR localtime (),
-.IR mktime (),
-.IR strftime ().
+.BR ctime (),
+.BR localtime (),
+.BR mktime (),
+.BR strftime ().
 See also
 .BR tzselect (1).
 .LP

man5/proc.5

@@ -592,7 +592,7 @@ except in bytes rather than KB.
 .I /proc/mounts
 This is a list of all the file systems currently mounted on the system.
 The format of this file is documented in
-.IR fstab (5).
+.BR fstab (5).
 .TP
 .I /proc/modules
 A text list of the modules that have been loaded by the system.

man5/resolv.conf.5

@@ -162,7 +162,7 @@ or control characters.
 sets RES_USE_INET6 in
 .IR _res.options .
 This has the effect of trying a AAAA query before an A query inside the
-.IR gethostbyname ()
+.BR gethostbyname ()
 function, and of mapping IPv4 responses in IPv6 ``tunnelled form''
 if no AAAA records are found but an A record set exists.
 .RE