Add 3.1.x files

[bacula/docs] / docs / manuals / en / install / installation.tex

diff --git a/docs/manuals/en/install/installation.tex b/docs/manuals/en/install/installation.tex
index f6a9349a0cda17a547b257b0d23d796dc928a859..66c8a5ce16ed82b12ccf3bebd2470d11cc6a4d85 100644 (file)
--- a/docs/manuals/en/install/installation.tex
+++ b/docs/manuals/en/install/installation.tex
@@ -80,7 +80,25 @@ them.
 
 If you are upgrading from one Bacula version to another, you should first
 carefully read the ReleaseNotes of all major versions between your current
-version and the version to which you are upgrading.  If the Bacula catalog
+version and the version to which you are upgrading.  In many upgrades,
+especially for minor patch upgrades (e.g. between 3.0.0 and 3.0.1) there
+will be no database upgrade, and hence the process is rather simple.
+
+With version 3.0.0 and later, you {\bf must} ensure that on any one
+machine that all components of Bacula are running on exactly the
+same version.  Prior to version 3.0.0, it was possible to run a 
+lower level FD with a newer Director and SD.  This is no longer the
+case.  
+
+As always, we attempt to support older File daemons. This avoids the
+need to do a simultaneous upgrade of many machines. For exactly what
+older versions of the FD are supported, please see the ReleaseNotes 
+for the new version.  In any case, you must always upgrade both the
+Director and the Storage daemon at the same time, and you must also
+upgrade any File daemon that is running on the same machine as a Director
+or a Storage daemon (see the prior paragraph).
+
+If the Bacula catalog
 database has been upgraded (as it is almost every major release), you will
 either need to reinitialize your database starting from scratch (not
 normally a good idea), or save an ASCII copy of your database, then proceed
@@ -693,15 +711,13 @@ customize your installation.
 \item [ {-}{-}enable-bat ]
    \label{enablebat}
    \index[general]{{-}{-}enable-bat}
-   If you have Qt4 >= 4.2 installed on your computer including the
+   If you have Qt4 >= 4.3 installed on your computer including the
    libqt4 and libqt4-devel (libqt4-dev on Debian) libraries, and you want
    to use the Bacula Administration Tool (bat) GUI Console interface to
    Bacula, you must specify this option.  Doing so will build everything in
    the {\bf src/qt-console} directory.  The build with enable-bat will work
    only with a full Bacula build (i.e. it will not work with a client-only
-   build).  In addition to the Qt4 libraries, linking bat requires
-   the qwt package installed on your system.  Please see the next
-   configure option (with-qwt) for how to build the qwt package.
+   build). 
 
    Qt4 is available on OpenSUSE 10.2, CentOS 5, Fedora, and Debian. If it
    is not available on your system, you can download the {\bf depkgs-qt}
@@ -713,8 +729,10 @@ customize your installation.
 
 \item [ {-}{-}with-qwt=\lt{}path\gt{} ]
   \index[general]{{-}{-}with-qwt}
-  To build bat, you need the qwt graphics package installed on
-  your system.  The path specified must be an absolute path and
+  The qwt package is a graphics library for Qt. If it is included
+  during the building of bat, you will get one extra graphical function.
+  At the current time, we recommend not including this option when
+  building bat. The path specified must be an absolute path and
   not relative.  
 
   The qwt package is available for download from
@@ -726,12 +744,12 @@ customize your installation.
  --with-qwt=/usr/lib/qwt-5.0.2
 \end{verbatim}
 
-  Alternatively, you can download the Bacula depkgs package (currently
-  version 11Jul07) and build it, then assuming that you have put it 
+  Alternatively, you can download the Bacula depkgs-qt package (currently
+  version 28Jul09) and build it, then assuming that you have put it 
   into a directory named bacula, you would specify:
 
 \begin{verbatim}
- --with-qwt=$HOME/bacula/depkgs/qwt
+ --with-qwt=$HOME/bacula/depkgs-qt/qwt
 \end{verbatim}
 
    Some packages such as Debian do not adhere to the standard of