#  FILE
#
#	brutab    bru data file for loadable device table
#
#
#  DESCRIPTION
#
#	Bru data file for loadable device table.
#	Note that the table MUST contain at least one entry and the
#	first entry is the default archive device.
#
#	Also, the table should contain an entry for the standard
#	input and output, with a name of "-".  This entry SHOULD NOT
#	be the first entry (or archives may be inadvertently written to
#	the user's terminal).
#
#	Entries consist of a device name field, followed by one
#	or more capabilities fields.  Entries may span more than
#	one line by escaping the newline at the end of the line with
#	a '\' character ('\' is last character on line before newline).
#	All whitespace (tabs, blanks, newlines, formfeeds) between fields
#	is ignored.
#
#	The device name field must be the first field in the entry and has
#	the following form:
#
#		<device name>|<device name>| ... |<device name>
#
#		ex:	/dev/rmt0|/dev/rmt1|/dev/rmt2
#
#	where each device has the same capabilities as the other devices
#	specified (a class of devices).
#
#	Each capability field is of the form:
#
#		<capability name>=<value>	or	<boolean flag>
#
#		ex:	size=640K   reopen  pwerr=EIO
#
#	Note that there can be no whitespace between the capability name
#	and the value.  Numeric values may be given in absolute form or
#	with a trailing scale factor of:
#
#		b or B		Blocks (512 bytes)
#		k or K		Kilobytes (1024 bytes)
#		m or M		Megabytes (1024 * 1024 bytes)
#
#======================================================================
#  These are sample entries for various systems.  Note that 
#  it is a good idea to underestimate the capacity slightly to allow for 
#  manufacturing variance in the tape length.  Underestimating only
#  wastes a small amount of tape.  Overestimating is generally very
#  bad news.  The actual achieved capacity can also depend upon
#  the buffer size (ratio of record size to interrecord gap changes).
#  Very large I/O buffer sizes may not work with double buffering,
#  and may even result in reduced throughput to the archive device.
#
#
#  ******************************
#  *** NOTE ABOUT TAPE SIZES ****
#  ******************************
#  
#  For some inexplicable reason, tape storage bytes are measured
#  differently than memory bytes.  For most tapes, a Kilobyte = 1000 bytes.
#  This is different than the normal memory Kilobyte of 1024 bytes.
#
#  When specifying media size, BRU assumes the normal Kilobyte size of
#  1024 bytes.  A Megabyte is 1024*1024 bytes, and a Gigabyte is
#  1024*1024*1024.
#
#  To use the manufacturer-specified size, use the 'T' modifier after
#  the 'K'(kilobytes) or 'M' (megabytes) size multiplier.
#
#  Listed below are some of the most common tape types, sizes and
#  typical maximum speeds for tape drives.  Please note that the
#  tape speeds may vary, you should check for manufacturer's specifications
#  for the maximum speed of your tape drive.
#
#
#                      MANUFACTURER               BRU          TYPICAL
#     TYPE   LENGTH     TAPE SIZE              MEDIA SIZE     MAX SPEED
#     ----   ------    ------------            ----------     ----------
#
#    DC600A   600 ft      60 MB                 size=60MT      90 KB/sec
#    DC6150   620 ft     150 MB                 size=150MT    100 KB/sec
#    DC6250  1020 ft     250 MB                 size=250MT    100 KB/sec
#    DC6525  1020 ft     525 MB                 size=525MT    200 KB/sec
#     4mm      60 m      1.3 GB                 size=1300MT   175 KB/sec
#     4mm      90 m      2.0 GB                 size=2000MT   175 KB/sec
#     8mm      54 m      2.0 GB (Exabyte 8200)  size=2000MT   200 KB/sec
#     8mm     112 m      2.3 GB (Exabyte 8200)  size=2300MT   200 KB/sec
#     8mm     112 m      5.0 GB (Exabyte 8500)  size=5000MT   500 KB/sec
#
####################################################################### 
#
# Note that this file should have device entries below this point.  If
# there is no further data below, please refer to the brutab chapter
# in your BRU manual.
#
######################################################################

