Remove section numbers for page references where the

reference refers to the page itself.  (This stops man2html
producing links from a page back to itself.)

man2/chroot.2

@@ -47,7 +47,7 @@ The root directory is inherited by all children of the current process.
 Only a privileged process (Linux: one with the
 .B CAP_SYS_CHROOT
 capability) may call
-.BR chroot (2).
+.BR chroot ().
 
 This call changes an ingredient in the pathname resolution process
 and does nothing else.

man2/clone.2

@@ -237,7 +237,7 @@ as seen by that process.
 After a
 .BR fork (2)
 or
-.BR clone (2)
+.BR clone ()
 where the
 .B CLONE_NEWNS
 flag is not set, the child lives in the same namespace as the parent.
@@ -250,7 +250,7 @@ all processes that live in the same namespace, but do not affect
 processes in a different namespace.
 
 After a
-.BR clone (2)
+.BR clone ()
 where the
 .B CLONE_NEWNS
 flag is set, the cloned child is started in a new namespace,

man2/epoll_create.2

@@ -43,15 +43,15 @@ The returned file descriptor will be used for all the subsequent calls to the
 .B epoll
 interface.
 The file descriptor returned by
-.BR epoll_create (2)
+.BR epoll_create ()
 must be closed by using
 .BR close (2).
 .SH "RETURN VALUE"
 When successful,
-.BR epoll_create (2)
+.BR epoll_create ()
 returns a non-negative integer identifying the descriptor.
 When an error occurs,
-.BR epoll_create (2)
+.BR epoll_create ()
 returns \-1 and
 .I errno
 is set appropriately.
@@ -67,7 +67,7 @@ The system limit on the total number of open files has been reached.
 .B ENOMEM
 There was insufficient memory to create the kernel object.
 .SH CONFORMING TO
-.BR epoll_create (2)
+.BR epoll_create ()
 is Linux specific, and was introduced in kernel 2.5.44.
 .\" The interface should be finalized by Linux kernel 2.5.66.
 .SH "SEE ALSO"

man2/epoll_ctl.2

@@ -116,7 +116,7 @@ will be reported by the
 .B epoll
 interface.
 The user must call
-.BR epoll_ctl (2)
+.BR epoll_ctl ()
 with
 .B EPOLL_CTL_MOD
 to re-enable the file descriptor with a new event mask.
@@ -161,10 +161,10 @@ is ignored and can be NULL (but see BUGS below).
 .RE
 .SH "RETURN VALUE"
 When successful,
-.BR epoll_ctl (2)
+.BR epoll_ctl ()
 returns zero.
 When an error occurs,
-.BR epoll_ctl (2)
+.BR epoll_ctl ()
 returns \-1 and
 .I errno
 is set appropriately.
@@ -220,7 +220,7 @@ The target file
 does not support
 .BR epoll .
 .SH CONFORMING TO
-.BR epoll_ctl (2)
+.BR epoll_ctl ()
 is Linux specific, and was introduced in kernel 2.5.44.
 .\" The interface should be finalized by Linux kernel 2.5.66.
 .SH BUGS

man2/epoll_wait.2

@@ -49,18 +49,18 @@ will contain the events that will be available for the caller.
 Up to
 .I maxevents
 are returned by
-.BR epoll_wait (2).
+.BR epoll_wait ().
 The
 .I maxevents
 parameter must be greater than zero.
 Specifying a
 .I timeout
 of \-1 makes
-.BR epoll_wait (2)
+.BR epoll_wait ()
 wait indefinitely, while specifying a
 .I timeout
 equal to zero makes
-.BR epoll_wait (2)
+.BR epoll_wait ()
 to return immediately even if no events are available
 (return code equal to zero).
 The
@@ -127,13 +127,13 @@ executing the following calls:
 .fi
 .SH "RETURN VALUE"
 When successful,
-.BR epoll_wait (2)
+.BR epoll_wait ()
 returns the number of file descriptors ready for the requested I/O, or zero
 if no file descriptor became ready during the requested
 .I timeout
 milliseconds.
 When an error occurs,
