From: Kern Sibbald <kern@sibbald.com>
Date: Fri, 4 Nov 2005 18:26:00 +0000 (+0000)
Subject: Update home page -- donations
X-Git-Tag: Release-1.38.1~40
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=90b5377115e409c4c4c5cb091bcf03d6c05c6424;p=bacula%2Fdocs

Update home page -- donations
---

diff --git a/docs/home-page/donations.txt b/docs/home-page/donations.txt
new file mode 100644
index 00000000..739e0173
--- /dev/null
+++ b/docs/home-page/donations.txt
@@ -0,0 +1,45 @@
+Kern;;;2005/11/02;;;12:30 
+Bacula is now able to accept direct donations, and as of
+02 November 2005, we have received the following:
+
+      Amount:      Donor: 
+       $ 50         Ludovic Strappazon         
+       $100         Pontis Corporation, Pavlo Tabashov
+       $ 20         Jan Kesten
+       $100         Ulrich Schaefer
+       $442         GDC A Kendall, Dominic Marks
+
+Total  $682.73      After PayPal fees are deducted 
+
+Many thanks to these Bacula supporters.
+
+;;;
+
+Kern;;;2005/09/28;;;16:30 
+Results to date of donations to EFF for the Data Encryption project
+28 October 2005
+      Donor:                  Amount:
+        WingNET Internet        $500 
+        Timo Neuvonen           $250
+        Ed Grether              $25
+        Charles Reinehr         $100
+        Michael Proto           $25
+        Phil Cordier            $100
+        Dan Langille            $100
+        Tom Plancon             $65
+        Felix Schwarz           $60
+        ClarkConnect            $500    
+        Andrew Ford             $25
+        INetU, Inc              $1000
+        Jo at Winfix.it         $70
+      Goal: $3000        Total: $2,820
+
+Additional information is available from Landon at:
+
+ http://landonf.bikemonkey.org/code/bacula
+
+Read on for details of the project, which is now partially
+implemented and being worked on by Landon in the Branch-1_38-encryption 
+branch of the Bacula CVS.
+
+;;;
diff --git a/docs/home-page/inc/footer.php b/docs/home-page/inc/footer.php
index a5ffd3e7..286806ac 100644
--- a/docs/home-page/inc/footer.php
+++ b/docs/home-page/inc/footer.php
@@ -1,11 +1,10 @@
-		<div>
-			<img src="images/spacer.gif" alt="spacer" width="1px" height="50px"><br>
-			<?
-			if($_SESSION['user'] == "bukdebug")
-				print_r($_SERVER);
-			?>
-		</div>
-	</div>
-	</body>
+         <div>
+            <img src="images/spacer.gif" alt="spacer" width="1px" height="50px"><br>
+              <?
+               if($_SESSION['user'] == "bukdebug")
+                  print_r($_SERVER);
+              ?>
+         </div>
+      </div>
+   </body>
 </html>
-
diff --git a/docs/home-page/inc/header.php b/docs/home-page/inc/header.php
index 8ef7ddaa..3907d46c 100644
--- a/docs/home-page/inc/header.php
+++ b/docs/home-page/inc/header.php
@@ -73,21 +73,21 @@
 
    <!-- Logo Bar -->
    <div class="pageLogo">
-           <table class="pageLogo">
-           <tr>
-                   <td style="text-align: left; vertical-align: middle">
-                           <img alt="Bacula Logo" src="images/bacu_logo-red.jpg">
-                   </td>
-           </tr>
-           </table>
+       <table class="pageLogo">
+         <tr>
+           <td style="text-align: left; vertical-align: middle">
+               <img alt="Bacula Logo" src="images/bacu_logo-red.jpg">
+           </td>
+         </tr>
+       </table>
    </div>
 
    <!-- User Bar - if logged in -->
    <?
    if($_SESSION['logged_in']) {
-           printf('<div class="userBar">');
-           printf('Welcome %s, <a style="color: white; text-decoration: none" href="/?page=logout">logout here</a>.', $_SESSION['user']);
-           printf('</div>');
+      printf('<div class="userBar">');
+      printf('Welcome %s, <a style="color: white; text-decoration: none" href="/?page=logout">logout here</a>.', $_SESSION['user']);
+      printf('</div>');
    }
    ?>
 
@@ -105,13 +105,6 @@
            <li class="menuItem"> <a href="dev-manual/Bacula_Copyri_Tradem_Licens.html"> License </a> </li>
            <li class="menuItem"> <a href="<? echo $spath ?>/?page=testimonials"> Testimonials</a> </li>
            <li class="menuItem"> <a href="http://sourceforge.net/projects/bacula"> SF Project Page </a> </li>
-           </ul>
-        </div>
-
-        <!-- Hardware -->
-        <div class="menuHead"> Hardware </div>
-        <div class="menuItem">
-           <ul class="menuitem">
            <li class="menuItem"> <a href="dev-manual/System_Requirements.html"> Requirements </a> </li>
            <li class="menuItem"> <a href="dev-manual/Supported_Operating_Systems.html"> Operating&nbsp;Systems </a> </li>
            <li class="menuItem"> <a href="dev-manual/Supported_Tape_Drives.html"> Tapedrives </a> </li>
@@ -123,11 +116,11 @@
         <div class="menuHead"> Support </div>
         <div class="menuItem">
            <ul class="menuitem">
-           <li class="menuItem"> <a href="<? echo $spath ?>/?page=bugs"> Bug Reports </a> </li>
-           <li class="menuItem"> <a href="<? echo $spath ?>/?page=donations"> Donations </a> </li>
+           <li class="menuItem"> <a href="<? echo $spath ?>/?page=support"> Getting Support </a> </li>
            <li class="menuItem"> <a href="<? echo $spath ?>/?page=maillists"> Email Lists </a> </li>
-           <li class="menuItem"> <a href="<? echo $spath ?>/?page=support"> Where & How </a> </li>
+           <li class="menuItem"> <a href="<? echo $spath ?>/?page=bugs"> Bug Reports </a> </li>
            <li class="menuItem"> <a href="<? echo $spath ?>/?page=professional"> Professional </a></li>
+           <li class="menuItem"> <a href="<? echo $spath ?>/?page=rfc"> Feature Requests </a></li>
            </ul>
         </div>
 
@@ -140,6 +133,16 @@
            </ul>
         </div>
 
+        <!-- Donations -->
+        <div class="menuHead"> Donations </div>
+        <div class="menuItem">
+           <ul class="menuitem">
+           <li class="menuItem"> <a href="<? echo $spath ?>/?page=makedonation"> Make a Donation </a> </li>
+           <li class="menuItem"> <a href="<? echo $spath ?>/?page=donations"> Donations Received </a> </li>
+           </ul>
+        </div>
+
+
         <!-- Projects -->
         <!-- div class="menuHead"> Projects </div>
         <div class="menuItem">
diff --git a/docs/home-page/news.txt b/docs/home-page/news.txt
index 4ed47e7b..4390eede 100644
--- a/docs/home-page/news.txt
+++ b/docs/home-page/news.txt
@@ -1,43 +1,216 @@
-Kern;;;2005/10/31;;;12:30 
-Bacula is now able to accept direct donations, and as of
-31 October 2005, we have received the following:
-
-      Amount:      Donor: 
-       $ 50         Ludovic Strappazon         
-       $100         Pontis Corporation, Pavlo Tabashov
-       $ 20         Jan Kesten
-       $100         Ulrich Schaefer
-
-Total  $258.27      After PayPal fees are deducted 
-
-Many thanks to these Bacula supporters.
+Kern;;;2005/10/31;;;14:30
+The Bacula Version 1.36.3 tar file is released to Source Forge.
 
