2 files changed, 44 insertions, 44 deletions
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