Replace `manual(section)' references with proper .Xr statements.

5 files changed, 25 insertions, 13 deletions

diff --git a/share/man/man4/man4.i386/cx.4 b/share/man/man4/man4.i386/cx.4
index 2853485..335f556 100644
--- a/share/man/man4/man4.i386/cx.4
+++ b/share/man/man4/man4.i386/cx.4
@@ -99,7 +99,9 @@ Start sending BREAK.
 Stop sending BREAK.
 .It Dv TIOCSDTR
 Set DTR signal (DTR := 1).  The DTR signal is always set
-on the first open(2) and could be changed by
+on the first
+.Xr open 2
+and could be changed by
 .Dv TIOCCDTR ,
 .Dv TIOCSDTR , 
 .Dv TIOCMSET , 
diff --git a/share/man/man4/man4.i386/gsc.4 b/share/man/man4/man4.i386/gsc.4
index 8c097b5..feae82e 100644
--- a/share/man/man4/man4.i386/gsc.4
+++ b/share/man/man4/man4.i386/gsc.4
@@ -128,7 +128,9 @@ do not know of tools which produce a graymap from a halftone bitmap.
 The ioctl requests that are served by
 .Nm gsc
 are listed below.
-There is a utility, called sgsc(1), that provides access to these
+There is a utility, called
+.Xr sgsc 1 ,
+that provides access to these
 requests from within shell.
 .Bl -tag -width Ds
 .It GSC_SRES int
@@ -235,7 +237,8 @@ Note that
 the timeout timer starts anew for each buffer to be read and thus does
 not cause you to scan faster for longer images.
 BLEN/BTIME is similar
-as MIN/TIME in termios(4).
+as MIN/TIME in
+.Xr termios 4 .
 .It GSC_GBTIME int
 Get the current buffer timeout.
 .El
@@ -329,5 +332,7 @@ Even though the scanner device has a little switch by which you should
 be able to select one of the four resolution modes, I could not yet
 determine how to read its status.
 Unless this is not fixed the driver
-depends on the value passed by means of ioctl(2) which need not match
+depends on the value passed by means of
+.Xr ioctl 2
+which need not match
 what is selected by the hardware.
diff --git a/share/man/man4/man4.i386/meteor.4 b/share/man/man4/man4.i386/meteor.4
index 63f23ec..732264a 100644
--- a/share/man/man4/man4.i386/meteor.4
+++ b/share/man/man4/man4.i386/meteor.4
@@ -87,7 +87,9 @@ The patch supplied with the driver will make the major number 67.
 .Sh Meteor Capture Modes
 The Meteor capture driver has three modes of capture operation.
 .Pp
-1) Conventional read(2) interface.
+1) Conventional
+.Xr read 2
+interface.
 .in +0.5i
 .Pp
 This mode is the easiest and slowest to use.
diff --git a/share/man/man4/man4.i386/wl.4 b/share/man/man4/man4.i386/wl.4
index 9ec25e9..405dfe3 100644
--- a/share/man/man4/man4.i386/wl.4
+++ b/share/man/man4/man4.i386/wl.4
@@ -70,7 +70,7 @@ Point to point antennae can be purchased that will go miles.
 The card can either be initialized with the vendor supplied DOS setup software.
 Typically minimally an IRQ, port, and Network ID must be supplied.
 Michael Smith's 
-.Nm wlconfig(8) 
+.Xr wlconfig 8
 utility can now be used to do this work from
 the UNIX side.  The card is "not" plug and play.
 The network id controls whether one set of cards can hear another.
@@ -80,7 +80,7 @@ by the radio modem.
 In addition to the config utility, there are several sysctl
 switches that can be used to modify runtime parameters.
 The 
-.Nm sysctl(8) 
+.Xr sysctl 8
 variables are as follows:
 .Bl -diag
 .It "machdep.wl_xmit_delay <useconds>"
@@ -101,7 +101,7 @@ This switch is not currently useful.
 .Pp
 There is also a signal strength cache in the driver.  It may be interrogated
 with
-.Nm wlconfig(8) .
+.Xr wlconfig 8 .
 Incoming packets
 are checked for certain hardware radio-modem values including signal
 strength, silence, and quality, which range fro 0..63, 0..63, and 0..15
@@ -123,8 +123,9 @@ as are any other network protocol barring IPv4 packets.
 The 82586 has numerous defects.  It may experience transmit-side
 errors when modern faster cpus send packets at it faster than it can handle.
 The driver (and probably the chip) does not support an all multicast mode.
-As a result, it can be used with applications like mrouted(8), but
-it must go into promiscuous mode for that to work.  The driver
+As a result, it can be used with applications like
+.Xr mrouted 8 ,
+but it must go into promiscuous mode for that to work.  The driver
 is slow to change modes from "normal" to promiscuous mode, presumably
 due to delays in the configuration code.
 .Sh SEE ALSO
diff --git a/share/man/man4/vinum.4 b/share/man/man4/vinum.4
index de3dfb3..c781e37 100644
--- a/share/man/man4/vinum.4
+++ b/share/man/man4/vinum.4
@@ -186,7 +186,9 @@ in the kernel configuration file or remove the -DVINUMDEBUG option from
 .Pa /usr/src/sbin/vinum/Makefile
 as described above.
 .Pp
-If the VINUMDEBUG variables do not match, vinum(8) will fail with a message
+If the VINUMDEBUG variables do not match,
+.Xr vinum 8
+will fail with a message
 explaining the problem and what to do to correct it.
 .Pp
 .Nm
@@ -330,7 +332,7 @@ from which they are derived.
 .Bl -bullet 
 .It
 When
-.Nm vinum(8)
+.Xr vinum 8
 creates or deletes objects, it creates a directory
 .Pa /dev/vinum ,
 in which it makes device entries for each volume it finds.  It also creates 
@@ -917,7 +919,7 @@ specification).
 The following example shows a remote debugging session using the
 .Ar debug
 command of
-.Nm vinum(8):
+.Xr vinum 8 :
 .if t .ps -3
 .if t .vs -3
 .Bd -literal