Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/trunk]: src/sbin/raidctl New sentence, new line.



details:   https://anonhg.NetBSD.org/src/rev/7f6b6cf367ff
branches:  trunk
changeset: 767886:7f6b6cf367ff
user:      wiz <wiz%NetBSD.org@localhost>
date:      Tue Aug 02 10:28:00 2011 +0000

description:
New sentence, new line.

diffstat:

 sbin/raidctl/raidctl.8 |  7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diffs (21 lines):

diff -r 6770c17ae5ed -r 7f6b6cf367ff sbin/raidctl/raidctl.8
--- a/sbin/raidctl/raidctl.8    Tue Aug 02 10:23:33 2011 +0000
+++ b/sbin/raidctl/raidctl.8    Tue Aug 02 10:28:00 2011 +0000
@@ -1,4 +1,4 @@
-.\"     $NetBSD: raidctl.8,v 1.62 2011/07/28 18:25:22 buhrow Exp $
+.\"     $NetBSD: raidctl.8,v 1.63 2011/08/02 10:28:00 wiz Exp $
 .\"
 .\" Copyright (c) 1998, 2002 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -1600,8 +1600,9 @@
 .Pp
 When replacing a failed component of a RAID set, it is a good
 idea to zero out the first 64 blocks of the new component to insure the
-RAIDframe driver doesn't erroneously detect a component label in the 
-new component.  This is particularly true on
+RAIDframe driver doesn't erroneously detect a component label in the
+new component.
+This is particularly true on
 .Em
 RAID 1
 sets because there is at most one correct component label in a failed RAID



Home | Main Index | Thread Index | Old Index