10 files changed, 150 insertions, 150 deletions

diff --git a/lib/libc/gen/dirname.3 b/lib/libc/gen/dirname.3
index d26593f24d1..214943c45a9 100644
--- a/lib/libc/gen/dirname.3
+++ b/lib/libc/gen/dirname.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: dirname.3,v 1.17 2007/05/31 19:19:28 jmc Exp $
+.\" $OpenBSD: dirname.3,v 1.18 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 1997 Todd C. Miller <Todd.Miller@courtesan.com>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt DIRNAME 3
 .Os
 .Sh NAME
@@ -63,17 +63,6 @@ The following error codes may be set in
 The path component to be returned was larger than
 .Dv MAXPATHLEN .
 .El
-.Sh WARNINGS
-.Fn dirname
-returns a pointer to internal static storage space that will be overwritten
-by subsequent calls (each function has its own separate storage).
-.Pp
-Other vendor implementations of
-.Fn dirname
-may modify the contents of the string passed to
-.Fn dirname ;
-this should be taken into account when writing code which calls this function
-if portability is desired.
 .Sh SEE ALSO
 .Xr basename 1 ,
 .Xr dirname 1 ,
@@ -90,3 +79,14 @@ function first appeared in
 .Ox 2.2 .
 .Sh AUTHORS
 .An Todd C. Miller
+.Sh CAVEATS
+.Fn dirname
+returns a pointer to internal static storage space that will be overwritten
+by subsequent calls (each function has its own separate storage).
+.Pp
+Other vendor implementations of
+.Fn dirname
+may modify the contents of the string passed to
+.Fn dirname ;
+this should be taken into account when writing code which calls this function
+if portability is desired.
diff --git a/lib/libc/stdlib/a64l.3 b/lib/libc/stdlib/a64l.3
index 6eec5ce3b3d..da0aae33c90 100644
--- a/lib/libc/stdlib/a64l.3
+++ b/lib/libc/stdlib/a64l.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: a64l.3,v 1.10 2007/05/31 19:19:31 jmc Exp $
+.\" $OpenBSD: a64l.3,v 1.11 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 1997 Todd C. Miller <Todd.Miller@courtesan.com>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt A64L 3
 .Os
 .Sh NAME
@@ -108,7 +108,14 @@ returns a null pointer and sets the global variable
 .Va errno
 to
 .Er EINVAL .
-.Sh WARNINGS
+.Sh STANDARDS
+The
+.Fn a64l
+and
+.Fn l64a
+functions conform to
+.St -xpg4.2 .
+.Sh CAVEATS
 The value returned by
 .Fn l64a
 is a pointer into a static buffer, the contents of which
@@ -124,10 +131,3 @@ should be used to call
 .Pp
 If a long integer is larger than 32 bits, only the low-order
 32 bits are used.
-.Sh STANDARDS
-The
-.Fn a64l
-and
-.Fn l64a
-functions conform to
-.St -xpg4.2 .
diff --git a/lib/libc/stdlib/ecvt.3 b/lib/libc/stdlib/ecvt.3
index 0717a2c02a1..2f107e11fd2 100644
--- a/lib/libc/stdlib/ecvt.3
+++ b/lib/libc/stdlib/ecvt.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ecvt.3,v 1.8 2007/05/31 19:19:31 jmc Exp $
+.\" $OpenBSD: ecvt.3,v 1.9 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 2002 Todd C. Miller <Todd.Miller@courtesan.com>
 .\"
@@ -18,7 +18,7 @@
 .\" Agency (DARPA) and Air Force Research Laboratory, Air Force
 .\" Materiel Command, USAF, under agreement number F39502-99-1-0512.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt ECVT 3
 .Os
 .Sh NAME
@@ -138,7 +138,18 @@ and
 .Fn gcvt
 functions return a NUL-terminated string representation of
 .Fa value .