-Kern;;;2005/09/28;;;16:30 
-Results to date of donations to EFF for the Data Encryption project
-28 October 2005
-      Donor:                  Amount:
-        WingNET Internet        $500 
-        Timo Neuvonen           $250
-        Ed Grether              $25
-        Charles Reinehr         $100
-        Michael Proto           $25
-        Phil Cordier            $100
-        Dan Langille            $100
-        Tom Plancon             $65
-        Felix Schwarz           $60
-        ClarkConnect            $500    
-        Andrew Ford             $25
-        INetU, Inc              $1000
-        Jo at Winfix.it         $70
-      Goal: $3000        Total: $2,820
+          Release Notes for Bacula 1.38.0
+
+  Bacula code: Total files = 420 Total lines = 138,440 (*.h *.c *.in)
+  20,440 additional lines of code since version 1.36.3
+
+Major Changes:
+- Fixed out of order Volumes in restore.
+- Improved algorithm for reserving drives in multiple drive
+  autochangers. Autochange users MUST use the new Autochanger
+  resource in the Storage daemon.
+- There is a new database format that is not compatible
+  with previous databases. You must upgrade if converting
+  from 1.36.x. No changes from version 1.37.30.
+- The Director, Storage daemon, and File daemons are
+  Deamons are not compatible with prior versions. 
+  All FDs must be upgraded at the same time.
+- Support for ANSI/IBM labels.
+- Faster database inserts due to combining the MD5/SHA1 into
+  the attributes record, eliminating one INSERT/file backed up.
+- Python Event support has been added. See below for
+  configuration and details. The implementation is somewhat minimal,
+  so the functionality is not complete. The Python interface
+  has not been extensively tested, so please consider it BETA.
+- DVD writing support, using parts, and some new directives in
+  the Device resource of the Storage configuration file thanks
+  to Nicolas Boichat. Please note that this code is still 
+  BETA and should be carefully tested before using in
+  production.
+- Seven new options keywords in a FileSet resource:
+  ignorecase, fstype, hfsplussupport, wilddir, wildfile, regexdir,
+  and regexfile thanks to Pruben Guldberg). See below for details.
+- Restore of all files for a Job or set of jobs even if the file
+  records have been removed from the catalog.
+- Restore of a directory (non-recursive, i.e. only one level).
+- Support for TLS (ssl) between all the daemon connections thanks
+  to Landon Fuller.                         
+- Any Volume in the Pool named Scratch may be reassigned to any
+  other Pool when a new Volume is needed.
+- You may clone a Job and thus write (almost) the same data
+  to multiple Volumes simultaneously (see below). Actually, 
+  any Job may start any other Job with this mechanism, so it
+  also be used to group jobs.
+- Unicode filename support for Win32 (thanks to Thorsten Engel)
+- Volume Shadow Copy support for Win32 thus the capability to
+  backup exclusively opened files (thanks to Thorsten Engel).
+  A VSS enabled Win32 FD is available.  You must explicitly
+  turn on VSS with "Enable VSS = yes" in your FileSet resource.
+- New manual format with an index (thanks to Karl Cunningham).
+- New Web site format (thanks to Michael Scherer).
+- SQLite3 support.
+- Web-bacula, previously a separate project by Juan Luis Frances,
+  is now included in the Bacula GUI release. This is a management
+  level tool for reporting the state of Bacula jobs.
+- The code is now Internationalized so that it can be localized
+  in native languages.  Thanks to Nicolas Boichat.
+
+New Directives:
+- New Job directive "Prefer Mounted Volumes = yes|no" causes the
+  SD to select either an Autochanger or a drive with a valid 
+  Volume already mounted in preference. If none is available,
+  it will select the first available drive.
+- New Run directive in Job resource of DIR. It permits
+  cloning of jobs.  To clone a copy of the current job, use
+     Run = "job-name level=%l since=\"%s\""
+  Note, job-name is normally the same name as the job that
+  is running but there is no restriction on what you put. If you
+  want to start the job by hand and use job overrides such as       
+  storage=xxx, realize that the job will be started with the
+  default storage values not the overrides.  The level=%l guarantees
+  that the chosen level of the job is the same, and the since=... 
+  ensures that the job uses *exactly* the same time/date for incremental
+  and differential jobs. The since=... is ignored when level=Full.
+  A cloned job will not start additional clones, so it is not possible
+  to recurse.
+- New Options keywords in a FileSet directive (backported to 1.36.3):
+  - WildDir xxx
+    Will do a wild card match against directories (files will not
+    be matched).
+  - WildFile xxx
+    Will do a wild card match against files (directories will not
+    be matched).
+  - RegexDir xxx
+    Will do a regular expression match against directories (files
+    will not be matched).
+  - RegexFile xxx
+    Will do a regular expression match against files( directories
+    will not be matched).
+  - IgnoreCase = yes | no
+    Will ignore case in wild card and regular expression matches.
+    This is handy for Windows where filename case is not significant.
+  - FsType = string
+    where string is a filesystem type: ext2, jfs, ntfs, proc,
+    reiserfs, xfs, usbdevfs, sysfs, smbfs, iso9660.  For ext3
+    systems, use ext2.  You may have multiple fstype directives
+    and thus permit multiple filesystem types.  If the type
+    specified on the fstype directive does not match the
+    filesystem for a particular directive, that directory will
+    not be backed up.  This directive can be used to prevent
+    backing up non-local filesystems.
+  - HFS Plus Support = yes | no 
+    If set, Mac OS X resource forks will be saved and restored.
+- Label Type = ANSI | IBM | Bacula   
+  Implemented in Director Pool resource and in SD Device resource.
+  If it is specified in the SD Device resource, it will take
+  precedence over the value passed from the Director to the SD.
+- Check Labels = yes | no
+  Implemented in the SD Device resource. If you intend to read
+  ANSI or IBM labels, this *must* be set. Even if the volume
+  is not ANSI labeled, you can set this to yes, and Bacula will
+  check the label type.
+- Scripts Directory = <directory> name.  Defines the directory from 
+  which Bacula scripts will be called for events. In fact, Bacula
+  appends this name to the standard Python list of search directories,
+  so the script could also be in any of the Python system directories.
+- In FileSet, you can exclude backing up of hardlinks (if you have
+  a lot, it can be very expensive), by using:
+    HardLinks = no
+  in the Options section. Patch supplied by David R Bosso. Thanks.
+- MaximumPartSize = bytes (SD, Device resource)
+  Defines the maximum part size.
+- Requires Mount = Yes/No (SD, Device resource)
+  Defines if the device require to be mounted to be read, and if it
+  must be written in a special way. If it set, the following directives 
+  must be defined in the same Device resource:
+  + Mount Point = directory
+    Directory where the device must be mounted. 
+  + Mount Command = name-string
+    Command that must be executed to mount the device. Before the command
+    is executed, %a is replaced with the Archive Device, and %m with the 
+    Mount Point.
+  + Unmount Command = name-string
+    Command that must be executed to unmount the device. Before the 
+    command is executed, %a is replaced with the Archive Device, and 
+    %m with the Mount Point.
+  + Write Part Command = name-string
+    Command that must be executed to write a part to the device. Before
+    the command is executed, %a is replaced with the Archive Device, %m 
+    with the Mount Point, %n with the current part number (0-based), 
+    and %v with the current part filename.
+  + Free Space Command = name-string
+    Command that must be executed to check how much free space is left 
+    on the device. Before the command is executed, %a is replaced with 
+    the Archive Device, %m with the Mount Point, %n with the current part
+    number (0-based), and %v with the current part filename.
+- Write Part After Job = Yes/No (DIR, Job Resource, and Schedule Resource)
+  If this directive is set to yes (default no), a new part file will be
+  created after the job is finished.
+- A pile of new Directives to support TLS. Please see the TLS chapter
+  of the manual.
 
