sg_ses: cleanups + output primary enc log id; manpages + spelling

git-svn-id: svn://localhost/trunk@431 6180dd3e-e324-4e3e-922d-17de1ae2f315

Author: doug-gilbert

ChangeLog

@@ -2,7 +2,7 @@ Each utility has its own version number, date of last change and
 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.33 [20111211] [svn: r430]
+Changelog for sg3_utils-1.33 [20111216] [svn: r431]
   - win: change DataBufferOffset type per MSDN; caused
     problem with 64 bit machines (buffered interface)
   - sg_inq, sg_vpd: sync with spc4r33

README

@@ -20,7 +20,7 @@ For example the sg_inq utility issues a SCSI INQUIRY command and decodes the
 response. The COVERAGE file has a table containing a row for each SCSI
 command issued by this package; to the right of each row is the utility
 (sometimes more than one) that issue that SCSI command. The COVERAGE file
-has a second table for ATA commands issude.
+has a second table for ATA commands usage.
 
 Some utilities interface at a slightly higher level, for example: sg_dd,
 sgm_dd and sgp_dd. These are closely related to the Unix dd command and
@@ -59,7 +59,7 @@ series.
 In sg3_utils version 1.27 support has been added for the Linux bsg driver
 which use the sg version 4 interface. There seems no point in renaming
 this package sg4_utils. The existing utilities just silently support either.
-Cuurently the source build must be able to see the /usr/include/linux/bsg.h
+Currently the source build must be able to see the /usr/include/linux/bsg.h
 file. Then at run time the /proc/devices pseudo file needs to have an entry
 for the bsg driver (appeared around lk 2.6.28). With this in place each
 utility at run time checks the device it has been given and if it is a char
@@ -124,7 +124,7 @@ scsi tape driver (st) in lk 2.6.6 .
 
 In the src directory the bulk of the utilities are written in relatively
 clean POSIX compliant C code with Linux specific system calls and structures
-removed and placed in linux specific files in the lib directory. A small
+removed and placed in Linux specific files in the lib directory. A small
 number of utilities in the src directory do contain Linux specific logic
 and are not ported to other OSes (e.g. sg_dd). One utility, sg_scan, has
 two separate implementations, one for Linux (sg_scan.c.linux) and one for
@@ -163,7 +163,7 @@ calls over OS specific calls.
 In Linux there are package build files for "rpm" based and for "deb" based
 systems. The 'sg3_utils.spec' file in the main directory can be used like
 this: 'rpmbuild -ba sg3_utils.spec' in a rpmbuild tree SPECS directory.
-To cross build or make a more widely distibutable package then the --target
+To cross build or make a more widely distributable package then the --target
 option may be useful: 'rpmbuild --target=i386 -ba sg3_utils.spec' .
 
 The 'build_debian.sh' script should build several "deb" packages and place
@@ -255,7 +255,7 @@ checks it against the asc/ascq text strings held in sg_lib_data.c .
 The 'doc' subdirectory contains a README file containing the urls of
 various related documents.
 
-The 'scripts' subdirectory contains some bourne (bash) shell scripts that
+The 'scripts' subdirectory contains some Bourne (bash) shell scripts that
 rely on utilities in the main directory. One script uses the sdparm utility.
 These scripts are described in the scripts/README file and have usage
 messages.

README.freebsd

@@ -6,7 +6,7 @@ similar functionality; for example 'sg_map' is similar to
 'camcontrol devlist'.
 
 The dd variants from the sg3_utils package (e.g. sg_dd) rely on too many
-Linux idiosyncracies to be easily ported. A new package called 'ddpt'
+Linux idiosyncrasies to be easily ported. A new package called 'ddpt'
 contains a utility with similar functionality to sg_dd and ddpt is available
 for FreeBSD.
 
@@ -70,7 +70,7 @@ the tarball and installed with the familiar
 running the "./autogen.sh" script prior to that sequence. There
 are generic instruction on configure and friend in the INSTALL file.
 
-Some man pages have examples which use linux device names which
+Some man pages have examples which use Linux device names which
 hopefully will not confuse the FreeBSD users.
 
 Device naming

README.iscsi

@@ -1,7 +1,7 @@
 iSCSI support for sg3-utils is available from external patches.
 
 To build sg3-utils from sources and activate built-in iSCSI support
-you need both sg3-utils and the external userspace iSCSI library hosted at :
+you need both sg3-utils and the external user-space iSCSI library hosted at :
 
 https://github.com/sahlberg/libiscsi
 

README.sg_start