-.Sh WARNINGS
+.Sh SEE ALSO
+.Xr printf 3 ,
+.Xr strtod 3
+.Sh STANDARDS
+The
+.Fn ecvt ,
+.Fn fcvt
+and
+.Fn gcvt
+functions conform to
+.St -p1003.1-2001 .
+.Sh CAVEATS
 The
 .Fn ecvt
 and
@@ -152,14 +163,3 @@ precision of a double and may not be the same on all architectures.
 The
 .Xr snprintf 3
 function is preferred over these functions for new code.
-.Sh SEE ALSO
-.Xr printf 3 ,
-.Xr strtod 3
-.Sh STANDARDS
-The
-.Fn ecvt ,
-.Fn fcvt
-and
-.Fn gcvt
-functions conform to
-.St -p1003.1-2001 .
diff --git a/lib/libc/sys/chroot.2 b/lib/libc/sys/chroot.2
index f6e13682b4f..e5177ae0284 100644
--- a/lib/libc/sys/chroot.2
+++ b/lib/libc/sys/chroot.2
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: chroot.2,v 1.15 2010/01/11 22:17:36 deraadt Exp $
+.\"	$OpenBSD: chroot.2,v 1.16 2010/04/01 17:06:55 jmc Exp $
 .\"	$NetBSD: chroot.2,v 1.7 1995/02/27 12:32:12 cgd Exp $
 .\"
 .\" Copyright (c) 1983, 1991, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)chroot.2	8.1 (Berkeley) 6/4/93
 .\"
-.Dd $Mdocdate: January 11 2010 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt CHROOT 2
 .Os
 .Sh NAME
@@ -113,10 +113,10 @@ The caller is not the superuser.
 .El
 .Sh SEE ALSO
 .Xr chdir 2
-.Sh WARNINGS
-There are ways for a root process to escape from the chroot jail.
 .Sh HISTORY
 The
 .Fn chroot
 function call appeared in
 .Bx 4.2 .
+.Sh CAVEATS
+There are ways for a root process to escape from the chroot jail.
diff --git a/lib/libc/sys/gettimeofday.2 b/lib/libc/sys/gettimeofday.2
index d248adf8cb5..bb9d00213d1 100644
--- a/lib/libc/sys/gettimeofday.2
+++ b/lib/libc/sys/gettimeofday.2
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: gettimeofday.2,v 1.18 2010/04/01 11:28:49 deraadt Exp $
+.\"	$OpenBSD: gettimeofday.2,v 1.19 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
@@ -124,7 +124,12 @@ A user other than the superuser attempted to set the time.
 .Xr getitimer 2 ,
 .Xr ctime 3 ,
 .Xr timed 8
-.Sh WARNINGS
+.Sh HISTORY
+The
+.Fn gettimeofday
+function call appeared in
+.Bx 4.2 .
+.Sh CAVEATS
 Setting the time with
 .Fn settimeofday
 is dangerous; if possible use
@@ -132,7 +137,7 @@ is dangerous; if possible use
 instead.
 Many daemon programming techniques utilize time-delta techniques
 using the results from
-.Xr gettimeofday 2
+.Fn gettimeofday
 instead of from
 .Xr clock_gettime 2
 on the
@@ -140,8 +145,3 @@ on the
 clock.
 Time jumps can cause these programs to malfunction in unexpected ways.
 If the time must be set, consider rebooting the machine for safety.
-.Sh HISTORY
-The
-.Fn gettimeofday
-function call appeared in
-.Bx 4.2 .
diff --git a/lib/libutil/opendev.3 b/lib/libutil/opendev.3
index d6193280c4a..f6266b0188b 100644
--- a/lib/libutil/opendev.3
+++ b/lib/libutil/opendev.3
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: opendev.3,v 1.17 2007/05/31 19:19:38 jmc Exp $
+.\"	$OpenBSD: opendev.3,v 1.18 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 2000, Todd C. Miller.  All rights reserved.
 .\" Copyright (c) 1996, Jason Downs.  All rights reserved.
@@ -24,7 +24,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt OPENDEV 3
 .Os
 .Sh NAME
@@ -84,13 +84,6 @@ The
 .Fn opendev
 return value and errors are the same as the return value and errors of
 .Xr open 2 .