-Additional information is available from Landon at:
+New Commands:
+- "python restart" restarts the Python interpreter. Rather brutal, make
+   sure no Python scripts are running. This permits you to change
+   a Python script and get Bacula to use the new script.
+
+New configure options:
+- --with-libintl-prefix for defining alternate locations for
+  the NLS internationalization libraries. Not normally required.
+- --datadir  for defining where the language files will be installed
+  required only if you do not want the default /usr/share.
+
+Items to note!!!
+- If you use an Autochanger, you MUST update your SD conf file
+  to use the new Autochanger resource.  Otherwise, certain commands
+  such as "update slots" may not work.
+- You must add --with-python=[DIR] to the configure command line
+  if you want Python support.  Python 2.2, 2.3 and 2.4 should be 
+  automatically detected if in the standard place.
+- When linking with --with-python, there are a few warnings that
+  can be ignored.
+- You must either create a new catalog database or upgrade your
+  old database. After installation, run from your scripts
+  directory:
+
+       ./upgrade_bacula_tables
+
+  You can also find this script in the <bacula-source>/src/cats
+  directory.
+- The Director, Storage daemon, and File daemons are
+  Deamons are not compatible with  prior versions. 
+  All FDs must be upgraded at the same time.
+- You must add --with-openssl to the configure command line if
+  you want TLS communications encryption support.
+- Disk seeking during restores does not yet work correctly in
+  all cases, so it is turned off.
+- Note, with gcc (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) on an
+  AMD64 CPU running 64 bit CentOS4, there is a compiler bug that
+  generates bad code that causes Bacula to segment fault.
+  Typically you will see this in the Storage daemon first.  The
+  solution is to compile Bacula ensuring that no optimization is
+  turned on (normally it is -O2).
+
+
+Other Items:
+- Security fixes for temp files created in mtx-changer, during
+  ./configure, and during making of Rescue disk.
+- A new script, dvd-handler, in the scripts directory,
+  which is designed to be used as parameters to Write Part Command and
+  Free Space Command. They need the dvd+rw-tools to be installed
+  (http://fy.chalmers.se/~appro/linux/DVD+RW/) AND, the growisofs
+  program must be patched using the 
+  <bacula-source>/patches/dvd+rw-tools-5.21.4.10.8.bacula.patch
+  You must have Python installed to run the scripts.
+- Part files support: File volumes can now be split into multiple
+  files, called "parts".
+- For the details of the Python scripting support, please see the new
+  Python Scripting chapter in the manual.
 
- http://landonf.bikemonkey.org/code/bacula
+;;;
 
-Read on for details of the project, which is now partially
-implemented and being worked on by Landon in the Branch-1_38-encryption 
-branch of the Bacula CVS.
 
 Kern;;;2005/07/26;;;14:30
 BACULA COMMUNITY NEWS RELEASE
@@ -104,197 +277,9 @@ Bacula an even better product for the good of the whole community.
 If you have any questions related to this project, please contact 
 Kern Sibbald &lt;kern at sibbald dot com&gt;.
 
-
-Kern;;;2005/04/26;;;12:00
-The Bacula Version 1.36.3 tar file is released to Source Forge.
-
-          Release Notes for Bacula 1.36.3
-
-  Bacula code: Total files = 398 Total lines = 118,000 (*.h *.c *.in)
-
-Major Changes to version 1.36.3:
-- Applied all fixes for bugs since version 1.36.2 (see below)
-- Use fseeko and ftello so that attributes can exceed 4 GB.
-- Thanks to Karl Cunningham's hard work and skilled Perl      
-  programming, the manual is now in LaTeX format
-  and has an index!
-- Drop support of old style Include/Excludes (see below).
-
-New Directives in 1.36.3:
-- None, but see 1.36.2 additions below.
-
-New Commands:
-- None since 1.36.1
-
-Items to note for 1.36.3!!!
-- Drop support of old style Include/Excludes. Matt Howard has
-  supplied a handy Perl program that will do a good job of
-  converting your FileSets. It can be found in 
-  examples/conf/fileset_convert.pl
-- Dan has reminded us that the arguments for make_catalog_backup
-  changed from 1.34.x to 1.36.1. The old arguments were typically
-  "-U bacula".  The new arguments are typically "bacula bacula",
-  where the first is the database name, and the second is the
-  user name.
-
-Patches applied:
-
-04Mar05 1.36.2-level.patch
- This patch should fix a problem with th %l editing in the 
- client (FD) where it edited nothing. With this fix, it should
- edit "since".  
-
-04Mar05 1.36.2-pool.patch
- This patch corrects a problem preventing multiple 
- simultaneous jobs from different pools.
-
-09Mar05 1.36.2-win32-drive.patch
- This patch will prevent the Win32 FD from printing an error message
- when it attempts to restore the permissions for a drive (which Win32
- doesn't permit). The error is harmless in any case.
-
-15Mar05 1.36.2-netbsd.patch
- This patch corrects a compile problem because of no statfs() 
- on NetBSD. The patch was submitted by kardel with bug 258.
-
-16Mar05 1.36.2-console.patch
- This patch causes the output directed to a file to be
- flushed after every line. This is a bit overkill, IMO, but
- a user complained about it.
-
-17Mar05 1.36.2-restore-speed.patch
- This patch will fix a subtle bug that was introduced in 1.36.2
- which causes Bacula to be very slow restoring a few files. This
- is because it reads completely to the end of the Volume rather
- than stopping when all the files on the Volume are loaded. The
- introduction of the bug was caused by a patch that fixed 
- Bacula truncating tapes after a restore.
- Note that all source files will be rebuilt during the make.
-   
-18Mar05 1.36.2-store.patch
- This patch fails a job if no Storage resource is specified and
- the job attempts to call the SD.
-
-18Mar05 1.36.2-reschedule.patch
- This patch should fix a Segfault bug when a job is rescheduled.
- The storage pointers were being released when they should not
- have been.
-
-24Mar05 1.36.2-wx-console-bugfixes.patch
- Major wx-console fixes (see src/wx-console/CHANGELOG for details).
-
-28Mar05 1.36.2-tray-monitor-memleak.patch
- This patch should fix memory leaks in tray-monitor.
-
-Kern;;;2005/02/28;;;12:00
-The Bacula Version 1.36.2 tar file is released to Source Forge.
-
-Release Notes for Bacula 1.36.2
-
-  Bacula code: Total files = 398 Total lines = 117,915 (*.h *.c *.in)
-
-Major Changes to version 1.36.2:
-- Applied all fixes for bugs since version 1.36.1 (see below)
-- Added new directives from 1.37 code (see below).
-- Applied Tim's patch for ACLS.
-- Eight new options keywords in a FileSet resource:
-  ignorecase, fstype, hfsplussupport, wilddir, wildfile, regexdir,
-  and regexfile, hardlinks. See below for details.
-- Fix deadlock in multiple simultaneous jobs.
-- Fix tape "truncation"/"number of files" after restore bug.
-- Fix ClientRun jobs on Win32 to faile if the 
-  return code is not zero.
-
-New Directives in 1.36.2:
-- New Options keywords in a FileSet directive:
-  - WildDir xxx
-    Will do a wild card match against directories (files will not
-    be matched).
-  - WildFile xxx
-    Will do a wild card match against files (directories will not
-    be matched).
-  - RegexDir xxx
-    Will do a regular expression match against directories (files
-    will not be matched).
-  - RegexFile xxx
-    Will do a regular expression match against files( directories
-    will not be matched).
-  - IgnoreCase = yes | no
-    Will ignore case in wild card and regular expression matches.
-    This is handy for Windows where filename case is not significant.
-  - FsType = string
-    where string is a filesystem type: ext2, jfs, ntfs, proc,
-    reiserfs, xfs, usbdevfs, sysfs, smbfs, iso9660.  For ext3
-    systems, use ext2.  You may have multiple fstype directives
-    and thus permit multiple filesystem types.  If the type
-    specified on the fstype directive does not match the
-    filesystem for a particular directive, that directory will
-    not be backed up.  This directive can be used to prevent
-    backing up non-local filesystems.
-  - HFS Plus Support = yes | no 
-    If set, Mac OS X resource forks will be saved and restored.
-- In FileSet, you can exclude backing up of hardlinks (if you have
-  a lot, it can be very expensive), by using:
-    HardLinks = no
-  in the Options section. Patch supplied by David R Bosso. Thanks.
-
-New Commands:
-- None since 1.36.1
-
-Items to note for 1.36.2!!!
-- Dan has reminded us that the arguments for make_catalog_backup
-  changed from 1.34.x to 1.36.1. The old arguments were typically
-  "-U bacula".  The new arguments are typically "bacula bacula",
-  where the first is the database name, and the second is the
-  user name.
-
-Patches applied:
-
-03Dec04  1.36.1-pool.patch
- This patch should hold jobs in the Director's start queue if
- more than one simultaneous backup job wants to use the same
- Storage device with two different Pools (i.e. 2 Volumes).
-
-03Dec04  1.16.1-slots.patch
- This patch should fix "update slots" with two different
- magazines in different pools by checking the pool when zapping
- the InChanger.
-
-18Dec04 1.36.1-spool.patch
- This patch fixes the despooling size printed in the Job 
- report. Previously, it reported the total size for the
- device. This patch makes it report the size for the job.
-
-21Dec04 1.36.1-store.patch
- This patch fixes a problem with overriding storage daemon
- specifications. Previously they were not always honored.
- This implements more uniform handling. It also eliminates
- an orphaned buffer situation using JobDefs.
-
-21Dec04 1.36.1-reload.patch
- This patch fixes Bacula so that it does not exit if there
- is a syntax error in its conf file during a reload command.
-
-24Dec04 1.36.1-fileset.patch
- This patch should correct a seg fault in the FD that occurs
- at the end of a job when the job uses old style include/excludes.
- Old style include/excludes are deprecated and should be
- converted to the new style as soon as possible.
-
-30Jan05 1.36.1-acl.patch
- This patch fixes some typos with ACL checking that results
- in the incorrect name being used for the check.
- This fixes possible security problems with unwanted 
- access by restricted consoles.
-
-15Feb05 1.36.1-truncate.patch
- This patch fixes a bug where a tape gets "truncated" after
- doing a restore. The number of files in the catalog do not
- agree with what Bacula thinks is on tape, then the tape is
- marked in error.
-
 ;;;
 
+
 Michael;;;2005/02/25;;;19:59
 News-Page for the Bacula-Website finished
 When you read this, you read the first news posted by me *hehe*
diff --git a/docs/home-page/pages/donations.php b/docs/home-page/pages/donations.php
index 11c2d3e6..b38f7c1f 100644
--- a/docs/home-page/pages/donations.php
+++ b/docs/home-page/pages/donations.php
@@ -1,94 +1,64 @@
-
 <? require_once("inc/header.php"); ?>
 
-<form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
-<input type="hidden" name="cmd" value="_xclick">
-<input type="hidden" name="business" value="donations@bacula.org">
-<input type="hidden" name="currency_code" value="USD">
-<input type="image" src="http://www.paypal.com/en_US/i/btn/x-click-butcc-donate.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
-</form>
-
-
-<table>
+<table width="100%">
 <tr>
         <td class="contentTopic">
-        Contributing to the Bacula Project
+                Donations Received
         </td>
 </tr>
+</table>
+<table width="90%" align="center">
 <tr>
-    <td class="content">
-    Although one talks about Free Software, in fact, software such
-    as Bacula was not developed without some cost. The software
-    may be free for the user, but it wasn't free for the developer
-    or developers, either in terms of time or in terms of financial
-    cost.
+        <td class="content">
+        <table class="news" style="width: 99%">
+<?
 
-    For example, since beginning work on the Bacula project in
-    January 2000 until now (October 2005), I (Kern) have spent
-    approximately $8000 per year for computers, tape drives,
-    communications expenses, electricity, software licenses, and
-    other expenses.  I am not complaining and am pleased to have
-    been able to afford these expenditures.  In addition, have no
-    desire to have them reimbursed.
+$max_news = 5;
+$news_counter = 0;
 
-    Bacula is now a fairly mature product, and to ensure its long
-    term survival, I believe it should start to pay its own way.
-    <p>
-    As a consequence, it is now possible for you
-    to contribute to the Bacula project.
-    All funds collected will be used to help further the Bacula project
-    by covering out of pocket expenses incurred by the project (no salaries).
-    Examples are, hardware, software licenses (yes Micro$oft), and possibly
-    a portion of travel/conference expenses.
-    <p>
-    The project actually has the following needs (approximate costs): <br>
-    Three Microsoft Visual C++ licenses:  $3000<br>
-    Autochanger for FreeBSD testing:      $3200<br>
-    Autochanger for Solaris testing:      $3200<br>
+// read file into an array and revert that
+// revert cause array_pop always gets the last element
+//
+$file = "donations.txt";
+$lines = array_reverse(file($file)) or
+        die("No newsfile!");
 
-      
-    <p>
-    Contributions may not be US tax deductible as this is a individual
-    Bacula project account with PayPal. 
-    <p>
-    If you are a government or for-profit corporation and cannot
-    make &quot;donations&quot;, please consider paying a (non-obglitory)
-    binary license fee for any Bacula built binaries that you download. 
-    By providing you with these pre-built, pre-tested binaries, we are
-    really providing you with an extra service, which merits you
-    careful consideration for making a contribution or paying a 
-    &quot;license fee&quot;.
+// as long as there are lines ...
+//
+while(count($lines) > 0 && $news_counter < $max_news) {
+        // next line
+        $line = array_pop($lines);
 
-    A reasonable license fee would be:
-    <p>
-    <table>
-    <tr> <td>Number of Machines</td> <td>Fee</td></tr>
-    <tr> <td>1-10</td>  <td>$10 per machine</td></tr>
-    <tr> <td>11-20</td> <td>$100 + $5.00 per machine over 10</td></tr>
-    <tr> <td>21-50</td> <td>$150 + $2.00 per machine over 20</td></tr>
-    <tr> <td>51-...</td> <td>$250 + $1.00 per machine over 50</td></tr>
-    </table>
-    <p>Example: 55 machines = $250 + 5 X $1.00 = $255<br>
-    <p>Upgrades are 10% of the original license fee.
-    <p>
-    The above table is just a suggestion. You are, of course, free
-    to make a larger or smaller contribution as you see fit.
+        // start of news
+        if(eregi("^[a-z0-9]+;;;", $line)) {
+                // news header
+                list($author,$date,$time) = explode(";;;",$line);
 
-    If you wish your payment to be anonymous, please put the word
-    ANONYMOUS in the &quot;Payment For:&quot; field on the PayPal      
-    payment form.
+                // news subject
+                $subject = array_pop($lines);
+                printf('<tr><td class="newsHeader">%s</td></tr>', $subject);
+                printf('<tr><td class="newsContent"><pre class="newsContent">');
 
-    <p>
-    To make a contribution, please click on the donate button at the
-    top of the screen, and your transaction will be secured and
-    confirmed directly by PayPal.
+                continue;
+        }
 
-<p>
-Donations received in 1995: 1 - $50.00 -- thanks Ludovic!<br> 
-Contributions to EFF for Landon's Encryption project: 13 - $2,820<br>
+        // end of news
+        if(eregi("^;;;", $line)) {
+                printf('</pre></td></tr>');
+                printf('<tr>');
+                printf('<td class="newsFooter">%s - %s, %s</td>', $date, $time, $author);
+                printf('</tr>');
+                printf('<tr><td><img src="images/spacer.gif" width="1px" height="15px"></td></tr>');
+                $news_counter++;
+                continue;
+        }
 
-<p>
+        // news content
+        printf('%s', $line);
+}
+?>
+        </table>
+        </td>
 </tr>
-
 </table>
-<? require_once("inc/footer.php"); ?>
+<? require_once("inc/header.php"); ?>
diff --git a/docs/home-page/pages/makedonation.php b/docs/home-page/pages/makedonation.php
new file mode 100644
index 00000000..f8e506ef
--- /dev/null
+++ b/docs/home-page/pages/makedonation.php
@@ -0,0 +1,93 @@
+
+<? require_once("inc/header.php"); ?>
+
+<form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
+<input type="hidden" name="cmd" value="_xclick">
+<input type="hidden" name="business" value="donations@bacula.org">
+<input type="hidden" name="currency_code" value="USD">
+<input type="image" src="http://www.paypal.com/en_US/i/btn/x-click-butcc-donate.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
+</form>
+
+
+<table>
+<tr>
+        <td class="contentTopic">
+        Contributing to the Bacula Project
+        </td>
+</tr>
+<tr>
+    <td class="content">
+    Although one talks about Free Software, in fact, software such
+    as Bacula was not developed without some cost. The software
+    may be free for the user, but it wasn't free for the developer
+    or developers, either in terms of time or in terms of financial
+    cost.
+
+    For example, since beginning work on the Bacula project in
+    January 2000 until now (October 2005), I (Kern) have spent
+    approximately $8000 per year for computers, tape drives,
+    communications expenses, electricity, software licenses, and
+    other expenses.  I am not complaining and am pleased to have
+    been able to afford these expenditures.  In addition, have no
+    desire to have them reimbursed.
+
+    Bacula is now a fairly mature product, and to ensure its long
+    term survival, I believe it should start to pay its own way.
+    <p>
+    As a consequence, it is now possible for you
+    to contribute to the Bacula project.
+    All funds collected will be used to help further the Bacula project
+    by covering out of pocket expenses incurred by the project (no salaries).
+    Examples are, hardware, software licenses (yes Micro$oft), and possibly
+    a portion of travel/conference expenses.
+    <p>
+    The project actually has the following needs (approximate costs): <br>
+    Three Microsoft Visual C++ licenses:  $3000<br>
+    Autochanger for FreeBSD testing:      $3200<br>
+    Autochanger for Solaris testing:      $3200<br>
+
+      
+    <p>
+    Contributions may not be US tax deductible as this is a individual
+    Bacula project account with PayPal. 
+    <p>
+    If you are a government or for-profit corporation and cannot
+    make &quot;donations&quot;, please consider paying a (non-obglitory)
+    binary license fee for any Bacula built binaries that you download. 
+    By providing you with these pre-built, pre-tested binaries, we are
+    really providing you with an extra service, which merits you
+    careful consideration for making a contribution or paying a 
+    &quot;license fee&quot;.
+
+    A reasonable license fee would be:
+    <p>
+    <table>
+    <tr> <td>Number of Machines</td> <td>Fee</td></tr>
+    <tr> <td>1-10</td>  <td>$10 per machine</td></tr>
+    <tr> <td>11-20</td> <td>$100 + $5.00 per machine over 10</td></tr>
+    <tr> <td>21-50</td> <td>$150 + $2.00 per machine over 20</td></tr>
+    <tr> <td>51-...</td> <td>$250 + $1.00 per machine over 50</td></tr>
+    </table>
+    <p>Example: 55 machines = $250 + 5 X $1.00 = $255<br>
+    <p>Upgrades are 10% of the original license fee.
+    <p>
+    The above table is just a suggestion. You are, of course, free
+    to make a larger or smaller contribution as you see fit.
+
+    If you wish your payment to be anonymous, please put the word
+    ANONYMOUS in the &quot;Payment For:&quot; field on the PayPal      
+    payment form.
+
+    <p>
+    To make a contribution, please click on the donate button at the
+    top of the screen, and your transaction will be secured and
+    confirmed directly by PayPal.
+
+<p>
+To see the donations made to date, please click on the 
+Donations Received menu item to the left of your screen.
+<p>
+</tr>
+
+</table>
+<? require_once("inc/footer.php"); ?>
diff --git a/docs/home-page/pages/rfc.php b/docs/home-page/pages/rfc.php
new file mode 100644
index 00000000..83b9efa7
--- /dev/null
+++ b/docs/home-page/pages/rfc.php
@@ -0,0 +1,71 @@
+<? require_once("inc/header.php"); ?>
+<table>
+<tr>
+   <td class="contentTopic"> Feature Requests </td>
+</tr>
+<tr>
+   <td class="content">
+
+In the past, users informally submitted feature requests by email, and 
+I collected them, then once a version was released, I would publish the
+list for users to vote on.
+
+Now that Bacula has become a bigger project, I would like to formalize
+the process a bit more. The main change will be to require users
+to carefully think about their feature, and submit it on a feature
+request form. A mostly empty form is shown below along with an 
+exaple of an actual filled in form.
+
+Once I receive and approve the Feature Request, possibly requesting
+some modifications, I'll add it to the projects file, which contains
+a list of all open Feature Requests.
+
+<h3>Feature Request Form</h3>
+<pre>
+Item n:   One line summary ...
+  Origin: Name and email of originator.
+  Status:
+
+  What:   More detailed explanation ...
+
+  Why:    Why it is important ...
+
+  Notes:  Additional notes or features ...
+
+</pre>
+
+<h3>An Example Feature Request</h3>
+<pre>
+Item 1:   Implement a Migration job type that will move the job
+          data from one device to another.
+  Origin: Sponsored by Riege Sofware International GmbH. Contact:
+          Daniel Holtkamp <holtkamp at riege dot com>
+  Status: Partially coded in 1.37 -- much more to do. Assigned to
+          Kern.
+
+  What:   The ability to copy, move, or archive data that is on a
+          device to another device is very important.
+
+  Why:    An ISP might want to backup to disk, but after 30 days
+          migrate the data to tape backup and delete it from
+          disk.  Bacula should be able to handle this
+          automatically.  It needs to know what was put where,
+          and when, and what to migrate -- it is a bit like
+          retention periods.  Doing so would allow space to be
+          freed up for current backups while maintaining older
+          data on tape drives.
+
+  Notes:  Migration could be triggered by:
+           Number of Jobs
+           Number of Volumes
+           Age of Jobs
+           Highwater size (keep total size)
+           Lowwater mark
+
+</pre>
+
+</td>
+</tr>
+
+</table>
+<? require_once("inc/footer.php"); ?>
diff --git a/docs/manual/configure.tex b/docs/manual/configure.tex
index 3be7d995..7d900cea 100644
--- a/docs/manual/configure.tex
+++ b/docs/manual/configure.tex
@@ -298,6 +298,8 @@ you need not worry about creating all these kinds of resources from scratch.
 \multicolumn{1}{c| }{\bf Client } & \multicolumn{1}{c| }{\bf Storage } &
 \multicolumn{1}{c| }{\bf Console  } \\
  \hline 
+{Autochanger } & {No  } & {No } & {Yes } & {No  } \\
+\hline
 {Catalog } & {Yes } & {No  } & {No } & {No  } \\
  \hline 
 {Client  } & {Yes } & {Yes } & {No } & {No  } \\
@@ -329,6 +331,7 @@ you need not worry about creating all these kinds of resources from scratch.
 \label{Names}
 \index[general]{Authorization!Names Passwords and }
 \index[general]{Names, Passwords and Authorization }
+\index[general]{Passwords}
 \addcontentsline{toc}{subsection}{Names, Passwords and Authorization}
 
 In order for one daemon to contact another daemon, it must authorize itself
diff --git a/docs/manual/install.tex b/docs/manual/install.tex
index cdabb120..187775c3 100644
--- a/docs/manual/install.tex
+++ b/docs/manual/install.tex
@@ -20,8 +20,44 @@ we have combined a number of these packages into two {\bf depkgs} releases
 (Dependency Packages). This can vastly simplify your life by providing you
 with all the necessary packages rather than requiring you to find them on the
 Web, load them, and install them. 
-\label{upgrading1}
 
+\subsection*{Source Release Files}
+\index[general]{Source Files}
+\index[general]{Release Files}
+\addcontentsline{toc}{subsection}{Source Release File}
+Beginning with Bacula 1.38.0, the source code has been broken into
+four separate tar files each corresponding to a different module in
+the Bacula CVS. The released files are:
+
+\begin{description}
+\item [bacula-1.38.0.tar.gz]
+  This is the primary source code release for Bacula. On each
+  release the version number (1.38.0) will be updated.
+
+\item [bacula-docs-1.38.0.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-1.38.0.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
+  a browser program for burning CDROM images with Bacula Volumes.
+
+\item [bacula-rescue-1.8.1.tar.gz]
+  This is the Bacula Rescue CDROM code. Note, the version number
+  of this package is not tied to the Bacula release version, so
+  it will be different.  Using this code, you can burn a CDROM
+  with your system configuration and containing a statically
+  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.
+
+\end{description}
+
+\label{upgrading1}
 \subsection*{Upgrading Bacula}
 \index[general]{Bacula!Upgrading }
 \index[general]{Upgrading Bacula }
@@ -32,13 +68,22 @@ carefully read the ReleaseNotes of all versions between your current version
 and the version to which you are upgrading. If the Bacula catalog database has
 been upgraded, you will either need to reinitialize your database starting
 from scratch, or save an ASCII copy of your database, then proceed to upgrade
-it. If there are several database upgrades between your version and the
+it. This is normally done after Bacula is build and installed by:
+
+\begin{verbatim}
+cd <installed-scripts-dir> (default /etc/bacula)
+./update_bacula_tables
+\end{verbatim}
+
+This update script can also be find in the Bacula source src/cats
+directory.
+
+If there are several database upgrades between your version and the
 version to which you are upgrading, you will need to apply each database
 upgrade script. For your convenience, you can find all the old upgrade scripts
 in the {\bf upgradedb} directory of the source code. You will need to edit the
 scripts to correspond to your system configuration. The final upgrade script,
-if any, will be in the {\bf src/cats} directory as described in the
-ReleaseNotes. 
+if any, can be applied as noted above.
 
 If you are upgrading from one major version to another, you will need to
 replace all your components at the same time as generally the inter-daemon
@@ -50,6 +95,9 @@ 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. 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 {\bf make install}.
+In general none of your existing .conf or .sql files will be overwritten.
+
 For additional information on upgrading, please see the \ilink{Upgrading Bacula
 Versions}{upgrading} in the Tips chapter of this manual.
 
@@ -79,7 +127,7 @@ needed), you do the following:
 \item Detar the {\bf depkg} into the {\bf bacula} directory.  
 \item cd bacula/depkgs  
 \item make 
-   \end{enumerate}
+\end{enumerate}
 
 Although the exact composition of the dependency packages may change from time
 to time, the current makeup is the following: 
@@ -132,9 +180,8 @@ with valuable information about your SCSI tape drive (e.g. compression,
 min/max block sizes, ...). 
 
 The {\bf depkgs-win32} package contains the source code for the pthreads,
-zlib, and wxWidgets libraries used by the native Win32 client program. 
-It will only be needed
-if you intend to build the Win32 client from source. 
+zlib, and wxWidgets libraries used by the native Win32 client program.  It
+will only be needed if you intend to build the Win32 client from source.
 
 \subsection*{Supported Operating Systems}
 \label{Systems}
@@ -167,21 +214,28 @@ The basic installation is rather simple.
    in the {\bf libz-devel} package. On Debian  systems, you will need to load the
    {\bf zlib1g-dev} package. If  you are not using rpms or debs, you will need to
    find the  appropriate package for your system.  
+
    Note, if you already have a running MySQL or PostgreSQL on your system, you 
    can skip this phase provided that you have built the thread  safe libraries.
    And you have already installed the additional  rpms noted above.  
+
 \item As an alternative to MySQL and PostgreSQL, configure and install SQLite,
     which is part of the {\bf depkgs}.  
    \ilink{Installing and Configuring SQLite}{_ChapterStart33}.  
-   \item Detar the Bacula source code preferably into the {\bf bacula}  directory
+
+\item Detar the Bacula source code preferably into the {\bf bacula}  directory
    discussed above.  
+
 \item {\bf cd} to the directory containing the source code.  
+
 \item ./configure (with appropriate options as described below)  
+
 \item Check the output of ./configure very carefully, especially  the Install
    binaries and Install config directories.  If they are not correct,
    please rerun ./configure until they  are. The output from ./configure is
    stored in {\bf config.out}  and can be re-displayed at any time without
    rerunning the  ./configure by doing {\bf cat config.out}.  
+
 \item If after running ./configure once, you decide to change options  and
    re-run it, that is perfectly fine, but before re-running it,  you should run: 
 
@@ -189,7 +243,6 @@ The basic installation is rather simple.
 \footnotesize
 \begin{verbatim}
       make distclean
-      
 \end{verbatim}
 \normalsize
 
@@ -198,44 +251,50 @@ options. This is because ./configure  caches much of the information. The {\bf
 make distclean}  is also critical if you move the source directory from one 
 machine to another. If the {\bf make distclean} fails,  just ignore it and
 continue on.  
+
 \item make  
+   If you get errors while linking in the Storage daemon directory
+   (src/stored), it is probably because you have not loaded the static
+   libraries on your system.  I noticed this problem on a Solaris system.
+   To correct it, make sure that you have not added {\bf
+   {-}{-}enable-static-tools} to the {\bf ./configure} command.
 
-   If you get errors while linking in the Storage daemon  directory (src/stored),
-it is probably because you have not  loaded the static libraries on your
-system. I noticed this  problem on a Solaris system. To correct it, make sure
-that you  have not added {\bf \verb:--:enable-static-tools} to the  {\bf ./configure}
-command. 
 \item make install  
-\item If you are new to Bacula, we {\bf strongly} recommend that you  skip the
-   next step and use the default configuration files,  then run the example
-   program in the next chapter, then  come back and modify your configuration
-files to suit your  particular needs.  
+
+\item If you are new to Bacula, we {\bf strongly} recommend that you skip
+   the next step and use the default configuration files, then run the
+   example program in the next chapter, then come back and modify your
+   configuration files to suit your particular needs.
+
 \item Customize the configuration files for each of the three daemons 
-   (Directory, File, Storage) and for the Console program. For the  details of
-   how to do this, please see 
-\ilink{Setting Up Bacula Configuration Files}{_ChapterStart16} in
-the Configuration chapter of this manual.  We recommend that you start by
-modifying the default configuration  files supplied, making the minimum
-changes necessary.  Complete customization can be done after you have Bacula 
-up and running.  Please take care when modifying passwords, which  were
-randomly generated, and the {\bf Name}s as the  passwords and names must agree
-between the configuration files  for security reasons. 
-\item Create the Bacula MySQL database and tables (if using MySQL)  
-   \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or 
-   create the Bacula PostgreSQL database and tables  
-\ilink{Installing and Configuring PostgreSQL Phase
-II}{PostgreSQL_phase2} or alternatively  if you are using
-SQLite  
-\ilink{Installing and Configuring SQLite Phase II}{phase2}.  
+   (Directory, File, Storage) and for the Console program.  For the details
+   of how to do this, please see \ilink{Setting Up Bacula Configuration
+   Files}{_ChapterStart16} in the Configuration chapter of this manual.  We
+   recommend that you start by modifying the default configuration files
+   supplied, making the minimum changes necessary.  Complete customization
+   can be done after you have Bacula up and running.  Please take care when
+   modifying passwords, which were randomly generated, and the {\bf Name}s
+   as the passwords and names must agree between the configuration files
+   for security reasons.  \item Create the Bacula MySQL database and tables
+   (if using MySQL)
+      \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or 
+      create the Bacula PostgreSQL database and tables  
+   \ilink{Installing and Configuring PostgreSQL Phase
+   II}{PostgreSQL_phase2} or alternatively  if you are using
+   SQLite  
+   \ilink{Installing and Configuring SQLite Phase II}{phase2}.  
+
 \item Start Bacula ({\bf ./bacula start}) Note. the next chapter  shows you
    how to do this in detail.  
+
 \item Interface with Bacula using the Console program  
+
 \item For the previous two items, please follow the instructions  in the 
    \ilink{Running Bacula}{_ChapterStart1} chapter of  this manual,
    where you will run a simple backup and do a  restore. Do this before you make
-heavy modifications to the  configuration files so that you are sure that
-Bacula works  and are familiar with it. After that changing the conf files 
-will be easier.  
+   heavy modifications to the  configuration files so that you are sure that
+   Bacula works  and are familiar with it. After that changing the conf files 
+   will be easier.  
 \item If after installing Bacula, you decide to "move it", that is  to
    install it in a different set of directories, proceed  as follows:  
 
@@ -430,7 +489,6 @@ The following command line options are available for {\bf configure} to
 customize your installation. 
 
 \begin{description}
-
 \item [ {-}{-}sysbindir=\lt{}binary-path\gt{}]
    \index[general]{{-}{-}sysbindir }
    Defines where the Bacula  binary (executable) files will be placed during a
@@ -509,7 +567,18 @@ customize your installation.
    from with in the {\bf src/filed} directory.  Also, the {\bf
    \verb:--:enable-client-only} option described below is useful for just
    building a client so that all the other parts of the program are not
-   compiled.
+   compiled.   
+     
+   When linking a static binary, the linker needs the static versions
+   of all the libraries that are used, so frequently users will 
+   experience linking errors when this option is used. The first 
+   thing to do is to make sure you have the static glibc library 
+   installed on your system. The second thing to do is the make sure
+   you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+   on your ./configure statement as these options require additional
+   libraries. You may be able to enable those options, but you will
+   need to load additional static libraries.
+
 
 \item [ {-}{-}enable-static-sd]
    \index[general]{{-}{-}enable-static-sd }
@@ -517,30 +586,74 @@ customize your installation.
    addition to the standard Storage daemon.  This static version will
    include statically linked libraries and could be useful during a Bare
    Metal recovery.
+
+   When linking a static binary, the linker needs the static versions
+   of all the libraries that are used, so frequently users will 
+   experience linking errors when this option is used. The first 
+   thing to do is to make sure you have the static glibc library 
+   installed on your system. The second thing to do is the make sure
+   you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+   on your ./configure statement as these options require additional
+   libraries. You may be able to enable those options, but you will
+   need to load additional static libraries.
+
  
 
 \item [ {-}{-}enable-static-dir]
    \index[general]{{-}{-}enable-static-dir }
-   This option causes the make process  to build a {\bf static-bacula-dir} in
-   addition to the standard  Director. This static version will include
-   statically linked  libraries and could be useful during a Bare Metal recovery.
+   This option causes the make process to build a {\bf static-bacula-dir}
+   in addition to the standard Director.  This static version will include
+   statically linked libraries and could be useful during a Bare Metal
+   recovery.
+
+   When linking a static binary, the linker needs the static versions
+   of all the libraries that are used, so frequently users will 
+   experience linking errors when this option is used. The first 
+   thing to do is to make sure you have the static glibc library 
+   installed on your system. The second thing to do is the make sure
+   you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+   on your ./configure statement as these options require additional
+   libraries. You may be able to enable those options, but you will
+   need to load additional static libraries.
 
 
 \item [ {-}{-}enable-static-cons]
    \index[general]{{-}{-}enable-static-cons }
-   This option causes the make process  to build a {\bf static-console} and a
-   {\bf static-gnome-console}  in addition to the standard console.  This static
-   version will include statically linked  libraries and could be useful during a
-   Bare Metal recovery.  
+   This option causes the make process to build a {\bf static-console} and
+   a {\bf static-gnome-console} in addition to the standard console.  This
+   static version will include statically linked libraries and could be
+   useful during a Bare Metal recovery.
+
+   When linking a static binary, the linker needs the static versions
+   of all the libraries that are used, so frequently users will 
+   experience linking errors when this option is used. The first 
+   thing to do is to make sure you have the static glibc library 
+   installed on your system. The second thing to do is the make sure
+   you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+   on your ./configure statement as these options require additional
+   libraries. You may be able to enable those options, but you will
+   need to load additional static libraries.
+
 
 \item [ {-}{-}enable-client-only]
    \index[general]{{-}{-}enable-client-only }
-   This option causes the make process  to build only the File daemon and the
-   libraries that it needs.  None of the other daemons, storage tools, nor the
-   console will  be built. Likewise a {\bf make install} will then only install 
-   the File daemon. To cause all daemons to be built, you will need  to do a
-   configuration without this option. This option greatly  facilitates building a
-   Client on a client only machine.  
+   This option causes the make process to build only the File daemon and
+   the libraries that it needs.  None of the other daemons, storage tools,
+   nor the console will be built.  Likewise a {\bf make install} will then
+   only install the File daemon.  To cause all daemons to be built, you
+   will need to do a configuration without this option.  This option
+   greatly facilitates building a Client on a client only machine.
+
+   When linking a static binary, the linker needs the static versions
+   of all the libraries that are used, so frequently users will 
+   experience linking errors when this option is used. The first 
+   thing to do is to make sure you have the static glibc library 
+   installed on your system. The second thing to do is the make sure
+   you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+   on your ./configure statement as these options require additional
+   libraries. You may be able to enable those options, but you will
+   need to load additional static libraries.
+
 
 \item [ {-}{-}enable-largefile]
    \index[general]{{-}{-}enable-largefile }
@@ -565,27 +678,38 @@ customize your installation.
    \ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
     this manual for more details.  
 
+   See the note below under the {-}{-}with-postgresql item.
+
 \item [ {-}{-}with-sqlite3=\lt{}sqlite3-path\gt{}]
    \index[general]{{-}{-}with-sqlite3 }
-   This enables use of the SQLite version 3.x database. The {\bf sqlite3-path} is not
-   normally  specified as Bacula looks for the necessary components in  a
-   standard location ({\bf depkgs/sqlite3}). Although Bacula will run
-   with SQLite version 3.x, our testing shows that it is 4 to 10 times
-   slower than version 2.8.x and consequently, we do not recommend using
-   it. See 
+   This enables use of the SQLite version 3.x database.  The {\bf
+   sqlite3-path} is not normally specified as Bacula looks for the
+   necessary components in a standard location ({\bf depkgs/sqlite3}).  See
    \ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
-    this manual for more details.  
+   this manual for more details.
 
 \item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}]
    \index[general]{{-}{-}with-mysql }