@@ -4,7 +4,7 @@ you can use sg_start to start (spin-up, 1) and stop (spin-down, 0) devices.
 I also offers a parameter (-s) to send a synchronize cache command to a
 device, so it should write back its internal buffers to the medium.
 
-Be aware that the Linux SCSI subsystem at this time does not autmatically
+Be aware that the Linux SCSI subsystem at this time does not automatically
 starts stopped devices, so stopping a device which is in use may have fatal
 results for you.
 

README.solaris

@@ -4,7 +4,7 @@ The Solaris port of sg3_utils contains those utilities that are
 _not_ specific to Linux.
 
 The dd variants from the sg3_utils package (e.g. sg_dd) rely on too many
-Linux idiosyncracies to be easily ported. A new package called 'ddpt'
+Linux idiosyncrasies to be easily ported. A new package called 'ddpt'
 contains a utility with similar functionality to sg_dd and is available
 for Solaris.
 
@@ -68,7 +68,7 @@ the tarball and installed with the familiar
 running the "./autogen.sh" script prior to that sequence. There
 are generic instruction on configure and friend in the INSTALL file.
 
-Some man pages have examples which use linux device names which
+Some man pages have examples which use Linux device names which
 hopefully will not confuse the Solaris users.
 
 Device naming
@@ -90,7 +90,7 @@ disk. So a whole disk may be referred to as either:
 And these device names are duplicated in the /dev/dsk and /dev/rdsk
 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:
+So in OpenSolaris something of the form:
    sg_inq /dev/rdsk/c5t4d3p0
 should work. If it doesn't add a '-vvv' option. If that is attempted
 on the /dev/dsk/c5t4d3p0 variant an inappropriate ioctl for device

README.tru64

@@ -63,7 +63,7 @@ This package uses autotools infrastructure with the now common
 from the source found in the tarball. If the "./configure" sequence
 fails try using the ./autogen.sh prior to that sequence.
 
-Some man pages have examples which use linux device names which hopefully
+Some man pages have examples which use Linux device names which hopefully
 will not confuse Tru64 users.
 
 

README.win32

@@ -5,11 +5,11 @@ to Linux. One utility for listing available devices, sg_scan, has a
 Windows-specific version for this port.
 
 The dd variants from the sg3_utils package (e.g. sg_dd) rely on too many
-Linux idiosyncracies to be easily ported. A new package called 'ddpt'
+Linux idiosyncrasies to be easily ported. A new package called 'ddpt'
 contains a utility with similar functionality to sg_dd and is available
 for Windows.
 
-Two build environments are caterered for: cygwin (see www.cygwin.com) and
+Two build environments are catered for: cygwin (see www.cygwin.com) and
 MinGW ("Minimalist GNU for Windows", see www.mingw.org). Both are based in
 the gcc compiler (although other C compilers should have little problem with
 the source code). Cygwin is a more sophisticated, commercial product that
@@ -75,7 +75,7 @@ file. An overview of sg3_utils can be found at:
 http://sg.danny.cz/sg/sg3_utils.html .
 A copy of the "sg3_utils.html" file is in the "doc" subdirectory.
 
-Some man pages have examples which use linux device names which hopefully
+Some man pages have examples which use Linux device names which hopefully
 will not confuse Windows users.
 
 Two pass-through variants
@@ -105,7 +105,7 @@ rather than:
    ./configure
 prior to the 'make' call.
 
-In sg3_utils version 1.31 runtime selection of the direct or indirect
+In sg3_utils version 1.31 run-time selection of the direct or indirect
 interface was added with the scsi_pt_win32_direct(int state_direct)
 function declared in sg_pt.h. The default is indirect unless
 './configure --enable-win32-spt-direct' was used in the build. If

doc/scsi_logging_level.8

@@ -12,7 +12,7 @@ scsi_logging_level \- access Linux SCSI logging level information
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script accesses the Linux SCSI subsystem logging
+This Bourne shell script accesses the Linux SCSI subsystem logging
 level. The current values can be shown (e.g. with \fI\-\-get\fR)
 or changed (e.g. with \fI\-\-set\fR). Superuser permissions will
 typically be required to set the logging level.

doc/scsi_mandat.8

@@ -8,7 +8,7 @@ scsi_mandat \- check SCSI device support for mandatory commands
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls several SCSI commands on the given
+This Bourne shell script calls several SCSI commands on the given
 \fIDEVICE\fR. These SCSI commands are considered mandatory (although
 that varies a little depending on which standard/draft the \fIDEVICE\fR
 complies with). The results of each test and a pass/fail count are

doc/scsi_readcap.8

