manpages: escape dashes

This patch is originally from the Debian package but no
authorship information was contained within it.

Signed-off-by: Jeff Mahoney <jeffm@suse.com>

debugreiserfs/debugreiserfs.8.in

@@ -31,7 +31,7 @@ an IDE disk partition or /dev/sdXX for a SCSI disk partition).
 .SH OPTIONS
 .TP
 \fB-j\fR \fIdevice\fR
-prints the contents of the journal. The option -p allows it to pack the journal 
+prints the contents of the journal. The option \-p allows it to pack the journal 
 with other metadata into the archive.
 .TP
 \fB-J\fR
@@ -61,22 +61,22 @@ prints the specified block of the filesystem.
 .\" formatted nodes found. Can be used to find specific key in the filesystem.
 .\" .TP
 .B -p
-extracts the filesystem's metadata with \fBdebugreiserfs\fR -p /dev/xxx | gzip -c > 
+extracts the filesystem's metadata with \fBdebugreiserfs\fR \-p /dev/xxx | gzip \-c > 
 xxx.gz. None of your data are packed unless a filesystem corruption presents when 
 the whole block having this corruption is packed. You send us the output, and we use 
-it to create a filesystem with the same strucure as yours using \fBdebugreiserfs -u\fR.
+it to create a filesystem with the same strucure as yours using \fBdebugreiserfs \-u\fR.
 When the data file is not too large, this usually allows us to quickly reproduce 
 and debug the problem.
 .TP
 .B -u
-builds the ReiserFS filesystem image with gunzip -c xxx.gz | \fBdebugreiserfs\fR 
+builds the ReiserFS filesystem image with gunzip \-c xxx.gz | \fBdebugreiserfs\fR 
--u /dev/image of the previously packed metadata with \fBdebugreiserfs -p\fR. The
+\-u /dev/image of the previously packed metadata with \fBdebugreiserfs \-p\fR. The
 result image is not the same as the original filesystem, because mostly only metadata
-were packed with \fBdebugreiserfs -p\fR, but the filesystem structure is completely 
+were packed with \fBdebugreiserfs \-p\fR, but the filesystem structure is completely 
 recreated.
 .TP
 .B -S 
-When -S is not specified -p 
+When \-S is not specified \-p 
 .\" and -s 
 deals with blocks marked used in the filesystem bitmap only. With this option 
 set \fBdebugreiserfs\fR will work with the entire device.
@@ -84,7 +84,7 @@ set \fBdebugreiserfs\fR will work with the entire device.
 .B -q
 When 
 .\" -s or 
--p is in use, suppress showing the speed of progress.
+\-p is in use, suppress showing the speed of progress.
 .SH AUTHOR
 This version of \fBdebugreiserfs\fR has been written by Vitaly Fertman 
 <vitaly@namesys.com>.

fsck/reiserfsck.8.in

@@ -59,10 +59,10 @@ for directories, and deleting invalid directory entries.
 .B --rebuild-tree
 This option rebuilds the entire filesystem tree using leaf nodes 
 found on the device.  Normally you only need this option if the 
-\fBreiserfsck --check\fR reports "Running with \fB--rebuild-tree\fR
+\fBreiserfsck \-\-check\fR reports "Running with \fB\-\-rebuild-tree\fR
 is required". You are strongly encouraged to make a backup copy 
 of the whole partition before attempting the \fB--rebuild-tree\fR 
-option. Once \fBreiserfsck --rebuild-tree\fR is started it must
+option. Once \fBreiserfsck \-\-rebuild-tree\fR is started it must
 finish its work (and you should not interrupt it), otherwise the
 filesystem will be left in the unmountable state to avoid subsequent
 data corruptions.
@@ -95,7 +95,7 @@ byte are corrected by \fB--fix-fixable\fR.
 This option sets the badblock list to be the list of blocks specified in 
 the given `file`. The filesystem badblock list is cleared before the new 
 list is added. It can be used with \fB--fix-fixable\fR to fix the list of 
-badblocks (see \fBdebugreiserfs -B\fR). If the device has bad blocks, every
+badblocks (see \fBdebugreiserfs \-B\fR). If the device has bad blocks, every
 time it must be given with the \fB--rebuild-tree\fR option.
 .TP
 \fB--logfile \fIfile\fR, \fB-l \fI file\fR
@@ -114,7 +114,7 @@ telling you what it is going to do. It will assuem you confirm. For safety,
 it does not work with the \fB--rebuild-tree\fR option.
 .TP
 \fB-a\fR, \fB-p\fR
-These options are usually passed by fsck -A during the automatic checking 
+These options are usually passed by fsck \-A during the automatic checking 
 of those partitions listed in /etc/fstab. These options cause \fBreiserfsck\fR 
 to print some information about the specified filesystem, to check if error 
 flags in the superblock are set and to do some light-weight checks. If these 
@@ -149,23 +149,23 @@ the used space on the partition.
 1. You think something may be wrong with a reiserfs partition on /dev/hda1 
 or you would just like to perform a periodic disk check.
 
-2. Run \fBreiserfsck --check --logfile check.log /dev/hda1\fR. If \fBreiserfsck 
+2. Run \fBreiserfsck \-\-check \-\-logfile check.log /dev/hda1\fR. If \fBreiserfsck 
---check\fR exits with status 0 it means no errors were discovered. 
+\-\-check\fR exits with status 0 it means no errors were discovered. 
 