-   This enables building of the Catalog services for Bacula. It  assumes that
-   MySQL is running on your system, and expects  it to be installed in the {\bf
-   mysql-path} that you  specify. If this option is not present, the build will 
-   automatically include the internal Bacula database  code. We recommend that
-   you use this option if possible.  If you do use this option, please proceed to
-   installing  MySQL in the 
-   \ilink{Installing and Configuring MySQL}{_ChapterStart} chapter
-   before proceeding with the configuration.
+   This enables building of the Catalog services for Bacula.  It assumes
+   that MySQL is running on your system, and expects it to be installed in
+   the {\bf mysql-path} that you specify.  Normally, if MySQL is installed
+   in a standard system location, you can simply use {\bf {-}{-}with-mysql}
+   with no path specification.  If you do use this option, please proceed
+   to installing MySQL in the \ilink{Installing and Configuring
+   MySQL}{_ChapterStart} chapter before proceeding with the configuration.
+
+   See the note below under the {-}{-}with-postgresql item.
+
+\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
+   \index[general]{{-}{-}with-postgresql }
+   This provides an explicit path to the PostgreSQL libraries if Bacula
+   cannot find it by default.  Normally to build with PostgreSQL, you would
+   simply use {\bf {-}{-}with-postgresql}.
+
+   Note, for Bacula to be configured properly, you must specify one
+   of the four database options supported.  That is:
+   {-}{-}with-sqlite, {-}{-}with-sqlite3, {-}{-}with-mysql, or
+   {-}{-}with-postgresql, otherwise the ./configure will fail.
 
 \item [ {-}{-}with-openssl=\lt{}path\gt{}]
    This configuration option is necessary if you want to enable TLS (ssl)