-.BR epoll_wait (2)
+.BR epoll_wait ()
 returns \-1 and
 .I errno
 is set appropriately.
@@ -169,7 +169,7 @@ Glibc support for
 .BR epoll_pwait ()
 is provided starting with version 2.6.
 .SH CONFORMING TO
-.BR epoll_wait (2)
+.BR epoll_wait ()
 is Linux specific, and was introduced in kernel 2.5.44.
 .\" The interface should be finalized by Linux kernel 2.5.66.
 .SH "SEE ALSO"

man2/execve.2

@@ -209,7 +209,7 @@ Any outstanding asynchronous I/O operations are canceled
 .BR aio_write (3)).
 .IP * 4
 For the handling of capabilities during
-.BR execve (2),
+.BR execve (),
 see
 .BR capabilities (7).
 .IP * 4
@@ -480,7 +480,7 @@ on most other Unix systems doing this will result in an error.
 .\" interpreters.  This is a security hole, because it allows users to
 .\" open any file, such as a rewinding tape device, for reading.  Some
 .\" Linux versions have also had other security holes in
-.\" .BR execve (2)
+.\" .BR execve ()
 .\" that could be exploited for denial of service by a suitably crafted
 .\" ELF binary. There are no known problems with 2.0.34 or 2.2.15.
 .SS Historical

man2/fcntl.2

@@ -113,7 +113,7 @@ initialized by
 .\" or
 .\" .BR creat (2),
 and possibly modified by
