Tweak rpm manual

diff --git a/docs/manuals/en/utility/rpm-faq.tex b/docs/manuals/en/utility/rpm-faq.tex
index e0d89071840d4237a86880a5f2cd4cb79f9c9c47..2e66285e865446894e923e76eb836a41e6e1a6f9 100644 (file)
--- a/docs/manuals/en/utility/rpm-faq.tex
+++ b/docs/manuals/en/utility/rpm-faq.tex
@@ -127,7 +127,7 @@ in the spec file directly or pass it to rpmbuild on the command line:
 
 \item 
    \label{faq3}
-   {\bf What other defines are used?}
+   {\bf What other defines are used?} \\
    Three other building defines of note are the depkgs\_version, docs\_version and
    \_rescuever identifiers. These  two defines are set with each release and must 
    match the version of those sources that are being used to build the packages. 
@@ -136,7 +136,7 @@ in the spec file directly or pass it to rpmbuild on the command line:
 \item 
    \label{faq4}
    {\bf I'm getting errors about not having permission when I try  to build the
-   packages. Do I need to be root?}
+   packages. Do I need to be root?} \\
    No, you do not need to be root and, in fact, it is better practice to
    build rpm packages as a non-root user.  Bacula packages are designed to
    be built by a regular user but you must make a few changes on your
@@ -185,41 +185,45 @@ creation of debug rpm packages is:
 \item 
    \label{faq5}
    {\bf I'm building my own rpms but on all platforms and compiles I get an
-   unresolved dependency for something called /usr/afsws/bin/pagsh.} This
-   is a shell from the OpenAFS (Andrew File System).  If you are seeing
-   this then you chose to include the docs/examples directory in your
-   package.  One of the example scripts in this directory is a pagsh
+   unresolved dependency for something called /usr/afsws/bin/pagsh.} \\
+   This is a shell from the OpenAFS (Andrew File System).  If you are
+   seeing this then you chose to include the docs/examples directory in
+   your package.  One of the example scripts in this directory is a pagsh
    script.  Rpmbuild, when scanning for dependencies, looks at the shebang
    line of all packaged scripts in addition to checking shared libraries.
-   To avoid this do not package the examples directory. If you are seeing this 
-   problem you are building a very old bacula package as the examples have been 
-   removed from the doc packaging.
+   To avoid this do not package the examples directory.  If you are seeing
+   this problem you are building a very old bacula package as the examples
+   have been removed from the doc packaging.
 
 \item 
    \label{faq6}
    {\bf I'm building my own rpms because you don't publish for my platform.
-    Can I get my packages released to sourceforge for other people to use?} Yes, 
-    contributions from users are accepted and appreciated. Please examine the 
-    directory platforms/contrib-rpm in the source code for further information.
+    Can I get my packages released to sourceforge for other people to use?}
+    \\
+    Yes, contributions from users are accepted and appreciated.  Please
+    examine the directory platforms/contrib-rpm in the source code for
+    further information.
 
 \item 
    \label{faq7}
-   {\bf Is there an easier way than sorting out all these command line options?} Yes, 
-    there is a gui wizard shell script which you can use to rebuild the src rpm package. 
-   Look in the source archive for platforms/contrib-rpm/rpm\_wizard.sh. This script will 
-   allow you to specify build options using GNOME dialog screens. It requires zenity.
+   {\bf Is there an easier way than sorting out all these command line options?}
+   \\
+   Yes, there is a gui wizard shell script which you can use to rebuild the
+   src rpm package.  Look in the source archive for
+   platforms/contrib-rpm/rpm\_wizard.sh.  This script will allow you to
+   specify build options using GNOME dialog screens.  It requires zenity.
 
 \item 
    \label{faq8}
    {\bf 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?} Beginning with
-1.38 the rpm packages are configured to run the director and storage
-daemons as a non-root user.  The file daemon runs as user root and group
-bacula, the storage daemon as user bacula and group disk, and the director
-as user bacula and group bacula.  If you are upgrading you will need to
-change some file permissions for things to work.  Execute the following
-commands as root:
+refused" error when starting the console.  What is wrong?} \\
+   Beginning with 1.38 the rpm packages are configured to run the director
+   and storage daemons as a non-root user.  The file daemon runs as user
+   root and group bacula, the storage daemon as user bacula and group disk,
+   and the director as user bacula and group bacula.  If you are upgrading
+   you will need to change some file permissions for things to work.
+   Execute the following commands as root:
 
 \footnotesize
 \begin{verbatim}
@@ -236,7 +240,8 @@ 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
+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
@@ -249,6 +254,7 @@ upgrading a server more than one database revision level.
 
 
 \item {\bf Support for RHEL3/4/5, CentOS 3/4/5, Scientific Linux 3/4/5 and x86\_64}
+   \\
    The examples below show
    explicit build support for RHEL4 and CentOS 4. Build support 
    for x86\_64 has also been added.