dsb Update rpm-faq with notes on package structure and uses.

diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex
index 368a3ea666787197dc9bb726c58632929b8a2150..ca0b4c3f063e132cd0ed859970688c0d43e3df2b 100644 (file)
--- a/docs/manual/rpm-faq.tex
+++ b/docs/manual/rpm-faq.tex
@@ -28,6 +28,8 @@
    \ilink{Is there an easier way than sorting out all these command line options?}{faq7}
 \item 
    \ilink{I just upgraded from 1.36.x to 1.38.x and now my director daemon won't start. It appears to start but dies silently and I get a "connection refused" error when starting the console. What is wrong?}{faq8}  
+\item 
+   \ilink{There are a lot of rpm packages. Which packages do I need for what?}{faq9}  
 \end{enumerate}
 
 \section{Answers}
@@ -216,6 +218,11 @@ creation of debug rpm packages is:
 
 Further, if you are using File storage volumes rather than tapes those files will also need to have ownership set to user bacula and group bacula.
 
+\item 
+   \label{faq9}
+   {\bf There are a lot of rpm packages. Which packages do I need for what?} For a bacula server you need to select the packsge based upon your preferred catalog database: one of bacula-mysql, bacula-postgresql or bacula-sqlite.  If your system does not provide an mtx package you also need bacula-mtx to satisfy that dependancy.  For a client machine you need only install bacula-client.  Optionally, for either server or client machines, you may install a graphical console bacula-gconsole and/or bacula-wxconsole. One last package, bacula-updatedb is required only when upgrading a server more than one database revision level.
+
+
 
 \item {\bf Support for RHEL3/4, CentOS 3/4 and x86\_64}
    The examples below show