summaryrefslogtreecommitdiff
path: root/share/man/man4/raid.4
diff options
context:
space:
mode:
authorMike Pechkin <mpech@cvs.openbsd.org>2001-06-22 12:15:49 +0000
committerMike Pechkin <mpech@cvs.openbsd.org>2001-06-22 12:15:49 +0000
commita9223deae9367063797cc5a9d6152f1daf583153 (patch)
tree47fa1d8bb4523318a4103665c655d1a22001c8fb /share/man/man4/raid.4
parent0eb87a4a02e0b6bc731a76a842c1b13646016e26 (diff)
o) remove unnecessary .Pp;
o) remove unnecessary .Nm args; o) closes .Bl; o) .Sh AUTHOR -> .Sh AUTHORS; o) sort SEE ALSO; o) better -mdoc style; o) typos; aaron@ ok.
Diffstat (limited to 'share/man/man4/raid.4')
-rw-r--r--share/man/man4/raid.46
1 files changed, 2 insertions, 4 deletions
diff --git a/share/man/man4/raid.4 b/share/man/man4/raid.4
index db3194717e4..1fec69c5072 100644
--- a/share/man/man4/raid.4
+++ b/share/man/man4/raid.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: raid.4,v 1.12 2000/12/21 18:15:13 avsm Exp $
+.\" $OpenBSD: raid.4,v 1.13 2001/06/22 12:15:46 mpech Exp $
.\" $NetBSD: raid.4,v 1.8 1999/12/15 22:07:33 abs Exp $
.\"
.\"
@@ -261,21 +261,19 @@ 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.
-.Pp
.Sh FILES
.Bl -tag -width /dev/XXrXraidX -compact
.It Pa /dev/{,r}raid*
.Nm
device special files.
.El
-.Pp
.Sh SEE ALSO
+.Xr sd 4 ,
.Xr MAKEDEV 8 ,
.Xr config 8 ,
.Xr fsck 8 ,
.Xr mount 8 ,
.Xr newfs 8 ,
-.Xr sd 4 ,
.Xr raidctl 8
.Sh HISTORY
The