@@ -595,10 +719,6 @@ customize your installation.
    between the daemons. For more information on using TLS, please see the
    \ilink{Bacula TLS}{_ChapterStart61} chapter of this manual.
 
-\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
-   \index[general]{{-}{-}with-postgresql }
-   This provides an explicit  path to the PostgreSQL libraries if Bacula cannot
-   find it by  default.  
 
 \item [ {-}{-}with-python=\lt{}path\gt{}]
    \index[general]{{-}{-}with-python }
@@ -618,18 +738,19 @@ customize your installation.
 
 \item [ {-}{-}enable-conio]
    \index[general]{{-}{-}enable-conio }
-   Tells Bacula to enable building the  small, light weight readline replacement
-   routine. It is generally  much easier to configure than readline, although,
-   like readline,  it needs either the termcap or ncurses library.  
+   Tells Bacula to enable building the small, light weight readline
+   replacement routine.  It is generally much easier to configure than
+   readline, although, like readline, it needs either the termcap or
+   ncurses library.
 
 \item [ {-}{-}with-readline=\lt{}readline-path\gt{}]
    \index[general]{{-}{-}with-readline }
-   Tells Bacula  where {\bf readline} is installed. Normally, Bacula will  find
-   readline if it is in a standard library. If it is not found  and no
-   \verb:--:with-readline is specified, readline will be disabled.  This option affects
-   the Bacula build. Readline provides  the Console program with a command line
-   history and editing  capability and is no longer supported, so you are on your
-   own  if you have problems. 
+   Tells Bacula where {\bf readline} is installed.  Normally, Bacula will
+   find readline if it is in a standard library.  If it is not found and no
+   {-}{-}with-readline is specified, readline will be disabled.  This
+   option affects the Bacula build.  Readline provides the Console program
+   with a command line history and editing capability and is no longer
+   supported, so you are on your own if you have problems.
 
 \item [ {-}{-}enable-readline]
    \index[general]{{-}{-}enable-readline }