-3. If \fBreiserfsck --check\fR exits with status 1 (and reports about fixable 
+3. If \fBreiserfsck \-\-check\fR exits with status 1 (and reports about fixable 
-corruptions) it means that you should run \fBreiserfsck --fix-fixable --logfile 
+corruptions) it means that you should run \fBreiserfsck \-\-fix-fixable \-\-logfile 
 fixable.log /dev/hda1\fR.
 
-4. If \fBreiserfsck --check\fR exits with status 2 (and reports about fatal 
+4. If \fBreiserfsck \-\-check\fR exits with status 2 (and reports about fatal 
-corruptions) it means that you need to run \fBreiserfsck --rebuild-tree\fR.  
+corruptions) it means that you need to run \fBreiserfsck \-\-rebuild\-tree\fR.  
-If \fBreiserfsck --check\fR fails in some way you should also run \fBreiserfsck 
+If \fBreiserfsck \-\-check\fR fails in some way you should also run \fBreiserfsck 
---rebuild-tree\fR, but we also encourage you to submit this as a bug report.
+\-\-rebuild-tree\fR, but we also encourage you to submit this as a bug report.
 
-5. Before running \fBreiserfsck --rebuild-tree\fR, please make a backup of 
+5. Before running \fBreiserfsck \-\-rebuild-tree\fR, please make a backup of 
-the whole partition before proceeding. Then run \fBreiserfsck --rebuild-tree 
+the whole partition before proceeding. Then run \fBreiserfsck \-\-rebuild-tree 
---logfile rebuild.log /dev/hda1\fR.
+\-\-logfile rebuild.log /dev/hda1\fR.
 
-6. If the \fBreiserfsck --rebuild-tree\fR step fails or does not recover what 
+6. If the \fBreiserfsck \-\-rebuild-tree\fR step fails or does not recover what 
 you expected, please submit this as a bug report. Try to provide as much 
 information as possible including your platform and Linux kernel version. We 
 will try to help solve the problem.
@@ -180,11 +180,11 @@ will try to help solve the problem.
 .br
 \   \fI4\fR \-\ File system fatal errors left uncorrected,
 .br
-\	  \fBreiserfsck --rebuild-tree\fR needs to be launched.
+\	  \fBreiserfsck \-\-rebuild-tree\fR needs to be launched.
 .br
 \   \fI6\fR \-\ File system fixable errors left uncorrected,
 .br
-\	  \fBreiserfsck --fix-fixable\fR needs to be launched.
+\	  \fBreiserfsck \-\-fix-fixable\fR needs to be launched.
 .br
 \   \fI8\fR \-\ Operational error.
 .br

mkreiserfs/mkreiserfs.8.in

@@ -88,7 +88,7 @@ be adjusted.
 \fB-B\fR | \fB--badblocks \fIfile
 \fIFile\fR is the file name of the file that contains the list of blocks to be 
 marked as bad on the filesystem. This list can be created by
-\fB/sbin/badblocks -b block-size device\fR.
+\fB/sbin/badblocks \-b block-size device\fR.
 .TP
 \fB-f\fR
 Forces \fBmkreiserfs\fR to continue even when the device is the whole disk, 

resize_reiserfs/resize_reiserfs.8.in

@@ -102,7 +102,7 @@ with a
 .br
 \	umount /mnt
 .br
-\	resize_reiserfs -s -1G /dev/hda8
+\	resize_reiserfs \-s \-1G /dev/hda8
 .br
 \	mount /dev/hda8 /mnt
 .br

tune/reiserfstune.8.in

@@ -197,14 +197,14 @@ it working with its journal on the device /dev/journal
 .nf
 .IP
 boot kernel patched with special "relocatable journal support" patch
-reiserfstune /dev/hda1 --journal-new-device /dev/journal -f
+reiserfstune /dev/hda1 \-\-journal\-new\-device /dev/journal \-f
 mount /dev/hda1 and use.
 You would like to change max transaction size to 512 blocks
-reiserfstune -t 512 /dev/hda1
+reiserfstune \-t 512 /dev/hda1
 You would like to use your file system on another kernel that doesn't 
 contain relocatable journal support.
 umount /dev/hda1
-reiserfstune /dev/hda1 -j /dev/journal --journal-new-device /dev/hda1 --make-journal-standard
+reiserfstune /dev/hda1 \-j /dev/journal \-\-journal\-new\-device /dev/hda1 \-\-make\-journal\-standard
 mount /dev/hda1 and use.
 .LP
 2. You would like to have ReiserFS on /dev/hda1 and to be able to
@@ -215,13 +215,13 @@ device containing the filesystem.
 boot kernel patched with special "relocatable journal support" patch
 mkreiserfs /dev/hda1
 you got solid state disk (perhaps /dev/sda, they typically look like scsi disks)
-reiserfstune --journal-new-device /dev/sda1 -f /dev/hda1
+reiserfstune \-\-journal\-new\-device /dev/sda1 \-f /dev/hda1
 Your scsi device dies, it is three in the morning, you have an extra IDE device
 lying around
-reiserfsck --no-journal-available /dev/hda1
+reiserfsck \-\-no\-journal\-available /dev/hda1
 or
-reiserfsck --rebuild-tree --no-journal-available /dev/hda1
+reiserfsck \-\-rebuild-tree \-\-no\-journal\-available /dev/hda1
-reiserfstune --no-journal-available --journal-new-device /dev/hda1 /dev/hda1
+reiserfstune \-\-no\-journal\-available \-\-journal\-new\-device /dev/hda1 /dev/hda1
 using /dev/hda1 under patched kernel
 .SH AUTHOR
 This version of \fBreiserfstune\fR has been written by Vladimir