-.BR fcntl (2).
+.BR fcntl ().
 Duplicated file descriptors
 (made with
 .BR dup (2),
@@ -304,7 +304,7 @@ terminates or if it closes
 file descriptor referring to a file on which locks are held.
 .\" (Additional file descriptors referring to the same file
 .\" may have been obtained by calls to
-.\" .BR open "(2), " dup "(2), " dup2 "(2), or " fcntl (2).)
+.\" .BR open "(2), " dup "(2), " dup2 "(2), or " fcntl ().)
 This is bad: it means that a process can lose the locks on
 a file like
 .I /etc/passwd
@@ -958,7 +958,7 @@ Since kernel 2.0, there is no interaction between the types of lock
 placed by
 .BR flock (2)
 and
-.BR fcntl (2).
+.BR fcntl ().
 
 POSIX.1-2001 allows
 .I l_len

man2/flock.2

@@ -134,15 +134,15 @@ The file is locked and the
 flag was selected.
 .SH "CONFORMING TO"
 4.4BSD (the
-.BR flock (2)
+.BR flock ()
 call first appeared in 4.2BSD).
 A version of
-.BR flock (2),
+.BR flock (),
 possibly implemented in terms of
 .BR fcntl (2),
 appears on most Unix systems.
 .SH NOTES
-.BR flock (2)
+.BR flock ()
 does not lock files over NFS.
 Use
 .BR fcntl (2)
@@ -150,27 +150,27 @@ instead: that does work over NFS, given a sufficiently recent version of
 Linux and a server which supports locking.
 .PP
 Since kernel 2.0,
-.BR flock (2)
+.BR flock ()
 is implemented as a system call in its own right rather
 than being emulated in the GNU C library as a call to
 .BR fcntl (2).
 This yields true BSD semantics:
 there is no interaction between the types of lock
 placed by
-.BR flock (2)
+.BR flock ()
 and
 .BR fcntl (2),
 and
-.BR flock (2)
+.BR flock ()
 does not detect deadlock.
 .PP
-.BR flock (2)
+.BR flock ()
 places advisory locks only; given suitable permissions on a file,
 a process is free to ignore the use of
-.BR flock (2)
+.BR flock ()
 and perform I/O on the file.
 .PP
-.BR flock (2)
+.BR flock ()
 and
 .BR fcntl (2)
 locks have different semantics with respect to forked processes and

man2/fork.2

@@ -109,7 +109,7 @@ Memory mappings that have been marked with the
 .BR madvise (2)
 .B MADV_DONTFORK
 flag are not inherited across a
-.BR fork (2).
+.BR fork ().
 .IP * 4
 The termination signal of the child is always
 .B SIGCHLD
@@ -120,7 +120,7 @@ Note the following further points:
 .IP * 4
 The child process is created with a single thread \(em the
 one that called
-.BR fork (2).
+.BR fork ().
 The entire virtual address space of the parent is replicated in the child,
 including the states of mutexes, condition variables,
 and other pthreads objects; the use of

man2/gethostid.2

@@ -65,7 +65,7 @@ argument is stored in the file
 .SH "RETURN VALUE"
 .BR gethostid ()
 returns the 32-bit identifier for the current host as set by
-.BR sethostid (2).
+.BR sethostid ().
 .SH FILES
 .I /etc/hostid
 .SH "CONFORMING TO"

man2/ioctl.2

@@ -115,7 +115,7 @@ references.
 .SH CONFORMING TO
 No single standard.
 Arguments, returns, and semantics of
-.BR ioctl (2)
+.BR ioctl ()
 vary according to the device driver in question (the call is used as a
 catch-all for operations that don't cleanly fit the Unix stream I/O
 model).

man2/link.2

@@ -122,7 +122,7 @@ The file is on a read-only filesystem.
 .IR oldpath " and " newpath
 are not on the same mounted filesystem.
 (Linux permits a filesystem to be mounted at multiple points, but
-.BR link (2)
+.BR link ()
 does not work across different mount points,
 even if the same filesystem is mounted on both.)
 .SH "CONFORMING TO"

man2/linkat.2

@@ -79,7 +79,7 @@ to the directory referred to by the file descriptor
 .IR newdirfd .
 
 By default,
-.BR linkat (2),
+.BR linkat (),
 does not dereference
 .I oldpath
 if it is a symbolic link (like

man2/mbind.2

@@ -208,7 +208,7 @@ arguments specify the empty set, then the memory is allocated on
 the node of the CPU that triggered the allocation.
 This is the only way to specify "local allocation" for a
 range of memory via
-.IR mbind (2).
+.IR mbind ().
 
 If
 .B MPOL_MF_STRICT
@@ -350,7 +350,7 @@ is ignored on huge page mappings.
 The
 .BR MPOL_DEFAULT ,
 mode has different effects for
-.BR mbind (2)
+.BR mbind ()
 and
 .BR set_mempolicy (2).
 When

man2/mmap.2

@@ -119,7 +119,7 @@ and are carried through to the underlying file.
 The file may not actually be updated until
 .BR msync (2)
 or
-.BR munmap (2)
+.BR munmap ()
 is called.
 .TP
 .B MAP_PRIVATE

man2/rename.2

@@ -215,7 +215,7 @@ The file is on a read-only filesystem.
 .IR oldpath " and " newpath
 are not on the same mounted filesystem.
 (Linux permits a filesystem to be mounted at multiple points, but
-.BR rename (2)
+.BR rename ()
 does not work across different mount points,
 even if the same filesystem is mounted on both.)
 .SH "CONFORMING TO"

man2/select.2

@@ -468,7 +468,7 @@ if the call is interrupted by a signal handler (i.e., the
 error return).
 This is not permitted by POSIX.1-2001.
 The Linux
-.BR pselect (2)
+.BR pselect ()
 system call has the same behavior,
 but the glibc wrapper hides this behavior by internally copying the
 .I timeout

man2/splice.2

@@ -154,13 +154,13 @@ or
 was not NULL, but the corresponding file descriptor refers to a pipe.
 .SH VERSIONS
 The
-.BR splice (2)
+.BR splice ()
 system call first appeared in Linux 2.6.17.
 .SH "CONFORMING TO"
 This system call is Linux specific.
 .SH NOTES
 The three system calls
-.BR splice (2),
+.BR splice (),
 .BR vmsplice (2),
 and
 .BR tee (2),
@@ -214,6 +214,6 @@ See
 .BR tee (2).
 .SH SEE ALSO
 .BR sendfile (2),
-.BR splice (2),
 .BR tee (2),
+.BR vmsplice (2),
 .BR feature_test_macros (7)

man2/spu_create.2

@@ -90,7 +90,7 @@ A new directory will be created at the location specified by the
 argument.
 This gang may be used to hold other SPU contexts, by providing
 a pathname that is within the gang directory to further calls to
-.BR spu_create (2).
+.BR spu_create ().
 .TP
 .B SPU_CREATE_NOSCHED
 Create a context that is not affected by the SPU scheduler.
@@ -147,7 +147,7 @@ for a full list of the possible
 values.
 .SH RETURN VALUE
 On success,
-.BR spu_create (2)
+.BR spu_create ()
 returns a new file descriptor.
 On error, \-1 is returned, and
 .I errno
@@ -228,7 +228,7 @@ By convention, it gets mounted in
 .IR /spu .
 .SH VERSIONS
 The
-.BR spu_create (2)
+.BR spu_create ()
 system call was added to Linux in kernel 2.6.16.
 .SH CONFORMING TO
 This call is Linux specific and only implemented on the PowerPC

man2/spu_run.2

@@ -182,7 +182,7 @@ either the hardware does not provide SPUs or the spufs module is not
 loaded.
 .SH VERSIONS
 The
-.BR spu_run (2)
+.BR spu_run ()
 system call was added to Linux in kernel 2.6.16.
 .SH CONFORMING TO
 This call is Linux specific and only implemented by the PowerPC

man2/stat.2

@@ -446,9 +446,9 @@ wrapper function hides these details from applications,
 invoking the most recent version of the system call provided by the kernel,
 and repacking the returned information if required for old binaries.
 Similar remarks apply for
-.BR fstat (2)
+.BR fstat ()
 and
-.BR lstat (2).
+.BR lstat ().
 .\"
 .\" A note from Andries Brouwer, July 2007
 .\"
@@ -479,7 +479,7 @@ and
 .\" (Note that the details depend on gcc being used as c compiler.)
 .SH EXAMPLE
 The following program calls
-.BR stat (2)
+.BR stat ()
 and displays selected fields in the returned
 .I stat
 structure.

man2/sysctl.2

@@ -101,7 +101,7 @@ Only Linux has the
 .I /proc/sys
 mirror, and the object naming schemes differ between Linux and 4.4BSD,
 but the declaration of the
-.BR sysctl (2)
+.BR sysctl ()
 function is the same in both.
 .SH NOTES
 Glibc does not provide a wrapper for this system call; call it using

man2/tee.2

@@ -112,7 +112,7 @@ refer to the same pipe.
 Out of memory.
 .SH VERSIONS
 The
-.BR tee (2)
+.BR tee ()
 system call first appeared in Linux 2.6.17.
 .SH "CONFORMING TO"
 This system call is Linux specific.
@@ -129,7 +129,7 @@ a reference to the input.
 The following example implements a basic
 .BR tee (1)
 program using the
-.BR tee (2)
+.BR tee ()
 system call.
 .nf
 

man2/vmsplice.2

@@ -136,7 +136,7 @@ set.
 Out of memory.
 .SH VERSIONS
 The
-.BR vmsplice (2)
+.BR vmsplice ()
 system call first appeared in Linux 2.6.17.
 .SH "CONFORMING TO"
 This system call is Linux specific.

man2/wait.2

@@ -507,7 +507,7 @@ This was the default before Linux 2.4.
 The following program demonstrates the use of
 .BR fork (2)
 and
-.BR waitpid (2).
+.BR waitpid ().
 The program creates a child process.
 If no command-line argument is supplied to the program,
 then the child suspends its execution using
@@ -517,7 +517,7 @@ Otherwise, if a command-line argument is supplied,
 then the child exits immediately,
 using the integer supplied on the command line as the exit status.
 The parent process executes a loop that monitors the child using
-.BR waitpid (2),
+.BR waitpid (),
 and uses the W*() macros described above to analyze the wait status value.
 
 The following shell session demonstrates the use of the program:

man3/atoi.3

@@ -91,7 +91,7 @@ POSIX.1-1996 include the functions
 and
 .BR atol ()
 only.
-.BR atoq (3)
+.BR atoq ()
 is a GNU extension.
 .SH NOTES
 The non-standard

man3/crypt.3

@@ -87,11 +87,11 @@ program that checks for crackable passwords during the selection process is
 recommended.
 .PP
 The DES algorithm itself has a few quirks which make the use of the
-.BR crypt (3)
+.BR crypt ()
 interface a very poor choice for anything other than password
 authentication.
 If you are planning on using the
-.BR crypt (3)
+.BR crypt ()
 interface for a cryptography project, don't do it: get a good book on
 encryption and one of the widely available DES libraries.
 .SH "RETURN VALUE"
@@ -123,9 +123,9 @@ function was not implemented, probably because of U.S.A. export restrictions.
 .\" Heavily redundant data causes trouble with DES encryption, when used in the
 .\" .I codebook
 .\" mode that
-.\" .BR crypt (3)
+.\" .BR crypt ()
 .\" implements.  The
-.\" .BR crypt (3)
+.\" .BR crypt ()
 .\" interface should be used only for its intended purpose of password
 .\" verification, and should not be used as part of a data encryption tool.
 .\" .PP

man3/getaddrinfo.3

@@ -46,7 +46,7 @@ getaddrinfo, freeaddrinfo, gai_strerror \- network address and service translati
 .fi
 .SH DESCRIPTION
 The
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 function combines the functionality provided by the
 .\" .BR getipnodebyname (3),
 .\" .BR getipnodebyaddr (3),
@@ -55,7 +55,7 @@ and
 .BR getservbyport (3)
 functions into a single interface.
 The thread-safe
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 function creates one or more socket address structures
 that can be used by the
 .BR bind (2)
@@ -64,7 +64,7 @@ and
 system calls to create a client or a server socket.
 .PP
 The
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 function is not limited to creating IPv4 socket address structures;
 IPv6 socket address structures can be created if IPv6 support is available.
 These socket address structures can be used directly by
@@ -90,7 +90,7 @@ struct addrinfo {
 };
 .fi
 .PP
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 sets
 .I res
 to point to a dynamically allocated linked list of
@@ -118,7 +118,7 @@ have the same meaning as the corresponding parameters in the
 .BR socket (2)
 system call.
 The
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 function returns socket addresses in either IPv4 or IPv6
 address family,
 .RI "(" "ai_family"
@@ -182,7 +182,7 @@ The
 flag suppresses any potentially lengthy network host address lookups.
 .PP
 The
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 function creates a linked list of
 .I addrinfo
 structures, one for each network address subject to any restrictions
@@ -288,7 +288,7 @@ This flag is used to inhibit the invocation of a name resolution service
 in cases where it is known not to be required.
 .PP
 The
-.BR freeaddrinfo (3)
+.BR freeaddrinfo ()
 function frees the memory that was allocated
 for the dynamically allocated linked list
 .IR res .
@@ -363,7 +363,7 @@ flags respectively to be used in the IDNA handling.
 .\" #  define EAI_INTR        -104  /* Interrupted by a signal.  */
 .\" #  define EAI_IDN_ENCODE  -105  /* IDN encoding failed.  */
 .\" # endif
-.BR getaddrinfo (3)
+.BR getaddrinfo ()
 returns 0 if it succeeds, or one of the following non-zero error codes:
 .TP
 .B EAI_ADDRFAMILY
@@ -421,7 +421,7 @@ Other system error, check
 for details.
 .PP
 The
-.BR gai_strerror (3)
+.BR gai_strerror ()
 function translates these error codes to a human readable string,
 suitable for error reporting.
 .SH "CONFORMING TO"

man3/getipnodebyname.3

@@ -50,9 +50,9 @@ and
 instead.
 .LP
 The
-.BR getipnodebyname (3)
+.BR getipnodebyname ()
 and
-.BR getipnodebyaddr (3)
+.BR getipnodebyaddr ()
 functions return the names and addresses of a network host.
 These functions return a pointer to the
 following structure:
@@ -73,9 +73,9 @@ and
 .BR gethostbyaddr (3)
 functions, which could only access the IPv4 network address family.
 The
-.BR getipnodebyname (3)
+.BR getipnodebyname ()
 and
-.BR getipnodebyaddr (3)
+.BR getipnodebyaddr ()
 functions can access multiple network address families.
 .PP
 Unlike the
@@ -83,14 +83,14 @@ Unlike the
 functions,
 these functions return pointers to dynamically allocated memory.
 The
-.BR freehostent (3)
+.BR freehostent ()
 function is used to release the dynamically allocated memory
 after the caller no longer needs the
 .I hostent
 structure.
 .SS getipnodebyname parameters
 The
-.BR getipnodebyname (3)
+.BR getipnodebyname ()
 function
 looks up network addresses for the host
 specified by the
@@ -151,7 +151,7 @@ This flag is equivalent to
 .BR "(AI_ADDRCONFIG | AI_V4MAPPED)" .
 .SS getipnodebyaddr parameters
 The
-.BR getipnodebyaddr (3)
+.BR getipnodebyaddr ()
 function
 looks up the name of the host whose
 network address is
@@ -217,9 +217,9 @@ The array is terminated by a null pointer.
 This is a copy of the
 .I af
 parameter to
-.BR getipnodebyname (3)
+.BR getipnodebyname ()
 or
-.BR getipnodebyaddr (3).
+.BR getipnodebyaddr ().
 .I h_addrtype
 will always be
 .B AF_INET

man3/getnameinfo.3

@@ -18,7 +18,7 @@ getnameinfo \- address-to-name translation in protocol-independent manner
 .fi
 .SH DESCRIPTION
 The
-.BR getnameinfo (3)
+.BR getnameinfo ()
 function is defined for protocol-independent address-to-nodename translation.
 It combines the functionality of
 .BR gethostbyaddr (3)
@@ -62,7 +62,7 @@ must be requested.
 The
 .I flags
 argument modifies the behavior of
-.BR getnameinfo (3)
+.BR getnameinfo ()
 as follows:
 .TP
 .B NI_NOFQDN

man3/inet_ntop.3

@@ -43,13 +43,13 @@ which is
 .I cnt
 bytes long.
 .PP
-.BR inet_ntop (3)
+.BR inet_ntop ()
 extends the
 .BR inet_ntoa (3)
 function to support multiple address families,
 .BR inet_ntoa (3)
 is now considered to be deprecated in favor of
-.BR inet_ntop (3).
+.BR inet_ntop ().
 The following address families are currently supported:
 .TP
 .B AF_INET

man3/inet_pton.3

@@ -41,13 +41,13 @@ copies
 the network address structure to
 .IR dst .
 .PP
-.BR inet_pton (3)
+.BR inet_pton ()
 extends the
 .BR inet_addr (3)
 function to support multiple address families,
 .BR inet_addr (3)
 is now considered to be deprecated in favor of
-.BR inet_pton (3).
+.BR inet_pton ().
 The following address families are currently supported:
 .TP
 .B AF_INET

man3/strstr.3

@@ -53,7 +53,7 @@ The terminating '\\0' characters are not compared.
 The
 .BR strcasestr ()
 function is like
-.BR strstr (3),
+.BR strstr (),
 but ignores the case of both arguments.
 .SH "RETURN VALUE"
 These functions return a pointer to the beginning of the

man3/tempnam.3

@@ -95,10 +95,10 @@ Allocation of storage failed.
 SVr4, 4.3BSD, POSIX.1-2001
 .SH NOTES
 Although
-.BR tempnam (3)
+.BR tempnam ()
 generates names that are difficult to guess,
 it is nevertheless possible that between the time that
-.BR tempnam (3)
+.BR tempnam ()
 returns a pathname, and the time that the program opens it,
 another program might create that pathname using
 .BR open (2),

man3/tmpnam.3

@@ -87,10 +87,10 @@ times,
 the behavior is implementation defined.
 .LP
 Although
-.BR tmpnam (3)
+.BR tmpnam ()
 generates names that are difficult to guess,
 it is nevertheless possible that between the time that
-.BR tmpnam (3)
+.BR tmpnam ()
 returns a pathname, and the time that the program opens it,
 another program might create that pathname using
 .BR open (2),