@@ -762,8 +883,8 @@ customize your installation.
 
 \end{description}
 
-Note, many other options are presented when you do a {\bf ./configure \verb:--:help},
-but they are not implemented. 
+Note, many other options are presented when you do a {\bf ./configure
+\verb:--:help}, but they are not implemented.
 
 \subsection*{Recommended Options for most Systems}
 \index[general]{Systems!Recommended Options for most }
@@ -925,11 +1046,11 @@ To install the binary Win32 version of the File daemon please see the
 \addcontentsline{toc}{subsection}{Windows Systems with CYGWIN Installed}
 
 As of version 1.34, Bacula no longer uses CYGWIN for the Win32 File daemon.
-However, it is still built under a CYGWIN build environment -- though you can
-probably do it with VC Studio only. If you wish to build the Win32 File daemon
-from the source, you will need Microsoft C++ version 6.0 or greater. In Bacula
-prior to version 1.33, CYGWIN was used. Details for building it are in the
-README.win32 file of the src/win32 directory. 
+However, it is still built under a CYGWIN build environment -- though you
+can probably do it with VC Studio only.  If you wish to build the Win32
+File daemon from the source, you will need Microsoft C++ version 7.1.
+Details for building the Win32 FD are in the README.win32 file of the
+src/win32 directory.
 
 Note, although most parts of Bacula build on Windows systems, the only part
 that we have tested and used is the File daemon. 
