latex2html -split 4 -local_icons -t "Developer's Guide" -long_titles 4 \
-contents_in_nav -toc_stars -white -notransparent ${DOC} >tex.out 2>&1
./translate_images.pl --to_meaningful_names ${DOC}/Developer*Guide.html
- @cp -f ${DOC}/Developers_Guide.html ${DOC}/index.html
+ @cp -f ${DOC}/Developer_s_Guide.html ${DOC}/index.html
@rm -f *.eps *.gif *.jpg ${DOC}/*.eps *.old
@rm -f ${DOC}/idle.png
@rm -f ${DOC}/win32-*.png ${DOC}/wx-console*.png ${DOC}/xp-*.png
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