[src/trunk]: src/share/man/man4/man4.hp300 New sentence, new line. Some mdoc ...

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/73cbc17ee386
branches:  trunk
changeset: 546558:73cbc17ee386
user:      wiz <wiz%NetBSD.org@localhost>
date:      Thu May 01 14:11:11 2003 +0000

description:
New sentence, new line. Some mdoc fixes.

diffstat:

 share/man/man4/man4.hp300/st.4 |  106 +++++++++++++++++++++++-----------------
 1 files changed, 62 insertions(+), 44 deletions(-)

diffs (190 lines):

diff -r 0f3bbe689ff5 -r 73cbc17ee386 share/man/man4/man4.hp300/st.4
--- a/share/man/man4/man4.hp300/st.4    Thu May 01 14:03:39 2003 +0000
+++ b/share/man/man4/man4.hp300/st.4    Thu May 01 14:11:11 2003 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: st.4,v 1.8 2003/05/01 08:42:07 uebayasi Exp $
+.\"    $NetBSD: st.4,v 1.9 2003/05/01 14:11:11 wiz Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
 .\"    The Regents of the University of California.  All rights reserved.
@@ -53,13 +53,14 @@
 driver was written especially to support the Exabyte
 .Tn EXB-8200 8MM
 Cartridge
-Tape Subsystem.  It has several extensions specific to the Exabyte,
+Tape Subsystem.
+It has several extensions specific to the Exabyte,
 but should support other tape drives as long has they follow
 the
 .Tn ANSI SCSI-I
-specification.  Besides extensive use with
-an Exabyte, the driver has been tested with an
-Archive
+specification.
+Besides extensive use with an Exabyte, the driver has been
+tested with an Archive
 .Tn QIC-24
 tape drive.
 The
@@ -70,12 +71,11 @@
 with the following exceptions:
 .Bl -enum
 .It
-Density is dependent on device type.  Current Exabyte hardware has
-only one density. The
+Density is dependent on device type.
+Current Exabyte hardware has only one density.
+The
 .Tn EXB-8500
-drive, when released, will have a high
-density format of
-.Tn 5.6GB .
+drive, when released, will have a high density format of 5.6GB.
 On an Archive
 .Tn QIC-24
 drive the driver reads both
@@ -107,25 +107,27 @@
 .Ed
 .Pp
 Bit 4 in the minor device number is used
-to select long filemarks or short filemarks. A long filemark occupies
+to select long filemarks or short filemarks.
+A long filemark occupies
 2.12 MBytes of space on the tape, while a short filemark occupies 488 KBytes.
 A long filemark includes an erase gap while the short filemark does not.
 The tape can be positioned on the
 .Tn BOT
 side of a long filemark allowing
-data to be appended with a write operation.  Since the short filemark does not
-contain an erase gap which would allow writing it is considered to be
-non-erasable.  If either type of filemark is followed by blank tape,
+data to be appended with a write operation.
+Since the short filemark does not contain an erase gap which would allow
+writing it is considered to be non-erasable.
+If either type of filemark is followed by blank tape,
 data may be appended on its
 .Tn EOT
 side.
 .Pp
 Bit 5 in the minor device number selects fixed block mode with a block
-size of 1K.  Variable length records are the default if bit 5 is not
-set.
+size of 1K.
+Variable length records are the default if bit 5 is not set.
 .Pp
-For unit 0 here are the effects of minor device bits 2,3,4,5. For other
-units add the
+For unit 0 here are the effects of minor device bits 2,3,4,5.
+For other units add the
 .Em unit#
 to each of the device names.
 .Bl -column norewind density filemarks -offset indent
@@ -162,24 +164,26 @@
 .Tn SCSI
 controller hardware can not do odd length
 .Tn DMA
-transfers.  If odd length
+transfers.
+If odd length
 .Tn DMA I/O
 is requested the driver will use the
 "Program Transfer Mode" of the Fujitsu
 .Tn MB87030
-chip. Read requests are
-normally even length for which a
+chip.
+Read requests are normally even length for which a
 .Tn DMA
-transfer is used. If, however, the
-driver detects that an odd length read has happened (when an even length
-was requested) it will issue the
+transfer is used.
+If, however, the driver detects that an odd length read has happened
+(when an even length was requested) it will issue the
 .Dv EIO
 error and the last byte of the read
-data will be 0x00. Odd length read requests must match the size of the
+data will be 0x00.
+Odd length read requests must match the size of the
 requested data block on tape.
 .Pp
-The following only applies when using long filemarks. Short filemarks can
-not be overwritten.
+The following only applies when using long filemarks.
+Short filemarks can not be overwritten.
 .Bd -filled -offset 4n
 Due to the helical scan and the erase mechanism, there is a writing
 limitation on Exabyte drives.
@@ -188,11 +192,20 @@
 .Dq Li tar u
 will not work
 .Pf ( Dq Li tar c
-is ok).  One can only start writing at  1) beginning of tape, 2) on the
-end of what was last written, 3) "front" side of a regular (long) filemark.
-For example, you have a tape with 3 tar files. If you want to save the first
-file, but overwrite the second two files with new data, on a normal
-1/4" or 1/2" drive you would do:
+is ok).
+One can only start writing at
+.Bl -enum
+.It
+beginning of tape,
+.It
+on the end of what was last written,
+.It
+"front" side of a regular (long) filemark.
+.El
+.Pp
+For example, you have a tape with 3 tar files.
+If you want to save the first file, but overwrite the second two files
+with new data, on a normal 1/4" or 1/2" drive you would do:
 .Pp
 .Li "mt fsf 1; tar cf /dev/nrst0 ..."
 .Pp
@@ -201,29 +214,34 @@
 .Li "mt fsf 1; mt bsf 1; mt weof 1; tar cf /dev/nrst0 ..."
 .Pp
 The regular long filemark consists of an erased zone 3.8" long
-(needed to begin a write).  In this case, the first filemark is
+(needed to begin a write).
+In this case, the first filemark is
 rewritten in place, which creates an erased zone
 .Em after
 it, clearing the
-way to write more on the tape.  The erase head is not helical.
+way to write more on the tape.
+The erase head is not helical.
 .Pp
 One can position a tape to the end of what was last written by reading
 until a
-.Tn \*qBLANK CHECK\*q
-error is returned.  Writing can be started at this
-point.  (This applies to both long and short filemarks.)  The tape does
-not become positioned somewhere down the "erased" area as does a
-conventional magtape.  One can issue multiple reads at the
-.Tn \*qBLANK CHECK\*q
+.Dq Tn BLANK CHECK
+error is returned.
+Writing can be started at this point.
+(This applies to both long and short filemarks.)
+The tape does not become positioned somewhere down the "erased" area
+as does a conventional magtape.
+One can issue multiple reads at the
+.Dq Tn BLANK CHECK
 error, but the Exabyte stays positioned at the beginning of the
-blank area, ready to accept write commands.  File skip operations do
-not stop at blank tape and will run into old data or run to the end of
-the tape, so you have to be careful not to
+blank area, ready to accept write commands.
+File skip operations do not stop at blank tape and will run into old
+data or run to the end of the tape, so you have to be careful not to
 .Dq Li mt fsf too_many .
 .Ed
 .Pp
 Archive support gets confused if asked to moved more filemarks than there are
 on the tape.
 .Pp
-This man page needs some work.  Some of these are not really bugs,
+This man page needs some work.
+Some of these are not really bugs,
 just unavoidable consequences of the hardware.