summaryrefslogtreecommitdiff
path: root/scsitape.1
diff options
context:
space:
mode:
Diffstat (limited to 'scsitape.1')
-rw-r--r--scsitape.167
1 files changed, 31 insertions, 36 deletions
diff --git a/scsitape.1 b/scsitape.1
index db4c220..3f135bb 100644
--- a/scsitape.1
+++ b/scsitape.1
@@ -23,14 +23,14 @@
.\"
.TH SCSITAPE 1 SCSITAPE1.0
.SH NAME
-scsitape \- control SCSI tape devices
+scsitape \- control SCSI tape devices
.SH SYNOPSIS
scsitape [-f <scsi-generic-device>] commands
.SH DESCRIPTION
-The
+The
.B scsitape
command controls SCSI tape drives in a platform-independent
-manner. As long as 'mtx' works on the platform, so does 'scsitape'.
+manner. As long as 'mtx' works on the platform, so does 'scsitape'.
.P
Note that 'scsitape' and your OS's native tape driver may stomp on each
other. In particular, if you use 'setblk' and your OS's native tape
@@ -38,13 +38,13 @@ driver has a different notion of the block size, you may get evil results.
It is recommended to use 'scsitape' only for software where you've written
your own low-level READ and WRITE routines that use the SCSI command set
to directly talk to tape drives (i.e., you do not use the OS's native tape
-driver at all).
+driver at all).
.SH OPTIONS
The first argument, given following
.B -f
, is the SCSI generic device corresponding to your tape drive.
Consult your operating system's documentation for more information (for
-example, under Linux these are generally /dev/sg0 through /dev/sg15,
+example, under Linux these are generally /dev/sg0 through /dev/sg15,
under FreeBSD these are /dev/pass0 through /dev/passX. Under Solaris
this is usually the same as your tape drive (Solaris has a SCSI passthrough
ioctl). You can set the STAPE or TAPE environment variable rather
@@ -54,7 +54,7 @@ than use -f.
.TP 10
.B setblk <n>
Set the tape drive's SCSI block size to <n> bytes. (NOTE: if you are
-using your OS's native tape driver, THIS IS EVIL!).
+using your OS's native tape driver, THIS IS EVIL!).
.TP 10
.B fsf <n>
@@ -67,7 +67,7 @@ after a tapemark and type 'bfs 1', it moves to immediately *before*
that tape mark, for a sum total of zero effective movement!).
.TP 10
.B eod
-Go to end of data.
+Go to end of data.
.TP 10
.B rewind
Rewind the tape drive.
@@ -76,21 +76,21 @@ Rewind the tape drive.
Eject the tape currently in the drive.
.TP 10
.B erase
-Does a *short* erase (warning: does NOT work on all drives!).
+Does a *short* erase (warning: does NOT work on all drives!).
.TP 10
.B mark <n>
- write <n> filemarks ( 'mark 0' flushes the drive's buffers ).
+ write <n> filemarks ( 'mark 0' flushes the drive's buffers ).
.TP 10
.B seek <n>
Seek to a logical position <n> that was reported by a previous 'tapeinfo'
-command.
+command.
.TP 10
-.B write <blocksize>
+.B write <blocksize>
write blocks from stdin to the tape. Chunk the data into <blocksize>-sized
-chunks. *DOES NOT WRITE OUT A TAPEMARK!* (you will need to use a
+chunks. *DOES NOT WRITE OUT A TAPEMARK!* (you will need to use a
subsequent
.B mark 1
-command to write out a tape mark).
+command to write out a tape mark).
.TP 10
.B read [<blocksize>] [ <#blocks/#bytes> ]
read blocks from the tape, write them to stdout. If we are in variable
@@ -99,13 +99,13 @@ we currently support in variable block mode is 128K, MAX_READ_SIZE will
need to be turned into a settable variable to allow bigger reads). If
<blocksize> is omitted, we assume that we're in variable block mode, and
that we are going to read from tape until we hit a tapemark or end of
-partition or end of tape.
+partition or end of tape.
.SH AUTHORS
-This program was written by Eric Lee Green <eric@badtux.org>.
+This program was written by Eric Lee Green <eric@badtux.org>.
Major portions of the 'mtxl.c' library used herein were written by
-Leonard Zubkoff.
+Leonard Zubkoff.
.P
The SCSI read and write routines are based upon those that Richard
@@ -120,28 +120,23 @@ identifiers). As required by 'mtxl.c', these routines are licensed
under the GNU General Public License.
.SH HINTS
-Under Linux,
-.B cat /proc/scsi/scsi
-will tell you what SCSI devices you have.
-You can then refer to them as
-.B /dev/sga,
-.B /dev/sgb,
-etc. by the order they
-are reported.
+Under Linux,
+.B lsscsi \-\-generic
+will tell you what SCSI devices you have and their device names.
.P
-Under FreeBSD,
+Under FreeBSD,
.B camcontrol devlist
will tell you what SCSI devices you
-have, along with which
+have, along with which
.B pass
device controls them.
.P
Under Solaris 7 and 8,
.B /usr/sbin/devfsadm -C
will clean up your /devices directory. Then
-.B find /devices -name 'st@*' -print
+.B find /devices -name 'st@*' -print
will return a list of all tape drives. /dev on Solaris is apparently only
-of historical interest.
+of historical interest.
.SH BUGS AND LIMITATIONS
@@ -150,7 +145,7 @@ for
where you are doing variable-block-size reads and wish for <n> bytes,
it instead reads one and exactly one block from tape and prints that
(no matter what its size). Use 'dd' on the output of scsitape if you
-want finer control.
+want finer control.
.P
.B scsitape read 0
attempts reads of MAX_READ_SIZE, which is currently 128K. If blocks on tape
@@ -161,19 +156,19 @@ This program does not interact well (or at all :-) with your OS's
native tape driver. You will likely see weird things happen if you
attempt to intermingle scsitape commands with native tape driver
operations. Note that BRU 16.1 for Solaris (and possibly others, but
-Solaris I know about) will have a 'scsi' keyword to bypass the
+Solaris I know about) will have a 'scsi' keyword to bypass the
native tape driver and write via direct uscsi commands, so if you
use 'scsitape' to bypass the flaws of the native Solaris driver, you can use
BRU 16.1 to write your actual tape archives. (Assuming that BRU 16.1
-has been released at the time that you read this).
+has been released at the time that you read this).
.SH AVAILABILITY
-This version of
+This version of
.B scsitape
-is currently being maintained by Robert Nelson <robertnelson@users.sourceforge.net>
-as part of the 'mtx' suite of programs. The 'mtx' home page is
-http://mtx.sourceforge.net and the actual code is currently available there and via
-SVN from http://sourceforge.net/projects/mtx.
+is currently being maintained by Robert Nelson <robertnelson@users.sourceforge.net>
+as part of the 'mtx' suite of programs. The 'mtx' home page is
+http://mtx.sourceforge.net and the actual code is currently available there and via
+SVN from http://sourceforge.net/projects/mtx.
.SH SEE ALSO
.BR loaderinfo (1), tapeinfo (1), mtx (1)