Tweak Bacula restrictions

diff --git a/docs/manuals/en/main/state.tex b/docs/manuals/en/main/state.tex
index 3312e2f51b6e268b152e0771093a6a4503deb688..a9b37c94c5d8b0e9588b599dc0b84f6d580c1706 100644 (file)
--- a/docs/manuals/en/main/state.tex
+++ b/docs/manuals/en/main/state.tex
@@ -212,6 +212,8 @@ In other words, what is and what is not currently implemented and functional.
    two jobs in the same restore if the Jobs' data blocks were
    intermixed on the backup medium. The problem is resolved by
    simply doing two restores, one for each Job. 
+   Normally this can happen only if you manually enter specific
+   JobIds to be restored in a single restore Job.
 \item Bacula can generally restore any backup made from one client
    to any other client. However, if the architecture is significantly
    different (i.e. 32 bit architecture to 64 bit or Win32 to Unix),
@@ -232,6 +234,18 @@ In other words, what is and what is not currently implemented and functional.
    this does not apply to filenames, which may be arbitrarily long.
 \item Command line input to some of the stand alone tools -- e.g. btape,
    bconsole is restricted to several hundred characters maximum.
+   Normally, this is not a restriction, except in the case of listing
+   multiple Volume names for programs such as {\bf bscan}. To avoid
+   this command line length restriction, please use a {\bf .bsr} 
+   file to specify the Volume names.
+\item Bacula configuration files for each of the components can be
+   any length. However, the length of an individual line is limited
+   to 500 characters after which it is truncated.  If you need lines
+   longer than 500 characters for directives such as ACLs where
+   they permit a list of names are character strings simply
+   specify multiple short lines repeating the directive on
+   each line but with different list values.
+
 \end{itemize}
 
 \section{Items to Note}

diff --git a/docs/manuals/en/main/supporteddrives.tex b/docs/manuals/en/main/supporteddrives.tex
index 73f0759943d05e5ce525c3329ee0a7b67774fefe..5eda0d249ea47dedbb72830916f4deb69630a361 100644 (file)
--- a/docs/manuals/en/main/supporteddrives.tex
+++ b/docs/manuals/en/main/supporteddrives.tex
@@ -10,7 +10,8 @@ Bacula uses standard operating system calls (read, write, ioctl) to
 interface to tape drives.  As a consequence, it relies on having a
 correctly written OS tape driver. Bacula is known to work perfectly well
 with SCSI tape drivers on FreeBSD, Linux, Solaris, and Windows machines,
-and it may work on other *nix machines, but we have not tested it.
+and it may work on other *nix machines.
+
 Recently there are many new drives that use IDE, ATAPI, or
 SATA interfaces rather than SCSI. On Linux the OnStream drive, which uses
 the OSST driver is one such
@@ -24,6 +25,10 @@ is a good chance that it will not work. We are working with the kernel
 developers to rectify this situation, but it will not be resolved in the 
 near future.
 
+Generally any modern tape drive (i.e. after 2010) will work out
+of the box with Bacula using the standard Bacula Device specification
+in the bacula-sd.conf file.
+
 Even if your drive is on the list below, please check the 
 \ilink{Tape Testing Chapter}{btape1} of this manual for
 procedures that you can use to verify if your tape drive will work with