minor man page cleanup
git-svn-id: https://svn.bingwo.ca/repos/sg3_utils/trunk@369 6180dd3e-e324-4e3e-922d-17de1ae2f315
diff --git a/ChangeLog b/ChangeLog
index 54c37f9..ac3a573 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,7 +2,7 @@
some description at the top of its ".c" file. All utilities in the main
directory have their own "man" pages. There is also a sg3_utils man page.
-Changelog for sg3_utils-1.31 [20101222] [svn: r368]
+Changelog for sg3_utils-1.31 [20101224] [svn: r369]
- sg_decode_sense: new utility to decode sense data
- sync asc/ascq and version descriptors with spc4r28
- sg_lib: implement forwarded sense data descriptor
diff --git a/doc/sg3_utils.8 b/doc/sg3_utils.8
index 20927a4..92d6a19 100644
--- a/doc/sg3_utils.8
+++ b/doc/sg3_utils.8
@@ -87,7 +87,7 @@
.PP
There is also a SCSI device driver which offers alternate generic access
to SCSI devices. It uses names of the form /dev/sg<num> where <num> starts
-at zero. The "lsscsi -g" command may be useful in finding these and which
+at zero. The "lsscsi \-g" command may be useful in finding these and which
generic name corresponds to a device type name (e.g. /dev/sg2 may
correspond to /dev/sda). In the lk 2.6 series a block SCSI generic
driver was introduced and its names are of the form
@@ -164,7 +164,7 @@
directories. The former is the block device name and the latter is
for "raw" (or char device) access which is what sg3_utils needs. So in
OpenSolaris something of the form 'sg_inq /dev/rdsk/c5t4d3p0' should work.
-If it doesn't work then add a '-vvv' option for more debug information.
+If it doesn't work then add a '\-vvv' option for more debug information.
Trying this form 'sg_inq /dev/dsk/c5t4d3p0' (note "rdsk" changed to "dsk")
will result in an "inappropriate ioctl for device" error.
.PP
@@ -180,9 +180,9 @@
.PP
Listing available SCSI devices in Solaris seems to be a challenge. "Use
the 'format' command" advice works but seems a very dangerous way to list
-devices. [It does prompt again before doing any damage.] 'devfsadm -Cv'
+devices. [It does prompt again before doing any damage.] 'devfsadm \-Cv'
cleans out the clutter in the /dev/rdsk directory, only leaving what
-is "live". The "cfgadm -v" command looks promising.
+is "live". The "cfgadm \-v" command looks promising.
.SH EXIT STATUS
To aid scripts that call these utilities, the exit status is set to indicate
success (0) or failure (1 or more). Note that some of the lower values
diff --git a/doc/sg_inq.8 b/doc/sg_inq.8
index 6962da1..e37e582 100644
--- a/doc/sg_inq.8
+++ b/doc/sg_inq.8
@@ -1,4 +1,4 @@
-.TH SG_INQ "8" "September 2010" "sg3_utils\-1.30" SG3_UTILS
+.TH SG_INQ "8" "December 2010" "sg3_utils\-1.30" SG3_UTILS
.SH NAME
sg_inq \- sends a SCSI INQUIRY or ATA IDENTIFY (PACKET) DEVICE command
and outputs the response
@@ -335,13 +335,13 @@
Some SCSI devices include version descriptors indicating the various
SCSI standards and drafts they support. They can be viewed with:
.PP
- sg_inq -d /dev/sda
+ sg_inq \-d /dev/sda
.PP
Modern SCSI devices include Vital Product Data (VPD)pages which can be
viewed with the SCSI INQUIRY command. To list the supported VPD
pages (but not their contents) try:
.PP
- sg_inq -e /dev/sda
+ sg_inq \-e /dev/sda
.PP
Some VPD pages can be read with the sg_inq utility but a newer utility
called sg_vpd specializes in showing their contents. The sdparm utility
diff --git a/doc/sg_raw.8 b/doc/sg_raw.8
index 905f8be..be3d826 100644
--- a/doc/sg_raw.8
+++ b/doc/sg_raw.8
@@ -1,4 +1,4 @@
-.TH SG_RAW "8" "September 2010" "sg3_utils\-1.30" SG3_UTILS
+.TH SG_RAW "8" "December 2010" "sg3_utils\-1.31" SG3_UTILS
.SH NAME
sg_raw \- sends an arbitrary SCSI command to a device
.SH SYNOPSIS
@@ -102,10 +102,10 @@
When used in conjunction with the previous example, if both commands
work then 'cmp i512.bin o512.bin' should show a match.
.TP
-sg_raw --infile=urandom.bin --send=512 --request=512 --outfile=out.bin "/dev/bsg/7:0:0:0" 53 00 00 00 00 00 00 00 01 00
+sg_raw \-\-infile=urandom.bin \-\-send=512 \-\-request=512 \-\-outfile=out.bin "/dev/bsg/7:0:0:0" 53 00 00 00 00 00 00 00 01 00
This is a bidirectional XDREADWRITE(10) command being sent via a Linux
bsg device. Note that data is being read from "urandom.bin" and sent
-to the device (data-out) while resulting data (data-in) is placed
+to the device (data\-out) while resulting data (data\-in) is placed
in the "out.bin" file. Also note the length of both is 512 bytes
which corresponds to the transfer length of 1 (block) in the cdb (i.e.
the second last byte).
