From: Jeremy C. Reed <jeremy-c-reed@users.sourceforge.net>
Date: Fri, 5 Jan 2007 17:37:47 +0000 (+0000)
Subject: Remove the "ilink" cross-references from within a few subsection header.
X-Git-Tag: Release-2.0.1~47
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=d89814c9af2123f5bbde9e672d89775284e1ab14;p=bacula%2Fdocs

Remove the "ilink" cross-references from within a few subsection header.

It didn't make sense for a subsection header to point to a different
chapter in a printed document. No hyperlink in print :)

Add a sentence at end each of these sub-sections to instead point
to that cross-reference. (The hyperlink is still in the section
but now can be read.)
---

diff --git a/docs/manual/quickstart.tex b/docs/manual/quickstart.tex
index 727fe597..fef1cbcc 100644
--- a/docs/manual/quickstart.tex
+++ b/docs/manual/quickstart.tex
@@ -119,8 +119,7 @@ right. Please do not despair. Once you have created your configuration files,
 you will rarely need to change them nor will you stop and start Bacula very
 often. Most of the work will simply be in changing the tape when it is full. 
 
-\subsection{
-\ilink{Configuring the Console Program}{ConsoleConfChapter}}
+\subsection{Configuring the Console Program}
 \index[general]{Configuring the Console Program }
 \index[general]{Program!Configuring the Console }
 
@@ -145,8 +144,10 @@ is, in this case, {\bf wx-console.conf}.
 Normally, for first time users, no change is needed to these files. Reasonable
 defaults are set. 
 
-\subsection{
-\ilink{Configuring the Monitor Program}{_MonitorChapter}}
+Further details are in the
+\ilink{Console configuration}{ConsoleConfChapter} chapter.
+
+\subsection{Configuring the Monitor Program}
 \index[general]{Program!Configuring the Monitor }
 \index[general]{Configuring the Monitor Program }
 
@@ -174,8 +175,10 @@ graphical environment (don't forget to allow non-root users to execute {\bf
 bacula-tray-monitor}). This is not a security problem as long as you use the
 default settings. 
 
-\subsection{
-\ilink{Configuring the File daemon}{FiledConfChapter}}
+More information is in the
+\ilink{Monitor configuration}{_MonitorChapter} chapter.
+
+\subsection{Configuring the File daemon}
 \index[general]{Daemon!Configuring the File }
 \index[general]{Configuring the File daemon }
 
@@ -194,8 +197,10 @@ File daemon must appear in the Director's configuration file.
 % TODO: point to section about how to install just the File daemon
 % TODO: and creating the unique configuration file.
 
-\subsection{
-\ilink{Configuring the Director}{DirectorChapter}}
+Further details are in the 
+\ilink{File daemon configuration}{FiledConfChapter} chapter.
+
+\subsection{Configuring the Director}
 \index[general]{Director!Configuring the }
 \index[general]{Configuring the Director }
 
@@ -241,8 +246,10 @@ working directory, the daemons temporary file names will not
 be unique, and you will get many strange failures.
 % TODO: why not check for that and not allow sharing working directory?
 
-\subsection{
-\ilink{Configuring the Storage daemon}{StoredConfChapter}}
+More information is in the
+\ilink{Director configuration}{DirectorChapter} chapter.
+
+\subsection{Configuring the Storage daemon}
 \index[general]{Daemon!Configuring the Storage }
 \index[general]{Configuring the Storage daemon }
 
@@ -262,6 +269,9 @@ instead of a tape, the Archive device must point to a directory in which the
 Volumes will be created as files when you label the Volume. 
 \label{ConfigTesting}
 
+Further information is in the
+\ilink{Storage daemon configuration}{StoredConfChapter} chapter.
+
 \section{Testing your Configuration Files}
 \index[general]{Testing your Configuration Files }
 \index[general]{Files!Testing your Configuration }