Update

[bacula/docs] / docs / manual / requirements.tex

diff --git a/docs/manual/requirements.tex b/docs/manual/requirements.tex
index 208aaca0d9c9fcc6ea535f8421f02f647c280c1c..2038cfe5208902c64f85cf1aaf12c482eb9e94ca 100644 (file)
--- a/docs/manual/requirements.tex
+++ b/docs/manual/requirements.tex
@@ -7,28 +7,30 @@
 \index[general]{Requirements!System }
 
 \begin{itemize}
-\item {\bf Bacula} has been compiled and run on Red Hat Linux, FreeBSD, and
+\item {\bf Bacula} has been compiled and run on OpenSuSE Linux, FreeBSD, and
    Solaris systems. 
 \item It requires GNU C++ version 2.95 or higher to compile. You can try  with
    other compilers and older versions, but you are on your own.  We have
-   successfully compiled and used Bacula on RH8.0/RH9/RHEL 3.0/FC3  with GCC 3.4.
-Note, in general GNU C++ is a separate package (e.g.  RPM) from GNU C, so you
-need them both loaded. On Red Hat systems, the C++ compiler is part of the
-{\bf gcc-c++} rpm package. 
-\item There are certain third party packages that Bacula needs.  Except for
+   successfully compiled and used Bacula using GNU C++ version 4.1.3.
+   Note, in general GNU C++ is a separate package (e.g.  RPM) from GNU C, so you
+   need them both loaded. On Red Hat systems, the C++ compiler is part of the
+   {\bf gcc-c++} rpm package. 
+\item There are certain third party packages that Bacula may need.  Except for
    MySQL and PostgreSQL, they can all be found in the  {\bf depkgs} and {\bf
-   depkgs1} releases. 
-\item If you want to build the Win32 binaries, you will need a  Microsoft
-   Visual C++ compiler (or Visual Studio).  Although all components build
-   (console has  some warnings), only the File daemon has been tested. 
+   depkgs1} releases. However, most current Linux and FreeBSD systems
+   provide these as system packages.
+\item If you want to build the Win32 binaries, please see the
+   README.mingw32 file in the src/win32 directory. We cross-compile the
+   Win32 release on Linux. We provide documentation on building the Win32
+   version, but due to the complexity, you are pretty much on your own
+   if you want to build it yourself.
 \item {\bf Bacula} requires a good implementation of pthreads to work.  This
    is not the case on some of the BSD systems. 
 \item The source code has been written with portability in mind and is  mostly
    POSIX compatible. Thus porting to any POSIX compatible  operating system
    should be relatively easy. 
-\item The GNOME Console program is developed and tested under GNOME 2.x. It 
-   also runs under GNOME 1.4 but this version is deprecated and  thus no longer
-   maintained. 
+\item The GNOME Console program is developed and tested under GNOME 2.x.
+   GNOME 1.4 is no longer supported.
 \item The wxWidgets Console program is developed and tested with the latest 
    stable ANSI or Unicode version of 
    \elink{wxWidgets}{http://www.wxwidgets.org/} (2.6.1).  It works fine with the
@@ -44,8 +46,13 @@ need them both loaded. On Red Hat systems, the C++ compiler is part of the
    loaded (libtermcap-devel or ncurses-devel). 
 \item If you want to use DVD as backup medium, you will need to download the
    \elink{dvd+rw-tools 5.21.4.10.8}{http://fy.chalmers.se/~appro/linux/DVD+RW/},
-   apply the \elink{patch}{http://cvs.sourceforge.net/viewcvs.py/*checkout*/bacula/bacula/patches/dvd+rw-tools-5.21.4.10.8.bacula.patch}
+   apply the patch that is in the {\bf patches} directory of the main
+   source tree
    to make these tools compatible with Bacula, then compile and install them.
-   Do not use the dvd+rw-tools provided by your distribution, they will not work
-   with Bacula.
+   There is also a patch for dvd+rw-tools version 6.1, and we hope that the
+   patch is integrated into a later version.
+   Do not use the dvd+rw-tools provided by your distribution, unless you
+   are sure it contains the patch. dvd+rw-tools without the patch will not
+   work with Bacula. DVD media is not recommended for serious or important
+   backups because of its low reliability.
 \end{itemize}