Updates

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index 30a146238a5b7c4d03c80db56891bc94a9853266..bc94aaa20b8c5c869e95d9c35cb258b09c06beb0 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -38,6 +38,8 @@ comparisons between every file in the FileSet and the list.
 Accurate must not be enabled when backing up with a plugin that is not
 specially designed to work with Accurate. If you enable it, your restores
 will probably not work correctly.
+
+This project was funded by Bacula Systems.
                                        
 
 
@@ -519,6 +521,8 @@ Compared to the Win32 Bacula Client, the 64 bit release contains a few differenc
       the same installation conventions as the Win64 version.
 \end{enumerate}
 
+This project was funded by Bacula Systems.
+
 
 \section{Duplicate Job Control}
 \index[general]{Duplicate Jobs}
@@ -679,7 +683,6 @@ applies to the two directories in question and any children (be they
 files, directories, etc).
 
 
-
 \section{Bacula Plugins}
 \index[general]{Plugin}
 Support for shared object plugins has been implemented in the Linux, Unix
@@ -825,6 +828,13 @@ on the program called.
 
 \section{Microsoft Exchange Server 2003/2007 Plugin}
 \index[general]{Microsoft Exchange Server 2003/2007 Plugin}
+\subsection{Background}
+The Exchange plugin was made possible by a funded development project
+between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems.
+The code for the plugin was written by James Harper, and the Bacula core
+code by Kern Sibbald.  All the code for this funded development has become
+part of the Bacula project.  Thanks to everyone who made it happen.
+
 \subsection{Concepts}
 Although it is possible to backup Exchange using Bacula VSS the Exchange 
 plugin adds a good deal of functionality, because while Bacula VSS
@@ -1134,6 +1144,50 @@ In your Director's {\bf Messages} resource.
   !$%&'()*+,-/:;<>?[]^`{|}~
 \end{verbatim}
 
+\section{Bare Metal Recovery}
+The old bare metal recovery project is essentially dead. One
+of the main features of it was that it would build a recovery
+CD based on the kernel on your system. The problem was that
+every distribution has a different boot procedure and different 
+scripts, and worse yet, the boot procedures and scripts change
+from one distribution to another.  This meant that maintaining
+(keeping up with the changes) the rescue CD was too much work.
+
+To replace it, a new bare metal recovery USB boot stick has been developed
+by Bacula Systems.  This technology involves remastering a Ubuntu LiveCD to
+boot from a USB key.  
+
+Advantages: 
+\begin{enumerate} 
+\item Recovery can be done from within graphical environment.  
+\item Recovery can be done in a shell.  
+\item Ubuntu boots on a large number of Linux systems.  
+\item The process of updating the system and adding new
+   packages is not too difficult. 
+\item The USB key can easily be upgraded to newer Ubuntu versions.
+\item The USB key has writable partitions for modifications to
+   the OS and for modification to your home directory.
+\item You can add new files/directories to the USB key very easily.
+\item You can save the environment from multiple machines on
+   one USB key.
+\item Bacula Systems is funding its ongoing development.
+\end{enumerate}
+
+The disadvantages are:
+\begin{enumerate}
+\item The USB key is usable but currently under development.
+\item Not everyone may be familiar with Ubuntu (no worse
+  than using Knoppix)
+\item Some older OSes cannot be booted from USB. This can
+   be resolved by first booting a Ubuntu LiveCD then plugging
+   in the USB key.
+\item Currently the documentation is sketchy and not yet added
+   to the main manual. See below ...
+\end{enumerate}
+
+The documentation and the code can be found in the {\bf rescue} package
+in the directory {\bf linux/usb}.
+
 \section{Miscellaneous}
 \index[general]{Misc New Features}
 
@@ -1418,13 +1472,21 @@ text based format. This is useful to backup it in a secure way.
 You can now specify the database connection port in the command line.
 
 \subsection{{-}{-}docdir configure option}
+\index[general]{{-}{-}docdir configure option}
 You can use {-}{-}docdir= on the ./configure command to
-specify the directory where you want Bacula release documentation 
-placed.  This document consists of a number of small files such as
-LICENSE, ReleaseNotes, ChangeLog, ...   The default is 
+specify the directory where you want Bacula to install the
+LICENSE, ReleaseNotes, ChangeLog, ... files.   The default is 
 {\bf /usr/share/doc/bacula}.
       
-\subsection{{-}{-}htmlir configure option}
+\subsection{{-}{-}htmldir configure option}
+\index[general]{{-}{-}htmldir configure option}
 You can use {-}{-}htmldir= on the ./configure command to
-specify the directory where you want Bacula bat html help files
-placed.  The default is {\bf /usr/share/doc/bacula/html}
+specify the directory where you want Bacula to install the bat html help
+files. The default is {\bf /usr/share/doc/bacula/html}
+
+\subsection{{-}{-}with-plugindir configure option}
+\index[general]{{-}{-}plugindir configure option}
+You can use {-}{-}plugindir= on the ./configure command to
+specify the directory where you want Bacula to install
+the plugins (currently only bpipe-fd). The default is
+sysconfdir.