From d2ab7576fa48e8994d93f7e5e3e8ef76952949b7 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Sat, 23 Feb 2008 14:05:01 +0000 Subject: [PATCH] Add new doc --- docs/manuals/en/install/installation.tex | 36 ++++++++++++++++-------- 1 file changed, 24 insertions(+), 12 deletions(-) diff --git a/docs/manuals/en/install/installation.tex b/docs/manuals/en/install/installation.tex index 953fa440..f6a9349a 100644 --- a/docs/manuals/en/install/installation.tex +++ b/docs/manuals/en/install/installation.tex @@ -27,17 +27,17 @@ them. the Bacula SVN. The released files are: \begin{description} -\item [bacula-2.0.3.tar.gz] +\item [bacula-2.2.8.tar.gz] This is the primary source code release for Bacula. On each - release the version number (2.0.3) will be updated. + release the version number (2.2.8) will be updated. -\item [bacula-docs-2.0.3.tar.gz] +\item [bacula-docs-2.2.8.tar.gz] This file contains a copy of the docs directory with the documents prebuild. English HTML directory, single HTML file, and pdf file. The French and German translations are in progress, but are not built. -\item [bacula-gui-2.0.3.tar.gz] +\item [bacula-gui-2.2.8.tar.gz] This file contains the non-core GUI programs. Currently, it contains bacula-web, a PHP program for producing management viewing of your Bacula job status in a browser; and bimagemgr @@ -51,14 +51,18 @@ them. linked version of the File daemon. This can permit you to easily repartition and reformat your hard disks and reload your system with Bacula in the case of a hard disk failure. + Unfortunately this rescue disk does not properly boot for + all Linux distributions. The problem is that the boot procedure + can vary significantly between distributions, and even within + a distribution, they are a moving target. - Note, this package evolves slower than the Bacula source code, + This package evolves slower than the Bacula source code, so there may not always be a new release of the rescue package when making minor updates to the Bacula code. For example, when releasing - Bacula version 2.0.3, the rescue package may still be at version + Bacula version 2.2.8, the rescue package may still be at version 2.0.0 if there were no updates. -\item [winbacula-2.0.3.exe] +\item [winbacula-2.2.8.exe] This file is the 32 bit Windows installer for installing the Windows client (File daemon) on a Windows machine. This client will also run on 64 bit Windows machines. @@ -109,8 +113,8 @@ protocol will change. However, within any particular release (e.g. version change. If this is confusing, simply read the ReleaseNotes very carefully as they will note if all daemons must be upgraded at the same time. -Finally, please note that in general it is not necessary to do a -{\bf make uninstall} before doing an upgrade providing you are careful +Finally, please note that in general it is not necessary or desirable +to do a {\bf make uninstall} before doing an upgrade providing you are careful not to change the installation directories. In fact, if you do so, you will most likely delete all your conf files, which could be disastrous. The normal procedure during an upgrade is simply: @@ -494,7 +498,7 @@ CFLAGS="-g -Wall" \ \end{verbatim} \normalsize -Note, the advantage of using the above configuration to start is that +The advantage of using the above configuration to start is that everything will be put into a single directory, which you can later delete once you have run the examples in the next chapter and learned how Bacula works. In addition, the above can be installed and run as non-root. @@ -534,7 +538,7 @@ export LDFLAGS="-L/usr/lib/termcap" The same library requirements apply if you wish to use the readline subroutines for command line editing and history or - if you are using a MySQL library that requires encryption. If you need encryption, +if you are using a MySQL library that requires encryption. If you need encryption, you can either export the appropriate additional library options as shown above or, alternatively, you can include them directly on the ./configure line as in: @@ -629,6 +633,15 @@ The following command line options are available for {\bf configure} to customize your installation. \begin{description} +\item [ {-}prefix=\lt{}patch\gt{}] + \index[general]{{-}prefix} + This option is meant to allow you to direct where the architecture + independent files should be placed. However, we find this a somewhat + vague concept, and so we have not implemented this option other than + what ./configure does by default. As a consequence, we suggest that + you avoid it. We have provided options that allow you to explicitly + specify the directories for each of the major categories of installation + files. \item [ {-}{-}sbindir=\lt{}binary-path\gt{}] \index[general]{{-}{-}sbindir} Defines where the Bacula binary (executable) files will be placed during a @@ -1298,7 +1311,6 @@ or finally, a completely traditional Red Hat Linux install: \footnotesize \begin{verbatim} CFLAGS="-g -Wall" ./configure \ - --prefix=/usr \ --sbindir=/usr/sbin \ --sysconfdir=/etc/bacula \ --with-scriptdir=/etc/bacula \ -- 2.39.5