- remove all trailing whitespace

     * except when it is escaped with a `\' at the end of the line
- fix remaining .Nm usage as well
- this is from a patch I received from kwesterback@home.com, who has been
  working on some scripts for fixing formatting errors in mdoc'd man pages

Ok, so there could be a cost/benefit debate with this commit, but since I have
the patch we might as well commit it...

1 files changed, 43 insertions, 43 deletions

diff --git a/share/man/man4/raid.4 b/share/man/man4/raid.4
index 54882d1fcc1..98a977f5757 100644
--- a/share/man/man4/raid.4
+++ b/share/man/man4/raid.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: raid.4,v 1.5 1999/07/08 09:41:43 hugh Exp $
+.\"	$OpenBSD: raid.4,v 1.6 1999/07/09 13:35:48 aaron Exp $
 .\"
 .\"
 .\" Copyright (c) 1998 The NetBSD Foundation, Inc.
@@ -38,29 +38,29 @@
 .\"
 .\" Copyright (c) 1995 Carnegie-Mellon University.
 .\" All rights reserved.
-.\" 
+.\"
 .\" Author: Mark Holland
-.\" 
+.\"
 .\" Permission to use, copy, modify and distribute this software and
 .\" its documentation is hereby granted, provided that both the copyright
 .\" notice and this permission notice appear in all copies of the
 .\" software, derivative works or modified versions, and any portions
 .\" thereof, and that both notices appear in supporting documentation.
-.\" 
+.\"
 .\" CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
 .\" CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND
 .\" FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
-.\" 
+.\"
 .\" Carnegie Mellon requests users of this software to return to
-.\" 
+.\"
 .\"  Software Distribution Coordinator  or  Software.Distribution@CS.CMU.EDU
 .\"  School of Computer Science
 .\"  Carnegie Mellon University
 .\"  Pittsburgh PA 15213-3890
-.\" 
+.\"
 .\" any improvements or extensions that they make and grant Carnegie the
 .\" rights to redistribute these changes.
-.\" 
+.\"
 .Dd November 9, 1998
 .Dt RAID 4
 .Os
@@ -75,20 +75,20 @@ The
 driver provides RAID 0, 1, 4, and 5 (and more!) capabilities.  This
 document assumes that the reader has at least some familiarity with RAID
 and RAID concepts.  The reader is also assumed to know how to configure
-disks and pseudo-devices into kernels, how to generate kernels, and how 
+disks and pseudo-devices into kernels, how to generate kernels, and how
 to partition disks.
 .Pp
 RAIDframe provides a number of different RAID levels including:
 .Bl -tag -width indent
-.It RAID 0 
+.It RAID 0
 provides simple data striping across the components.
-.It RAID 1 
+.It RAID 1
 provides mirroring.
-.It RAID 4 
+.It RAID 4
 provides data striping across the components, with parity
 stored on a dedicated drive (in this case, the last component).
-.It RAID 5 
-provides data striping across the components, with parity 
+.It RAID 5
+provides data striping across the components, with parity
 distributed across all the components.
 .El
 .Pp
@@ -108,8 +108,8 @@ reconstructed from the data and parity present on the other
 components.  This results in much slower data accesses, but
 does mean that a failure need not bring the system to a complete halt.
 .Pp
-The driver supports 
-.Sq hot spares , 
+The driver supports
+.Sq hot spares ,
 disks which are on-line, but are not
 actively used in an existing filesystem.  Should a disk fail, the
 driver is capable of reconstructing the failed disk onto a hot spare.
@@ -122,39 +122,39 @@ the reconstructed data from the hot spare to the previously failed
 If a component cannot be detected when the RAID device is configured,
 that component will be simply marked as 'failed'.
 .Pp
-The user-land utility for doing all 
+The user-land utility for doing all
 .Nm
 configuration and other operations
-is 
+is
 .Xr raidctl 8 .
-For any of the RAID flavours which have parity data, 
+For any of the RAID flavours which have parity data,
 .Xr raidctl 8
-must be used with the 
+must be used with the
 .Fl r
 option to re-write the data when either a) a new RAID device is
 brought up for the first time or b) after an un-clean shutdown of a
-RAID device.  By performing this on-demand recomputation of all parity 
-before doing a 
+RAID device.  By performing this on-demand recomputation of all parity
+before doing a
 .Xr fsck 8
 or a
 .Xr newfs 8
 filesystem integrity and parity integrity can be ensured.  It bears
-repeating again that parity recomputation is 
+repeating again that parity recomputation is
 .Em required
 before any filesystems are created or used on the RAID device.  If the
 parity is not correct, then missing data cannot be correctly recovered.
 .Pp
-RAID levels may be combined in a hierarchical fashion.  For example, a RAID 0 
-device can be constructed out of a number of RAID 5 devices (which, in turn, 
+RAID levels may be combined in a hierarchical fashion.  For example, a RAID 0
+device can be constructed out of a number of RAID 5 devices (which, in turn,
 may be constructed out of the physical disks, or of other RAID devices).
 .Pp
-At the time of this writing, it is 
+At the time of this writing, it is
 .Em imperative
-that drives be 
+that drives be
 .Sq nailed down
 at their respective addresses (i.e. not left free-floating, where a
-drive with SCSI ID of 4 can end up as /dev/sd0c).  Consider a system 
-with three SCSI drives at SCSI IDs 4, 5, and 6, and which map to 
+drive with SCSI ID of 4 can end up as /dev/sd0c).  Consider a system
+with three SCSI drives at SCSI IDs 4, 5, and 6, and which map to
 components /dev/sd0e, /dev/sd1e, and /dev/sd2e.  If the drive with
 SCSI ID 5 fails,
 and the system reboots, the old /dev/sd2e will show up as /dev/sd1e.
@@ -164,7 +164,7 @@ actually become /dev/sd1e.  Hopefully this will change within a few
 days of this writing with the addition of MD5 checksums to each of the
 components.
 .Pp
-The first step to using the 
+The first step to using the
 .Nm
 driver is to ensure that it is suitably configured in the kernel.  This is
 done by adding a line similar to:
@@ -172,12 +172,12 @@ done by adding a line similar to:
 pseudo-device   raid   4       # RAIDframe disk device
 .Ed
 .Pp
-to the kernel configuration file.  The 
+to the kernel configuration file.  The
 .Sq count
 argument (
 .Sq 4 ,
 in this case), specifies the number of RAIDframe drivers to configure.
-At the time of this writing, 4 is the MAXIMUM of 
+At the time of this writing, 4 is the MAXIMUM of
 .Nm
 devices which are supported.  This will change as soon as kernel threads
 are available.
@@ -187,17 +187,17 @@ In all cases the
 partitions of the disks
 .Pa must not
 be combined.  Rather, each component parition should be offset by at least one
-cylinder from the beginning of that component disk.  This ensures that 
+cylinder from the beginning of that component disk.  This ensures that
 the disklabels for the component disks do not conflict with the
-disklabel for the 
+disklabel for the
 .Nm
 device.
 As well, all component paritions must be of the type
 .Dv FS_BSDFFS .
 .Pp
-A more detailed treatment of actually using a 
+A more detailed treatment of actually using a
 .Nm
-device is found in 
+device is found in
 .Xr raidctl 8 .
 It is highly recommended that the steps to reconstruct, copyback, and
 re-compute parity are well understood by the system administrator(s)
@@ -211,11 +211,11 @@ 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 
+RAID is
 .Em not
 a substitute for good backup practices.
 .Pp
-Recomputation of parity 
+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
@@ -223,7 +223,7 @@ 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. 
+0 there is no perception of increased data security.
 .Pp
 .Sh FILES
 .Bl -tag -width /dev/XXrXraidX -compact
@@ -240,16 +240,16 @@ device special files.
 .Xr newfs 8 ,
 .Xr raidctl 8
 .Sh HISTORY
-The 
+The
 .Nm
-driver in 
+driver in
 .Ox
 is a port of RAIDframe, a framework for rapid prototyping of RAID
 structures developed by the folks at the Parallel Data Laboratory at
 Carnegie Mellon University (CMU).  RAIDframe, as originally distributed
 by CMU, provides a RAID simulator for a number of different
 architectures, and a user-level device driver and a kernel device
-driver for Digital Unix.  The 
+driver for Digital Unix.  The
 .Nm
 driver is a kernelized version of RAIDframe v1.1.
 .Pp
@@ -258,7 +258,7 @@ RAIDframe is found in the paper "RAIDframe: A Rapid Prototyping Tool
 for RAID Systems", by William V. Courtright II, Garth Gibson, Mark
 Holland, LeAnn Neal Reilly, and Jim Zelenka, and published by the
 Parallel Data Laboratory of Carnegie Mellon University.
-The 
+The
 .Nm
 driver first appeared in
 .Nx 1.4