-.Sh WARNINGS
-If
-.Fa realpath
-is not
-.Dv NULL ,
-on return it will point to internal
-static storage space that will be overwritten by subsequent calls.
 .Sh SEE ALSO
 .Xr open 2 ,
 .Xr getrawpartition 3
@@ -99,3 +92,10 @@ The
 .Fn opendev
 function first appeared in
 .Ox 1.2 .
+.Sh CAVEATS
+If
+.Fa realpath
+is not
+.Dv NULL ,
+on return it will point to internal
+static storage space that will be overwritten by subsequent calls.
diff --git a/sbin/raidctl/raidctl.8 b/sbin/raidctl/raidctl.8
index fe258ff148d..c00be5d3bc0 100644
--- a/sbin/raidctl/raidctl.8
+++ b/sbin/raidctl/raidctl.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: raidctl.8,v 1.41 2008/06/26 05:42:06 ray Exp $
+.\"	$OpenBSD: raidctl.8,v 1.42 2010/04/01 17:06:55 jmc Exp $
 .\"     $NetBSD: raidctl.8,v 1.24 2001/07/10 01:30:52 lukem Exp $
 .\"
 .\" Copyright (c) 1998 The NetBSD Foundation, Inc.
@@ -54,7 +54,7 @@
 .\" any improvements or extensions that they make and grant Carnegie the
 .\" rights to redistribute these changes.
 .\"
-.Dd $Mdocdate: June 26 2008 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt RAIDCTL 8
 .Os
 .Sh NAME
@@ -1334,26 +1334,6 @@ where it will automatically be started by the
 .Pa /etc/rc
 scripts.
 .El
-.Sh WARNINGS
-Certain RAID levels (1, 4, 5, 6, and others) can protect against some
-data loss due to component failure.
-However the loss of two components of a RAID 4 or 5 system, or the loss
-of a single component of a RAID 0 system will result in the entire
-filesystem being lost.
-RAID is
-.Em NOT
-a substitute for good backup practices.
-.Pp
-Recomputation of parity
-.Em MUST
-be performed whenever there is a chance that it may have been
-compromised.
-This includes after system crashes, or before a RAID
-device has been used for the first time.
-Failure to keep parity correct will be catastrophic should a component
-ever fail -- it is better to use RAID 0 and get the additional space
-and speed, than it is to use parity, but not keep the parity correct.
-At least with RAID 0 there is no perception of increased data security.
 .Sh FILES
 .Bl -tag -width "/etc/raid[0-3].conf" -compact
 .It Pa /dev/{,r}raid*
@@ -1387,5 +1367,25 @@ is a complete re-write, and first appeared in
 .Nx 1.4
 from where it was ported to
 .Ox 2.5 .
+.Sh CAVEATS
+Certain RAID levels (1, 4, 5, 6, and others) can protect against some
+data loss due to component failure.
+However the loss of two components of a RAID 4 or 5 system, or the loss
+of a single component of a RAID 0 system will result in the entire
+filesystem being lost.
+RAID is
+.Em NOT
+a substitute for good backup practices.
+.Pp
+Recomputation of parity
+.Em MUST
+be performed whenever there is a chance that it may have been
+compromised.
+This includes after system crashes, or before a RAID
+device has been used for the first time.
+Failure to keep parity correct will be catastrophic should a component
+ever fail -- it is better to use RAID 0 and get the additional space
+and speed, than it is to use parity, but not keep the parity correct.
+At least with RAID 0 there is no perception of increased data security.
 .Sh BUGS
 Hot-spare removal is currently not available.
diff --git a/share/man/man4/raid.4 b/share/man/man4/raid.4
index f338c9cf3c3..7445c6fb384 100644
--- a/share/man/man4/raid.4
+++ b/share/man/man4/raid.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: raid.4,v 1.30 2008/06/26 05:42:07 ray Exp $
+.\"	$OpenBSD: raid.4,v 1.31 2010/04/01 17:06:55 jmc Exp $
 .\"     $NetBSD: raid.4,v 1.20 2001/09/22 16:03:58 wiz Exp $
 .\"
 .\" Copyright (c) 1998 The NetBSD Foundation, Inc.