@@ -8,7 +8,7 @@ scsi_readcap \- do SCSI READ CAPACITY command on disks
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls the sg_readcap utility on each given
+This Bourne shell script calls the sg_readcap utility on each given
 \fIDEVICE\fR. This will send a SCSI READ CAPACITY command to each
 \fIDEVICE\fR.
 .PP

doc/scsi_ready.8

@@ -8,7 +8,7 @@ scsi_ready \- do SCSI TEST UNIT READY on devices
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls the sg_turs utility on each given
+This Bourne shell script calls the sg_turs utility on each given
 \fIDEVICE\fR. This will send a SCSI TEST UNIT READY command to each
 \fIDEVICE\fR. Disks, tape drives and DVD/BD players amongst others
 may respond to this SCSI command.

doc/scsi_satl.8

@@ -8,7 +8,7 @@ scsi_satl \- check SCSI to ATA Translation (SAT) device support
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls several SCSI commands on the given
+This Bourne shell script calls several SCSI commands on the given
 \fIDEVICE\fR that is assumed to be an ATA device behind a SCSI
 to ATA Translation (SAT) layer (SATL). The results of each test
 and a pass/fail count are output.

doc/scsi_start.8

@@ -8,7 +8,7 @@ scsi_start \- start one or more SCSI disks
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls the sg_start utility on each given
+This Bourne shell script calls the sg_start utility on each given
 \fIDEVICE\fR. The purpose is to spin up (start) each given \fIDEVICE\fR.
 .SH OPTIONS
 Arguments to long options are mandatory for short options as well.

doc/scsi_stop.8

@@ -8,7 +8,7 @@ scsi_stop \- stop (spin down) one or more SCSI disks
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls the sg_start utility on each given
+This Bourne shell script calls the sg_start utility on each given
 \fIDEVICE\fR. The purpose is to spin down (stop) each given \fIDEVICE\fR.
 .SH OPTIONS
 Arguments to long options are mandatory for short options as well.

doc/scsi_temperature.8

@@ -8,7 +8,7 @@ scsi_temperature \- fetch the temperature of a SCSI device
 .SH DESCRIPTION
 .\" Add any additional description here
 .PP
-This bourne shell script calls the sg_logs utility on each given
+This Bourne shell script calls the sg_logs utility on each given
 \fIDEVICE\fR in order to find the device's temperature. The Temperature
 log page is checked first and if it is not available then the Informational
 Exceptions log page is checked.

doc/sg3_utils.8

@@ -366,7 +366,7 @@ trailing "h" or "H" as found in (storage) standards. When hex numbers are
 given, multipliers cannot be used. For example the decimal value "256" can
 be given as "0x100" or "100h".
 .SH SCRIPTS, EXAMPLES and UTILS
-There are several bourne shell scripts in the 'scripts' subdirectory that
+There are several Bourne shell scripts in the 'scripts' subdirectory that
 invoke compiled utilities (e.g. sg_readcap). The scripts start with 'scsi_'
 rather than 'sg_'. One purpose of these scripts is to call the same
 utility (e.g. sg_readcap) on multiple disks. Most of the basic compiled

doc/sg_logs.8

@@ -30,7 +30,7 @@ LOG SELECT command. At the same time a page code field was introduced to the
 to the LOG SELECT command. The log subpage code can range from 0 to 255 (0xff)
 inclusive. The subpage code value 255 can be thought of as a wildcard.
 .PP
-This utility supports two command line syntaxes, the preferred one is shown
+This utility supports two command line surtaxes, the preferred one is shown
 first in the synopsis and explained in this section. A later section on the
 old command line syntax outlines the second group of options.
 .SH OPTIONS

doc/sg_senddiag.8

@@ -26,7 +26,7 @@ the page numbers of supported diagnostic pages).
 When the \fI\-\-list\fR option is given without a \fIDEVICE\fR then a list of
 diagnostic page names and their numbers, known by this utility, are listed.
 .PP
-This utility supports two command line syntaxes, the preferred one is
+This utility supports two command line syntax\-es, the preferred one is
 shown first in the synopsis and explained in this section. A later section
 on the old command line syntax outlines the second group of options.
 .SH OPTIONS
@@ -235,7 +235,7 @@ print out version string then exit.
 \fB\-?\fR
 output usage message. Ignore all other parameters.
 .SH EXAMPLES
-The examples subdirectory in the sg3_utils packages contains two example
+The examples sub\-directory in the sg3_utils packages contains two example
 scripts that turn on the CJTPAT (jitter pattern) on some SAS disks (one
 script for each phy). One possible invocation for phy 1 is:
 .PP