-<para><programlisting>YYYYMMDD label flags
-</programlisting></para>
-
-<para>Where
-<emphasis remap='I'>YYYYMMDD</emphasis>
-is the date the tape was written,
-<emphasis remap='I'>label</emphasis>
-is a label for the tape as written by
-<emphasis remap='B'>amlabel</emphasis>
-and
-<emphasis remap='I'>flags</emphasis>
-tell &A; whether the tape may be reused, etc (see the
-<emphasis remap='B'>reuse</emphasis>
-options of
-<emphasis remap='B'>amadmin</emphasis>).</para>
-
-<para><emphasis remap='B'>Amdump</emphasis>
-and
-<emphasis remap='B'>amflush</emphasis>
-will refuse to write to an unlabeled tape, or to a labeled tape that is considered active.
-There must be more tapes in active rotation (see the
-<emphasis remap='B'>tapecycle</emphasis>
-option) than there are runs in the backup cycle (see the
-<emphasis remap='B'>dumpcycle</emphasis>
-option) to prevent overwriting a backup image that would be needed to do a full recovery.</para>
-</refsect1>
-
-<refsect1 id='output_drivers'><title>OUTPUT DRIVERS</title>
-<para>The normal value for the
-<emphasis remap='B'>tapedev</emphasis>
-parameter, or for what a tape changer returns,
-is a full path name to a non-rewinding tape device, such as
-<filename>/dev/nst0</filename>
-or
-<filename>/dev/rmt/0mn</filename>
-or
-<filename>/dev/nst0.1</filename>
-or whatever conventions the operating system uses. &A; provides additional application level drivers that
-support non-traditional tape-simulations or features. To access a specific output driver, set
-<emphasis remap='B'>tapedev</emphasis>
-(or configure your changer to return) a string of the form
-<emphasis remap='I'>driver</emphasis>:<emphasis remap='I'>driver-info</emphasis>
-where
-<emphasis remap='I'>driver</emphasis>
-is one of the supported drivers and
-<emphasis remap='I'>driver-info</emphasis>
-is optional additional information needed by the driver.</para>
-
-<para>The supported drivers are:</para>
-<variablelist remap='TP'>
- <varlistentry>
- <term><emphasis remap='I'>tape</emphasis></term>
- <listitem>
-<para>This is the default driver.
-The
-<emphasis remap='I'>driver-info</emphasis>
-is the tape device name.
-Entering
-<programlisting>tapedev /dev/rmt/0mn
-</programlisting>
-is really a short hand for
-<programlisting>tapedev tape:/dev/rmt/0mn
-</programlisting></para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis remap='I'>null</emphasis></term>
- <listitem>
-<para>This driver throws away anything written to it and returns EOF
-for any reads except a special case is made for reading a label,
-in which case a "fake" value is returned that &A; checks for
-and allows through regardless of what you have set in
-<emphasis remap='B'>labelstr</emphasis>.
-The
-<emphasis remap='I'>driver-info</emphasis>
-field is not used and may be left blank:</para>
-
-<para><programlisting>tapedev null:
-</programlisting></para>
-
-<para>The <emphasis remap='I'>length</emphasis>
-value from the associated
-<emphasis remap='B'>tapetype</emphasis>
-is used to limit the amount of data written. When the limit is reached, the driver will simulate end of tape.</para>
-
-<note><para>This driver should only be used for debugging and testing,
-and probably only with the
-<emphasis remap='B'>record</emphasis>
-option set to
-<emphasis remap='I'>no</emphasis>.
-</para>
-</note>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis remap='I'>rait</emphasis></term>
- <listitem>
-<para><emphasis remap='I'>R</emphasis>edundant
-<emphasis remap='I'>A</emphasis>rray
-of
-<emphasis remap='I'>I</emphasis>nexpensive (?)
-<emphasis remap='I'>T</emphasis>apes.
-Reads and writes tapes mounted on multiple drives by spreading
-the data across N-1 drives and using the last drive for a checksum.
-See docs/RAIT for more information.</para>
-
-<para>The
-<emphasis remap='I'>driver-info</emphasis>
-field describes the devices to use. Curly braces indicate multiple replacements in the string.
-For instance:</para>
-
-<para><programlisting>tapedev rait:/dev/rmt/tps0d{4,5,6}n
-</programlisting></para>
-
-<para>would use the following devices:</para>
-
-<para><filename>/dev/rmt/tps0d4n</filename>
-<filename>/dev/rmt/tps0d5n</filename>
-<filename>/dev/rmt/tps0d6n</filename>
-</para>
- </listitem>
- </varlistentry>
-</variablelist>
-<variablelist remap='TP'>
- <varlistentry>
- <term><emphasis remap='I'>file</emphasis></term>
- <listitem>
-<para>This driver emulates a tape device with a set of files in a directory.
-The
-<emphasis remap='I'>driver-info</emphasis>
-field must be the name of an existing directory.
-The driver will test for a subdirectory of that named
-<emphasis remap='I'>data</emphasis>
-and return
-<emphasis remap='B'>offline</emphasis>
-until it is present.
-When present, the driver uses two files in the
-<emphasis remap='I'>data</emphasis>
-subdirectory for each tape file. One contains the actual data.
-The other contains record length information.</para>
-
-<para>The driver uses a file named
-<emphasis remap='I'>status</emphasis>
-in the
-<emphasis remap='B'>file</emphasis>
-device directory to hold driver status information, such as tape position.
-If not present, the driver will create it as though the device is rewound.</para>
-
-<para>The
-<emphasis remap='I'>length</emphasis>
-value from the associated
-<emphasis remap='B'>tapetype</emphasis>
-is used to limit the amount of data written.
-When the limit is reached, the driver will simulate end of tape.</para>
-
-<para>One way to use this driver with a real device such as a CD-writer is to
-create a directory for the
-<emphasis remap='B'>file</emphasis>
-device and one or more other directories for the actual data.
-Create a symlink named
-<emphasis remap='I'>data</emphasis>
-in the
-<emphasis remap='B'>file</emphasis>
-directory to one of the data directories.
-Set the
-<emphasis remap='B'>tapetype</emphasis>
-length to whatever the medium will hold.</para>
-
-<para>When &A; fills the
-<emphasis remap='B'>file</emphasis>
-device, remove the symlink and (optionally) create a new symlink to another
-data area.
-Use a CD writer software package to burn the image from the first data area.</para>
-
-<para>To read the CD, mount it and create the
-<emphasis remap='I'>data</emphasis>
-symlink in the
-<emphasis remap='B'>file</emphasis>
-device directory.</para>
-</listitem>
-</varlistentry>
-</variablelist>
-</refsect1>
-
-<refsect1><title>AUTHORIZATION</title>
-<para>&A; processes on the tape server host run as the
-<emphasis remap='B'>dumpuser</emphasis>
-user listed in
-<emphasis remap='B'>amanda.conf</emphasis>.
-When they connect to a backup client, they do so with an &A;-specific protocol.
-They do not, for instance, use
-<emphasis remap='B'>rsh</emphasis>
-or
-<emphasis remap='B'>ssh</emphasis>
-directly.</para>
-
-<para>On the client side, the
-<emphasis remap='B'>amandad</emphasis>
-daemon validates the connection using one of several methods,
-depending on how it was compiled and on options it is passed:</para>
-
-<variablelist remap='IP'>
- <varlistentry>
- <term>.rhosts</term>
- <listitem>
-<para>Even though &A; does not use
-<emphasis remap='B'>rsh</emphasis>,
-it can use
-<markup>.rhosts</markup>-style
-authentication and a
-<markup>.rhosts</markup>
-file.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>.amandahosts</term>
- <listitem>
-<para>This is essentially the same as
-<markup>.rhosts</markup>
-authentication except a different file, with almost the same format, is used.
-This is the default mechanism built into &A;.</para>
-
-<para>The format of the
-<filename>.amandahosts</filename>
-file is:</para>
-
-<para><emphasis remap='I'>hostname</emphasis>
-[
-<emphasis remap='I'>username</emphasis>
-[
-<emphasis remap='I'>service</emphasis>
-]*]</para>
-
-<para>If
-<emphasis remap='I'>username</emphasis>
-is ommitted, it defaults to the user running
-<emphasis remap='B'>amandad</emphasis>,
-i.e. the user listed in the
-<emphasis remap='B'>inetd</emphasis>
-or
-<emphasis remap='B'>xinetd</emphasis>
-configuration file.</para>
-<para>The <emphasis remap='I'>service</emphasis> is a list of the service the client is authorized to execute:
-<emphasis remap='B'>amdump</emphasis>,
-<emphasis remap='B'>noop</emphasis>,
-<emphasis remap='B'>selfcheck</emphasis>,
-<emphasis remap='B'>sendsize</emphasis>,
-<emphasis remap='B'>sendbackup</emphasis>,
-<emphasis remap='B'>amindexd</emphasis>,
-<emphasis remap='B'>amidxtaped</emphasis>.
-<emphasis remap='B'>amdump</emphasis> is a shortcut for "noop selfcheck sendsize sendbackup"</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Kerberos</term>
- <listitem>
-<para>&A; may use the Kerberos authentication system.
-Further information is in the
-<emphasis remap='B'>docs/KERBEROS</emphasis>
-<!-- TODO: edit link -->
-file that comes with an &A; distribution.</para>
-
-<para>For Samba access,
-&A; needs a file on the Samba server (which may