1 files changed, 45 insertions, 84 deletions
diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html
index 2abd8a9ac15..0b293c7edfd 100644
--- a/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html
+++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html
@@ -1,11 +1,11 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <HTML
 ><HEAD
 ><TITLE
 >BIND Resource Requirements</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.73
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
 REL="HOME"
 TITLE="BIND 9 Administrator Reference Manual"
 HREF="Bv9ARM.html"><LINK
@@ -13,7 +13,7 @@ REL="PREVIOUS"
 TITLE="Introduction "
 HREF="Bv9ARM.ch01.html"><LINK
 REL="NEXT"
-TITLE="Nameserver Configuration"
+TITLE="Name Server Configuration"
 HREF="Bv9ARM.ch03.html"></HEAD
 ><BODY
 CLASS="chapter"
@@ -70,11 +70,11 @@ CLASS="chapter"
 ><H1
 ><A
 NAME="ch02"
->Chapter 2. <SPAN
+></A
+>Chapter 2. <ACRONYM
 CLASS="acronym"
->BIND</SPAN
-> Resource Requirements</A
-></H1
+>BIND</ACRONYM
+> Resource Requirements</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -84,27 +84,27 @@ CLASS="TOC"
 ></DT
 ><DT
 >2.1. <A
-HREF="Bv9ARM.ch02.html#AEN223"
+HREF="Bv9ARM.ch02.html#AEN228"
 >Hardware requirements</A
 ></DT
 ><DT
 >2.2. <A
-HREF="Bv9ARM.ch02.html#AEN231"
+HREF="Bv9ARM.ch02.html#AEN236"
 >CPU Requirements</A
 ></DT
 ><DT
 >2.3. <A
-HREF="Bv9ARM.ch02.html#AEN235"
+HREF="Bv9ARM.ch02.html#AEN240"
 >Memory Requirements</A
 ></DT
 ><DT
 >2.4. <A
-HREF="Bv9ARM.ch02.html#AEN240"
->Nameserver Intensive Environment Issues</A
+HREF="Bv9ARM.ch02.html#AEN245"
+>Name Server Intensive Environment Issues</A
 ></DT
 ><DT
 >2.5. <A
-HREF="Bv9ARM.ch02.html#AEN243"
+HREF="Bv9ARM.ch02.html#AEN248"
 >Supported Operating Systems</A
 ></DT
 ></DL
@@ -114,30 +114,30 @@ CLASS="sect1"
 ><H1
 CLASS="sect1"
 ><A
-NAME="AEN223"
+NAME="AEN228"
 >2.1. Hardware requirements</A
 ></H1
 ><P
-><SPAN
+><ACRONYM
 CLASS="acronym"
->DNS</SPAN
+>DNS</ACRONYM
 > hardware requirements have traditionally been quite modest.
 For many installations, servers that have been pensioned off from
-active duty have performed admirably as <SPAN
+active duty have performed admirably as <ACRONYM
 CLASS="acronym"
->DNS</SPAN
+>DNS</ACRONYM
 > servers.</P
 ><P
->The DNSSEC and IPv6 features of <SPAN
+>The DNSSEC and IPv6 features of <ACRONYM
 CLASS="acronym"
->BIND</SPAN
+>BIND</ACRONYM
 > 9 may prove to be quite
 CPU intensive however, so organizations that make heavy use of these
 features may wish to consider larger systems for these applications.
-<SPAN
+<ACRONYM
 CLASS="acronym"
->BIND</SPAN
-> 9 is now fully multithreaded, allowing full utilization of
+>BIND</ACRONYM
+> 9 is fully multithreaded, allowing full utilization of
 multiprocessor systems for installations that need it.</P
 ></DIV
 ><DIV
@@ -145,13 +145,13 @@ CLASS="sect1"
 ><H1
 CLASS="sect1"
 ><A
-NAME="AEN231"
+NAME="AEN236"
 >2.2. CPU Requirements</A
 ></H1
 ><P
->CPU requirements for <SPAN
+>CPU requirements for <ACRONYM
 CLASS="acronym"
