-<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
-or may not also be the tape server) named
-<filename>/etc/amandapass</filename>
-with share names, (clear text) passwords and (optional) domain names,
-in that order, one per line, whitespace separated.
-By default, the user used to connect to the PC is the same for all
-PC's and is compiled into &A;.
-It may be changed on a host by host basis
-by listing it first in the password field followed
-by a percent sign and then the password.
-For instance:</para>