[deployment-guide/comm-rel: 374/727] Removed the TODO comment.

[Jaromir Hradilek]

commit 19307ebd63a2169facb6d4ba85414d10eb1f8bb1
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 11:27:51 2010 +0200

    Removed the TODO comment.

 en-US/The_BIND_DNS_Server.xml |   64 -----------------------------------------
 1 files changed, 0 insertions(+), 64 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 5f680a9..f698123 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -155,70 +155,6 @@
         BIND consists of a set of DNS-related programs. It contains a monolithic nameserver called <systemitem class="service">named</systemitem>, an administration utility called <command>rndc</command>, and a debugging tool called <command>dig</command>.
       </para>
       <!-- TODO: Add "dig" utility decription -->
-      <!-- TODO: Move these information to different sections.
-      <para>
-        BIND stores its configuration files in the following locations:
-      </para>
-      <variablelist>
-        <varlistentry>
-          <term><filename>/etc/named.conf</filename></term>
-          <listitem>
-            <para>
-              The configuration file for the <command>named</command> daemon
-            </para>
-          </listitem>
-        </varlistentry>
-        <varlistentry>
-          <term><filename>/etc/named/</filename> directory</term>
-          <listitem>
-            <para>
-              Auxiliary directory for configuration files which is included in the main named.conf file
-            </para>
-          </listitem>
-        </varlistentry>
-        <varlistentry>
-          <term><filename>/var/named/</filename> directory</term>
-          <listitem>
-            <para>
-              The <command>named</command> working directory which stores zones. This directory is not writable by <command>named</command>
-            </para>
-          </listitem>
-        </varlistentry>
-        <varlistentry>
-          <term><filename>/var/named/slaves</filename> directory</term>
-          <listitem>
-            <para>
-              This directory is writable by <command>named</command> and should be used to store secondary (slave) zones.
-            </para>
-          </listitem>
-        </varlistentry>
-        <varlistentry>
-          <term><filename>/var/named/dynamic</filename> directory</term>
-          <listitem>
-            <para>
-              This directory is writable by <command>named</command> and should be used to store other writable files, like DDNS (dynamic DNS) zones or managed DNSSEC keys
-            </para>
-          </listitem>
-        </varlistentry>
-        <varlistentry>
-          <term><filename>/var/named/data</filename> directory</term>
-          <listitem>
-            <para>
-              This directory is writable by <command>named</command> and should be used to store various statistics and debugging files
-            </para>
-          </listitem>
-        </varlistentry>
-      </variablelist>
-      <note>
-        <title>Note</title>
-        <para>
-          If you have installed the <filename>bind-chroot</filename> package, the BIND service will run in the <command>/var/named/chroot</command> environment. All configuration files will be automatically mounted (via <command>mount &dash;&dash;bind</command>) there by initscript so you can manage your configuration in non-chroot environment. All files and directories written above are mounted.
-        </para>
-      </note>
-      <para>
-        The next few sections review the BIND configuration in more detail.
-      </para>
-      -->
     </section>
   </section>
   <section id="s1-bind-namedconf">