->BIND</SPAN
+>BIND</ACRONYM
 > 9 range from i486-class machines
 for serving of static zones without caching, to enterprise-class
 machines if you intend to process many dynamic updates and DNSSEC
@@ -162,7 +162,7 @@ CLASS="sect1"
 ><H1
 CLASS="sect1"
 ><A
-NAME="AEN235"
+NAME="AEN240"
 >2.3. Memory Requirements</A
 ></H1
 ><P
@@ -172,92 +172,53 @@ CLASS="command"
 >max-cache-size</B
 >
 option can be used to limit the amount of memory used by the cache,
-at the expense of reducing cache hit rates and causing more <SPAN
+at the expense of reducing cache hit rates and causing more <ACRONYM
 CLASS="acronym"
->DNS</SPAN
+>DNS</ACRONYM
 >
 traffic. It is still good practice to have enough memory to load
 all zone and cache data into memory &#8212; unfortunately, the best way
-to determine this for a given installation is to watch the nameserver
+to determine this for a given installation is to watch the name server
 in operation. After a few weeks the server process should reach
 a relatively stable size where entries are expiring from the cache as
-fast as they are being inserted. Ideally, the resource limits should
-be set higher than this stable size.</P
+fast as they are being inserted.</P
 ></DIV
 ><DIV
 CLASS="sect1"
 ><H1
 CLASS="sect1"
 ><A
-NAME="AEN240"
->2.4. Nameserver Intensive Environment Issues</A
+NAME="AEN245"
+>2.4. Name Server Intensive Environment Issues</A
 ></H1
 ><P
->For nameserver intensive environments, there are two alternative
+>For name server intensive environments, there are two alternative
 configurations that may be used. The first is where clients and
-any second-level internal nameservers query a main nameserver, which
+any second-level internal name servers query a main name server, which
 has enough memory to build a large cache. This approach minimizes
 the bandwidth used by external name lookups. The second alternative
-is to set up second-level internal nameservers to make queries independently.
+is to set up second-level internal name servers to make queries independently.
 In this configuration, none of the individual machines needs to
 have as much memory or CPU power as in the first alternative, but
 this has the disadvantage of making many more external queries,
-as none of the nameservers share their cached data.</P
+as none of the name servers share their cached data.</P
 ></DIV
 ><DIV
 CLASS="sect1"
 ><H1
 CLASS="sect1"
 ><A
-NAME="AEN243"
+NAME="AEN248"
 >2.5. Supported Operating Systems</A
 ></H1
 ><P
->ISC <SPAN
+>ISC <ACRONYM
 CLASS="acronym"
->BIND</SPAN
-> 9 compiles and runs on the following operating
-systems:</P
-><P
-></P
-><UL
-><LI
-><P
->IBM AIX 4.3</P
-></LI
-><LI
-><P
->Compaq Digital/Tru64 UNIX 4.0D</P
-></LI
-><LI
-><P
->Compaq Digital/Tru64 UNIX 5 (with IPv6 EAK)</P
-></LI
-><LI
-><P
->HP HP-UX 11</P
-></LI
-><LI
-><P
->IRIX64 6.5</P
-></LI
-><LI
-><P
->Sun Solaris 2.6, 7, 8</P
-></LI
-><LI
-><P
->NetBSD 1.5 (with unproven-pthreads 0.17)</P
-></LI
-><LI
-><P
->FreeBSD 3.4-STABLE, 3.5, 4.0, 4.1</P
-></LI
-><LI
-><P
->Red Hat Linux 6.0, 6.1, 6.2, 7.0</P
-></LI
-></UL
+>BIND</ACRONYM
+> 9 compiles and runs on a large number
+of Unix-like operating system and on Windows NT / 2000.  For an up-to-date
+list of supported systems, see the README file in the top level directory
+of the BIND 9 source distribution.</P
 ></DIV
 ></DIV
 ><DIV
@@ -314,7 +275,7 @@ VALIGN="top"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Nameserver Configuration</TD
+>Name Server Configuration</TD
 ></TR
 ></TABLE
 ></DIV