@@ -54,7 +54,7 @@
 .\" any improvements or extensions that they make and grant Carnegie the
 .\" rights to redistribute these changes.
 .\"
-.Dd $Mdocdate: June 26 2008 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt RAID 4
 .Os
 .Sh NAME
@@ -289,26 +289,6 @@ Additional debug information can be sent to the console by specifying:
 .Bd -unfilled -offset indent
 option	RAIDDEBUG
 .Ed
-.Sh WARNINGS
-Certain RAID levels (1, 4, 5, 6, and others) can protect against some
-data loss due to component failure.
-However the loss of two components of a RAID 4 or 5 system, or the loss
-of a single component of a RAID 0 system, will result in the entire
-filesystems on that RAID device being lost.
-RAID is
-.Ar NOT
-a substitute for good backup practices.
-.Pp
-Recomputation of parity
-.Ar MUST
-be performed whenever there is a chance that it may have been
-compromised.
-This includes after system crashes, or before a RAID
-device has been used for the first time.
-Failure to keep parity correct will be catastrophic should a component
-ever fail -- it is better to use RAID 0 and get the additional space and
-speed, than it is to use parity, but not keep the parity correct.
-At least with RAID 0 there is no perception of increased data security.
 .Sh FILES
 .Bl -tag -width /dev/XXrXraidX -compact
 .It Pa /dev/{,r}raid*
@@ -319,9 +299,9 @@ device special files.
 .Xr ccd 4 ,
 .Xr sd 4 ,
 .Xr wd 4 ,
-.Xr MAKEDEV 8 ,
 .Xr config 8 ,
 .Xr fsck 8 ,
+.Xr MAKEDEV 8 ,
 .Xr mount 8 ,
 .Xr newfs 8 ,
 .Xr raidctl 8
@@ -352,3 +332,23 @@ driver first appeared in
 .Nx 1.4
 from where it was ported to
 .Ox 2.5 .
+.Sh CAVEATS
+Certain RAID levels (1, 4, 5, 6, and others) can protect against some
+data loss due to component failure.
+However the loss of two components of a RAID 4 or 5 system, or the loss
+of a single component of a RAID 0 system, will result in the entire
+filesystems on that RAID device being lost.
+RAID is
+.Ar NOT
+a substitute for good backup practices.
+.Pp
+Recomputation of parity
+.Ar MUST
+be performed whenever there is a chance that it may have been
+compromised.
+This includes after system crashes, or before a RAID
+device has been used for the first time.
+Failure to keep parity correct will be catastrophic should a component
+ever fail -- it is better to use RAID 0 and get the additional space and
+speed, than it is to use parity, but not keep the parity correct.
+At least with RAID 0 there is no perception of increased data security.
diff --git a/share/man/man5/hosts.equiv.5 b/share/man/man5/hosts.equiv.5
index e845d5d5a60..307c70b7d65 100644
--- a/share/man/man5/hosts.equiv.5
+++ b/share/man/man5/hosts.equiv.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: hosts.equiv.5,v 1.11 2007/05/31 19:19:58 jmc Exp $
+.\"	$OpenBSD: hosts.equiv.5,v 1.12 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 1997 Todd Vierling
 .\" Copyright (c) 1997 The NetBSD Foundation, Inc.
@@ -35,7 +35,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt HOSTS.EQUIV 5
 .Os
 .Sh NAME
@@ -87,6 +87,13 @@ local machine.
 If a
 .Ar username
 is not specified, any user may log in with the same user name.
+.Sh FILES
+.Bl -tag -width /etc/hosts.equiv -compact
+.It Pa /etc/hosts.equiv
+global trusted host-user pairs list
+.It Pa ~/.rhosts
+per-user trusted host-user pairs list
+.El
 .Sh EXAMPLES
 .Bl -ohang -compact
 .It Li somehost
