summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Pechkin <mpech@cvs.openbsd.org>2001-12-13 20:16:49 +0000
committerMike Pechkin <mpech@cvs.openbsd.org>2001-12-13 20:16:49 +0000
commita37e294bfb52a06afd6eb6645870cf1c540b877e (patch)
tree36ba9d9b5ffc6d45680f435ed5a7932be0645989
parent341511d89cf2709a82733b614acd805624150322 (diff)
o) start new sentence on a new line;
o) wrap long lines; o) fix bogus .Xr usage; o) we don't like blank lines; o) always close .Bl tags; o) OpenBSD -> .Ox; o) don't like .Pp before .Ss; millert@ ok;
-rw-r--r--sbin/ancontrol/ancontrol.85
-rw-r--r--sbin/atactl/atactl.8101
-rw-r--r--sbin/badsect/badsect.88
-rw-r--r--sbin/brconfig/brconfig.821
-rw-r--r--sbin/disklabel/disklabel.522
-rw-r--r--sbin/disklabel/disklabel.85
-rw-r--r--sbin/dump/dump.84
-rw-r--r--sbin/ifconfig/ifconfig.821
-rw-r--r--sbin/init/init.836
-rw-r--r--sbin/iopctl/iopctl.86
-rw-r--r--sbin/ipsecadm/ipsecadm.830
-rw-r--r--sbin/isakmpd/apps/keyconv/keyconv.85
-rw-r--r--sbin/isakmpd/isakmpd.886
-rw-r--r--sbin/isakmpd/isakmpd.conf.567
-rw-r--r--sbin/isakmpd/isakmpd.policy.59
-rw-r--r--sbin/lmccontrol/lmccontrol.85
-rw-r--r--sbin/mount_tcfs/mount_tcfs.86
-rw-r--r--sbin/pdisk/pdisk.84
-rw-r--r--sbin/pfctl/pfctl.83
-rw-r--r--sbin/pflogd/pflogd.86
-rw-r--r--sbin/shutdown/shutdown.87
-rw-r--r--sbin/sysctl/sysctl.86
-rw-r--r--sbin/wicontrol/wicontrol.88
23 files changed, 265 insertions, 206 deletions
diff --git a/sbin/ancontrol/ancontrol.8 b/sbin/ancontrol/ancontrol.8
index 8b8c25b65a3..2d8c0541a45 100644
--- a/sbin/ancontrol/ancontrol.8
+++ b/sbin/ancontrol/ancontrol.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ancontrol.8,v 1.13 2001/08/23 14:17:08 aaron Exp $
+.\" $OpenBSD: ancontrol.8,v 1.14 2001/12/13 20:16:47 mpech Exp $
.\"
.\" Copyright (c) 1997, 1998, 1999
.\" Bill Paul <wpaul@ee.columbia.edu> All rights reserved.
@@ -237,7 +237,8 @@ sets the transmit diversity.
.It Fl e Ar "0|1|2|3"
Set the transmit WEP key to use.
Note that until this command is issued, the device will use the
-last key programmed. The transmit key is stored in NVRAM.
+last key programmed.
+The transmit key is stored in NVRAM.
Currently set transmit key can be checked via
.Fl C
option.
diff --git a/sbin/atactl/atactl.8 b/sbin/atactl/atactl.8
index 917d0d971c4..c12e3fef600 100644
--- a/sbin/atactl/atactl.8
+++ b/sbin/atactl/atactl.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: atactl.8,v 1.9 2001/09/03 21:24:07 deraadt Exp $
+.\" $OpenBSD: atactl.8,v 1.10 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: atactl.8,v 1.5 1999/02/24 18:49:14 jwise Exp $
.\"
.\" Copyright (c) 1998 The NetBSD Foundation, Inc.
@@ -120,18 +120,22 @@ management mode.
.Ar power-management-level
.Pp
Enables and sets the advanced power management level to the requested
-level on the specified device (if supported). Device performance may
+level on the specified device (if supported).
+Device performance may
increase with increasing power management levels at the cost of
-potentially requiring more power. Values up to and including 126 allow
-the device to go into standby mode and spin-down the disk. This
+potentially requiring more power.
+Values up to and including 126 allow
+the device to go into standby mode and spin-down the disk.
+This
.Em may cause disk time-outs
and is therefore
.Em not
-recommended. These values are more suitable optimization for low power
-usage on infrequently used devices. Values 127 up to and including 253
-do not allow the device to go to standby mode and are more suitable for
-optimization for performance. Support for advanced power management is
-indicated by the device with
+recommended.
+These values are more suitable optimization for low power
+usage on infrequently used devices.
+Values 127 up to and including 253 do not allow the device to go to
+standby mode and are more suitable for optimization for performance.
+Support for advanced power management is indicated by the device with
.Sq Advanced Power Management feature set
in the output of the
.Cm identify
@@ -149,11 +153,12 @@ warning.
.Ar acoustic-management-level
.Pp
Enables and sets the automatic acoustic management level to the requested
-level on the specified device (if supported). Device performance may
+level on the specified device (if supported).
+Device performance may
increase with increasing automatic acoustic management levels at the cost of
-potentially generating more noise and requiring more power. Valid values are
-0 up to and including 126. Support for automatic acoustic management is
-indicated by the device with
+potentially generating more noise and requiring more power.
+Valid values are 0 up to and including 126.
+Support for automatic acoustic management is indicated by the device with
.Sq Automatic Acoustic Management feature set
in the output of the
.Cm identify
@@ -180,13 +185,13 @@ after a reset.
.Cm puisenable
.Pp
Enables power-up in standby (puis) on the specified device, causing the
-device to wait with spinning up the disks after power-up. This may cause
-problems at boot if the device is to slow in spin-up. This option is
-therefore
+device to wait with spinning up the disks after power-up.
+This may cause problems at boot if the device is to slow in spin-up.
+This option is therefore
.Em not recommended
-unless the implications are understood. Note that the power-up in
-standby mode stays enabled over power-downs, hardware and software
-resets.
+unless the implications are understood.
+Note that the power-up in standby mode stays enabled over power-downs,
+hardware and software resets.
Support for power-up in standby is indicated by the device with
.Sq Power-up in standby feature set
in the output of the
@@ -196,7 +201,8 @@ command.
.Cm puisdisable
.Pp
Disables power-up in standby (puis) on the specified device, causing the
-device to spin up the disks after power-up. This should be the factory
+device to spin up the disks after power-up.
+This should be the factory
default setting of the device and it is recommended to leave this
setting disabled.
.Pp
@@ -207,8 +213,9 @@ power-up in standby was enabled).
.Pp
.Cm readaheadenable
.Pp
-Enables read look-ahead on the specified device. This may increase
-performance. Support for and status of read look-ahead is indicated by
+Enables read look-ahead on the specified device.
+This may increase performance.
+Support for and status of read look-ahead is indicated by
the device with
.Sq read look-ahead
in the output of the
@@ -217,8 +224,9 @@ command.
.Pp
.Cm readaheaddisable
.Pp
-Disables read look-ahead on the specified device. This may decrease
-performance. Note that the device may use
+Disables read look-ahead on the specified device.
+This may decrease performance.
+Note that the device may use
.Sq vendor specific
behaviour in implementing this, so it is
.Em not
@@ -228,9 +236,10 @@ mounted filesystems.
.Cm smartenable
.Pp
Enables SMART (Self-Monitoring, Analysis, and Reporting Technology) on the
-specified device (if supported). This causes the device to record information
-for prediction of device degradation and/or faults. Support for SMART is
-indicated by the device with
+specified device (if supported).
+This causes the device to record information
+for prediction of device degradation and/or faults.
+Support for SMART is indicated by the device with
.Sq SMART feature set
in the output of the
.Cm identify
@@ -238,24 +247,27 @@ command.
.Pp
.Cm smartdisable
.Pp
-Disables support for SMART on the specified device. Note that this means that
-the device will no longer record any SMART information.
+Disables support for SMART on the specified device.
+Note that this means that the device will no longer record any SMART
+information.
.Pp
.Cm smartstatus
.Pp
-Reads the reliability status of the specified device. If the device reports
+Reads the reliability status of the specified device.
+If the device reports
that one of its thresholds is exceeded (a strong indication of imminent
failure), the warning
.Sq SMART threshold exceeded!
-is printed to stderr and a status of 2 is returned. Note that SMART
+is printed to stderr and a status of 2 is returned.
+Note that SMART
.Em must
be enabled or the device will return an error.
.Pp
.Cm writecachedisable
.Pp
-Disable the write cache on the specified device (if supported). This may
-decrease performance. Support for and status of write caching is
-indicated by the device with
+Disable the write cache on the specified device (if supported).
+This may decrease performance.
+Support for and status of write caching is indicated by the device with
.Sq write cache
in the output of the
.Cm identify
@@ -263,8 +275,8 @@ command.
.Pp
.Cm writecacheenable
.Pp
-Enables the write cache on the specified device (if supported). This may
-increase performance, however data still in the device's cache at
+Enables the write cache on the specified device (if supported).
+This may increase performance, however data still in the device's cache at
powerdown
.Em may be lost.
The
@@ -289,8 +301,8 @@ In a
.Xr crontab 5
entry queries
.Pa /dev/wd0
-each hour for early warning signs of failure. If the device exceeded one
-of the SMART thresholds,
+each hour for early warning signs of failure.
+If the device exceeded one of the SMART thresholds,
.Nm
will output
.Sq SMART threshold exceeded!
@@ -298,15 +310,16 @@ to stderr and
.Xr cron 8
will mail it.
.Sh DIAGNOSTICS
-Not all devices are created equally. Some may not support the feature sets
+Not all devices are created equally.
+Some may not support the feature sets
and/or commands needed to perform the requested action, even when the
.Cm identify
-command indicates support for the requested action. The device will
-typically respond with an
+command indicates support for the requested action.
+The device will typically respond with an
.Sq ATA device returned Aborted Command
-if the requested action is not supported. Similarly a device might
-not implement all commands in a feature set, so even though disabling a
-feature works, enabling might not.
+if the requested action is not supported.
+Similarly a device might not implement all commands in a feature set,
+so even though disabling a feature works, enabling might not.
.Sh SEE ALSO
.Xr ioctl 2 ,
.Xr wd 4
diff --git a/sbin/badsect/badsect.8 b/sbin/badsect/badsect.8
index 0c1cfea582b..099c3e32655 100644
--- a/sbin/badsect/badsect.8
+++ b/sbin/badsect/badsect.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: badsect.8,v 1.10 2000/03/18 22:55:54 aaron Exp $
+.\" $OpenBSD: badsect.8,v 1.11 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: badsect.8,v 1.8 1995/03/18 14:54:27 cgd Exp $
.\"
.\" Copyright (c) 1985, 1991, 1993
@@ -94,7 +94,7 @@ on the file system.
The bad sectors should show up in two files
or in the bad sector files and the free list.
Have
-.Xr fsck
+.Em fsck
remove files containing the offending bad sectors, but
.Em do not
have it remove the
@@ -111,11 +111,11 @@ system call,
creating an illegal file whose first block address is the block containing
bad sector and whose name is the bad sector number.
When it is discovered by
-.Xr fsck
+.Em fsck
it will ask
.Dq Li "HOLD BAD BLOCK ?"
A positive response will cause
-.Xr fsck
+.Em fsck
to convert the inode to a regular file containing the bad block.
.Sh DIAGNOSTICS
.Nm
diff --git a/sbin/brconfig/brconfig.8 b/sbin/brconfig/brconfig.8
index c65940e0272..f4ab279b875 100644
--- a/sbin/brconfig/brconfig.8
+++ b/sbin/brconfig/brconfig.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: brconfig.8,v 1.29 2001/12/05 19:55:34 jason Exp $
+.\" $OpenBSD: brconfig.8,v 1.30 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 1999, 2000 Jason L. Wright (jason@thought.net)
.\" All rights reserved.
@@ -259,21 +259,25 @@ All other traffic trying to go into and be sent from fxp0 will be blocked.
The bridge can also be used to tunnel ethernet frames over IPv4 or
IPv6 by using the
.Xr gif 4
-interface. In addition to adding Ethernet interfaces,
+interface.
+In addition to adding Ethernet interfaces,
one or more
.Xr gif 4 ,
-interfaces are added as members of the bridge. Ethernet frames sent
+interfaces are added as members of the bridge.
+Ethernet frames sent
through the
.Xr gif 4
interfaces are encapsulated inside
.Xr ip 4
datagrams and sent across the network to another bridge, which
decapsulates the datagram and then processes the resulting Ethernet
-frame as if it had originated on a normal Ethernet interface. This
-effectively allows a layer-2 network to be extended from one point to
-another, possibly through the Internet. This mechanism may be used in
+frame as if it had originated on a normal Ethernet interface.
+This effectively allows a layer-2 network to be extended from one point to
+another, possibly through the Internet.
+This mechanism may be used in
conjunction with IPsec, by specifying the appropriate IPsec flows
-between the two bridges. To only protect the bridge traffic between
+between the two bridges.
+To only protect the bridge traffic between
the two bridges, the transport protocol 97 (etherip) selector may be
used in
.Xr ipsecadm 8
@@ -348,7 +352,8 @@ and
files, using the ! operator.
.Sh SPANNING TREE
The bridge has support for 802.1D Spanning Tree Protocol (STP), which can
-be used to detect and remove loops in a network topology. Using the
+be used to detect and remove loops in a network topology.
+Using the
.Cm stp
or
.Cm -stp
diff --git a/sbin/disklabel/disklabel.5 b/sbin/disklabel/disklabel.5
index 6848f06c1fc..8ef9a34da42 100644
--- a/sbin/disklabel/disklabel.5
+++ b/sbin/disklabel/disklabel.5
@@ -1,4 +1,4 @@
-.\" $OpenBSD: disklabel.5,v 1.11 2001/08/12 12:03:01 heko Exp $
+.\" $OpenBSD: disklabel.5,v 1.12 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: disklabel.5,v 1.3 1995/03/18 14:54:36 cgd Exp $
.\"
.\" Copyright (c) 1987, 1991, 1993
@@ -78,18 +78,18 @@ the
.Dv DIOCWLABEL
.Xr ioctl 2 ,
which is done as needed by the
-.Xr disklabel
+.Em disklabel
program, allows modification of the label sector.
.Pp
A copy of the in-core label for a disk can be obtained with the
.Dv DIOCGDINFO
-.Xr ioctl ;
+.Em ioctl ;
this works with a file descriptor for a block or character
.Pq Dq raw
device for any partition of the disk.
The in-core copy of the label is set by the
.Dv DIOCSDINFO
-.Xr ioctl .
+.Em ioctl .
The offset of a partition cannot generally be changed while it is open,
nor can it be made smaller while it is open.
One exception is that any change is allowed if no label was found
@@ -97,27 +97,29 @@ on the disk, and the driver was able to construct only a skeletal label
without partition information.
The
.Dv DIOCWDINFO
-.Xr ioctl
+.Em ioctl
operation sets the in-core label and then updates the on-disk label;
there must be an existing label on the disk for this operation to succeed.
Thus, the initial label for a disk or disk pack must be installed
by writing to the raw disk.
The
.Dv DIOCGPDINFO
-.Xr ioctl
-operation gets the default label for a disk. This simulates the case
+.Em ioctl
+operation gets the default label for a disk.
+This simulates the case
where there is no physical label on the disk itself and can be used to
see the label the kernel would construct in that case.
The
.Dv DIOCRLDINFO
-.Xr ioctl
+.Em ioctl
operation causes the kernel to update its copy of label based on the
-physical label on the disk. It can be used when the on-disk version
+physical label on the disk.
+It can be used when the on-disk version
of the label was changed directly or, if there is no physical label,
to update the kernel's skeletal label if some variable affecting label
generation has changed (e.g. the fdisk partition table).
All of these operations are normally done using
-.Xr disklabel .
+.Em disklabel .
.Pp
The format of the disk label, as specified in
.Pa sys/disklabel.h ,
diff --git a/sbin/disklabel/disklabel.8 b/sbin/disklabel/disklabel.8
index 8a020294a05..60c2b52466e 100644
--- a/sbin/disklabel/disklabel.8
+++ b/sbin/disklabel/disklabel.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: disklabel.8,v 1.42 2001/08/17 11:13:57 mpech Exp $
+.\" $OpenBSD: disklabel.8,v 1.43 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: disklabel.8,v 1.9 1995/03/18 14:54:38 cgd Exp $
.\"
.\" Copyright (c) 1987, 1988, 1991, 1993
@@ -421,7 +421,8 @@ block and fragment size on ffs partitions).
.It z
Zeroes out the existing partition table, leaving only the
.Dq c
-partition. The drive parameters are not changed.
+partition.
+The drive parameters are not changed.
.El
.Pp
In the restore form of the command, the prototype file used to create
diff --git a/sbin/dump/dump.8 b/sbin/dump/dump.8
index 52ceb061175..0e909fd9db4 100644
--- a/sbin/dump/dump.8
+++ b/sbin/dump/dump.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: dump.8,v 1.25 2001/10/04 22:28:03 ho Exp $
+.\" $OpenBSD: dump.8,v 1.26 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: dump.8,v 1.17 1997/06/05 11:15:06 lukem Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
@@ -425,4 +425,4 @@ kept track of the tapes scribbled on,
told the operator which tape to mount when,
and provided more assistance
for the operator running
-.Xr restore .
+.Xr restore 8 .
diff --git a/sbin/ifconfig/ifconfig.8 b/sbin/ifconfig/ifconfig.8
index 098f3ce8b75..d9b12804f5e 100644
--- a/sbin/ifconfig/ifconfig.8
+++ b/sbin/ifconfig/ifconfig.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ifconfig.8,v 1.52 2001/09/15 18:06:56 mickey Exp $
+.\" $OpenBSD: ifconfig.8,v 1.53 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: ifconfig.8,v 1.11 1996/01/04 21:27:29 pk Exp $
.\" $FreeBSD: ifconfig.8,v 1.16 1998/02/01 07:03:29 steve Exp $
.\"
@@ -283,7 +283,8 @@ If the interface is a vlan pseudo interface, set the vlan tag value
to
.Ar vlan_tag .
This value is a 16-bit number which is used to create an 802.1Q
-vlan header for packets sent from the vlan interface. Note that
+vlan header for packets sent from the vlan interface.
+Note that
.Cm vlan
and
.Cm vlandev
@@ -294,17 +295,20 @@ If the interface is a vlan pseudo device, associate physical interface
with it. Packets transmitted through the vlan interface will be
diverted to the specified physical interface
.Ar iface
-with 802.1Q vlan encapsulation. Packets with 802.1Q encapsulation received
+with 802.1Q vlan encapsulation.
+Packets with 802.1Q encapsulation received
by the parent interface with the correct vlan tag will be diverted to
-the associated vlan pseudo-interface. The vlan interface is assigned a
+the associated vlan pseudo-interface.
+The vlan interface is assigned a
copy of the parent interface's flags and the parent's ethernet address.
The
.Cm vlandev
and
.Cm vlan
-must both be set at the same time. If the vlan interface already has
-a physical interface associated with it, this command will fail. To
-change the association to another physical interface, the existing
+must both be set at the same time.
+If the vlan interface already has
+a physical interface associated with it, this command will fail.
+To change the association to another physical interface, the existing
association must be cleared first.
.Pp
Note: if the
@@ -318,7 +322,8 @@ own (usually in firmware) and that it should pass packets to and from
the parent unaltered.
.It Fl vlandev
If the driver is a vlan pseudo device, disassociate the physical interface
-from it. This breaks the link between the vlan interface and its parent,
+from it.
+This breaks the link between the vlan interface and its parent,
clears its vlan tag, flags and its link address and shuts the interface down.
.It Cm metric Ar n
Set the routing metric of the interface to
diff --git a/sbin/init/init.8 b/sbin/init/init.8
index a0dd333a96f..4de70749109 100644
--- a/sbin/init/init.8
+++ b/sbin/init/init.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: init.8,v 1.29 2001/04/05 18:54:03 deraadt Exp $
+.\" $OpenBSD: init.8,v 1.30 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: init.8,v 1.6 1995/03/18 14:56:31 cgd Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
@@ -116,14 +116,14 @@ processes for the terminal ports found in the file
reads this file, and executes the command found in the second field.
This command is usually
.Xr getty 8 ;
-.Xr getty
+.Em getty
opens and initializes the tty line
and
executes the
-.Xr login
+.Em login
program.
The
-.Xr login
+.Em login
program, when a valid user logs in,
executes a shell for that user.
When this shell dies, either because the user logged out
@@ -134,18 +134,18 @@ program wakes up, deletes the user
from the
.Xr utmp 5
file of current users and records the logout in the
-.Xr wtmp
+.Em wtmp
file.
The cycle is
then restarted by
.Nm
executing a new
-.Xr getty
+.Em getty
for the line.
.Pp
Line status (on, off, secure, getty, or window information)
may be changed in the
-.Xr ttys
+.Em ttys
file without a reboot by sending the signal
.Dv SIGHUP
to
@@ -155,21 +155,21 @@ with the command
On receipt of this signal,
.Nm
re-reads the
-.Xr ttys
+.Em ttys
file.
When a line is turned off in
-.Xr ttys ,
+.Em ttys ,
.Nm
will send a
.Dv SIGHUP
signal to the controlling process
for the session associated with the line.
For any lines that were previously turned off in the
-.Xr ttys
+.Em ttys
file and are now on,
.Nm
executes a new
-.Xr getty
+.Em getty
to enable a new login.
If the getty or window field for a line is changed,
the change takes effect at the end of the current
@@ -177,14 +177,14 @@ login session (e.g., the next time
.Nm
starts a process on the line).
If a line is commented out or deleted from
-.Xr ttys ,
+.Em ttys ,
.Nm
will not do anything at all to that line.
However, it will complain that the relationship between lines
in the
-.Xr ttys
+.Em ttys
file and records in the
-.Xr utmp
+.Em utmp
file is out of sync,
so this practice is not recommended.
.Pp
@@ -241,11 +241,13 @@ When starting the
.Xr rc 8
files, the login class
.Dq daemon
-is used. When starting a window system or
+is used.
+When starting a window system or
.Xr getty 8 ,
the login class
.Dq default
-is used. No resource changes are made when entering single user mode.
+is used.
+No resource changes are made when entering single user mode.
.Sh DIAGNOSTICS
.Bl -diag
.It "getty repeating too quickly on port %s, sleeping"
@@ -268,7 +270,7 @@ a persistent device error condition.
system console device
.It Pa /dev/tty*
terminal ports found in
-.Xr ttys
+.Em ttys
.It Pa /var/run/utmp
record of users currently logged in
.It Pa /var/log/wtmp
diff --git a/sbin/iopctl/iopctl.8 b/sbin/iopctl/iopctl.8
index 7e93dd8d094..adfc9c6ecce 100644
--- a/sbin/iopctl/iopctl.8
+++ b/sbin/iopctl/iopctl.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: iopctl.8,v 1.2 2001/08/02 18:37:34 mpech Exp $
+.\" $OpenBSD: iopctl.8,v 1.3 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: iopctl.8,v 1.4 2001/03/20 13:07:51 ad Exp $
.\"
.\" Copyright (c) 2000 The NetBSD Foundation, Inc.
@@ -70,8 +70,8 @@ from the specified target.
Retrieve and display the device identity parameter group from the specified
target.
.It showlct
-Display the driver's private copy of the logical configuration table. This
-copy of the LCT matches the current device configuration, but is not
+Display the driver's private copy of the logical configuration table.
+This copy of the LCT matches the current device configuration, but is not
necessarily the latest available version of the LCT.
.It showstatus
Display the current status of the IOP.
diff --git a/sbin/ipsecadm/ipsecadm.8 b/sbin/ipsecadm/ipsecadm.8
index 99a6aba22e2..e0225eee7b8 100644
--- a/sbin/ipsecadm/ipsecadm.8
+++ b/sbin/ipsecadm/ipsecadm.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ipsecadm.8,v 1.47 2001/12/10 03:26:51 ho Exp $
+.\" $OpenBSD: ipsecadm.8,v 1.48 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright 1997 Niels Provos <provos@physnet.uni-hamburg.de>
.\" All rights reserved.
@@ -291,10 +291,12 @@ Default action is to flush all types of security associations
from the kernel.
.It ipcomp
Setup an IP Compression Association (IPCA) which will use the IPcomp
-transforms. Just like an SA, an IPCA consists of the destination
+transforms.
+Just like an SA, an IPCA consists of the destination
address, a Compression Parameter Index (CPI) and a protocol (which is
-fixed to IPcomp). Compression algorithms are applied. Allowed
-modifiers are:
+fixed to IPcomp).
+Compression algorithms are applied.
+Allowed modifiers are:
.Fl dst ,
.Fl src ,
.Fl cpi ,
@@ -302,9 +304,11 @@ modifiers are:
and
.Fl forcetunnel .
To create an IPsec SA using compression, an IPCA and an SA must first
-be created. After this a IPCA/SA bundle must be created using the
+be created.
+After this a IPCA/SA bundle must be created using the
.Nm group
-keyword. The IPCA must be applied first.
+keyword.
+The IPCA must be applied first.
.El
.Pp
If no command is given
@@ -405,8 +409,8 @@ Also
.Nm rmd160
for both new ah and esp.
.It Fl comp
-The compression algorithm to be used with the IPCA. The only possible value
-currently is:
+The compression algorithm to be used with the IPCA.
+The only possible value currently is:
.Nm deflate .
.It Fl key
The secret symmetric key used for encryption and authentication.
@@ -433,7 +437,8 @@ One practical way of generating keys is by using the
.Xr random 4
device (e.g., dd if=/dev/urandom bs=1024 count=1 | sha1)
.It Fl keyfile
-Read the key from a file. May be used instead of the
+Read the key from a file.
+May be used instead of the
.Fl key
flag, and has the same syntax considerations.
.It Fl authkey
@@ -454,7 +459,8 @@ One practical way of generating keys is by using the
.Xr random 4
device (e.g., dd if=/dev/urandom bs=1024 count=1 | sha1)
.It Fl authkeyfile
-Read the authkey from a file. May be used instead of the
+Read the authkey from a file.
+May be used instead of the
.Fl authkey
flag, and has the same syntax considerations.
.It Fl iv
@@ -588,8 +594,8 @@ traffic.
For
.Nm flow ,
specify that packets matching this flow must use IPsec, and establish
-SAs dynamically as needed. If no SAs are established, traffic is not
-allowed through.
+SAs dynamically as needed.
+If no SAs are established, traffic is not allowed through.
.It Fl dontacq
For
.Nm flow ,
diff --git a/sbin/isakmpd/apps/keyconv/keyconv.8 b/sbin/isakmpd/apps/keyconv/keyconv.8
index 3f54570b35e..a6f7dea1580 100644
--- a/sbin/isakmpd/apps/keyconv/keyconv.8
+++ b/sbin/isakmpd/apps/keyconv/keyconv.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: keyconv.8,v 1.3 2001/08/22 16:24:44 ho Exp $
+.\" $OpenBSD: keyconv.8,v 1.4 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 2001 Hakan Olsson. All rights reserved.
.\"
@@ -67,7 +67,8 @@ Convert from
.Pa OpenSSL
to
.Pa DNSSEC
-format. In this mode,
+format.
+In this mode,
.Nm
outputs both the private key, plus a
.Em outfile.pubkey
diff --git a/sbin/isakmpd/isakmpd.8 b/sbin/isakmpd/isakmpd.8
index b9612909e7e..b4ca86e1a32 100644
--- a/sbin/isakmpd/isakmpd.8
+++ b/sbin/isakmpd/isakmpd.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: isakmpd.8,v 1.35 2001/12/10 04:06:45 ho Exp $
+.\" $OpenBSD: isakmpd.8,v 1.36 2001/12/13 20:16:48 mpech Exp $
.\" $EOM: isakmpd.8,v 1.23 2000/05/02 00:30:23 niklas Exp $
.\"
.\" Copyright (c) 1998, 1999, 2000, 2001 Niklas Hallqvist.
@@ -59,8 +59,8 @@
The
.Nm
daemon establishes security associations for encrypted
-and/or authenticated network traffic. At this moment,
-and probably forever, this means
+and/or authenticated network traffic.
+At this moment, and probably forever, this means
.Xr ipsec 4
traffic.
.Pp
@@ -79,13 +79,14 @@ socket, and lastly by scheduled events triggered by timers running out.
Most uses of
.Nm
will be to implement so called "virtual private
-networks" or VPNs for short. The
+networks" or VPNs for short.
+The
.Xr vpn 8
manual page describes how to setup
.Nm
-for a simple VPN. For other
-uses, some more knowledge of IKE as a protocol is required. One source
-of information are the RFCs mentioned below.
+for a simple VPN.
+For other uses, some more knowledge of IKE as a protocol is required.
+One source of information are the RFCs mentioned below.
.Pp
The options are as follows:
.Bl -tag -width Ds
@@ -190,10 +191,12 @@ On the other hand, the port specified to capital
will be what the daemon binds its local end to when acting as
initiator.
.It Fl L
-Enable IKE packet capture. When this option is given,
+Enable IKE packet capture.
+When this option is given,
.Nm
will capture to file an unencrypted copy of the negotiation packets it
-is sending and receiveing. This file can later be read by
+is sending and receiveing.
+This file can later be read by
.Xr tcpdump 8
and other utilities using
.Xr pcap 3 .
@@ -218,16 +221,17 @@ flag.
.El
.Ss Setting up an IKE public key infrastructure (a.k.a. PKI)
In order to use public key based authentication, there has to be an
-infrastructure managing the key signing. Either there is an already
-existing PKI
+infrastructure managing the key signing.
+Either there is an already existing PKI
.Nm
-should take part in, or there will be a need to setup one. In the former
-case, what is needed to be done varies depending on the actual Certificate
-Authority used, and is therefore not covered here, more than
-mentioning that
+should take part in, or there will be a need to setup one.
+In the former case, what is needed to be done varies depending on the
+actual Certificate Authority used, and is therefore not covered here,
+more than mentioning that
.Xr openssl 1
needs to be used to create a certificate signing request that the
-CA understands. The latter case however is described here:
+CA understands.
+The latter case however is described here:
.Pp
.Bl -enum
.It
@@ -240,10 +244,11 @@ Create your own CA as root.
.Ed
.Pp
You are now being asked to enter information that will be incorporated
-into your certificate request. What you are about to enter is what is
-called a Distinguished Name or a DN. There are quite a few fields but
-you can leave some blank. For some fields there will be a default
-value, if you enter '.', the field will be left blank.
+into your certificate request.
+What you are about to enter is what is called a Distinguished Name or a DN.
+There are quite a few fields but you can leave some blank.
+For some fields there will be a default value, if you enter '.', the field
+will be left blank.
.Pp
.Bd -literal
# openssl x509 -req -days 365 -in /etc/ssl/private/ca.csr \\
@@ -253,13 +258,14 @@ value, if you enter '.', the field will be left blank.
.Ed
.Pp
.It
-Create keys and certificates for your IKE peers. This step as well
-as the next one, needs to be done for every peer. Furthermore the
-last step will need to be done once for each ID you want the peer
-to have. The 10.0.0.1 below symbolizes that ID, in this case an IPv4 ID,
-and should be changed for each invocation. You will be asked for a DN
-for each run. Encoding the ID in the common name is recommended, as
-it should be unique.
+Create keys and certificates for your IKE peers.
+This step as well as the next one, needs to be done for every peer.
+Furthermore the last step will need to be done once for each ID you
+want the peer to have.
+The 10.0.0.1 below symbolizes that ID, in this case an IPv4 ID,
+and should be changed for each invocation.
+You will be asked for a DN for each run.
+Encoding the ID in the common name is recommended, as it should be unique.
.Pp
.Bd -literal
# openssl genrsa -out /etc/isakmpd/private/local.key 1024
@@ -268,8 +274,9 @@ it should be unique.
.Ed
.Pp
Now take these certificate signing requests to your CA and process
-them like below. You have to add some extensions to the certificate
-in order to make it usable for
+them like below.
+You have to add some extensions to the certificate in order to make it
+usable for
.Nm isakmpd .
There are two possible ways to add the extensions to the certificate.
Either you have to to run
@@ -315,7 +322,8 @@ somehost.somedomain instead of 10.0.0.1)
.Pp
Put the certificate (the file ending in .crt) in
.Pa /etc/isakmpd/certs/
-on your local system. Also carry over the CA cert
+on your local system.
+Also carry over the CA cert
.Pa /etc/ssl/ca.crt
and put it in
.Pa /etc/isakmpd/ca/.
@@ -359,21 +367,23 @@ The directory where IKE certificates can be found, both the local
certificate(s) and those of the peers, if a choice to have them kept
permanently has been made.
.It Pa /etc/isakmpd/isakmpd.conf
-The configuration file. As this file can contain sensitive information
+The configuration file.
+As this file can contain sensitive information
it must not be readable by anyone but the user running
.Nm isakmpd .
.It Pa /etc/isakmpd/isakmpd.policy
-The keynote policy configuration file. The same mode
-requirements as
+The keynote policy configuration file.
+The same mode requirements as
.Nm isakmpd.conf .
.It Pa /etc/isakmpd/private/local.key
-A local private key for certificate based authentication. There has
-to be a certificate for this key in the certificate directory mentioned
-above. The same mode requirements as
+A local private key for certificate based authentication.
+There has to be a certificate for this key in the certificate directory
+mentioned above.
+The same mode requirements as
.Nm isakmpd.conf .
.It Pa /etc/isakmpd/pubkeys/
-Directory in which trusted public keys can be kept. The keys must be
-named after a fashion described above.
+Directory in which trusted public keys can be kept.
+The keys must be named after a fashion described above.
.It Pa /var/run/isakmpd.pid
The PID of the current daemon.
.It Pa /var/run/isakmpd.fifo
diff --git a/sbin/isakmpd/isakmpd.conf.5 b/sbin/isakmpd/isakmpd.conf.5
index 18ebb3ef507..e97dc36a03f 100644
--- a/sbin/isakmpd/isakmpd.conf.5
+++ b/sbin/isakmpd/isakmpd.conf.5
@@ -1,4 +1,4 @@
-.\" $OpenBSD: isakmpd.conf.5,v 1.60 2001/12/10 03:45:03 ho Exp $
+.\" $OpenBSD: isakmpd.conf.5,v 1.61 2001/12/13 20:16:48 mpech Exp $
.\" $EOM: isakmpd.conf.5,v 1.57 2000/12/21 14:43:17 ho Exp $
.\"
.\" Copyright (c) 1998, 1999, 2000 Niklas Hallqvist. All rights reserved.
@@ -80,7 +80,6 @@ To activate changes to
without restarting
.Nm isakmpd ,
send a SIGHUP signal to the daemon process.
-.Pp
.Ss Auto-generated parts of the configuration
.Pp
Some predefined section names are recognized by the daemon, voiding the need
@@ -102,16 +101,15 @@ pre-shared keys.
Example 2: QM-ESP-3DES-SHA-PFS-SUITE means; ESP protocol, 3DES encryption,
SHA hash, and use Perfect Forward Security.
.Pp
-There are two predefined lifetimes used. The Main Mode lifetime,
-named LIFE_MAIN_MODE, currently
-defaults to one hour (minimum 60 seconds, maximum 1 day). The Quick Mode
-lifetime,
-LIFE_QUICK_MODE,
+There are two predefined lifetimes used.
+The Main Mode lifetime, named LIFE_MAIN_MODE, currently
+defaults to one hour (minimum 60 seconds, maximum 1 day).
+The Quick Mode lifetime, LIFE_QUICK_MODE,
defaults to 20 minutes (minimum 60 seconds, maximum 1 day).
.Pp
In addition, the predefinitions include some default values for the special
-sections "General", and "X509-certificates". These values are presented in
-the example below.
+sections "General", and "X509-certificates".
+These values are presented in the example below.
.Pp
Note that using the predefined section names imply some minor limitations.
There are currently no predefined ESP+AH Quick Mode suites, and the
@@ -189,8 +187,9 @@ updating an SA with its parameters a 2nd time will be ignored.
.It Em Pubkey-directory
The directory in which
.Nm
-looks for explicitly trusted public keys. The default is
-"/etc/isakmpd/pubkeys". Read
+looks for explicitly trusted public keys.
+The default is "/etc/isakmpd/pubkeys".
+Read
.Xr isakmpd 8
for the required naming convention of the files in here.
.El
@@ -200,8 +199,8 @@ ISAKMP SA negotiation parameter root
.It Em <IP-address>
A name of the ISAKMP peer at the given IP-address.
.It Em Default
-A name of the default ISAKMP peer. Incoming
-Phase 1 connections from other IP-addresses will use this peer name.
+A name of the default ISAKMP peer.
+Incoming Phase 1 connections from other IP-addresses will use this peer name.
.It ""
This name is used as the section name for further information to be found.
Look at <ISAKMP-peer> below.
@@ -238,36 +237,39 @@ The credentials file contains
.Xr keynote 4
credentials that are sent to a remote IKE daemon when we use the
associated ID, or credentials that we may want to consider when doing
-an exchange with a remote IKE daemon that uses that ID. Note that, in
-the former case, the last credential in the file MUST contain our
-public key in its Licensees field. More than one credentials may exist
-in the file. They are separated by whitelines (the format is
-essentially the same as that of the policy file). The credentials are
-of the same format as the policies described in
+an exchange with a remote IKE daemon that uses that ID.
+Note that, in the former case, the last credential in the file
+MUST contain our public key in its Licensees field.
+More than one credentials may exist in the file.
+They are separated by whitelines (the format is essentially the same as
+that of the policy file).
+The credentials are of the same format as the policies described in
.Xr isakmpd.policy 5 .
The only difference is that the Authorizer field contains a public
-key, and the assertion is signed. Signed assertions can be generated
-using the
+key, and the assertion is signed.
+Signed assertions can be generated using the
.Xr keynote 1
utility.
.Pp
The private_key file contains the private RSA key we use for
-authentication. If the directory (and the files) exist, they take
-precedence over X509-based authentication.
+authentication.
+If the directory (and the files) exist, they take precedence over X509-based
+authentication.
.El
.It Em X509-Certificates
.Bl -tag -width 12n
.It Em Ca-directory
A directory containing PEM certificates of certification authorities
-that we trust to sign other certificates. Note that for a CA to be
-really trusted, it needs to be somehow referred to by policy, in
+that we trust to sign other certificates.
+Note that for a CA to be really trusted, it needs to be somehow
+referred to by policy, in
.Xr isakmpd.policy 5 .
The certificates in this directory are used for the actual X.509
authentication and for cross-referencing policies that refer to
-Distinguished Names (DNs). Keeping a separate directory (as opposed
-to integrating policies and X.509 CA certificates) allows for maintenance
-of a list of "well known" CAs without actually having to trust all (or any)
-of them.
+Distinguished Names (DNs).
+Keeping a separate directory (as opposed to integrating policies
+and X.509 CA certificates) allows for maintenance of a list of
+"well known" CAs without actually having to trust all (or any) of them.
.It Em Cert-directory
A directory containing PEM certificates that we trust to be valid.
These certificates are used in preference to those passed in messages and
@@ -971,9 +973,10 @@ configuration files.
.Xr isakmpd 8
.Sh BUGS
The RFCs does not permit differing DH groups in the same proposal for
-aggressive and quick mode exchanges. As the predefined suites currently
-uses DH group 1 for MD5 suites and DH group 2 for SHA suites, combining
-a MD5 and a SHA suite in a proposal will cause the exchange to fail.
+aggressive and quick mode exchanges.
+As the predefined suites currently uses DH group 1 for MD5 suites and
+DH group 2 for SHA suites, combining a MD5 and a SHA suite in a proposal
+will cause the exchange to fail.
.Pp
The current recommended workaround is to either use MD5- or SHA-only
suites, or to specify the suites manually.
diff --git a/sbin/isakmpd/isakmpd.policy.5 b/sbin/isakmpd/isakmpd.policy.5
index d0408c91437..51cb295154d 100644
--- a/sbin/isakmpd/isakmpd.policy.5
+++ b/sbin/isakmpd/isakmpd.policy.5
@@ -1,4 +1,4 @@
-.\" $OpenBSD: isakmpd.policy.5,v 1.23 2001/10/05 04:40:42 ho Exp $
+.\" $OpenBSD: isakmpd.policy.5,v 1.24 2001/12/13 20:16:48 mpech Exp $
.\" $EOM: isakmpd.policy.5,v 1.24 2000/11/23 12:55:25 niklas Exp $
.\"
.\" Copyright (c) 1999-2001, Angelos D. Keromytis. All rights reserved.
@@ -134,10 +134,11 @@ is read when
.Xr isakmpd 8
is first started, and every time it receives a
.Dv SIGHUP
-signal. The new policies read will be used for all new Phase 2 (IPsec)
+signal.
+The new policies read will be used for all new Phase 2 (IPsec)
SAs established from that point on (even if the associated Phase 1 SA
-was already established when the new policies were loaded). The policy
-change will not affect already established Phase 2 SAs.
+was already established when the new policies were loaded).
+The policy change will not affect already established Phase 2 SAs.
.Pp
For more details on KeyNote assertion format, please see
.Xr keynote 5 .
diff --git a/sbin/lmccontrol/lmccontrol.8 b/sbin/lmccontrol/lmccontrol.8
index fbf78cd6684..312c1708e13 100644
--- a/sbin/lmccontrol/lmccontrol.8
+++ b/sbin/lmccontrol/lmccontrol.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: lmccontrol.8,v 1.7 2001/08/02 18:37:34 mpech Exp $
+.\" $OpenBSD: lmccontrol.8,v 1.8 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 1997-1999 LAN Media Corporation (LMC)
.\" All rights reserved. www.lanmedia.com
@@ -85,7 +85,8 @@ The options are as follows:
.It Ar interface
The interface name of the Lan Media card (default is lmc0)
.It Fl l Ar speed
-To manually specify line speed, in bits per second (for devices without built-in CSU/DSU)
+To manually specify line speed, in bits per second (for devices without
+built-in CSU/DSU)
.It Fl c
Sets the interface to use an external clock source.
This is only valid for SSI/HSSI cards.
diff --git a/sbin/mount_tcfs/mount_tcfs.8 b/sbin/mount_tcfs/mount_tcfs.8
index c38bd95283e..bfcf954bda6 100644
--- a/sbin/mount_tcfs/mount_tcfs.8
+++ b/sbin/mount_tcfs/mount_tcfs.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: mount_tcfs.8,v 1.4 2001/07/20 18:07:11 mpech Exp $
+.\" $OpenBSD: mount_tcfs.8,v 1.5 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 1980, 1989, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@@ -72,7 +72,7 @@ A
command appeared in
.Ox 2.7 .
.Sh BUGS
-This is a preliminary version, only for developers. Each other use is
-discouraged.
+This is a preliminary version, only for developers.
+Each other use is discouraged.
.Pp
Sorry, no docs.
diff --git a/sbin/pdisk/pdisk.8 b/sbin/pdisk/pdisk.8
index 4722599d5c4..d88152f13f0 100644
--- a/sbin/pdisk/pdisk.8
+++ b/sbin/pdisk/pdisk.8
@@ -84,7 +84,9 @@ initialize partition map
.It Em s
change size of partition map
.It Em c
-create new partition (standard OpenBSD type)
+create new partition (standard
+.Ox
+type)
.It Em C
create with type also specified
.It Em n
diff --git a/sbin/pfctl/pfctl.8 b/sbin/pfctl/pfctl.8
index f3a38bf265f..9a7694ddc56 100644
--- a/sbin/pfctl/pfctl.8
+++ b/sbin/pfctl/pfctl.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: pfctl.8,v 1.36 2001/12/10 18:13:30 dhartmei Exp $
+.\" $OpenBSD: pfctl.8,v 1.37 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 2001 Kjell Wooding. All rights reserved.
.\"
@@ -255,6 +255,7 @@ Generate debug messages only for serious errors.
.It Fl x Ar misc
Generate debug messages for various errors.
.El
+.El
.Sh FILES
.Bl -tag -width "/etc/nat.conf" -compact
.It Pa /etc/pf.conf
diff --git a/sbin/pflogd/pflogd.8 b/sbin/pflogd/pflogd.8
index 51955cd5fab..27231d1083c 100644
--- a/sbin/pflogd/pflogd.8
+++ b/sbin/pflogd/pflogd.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: pflogd.8,v 1.9 2001/12/06 03:58:29 deraadt Exp $
+.\" $OpenBSD: pflogd.8,v 1.10 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 2001 Can Erkin Acar. All rights reserved.
.\"
@@ -88,7 +88,8 @@ Debugging mode.
.Nm
does not disassociate from the controlling terminal.
.It Fl f Ar filename
-Log output filename. Default is
+Log output filename.
+Default is
.Pa /var/log/pflog .
.It Fl s Ar snaplen
Analyze at most the first
@@ -100,6 +101,7 @@ Other file parsers may desire a higher snaplen.
.It Ar expression
selects which packets will be dumped, using the regular language of
.Xr tcpdump 8 .
+.El
.Sh EXAMPLES
Log specific tcp packets to a different log file with a large snaplen
(useful with a log-all rule to dump complete sessions)
diff --git a/sbin/shutdown/shutdown.8 b/sbin/shutdown/shutdown.8
index afe3c29438d..469eb16b964 100644
--- a/sbin/shutdown/shutdown.8
+++ b/sbin/shutdown/shutdown.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: shutdown.8,v 1.30 2001/10/11 19:54:29 miod Exp $
+.\" $OpenBSD: shutdown.8,v 1.31 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: shutdown.8,v 1.6 1995/03/18 15:01:07 cgd Exp $
.\"
.\" Copyright (c) 1988, 1991, 1993
@@ -51,7 +51,8 @@
provides an automated shutdown procedure for superusers
to nicely notify users when the system is shutting down,
saving them from system administrators, hackers, and gurus, who
-would otherwise not bother with such niceties. When the
+would otherwise not bother with such niceties.
+When the
.Nm
command is issued without options the system is placed in single
user mode at the indicated time after shutting down all system
@@ -162,7 +163,7 @@ At shutdown time a message is written in the system log, containing the
time of shutdown, who initiated the shutdown and the reason.
A terminate
signal is then sent to
-.Xr init
+.Em init
to bring the system down to single-user state (depending on above
options).
The time of the shutdown and the warning message
diff --git a/sbin/sysctl/sysctl.8 b/sbin/sysctl/sysctl.8
index 518b43a4943..037912b1e3b 100644
--- a/sbin/sysctl/sysctl.8
+++ b/sbin/sysctl/sysctl.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: sysctl.8,v 1.70 2001/12/06 20:37:16 ericj Exp $
+.\" $OpenBSD: sysctl.8,v 1.71 2001/12/13 20:16:48 mpech Exp $
.\" $NetBSD: sysctl.8,v 1.4 1995/09/30 07:12:49 thorpej Exp $
.\"
.\" Copyright (c) 1993
@@ -80,8 +80,8 @@ set psize=`sysctl -n hw.pagesize`
If just a MIB style name is given,
the corresponding value is retrieved.
.It Fl w
-required to set a variable. The MIB name should be followed
-by an equal sign and the new value.
+required to set a variable.
+The MIB name should be followed by an equal sign and the new value.
.El
.Pp
The information available from
diff --git a/sbin/wicontrol/wicontrol.8 b/sbin/wicontrol/wicontrol.8
index ad235978e45..617cc3d736f 100644
--- a/sbin/wicontrol/wicontrol.8
+++ b/sbin/wicontrol/wicontrol.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: wicontrol.8,v 1.21 2001/08/02 18:37:34 mpech Exp $
+.\" $OpenBSD: wicontrol.8,v 1.22 2001/12/13 20:16:48 mpech Exp $
.\"
.\" Copyright (c) 1997, 1998, 1999
.\" Bill Paul <wpaul@ctr.columbia.edu> All rights reserved.
@@ -75,7 +75,8 @@ IEEE 802.11 protocol which the WaveLAN implements.
This includes
the station name, whether the station is operating in ad-hoc (point
to point) or BSS (service set) mode, and the network name of a service
-set to join (IBSS) if BSS mode is enabled. The
+set to join (IBSS) if BSS mode is enabled.
+The
.Nm
command can also be used to view the current settings of these parameters
and to dump out the values of the card's statistics counters.
@@ -299,7 +300,8 @@ The legal values are
.Ar 1
(Roaming handled by firmware) and
.Ar 3
-(Roaming Disabled). The default is 1.
+(Roaming Disabled).
+The default is 1.
.It Fl S Ar max sleep interval
Specify the sleep interval to use when power management is enabled.
The