diff options
| author | Peter Samuelson <peter@p12n.org> | 2007-05-08 17:13:25 +1000 |
|---|---|---|
| committer | Neil Brown <neilb@suse.de> | 2007-05-08 17:13:25 +1000 |
| commit | b3f1c093b77428e5746a563da1526da156011065 (patch) | |
| tree | 0234af8fc4b26aefefecbe011ec2e8b4a3e8611c | |
| parent | 35cc5be496384f053bf194ad7c91920178e8304b (diff) | |
| download | mdadm-b3f1c093b77428e5746a563da1526da156011065.tar.gz mdadm-b3f1c093b77428e5746a563da1526da156011065.tar.xz mdadm-b3f1c093b77428e5746a563da1526da156011065.zip | |
Hyphens and Other Manpage Typography, 2/4: proper nroff "em dash".
From: Peter Samuelson <peter@p12n.org>
\(em renders as "--" in ASCII, and a nice em dash (i.e., a dash the
width of the letter "m") in more capable formats like PostScript.
Signed-Off-By: Peter Samuelson <peter@p12n.org>
| -rw-r--r-- | md.4 | 6 | ||||
| -rw-r--r-- | mdadm.8 | 6 | ||||
| -rw-r--r-- | mdadm.conf.5 | 2 |
3 files changed, 7 insertions, 7 deletions
@@ -49,7 +49,7 @@ provides support for two different formats of this superblock, and other formats can be added. Prior to this release, only one format is supported. -The common format - known as version 0.90 - has +The common format \(em known as version 0.90 \(em has a superblock that is 4K long and is written into a 64K aligned block that starts at least 64K and less than 128K from the end of the device (i.e. to get the address of the superblock round the size of the @@ -61,7 +61,7 @@ This superblock stores multi-byte fields in a processor-dependant manner, so arrays cannot easily be moved between computers with different processors. -The new format - known as version 1 - has a superblock that is +The new format \(em known as version 1 \(em has a superblock that is normally 1K long, but can be longer. It is normally stored between 8K and 12K from the end of the device, on a 4K boundary, though variations can be stored at the start of the device (version 1.1) or 4K from @@ -432,7 +432,7 @@ increasing the number of drives in a raid5, this critical section covers the first few stripes (the number being the product of the old and new number of devices). After this critical section is passed, data is only written to areas of the array which no longer hold live -data - the live data has already been located away. +data \(em the live data has already been located away. md is not able to ensure data preservation if there is a crash (e.g. power failure) during the critical section. If md is asked to @@ -536,7 +536,7 @@ that the array pre-existed and is known to be clean. It can be useful when trying to recover from a major failure as you can be sure that no data will be affected unless you actually write to the array. It can also be used when creating a RAID1 or RAID10 if you want to avoid the -initial resync, however this practice - while normally safe - is not +initial resync, however this practice \(em while normally safe \(em is not recommended. Use this ony if you really know what you are doing. .TP @@ -1121,7 +1121,7 @@ option must be given to clarify how and whether the device should be created. This can be useful for handling partitioned devices (which don't have -a stable device number - it can change after a reboot) and when using +a stable device number \(em it can change after a reboot) and when using "udev" to manage your .B /dev tree (udev cannot handle md devices because of the unusual device @@ -1328,7 +1328,7 @@ be in use. .TP .B --readonly -start the array readonly - not supported yet. +start the array readonly \(em not supported yet. .SH MANAGE MODE diff --git a/mdadm.conf.5 b/mdadm.conf.5 index 2b9995b..5d09c9c 100644 --- a/mdadm.conf.5 +++ b/mdadm.conf.5 @@ -265,7 +265,7 @@ flag to mdadm. Give .BR md , .BR mdp , .B part -- possibly followed by a number of partitions - to indicate how +\(em possibly followed by a number of partitions \(em to indicate how missing device entries should be created. .TP |