@@ -1024,12 +1145,13 @@ File daemon on the Client machine. To do so, you can use the same {\bf
 fresh copy of the source tree, or using {\bf make\ distclean} before the {\bf
 ./configure}. 
 
-Since the File daemon does not access the Catalog database, you can remove the
-{\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then add {\bf
-\verb:--:enable-client-only}. This will compile only the necessary libraries and the
-client programs and thus avoids the necessity of installing one or another of
-those database programs to build the File daemon. With the above option, you
-simply enter {\bf make} and just the client will be built. 
+Since the File daemon does not access the Catalog database, you can remove
+the {\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then
+add {\bf \verb:--:enable-client-only}.  This will compile only the
+necessary libraries and the client programs and thus avoids the necessity
+of installing one or another of those database programs to build the File
+daemon.  With the above option, you simply enter {\bf make} and just the
+client will be built.
 
 \label{autostart}
 \subsection*{Auto Starting the Daemons}
@@ -1050,15 +1172,15 @@ make install-autostart
 \end{verbatim}
 \normalsize
 
-Please note, that the auto-start feature is implemented only on systems that
-we officially support (currently, FreeBSD, RedHat/Fedora Linux, and Solaris), and has
-only been fully tested on Fedora Linux. 
+Please note, that the auto-start feature is implemented only on systems
+that we officially support (currently, FreeBSD, RedHat/Fedora Linux, and
+Solaris), and has only been fully tested on Fedora Linux.
 
-The {\bf make install-autostart} will cause the appropriate startup scripts to
-be installed with the necessary symbolic links. On RedHat/Fedora Linux systems, these
-scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
-/etc/rc.d/init.d/bacula-fd}, and {\bf /etc/rc.d/init.d/bacula-sd}. However the
-exact location depends on what operating system you are using. 
+The {\bf make install-autostart} will cause the appropriate startup scripts
+to be installed with the necessary symbolic links.  On RedHat/Fedora Linux
+systems, these scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
+/etc/rc.d/init.d/bacula-fd}, and {\bf /etc/rc.d/init.d/bacula-sd}.  However
+the exact location depends on what operating system you are using.
 
 If you only wish to install the File daemon, you may do so with: