Update

diff --git a/docs/manual/install.tex b/docs/manual/install.tex
index ffea50b94264afaaf13b7b2fa836090541c6285f..01b19a992f5b0228028ce8d2f1283d558f4b3fe2 100644 (file)
--- a/docs/manual/install.tex
+++ b/docs/manual/install.tex
@@ -616,7 +616,8 @@ customize your installation.
 \item [ {-}{-}mandir=\lt{}path\gt{}]
    \index[general]{{-}{-}mandir}
    Note, as of Bacula version 1.39.14, the meaning of any path
-   specified is now changed to mean the top level man directory.
+   specified on this option is change from prior versions. It
+   now specifies the top level man directory.
    Previously the mandir specified the full path to where you
    wanted the man files installed.
    The man files will be installed in gzip'ed format under
@@ -638,6 +639,8 @@ customize your installation.
    {-}{-}datadir} option. You must manually install any po files as
    Bacula does not (yet) automatically do so.
 
+\item [ {-}{-}disable-ipv6 ]
+   \index[general]{{-}{-}disable-ipv6}
 
 \item [ {-}{-}enable-smartalloc ]
    \index[general]{{-}{-}enable-smartalloc}
@@ -809,6 +812,14 @@ customize your installation.
    may specify {\bf {-}{-}disable-nls} to disable use of those libraries.
    In such a case, Bacula will revert to using English.
 
+\item [ {-}{-}disable-ipv6 ]
+   \index[general]{{-}{-}disable-ipv6}
+   By default, Bacula enables IPv6 protocol. On some systems, the files
+   for IPv6 may exist, but the functionality could be turned off in the
+   kernel. In that case, in order to correctly build Bacula, you will
+   explicitly need to use this option so that Bacula does not attempt
+   to reference OS function calls that do not exist.
+
 \item [ {-}{-}with-sqlite=\lt{}sqlite-path\gt{}]
    \index[general]{{-}{-}with-sqlite}
    This enables use of the SQLite version 2.8.x database. The {\bf sqlite-path} is not
@@ -1073,8 +1084,7 @@ paths. Neither are necessary if you do not use "make install" as is the case
 for most development work. The install process will create the sbindir and
 sysconfdir if they do not exist, but it will not automatically create the
 pid-dir, subsys-dir, or working-dir, so you must ensure that they exist before
-running Bacula for the first time. See below for an example of how Kern does
-it. 
+running Bacula for the first time.
 
 \section{Red Hat}
 \index[general]{Red Hat}
@@ -1219,16 +1229,16 @@ probably not work.
 To install the binary Win32 version of the File daemon please see the 
 \ilink{Win32 Installation Chapter}{_ChapterStart7} in this document. 
 
-\section{Kern's Configure Script}
-\index[general]{Script!Kern's Configure}
-\index[general]{Kern's Configure Script}
+\section{One File Configure Script}
+\index[general]{Script!One File Configure}
+\index[general]{One Files Configure Script}
 
-The script that I use for building on my "production" Linux machines is: 
+The following script could be used if you want to put everything
+in a single file:
 
 \footnotesize
 \begin{verbatim}
 #!/bin/sh
-# This is Kern's configure script for Bacula
 CFLAGS="-g -Wall" \
   ./configure \
     --sbindir=$HOME/bacula/bin \
@@ -1355,7 +1365,7 @@ make
 \normalsize
 
 To clean out all the objects and binaries (including the files named 1, 2, or
-3, which Kern uses as temporary files), enter: 
+3, which are development temporary files), enter: 
 
 \footnotesize
 \begin{verbatim}