@@ -120,7 +127,18 @@ case, allows any user on any machine to log in to the local host (as any
 user, if in
 .Pa /etc/hosts.equiv ) .
 .El
-.Sh WARNINGS
+.Sh SEE ALSO
+.Xr rcp 1 ,
+.Xr rsh 1 ,
+.Xr rcmd 3 ,
+.Xr ruserok 3 ,
+.Xr netgroup 5
+.Sh HISTORY
+The
+.Nm .rhosts
+file format appeared in
+.Bx 4.2 .
+.Sh CAVEATS
 The user name checks provided by this mechanism are
 .Em not
 secure, as the remote user name is received by the server unchecked
@@ -157,24 +175,6 @@ Access permitted through root's
 .Pa .rhosts
 file is typically only for
 .Xr rsh 1 .
-.Sh FILES
-.Bl -tag -width /etc/hosts.equiv -compact
-.It Pa /etc/hosts.equiv
-global trusted host-user pairs list
-.It Pa ~/.rhosts
-per-user trusted host-user pairs list
-.El
-.Sh SEE ALSO
-.Xr rcp 1 ,
-.Xr rsh 1 ,
-.Xr rcmd 3 ,
-.Xr ruserok 3 ,
-.Xr netgroup 5
-.Sh HISTORY
-The
-.Nm .rhosts
-file format appeared in
-.Bx 4.2 .
 .Sh BUGS
 The
 .Xr ruserok 3
diff --git a/usr.sbin/timed/timed/timed.8 b/usr.sbin/timed/timed/timed.8
index 6062bd1ce37..75a7b414308 100644
--- a/usr.sbin/timed/timed/timed.8
+++ b/usr.sbin/timed/timed/timed.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: timed.8,v 1.15 2007/05/31 19:20:30 jmc Exp $
+.\"	$OpenBSD: timed.8,v 1.16 2010/04/01 17:06:55 jmc Exp $
 .\"
 .\" Copyright (c) 1980, 1991 Regents of the University of California.
 .\" All rights reserved.
@@ -29,7 +29,7 @@
 .\"
 .\"     @(#)timed.8	6.7 (Berkeley) 5/11/93
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 1 2010 $
 .Dt TIMED 8
 .Os
 .Sh NAME
@@ -226,30 +226,6 @@ settings are often associated with
 .Dq multi-homed
 machines that looked for time masters on more than one network and eventually
 chose to become a slave on the other network.
-.Sh WARNINGS
-Temporal chaos will result if two or more time daemons attempt
-to adjust the same clock.
-If both
-.Nm
-and another time daemon are run on the same machine,
-ensure that the
-.Fl F
-flag is used, so that
-.Nm
-never attempts to adjust the local clock.
-.Pp
-The protocol is based on
-.Tn UDP/IP
-broadcasts.
-All machines within the range of a broadcast that are using the
-.Tn TSP
-protocol must cooperate.
-There cannot be more than a single administrative domain using the
-.Fl F
-flag among all machines reached by a broadcast packet.
-Failure to follow this rule is usually indicated by complaints concerning
-.Dq untrusted
-machines in the system log.
 .Sh FILES
 .Bl -tag -width /var/log/timed.masterlog -compact
 .It Pa /var/log/timed.log
@@ -279,3 +255,27 @@ The
 .Nm
 utility appeared in
 .Bx 4.3 .
+.Sh CAVEATS
+Temporal chaos will result if two or more time daemons attempt
+to adjust the same clock.
+If both
+.Nm
+and another time daemon are run on the same machine,
+ensure that the
+.Fl F
+flag is used, so that
+.Nm
+never attempts to adjust the local clock.
+.Pp
+The protocol is based on
+.Tn UDP/IP
+broadcasts.
+All machines within the range of a broadcast that are using the
+.Tn TSP
+protocol must cooperate.
+There cannot be more than a single administrative domain using the
+.Fl F
+flag among all machines reached by a broadcast packet.
+Failure to follow this rule is usually indicated by complaints concerning
+.Dq untrusted
+machines in the system log.