Massive rearrangement of the installation section. Hopefully it makes sense now.

docs/html/about.html

@@ -7,11 +7,11 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="NEXT"
@@ -36,7 +36,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -154,7 +154,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TD
 ><TD
 WIDTH="34%"

docs/html/administration.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -73,7 +73,7 @@ CLASS="chapter"
 ><A
 NAME="administration"
 ></A
->Chapter 5. Administering Bugzilla</H1
+>Chapter 3. Administering Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -82,61 +82,61 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->5.1. <A
+>3.1. <A
 HREF="parameters.html"
 >Bugzilla Configuration</A
 ></DT
 ><DT
->5.2. <A
+>3.2. <A
 HREF="useradmin.html"
 >User Administration</A
 ></DT
 ><DD
 ><DL
 ><DT
->5.2.1. <A
+>3.2.1. <A
 HREF="useradmin.html#defaultuser"
 >Creating the Default User</A
 ></DT
 ><DT
->5.2.2. <A
+>3.2.2. <A
 HREF="useradmin.html#manageusers"
 >Managing Other Users</A
 ></DT
 ></DL
 ></DD
 ><DT
->5.3. <A
+>3.3. <A
 HREF="products.html"
 >Products</A
 ></DT
 ><DT
->5.4. <A
+>3.4. <A
 HREF="components.html"
 >Components</A
 ></DT
 ><DT
->5.5. <A
+>3.5. <A
 HREF="versions.html"
 >Versions</A
 ></DT
 ><DT
->5.6. <A
+>3.6. <A
 HREF="milestones.html"
 >Milestones</A
 ></DT
 ><DT
->5.7. <A
+>3.7. <A
 HREF="voting.html"
 >Voting</A
 ></DT
 ><DT
->5.8. <A
+>3.8. <A
 HREF="groups.html"
 >Groups and Group Security</A
 ></DT
 ><DT
->5.9. <A
+>3.9. <A
 HREF="upgrading.html"
 >Upgrading to New Releases</A
 ></DT

docs/html/bug_page.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="bug_page"
 ></A
->3.3. Anatomy of a Bug</H1
+>5.3. Anatomy of a Bug</H1
 ><P
 >The core of Bugzilla is the screen which displays a particular
     bug. It's a good place to explain some Bugzilla concepts. 

docs/html/bugreports.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="bugreports"
 ></A
->3.6. Filing Bugs</H1
+>5.6. Filing Bugs</H1
 ><P
 >Years of bug writing experience has been distilled for your
     reading pleasure into the 

docs/html/cmdline.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -17,8 +17,8 @@ REL="PREVIOUS"
 TITLE="Contrib"
 HREF="patches.html"><LINK
 REL="NEXT"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"></HEAD
+TITLE="Manual Installation of Perl Modules"
+HREF="install-perlmodules-manual.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -61,7 +61,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="gfdl.html"
+HREF="install-perlmodules-manual.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -186,7 +186,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="gfdl.html"
+HREF="install-perlmodules-manual.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -210,7 +210,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->GNU Free Documentation License</TD
+>Manual Installation of Perl Modules</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/components.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="components"
 ></A
->5.4. Components</H1
+>3.4. Components</H1
 ><P
 >Components are subsections of a Product. E.g. the computer game 
     you are designing may have a "UI"

docs/html/stepbystep.html → docs/html/configuration.html

 <HTML
 ><HEAD
 ><TITLE
->Step-by-step Install</TITLE
+>Configuration</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
 REL="PREVIOUS"
 TITLE="Installation"
 HREF="installation.html"><LINK
 REL="NEXT"
-TITLE="HTTP Server Configuration"
-HREF="http.html"></HEAD
+TITLE="Optional Additional Configuration"
+HREF="extraconfig.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 4. Installation</TD
+>Chapter 2. Installing Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="http.html"
+HREF="extraconfig.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -75,58 +75,9 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="stepbystep"
+NAME="configuration"
 ></A
->4.1. Step-by-step Install</H1
-><P
->Bugzilla has been successfully installed under many different
-      operating systems including almost all Unix clones and
-      <SPAN
-CLASS="productname"
->Microsoft Windows</SPAN
->.  Many
-      operating systems have utilities that make installation easier or quirks
-      that make it harder. We have tried to collect that information in
-      <A
-HREF="os-specific.html"
->Section 4.4</A
->, so unless you are on Linux,
-      be sure to check out that section before
-      you start your installation.
-      </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Windows is one of those operating systems that has many quirks
-        and is not yet officially supported by the Bugzilla team. If you wish
-        to install Bugzilla on Windows, be sure to see
-        <A
-HREF="os-specific.html#os-win32"
->Section 4.4.1</A
->.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
+>2.2. Configuration</H1
 ><DIV
 CLASS="warning"
 ><P
@@ -148,198 +99,174 @@ ALT="Warning"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->While installing Bugzilla, it is a good idea to ensure that there
-        is some kind of configurable firewall between you and the rest of the 
-        Internet
-        as your machine may be insecure for periods during the install. Many
-        installation steps require an active Internet connection to complete,
-        but you must take care to ensure that at no point is your machine
-        vulnerable to an attack.</P
+>Poorly-configured MySQL and Bugzilla installations have
+      given attackers full access to systems in the past. Please take the
+      security parts of these guidelines seriously, even for Bugzilla 
+      machines hidden away behind your firewall.</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="localconfig"
+></A
+>2.2.1. localconfig</H2
 ><P
->This guide assumes that you already have your operating system
-      installed, network configured, and have administrative access to the
-      machine onto which you are installing Bugzilla. It is possible to
-      install and run Bugzilla itself without administrative access, but you 
-      have to
-      either make sure all the required software is installed or get somebody
-      with administrative access to install it for you.
+>&#13;        Once you run <TT
+CLASS="filename"
+>checksetup.pl</TT
+> with all the correct 
+        modules installed, it displays a message about, and write out a 
+        file called, 
+        <TT
+CLASS="filename"
+>localconfig</TT
+>. This file contains the default
+        settings for a number of Bugzilla parameters.
       </P
 ><P
->&#13;      You are strongly recommended to make a backup of your system
-      before installing Bugzilla (and at regular intervals thereafter :-).
+>Load this file in your editor. The only value you 
+      <EM
+>need</EM
+> to change is $db_pass, the password for
+      the user you will create for your database.
+      Pick a strong password (for simplicity, it should not contain
+      single quote characters) and put it here.
       </P
 ><P
->Here's a basic step-by-step list:
+>&#13;        The other options in the <TT
+CLASS="filename"
+>localconfig</TT
+> file
+        are documented by their accompanying comments. If you have a slightly
+        non-standard MySQL setup, you may wish to change one or more of
+        the other "$db_*" parameters. 
       </P
-><DIV
-CLASS="procedure"
-><OL
-TYPE="1"
-><LI
-><P
-><A
-HREF="stepbystep.html#install-perl"
->Install Perl</A
->
-          (5.6.0 or above)
-          </P
-></LI
-><LI
-><P
-><A
-HREF="stepbystep.html#install-mysql"
->Install MySQL</A
->
-          (3.23.41 or above)
-          </P
-></LI
-><LI
-><P
-><A
-HREF="stepbystep.html#install-webserver"
->Install a Webserver</A
->
-          </P
-></LI
-><LI
-><P
-><A
-HREF="stepbystep.html#install-bzfiles"
->Put Bugzilla in the Webspace</A
->
-          </P
-></LI
-><LI
-><P
-><A
-HREF="stepbystep.html#install-perlmodules"
->Install Perl Modules</A
->
-          </P
-></LI
-><LI
 ><P
-><A
-HREF="stepbystep.html#install-setupdatabase"
->Setup the MySQL Database</A
->
-          </P
-></LI
-></OL
+>&#13;        You may also wish to change the names of 
+        the priorities, severities, operating systems and platforms for your
+        installation. However, you can always change these after installation
+        has finished; if you then re-run 
+        <TT
+CLASS="filename"
+>checksetup.pl</TT
+>, the changes will get picked up.
+      </P
 ></DIV
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-perl"
+NAME="mysql"
 ></A
->4.1.1. Perl</H2
-><P
->Any machine that doesn't have Perl on it is a sad machine indeed.
-      If your OS doesn't come with it, Perl can be got in source form 
-      from <A
-HREF="http://www.perl.com"
-TARGET="_top"
->http://www.perl.com</A
->.
-      There are also binary versions available for many platforms, most of which
-      are linked to from perl.com.
-      Although Bugzilla runs with perl 5.6.0,
-      it's a good idea to be up to the very latest version
-      if you can when running Bugzilla. As of this writing, that is Perl
-      version 5.8.2.</P
-></DIV
+>2.2.2. MySQL</H2
 ><DIV
 CLASS="section"
-><H2
+><H3
 CLASS="section"
 ><A
-NAME="install-mysql"
+NAME="security-mysql"
 ></A
->4.1.2. MySQL</H2
-><P
->If your OS doesn't come with it or provide official packages,
-      visit the MySQL homepage at 
-      <A
-HREF="http://www.mysql.com"
-TARGET="_top"
->http://www.mysql.com</A
->
-      to grab and install the latest stable release of the server. 
-      </P
-><DIV
-CLASS="note"
+>2.2.2.1. Security</H3
+><P
+>MySQL ships as insecure by default.
+        It allows anybody to on the local machine full administrative 
+        capabilities without requiring a password; the special
+        MySQL root account (note: this is <EM
+>not</EM
+> the same as
+        the system root) also has no password.
+        Also, many installations default to running
+        <SPAN
+CLASS="application"
+>mysqld</SPAN
+> as the system root.
+        </P
 ><P
 ></P
+><OL
+TYPE="1"
+><LI
+><P
+>To disable the anonymous user account
+            and set a password for the root user, execute the following. The
+            root user password should be different to the bugs user password
+            you set in 
+            <TT
+CLASS="filename"
+>localconfig</TT
+> in the previous section, 
+            and also different to
+            the password for the system root account on your machine.
+            </P
 ><TABLE
-CLASS="note"
-WIDTH="100%"
 BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
 ><TR
 ><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Many of the binary
-        versions of MySQL store their data files in 
-        <TT
-CLASS="filename"
->/var</TT
->.
-        On some Unix systems, this is part of a smaller root partition,
-        and may not have room for your bug database. You can set the data
-         directory as an option to <TT
-CLASS="filename"
->configure</TT
->
-         if you build MySQL from source yourself.</P
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="screen"
+>  <TT
+CLASS="prompt"
+>bash$</TT
+> mysql mysql
+  <TT
+CLASS="prompt"
+>mysql&#62;</TT
+> DELETE FROM user WHERE user = '';
+  <TT
+CLASS="prompt"
+>mysql&#62;</TT
+> UPDATE user SET password = password('<TT
+CLASS="replaceable"
+><I
+>new_password</I
+></TT
+>') WHERE user = 'root';
+  <TT
+CLASS="prompt"
+>mysql&#62;</TT
+> FLUSH PRIVILEGES;</PRE
+></FONT
 ></TD
 ></TR
 ></TABLE
-></DIV
-><P
->If you install from something other than a packaging/installation
-      system (such as .rpm, .dep, .exe, or .msi) you will need to configure
-      your system so the MySQL server daemon will come back up whenever
-      your machine reboots.
-      </P
 ><P
->If you wish to have attachments larger than 64K, you will have to
-      configure MySQL to accept large packets. This is done by adding the text
-      in <A
-HREF="stepbystep.html#install-mysql-packets"
->Figure 4-1</A
-> to your
-      <TT
+>From this point forward, to run the 
+            <TT
 CLASS="filename"
->my.conf</TT
-> file. There is also a parameter in Bugzilla
-      for setting the maximum allowable attachment size.
-      
-      You should set this value to be slightly larger than that parameter.
-      </P
-><DIV
-CLASS="figure"
-><A
-NAME="install-mysql-packets"
-></A
+>mysql</TT
+> command-line client, 
+            you will need to type
+            <B
+CLASS="command"
+>mysql -u root -p</B
+> and enter
+            <TT
+CLASS="replaceable"
+><I
+>new_password</I
+></TT
+> when prompted.
+            </P
+></LI
+><LI
 ><P
-><B
->Figure 4-1. Set Max Packet Size in MySQL</B
-></P
+>If you run MySQL on the same machine as your web server, you
+            should disable remote access to MySQL by adding
+            the following to your <TT
+CLASS="filename"
+>/etc/my.conf</TT
+>:
+            </P
 ><TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
@@ -350,26 +277,34 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
->&#13;[mysqld]
-# Allow packets up to 1M
-set-variable = max_allowed_packet=1M
-        </PRE
+>  [myslqd]
+  # Prevent network access to MySQL.
+  skip-networking</PRE
 ></FONT
 ></TD
 ></TR
 ></TABLE
-></DIV
+></LI
+><LI
 ><P
->If you are running Bugzilla and MySQL on the same machine, you may
-      also wish to utilize the <TT
-CLASS="option"
->--skip-networking</TT
-> option as
-      mentioned in <A
-HREF="security.html#security-mysql"
->Section 4.5.2</A
-> for the added security.
-      </P
+>Consult the documentation that came with your system for
+            information on making <SPAN
+CLASS="application"
+>mysqld</SPAN
+> run as an
+            unprivileged user.
+            </P
+></LI
+><LI
+><P
+>For added security, you could also run MySQL, or even all 
+            of Bugzilla
+            in a chroot jail; however, instructions for doing that are beyond
+            the scope of this document.
+            </P
+></LI
+></OL
+></DIV
 ><DIV
 CLASS="section"
 ><H3
@@ -377,66 +312,71 @@ CLASS="section"
 ><A
 NAME="install-setupdatabase"
 ></A
->4.1.2.1. Adding a user to MySQL</H3
+>2.2.2.2. Allow large attachments</H3
 ><P
->This first thing you'll want to do is make sure you've given the
-        <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> user a password as suggested in
-        <A
-HREF="security.html#security-mysql"
->Section 4.5.2</A
->. Then, you need to add a user for
-        Bugzilla to use. For clarity, these instructions will
-        assume that your MySQL user for Bugzilla will be <SPAN
-CLASS="QUOTE"
->"bugs_user"</SPAN
->,
-        the database will be called <SPAN
-CLASS="QUOTE"
->"bugs_db"</SPAN
-> and the password for
-        the <SPAN
-CLASS="QUOTE"
->"bugs_user"</SPAN
-> user is <SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
->. You
-        should, of course, substitute the values you intend to use for your site.
+>You need to configure MySQL to accept large packets, if you
+        want to have attachments larger than 64K. Add the text
+        below to your
+        <TT
+CLASS="filename"
+>/etc/my.conf</TT
+>. 
+        There is also a parameter in Bugzilla
+        for setting the maximum allowable attachment size, (default 1MB).
+        Bugzilla will only accept attachments up to the lower of these two
+        sizes.
         </P
-><DIV
-CLASS="note"
-><P
-></P
 ><TABLE
-CLASS="note"
-WIDTH="100%"
 BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
 ><TR
 ><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Most people use <SPAN
-CLASS="QUOTE"
->"bugs"</SPAN
-> for both the user and
-          database name. Don't use it for the password, though...
-          </P
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="screen"
+>  [mysqld]
+  # Allow packets up to 1M
+  set-variable = max_allowed_packet=1M</PRE
+></FONT
 ></TD
 ></TR
 ></TABLE
 ></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-setupdatabase-adduser"
+></A
+>2.2.2.3. Add a user to MySQL</H3
+><P
+>You need to add a new MySQL user for
+        Bugzilla to use. (It's not safe to have Bugzilla use the MySQL root
+        account.) The following instructions assume the defaults in 
+        <TT
+CLASS="filename"
+>localconfig</TT
+>; 
+        if you changed those, you need to modify the 
+        SQL command appropriately. You will need the 
+        <TT
+CLASS="replaceable"
+><I
+>$db_pass</I
+></TT
+> password you set in
+        <TT
+CLASS="filename"
+>localconfig</TT
+> in 
+        <A
+HREF="configuration.html#localconfig"
+>Section 2.2.1</A
+>.
+        </P
 ><P
 >We use an SQL <B
 CLASS="command"
@@ -444,17 +384,17 @@ CLASS="command"
 > command to create a 
         <SPAN
 CLASS="QUOTE"
->"bugs_user"</SPAN
+>"bugs"</SPAN
 >
         user. This also restricts the 
         <SPAN
 CLASS="QUOTE"
->"bugs_user"</SPAN
+>"bugs"</SPAN
 >
         user to operations within a database called 
         <SPAN
 CLASS="QUOTE"
->"bugs_db"</SPAN
+>"bugs"</SPAN
 >, and only allows the account to connect from 
         <SPAN
 CLASS="QUOTE"
@@ -462,6 +402,12 @@ CLASS="QUOTE"
 >. 
         Modify it to reflect your setup if you will be connecting from
         another machine or as a different user.</P
+><P
+>Run the <TT
+CLASS="filename"
+>mysql</TT
+> command-line client and
+        enter:</P
 ><TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
@@ -472,17 +418,21 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="screen"
->&#13;  <TT
+>  <TT
 CLASS="prompt"
 >mysql&#62;</TT
 > GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,
-         DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost
-         IDENTIFIED BY 'bugs_password';
+         DROP,REFERENCES ON bugs.* TO bugs@localhost
+         IDENTIFIED BY '<TT
+CLASS="replaceable"
+><I
+>$db_pass</I
+></TT
+>';
   <TT
 CLASS="prompt"
 >mysql&#62;</TT
-> FLUSH PRIVILEGES;
-        </PRE
+> FLUSH PRIVILEGES</PRE
 ></FONT
 ></TD
 ></TR
@@ -508,7 +458,7 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->If you are using MySQL 4, the bugs user also needs to be granted
+>If you are using MySQL 4, you need to add
           the <TT
 CLASS="computeroutput"
 >LOCK TABLES</TT
@@ -516,12 +466,8 @@ CLASS="computeroutput"
           <TT
 CLASS="computeroutput"
 >CREATE TEMPORARY TABLES</TT
-> permissions,
-          so add them to the list in the 
-          <TT
-CLASS="computeroutput"
->GRANT</TT
-> command.
+> permissions
+          to the list.
           </P
 ></TD
 ></TR
@@ -534,203 +480,114 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-webserver"
+NAME="AEN400"
 ></A
->4.1.3. HTTP Server</H2
+>2.2.3. checksetup.pl</H2
 ><P
->You have freedom of choice here, pretty much any web server that
-      is capable of running <A
-HREF="glossary.html#gloss-cgi"
-><I
-CLASS="glossterm"
->CGI</I
-></A
->
-      scripts will work. <A
-HREF="http.html"
->Section 4.2</A
-> has more information about
-      configuring web servers to work with Bugzilla.
+>&#13;        Next, rerun <TT
+CLASS="filename"
+>checksetup.pl</TT
+>. It reconfirms
+        that all the modules are present, and notices the altered 
+        localconfig file, which it assumes you have edited to your
+        satisfaction. It compiles the UI templates,
+        connects to the database using the 'bugs'
+        user you created and the password you defined, and creates the 
+        'bugs' database and the tables therein. 
       </P
-><DIV
-CLASS="note"
 ><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
+>&#13;        After that, it asks for details of an administrator account. Bugzilla
+        can have multiple administrators - you can create more later - but
+        it needs one to start off with.
+        Enter the email address of an administrator, his or her full name, 
+        and a suitable Bugzilla password.
+      </P
 ><P
->We strongly recommend Apache as the web server to use. The
-        Bugzilla Guide installation instructions, in general, assume you are
-        using Apache. If you have got Bugzilla working using another webserver,
-        please share your experiences with us by filing a bug in <A
-HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
-TARGET="_top"
->Bugzilla Documentation</A
->.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
+>&#13;        <TT
+CLASS="filename"
+>checksetup.pl</TT
+> will then finish. You may rerun
+        <TT
+CLASS="filename"
+>checksetup.pl</TT
+> at any time if you wish.
+      </P
 ></DIV
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="install-bzfiles"
+NAME="http"
 ></A
->4.1.4. Bugzilla</H2
+>2.2.4. Web server</H2
 ><P
->You should untar the Bugzilla files into a directory that you're
-      willing to make writable by the default web server user (probably 
-      <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->). 
-      You may decide to put the files in the main web space for your
-      web server or perhaps in 
-      <TT
-CLASS="filename"
->/usr/local</TT
->
-      with a symbolic link in the web space that points to the Bugzilla
-      directory.</P
+>Configure your web server according to the instructions in the
+      appropriate section. The Bugzilla Team recommends Apache.
+      </P
 ><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="http-apache"
+></A
+>2.2.4.1. Apache <SPAN
+CLASS="productname"
+>httpd</SPAN
+></H3
 ><P
->If you symlink the bugzilla directory into your Apache's 
-        <TT
-CLASS="filename"
->html</TT
->
-        hierarchy, you may receive 
-        <SPAN
-CLASS="errorname"
->Forbidden</SPAN
->
-        errors unless you add the 
-        <TT
-CLASS="filename"
->FollowSymLinks</TT
->
-        directive to the <TT
+>Load <TT
 CLASS="filename"
->&#60;Directory&#62;</TT
-> entry for 
-        the HTML root directory in httpd.conf.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="caution"
+>httpd.conf</TT
+> in your editor.</P
 ><P
-></P
+>Uncomment (or add) the following line. 
+          This configures Apache to run .cgi files outside the
+          <TT
+CLASS="filename"
+>cgi-bin</TT
+> directory.
+          </P
 ><TABLE
-CLASS="caution"
-WIDTH="100%"
 BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
 ><TR
 ><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The default Bugzilla distribution is not designed to be placed
-        in a <TT
-CLASS="filename"
->cgi-bin</TT
-> directory (this
-        includes any directory which is configured using the
-        <TT
-CLASS="option"
->ScriptAlias</TT
-> directive of Apache).
-        </P
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>  AddHandler cgi-script .cgi</PRE
+></FONT
 ></TD
 ></TR
 ></TABLE
-></DIV
 ><P
->Once all the files are in a web accessible directory, make that
-      directory writable by your webserver's user. This is a temporary step
-      until you run the post-install 
-      <TT
-CLASS="filename"
->checksetup.pl</TT
+>Apache uses <TT
+CLASS="computeroutput"
+>&#60;Directory&#62;</TT
 >
-      script, which locks down your installation.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN522"
-></A
->4.1.5. <TT
-CLASS="filename"
->checksetup.pl</TT
-></H2
-><P
->Next, run the magic checksetup.pl script. 
-      This is designed to check whether you have all of the right
-      Perl modules in the correct
-      versions, and that Bugzilla is generally set up correctly. 
-      </P
-><P
->&#13;      Eventually, 
-      it will make sure Bugzilla files and directories have reasonable
-      permissions, set up the 
-      <TT
-CLASS="filename"
->data</TT
+          directives to permit fine-grained permission setting.
+          Add the following two lines to a 
+          <TT
+CLASS="computeroutput"
+>&#60;Directory&#62;</TT
+> directive that 
+          applies either to the Bugzilla directory or one of its parents
+          (e.g. the <TT
+CLASS="computeroutput"
+>&#60;Directory /var/www/html&#62;</TT
 >
-      directory, and create all the MySQL tables. But the first time you
-      run it, it's highly likely to tell you that you are missing a few
-      Perl modules. Make a note of which ones they are, and then proceed to
-      the next section to install them.
-      </P
+          directive).
+          This allows Bugzilla's <TT
+CLASS="filename"
+>.htaccess</TT
+> files to 
+          override global permissions, and allows .cgi files to run in the 
+          Bugzilla directory.
+          </P
 ><TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
@@ -740,879 +597,191 @@ WIDTH="100%"
 ><FONT
 COLOR="#000000"
 ><PRE
-CLASS="screen"
->&#13;<TT
-CLASS="prompt"
->bash#</TT
-> ./checksetup.pl
-      </PRE
+CLASS="programlisting"
+>  Options +ExecCGI +FollowSymLinks
+  AllowOverride Limit</PRE
 ></FONT
 ></TD
 ></TR
 ></TABLE
 ><P
->&#13;      The first time you run it with all the correct modules installed, 
-      it will create a file called 
-      <TT
+>Add <TT
 CLASS="filename"
->localconfig</TT
->.</P
-><P
->This file contains a variety of settings you may need to tweak
-      including how Bugzilla should connect to the MySQL database.</P
-><P
->The connection settings include: 
-      <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->server's host: just use 
-          <SPAN
-CLASS="QUOTE"
->"localhost"</SPAN
->
-          if the MySQL server is local</P
-></LI
-><LI
-><P
->database name: 
-          <SPAN
-CLASS="QUOTE"
->"bugs_db"</SPAN
->
-          if you're following these directions</P
-></LI
-><LI
-><P
->MySQL username: 
-          <SPAN
-CLASS="QUOTE"
->"bugs_user"</SPAN
->
-          if you're following these directions</P
-></LI
-><LI
+>index.cgi</TT
+> to the end
+          of the <TT
+CLASS="computeroutput"
+>DirectoryIndex</TT
+> 
+          line.</P
 ><P
->Password for the 
-          <SPAN
-CLASS="QUOTE"
->"bugs_user"</SPAN
->
-          MySQL account; (<SPAN
-CLASS="QUOTE"
->"bugs_password"</SPAN
-> above)</P
-></LI
-></OL
+><TT
+CLASS="filename"
+>checksetup.pl</TT
+> can set tighter permissions
+          on Bugzilla's files and directories if it knows what user the
+          webserver runs as. Look for the <TT
+CLASS="computeroutput"
+>User</TT
 >
-      </P
-><P
->Edit the file to change these. Once you are happy with the 
-      settings, <TT
+          line in <TT
+CLASS="filename"
+>httpd.conf</TT
+>, and place that value in
+          the <TT
+CLASS="replaceable"
+><I
+>$webservergroup</I
+></TT
+> variable in
+          <TT
 CLASS="filename"
->su</TT
-> to the user
-      your web server runs as, and re-run 
-      <TT
+>localconfig</TT
+>. Then rerun
+          <TT
 CLASS="filename"
 >checksetup.pl</TT
->. (Note: on some security-conscious
-      systems, you may need to change the login shell for the webserver 
-      account before you can do this.)
-      On this second run, it will create the database and an administrator
-      account for which you will be prompted to provide information.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The checksetup.pl script is designed so that you can run it at
-        any time without causing harm. You should run it after any upgrade to
-        Bugzilla.</P
-></TD
-></TR
-></TABLE
-></DIV
+>.
+          </P
 ></DIV
 ><DIV
 CLASS="section"
-><H2
+><H3
 CLASS="section"
 ><A
-NAME="install-perlmodules"
+NAME="http-iis"
 ></A
->4.1.6. Perl Modules</H2
-><P
->Don't be intimidated by this long list of modules. See
-      <A
-HREF="stepbystep.html#install-modules-bundle-bugzilla"
->Section 4.1.6.1</A
-> for a way of 
-      installing all the ones you need with a single command.
-      </P
+>2.2.4.2. Microsoft <SPAN
+CLASS="productname"
+>Internet Information Services</SPAN
+></H3
 ><P
->Perl modules can be found using
-      <A
-HREF="glossary.html#gloss-cpan"
-><I
-CLASS="glossterm"
->CPAN</I
-></A
-> on Unix based systems or
-      <A
-HREF="glossary.html#gloss-ppm"
-><I
-CLASS="glossterm"
->PPM</I
-></A
-> on Win32.
-      </P
+>If you need, or for some reason even want, to use Microsoft's
+        <SPAN
+CLASS="productname"
+>Internet Information Services</SPAN
+> or
+        <SPAN
+CLASS="productname"
+>Personal Web Server</SPAN
+> you should be able
+        to. You will need to configure them to know how to run CGI scripts.
+        This is described in Microsoft Knowledge Base article
+        <A
+HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp"
+TARGET="_top"
+>Q245225</A
+>
+        for <SPAN
+CLASS="productname"
+>Internet Information Services</SPAN
+> and
+        <A
+HREF="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp"
+TARGET="_top"
+>Q231998</A
+>          
+        for <SPAN
+CLASS="productname"
+>Personal Web Server</SPAN
+>.
+        </P
 ><P
->Good instuctions can be found for using each of these services on
-      their respective websites. The basics can be found in
-      <A
-HREF="stepbystep.html#install-perlmodules-cpan"
->Example 4-1</A
-> for CPAN and
-      <A
-HREF="os-specific.html#win32-perlmodules"
->Section 4.4.1.2</A
-> for PPM.
-      </P
+>Also, and this can't be stressed enough, make sure that files such as
+        <TT
+CLASS="filename"
+>localconfig</TT
+> and your <TT
+CLASS="filename"
+>data</TT
+>
+        directory are secured as described in <A
+HREF="configuration.html#security-access"
+>Section 2.2.4.4</A
+>.
+        </P
+></DIV
 ><DIV
-CLASS="example"
+CLASS="section"
+><H3
+CLASS="section"
 ><A
-NAME="install-perlmodules-cpan"
+NAME="http-aol"
 ></A
+>2.2.4.3. AOL Server</H3
 ><P
-><B
->Example 4-1. Installing perl modules with CPAN</B
-></P
+>Ben FrantzDale reported success using AOL Server with Bugzilla. He
+        reported his experience and what appears below is based on that.
+        </P
 ><P
->The easy way:
-          <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="screen"
->&#13;<TT
-CLASS="prompt"
->bash#</TT
-> perl -MCPAN -e 'install "&#60;modulename&#62;"'
-          </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
+>AOL Server will have to be configured to run
+        <A
+HREF="glossary.html#gloss-cgi"
+><I
+CLASS="glossterm"
+>CGI</I
+></A
+> scripts, please consult
+        the documentation that came with your server for more information on
+        how to do this.
         </P
 ><P
->Or the hard way:
-          <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="screen"
->&#13;<TT
-CLASS="prompt"
->bash#</TT
-> tar xzvf &#60;module&#62;.tar.gz     <A
-NAME="cpan-moduletar"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
->
-<TT
-CLASS="prompt"
->bash#</TT
-> cd &#60;module&#62;                  <A
-NAME="cpan-moduledir"
-><IMG
-SRC="../images/callouts/2.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(2)"></A
->
-<TT
-CLASS="prompt"
->bash#</TT
-> perl Makefile.PL
-<TT
-CLASS="prompt"
->bash#</TT
-> make
-<TT
-CLASS="prompt"
->bash#</TT
-> make test
-<TT
-CLASS="prompt"
->bash#</TT
-> make install
-          </PRE
-></FONT
-></TD
-></TR
-></TABLE
->
-          <DIV
-CLASS="calloutlist"
-><DL
-COMPACT="COMPACT"
-><DT
-><A
-HREF="stepbystep.html#cpan-moduletar"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
-></DT
-><DD
->This assumes that you've already downloaded the
-              <TT
-CLASS="filename"
->&#60;module&#62;.tar.gz</TT
-> to the current working
-              directory.
-              </DD
-><DT
-><A
-HREF="stepbystep.html#cpan-moduledir"
-><IMG
-SRC="../images/callouts/2.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(2)"></A
-></DT
-><DD
->The process of untarring the module as defined in
-              <A
-HREF="stepbystep.html#cpan-moduletar"
-><A
-HREF="stepbystep.html#cpan-moduletar"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
-></A
-> will create the
-              <TT
+>Because AOL Server doesn't support <TT
 CLASS="filename"
->&#60;module&#62;</TT
-> directory.
-              </DD
-></DL
-></DIV
->
-        </P
-></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Many people complain that Perl modules will not install for
-        them. Most times, the error messages complain that they are missing a
-        file in 
-        <SPAN
-CLASS="QUOTE"
->"@INC"</SPAN
->. 
-        Virtually every time, this error is due to permissions being set too
-        restrictively for you to compile Perl modules or not having the
-        necessary Perl development libraries installed on your system.
-        Consult your local UNIX systems administrator for help solving these
-        permissions issues; if you 
-        <EM
->are</EM
->
-        the local UNIX sysadmin, please consult the newsgroup/mailing list
-        for further assistance or hire someone to help you out.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Perl Modules (minimum version):
-      <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-bundle-bugzilla"
->Bundle::Bugzilla</A
->
-            (Will allow you to skip the rest)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-cgi"
->CGI</A
-> 
-            (2.88)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-date-format"
->Date::Format</A
+>.htaccess</TT
 >
-            (2.21)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-dbi"
->DBI</A
-> 
-            (1.32)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-dbd-mysql"
->DBD::mysql</A
->
-            (2.1010)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-file-spec"
->File::Spec</A
->
-            (0.82)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-file-temp"
->File::Temp</A
->
-            (any)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-template"
->Template Toolkit</A
->
-            (2.08)
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-text-wrap"
->Text::Wrap</A
-> 
-            (2001.0131)
-          </P
-></LI
-></OL
->
-
-      and, optionally:
-      <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-gd"
->GD</A
->
-            (1.20) for bug charting
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-chart-base"
->Chart::Base</A
->
-            (0.99c) for bug charting
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-xml-parser"
->XML::Parser</A
->
-            (any) for the XML interface
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-gd-graph"
->GD::Graph</A
->
-            (any) for bug charting
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-gd-text-align"
->GD::Text::Align</A
->
-            (any) for bug charting
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-mime-parser"
->MIME::Parser</A
->
-            (any) for the email interface
-          </P
-></LI
-><LI
-><P
->&#13;            <A
-HREF="stepbystep.html#install-modules-patchreader"
->PatchReader</A
->
-            (0.9.1) for pretty HTML view of patches
-          </P
-></LI
-></OL
->          
-      </P
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-bundle-bugzilla"
-></A
->4.1.6.1. Bundle::Bugzilla</H3
-><P
->If you are running at least perl 5.6.1, you can save yourself a lot
-      of time by using Bundle::Bugzilla. This bundle contains every module
-      required to get Bugzilla running. It does not include GD and friends, but
-      these are not required for a base install and can always be added later
-      if the need arises.
-      </P
-><P
->Assuming your perl was installed with CPAN (most unix installations
-      are), using Bundle::Bugzilla is really easy. Simply follow along with the
-      commands below.
-      </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="screen"
->&#13;<TT
-CLASS="prompt"
->bash#</TT
-> <B
-CLASS="command"
->perl -MCPAN -eshell</B
->              <A
-NAME="bundle-cpanconfig"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
->
-cpan shell -- CPAN exploration and modules installation (v1.63)
-ReadLine support enabled
-
-<TT
-CLASS="prompt"
->cpan&#62;</TT
->
-
-        </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="calloutlist"
-><DL
-COMPACT="COMPACT"
-><DT
-><A
-HREF="stepbystep.html#bundle-cpanconfig"
-><IMG
-SRC="../images/callouts/1.gif"
-HSPACE="0"
-VSPACE="0"
-BORDER="0"
-ALT="(1)"></A
-></DT
-><DD
->At this point, unless you've used CPAN on this machine before,
-            you'll have to go through a series of configuration steps.
-            </DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-cgi"
-></A
->4.1.6.2. CGI (2.88)</H3
-><P
->The CGI module parses form elements and cookies and does many
-      other usefule things. It come as a part of recent perl distributions, but
-      Bugzilla needs a fairly new version.
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/CGI.pm/"
-TARGET="_top"
->http://search.cpan.org/dist/CGI.pm/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/CGI.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/CGI.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.perldoc.com/perl5.8.0/lib/CGI.html"
-TARGET="_top"
->http://www.perldoc.com/perl5.8.0/lib/CGI.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-date-format"
-></A
->4.1.6.3. TimeDate modules (2.21)</H3
-><P
->Many of the more common date/time/calendar related Perl modules
-      have been grouped into a bundle similar to the MySQL modules bundle.
-      This bundle is stored on the CPAN under the name TimeDate. 
-      The component module we're most interested in is the Date::Format
-      module, but installing all of them is probably a good idea anyway.
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/TimeDate/"
-TARGET="_top"
->http://search.cpan.org/dist/TimeDate/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/TimeDate.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/TimeDate.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm"
-TARGET="_top"
->http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-dbi"
-></A
->4.1.6.4. DBI (1.32)</H3
-><P
->The DBI module is a generic Perl module used the
-      MySQL-related modules. As long as your Perl installation was done
-      correctly the DBI module should be a breeze. It's a mixed Perl/C
-      module, but Perl's MakeMaker system simplifies the C compilation
-      greatly.</P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/DBI/"
-TARGET="_top"
->http://search.cpan.org/dist/DBI/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBI.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBI.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://dbi.perl.org/doc/"
-TARGET="_top"
->http://dbi.perl.org/doc/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-dbd-mysql"
-></A
->4.1.6.5. MySQL-related modules</H3
-><P
->The Perl/MySQL interface requires a few mutually-dependent Perl
-      modules. These modules are grouped together into the the
-      Msql-Mysql-modules package.</P
-><P
->The MakeMaker process will ask you a few questions about the
-      desired compilation target and your MySQL installation. For most of the
-      questions the provided default will be adequate, but when asked if your
-      desired target is the MySQL or mSQL packages, you should
-      select the MySQL related ones. Later you will be asked if you wish to
-      provide backwards compatibility with the older MySQL packages; you
-      should answer YES to this question. The default is NO.</P
-><P
->A host of 'localhost' should be fine and a testing user of 'test'
-      with a null password should find itself with sufficient access to run
-      tests on the 'test' database which MySQL created upon installation.
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/DBD-mysql/"
-TARGET="_top"
->http://search.cpan.org/dist/DBD-mysql/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBD-Mysql.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBD-Mysql.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pod"
-TARGET="_top"
->http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pod</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-file-spec"
-></A
->4.1.6.6. File::Spec (0.82)</H3
-><P
->File::Spec is a perl module that allows file operations, such as
-      generating full path names, to work cross platform.
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/File-Spec/"
-TARGET="_top"
->http://search.cpan.org/dist/File-Spec/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.perldoc.com/perl5.8.0/lib/File/Spec.html"
-TARGET="_top"
->http://www.perldoc.com/perl5.8.0/lib/File/Spec.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-file-temp"
-></A
->4.1.6.7. File::Temp (any)</H3
-><P
->File::Temp is used to generate a temporary filename that is
-      guaranteed to be unique. It comes as a standard part of perl
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/File-Spec/"
-TARGET="_top"
->http://search.cpan.org/dist/File-Spec/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.perldoc.com/perl5.8.0/lib/File/Temp.html"
-TARGET="_top"
->http://www.perldoc.com/perl5.8.0/lib/File/Temp.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-template"
-></A
->4.1.6.8. Template Toolkit (2.08)</H3
-><P
->When you install Template Toolkit, you'll get asked various
-      questions about features to enable. The defaults are fine, except
-      that it is recommended you use the high speed XS Stash of the Template
-      Toolkit, in order to achieve best performance.
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/Template-Toolkit/"
-TARGET="_top"
->http://search.cpan.org/dist/Template-Toolkit/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://openinteract.sourceforge.net/ppmpackages/5.6/Template-Toolkit.tar.gz"
-TARGET="_top"
->http://openinteract.sourceforge.net/ppmpackages/5.6/Template-Toolkit.tar.gz</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.template-toolkit.org/docs.html"
-TARGET="_top"
->http://www.template-toolkit.org/docs.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-text-wrap"
-></A
->4.1.6.9. Text::Wrap (2001.0131)</H3
-><P
->Text::Wrap is designed to proved intelligent text wrapping.
-      </P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/Text-Tabs+Wrap/"
-TARGET="_top"
->http://search.cpan.org/dist/Text-Tabs+Wrap/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.perldoc.com/perl5.8.0/lib/Text/Wrap.html"
-TARGET="_top"
->http://www.perldoc.com/perl5.8.0/lib/Text/Wrap.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-gd"
+        files, you'll have to create a <A
+HREF="glossary.html#gloss-tcl"
+><I
+CLASS="glossterm"
+>TCL</I
 ></A
->4.1.6.10. GD (1.20) [optional]</H3
-><P
->You need the GD library if you want any of the graphing to work.
-      </P
+>
+        script. You should create an <TT
+CLASS="filename"
+>aolserver/modules/tcl/filter.tcl</TT
+>
+        file (the filename shouldn't matter) with the following contents (change
+        <TT
+CLASS="computeroutput"
+>/bugzilla/</TT
+> to the web-based path to
+        your Bugzilla installation):
+        </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>&#13;  ns_register_filter preauth GET /bugzilla/localconfig filter_deny
+  ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny
+  ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny
+  ns_register_filter preauth GET /bugzilla/*.pl filter_deny
+  ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
+  ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
+  ns_register_filter preauth GET /bugzilla/data/* filter_deny
+  ns_register_filter preauth GET /bugzilla/template/* filter_deny
+
+  proc filter_deny { why } {
+      ns_log Notice "filter_deny"
+      return "filter_return"
+  }
+        </PRE
+></FONT
+></TD
+></TR
+></TABLE
 ><DIV
-CLASS="note"
+CLASS="warning"
 ><P
 ></P
 ><TABLE
-CLASS="note"
+CLASS="warning"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -1621,37 +790,39 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="../images/note.gif"
+SRC="../images/warning.gif"
 HSPACE="5"
-ALT="Note"></TD
+ALT="Warning"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->The Perl GD library requires some other libraries that may or
-        may not be installed on your system, including 
-        <TT
-CLASS="classname"
->libpng</TT
->
-        and 
-        <TT
-CLASS="classname"
->libgd</TT
->. 
-        The full requirements are listed in the Perl GD library README.
-        If compiling GD fails, it's probably because you're
-        missing a required library.</P
+>This probably doesn't account for all possible editor backup
+          files so you may wish to add some additional variations of
+          <TT
+CLASS="filename"
+>localconfig</TT
+>. For more information, see 
+          <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
+TARGET="_top"
+>&#13;          bug 186383</A
+> or <A
+HREF="http://online.securityfocus.com/bid/6501"
+TARGET="_top"
+>Bugtraq ID 6501</A
+>.
+          </P
 ></TD
 ></TR
 ></TABLE
 ></DIV
 ><DIV
-CLASS="tip"
+CLASS="note"
 ><P
 ></P
 ><TABLE
-CLASS="tip"
+CLASS="note"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -1660,247 +831,277 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="../images/tip.gif"
+SRC="../images/note.gif"
 HSPACE="5"
-ALT="Tip"></TD
+ALT="Note"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->The version of the GD perl module you need is very closely tied
-        to the <TT
-CLASS="classname"
->libgd</TT
-> version installed on your system.
-        If you have a version 1.x of <TT
-CLASS="classname"
->libgd</TT
-> the 2.x
-        versions of the GD perl module won't work for you.
-       </P
+>If you are using webdot from research.att.com (the default
+          configuration for the <TT
+CLASS="option"
+>webdotbase</TT
+> paramater), you
+          will need to allow access to <TT
+CLASS="filename"
+>data/webdot/*.dot</TT
+>
+          for the reasearch.att.com machine.
+          </P
+><P
+>If you are using a local installation of <A
+HREF="http://www.graphviz.org"
+TARGET="_top"
+>GraphViz</A
+>, you will need to allow
+          everybody to access <TT
+CLASS="filename"
+>*.png</TT
+>,
+          <TT
+CLASS="filename"
+>*.gif</TT
+>, <TT
+CLASS="filename"
+>*.jpg</TT
+>, and
+          <TT
+CLASS="filename"
+>*.map</TT
+> in the
+          <TT
+CLASS="filename"
+>data/webdot</TT
+> directory.
+          </P
 ></TD
 ></TR
 ></TABLE
 ></DIV
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/GD/"
-TARGET="_top"
->http://search.cpan.org/dist/GD/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GD.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GD.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://stein.cshl.org/WWW/software/GD/"
-TARGET="_top"
->http://stein.cshl.org/WWW/software/GD/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-chart-base"
-></A
->4.1.6.11. Chart::Base (0.99c) [optional]</H3
-><P
->The Chart module provides Bugzilla with on-the-fly charting
-      abilities. It can be installed in the usual fashion after it has been
-      fetched from CPAN. 
-      Note that earlier versions that 0.99c used GIFs, which are no longer
-      supported by the latest versions of GD.</P
-><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/Chart/"
-TARGET="_top"
->http://search.cpan.org/dist/Chart/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Chart.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Chart.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
 ></DIV
 ><DIV
 CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="install-modules-xml-parser"
+NAME="security-access"
 ></A
->4.1.6.12. XML::Parser (any) [optional]</H3
+>2.2.4.4. Web Server Access Controls</H3
+><P
+>Users of Apache can skip this section because
+        Bugzilla ships with <TT
+CLASS="filename"
+>.htaccess</TT
+> files which 
+        restrict access in the manner required. 
+        Users of other webservers, read on.
+        </P
+><P
+>There are several files in the Bugzilla directory
+        that should not be accessible from the web. You need to configure
+        your webserver so they they aren't. Not doing this may reveal
+        sensitive information such as database passwords.
+        </P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>In the main Bugzilla directory, you should:</P
 ><P
->XML::Parser is used by the <TT
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block:
+                <TT
 CLASS="filename"
->importxml.pl</TT
+>*.pl</TT
+>, <TT
+CLASS="filename"
+>*localconfig*</TT
+>, <TT
+CLASS="filename"
+>runtests.sh</TT
 >
-      script. You only need it if you are going to be importing bugs (such as
-      for bug moving).  XML::Parser requires that the
-      <TT
-CLASS="classname"
->expat</TT
-> library is already installed on your machine.
-      </P
+                </P
+></LI
+><LI
 ><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/XML-Parser/"
-TARGET="_top"
->http://search.cpan.org/dist/XML-Parser/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.perldoc.com/perl5.6.1/lib/XML/Parser.html"
-TARGET="_top"
->http://www.perldoc.com/perl5.6.1/lib/XML/Parser.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-gd-graph"
-></A
->4.1.6.13. GD::Graph (any) [optional]</H3
+>But allow:
+                <TT
+CLASS="filename"
+>localconfig.js</TT
+>, <TT
+CLASS="filename"
+>localconfig.rdf</TT
+>
+                </P
+></LI
+></UL
+></LI
+><LI
 ><P
->In addition to GD listed above, the reporting interface of Bugzilla
-      needs to have the GD::Graph module installed.
-      </P
+>In <TT
+CLASS="filename"
+>data</TT
+>:</P
 ><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/GDGraph/"
-TARGET="_top"
->http://search.cpan.org/dist/GDGraph/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDGraph.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDGraph.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://search.cpan.org/dist/GDGraph/Graph.pm"
-TARGET="_top"
->http://search.cpan.org/dist/GDGraph/Graph.pm</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-gd-text-align"
-></A
->4.1.6.14. GD::Text::Align (any) [optional]</H3
+></P
+><UL
+COMPACT="COMPACT"
+><LI
 ><P
->GD::Text::Align, as the name implies, is used to draw aligned
-      strings of text. It is needed by the reporting interface.
-      </P
+>Block everything</P
+></LI
+><LI
 ><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/GDTextUtil/"
-TARGET="_top"
->http://search.cpan.org/dist/GDTextUtil/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDTextUtil.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDTextUtil.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://search.cpan.org/dist/GDTextUtil/Text/Align.pm"
-TARGET="_top"
->http://search.cpan.org/dist/GDTextUtil/Text/Align.pm</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-mime-parser"
-></A
->4.1.6.15. MIME::Parser (any) [optional]</H3
+>But allow:
+                <TT
+CLASS="filename"
+>duplicates.rdf</TT
+>
+                </P
+></LI
+></UL
+></LI
+><LI
 ><P
->MIME::Parser is only needed if you want to use the e-mail interface
-      located in the <TT
+>In <TT
 CLASS="filename"
->contrib</TT
-> directory.
-      </P
+>data/webdot</TT
+>:</P
 ><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/dist/MIME-tools/"
-TARGET="_top"
->http://search.cpan.org/dist/MIME-tools/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
-HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/MIME-tools.zip"
-TARGET="_top"
->http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/MIME-tools.zip</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm"
-TARGET="_top"
->http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="install-modules-patchreader"
-></A
->4.1.6.16. PatchReader (0.9.1) [optional]</H3
-><P
->PatchReader is only needed if you want to use Patch Viewer, a
-      Bugzilla feature to format patches in a pretty HTML fashion.  There are a
-      number of optional parameters you can configure Patch Viewer with as well,
-      including cvsroot, cvsroot_get, lxr_root, bonsai_url, lxr_url, and
-      lxr_root.  Patch Viewer also optionally will use cvs, diff and interdiff
-      utilities if they exist on the system (interdiff can be found in the
-      patchutils package at <A
-HREF="http://cyberelk.net/tim/patchutils/"
-TARGET="_top"
->http://cyberelk.net/tim/patchutils/</A
->.
-      These programs' locations can be configured in localconfig.
-      </P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
 ><P
-CLASS="literallayout"
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
-HREF="http://search.cpan.org/author/JKEISER/PatchReader/"
-TARGET="_top"
->http://search.cpan.org/author/JKEISER/PatchReader/</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
-HREF="http://www.johnkeiser.com/mozilla/Patch_Viewer.html"
+>If you use a remote webdot server:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow
+                    <TT
+CLASS="filename"
+>*.dot</TT
+>
+                    only for the remote webdot server</P
+></LI
+></UL
+></LI
+><LI
+><P
+>Otherwise, if you use a local GraphViz:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+><LI
+><P
+>But allow:
+                    <TT
+CLASS="filename"
+>*.png</TT
+>, <TT
+CLASS="filename"
+>*.gif</TT
+>, <TT
+CLASS="filename"
+>*.jpg</TT
+>, <TT
+CLASS="filename"
+>*.map</TT
+>
+                    </P
+></LI
+></UL
+></LI
+><LI
+><P
+>And if you don't use any dot:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>Bugzilla</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+><LI
+><P
+>In <TT
+CLASS="filename"
+>template</TT
+>:</P
+><P
+></P
+><UL
+COMPACT="COMPACT"
+><LI
+><P
+>Block everything</P
+></LI
+></UL
+></LI
+></UL
+><P
+>You should test to make sure that the files mentioned above are
+        not accessible from the Internet, especially your
+        <TT
+CLASS="filename"
+>localconfig</TT
+> file which contains your database
+        password. To test, simply point your web browser at the file; for
+        example, to test mozilla.org's installation, we'd try to access
+        <A
+HREF="http://bugzilla.mozilla.org/localconfig"
 TARGET="_top"
->http://www.johnkeiser.com/mozilla/Patch_Viewer.html</A
-><br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>http://bugzilla.mozilla.org/localconfig</A
+>. You should
+        get a <SPAN
+CLASS="errorcode"
+>403</SPAN
+> <SPAN
+CLASS="errorname"
+>Forbidden</SPAN
+>
+        error.
+        </P
 ></DIV
 ></DIV
 ><DIV
@@ -1908,20 +1109,71 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN768"
+NAME="install-config-bugzilla"
 ></A
->4.1.7. Configuring Bugzilla</H2
+>2.2.5. Bugzilla</H2
 ><P
->&#13;      Once checksetup.pl has run successfully, Bugzilla should start up.
-      Proceed to the correct URL and log in with the administrator account
-      you defined in the last checksetup.pl run.
+>&#13;        Your Bugzilla should now be working. Access 
+        <TT
+CLASS="filename"
+>http://&#60;your-bugzilla-server&#62;/</TT
+> - 
+        you should see the Bugzilla
+        front page. If not, consult the Troubleshooting section,
+        <A
+HREF="troubleshooting.html"
+>Section 2.5</A
+>.
       </P
 ><P
->&#13;      You should run through the parameters on the Edit Parameters page
-      (link in the footer) and set them all to appropriate values. 
-      They key parameters are documented in <A
+>&#13;        Log in with the administrator account you defined in the last 
+        <TT
+CLASS="filename"
+>checksetup.pl</TT
+> run. You should go through 
+        the parameters on the Edit Parameters page
+        (see link in the footer) and see if there are any you wish to
+        change. 
+        They key parameters are documented in <A
 HREF="parameters.html"
->Section 5.1</A
+>Section 3.1</A
+>;
+        you should certainly alter 
+        <B
+CLASS="command"
+>maintainer</B
+> and <B
+CLASS="command"
+>urlbase</B
+>; 
+        you may also want to alter 
+        <B
+CLASS="command"
+>cookiepath</B
+> or <B
+CLASS="command"
+>requirelogin</B
+>.
+      </P
+><P
+>&#13;        This would also be a good time to revisit the
+        <TT
+CLASS="filename"
+>localconfig</TT
+> file and make sure that the 
+        names of the priorities, severities, platforms and operating systems
+        are those you wish to use when you start creating bugs. Remember
+        to rerun <TT
+CLASS="filename"
+>checksetup.pl</TT
+> if you change it.
+      </P
+><P
+>&#13;        Bugzilla has several optional features which require extra 
+        configuration. You can read about those in
+        <A
+HREF="extraconfig.html"
+>Section 2.3</A
 >.
       </P
 ></DIV
@@ -1960,7 +1212,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="http.html"
+HREF="extraconfig.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -1976,7 +1228,7 @@ WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="installation.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="U"
 >Up</A
 ></TD
@@ -1984,7 +1236,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->HTTP Server Configuration</TD
+>Optional Additional Configuration</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/conventions.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -17,8 +17,8 @@ REL="PREVIOUS"
 TITLE="Credits"
 HREF="credits.html"><LINK
 REL="NEXT"
-TITLE="Introduction"
-HREF="introduction.html"></HEAD
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -61,7 +61,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="introduction.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -83,7 +83,7 @@ NAME="conventions"
 ><DIV
 CLASS="informaltable"
 ><A
-NAME="AEN72"
+NAME="AEN83"
 ></A
 ><P
 ></P
@@ -438,7 +438,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="introduction.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -462,7 +462,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Introduction</TD
+>Installing Bugzilla</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/copyright.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -78,23 +78,14 @@ CLASS="section"
 NAME="copyright"
 ></A
 >1.1. Copyright Information</H1
+><P
+>This document is copyright (c) 2000-2004 by the various
+    Bugzilla contributors who wrote it.</P
 ><A
-NAME="AEN25"
+NAME="AEN26"
 ></A
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
+><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
-><TR
-><TD
-WIDTH="10%"
-VALIGN="TOP"
->&nbsp;</TD
-><TD
-WIDTH="80%"
-VALIGN="TOP"
 ><P
 >&#13;	Permission is granted to copy, distribute and/or modify this
 	document under the terms of the GNU Free Documentation
@@ -103,29 +94,10 @@ VALIGN="TOP"
 	Front-Cover Texts, and with no Back-Cover Texts. A copy of
 	the license is included in <A
 HREF="gfdl.html"
->Appendix C</A
+>Appendix D</A
 >.
       </P
-></TD
-><TD
-WIDTH="10%"
-VALIGN="TOP"
->&nbsp;</TD
-></TR
-><TR
-><TD
-COLSPAN="2"
-ALIGN="RIGHT"
-VALIGN="TOP"
->--<SPAN
-CLASS="attribution"
->Copyright (c) 2000-2004 The Bugzilla Team</SPAN
-></TD
-><TD
-WIDTH="10%"
->&nbsp;</TD
-></TR
-></TABLE
+></BLOCKQUOTE
 ><P
 >&#13;      If you have any questions regarding this document, its
       copyright, or publishing this document in non-electronic form,

docs/html/credits.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -88,7 +88,7 @@ NAME="credits"
 >&#13;      Matthew P. Barnson, Kevin Brannen, Dawn Endico, Ben FrantzDale, Eric Hanson, Tara Hernandez, Dave Lawrence, Zach Lipton, Gervase Markham, Andrew Pearson, Joe Robins, Spencer Smith, Jacob Steenhagen, Ron Teitelbaum, Terry Weissman, Martin Wulffeld.
     </P
 ><P
->&#13;      Last but not least, all the members of the 
+>&#13;      Also, thanks are due to the members of the 
       <A
 HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
 TARGET="_top"

docs/html/cust-change-permissions.html

@@ -7,15 +7,15 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="Customising Bugzilla"
 HREF="customization.html"><LINK
 REL="PREVIOUS"
-TITLE="Template Customization"
-HREF="cust-templates.html"><LINK
+TITLE="Template Hooks"
+HREF="cust-hooks.html"><LINK
 REL="NEXT"
 TITLE="Modifying Your Running System"
 HREF="dbmodify.html"></HEAD
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -47,7 +47,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="cust-templates.html"
+HREF="cust-hooks.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 6. Customising Bugzilla</TD
+>Chapter 4. Customising Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="cust-change-permissions"
 ></A
->6.2. Customizing Who Can Change What</H1
+>4.3. Customizing Who Can Change What</H1
 ><DIV
 CLASS="warning"
 ><P
@@ -258,7 +258,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="cust-templates.html"
+HREF="cust-hooks.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -286,7 +286,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Template Customization</TD
+>Template Hooks</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"

docs/html/cust-hooks.html

+<HTML
+><HEAD
+><TITLE
+>Template Hooks</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.17.7 
+    Development Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Customising Bugzilla"
+HREF="customization.html"><LINK
+REL="PREVIOUS"
+TITLE="Template Customization"
+HREF="cust-templates.html"><LINK
+REL="NEXT"
+TITLE="Customizing Who Can Change What"
+HREF="cust-change-permissions.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.17.7 
+    Development Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="cust-templates.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 4. Customising Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="cust-change-permissions.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="cust-hooks"
+></A
+>4.2. Template Hooks</H1
+><P
+>&#13;      Template hooks are a way for extensions to Bugzilla to insert code
+      into the standard Bugzilla templates without modifying the template files
+      themselves.  The hooks mechanism defines a consistent API for extending
+      the standard templates in a way that cleanly separates standard code
+      from extension code.  Hooks reduce merge conflicts and make it easier
+      to write extensions that work across multiple versions of Bugzilla,
+      making upgrading a Bugzilla installation with installed extensions easier.
+    </P
+><P
+>&#13;      A template hook is just a named place in a standard template file
+      where extension template files for that hook get processed.  Each hook
+      has a corresponding directory in the Bugzilla directory tree.  Hooking an
+      extension template to a hook is as simple as putting the extension file
+      into the hook's directory.  When Bugzilla processes the standard template
+      and reaches the hook, it will process all extension templates in the
+      hook's directory. The hooks themselves can be added into any standard
+      template upon request by extension authors.
+    </P
+><P
+>&#13;      To use hooks to extend a Bugzilla template, first make sure there is
+      a hook at the appropriate place within the template you want to extend. 
+      Hooks appear in the standard Bugzilla templates as a single directive
+      in the format
+      <TT
+CLASS="literal"
+>[% Hook.process("<TT
+CLASS="varname"
+>name</TT
+>") %]</TT
+>,
+      where <TT
+CLASS="varname"
+>name</TT
+> is the unique (within that template)
+      name of the hook.
+    </P
+><P
+>&#13;      If you aren't sure which template you want to extend or just want
+      to browse the available hooks, either use your favorite multi-file search
+      tool (e.g. <B
+CLASS="command"
+>grep</B
+>) to search the standard templates
+      for occurrences of <TT
+CLASS="methodname"
+>Hook.process</TT
+> or browse
+      the directory tree in
+      <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/extension/hook/</TT
+>,
+      which contains a directory for each hook in the following location:
+    </P
+><P
+>&#13;      <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/extension/hook/PATH_TO_STANDARD_TEMPLATE/STANDARD_TEMPLATE_NAME/HOOK_NAME/</TT
+>
+    </P
+><P
+>&#13;      If there is no hook at the appropriate place within the Bugzilla template
+      you want to extend,
+      <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=User%20Interface"
+TARGET="_top"
+>file
+      a bug requesting one</A
+>, specifying:
+    </P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>the template for which you are requesting a hook;</TD
+></TR
+><TR
+><TD
+>&#13;        where in the template you would like the hook to be placed
+        (line number/position for latest version of template in CVS
+        or description of location);
+      </TD
+></TR
+><TR
+><TD
+>the purpose of the hook;</TD
+></TR
+><TR
+><TD
+>a link to information about your extension, if any.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+>&#13;      The Bugzilla reviewers will promptly review each hook request,
+      name the hook, add it to the template, check the new version
+      of the template into CVS, and create the corresponding directory in
+      <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/extension/hook/</TT
+>.
+    </P
+><P
+>&#13;      You may optionally attach a patch to the bug which implements the hook
+      and check it in yourself after receiving approval from a Bugzilla
+      reviewer.  The developers may suggest changes to the location of the
+      hook based on their analysis of your needs or so the hook can satisfy
+      the needs of multiple extensions, but the process of getting hooks
+      approved and checked in is not as stringent as the process for general
+      changes to Bugzilla, and any extension, whether released or still in
+      development, can have hooks added to meet their needs.
+    </P
+><P
+>&#13;      After making sure the hook you need exists (or getting it added if not),
+      add your extension template to the directory within the Bugzilla
+      directory tree corresponding to the hook. 
+    </P
+><P
+>&#13;      That's it!  Now, when the standard template containing the hook
+      is processed, your extension template will be processed at the point 
+      where the hook appears.
+    </P
+><P
+>&#13;      For example, let's say you have an extension named Projman that adds
+      project management capabilities to Bugzilla.  Projman has an
+      administration interface <TT
+CLASS="filename"
+>edit-projects.cgi</TT
+>, 
+      and you want to add a link to it into the navigation bar at the bottom
+      of every Bugzilla page for those users who are authorized
+      to administer projects.
+    </P
+><P
+>&#13;      The navigation bar is generated by the template file
+      <TT
+CLASS="filename"
+>useful-links.html.tmpl</TT
+>, which is located in
+      the <TT
+CLASS="filename"
+>global/</TT
+> subdirectory on the standard Bugzilla 
+      template path
+      <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/default/</TT
+>.
+      Looking in <TT
+CLASS="filename"
+>useful-links.html.tmpl</TT
+>, you find
+      the following hook at the end of the list of standard Bugzilla
+      administration links:
+    </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>...
+    [% ', &#60;a href="editkeywords.cgi"&#62;keywords&#60;/a&#62;' 
+                                              IF user.groups.editkeywords %]
+    [% Hook.process("edit") %]
+...</PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>&#13;      The corresponding directory for this hook is
+      <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/extension/hook/global/useful-links.html.tmpl/edit/</TT
+>.
+    </P
+><P
+>&#13;      You put a template named
+      <TT
+CLASS="filename"
+>projman-edit-projects.html.tmpl</TT
+>
+      into that directory with the following content:
+    </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>...[% ', &#60;a href="edit-projects.cgi"&#62;projects&#60;/a&#62;' IF user.groups.projman_admins %]</PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>&#13;      Voila!  The link now appears after the other administration links in the
+      navigation bar for users in the <TT
+CLASS="literal"
+>projman_admins</TT
+> group.
+    </P
+><P
+>&#13;      Notes:
+    </P
+><P
+></P
+><UL
+><LI
+><P
+>&#13;          You may want to prefix your extension template names
+          with the name of your extension, e.g. 
+          <TT
+CLASS="filename"
+>projman-foo.html.tmpl</TT
+>, 
+          so they do not conflict with the names of templates installed by
+          other extensions.
+        </P
+></LI
+><LI
+><P
+>&#13;          If your extension includes entirely new templates in addition to
+          extensions of standard templates, it should install those new
+          templates into an extension-specific subdirectory of the
+          <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/extension/</TT
+> 
+          directory.  The <TT
+CLASS="filename"
+>extension/</TT
+> directory, like the 
+          <TT
+CLASS="filename"
+>default/</TT
+> and <TT
+CLASS="filename"
+>custom/</TT
+>
+          directories, is part of the template search path, so putting templates
+          there enables them to be found by the template processor.
+        </P
+><P
+>&#13;          The template processor looks for templates first in the
+          <TT
+CLASS="filename"
+>custom/</TT
+> directory (i.e. templates added by the 
+          specific installation), then in the <TT
+CLASS="filename"
+>extension/</TT
+> 
+          directory (i.e. templates added by extensions), and finally in the
+          <TT
+CLASS="filename"
+>default/</TT
+> directory (i.e. the standard Bugzilla 
+          templates).  Thus extension templates can override standard templates,
+          but installation-specific templates override both.
+        </P
+><P
+>&#13;          Note that overriding standard templates with extension templates
+          gives you great power but also makes upgrading an installation harder.
+          As with custom templates,  we recommend using this functionality
+          sparingly and only when absolutely necessary.
+        </P
+></LI
+><LI
+><P
+>&#13;          Installation customizers can also take advantage of hooks when adding
+          code to a Bugzilla template.  To do so, create directories in
+          <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/custom/hook/</TT
+>
+          equivalent to the directories in
+          <TT
+CLASS="filename"
+>BUGZILLA_ROOT/template/en/extension/hook/</TT
+>          
+          for the hooks you want to use, then place your customization templates
+          into those directories.
+        </P
+><P
+>&#13;          Obviously this method of customizing Bugzilla only lets you add code
+          to the standard templates; you cannot change the existing code.
+          Nevertheless, for those customizations that only add code, this method
+          can reduce conflicts when merging changes, making upgrading
+          your customized Bugzilla installation easier.
+        </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="cust-templates.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="cust-change-permissions.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Template Customization</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="customization.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Customizing Who Can Change What</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file

docs/html/cust-templates.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -17,8 +17,8 @@ REL="PREVIOUS"
 TITLE="Customising Bugzilla"
 HREF="customization.html"><LINK
 REL="NEXT"
-TITLE="Customizing Who Can Change What"
-HREF="cust-change-permissions.html"></HEAD
+TITLE="Template Hooks"
+HREF="cust-hooks.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 6. Customising Bugzilla</TD
+>Chapter 4. Customising Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="cust-change-permissions.html"
+HREF="cust-hooks.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="cust-templates"
 ></A
->6.1. Template Customization</H1
+>4.1. Template Customization</H1
 ><P
 >&#13;      Administrators can configure the look and feel of Bugzilla without
       having to edit Perl files or face the nightmare of massive merge
@@ -89,7 +89,7 @@ NAME="cust-templates"
       determined by the user's browser. More information is available in
       <A
 HREF="cust-templates.html#template-http-accept"
->Section 6.1.5</A
+>Section 4.1.5</A
 >.
     </P
 ><DIV
@@ -97,9 +97,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1588"
+NAME="AEN1208"
 ></A
->6.1.1. What to Edit</H2
+>4.1.1. What to Edit</H2
 ><P
 >&#13;        The template directory structure is that there's a top level directory,
         <TT
@@ -249,9 +249,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1611"
+NAME="AEN1231"
 ></A
->6.1.2. How To Edit Templates</H2
+>4.1.2. How To Edit Templates</H2
 ><DIV
 CLASS="note"
 ><P
@@ -329,9 +329,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1621"
+NAME="AEN1241"
 ></A
->6.1.3. Template Formats</H2
+>4.1.3. Template Formats</H2
 ><P
 >&#13;        Some CGIs have the ability to use more than one template. For
         example, buglist.cgi can output bug lists as RDF or two
@@ -391,9 +391,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1634"
+NAME="AEN1254"
 ></A
->6.1.4. Particular Templates</H2
+>4.1.4. Particular Templates</H2
 ><P
 >&#13;        There are a few templates you may be particularly interested in
         customizing for your installation.
@@ -567,7 +567,7 @@ CLASS="section"
 ><A
 NAME="template-http-accept"
 ></A
->6.1.5. Configuring Bugzilla to Detect the User's Language</H2
+>4.1.5. Configuring Bugzilla to Detect the User's Language</H2
 ><P
 >Bugzilla honours the user's Accept: HTTP header. You can install
       templates in other languages, and Bugzilla will pick the most appropriate
@@ -583,7 +583,7 @@ TARGET="_top"
 >After untarring the localizations (or creating your own) in the 
       <TT
 CLASS="filename"
->$BUGZILLA_HOME/template</TT
+>BUGZILLA_ROOT/template</TT
 > directory,
       you must update the <TT
 CLASS="option"
@@ -635,7 +635,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="cust-change-permissions.html"
+HREF="cust-hooks.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -659,7 +659,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Customizing Who Can Change What</TD
+>Template Hooks</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/customization.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -73,7 +73,7 @@ CLASS="chapter"
 ><A
 NAME="customization"
 ></A
->Chapter 6. Customising Bugzilla</H1
+>Chapter 4. Customising Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -82,78 +82,83 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->6.1. <A
+>4.1. <A
 HREF="cust-templates.html"
 >Template Customization</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.1.1. <A
-HREF="cust-templates.html#AEN1588"
+>4.1.1. <A
+HREF="cust-templates.html#AEN1208"
 >What to Edit</A
 ></DT
 ><DT
->6.1.2. <A
-HREF="cust-templates.html#AEN1611"
+>4.1.2. <A
+HREF="cust-templates.html#AEN1231"
 >How To Edit Templates</A
 ></DT
 ><DT
->6.1.3. <A
-HREF="cust-templates.html#AEN1621"
+>4.1.3. <A
+HREF="cust-templates.html#AEN1241"
 >Template Formats</A
 ></DT
 ><DT
->6.1.4. <A
-HREF="cust-templates.html#AEN1634"
+>4.1.4. <A
+HREF="cust-templates.html#AEN1254"
 >Particular Templates</A
 ></DT
 ><DT
->6.1.5. <A
+>4.1.5. <A
 HREF="cust-templates.html#template-http-accept"
 >Configuring Bugzilla to Detect the User's Language</A
 ></DT
 ></DL
 ></DD
 ><DT
->6.2. <A
+>4.2. <A
+HREF="cust-hooks.html"
+>Template Hooks</A
+></DT
+><DT
+>4.3. <A
 HREF="cust-change-permissions.html"
 >Customizing Who Can Change What</A
 ></DT
 ><DT
->6.3. <A
+>4.4. <A
 HREF="dbmodify.html"
 >Modifying Your Running System</A
 ></DT
 ><DT
->6.4. <A
+>4.5. <A
 HREF="dbdoc.html"
 >MySQL Bugzilla Database Introduction</A
 ></DT
 ><DT
->6.5. <A
+>4.6. <A
 HREF="integration.html"
 >Integrating Bugzilla with Third-Party Tools</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.5.1. <A
+>4.6.1. <A
 HREF="integration.html#bonsai"
 >Bonsai</A
 ></DT
 ><DT
->6.5.2. <A
+>4.6.2. <A
 HREF="integration.html#cvs"
 >CVS</A
 ></DT
 ><DT
->6.5.3. <A
+>4.6.3. <A
 HREF="integration.html#scm"
 >Perforce SCM</A
 ></DT
 ><DT
->6.5.4. <A
+>4.6.4. <A
 HREF="integration.html#tinderbox"
 >Tinderbox/Tinderbox2</A
 ></DT

docs/html/dbdoc.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 6. Customising Bugzilla</TD
+>Chapter 4. Customising Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="dbdoc"
 ></A
->6.4. MySQL Bugzilla Database Introduction</H1
+>4.5. MySQL Bugzilla Database Introduction</H1
 ><P
 >This information comes straight from my life. I was forced to learn
     how Bugzilla organizes database because of nitpicky requests from users
@@ -137,9 +137,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1710"
+NAME="AEN1392"
 ></A
->6.4.1. Bugzilla Database Basics</H2
+>4.5.1. Bugzilla Database Basics</H2
 ><P
 >If you were like me, at this point you're totally clueless about
       the internals of MySQL, and if it weren't for this executive order from
@@ -251,9 +251,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN1737"
+NAME="AEN1419"
 ></A
->6.4.1.1. Bugzilla Database Tables</H3
+>4.5.1.1. Bugzilla Database Tables</H3
 ><P
 >Imagine your MySQL database as a series of spreadsheets, and
         you won't be too far off. If you use this command:</P

docs/html/dbmodify.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 6. Customising Bugzilla</TD
+>Chapter 4. Customising Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="dbmodify"
 ></A
->6.3. Modifying Your Running System</H1
+>4.4. Modifying Your Running System</H1
 ><P
 >Bugzilla optimizes database lookups by storing all relatively
       static information in the 

docs/html/disclaimer.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -97,10 +97,10 @@ NAME="disclaimer"
     </P
 ><P
 >&#13;      Although the Bugzilla development team has taken great care to
-      ensure that all exploitable bugs or options have been
-      fixed, security holes surely exist. Great care should be taken both in 
+      ensure that all exploitable bugs have been fixed, security holes surely 
+      exist in any piece of code. Great care should be taken both in 
       the installation and usage of this software. The Bugzilla development
-      team members assume no liability for your use of this software. You have 
+      team members assume no liability for your use of Bugzilla. You have 
       the source code, and are responsible for auditing it yourself to ensure
       your security needs are met.
     </P

docs/html/extraconfig.html

@@ -7,17 +7,17 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
 REL="PREVIOUS"
-TITLE="HTTP Server Configuration"
-HREF="http.html"><LINK
+TITLE="Configuration"
+HREF="configuration.html"><LINK
 REL="NEXT"
-TITLE="OS Specific Installation Notes"
+TITLE="OS-Specific Installation Notes"
 HREF="os-specific.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -47,7 +47,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="http.html"
+HREF="configuration.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 4. Installation</TD
+>Chapter 2. Installing Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,18 +77,84 @@ CLASS="section"
 ><A
 NAME="extraconfig"
 ></A
->4.3. Optional Additional Configuration</H1
+>2.3. Optional Additional Configuration</H1
+><P
+>&#13;      Bugzilla has a number of optional features. This section describes how
+      to configure or enable them.
+    </P
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN843"
+NAME="AEN584"
 ></A
->4.3.1. Dependency Charts</H2
+>2.3.1. Bug Graphs</H2
+><P
+>If you have installed the necessary Perl modules you
+      can start collecting statistics for the nifty Bugzilla 
+      graphs.</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="screen"
+><TT
+CLASS="prompt"
+>bash#</TT
+> <B
+CLASS="command"
+>crontab -e</B
+></PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>&#13;        This should bring up the crontab file in your editor. 
+        Add a cron entry like this to run 
+        <TT
+CLASS="filename"
+>collectstats.pl</TT
+> 
+        daily at 5 after midnight:
+      </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="programlisting"
+>5 0 * * * cd &#60;your-bugzilla-directory&#62; ; ./collectstats.pl</PRE
+></FONT
+></TD
+></TR
+></TABLE
 ><P
->As well as the text-based dependency graphs, Bugzilla also
-      supports dependency graphing, using a package called 'dot'.
+>After two days have passed you'll be able to view bug graphs from
+      the Reports page.</P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="AEN594"
+></A
+>2.3.2. Dependency Charts</H2
+><P
+>As well as the text-based dependency trees, Bugzilla also
+      supports a graphical view of dependency relationships, using a 
+      package called 'dot'.
       Exactly how this works is controlled by the 'webdotbase' parameter,
       which can have one of three values:
       </P
@@ -123,7 +189,7 @@ TARGET="_top"
 >
       </P
 ><P
->So, to get this working, install
+>The easiest way to get this working is to install
       <A
 HREF="http://www.graphviz.org/"
 TARGET="_top"
@@ -137,137 +203,37 @@ TARGET="_top"
       server-side image maps</A
 > in Apache.
       Alternatively, you could set up a webdot server, or use the AT&#38;T 
-      public webdot server (the
-      default for the webdotbase param). Note that AT&#38;T's server won't work
-      if Bugzilla is only accessible using HARTS.
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="AEN858"
-></A
->4.3.2. Bug Graphs</H2
-><P
->As long as you installed the GD and Graph::Base Perl modules you
-      might as well turn on the nifty Bugzilla bug reporting graphs.</P
-><P
->Add a cron entry like this to run 
-      <TT
-CLASS="filename"
->collectstats.pl</TT
-> 
-      daily at 5 after midnight: 
-      <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->&#13;          <TT
-CLASS="computeroutput"
->&#13;            <TT
-CLASS="prompt"
->bash#</TT
->
-
-            <B
-CLASS="command"
->crontab -e</B
->
-          </TT
->
-        </TD
-></TR
-><TR
-><TD
->&#13;          <TT
-CLASS="computeroutput"
->5 0 * * * cd &#60;your-bugzilla-directory&#62; ;
-          ./collectstats.pl</TT
->
-        </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
+      public webdot server. This is the default for the webdotbase param, 
+      but it's often overloaded and slow. Note that AT&#38;T's server 
+      won't work
+      if Bugzilla is only accessible using HARTS. 
+      <EM
+>Editor's note: What the heck is HARTS? Google doesn't know...
+      </EM
 >
       </P
-><P
->After two days have passed you'll be able to view bug graphs from
-      the Bug Reports page.</P
 ></DIV
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN871"
+NAME="AEN610"
 ></A
->4.3.3. The Whining Cron</H2
+>2.3.3. The Whining Cron</H2
 ><P
->By now you have a fully functional Bugzilla, but what good are
-      bugs if they're not annoying? To help make those bugs more annoying you
+>What good are
+      bugs if they're not annoying? To help make them more so you
       can set up Bugzilla's automatic whining system to complain at engineers
       which leave their bugs in the NEW or REOPENED state without triaging them.
       </P
 ><P
->&#13;      This can be done by
-      adding the following command as a daily crontab entry (for help on that
-      see that crontab man page): 
-      <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->&#13;          <TT
-CLASS="computeroutput"
->&#13;            <B
-CLASS="command"
->cd &#60;your-bugzilla-directory&#62; ;
-            ./whineatnews.pl</B
->
-          </TT
->
-        </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
+>&#13;      
+      This can be done by
+      adding the following command as a daily crontab entry, in the same manner
+      as explained above for bug graphs. This example runs it at 12.55am. 
       </P
-><DIV
-CLASS="tip"
-><P
-></P
 ><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Depending on your system, crontab may have several manpages.
-        The following command should lead you to the most useful page for
-        this purpose: 
-        <TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
 WIDTH="100%"
@@ -277,18 +243,66 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
->&#13;man 5 crontab
-	</PRE
+>55 0 * * * cd &#60;your-bugzilla-directory&#62; ; ./whineatnews.pl</PRE
 ></FONT
 ></TD
 ></TR
 ></TABLE
->
-        </P
-></TD
-></TR
-></TABLE
 ></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="patch-viewer"
+></A
+>2.3.4. Patch Viewer</H2
+><P
+>&#13;        Patch Viewer is the engine behind Bugzilla's graphical display of
+        code patches. You can integrate this with copies of the
+        <TT
+CLASS="filename"
+>cvs</TT
+>, <TT
+CLASS="filename"
+>lxr</TT
+> and
+        <TT
+CLASS="filename"
+>bonsai</TT
+> tools if you have them, by giving
+        the locations of your installation of these tools in
+        <TT
+CLASS="filename"
+>editparams.cgi</TT
+>.
+      </P
+><P
+>&#13;        Patch Viewer also optionally will use the 
+        <TT
+CLASS="filename"
+>cvs</TT
+>, <TT
+CLASS="filename"
+>diff</TT
+> and 
+        <TT
+CLASS="filename"
+>interdiff</TT
+>
+        command-line utilities if they exist on the system.
+        Interdiff can be obtained from 
+        <A
+HREF="http://cyberelk.net/tim/patchutils/"
+TARGET="_top"
+>http://cyberelk.net/tim/patchutils/</A
+>.
+        If these programs are not in the system path, you can configure
+        their locations in <TT
+CLASS="filename"
+>localconfig</TT
+>.
+      </P
 ></DIV
 ><DIV
 CLASS="section"
@@ -297,7 +311,7 @@ CLASS="section"
 ><A
 NAME="bzldap"
 ></A
->4.3.4. LDAP Authentication</H2
+>2.3.5. LDAP Authentication</H2
 ><P
 >LDAP authentication is a module for Bugzilla's plugin 
       authentication architecture.
@@ -457,7 +471,7 @@ NAME="param-LDAPBaseDN"
 ><DD
 ><P
 >The LDAPBaseDN parameter should be set to the location in
-             your LDAP tree that you would like to search for e-mail addresses.
+             your LDAP tree that you would like to search for email addresses.
              Your uids should be unique under the DN specified here.
              </P
 ><P
@@ -492,7 +506,7 @@ NAME="param-LDAPmailattribute"
 ><DD
 ><P
 >The LDAPmailattribute parameter should be the name of the
-             attribute which contains the e-mail address your users will enter
+             attribute which contains the email address your users will enter
              into the Bugzilla login boxes.
              </P
 ><P
@@ -511,21 +525,19 @@ CLASS="section"
 ><A
 NAME="content-type"
 ></A
->4.3.5. Preventing untrusted Bugzilla content from executing malicious
-      Javascript code</H2
+>2.3.6. Prevent users injecting malicious
+      Javascript</H2
 ><P
->It is possible for a Bugzilla attachment to contain malicious 
-      Javascript
-      code, which would be executed in the domain of your Bugzilla, thereby
-      making it possible for the attacker to e.g. steal your login cookies. 
+>It is possible for a Bugzilla user to take advantage of character
+      set encoding ambiguities to inject HTML into Bugzilla comments. This
+      could include malicious scripts. 
       Due to internationalization concerns, we are unable to
-      incorporate by default the code changes necessary to fulfill the CERT 
-      advisory requirements mentioned in 
+      incorporate by default the code changes suggested by 
       <A
-HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3"
+HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html#3"
 TARGET="_top"
->http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3</A
->.
+>&#13;      the CERT advisory</A
+> on this issue.
       If your installation is for an English speaking audience only, making the
       change below will prevent this problem. 
       </P
@@ -545,8 +557,7 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
->&#13;    $self-&#62;charset('');
-      </PRE
+>$self-&#62;charset('');</PRE
 ></FONT
 ></TD
 ></TR
@@ -563,8 +574,7 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
->&#13;    $self-&#62;charset('ISO-8859-1');
-      </PRE
+>$self-&#62;charset('ISO-8859-1');</PRE
 ></FONT
 ></TD
 ></TR
@@ -577,42 +587,22 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="mod_perl"
-></A
->4.3.6. Bugzilla and <TT
-CLASS="filename"
->mod_perl</TT
-></H2
-><P
->Bugzilla is unsupported under mod_perl.  Effort is underway
-      to make it work cleanly in a mod_perl environment, but it is
-      slow going.
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
 NAME="mod-throttle"
 ></A
->4.3.7. <TT
+>2.3.7. <TT
 CLASS="filename"
 >mod_throttle</TT
->
-
-      and Security</H2
+></H2
 ><P
 >It is possible for a user, by mistake or on purpose, to access
       the database many times in a row which can result in very slow access
       speeds for other users. If your Bugzilla installation is experiencing
-      this problem , you may install the Apache module 
+      this problem, you may install the Apache module 
       <TT
 CLASS="filename"
 >mod_throttle</TT
 >
-
-      which can limit connections by ip-address. You may download this module
+      which can limit connections by IP address. You may download this module
       at 
       <A
 HREF="http://www.snert.com/Software/mod_throttle/"
@@ -624,21 +614,66 @@ TARGET="_top"
 >This module only functions with the Apache web
       server!</EM
 >
-      You may use the 
+      The command you need is 
       <B
 CLASS="command"
 >ThrottleClientIP</B
->
-
-      command provided by this module to accomplish this goal. See the 
+>. See the 
       <A
 HREF="http://www.snert.com/Software/mod_throttle/"
 TARGET="_top"
->Module
-      Instructions</A
+>documentation</A
 >
       for more information.</P
 ></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="security-networking"
+></A
+>2.3.8. TCP/IP Ports</H2
+><P
+>A single-box Bugzilla only requires port 80, plus port 25 if
+      you are using the optional email interface. You should firewall all 
+      other ports and/or disable services listening on them.
+      </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="security-daemon"
+></A
+>2.3.9. Daemon Accounts</H2
+><P
+>Many daemons, such as Apache's httpd and MySQL's mysqld default to
+      running as either <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> or <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+>. Running
+      as <SPAN
+CLASS="QUOTE"
+>"root"</SPAN
+> introduces obvious security problems, but the
+      problems introduced by running everything as <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+> may
+      not be so obvious. Basically, if you're running every daemon as
+      <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+> and one of them gets compromised, they all get
+      compromised. For this reason it is recommended that you create a user
+      account for each daemon.
+      </P
+></DIV
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
@@ -656,7 +691,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="http.html"
+HREF="configuration.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -684,13 +719,13 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->HTTP Server Configuration</TD
+>Configuration</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="installation.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="U"
 >Up</A
 ></TD
@@ -698,7 +733,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->OS Specific Installation Notes</TD
+>OS-Specific Installation Notes</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/faq.html

@@ -7,12 +7,12 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
+TITLE="Reports"
+HREF="reporting.html"><LINK
 REL="NEXT"
 TITLE="Contrib"
 HREF="patches.html"></HEAD
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -44,7 +44,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="integration.html"
+HREF="reporting.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -157,6 +157,15 @@ HREF="faq.html#faq-general-cookie"
 >&#13;	    Is there an easy way to change the Bugzilla cookie name?
 	  </A
 ></DT
+><DT
+>A.1.11. <A
+HREF="faq.html#faq-mod-perl"
+>&#13;	    Does bugzilla run under <TT
+CLASS="filename"
+>mod_perl</TT
+>?
+	  </A
+></DT
 ></DL
 ></DD
 ><DT
@@ -887,6 +896,33 @@ CLASS="answer"
 	  </P
 ></DIV
 ></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-mod-perl"
+></A
+><B
+>A.1.11. </B
+>
+	    Does bugzilla run under <TT
+CLASS="filename"
+>mod_perl</TT
+>?
+	  </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+	    At present, no. This is being worked on.
+	  </P
+></DIV
+></DIV
 ></DIV
 ><DIV
 CLASS="qandadiv"
@@ -1974,7 +2010,7 @@ CLASS="answer"
 ><P
 >&#13;	    Microsoft has some advice on this matter, as well:
 	    <A
-NAME="AEN2053"
+NAME="AEN1977"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -2504,7 +2540,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="integration.html"
+HREF="reporting.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -2532,7 +2568,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
+>Reports</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"

docs/html/gfdl-0.html

 <HTML
 ><HEAD
 ><TITLE
->PREAMBLE</TITLE
+>Preamble</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -17,7 +17,7 @@ REL="PREVIOUS"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="NEXT"
-TITLE="APPLICABILITY AND DEFINITIONS"
+TITLE="Applicability and Definition"
 HREF="gfdl-1.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-0"
 ></A
->0. PREAMBLE</H1
+>0. Preamble</H1
 ><P
 >The purpose of this License is to make a manual, textbook, or other
     written document "free" in the sense of freedom: to assure everyone the
@@ -158,7 +158,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->APPLICABILITY AND DEFINITIONS</TD
+>Applicability and Definition</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-1.html

 <HTML
 ><HEAD
 ><TITLE
->APPLICABILITY AND DEFINITIONS</TITLE
+>Applicability and Definition</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="PREAMBLE"
+TITLE="Preamble"
 HREF="gfdl-0.html"><LINK
 REL="NEXT"
-TITLE="VERBATIM COPYING"
+TITLE="Verbatim Copying"
 HREF="gfdl-2.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-1"
 ></A
->1. APPLICABILITY AND DEFINITIONS</H1
+>1. Applicability and Definition</H1
 ><P
 >This License applies to any manual or other work that contains a
     notice placed by the copyright holder saying it can be distributed under
@@ -179,7 +179,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->PREAMBLE</TD
+>Preamble</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -193,7 +193,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->VERBATIM COPYING</TD
+>Verbatim Copying</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-10.html

 <HTML
 ><HEAD
 ><TITLE
->FUTURE REVISIONS OF THIS LICENSE</TITLE
+>Future Revisions of this License</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="TERMINATION"
+TITLE="Termination"
 HREF="gfdl-9.html"><LINK
 REL="NEXT"
 TITLE="How to use this License for your documents"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-10"
 ></A
->10. FUTURE REVISIONS OF THIS LICENSE</H1
+>10. Future Revisions of this License</H1
 ><P
 >The Free Software Foundation may publish new, revised versions of
     the GNU Free Documentation License from time to time. Such new versions
@@ -142,7 +142,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->TERMINATION</TD
+>Termination</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"

docs/html/gfdl-2.html

 <HTML
 ><HEAD
 ><TITLE
->VERBATIM COPYING</TITLE
+>Verbatim Copying</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="APPLICABILITY AND DEFINITIONS"
+TITLE="Applicability and Definition"
 HREF="gfdl-1.html"><LINK
 REL="NEXT"
-TITLE="COPYING IN QUANTITY"
+TITLE="Copying in Quantity"
 HREF="gfdl-3.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-2"
 ></A
->2. VERBATIM COPYING</H1
+>2. Verbatim Copying</H1
 ><P
 >You may copy and distribute the Document in any medium, either
     commercially or noncommercially, provided that this License, the
@@ -136,7 +136,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->APPLICABILITY AND DEFINITIONS</TD
+>Applicability and Definition</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -150,7 +150,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->COPYING IN QUANTITY</TD
+>Copying in Quantity</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-3.html

 <HTML
 ><HEAD
 ><TITLE
->COPYING IN QUANTITY</TITLE
+>Copying in Quantity</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="VERBATIM COPYING"
+TITLE="Verbatim Copying"
 HREF="gfdl-2.html"><LINK
 REL="NEXT"
-TITLE="MODIFICATIONS"
+TITLE="Modifications"
 HREF="gfdl-4.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-3"
 ></A
->3. COPYING IN QUANTITY</H1
+>3. Copying in Quantity</H1
 ><P
 >If you publish printed copies of the Document numbering more than
     100, and the Document's license notice requires Cover Texts, you must
@@ -158,7 +158,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->VERBATIM COPYING</TD
+>Verbatim Copying</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -172,7 +172,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->MODIFICATIONS</TD
+>Modifications</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-4.html

 <HTML
 ><HEAD
 ><TITLE
->MODIFICATIONS</TITLE
+>Modifications</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="COPYING IN QUANTITY"
+TITLE="Copying in Quantity"
 HREF="gfdl-3.html"><LINK
 REL="NEXT"
-TITLE="COMBINING DOCUMENTS"
+TITLE="Combining Documents"
 HREF="gfdl-5.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-4"
 ></A
->4. MODIFICATIONS</H1
+>4. Modifications</H1
 ><P
 >You may copy and distribute a Modified Version of the Document
     under the conditions of sections 2 and 3 above, provided that you release
@@ -252,7 +252,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->COPYING IN QUANTITY</TD
+>Copying in Quantity</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -266,7 +266,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->COMBINING DOCUMENTS</TD
+>Combining Documents</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-5.html

 <HTML
 ><HEAD
 ><TITLE
->COMBINING DOCUMENTS</TITLE
+>Combining Documents</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="MODIFICATIONS"
+TITLE="Modifications"
 HREF="gfdl-4.html"><LINK
 REL="NEXT"
-TITLE="COLLECTIONS OF DOCUMENTS"
+TITLE="Collections of Documents"
 HREF="gfdl-6.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-5"
 ></A
->5. COMBINING DOCUMENTS</H1
+>5. Combining Documents</H1
 ><P
 >You may combine the Document with other documents released under
     this License, under the terms defined in section 4 above for modified
@@ -145,7 +145,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->MODIFICATIONS</TD
+>Modifications</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -159,7 +159,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->COLLECTIONS OF DOCUMENTS</TD
+>Collections of Documents</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-6.html

 <HTML
 ><HEAD
 ><TITLE
->COLLECTIONS OF DOCUMENTS</TITLE
+>Collections of Documents</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="COMBINING DOCUMENTS"
+TITLE="Combining Documents"
 HREF="gfdl-5.html"><LINK
 REL="NEXT"
-TITLE="AGGREGATION WITH INDEPENDENT WORKS"
+TITLE="Aggregation with Independent Works"
 HREF="gfdl-7.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-6"
 ></A
->6. COLLECTIONS OF DOCUMENTS</H1
+>6. Collections of Documents</H1
 ><P
 >You may make a collection consisting of the Document and other
     documents released under this License, and replace the individual copies
@@ -135,7 +135,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->COMBINING DOCUMENTS</TD
+>Combining Documents</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -149,7 +149,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->AGGREGATION WITH INDEPENDENT WORKS</TD
+>Aggregation with Independent Works</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-7.html

 <HTML
 ><HEAD
 ><TITLE
->AGGREGATION WITH INDEPENDENT WORKS</TITLE
+>Aggregation with Independent Works</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="COLLECTIONS OF DOCUMENTS"
+TITLE="Collections of Documents"
 HREF="gfdl-6.html"><LINK
 REL="NEXT"
-TITLE="TRANSLATION"
+TITLE="Translation"
 HREF="gfdl-8.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-7"
 ></A
->7. AGGREGATION WITH INDEPENDENT WORKS</H1
+>7. Aggregation with Independent Works</H1
 ><P
 >A compilation of the Document or its derivatives with other
     separate and independent documents or works, in or on a volume of a
@@ -138,7 +138,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->COLLECTIONS OF DOCUMENTS</TD
+>Collections of Documents</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -152,7 +152,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->TRANSLATION</TD
+>Translation</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-8.html

 <HTML
 ><HEAD
 ><TITLE
->TRANSLATION</TITLE
+>Translation</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="AGGREGATION WITH INDEPENDENT WORKS"
+TITLE="Aggregation with Independent Works"
 HREF="gfdl-7.html"><LINK
 REL="NEXT"
-TITLE="TERMINATION"
+TITLE="Termination"
 HREF="gfdl-9.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-8"
 ></A
->8. TRANSLATION</H1
+>8. Translation</H1
 ><P
 >Translation is considered a kind of modification, so you may
     distribute translations of the Document under the terms of section 4.
@@ -134,7 +134,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->AGGREGATION WITH INDEPENDENT WORKS</TD
+>Aggregation with Independent Works</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -148,7 +148,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->TERMINATION</TD
+>Termination</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-9.html

 <HTML
 ><HEAD
 ><TITLE
->TERMINATION</TITLE
+>Termination</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="TRANSLATION"
+TITLE="Translation"
 HREF="gfdl-8.html"><LINK
 REL="NEXT"
-TITLE="FUTURE REVISIONS OF THIS LICENSE"
+TITLE="Future Revisions of this License"
 HREF="gfdl-10.html"></HEAD
 ><BODY
 CLASS="section"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="gfdl-9"
 ></A
->9. TERMINATION</H1
+>9. Termination</H1
 ><P
 >You may not copy, modify, sublicense, or distribute the Document
     except as expressly provided for under this License. Any other attempt to
@@ -131,7 +131,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->TRANSLATION</TD
+>Translation</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -145,7 +145,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->FUTURE REVISIONS OF THIS LICENSE</TD
+>Future Revisions of this License</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/gfdl-howto.html

@@ -7,14 +7,14 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
 TITLE="GNU Free Documentation License"
 HREF="gfdl.html"><LINK
 REL="PREVIOUS"
-TITLE="FUTURE REVISIONS OF THIS LICENSE"
+TITLE="Future Revisions of this License"
 HREF="gfdl-10.html"><LINK
 REL="NEXT"
 TITLE="Glossary"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix C. GNU Free Documentation License</TD
+>Appendix D. GNU Free Documentation License</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -83,7 +83,7 @@ NAME="gfdl-howto"
     of the License in the document and put the following copyright and
     license notices just after the title page:</P
 ><A
-NAME="AEN2273"
+NAME="AEN2282"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -151,7 +151,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->FUTURE REVISIONS OF THIS LICENSE</TD
+>Future Revisions of this License</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"

docs/html/gfdl.html

@@ -7,14 +7,14 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
-TITLE="Command-line Search Interface"
-HREF="cmdline.html"><LINK
+TITLE="Download Locations"
+HREF="modules-manual-download.html"><LINK
 REL="NEXT"
-TITLE="PREAMBLE"
+TITLE="Preamble"
 HREF="gfdl-0.html"></HEAD
 ><BODY
 CLASS="appendix"
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -44,7 +44,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="cmdline.html"
+HREF="modules-manual-download.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -73,7 +73,7 @@ CLASS="appendix"
 ><A
 NAME="gfdl"
 ></A
->Appendix C. GNU Free Documentation License</H1
+>Appendix D. GNU Free Documentation License</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -84,57 +84,57 @@ CLASS="TOC"
 ><DT
 >0. <A
 HREF="gfdl-0.html"
->PREAMBLE</A
+>Preamble</A
 ></DT
 ><DT
 >1. <A
 HREF="gfdl-1.html"
->APPLICABILITY AND DEFINITIONS</A
+>Applicability and Definition</A
 ></DT
 ><DT
 >2. <A
 HREF="gfdl-2.html"
->VERBATIM COPYING</A
+>Verbatim Copying</A
 ></DT
 ><DT
 >3. <A
 HREF="gfdl-3.html"
->COPYING IN QUANTITY</A
+>Copying in Quantity</A
 ></DT
 ><DT
 >4. <A
 HREF="gfdl-4.html"
->MODIFICATIONS</A
+>Modifications</A
 ></DT
 ><DT
 >5. <A
 HREF="gfdl-5.html"
->COMBINING DOCUMENTS</A
+>Combining Documents</A
 ></DT
 ><DT
 >6. <A
 HREF="gfdl-6.html"
->COLLECTIONS OF DOCUMENTS</A
+>Collections of Documents</A
 ></DT
 ><DT
 >7. <A
 HREF="gfdl-7.html"
->AGGREGATION WITH INDEPENDENT WORKS</A
+>Aggregation with Independent Works</A
 ></DT
 ><DT
 >8. <A
 HREF="gfdl-8.html"
->TRANSLATION</A
+>Translation</A
 ></DT
 ><DT
 >9. <A
 HREF="gfdl-9.html"
->TERMINATION</A
+>Termination</A
 ></DT
 ><DT
 >10. <A
 HREF="gfdl-10.html"
->FUTURE REVISIONS OF THIS LICENSE</A
+>Future Revisions of this License</A
 ></DT
 ><DT
 ><A
@@ -146,7 +146,7 @@ HREF="gfdl-howto.html"
 ><P
 >Version 1.1, March 2000</P
 ><A
-NAME="AEN2183"
+NAME="AEN2192"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -173,7 +173,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="cmdline.html"
+HREF="modules-manual-download.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -201,7 +201,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Command-line Search Interface</TD
+>Download Locations</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -211,7 +211,7 @@ VALIGN="top"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->PREAMBLE</TD
+>Preamble</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/glossary.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
@@ -32,7 +32,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -72,7 +72,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="AEN2278"
+NAME="AEN2287"
 ></A
 >0-9, high ascii</H1
 ><DL
@@ -241,8 +241,8 @@ TARGET="_top"
 ><P
 >For more information about how to configure Apache for Bugzilla,
         see <A
-HREF="http.html#http-apache"
->Section 4.2.1</A
+HREF="configuration.html#http-apache"
+>Section 2.2.4.1</A
 >.
         </P
 ></DD
@@ -634,8 +634,8 @@ TARGET="_top"
 ><P
 >Much more detailed information about the suggestions in
               <A
-HREF="security.html#security-mysql"
->Section 4.5.2</A
+HREF="configuration.html#security-mysql"
+>Section 2.2.2.1</A
 >.
               </P
 ></DD
@@ -936,7 +936,7 @@ NAME="gloss-zarro"
         Terry had the following to say:
         </P
 ><A
-NAME="AEN2513"
+NAME="AEN2522"
 ></A
 ><TABLE
 BORDER="0"

docs/html/groups.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="groups"
 ></A
->5.8. Groups and Group Security</H1
+>3.8. Groups and Group Security</H1
 ><P
 >Groups allow the administrator
     to isolate bugs or products that should only be seen by certain people.

docs/html/hintsandtips.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="hintsandtips"
 ></A
->3.8. Hints and Tips</H1
+>5.8. Hints and Tips</H1
 ><P
 >This section distills some Bugzilla tips and best practices
     that have been developed.</P
@@ -86,9 +86,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN363"
+NAME="AEN1641"
 ></A
->3.8.1. Autolinkification</H2
+>5.8.1. Autolinkification</H2
 ><P
 >Bugzilla comments are plain text - so typing &#60;U&#62; will
       produce less-than, U, greater-than rather than underlined text.
@@ -157,7 +157,7 @@ CLASS="section"
 ><A
 NAME="quicksearch"
 ></A
->3.8.2. Quicksearch</H2
+>5.8.2. Quicksearch</H2
 ><P
 >Quicksearch is a single-text-box query tool which uses
       metacharacters to indicate what is to be searched. For example, typing
@@ -190,7 +190,7 @@ CLASS="section"
 ><A
 NAME="commenting"
 ></A
->3.8.3. Comments</H2
+>5.8.3. Comments</H2
 ><P
 >If you are changing the fields on a bug, only comment if
       either you have something pertinent to say, or Bugzilla requires it.
@@ -214,7 +214,7 @@ CLASS="section"
 ><A
 NAME="attachments"
 ></A
->3.8.4. Attachments</H2
+>5.8.4. Attachments</H2
 ><P
 >&#13;      Use attachments, rather than comments, for large chunks of ASCII data,
       such as trace, debugging output files, or log files. That way, it doesn't

docs/html/how.html

-<HTML
-><HEAD
-><TITLE
->How do I use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="PREVIOUS"
-TITLE="Using Bugzilla"
-HREF="using.html"><LINK
-REL="NEXT"
-TITLE="Hints and Tips"
-HREF="hintsandtips.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="hintsandtips.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="how"
-></A
->3.1. How do I use Bugzilla?</H1
-><P
->This section contains information for end-users of Bugzilla. 
-    There is a Bugzilla test installation, called 
-    <A
-HREF="http://landfill.bugzilla.org/"
-TARGET="_top"
->Landfill</A
->, 
-    which you are welcome to play with (if it's up.) 
-    However, it does not necessarily
-    have all Bugzilla features enabled, and often runs cutting-edge versions
-    of Bugzilla for testing, so some things may work slightly differently
-    than mentioned here.</P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="myaccount"
-></A
->3.1.1. Create a Bugzilla Account</H2
-><P
->If you want to use Bugzilla, first you need to create an account.
-      Consult with the administrator responsible for your installation of
-      Bugzilla for the URL you should use to access it. If you're
-      test-driving Bugzilla, use this URL: 
-      <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/"
-TARGET="_top"
->http://landfill.bugzilla.org/bugzilla-tip/</A
->.
-      </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Click the 
-          <SPAN
-CLASS="QUOTE"
->"Open a new Bugzilla account"</SPAN
->
-
-          link, enter your email address and, optionally, your name in the
-          spaces provided, then click 
-          <SPAN
-CLASS="QUOTE"
->"Create Account"</SPAN
->
-
-          .</P
-></LI
-><LI
-><P
->Within moments, you should receive an email to the address
-          you provided above, which contains your login name (generally the
-          same as the email address), and a password you can use to access
-          your account. This password is randomly generated, and can be
-          changed to something more memorable.</P
-></LI
-><LI
-><P
->Click the 
-          <SPAN
-CLASS="QUOTE"
->"Log In"</SPAN
->
-          link in the yellow area at the bottom of the page in your browser,
-          enter your email address and password into the spaces provided, and
-          click 
-          <SPAN
-CLASS="QUOTE"
->"Login"</SPAN
->.
-          </P
-></LI
-></OL
-><P
->You are now logged in. Bugzilla uses cookies for authentication
-      so, unless your IP address changes, you should not have to log in
-      again.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bug_page"
-></A
->3.1.2. Anatomy of a Bug</H2
-><P
->The core of Bugzilla is the screen which displays a particular
-      bug. It's a good place to explain some Bugzilla concepts. 
-      <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"
-TARGET="_top"
->&#13;      Bug 1 on Landfill</A
->
-
-      is a good example. Note that the labels for most fields are hyperlinks;
-      clicking them will take you to context-sensitive help on that
-      particular field. Fields marked * may not be present on every
-      installation of Bugzilla.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->&#13;          <EM
->Product and Component</EM
->: 
-          Bugs are divided up by Product and Component, with a Product
-          having one or more Components in it. For example,
-          bugzilla.mozilla.org's "Bugzilla" Product is composed of several
-          Components: 
-          <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->&#13;          <EM
->Administration:</EM
->
-          Administration of a Bugzilla installation.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Bugzilla-General:</EM
->
-          Anything that doesn't fit in the other components, or spans
-          multiple components.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Creating/Changing Bugs:</EM
->
-          Creating, changing, and viewing bugs.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Documentation:</EM
->
-          The Bugzilla documentation, including The Bugzilla Guide.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Email:</EM
->
-          Anything to do with email sent by Bugzilla.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Installation:</EM
->
-          The installation process of Bugzilla.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Query/Buglist:</EM
->
-          Anything to do with searching for bugs and viewing the
-          buglists.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->Reporting/Charting:</EM
->
-          Getting reports from Bugzilla.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->User Accounts:</EM
->
-          Anything about managing a user account from the user's perspective.
-          Saved queries, creating accounts, changing passwords, logging in,
-          etc.</TD
-></TR
-><TR
-><TD
->&#13;          <EM
->User Interface:</EM
->
-          General issues having to do with the user interface cosmetics (not
-          functionality) including cosmetic issues, HTML templates,
-          etc.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-          </P
-></LI
-><LI
-><P
->&#13;          <EM
->Status and Resolution:</EM
->
-
-          These define exactly what state the bug is in - from not even
-          being confirmed as a bug, through to being fixed and the fix
-          confirmed by Quality Assurance. The different possible values for
-          Status and Resolution on your installation should be documented in the
-          context-sensitive help for those items.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Assigned To:</EM
->
-          The person responsible for fixing the bug.</P
-></LI
-><LI
-><P
->&#13;          <EM
->*URL:</EM
->
-          A URL associated with the bug, if any.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Summary:</EM
->
-          A one-sentence summary of the problem.</P
-></LI
-><LI
-><P
->&#13;          <EM
->*Status Whiteboard:</EM
->
-          (a.k.a. Whiteboard) A free-form text area for adding short notes
-          and tags to a bug.</P
-></LI
-><LI
-><P
->&#13;          <EM
->*Keywords:</EM
->
-          The administrator can define keywords which you can use to tag and
-          categorise bugs - e.g. The Mozilla Project has keywords like crash
-          and regression.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Platform and OS:</EM
->
-          These indicate the computing environment where the bug was
-          found.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Version:</EM
->
-          The "Version" field is usually used for versions of a product which
-          have been released, and is set to indicate which versions of a
-          Component have the particular problem the bug report is
-          about.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Priority:</EM
->
-          The bug assignee uses this field to prioritise his or her bugs.
-          It's a good idea not to change this on other people's bugs.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Severity:</EM
->
-          This indicates how severe the problem is - from blocker
-          ("application unusable") to trivial ("minor cosmetic issue"). You
-          can also use this field to indicate whether a bug is an enhancement
-          request.</P
-></LI
-><LI
-><P
->&#13;          <EM
->*Target:</EM
->
-          (a.k.a. Target Milestone) A future version by which the bug is to
-          be fixed. e.g. The Bugzilla Project's milestones for future
-          Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
-          restricted to numbers, thought - you can use any text strings, such
-          as dates.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Reporter:</EM
->
-          The person who filed the bug.</P
-></LI
-><LI
-><P
->&#13;          <EM
->CC list:</EM
->
-          A list of people who get mail when the bug changes.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Attachments:</EM
->
-          You can attach files (e.g. testcases or patches) to bugs. If there
-          are any attachments, they are listed in this section.</P
-></LI
-><LI
-><P
->&#13;          <EM
->*Dependencies:</EM
->
-          If this bug cannot be fixed unless other bugs are fixed (depends
-          on), or this bug stops other bugs being fixed (blocks), their
-          numbers are recorded here.</P
-></LI
-><LI
-><P
->&#13;          <EM
->*Votes:</EM
->
-          Whether this bug has any votes.</P
-></LI
-><LI
-><P
->&#13;          <EM
->Additional Comments:</EM
->
-          You can add your two cents to the bug discussion here, if you have
-          something worthwhile to say.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="query"
-></A
->3.1.3. Searching for Bugs</H2
-><P
->The Bugzilla Search page is is the interface where you can find
-      any bug report, comment, or patch currently in the Bugzilla system. You
-      can play with it here: 
-      <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"
-TARGET="_top"
->http://landfill.bugzilla.org/bugzilla-tip/query.cgi</A
->.</P
-><P
->The Search page has controls for selecting different possible
-      values for all of the fields in a bug, as described above. For some
-      fields, multiple values can be selected. In those cases, Bugzilla
-      returns bugs where the content of the field matches one of the selected
-      values. If none is selected, then the field can take any value.</P
-><P
->Once you've defined a search, you can either run it, or save it
-      as a Remembered Query, which can optionally appear in the footer of
-      your pages.</P
-><P
->Highly advanced querying is done using Boolean Charts.</P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="list"
-></A
->3.1.4. Bug Lists</H2
-><P
->If you run a search, a list of matching bugs will be returned.
-      The default search is to return all open bugs on the system - don't try
-      running this search on a Bugzilla installation with a lot of
-      bugs!</P
-><P
->The format of the list is configurable. For example, it can be
-      sorted by clicking the column headings. Other useful features can be
-      accessed using the links at the bottom of the list: 
-      <P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->&#13;        <EM
->Long Format:</EM
->
-
-        this gives you a large page with a non-editable summary of the fields
-        of each bug.</TD
-></TR
-><TR
-><TD
->&#13;        <EM
->Change Columns:</EM
->
-
-        change the bug attributes which appear in the list.</TD
-></TR
-><TR
-><TD
->&#13;        <EM
->Change several bugs at once:</EM
->
-
-        If your account is sufficiently empowered, you can make the same
-        change to all the bugs in the list - for example, changing their
-        owner.</TD
-></TR
-><TR
-><TD
->&#13;        <EM
->Send mail to bug owners:</EM
->
-
-        Sends mail to the owners of all bugs on the list.</TD
-></TR
-><TR
-><TD
->&#13;        <EM
->Edit this query:</EM
->
-
-        If you didn't get exactly the results you were looking for, you can
-        return to the Query page through this link and make small revisions
-        to the query you just made so you get more accurate results.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="bugreports"
-></A
->3.1.5. Filing Bugs</H2
-><P
->Years of bug writing experience has been distilled for your
-      reading pleasure into the 
-      <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html"
-TARGET="_top"
->&#13;      Bug Writing Guidelines</A
->. 
-      While some of the advice is Mozilla-specific, the basic principles of
-      reporting Reproducible, Specific bugs, isolating the Product you are
-      using, the Version of the Product, the Component which failed, the
-      Hardware Platform, and Operating System you were using at the time of
-      the failure go a long way toward ensuring accurate, responsible fixes
-      for the bug that bit you.</P
-><P
->The procedure for filing a test bug is as follows:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Go to 
-          <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/"
-TARGET="_top"
->&#13;          Landfill</A
->
-          in your browser and click 
-          <A
-HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi"
-TARGET="_top"
->&#13;          Enter a new bug report</A
->.
-          </P
-></LI
-><LI
-><P
->Select a product - any one will do.</P
-></LI
-><LI
-><P
->Fill in the fields. Bugzilla should have made reasonable
-          guesses, based upon your browser, for the "Platform" and "OS"
-          drop-down boxes. If they are wrong, change them.</P
-></LI
-><LI
-><P
->Select "Commit" and send in your bug report.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="patchviewer"
-></A
->3.1.6. Patch Viewer</H2
-><P
->Viewing and reviewing patches in Bugzilla is often difficult due to
-      lack of context, improper format and the inherent readability issues that
-      raw patches present.  Patch Viewer is an enhancement to Bugzilla designed
-      to fix that by offering increased context, linking to sections, and
-      integrating with Bonsai, LXR and CVS.</P
-><P
->Patch viewer allows you to:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->View patches in color, with side-by-side view rather than trying
-        to interpret the contents of the patch.</TD
-></TR
-><TR
-><TD
->See the difference between two patches.</TD
-></TR
-><TR
-><TD
->Get more context in a patch.</TD
-></TR
-><TR
-><TD
->Collapse and expand sections of a patch for easy
-        reading.</TD
-></TR
-><TR
-><TD
->Link to a particular section of a patch for discussion or
-        review</TD
-></TR
-><TR
-><TD
->Go to Bonsai or LXR to see more context, blame, and
-        cross-references for the part of the patch you are looking at</TD
-></TR
-><TR
-><TD
->Create a rawtext unified format diff out of any patch, no
-        matter what format it came from</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_view"
-></A
->3.1.6.1. Viewing Patches in Patch Viewer</H3
-><P
->The main way to view a patch in patch viewer is to click on the
-        "Diff" link next to a patch in the Attachments list on a bug. You may
-        also do this within the edit window by clicking the "View Attachment As
-        Diff" button in the Edit Attachment screen.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_diff"
-></A
->3.1.6.2. Seeing the Difference Between Two Patches</H3
-><P
->To see the difference between two patches, you must first view the
-        newer patch in Patch Viewer.  Then select the older patch from the
-        dropdown at the top of the page ("Differences between [dropdown] and
-        this patch") and click the "Diff" button. This will show you what
-        is new or changed in the newer patch.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_context"
-></A
->3.1.6.3. Getting More Context in a Patch</H3
-><P
->To get more context in a patch, you put a number in the textbox at
-        the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
-        This will give you that many lines of context before and after each
-        change. Alternatively, you can click on the "File" link there and it
-        will show each change in the full context of the file. This feature only
-        works against files that were diffed using "cvs diff".</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_collapse"
-></A
->3.1.6.4. Collapsing and Expanding Sections of a Patch</H3
-><P
->To view only a certain set of files in a patch (for example, if a
-        patch is absolutely huge and you want to only review part of it at a
-        time), you can click the "(+)" and "(-)" links next to each file (to
-        expand it or collapse it). If you want to collapse all files or expand
-        all files, you can click the "Collapse All" and "Expand All" links at the
-        top of the page.</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_link"
-></A
->3.1.6.5. Linking to a Section of a Patch</H3
-><P
->To link to a section of a patch (for example, if you want to be
-        able to give someone a URL to show them which part you are talking
-        about) you simply click the "Link Here" link on the section header. The
-        resulting URL can be copied and used in discussion. (Copy Link
-        Location in Mozilla works as well.)</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_bonsai_lxr"
-></A
->3.1.6.6. Going to Bonsai and LXR</H3
-><P
->To go to Bonsai to get blame for the lines you are interested in,
-        you can click the "Lines XX-YY" link on the section header you are
-        interested in. This works even if the patch is against an old
-        version of the file, since Bonsai stores all versions of the file.</P
-><P
->To go to LXR, you click on the filename on the file header
-        (unfortunately, since LXR only does the most recent version, line
-        numbers are likely to rot).</P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="patchviewer_unified_diff"
-></A
->3.1.6.7. Creating a Unified Diff</H3
-><P
->If the patch is not in a format that you like, you can turn it
-        into a unified diff format by clicking the "Raw Unified" link at the top
-        of the page.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="hintsandtips.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Hints and Tips</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/http.html

-<HTML
-><HEAD
-><TITLE
->HTTP Server Configuration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Step-by-step Install"
-HREF="stepbystep.html"><LINK
-REL="NEXT"
-TITLE="Optional Additional Configuration"
-HREF="extraconfig.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="http"
-></A
->4.2. HTTP Server Configuration</H1
-><P
->The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
-    that can be configured to run <A
-HREF="glossary.html#gloss-cgi"
-><I
-CLASS="glossterm"
->CGI</I
-></A
-> scripts
-    should be able to handle Bugzilla. No matter what web server you choose, but
-    especially if you choose something other than Apache, you should be sure to read
-    <A
-HREF="security.html#security-access"
->Section 4.5.4</A
->.
-    </P
-><P
->The plan for this section is to eventually document the specifics of how to lock
-    down permissions on individual web servers.
-    </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="http-apache"
-></A
->4.2.1. Apache <SPAN
-CLASS="productname"
->httpd</SPAN
-></H2
-><P
->You will have to make sure that Apache is properly
-      configured to run the Bugzilla CGI scripts. You also need to make sure
-      that the <TT
-CLASS="filename"
->.htaccess</TT
-> files created by
-      <B
-CLASS="command"
->./checksetup.pl</B
-> are allowed to override Apache's normal access
-      permissions or else important password information may be exposed to the
-      Internet.
-      </P
-><P
->You need to configure Apache to run .cgi files outside the
-        <TT
-CLASS="filename"
->cgi-bin</TT
-> directory.
-        Open your
-        <TT
-CLASS="filename"
->httpd.conf</TT
-> file and make sure the
-        following line exists and is uncommented:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;AddHandler cgi-script .cgi
-        </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->To allow <TT
-CLASS="filename"
->.htaccess</TT
-> files to override
-        permissions and .cgi files to run in the Bugzilla directory, make sure
-        the following two lines are in a <TT
-CLASS="computeroutput"
->Directory</TT
->
-        directive that applies to the Bugzilla directory on your system
-        (either the Bugzilla directory or one of its parents).
-        </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;Options +ExecCGI
-AllowOverride Limit
-        </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->You should modify the &#60;DirectoryIndex&#62; parameter for
-        the Apache virtual host running your Bugzilla installation to
-        allow <TT
-CLASS="filename"
->index.cgi</TT
-> as the index page for a
-        directory, as well as the usual <TT
-CLASS="filename"
->index.html</TT
->,
-        <TT
-CLASS="filename"
->index.htm</TT
->, and so forth. </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->For more information on Apache and its directives, see the
-          glossary entry on <A
-HREF="glossary.html#gloss-apache"
-><I
-CLASS="glossterm"
->Apache</I
-></A
->.
-          </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="http-iis"
-></A
->4.2.2. Microsoft <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
-></H2
-><P
->If you need, or for some reason even want, to use Microsoft's
-      <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
-> or
-      <SPAN
-CLASS="productname"
->Personal Web Server</SPAN
-> you should be able
-      to. You will need to configure them to know how to run CGI scripts,
-      however. This is described in Microsoft Knowledge Base article
-      <A
-HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp"
-TARGET="_top"
->Q245225</A
->
-      for <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
-> and
-      <A
-HREF="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp"
-TARGET="_top"
->Q231998</A
->          
-      for <SPAN
-CLASS="productname"
->Personal Web Server</SPAN
->.
-      </P
-><P
->Also, and this can't be stressed enough, make sure that files such as
-      <TT
-CLASS="filename"
->localconfig</TT
-> and your <TT
-CLASS="filename"
->data</TT
->
-      directory are secured as described in <A
-HREF="security.html#security-access"
->Section 4.5.4</A
->.
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="http-aol"
-></A
->4.2.3. AOL Server</H2
-><P
->Ben FrantzDale reported success using AOL Server with Bugzilla. He
-      reported his experience and what appears below is based on that.
-      </P
-><P
->AOL Server will have to be configured to run
-      <A
-HREF="glossary.html#gloss-cgi"
-><I
-CLASS="glossterm"
->CGI</I
-></A
-> scripts, please consult
-      the documentation that came with your server for more information on
-      how to do this.
-      </P
-><P
->Because AOL Server doesn't support <TT
-CLASS="filename"
->.htaccess</TT
->
-      files, you'll have to create a <A
-HREF="glossary.html#gloss-tcl"
-><I
-CLASS="glossterm"
->TCL</I
-></A
->
-      script. You should create an <TT
-CLASS="filename"
->aolserver/modules/tcl/filter.tcl</TT
->
-      file (the filename shouldn't matter) with the following contents (change
-      <TT
-CLASS="computeroutput"
->/bugzilla/</TT
-> to the web-based path to
-      your Bugzilla installation):
-      </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;ns_register_filter preauth GET /bugzilla/localconfig filter_deny
-ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny
-ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny
-ns_register_filter preauth GET /bugzilla/*.pl filter_deny
-ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
-ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
-ns_register_filter preauth GET /bugzilla/data/* filter_deny
-ns_register_filter preauth GET /bugzilla/template/* filter_deny
-                                                                                
-proc filter_deny { why } {
-    ns_log Notice "filter_deny"
-    return "filter_return"
-}
-      </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This probably doesn't account for all possible editor backup
-        files so you may wish to add some additional variations of
-        <TT
-CLASS="filename"
->localconfig</TT
->. For more information, see 
-        <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
-TARGET="_top"
->&#13;        bug 186383</A
-> or <A
-HREF="http://online.securityfocus.com/bid/6501"
-TARGET="_top"
->Bugtraq ID 6501</A
->.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using webdot from research.att.com (the default
-        configuration for the <TT
-CLASS="option"
->webdotbase</TT
-> paramater), you
-        will need to allow access to <TT
-CLASS="filename"
->data/webdot/*.dot</TT
->
-        for the reasearch.att.com machine.
-        </P
-><P
->If you are using a local installation of <A
-HREF="http://www.graphviz.org"
-TARGET="_top"
->GraphViz</A
->, you will need to allow
-        everybody to access <TT
-CLASS="filename"
->*.png</TT
->,
-        <TT
-CLASS="filename"
->*.gif</TT
->, <TT
-CLASS="filename"
->*.jpg</TT
->, and
-        <TT
-CLASS="filename"
->*.map</TT
-> in the
-        <TT
-CLASS="filename"
->data/webdot</TT
-> directory.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Step-by-step Install</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Optional Additional Configuration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/index.html

 <HTML
 ><HEAD
 ><TITLE
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TITLE
 ><META
 NAME="GENERATOR"
@@ -47,14 +47,14 @@ CLASS="title"
 ><A
 NAME="AEN2"
 ></A
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</H1
 ><H3
 CLASS="corpauthor"
 >The Bugzilla Team</H3
 ><P
 CLASS="pubdate"
->2004-01-15<BR></P
+>2004-01-24<BR></P
 ><DIV
 ><DIV
 CLASS="abstract"
@@ -127,211 +127,187 @@ HREF="conventions.html"
 ></DD
 ><DT
 >2. <A
-HREF="introduction.html"
->Introduction</A
+HREF="installing-bugzilla.html"
+>Installing Bugzilla</A
 ></DT
 ><DD
 ><DL
 ><DT
 >2.1. <A
-HREF="what-is-bugzilla.html"
->What is Bugzilla?</A
+HREF="installation.html"
+>Installation</A
 ></DT
 ><DT
 >2.2. <A
-HREF="why-tracking.html"
->Why use a bug-tracking system?</A
+HREF="configuration.html"
+>Configuration</A
 ></DT
 ><DT
 >2.3. <A
-HREF="why-bugzilla.html"
->Why use Bugzilla?</A
+HREF="extraconfig.html"
+>Optional Additional Configuration</A
+></DT
+><DT
+>2.4. <A
+HREF="os-specific.html"
+>OS-Specific Installation Notes</A
+></DT
+><DT
+>2.5. <A
+HREF="troubleshooting.html"
+>Troubleshooting</A
 ></DT
 ></DL
 ></DD
 ><DT
 >3. <A
-HREF="using.html"
->Using Bugzilla</A
+HREF="administration.html"
+>Administering Bugzilla</A
 ></DT
 ><DD
 ><DL
 ><DT
 >3.1. <A
-HREF="using-intro.html"
->Introduction</A
+HREF="parameters.html"
+>Bugzilla Configuration</A
 ></DT
 ><DT
 >3.2. <A
-HREF="myaccount.html"
->Create a Bugzilla Account</A
+HREF="useradmin.html"
+>User Administration</A
 ></DT
 ><DT
 >3.3. <A
-HREF="bug_page.html"
->Anatomy of a Bug</A
+HREF="products.html"
+>Products</A
 ></DT
 ><DT
 >3.4. <A
-HREF="query.html"
->Searching for Bugs</A
+HREF="components.html"
+>Components</A
 ></DT
 ><DT
 >3.5. <A
-HREF="list.html"
->Bug Lists</A
+HREF="versions.html"
+>Versions</A
 ></DT
 ><DT
 >3.6. <A
-HREF="bugreports.html"
->Filing Bugs</A
+HREF="milestones.html"
+>Milestones</A
 ></DT
 ><DT
 >3.7. <A
-HREF="patchviewer.html"
->Patch Viewer</A
+HREF="voting.html"
+>Voting</A
 ></DT
 ><DT
 >3.8. <A
-HREF="hintsandtips.html"
->Hints and Tips</A
+HREF="groups.html"
+>Groups and Group Security</A
 ></DT
 ><DT
 >3.9. <A
-HREF="userpreferences.html"
->User Preferences</A
-></DT
-><DT
->3.10. <A
-HREF="reporting.html"
->Reports</A
+HREF="upgrading.html"
+>Upgrading to New Releases</A
 ></DT
 ></DL
 ></DD
 ><DT
 >4. <A
-HREF="installation.html"
->Installation</A
+HREF="customization.html"
+>Customising Bugzilla</A
 ></DT
 ><DD
 ><DL
 ><DT
 >4.1. <A
-HREF="stepbystep.html"
->Step-by-step Install</A
+HREF="cust-templates.html"
+>Template Customization</A
 ></DT
 ><DT
 >4.2. <A
-HREF="http.html"
->HTTP Server Configuration</A
+HREF="cust-hooks.html"
+>Template Hooks</A
 ></DT
 ><DT
 >4.3. <A
-HREF="extraconfig.html"
->Optional Additional Configuration</A
+HREF="cust-change-permissions.html"
+>Customizing Who Can Change What</A
 ></DT
 ><DT
 >4.4. <A
-HREF="os-specific.html"
->OS Specific Installation Notes</A
+HREF="dbmodify.html"
+>Modifying Your Running System</A
 ></DT
 ><DT
 >4.5. <A
-HREF="security.html"
->Bugzilla Security</A
+HREF="dbdoc.html"
+>MySQL Bugzilla Database Introduction</A
 ></DT
 ><DT
 >4.6. <A
-HREF="troubleshooting.html"
->Troubleshooting</A
+HREF="integration.html"
+>Integrating Bugzilla with Third-Party Tools</A
 ></DT
 ></DL
 ></DD
 ><DT
 >5. <A
-HREF="administration.html"
->Administering Bugzilla</A
+HREF="using.html"
+>Using Bugzilla</A
 ></DT
 ><DD
 ><DL
 ><DT
 >5.1. <A
-HREF="parameters.html"
->Bugzilla Configuration</A
+HREF="using-intro.html"
+>Introduction</A
 ></DT
 ><DT
 >5.2. <A
-HREF="useradmin.html"
->User Administration</A
+HREF="myaccount.html"
+>Create a Bugzilla Account</A
 ></DT
 ><DT
 >5.3. <A
-HREF="products.html"
->Products</A
+HREF="bug_page.html"
+>Anatomy of a Bug</A
 ></DT
 ><DT
 >5.4. <A
-HREF="components.html"
->Components</A
+HREF="query.html"
+>Searching for Bugs</A
 ></DT
 ><DT
 >5.5. <A
-HREF="versions.html"
->Versions</A
+HREF="list.html"
+>Bug Lists</A
 ></DT
 ><DT
 >5.6. <A
-HREF="milestones.html"
->Milestones</A
+HREF="bugreports.html"
+>Filing Bugs</A
 ></DT
 ><DT
 >5.7. <A
-HREF="voting.html"
->Voting</A
+HREF="patchviewer.html"
+>Patch Viewer</A
 ></DT
 ><DT
 >5.8. <A
-HREF="groups.html"
->Groups and Group Security</A
+HREF="hintsandtips.html"
+>Hints and Tips</A
 ></DT
 ><DT
 >5.9. <A
-HREF="upgrading.html"
->Upgrading to New Releases</A
-></DT
-></DL
-></DD
-><DT
->6. <A
-HREF="customization.html"
->Customising Bugzilla</A
-></DT
-><DD
-><DL
-><DT
->6.1. <A
-HREF="cust-templates.html"
->Template Customization</A
-></DT
-><DT
->6.2. <A
-HREF="cust-change-permissions.html"
->Customizing Who Can Change What</A
-></DT
-><DT
->6.3. <A
-HREF="dbmodify.html"
->Modifying Your Running System</A
-></DT
-><DT
->6.4. <A
-HREF="dbdoc.html"
->MySQL Bugzilla Database Introduction</A
+HREF="userpreferences.html"
+>User Preferences</A
 ></DT
 ><DT
->6.5. <A
-HREF="integration.html"
->Integrating Bugzilla with Third-Party Tools</A
+>5.10. <A
+HREF="reporting.html"
+>Reports</A
 ></DT
 ></DL
 ></DD
@@ -356,6 +332,25 @@ HREF="cmdline.html"
 ></DD
 ><DT
 >C. <A
+HREF="install-perlmodules-manual.html"
+>Manual Installation of Perl Modules</A
+></DT
+><DD
+><DL
+><DT
+>C.1. <A
+HREF="modules-manual-instructions.html"
+>Instructions</A
+></DT
+><DT
+>C.2. <A
+HREF="modules-manual-download.html"
+>Download Locations</A
+></DT
+></DL
+></DD
+><DT
+>D. <A
 HREF="gfdl.html"
 >GNU Free Documentation License</A
 ></DT
@@ -364,57 +359,57 @@ HREF="gfdl.html"
 ><DT
 >0. <A
 HREF="gfdl-0.html"
->PREAMBLE</A
+>Preamble</A
 ></DT
 ><DT
 >1. <A
 HREF="gfdl-1.html"
->APPLICABILITY AND DEFINITIONS</A
+>Applicability and Definition</A
 ></DT
 ><DT
 >2. <A
 HREF="gfdl-2.html"
->VERBATIM COPYING</A
+>Verbatim Copying</A
 ></DT
 ><DT
 >3. <A
 HREF="gfdl-3.html"
->COPYING IN QUANTITY</A
+>Copying in Quantity</A
 ></DT
 ><DT
 >4. <A
 HREF="gfdl-4.html"
->MODIFICATIONS</A
+>Modifications</A
 ></DT
 ><DT
 >5. <A
 HREF="gfdl-5.html"
->COMBINING DOCUMENTS</A
+>Combining Documents</A
 ></DT
 ><DT
 >6. <A
 HREF="gfdl-6.html"
->COLLECTIONS OF DOCUMENTS</A
+>Collections of Documents</A
 ></DT
 ><DT
 >7. <A
 HREF="gfdl-7.html"
->AGGREGATION WITH INDEPENDENT WORKS</A
+>Aggregation with Independent Works</A
 ></DT
 ><DT
 >8. <A
 HREF="gfdl-8.html"
->TRANSLATION</A
+>Translation</A
 ></DT
 ><DT
 >9. <A
 HREF="gfdl-9.html"
->TERMINATION</A
+>Termination</A
 ></DT
 ><DT
 >10. <A
 HREF="gfdl-10.html"
->FUTURE REVISIONS OF THIS LICENSE</A
+>Future Revisions of this License</A
 ></DT
 ><DT
 ><A
@@ -436,50 +431,20 @@ CLASS="LOT"
 CLASS="LOT"
 ><DT
 ><B
->List of Figures</B
-></DT
-><DT
->4-1. <A
-HREF="stepbystep.html#install-mysql-packets"
->Set Max Packet Size in MySQL</A
-></DT
-><DT
->4-2. <A
-HREF="troubleshooting.html#trouble-filetemp-errors"
->Other File::Temp error messages</A
-></DT
-><DT
->4-3. <A
-HREF="troubleshooting.html#trouble-filetemp-patch"
->Patch for File::Temp in Perl 5.6.0</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="LOT"
-><DL
-CLASS="LOT"
-><DT
-><B
 >List of Examples</B
 ></DT
 ><DT
->4-1. <A
-HREF="stepbystep.html#install-perlmodules-cpan"
->Installing perl modules with CPAN</A
-></DT
-><DT
->5-1. <A
+>3-1. <A
 HREF="upgrading.html#upgrade-cvs"
 >Upgrading using CVS</A
 ></DT
 ><DT
->5-2. <A
+>3-2. <A
 HREF="upgrading.html#upgrade-tarball"
 >Upgrading using the tarball</A
 ></DT
 ><DT
->5-3. <A
+>3-3. <A
 HREF="upgrading.html#upgrade-patches"
 >Upgrading using patches</A
 ></DT

docs/html/introduction.html → docs/html/install-perlmodules-manual.html

 <HTML
 ><HEAD
 ><TITLE
->Introduction</TITLE
+>Manual Installation of Perl Modules</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
-TITLE="Document Conventions"
-HREF="conventions.html"><LINK
+TITLE="Command-line Search Interface"
+HREF="cmdline.html"><LINK
 REL="NEXT"
-TITLE="What is Bugzilla?"
-HREF="what-is-bugzilla.html"></HEAD
+TITLE="Instructions"
+HREF="modules-manual-instructions.html"></HEAD
 ><BODY
-CLASS="chapter"
+CLASS="appendix"
 BGCOLOR="#FFFFFF"
 TEXT="#000000"
 LINK="#0000FF"
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -44,7 +44,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="conventions.html"
+HREF="cmdline.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -58,7 +58,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="what-is-bugzilla.html"
+HREF="modules-manual-instructions.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -68,12 +68,12 @@ ACCESSKEY="N"
 ALIGN="LEFT"
 WIDTH="100%"></DIV
 ><DIV
-CLASS="chapter"
+CLASS="appendix"
 ><H1
 ><A
-NAME="introduction"
+NAME="install-perlmodules-manual"
 ></A
->Chapter 2. Introduction</H1
+>Appendix C. Manual Installation of Perl Modules</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -82,19 +82,14 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->2.1. <A
-HREF="what-is-bugzilla.html"
->What is Bugzilla?</A
+>C.1. <A
+HREF="modules-manual-instructions.html"
+>Instructions</A
 ></DT
 ><DT
->2.2. <A
-HREF="why-tracking.html"
->Why use a bug-tracking system?</A
-></DT
-><DT
->2.3. <A
-HREF="why-bugzilla.html"
->Why use Bugzilla?</A
+>C.2. <A
+HREF="modules-manual-download.html"
+>Download Locations</A
 ></DT
 ></DL
 ></DIV
@@ -115,7 +110,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="conventions.html"
+HREF="cmdline.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -133,7 +128,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="what-is-bugzilla.html"
+HREF="modules-manual-instructions.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -143,7 +138,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Document Conventions</TD
+>Command-line Search Interface</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -153,7 +148,7 @@ VALIGN="top"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->What is Bugzilla?</TD
+>Instructions</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/installation.html

@@ -7,17 +7,20 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
+REL="UP"
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
 REL="PREVIOUS"
-TITLE="Reports"
-HREF="reporting.html"><LINK
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
 REL="NEXT"
-TITLE="Step-by-step Install"
-HREF="stepbystep.html"></HEAD
+TITLE="Configuration"
+HREF="configuration.html"></HEAD
 ><BODY
-CLASS="chapter"
+CLASS="section"
 BGCOLOR="#FFFFFF"
 TEXT="#000000"
 LINK="#0000FF"
@@ -35,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -44,7 +47,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="reporting.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -52,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
-></TD
+>Chapter 2. Installing Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="stepbystep.html"
+HREF="configuration.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -68,235 +71,872 @@ ACCESSKEY="N"
 ALIGN="LEFT"
 WIDTH="100%"></DIV
 ><DIV
-CLASS="chapter"
+CLASS="section"
 ><H1
+CLASS="section"
 ><A
 NAME="installation"
 ></A
->Chapter 4. Installation</H1
+>2.1. Installation</H1
 ><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->4.1. <A
-HREF="stepbystep.html"
->Step-by-step Install</A
-></DT
-><DD
-><DL
-><DT
->4.1.1. <A
-HREF="stepbystep.html#install-perl"
->Perl</A
-></DT
-><DT
->4.1.2. <A
-HREF="stepbystep.html#install-mysql"
->MySQL</A
-></DT
-><DT
->4.1.3. <A
-HREF="stepbystep.html#install-webserver"
->HTTP Server</A
-></DT
-><DT
->4.1.4. <A
-HREF="stepbystep.html#install-bzfiles"
->Bugzilla</A
-></DT
-><DT
->4.1.5. <A
-HREF="stepbystep.html#AEN522"
-><TT
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>If you just want to <EM
+>use</EM
+> Bugzilla, 
+      you do not need to install it. None of this chapter is relevant to
+      you. Ask your Bugzilla administrator
+      for the URL to access it over the web.
+      </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>The Bugzilla server software is usually installed on Linux or 
+    Solaris. 
+    If you are installing on another OS, check <A
+HREF="os-specific.html"
+>Section 2.4</A
+>
+    before you start your installation to see if there are any special
+    instructions.
+    </P
+><P
+>&#13;      As an alternative to following these instructions, you may wish to
+      try Arne Schirmacher's unofficial and unsupported 
+      <A
+HREF="http://www.softwaretesting.de/article/view/33/1/8/"
+TARGET="_top"
+>Bugzilla
+      Installer</A
+>, which installs Bugzilla and all its prerequisites
+      on Linux or Solaris systems.
+    </P
+><P
+>This guide assumes that you have administrative access to the
+    Bugzilla machine. It not possible to
+    install and run Bugzilla itself without administrative access except
+    in the very unlikely event that every single prerequisite is
+    already installed.
+    </P
+><DIV
+CLASS="warning"
+><P
+></P
+><TABLE
+CLASS="warning"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The installation process may make your machine insecure for
+      short periods of time. Make sure there is a firewall between you
+      and the Internet.
+      </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>&#13;    You are strongly recommended to make a backup of your system
+    before installing Bugzilla (and at regular intervals thereafter :-).
+    </P
+><P
+>In outline, the installation proceeds as follows:
+    </P
+><DIV
+CLASS="procedure"
+><OL
+TYPE="1"
+><LI
+><P
+><A
+HREF="installation.html#install-perl"
+>Install Perl</A
+>
+        (5.6.0 or above)
+        </P
+></LI
+><LI
+><P
+><A
+HREF="installation.html#install-mysql"
+>Install MySQL</A
+>
+        (3.23.41 or above)
+        </P
+></LI
+><LI
+><P
+><A
+HREF="installation.html#install-webserver"
+>Install a Webserver</A
+>
+        </P
+></LI
+><LI
+><P
+><A
+HREF="installation.html#install-bzfiles"
+>Install Bugzilla</A
+>
+        </P
+></LI
+><LI
+><P
+><A
+HREF="installation.html#install-perlmodules"
+>Install Perl modules</A
+>
+        </P
+></LI
+><LI
+><P
+>Configure all of the above.
+        </P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="install-perl"
+></A
+>2.1.1. Perl</H2
+><P
+>Installed Version Test: <TT
 CLASS="filename"
->checksetup.pl</TT
+>perl -v</TT
+></P
+><P
+>Any machine that doesn't have Perl on it is a sad machine indeed.
+      If you don't have it and your OS doesn't provide official packages, 
+      visit <A
+HREF="http://www.perl.com"
+TARGET="_top"
+>http://www.perl.com</A
+>.
+      Although Bugzilla runs with Perl 5.6.0,
+      it's a good idea to be using the latest stable version. 
+      As of this writing, that is Perl 5.8.2.</P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="install-mysql"
+></A
+>2.1.2. MySQL</H2
+><P
+>Installed Version Test: <TT
+CLASS="filename"
+>mysql -V</TT
+></P
+><P
+>&#13;      If you don't have it and your OS doesn't provide official packages, 
+      visit <A
+HREF="http://www.mysql.com"
+TARGET="_top"
+>http://www.mysql.com</A
+>. You need MySQL version
+      3.23.41 or higher.
+      </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Many of the binary
+        versions of MySQL store their data files in 
+        <TT
+CLASS="filename"
+>/var</TT
+>.
+        On some Unix systems, this is part of a smaller root partition,
+        and may not have room for your bug database. To change the data
+         directory, you have to build MySQL from source yourself, and
+         set it as an option to <TT
+CLASS="filename"
+>configure</TT
+>.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>If you install from something other than a packaging/installation
+      system (such as .rpm, .dep, .exe, or .msi) make sure the MySQL server
+      is started when the machine boots.
+      </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="install-webserver"
 ></A
-></DT
-><DT
->4.1.6. <A
-HREF="stepbystep.html#install-perlmodules"
->Perl Modules</A
-></DT
-><DT
->4.1.7. <A
-HREF="stepbystep.html#AEN768"
->Configuring Bugzilla</A
-></DT
-></DL
-></DD
-><DT
->4.2. <A
-HREF="http.html"
->HTTP Server Configuration</A
-></DT
-><DD
-><DL
-><DT
->4.2.1. <A
-HREF="http.html#http-apache"
->Apache <SPAN
-CLASS="productname"
->httpd</SPAN
+>2.1.3. Web Server</H2
+><P
+>Installed Version Test: view the default welcome page at
+      http://&#60;your-machine&#62;/</P
+><P
+>You have freedom of choice here, pretty much any web server that
+      is capable of running <A
+HREF="glossary.html#gloss-cgi"
+><I
+CLASS="glossterm"
+>CGI</I
 ></A
-></DT
-><DT
->4.2.2. <A
-HREF="http.html#http-iis"
->Microsoft <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
+>
+      scripts will work.
+       However, we strongly recommend using the Apache web server
+       (either 1.3.x or 2.x), and 
+       the installation instructions usually assume you are
+        using it. If you have got Bugzilla working using another webserver,
+        please share your experiences with us by filing a bug in <A
+HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
+TARGET="_top"
+>Bugzilla Documentation</A
+>.
+      </P
+><P
+>&#13;      If you don't have Apache and your OS doesn't provide official packages, 
+      visit <A
+HREF="http://httpd.apache.org/"
+TARGET="_top"
+>http://httpd.apache.org/</A
+>.
+      </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="install-bzfiles"
 ></A
-></DT
-><DT
->4.2.3. <A
-HREF="http.html#http-aol"
->AOL Server</A
-></DT
-></DL
-></DD
-><DT
->4.3. <A
-HREF="extraconfig.html"
->Optional Additional Configuration</A
-></DT
-><DD
-><DL
-><DT
->4.3.1. <A
-HREF="extraconfig.html#AEN843"
->Dependency Charts</A
-></DT
-><DT
->4.3.2. <A
-HREF="extraconfig.html#AEN858"
->Bug Graphs</A
-></DT
-><DT
->4.3.3. <A
-HREF="extraconfig.html#AEN871"
->The Whining Cron</A
-></DT
-><DT
->4.3.4. <A
-HREF="extraconfig.html#bzldap"
->LDAP Authentication</A
-></DT
-><DT
->4.3.5. <A
-HREF="extraconfig.html#content-type"
->Preventing untrusted Bugzilla content from executing malicious
-      Javascript code</A
-></DT
-><DT
->4.3.6. <A
-HREF="extraconfig.html#mod_perl"
->Bugzilla and <TT
+>2.1.4. Bugzilla</H2
+><P
+>&#13;        Download a Bugzilla tarball (or check it out from CVS) and place
+        it in a suitable directory, writable by the default web server user 
+        (probably <SPAN
+CLASS="QUOTE"
+>"nobody"</SPAN
+>). 
+        Good locations are either directly in the main web space for your
+        web server or perhaps in 
+        <TT
+CLASS="filename"
+>/usr/local</TT
+>
+        with a symbolic link from the web space.
+      </P
+><DIV
+CLASS="caution"
+><P
+></P
+><TABLE
+CLASS="caution"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The default Bugzilla distribution is not designed to be placed
+        in a <TT
 CLASS="filename"
->mod_perl</TT
+>cgi-bin</TT
+> directory. This
+        includes any directory which is configured using the
+        <TT
+CLASS="option"
+>ScriptAlias</TT
+> directive of Apache.
+        </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Once all the files are in a web accessible directory, make that
+      directory writable by your webserver's user. This is a temporary step
+      until you run the 
+      <TT
+CLASS="filename"
+>checksetup.pl</TT
+>
+      script, which locks down your installation.</P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="install-perlmodules"
 ></A
-></DT
-><DT
->4.3.7. <A
-HREF="extraconfig.html#mod-throttle"
+>2.1.5. Perl Modules</H2
+><P
+>Bugzilla's installation process is based
+      on a script called <TT
+CLASS="filename"
+>checksetup.pl</TT
+>. 
+      The first thing it checks is whether you have appropriate 
+      versions of all the required
+      Perl modules. The aim of this section is to pass this check. 
+      When it passes, 
+      <EM
+>do not run it again</EM
+>, 
+      but proceed to <A
+HREF="configuration.html"
+>Section 2.2</A
+>.
+      </P
+><P
+>&#13;      At this point, you need to <TT
+CLASS="filename"
+>su</TT
+> to root. You should
+      remain as root until the end of the install. Then run:
+      </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="screen"
+><TT
+CLASS="prompt"
+>bash#</TT
+> ./checksetup.pl</PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>&#13;        <TT
+CLASS="filename"
+>checksetup.pl</TT
+> will print out a list of the
+        required and optional Perl modules, together with the versions
+        (if any) installed on your machine.
+        The list of required modules is reasonably long; however, you 
+        may already have several of them installed.
+      </P
+><P
+>&#13;        There is a meta-module called Bundle::Bugzilla, 
+        which installs all the other 
+        modules with a single command. You should use this if you are running
+        Perl 5.6.1 or above.
+      </P
+><P
+>&#13;        The preferred way of installing Perl modules is via CPAN on Unix, 
+        or PPM on Windows (see <A
+HREF="os-specific.html#win32-perlmodules"
+>Section 2.4.1.2</A
+>). These
+        instructions assume you are using CPAN; if for some reason you need 
+        to install the Perl modules manually, see 
+        <A
+HREF="install-perlmodules-manual.html"
+>Appendix C</A
+>.
+      </P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="screen"
 ><TT
+CLASS="prompt"
+>bash#</TT
+> perl -MCPAN -e 'install "&#60;modulename&#62;"'</PRE
+></FONT
+></TD
+></TR
+></TABLE
+><P
+>&#13;        If you using Bundle::Bugzilla, invoke the magic CPAN command on it.
+        Otherwise, you need to work down the 
+        list of modules that <TT
 CLASS="filename"
->mod_throttle</TT
+>checksetup.pl</TT
+> says are
+        required, in the order given, invoking the command on each.
+      </P
+><DIV
+CLASS="tip"
+><P
+></P
+><TABLE
+CLASS="tip"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Many people complain that Perl modules will not install for
+        them. Most times, the error messages complain that they are missing a
+        file in 
+        <SPAN
+CLASS="QUOTE"
+>"@INC"</SPAN
+>. 
+        Virtually every time, this error is due to permissions being set too
+        restrictively for you to compile Perl modules or not having the
+        necessary Perl development libraries installed on your system.
+        Consult your local UNIX systems administrator for help solving these
+        permissions issues; if you 
+        <EM
+>are</EM
+>
+        the local UNIX sysadmin, please consult the newsgroup/mailing list
+        for further assistance or hire someone to help you out.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>&#13;        Here is a complete list of modules and their minimum versions.
+        Some modules have special installation notes, which follow.
+      </P
+><P
+>Required Perl modules:
+      <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>&#13;            AppConfig (1.52)
+          </P
+></LI
+><LI
+><P
+>&#13;            CGI (2.93)
+          </P
+></LI
+><LI
+><P
+>&#13;            Data::Dumper (any)
+          </P
+></LI
+><LI
+><P
+>&#13;            Date::Format (2.21)
+          </P
+></LI
+><LI
+><P
+>&#13;            DBI (1.32)
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-dbd-mysql"
+>DBD::mysql</A
+>
+            (2.1010)
+          </P
+></LI
+><LI
+><P
+>&#13;            File::Spec (0.82)
+          </P
+></LI
+><LI
+><P
+>&#13;            File::Temp (any)
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-template"
+>Template</A
+>
+            (2.08)
+          </P
+></LI
+><LI
+><P
+>&#13;            Text::Wrap (2001.0131)
+          </P
+></LI
+></OL
 >
 
-      and Security</A
-></DT
-></DL
-></DD
-><DT
->4.4. <A
-HREF="os-specific.html"
->OS Specific Installation Notes</A
-></DT
-><DD
-><DL
-><DT
->4.4.1. <A
-HREF="os-specific.html#os-win32"
->Microsoft Windows</A
-></DT
-><DT
->4.4.2. <A
-HREF="os-specific.html#os-macosx"
-><SPAN
-CLASS="productname"
->Mac OS X</SPAN
+      Optional Perl modules:
+      <P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-gd"
+>GD</A
+>
+            (1.20) for bug charting
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-chart-base"
+>Chart::Base</A
+>
+            (0.99c) for bug charting
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-gd-graph"
+>GD::Graph</A
+>
+            (any) for bug charting
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-gd-text-align"
+>GD::Text::Align</A
+>
+            (any) for bug charting
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-xml-parser"
+>XML::Parser</A
+>
+            (any) for the XML interface
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-patchreader"
+>PatchReader</A
+>
+            (0.9.1) for pretty HTML view of patches
+          </P
+></LI
+><LI
+><P
+>&#13;            <A
+HREF="installation.html#install-modules-mime-parser"
+>MIME::Parser</A
+>
+            (any) for the optional email interface
+          </P
+></LI
+></OL
+>          
+      </P
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-dbd-mysql"
+></A
+>2.1.5.1. DBD::mysql</H3
+><P
+>The installation process will ask you a few questions about the
+        desired compilation target and your MySQL installation. For most of the
+        questions the provided default will be adequate, but when asked if your
+        desired target is the MySQL or mSQL packages, you should
+        select the MySQL-related ones. Later you will be asked if you wish to
+        provide backwards compatibility with the older MySQL packages; you
+        should answer YES to this question. The default is NO.</P
+><P
+>A host of 'localhost' should be fine. A testing user of 'test',
+        with a null password, should have sufficient access to run
+        tests on the 'test' database which MySQL creates upon installation.
+        </P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-template"
+></A
+>2.1.5.2. Template Toolkit (2.08)</H3
+><P
+>When you install Template Toolkit, you'll get asked various
+        questions about features to enable. The defaults are fine, except
+        that it is recommended you use the high speed XS Stash of the Template
+        Toolkit, in order to achieve best performance.
+        </P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-gd"
+></A
+>2.1.5.3. GD (1.20)</H3
+><P
+>The GD module is only required if you want graphical reports.
+        </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The Perl GD module requires some other libraries that may or
+          may not be installed on your system, including 
+          <TT
+CLASS="classname"
+>libpng</TT
+>
+          and 
+          <TT
+CLASS="classname"
+>libgd</TT
+>. 
+          The full requirements are listed in the Perl GD module README.
+          If compiling GD fails, it's probably because you're
+          missing a required library.</P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="tip"
+><P
+></P
+><TABLE
+CLASS="tip"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The version of the GD module you need is very closely tied
+          to the <TT
+CLASS="classname"
+>libgd</TT
+> version installed on your system.
+          If you have a version 1.x of <TT
+CLASS="classname"
+>libgd</TT
+> the 2.x
+          versions of the GD module won't work for you.
+         </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-chart-base"
+></A
+>2.1.5.4. Chart::Base (0.99c)</H3
+><P
+>The Chart::Base module is only required if you want graphical 
+        reports. 
+        Note that earlier versions that 0.99c used GIFs, which are no longer
+        supported by the latest versions of GD.</P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-gd-graph"
 ></A
-></DT
-><DT
->4.4.3. <A
-HREF="os-specific.html#os-mandrake"
->Linux-Mandrake 8.0</A
-></DT
-></DL
-></DD
-><DT
->4.5. <A
-HREF="security.html"
->Bugzilla Security</A
-></DT
-><DD
-><DL
-><DT
->4.5.1. <A
-HREF="security.html#security-networking"
->TCP/IP Ports</A
-></DT
-><DT
->4.5.2. <A
-HREF="security.html#security-mysql"
->MySQL</A
-></DT
-><DT
->4.5.3. <A
-HREF="security.html#security-daemon"
->Daemon Accounts</A
-></DT
-><DT
->4.5.4. <A
-HREF="security.html#security-access"
->Web Server Access Controls</A
-></DT
-></DL
-></DD
-><DT
->4.6. <A
-HREF="troubleshooting.html"
->Troubleshooting</A
-></DT
-><DD
-><DL
-><DT
->4.6.1. <A
-HREF="troubleshooting.html#AEN1206"
->Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
-></DT
-><DT
->4.6.2. <A
-HREF="troubleshooting.html#AEN1211"
->DBD::Sponge::db prepare failed</A
-></DT
-><DT
->4.6.3. <A
-HREF="troubleshooting.html#paranoid-security"
->cannot chdir(/var/spool/mqueue)</A
-></DT
-><DT
->4.6.4. <A
-HREF="troubleshooting.html#trouble-filetemp"
->Your vendor has not defined Fcntl macro O_NOINHERIT</A
-></DT
-></DL
-></DD
-></DL
+>2.1.5.5. GD::Graph (any)</H3
+><P
+>The GD::Graph module is only required if you want graphical 
+        reports.
+        </P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-gd-text-align"
+></A
+>2.1.5.6. GD::Text::Align (any)</H3
+><P
+>The GD::Text::Align module is only required if you want graphical 
+        reports.
+        </P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-xml-parser"
+></A
+>2.1.5.7. XML::Parser (any)</H3
+><P
+>The XML::Parser module is only required if you want to import
+        XML bugs using the <TT
+CLASS="filename"
+>importxml.pl</TT
+>
+        script. This is required to use Bugzilla's "move bugs" feature;
+        you may also want to use it for migrating from another bug database.
+        XML::Parser requires that the
+        <TT
+CLASS="classname"
+>expat</TT
+> library is already installed on your machine.
+        </P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-mime-parser"
+></A
+>2.1.5.8. MIME::Parser (any)</H3
+><P
+>The MIME::Parser module is only required if you want to use the 
+        email interface
+        located in the <TT
+CLASS="filename"
+>contrib</TT
+> directory.
+        </P
+></DIV
+><DIV
+CLASS="section"
+><H3
+CLASS="section"
+><A
+NAME="install-modules-patchreader"
+></A
+>2.1.5.9. PatchReader (0.9.1)</H3
+><P
+>The PatchReader module is only required if you want to use 
+        Patch Viewer, a
+        Bugzilla feature to show code patches in your web browser in a more
+        readable form. 
+        </P
+></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -315,7 +955,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="reporting.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -333,7 +973,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="stepbystep.html"
+HREF="configuration.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -343,17 +983,21 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Reports</TD
+>Installing Bugzilla</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
->&nbsp;</TD
+><A
+HREF="installing-bugzilla.html"
+ACCESSKEY="U"
+>Up</A
+></TD
 ><TD
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Step-by-step Install</TD
+>Configuration</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/database.html → docs/html/installing-bugzilla.html

 <HTML
 ><HEAD
 ><TITLE
->The Bugzilla Database</TITLE
+>Installing Bugzilla</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
-TITLE="Integrating Bugzilla with Third-Party Tools"
-HREF="integration.html"><LINK
+TITLE="Document Conventions"
+HREF="conventions.html"><LINK
 REL="NEXT"
-TITLE="Template Customization"
-HREF="cust-templates.html"></HEAD
+TITLE="Installation"
+HREF="installation.html"></HEAD
 ><BODY
-CLASS="appendix"
+CLASS="chapter"
 BGCOLOR="#FFFFFF"
 TEXT="#000000"
 LINK="#0000FF"
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -44,7 +44,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="integration.html"
+HREF="conventions.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -58,7 +58,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="cust-templates.html"
+HREF="installation.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -68,12 +68,12 @@ ACCESSKEY="N"
 ALIGN="LEFT"
 WIDTH="100%"></DIV
 ><DIV
-CLASS="appendix"
+CLASS="chapter"
 ><H1
 ><A
-NAME="database"
+NAME="installing-bugzilla"
 ></A
->Appendix A. The Bugzilla Database</H1
+>Chapter 2. Installing Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -82,83 +82,202 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->A.1. <A
-HREF="cust-templates.html"
->Template Customization</A
+>2.1. <A
+HREF="installation.html"
+>Installation</A
 ></DT
 ><DD
 ><DL
 ><DT
->A.1.1. <A
-HREF="cust-templates.html#AEN1667"
->What to Edit</A
+>2.1.1. <A
+HREF="installation.html#install-perl"
+>Perl</A
 ></DT
 ><DT
->A.1.2. <A
-HREF="cust-templates.html#AEN1690"
->How To Edit Templates</A
+>2.1.2. <A
+HREF="installation.html#install-mysql"
+>MySQL</A
 ></DT
 ><DT
->A.1.3. <A
-HREF="cust-templates.html#AEN1700"
->Template Formats</A
+>2.1.3. <A
+HREF="installation.html#install-webserver"
+>Web Server</A
 ></DT
 ><DT
->A.1.4. <A
-HREF="cust-templates.html#AEN1713"
->Particular Templates</A
+>2.1.4. <A
+HREF="installation.html#install-bzfiles"
+>Bugzilla</A
 ></DT
 ><DT
->A.1.5. <A
-HREF="cust-templates.html#template-http-accept"
->Configuring Bugzilla to Detect the User's Language</A
+>2.1.5. <A
+HREF="installation.html#install-perlmodules"
+>Perl Modules</A
 ></DT
 ></DL
 ></DD
 ><DT
->A.2. <A
-HREF="cust-change-permissions.html"
->Change Permission Customization</A
+>2.2. <A
+HREF="configuration.html"
+>Configuration</A
+></DT
+><DD
+><DL
+><DT
+>2.2.1. <A
+HREF="configuration.html#localconfig"
+>localconfig</A
+></DT
+><DT
+>2.2.2. <A
+HREF="configuration.html#mysql"
+>MySQL</A
+></DT
+><DT
+>2.2.3. <A
+HREF="configuration.html#AEN400"
+>checksetup.pl</A
 ></DT
 ><DT
->A.3. <A
-HREF="dbmodify.html"
->Modifying Your Running System</A
+>2.2.4. <A
+HREF="configuration.html#http"
+>Web server</A
 ></DT
 ><DT
->A.4. <A
-HREF="dbdoc.html"
->MySQL Bugzilla Database Introduction</A
+>2.2.5. <A
+HREF="configuration.html#install-config-bugzilla"
+>Bugzilla</A
 ></DT
 ></DL
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This document really needs to be updated with more fleshed out
-    information about primary keys, interrelationships, and maybe some nifty
-    tables to document dependencies. Any takers?</P
-></TD
-></TR
-></TABLE
+></DD
+><DT
+>2.3. <A
+HREF="extraconfig.html"
+>Optional Additional Configuration</A
+></DT
+><DD
+><DL
+><DT
+>2.3.1. <A
+HREF="extraconfig.html#AEN584"
+>Bug Graphs</A
+></DT
+><DT
+>2.3.2. <A
+HREF="extraconfig.html#AEN594"
+>Dependency Charts</A
+></DT
+><DT
+>2.3.3. <A
+HREF="extraconfig.html#AEN610"
+>The Whining Cron</A
+></DT
+><DT
+>2.3.4. <A
+HREF="extraconfig.html#patch-viewer"
+>Patch Viewer</A
+></DT
+><DT
+>2.3.5. <A
+HREF="extraconfig.html#bzldap"
+>LDAP Authentication</A
+></DT
+><DT
+>2.3.6. <A
+HREF="extraconfig.html#content-type"
+>Prevent users injecting malicious
+      Javascript</A
+></DT
+><DT
+>2.3.7. <A
+HREF="extraconfig.html#mod-throttle"
+><TT
+CLASS="filename"
+>mod_throttle</TT
+></A
+></DT
+><DT
+>2.3.8. <A
+HREF="extraconfig.html#security-networking"
+>TCP/IP Ports</A
+></DT
+><DT
+>2.3.9. <A
+HREF="extraconfig.html#security-daemon"
+>Daemon Accounts</A
+></DT
+></DL
+></DD
+><DT
+>2.4. <A
+HREF="os-specific.html"
+>OS-Specific Installation Notes</A
+></DT
+><DD
+><DL
+><DT
+>2.4.1. <A
+HREF="os-specific.html#os-win32"
+>Microsoft Windows</A
+></DT
+><DT
+>2.4.2. <A
+HREF="os-specific.html#os-macosx"
+><SPAN
+CLASS="productname"
+>Mac OS X</SPAN
+></A
+></DT
+><DT
+>2.4.3. <A
+HREF="os-specific.html#os-mandrake"
+>Linux-Mandrake 8.0</A
+></DT
+></DL
+></DD
+><DT
+>2.5. <A
+HREF="troubleshooting.html"
+>Troubleshooting</A
+></DT
+><DD
+><DL
+><DT
+>2.5.1. <A
+HREF="troubleshooting.html#general-advice"
+>General Advice</A
+></DT
+><DT
+>2.5.2. <A
+HREF="troubleshooting.html#AEN827"
+>I installed a Perl module, but 
+      <TT
+CLASS="filename"
+>checksetup.pl</TT
+> claims it's not installed!</A
+></DT
+><DT
+>2.5.3. <A
+HREF="troubleshooting.html#AEN832"
+>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
+></DT
+><DT
+>2.5.4. <A
+HREF="troubleshooting.html#AEN837"
+>DBD::Sponge::db prepare failed</A
+></DT
+><DT
+>2.5.5. <A
+HREF="troubleshooting.html#paranoid-security"
+>cannot chdir(/var/spool/mqueue)</A
+></DT
+><DT
+>2.5.6. <A
+HREF="troubleshooting.html#trouble-filetemp"
+>Your vendor has not defined Fcntl macro O_NOINHERIT</A
+></DT
+></DL
+></DD
+></DL
 ></DIV
 ></DIV
 ><DIV
@@ -177,7 +296,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="integration.html"
+HREF="conventions.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -195,7 +314,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="cust-templates.html"
+HREF="installation.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -205,7 +324,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Integrating Bugzilla with Third-Party Tools</TD
+>Document Conventions</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -215,7 +334,7 @@ VALIGN="top"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Template Customization</TD
+>Installation</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/integration.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -17,8 +17,8 @@ REL="PREVIOUS"
 TITLE="MySQL Bugzilla Database Introduction"
 HREF="dbdoc.html"><LINK
 REL="NEXT"
-TITLE="The Bugzilla FAQ"
-HREF="faq.html"></HEAD
+TITLE="Using Bugzilla"
+HREF="using.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 6. Customising Bugzilla</TD
+>Chapter 4. Customising Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="faq.html"
+HREF="using.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="integration"
 ></A
->6.5. Integrating Bugzilla with Third-Party Tools</H1
+>4.6. Integrating Bugzilla with Third-Party Tools</H1
 ><DIV
 CLASS="section"
 ><H2
@@ -85,7 +85,7 @@ CLASS="section"
 ><A
 NAME="bonsai"
 ></A
->6.5.1. Bonsai</H2
+>4.6.1. Bonsai</H2
 ><P
 >Bonsai is a web-based tool for managing 
     <A
@@ -111,7 +111,7 @@ CLASS="section"
 ><A
 NAME="cvs"
 ></A
->6.5.2. CVS</H2
+>4.6.2. CVS</H2
 ><P
 >CVS integration is best accomplished, at this point, using the
     Bugzilla Email Gateway.</P
@@ -147,7 +147,7 @@ CLASS="section"
 ><A
 NAME="scm"
 ></A
->6.5.3. Perforce SCM</H2
+>4.6.3. Perforce SCM</H2
 ><P
 >You can find the project page for Bugzilla and Teamtrack Perforce
     integration (p4dti) at: 
@@ -187,7 +187,7 @@ CLASS="section"
 ><A
 NAME="tinderbox"
 ></A
->6.5.4. Tinderbox/Tinderbox2</H2
+>4.6.4. Tinderbox/Tinderbox2</H2
 ><P
 >Tinderbox is a continuous-build system which can integrate with
     Bugzilla - see
@@ -239,7 +239,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="faq.html"
+HREF="using.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -263,7 +263,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->The Bugzilla FAQ</TD
+>Using Bugzilla</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/list.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="list"
 ></A
->3.5. Bug Lists</H1
+>5.5. Bug Lists</H1
 ><P
 >If you run a search, a list of matching bugs will be returned.
     </P

docs/html/milestones.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="milestones"
 ></A
->5.6. Milestones</H1
+>3.6. Milestones</H1
 ><P
 >Milestones are "targets" that you plan to get a bug fixed by. For
     example, you have a bug that you plan to fix for your 3.0 release, it

docs/html/modules-manual-download.html

+<HTML
+><HEAD
+><TITLE
+>Download Locations</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.17.7 
+    Development Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Manual Installation of Perl Modules"
+HREF="install-perlmodules-manual.html"><LINK
+REL="PREVIOUS"
+TITLE="Instructions"
+HREF="modules-manual-instructions.html"><LINK
+REL="NEXT"
+TITLE="GNU Free Documentation License"
+HREF="gfdl.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.17.7 
+    Development Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="modules-manual-instructions.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Appendix C. Manual Installation of Perl Modules</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="gfdl.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="modules-manual-download"
+></A
+>C.2. Download Locations</H1
+><P
+>Note: some modules are in the core distribution of
+    ActiveState Perl for Windows. Others are not available.
+    No PPM links have been provided in either of these two cases.
+    </P
+><P
+>CGI:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/CGI.pm/"
+TARGET="_top"
+>http://search.cpan.org/dist/CGI.pm/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/CGI.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/CGI.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.perldoc.com/perl5.8.0/lib/CGI.html"
+TARGET="_top"
+>http://www.perldoc.com/perl5.8.0/lib/CGI.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>TimeDate:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/TimeDate/"
+TARGET="_top"
+>http://search.cpan.org/dist/TimeDate/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/TimeDate.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/TimeDate.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm"
+TARGET="_top"
+>http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>DBI:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/DBI/"
+TARGET="_top"
+>http://search.cpan.org/dist/DBI/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBI.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBI.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://dbi.perl.org/docs/"
+TARGET="_top"
+>http://dbi.perl.org/docs/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>DBD::mysql:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/DBD-mysql/"
+TARGET="_top"
+>http://search.cpan.org/dist/DBD-mysql/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBD-Mysql.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBD-Mysql.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm"
+TARGET="_top"
+>http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>File::Spec:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/File-Spec/"
+TARGET="_top"
+>http://search.cpan.org/dist/File-Spec/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.perldoc.com/perl5.8.0/lib/File/Spec.html"
+TARGET="_top"
+>http://www.perldoc.com/perl5.8.0/lib/File/Spec.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>File::Temp:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/File-Temp/"
+TARGET="_top"
+>http://search.cpan.org/dist/File-Temp/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.perldoc.com/perl5.8.0/lib/File/Temp.html"
+TARGET="_top"
+>http://www.perldoc.com/perl5.8.0/lib/File/Temp.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>Template Toolkit:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/Template-Toolkit/"
+TARGET="_top"
+>http://search.cpan.org/dist/Template-Toolkit/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://openinteract.sourceforge.net/ppmpackages/5.6/Template-Toolkit.tar.gz"
+TARGET="_top"
+>http://openinteract.sourceforge.net/ppmpackages/5.6/Template-Toolkit.tar.gz</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.template-toolkit.org/docs.html"
+TARGET="_top"
+>http://www.template-toolkit.org/docs.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>Text::Wrap:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/Text-Tabs+Wrap/"
+TARGET="_top"
+>http://search.cpan.org/dist/Text-Tabs+Wrap/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.perldoc.com/perl5.8.0/lib/Text/Wrap.html"
+TARGET="_top"
+>http://www.perldoc.com/perl5.8.0/lib/Text/Wrap.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>GD:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/GD/"
+TARGET="_top"
+>http://search.cpan.org/dist/GD/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GD.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GD.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://stein.cshl.org/WWW/software/GD/"
+TARGET="_top"
+>http://stein.cshl.org/WWW/software/GD/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>Chart::Base:
+      
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/Chart/"
+TARGET="_top"
+>http://search.cpan.org/dist/Chart/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>GD::Graph:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/GDGraph/"
+TARGET="_top"
+>http://search.cpan.org/dist/GDGraph/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDGraph.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDGraph.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://search.cpan.org/dist/GDGraph/Graph.pm"
+TARGET="_top"
+>http://search.cpan.org/dist/GDGraph/Graph.pm</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>GD::Text::Align:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/GDTextUtil/"
+TARGET="_top"
+>http://search.cpan.org/dist/GDTextUtil/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDTextUtil.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDTextUtil.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://search.cpan.org/dist/GDTextUtil/Text/Align.pm"
+TARGET="_top"
+>http://search.cpan.org/dist/GDTextUtil/Text/Align.pm</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>MIME::Parser:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/MIME-tools/"
+TARGET="_top"
+>http://search.cpan.org/dist/MIME-tools/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
+HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/MIME-tools.zip"
+TARGET="_top"
+>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/MIME-tools.zip</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm"
+TARGET="_top"
+>http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>XML::Parser:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/dist/XML-Parser/"
+TARGET="_top"
+>http://search.cpan.org/dist/XML-Parser/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.perldoc.com/perl5.6.1/lib/XML/Parser.html"
+TARGET="_top"
+>http://www.perldoc.com/perl5.6.1/lib/XML/Parser.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+><P
+>PatchReader:
+      <P
+CLASS="literallayout"
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
+HREF="http://search.cpan.org/author/JKEISER/PatchReader/"
+TARGET="_top"
+>http://search.cpan.org/author/JKEISER/PatchReader/</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
+HREF="http://www.johnkeiser.com/mozilla/Patch_Viewer.html"
+TARGET="_top"
+>http://www.johnkeiser.com/mozilla/Patch_Viewer.html</A
+><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
+>
+    </P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="modules-manual-instructions.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="gfdl.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Instructions</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="install-perlmodules-manual.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>GNU Free Documentation License</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file

docs/html/variant-perforce.html → docs/html/modules-manual-instructions.html

 <HTML
 ><HEAD
 ><TITLE
->Perforce SCM</TITLE
+>Instructions</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
+TITLE="Manual Installation of Perl Modules"
+HREF="install-perlmodules-manual.html"><LINK
 REL="PREVIOUS"
-TITLE="Scarab"
-HREF="variant-scarab.html"><LINK
+TITLE="Manual Installation of Perl Modules"
+HREF="install-perlmodules-manual.html"><LINK
 REL="NEXT"
-TITLE="SourceForge"
-HREF="variant-sourceforge.html"></HEAD
+TITLE="Download Locations"
+HREF="modules-manual-download.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -47,7 +47,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="variant-scarab.html"
+HREF="install-perlmodules-manual.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -55,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
+>Appendix C. Manual Installation of Perl Modules</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="variant-sourceforge.html"
+HREF="modules-manual-download.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -75,25 +75,56 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="variant-perforce"
+NAME="modules-manual-instructions"
 ></A
->D.5. Perforce SCM</H1
+>C.1. Instructions</H1
 ><P
->Although Perforce isn't really a bug tracker, it can be used as
-    such through the <SPAN
-CLASS="QUOTE"
->"jobs"</SPAN
->
-    functionality.</P
+>If you need to install Perl modules manually, here's how it's done.
+    Download the module using the link given in the next section, and then
+    apply this magic incantation, as root:
+    </P
 ><P
->URL: <A
-HREF="http://www.perforce.com/perforce/technotes/note052.html"
-TARGET="_top"
->http://www.perforce.com/perforce/technotes/note052.html</A
+>  
+      <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="screen"
+><TT
+CLASS="prompt"
+>bash#</TT
+> tar -xzvf &#60;module&#62;.tar.gz
+<TT
+CLASS="prompt"
+>bash#</TT
+> cd &#60;module&#62;
+<TT
+CLASS="prompt"
+>bash#</TT
+> perl Makefile.PL
+<TT
+CLASS="prompt"
+>bash#</TT
+> make
+<TT
+CLASS="prompt"
+>bash#</TT
+> make test
+<TT
+CLASS="prompt"
+>bash#</TT
+> make install</PRE
+></FONT
+></TD
+></TR
+></TABLE
 >
     </P
-><P
->This section last updated 27 Jul 2002</P
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
@@ -111,7 +142,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="variant-scarab.html"
+HREF="install-perlmodules-manual.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -129,7 +160,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="variant-sourceforge.html"
+HREF="modules-manual-download.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -139,13 +170,13 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Scarab</TD
+>Manual Installation of Perl Modules</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="variants.html"
+HREF="install-perlmodules-manual.html"
 ACCESSKEY="U"
 >Up</A
 ></TD
@@ -153,7 +184,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->SourceForge</TD
+>Download Locations</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/myaccount.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="myaccount"
 ></A
->3.2. Create a Bugzilla Account</H1
+>5.2. Create a Bugzilla Account</H1
 ><P
 >If you want to use Bugzilla, first you need to create an account.
     Consult with the administrator responsible for your installation of

docs/html/newversions.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -79,7 +79,7 @@ NAME="newversions"
 ></A
 >1.3. New Versions</H1
 ><P
->&#13;      This is the 2.17.5 version of The Bugzilla Guide. It is so named 
+>&#13;      This is the 2.17.7 version of The Bugzilla Guide. It is so named 
       to match the current version of Bugzilla. 
       
         This version of the guide, like its associated Bugzilla version, is a
@@ -91,8 +91,8 @@ NAME="newversions"
 HREF="http://www.bugzilla.org"
 TARGET="_top"
 >http://www.bugzilla.org</A
->, or checked out via CVS.
-      (Please follow the <A
+>, or checked out via CVS by
+      following the <A
 HREF="http://www.mozilla.org/cvs.html"
 TARGET="_top"
 >Mozilla 
@@ -102,12 +102,68 @@ TARGET="_top"
 CLASS="filename"
 >mozilla/webtools/bugzilla/docs/</TT
 >
-      subtree.) However, you should read the version
+      subtree. However, you should read the version
       which came with the Bugzilla release you are using.
     </P
 ><P
->&#13;      The Bugzilla Guide is currently only available in English. 
-      If you would like to volunteer to translate it, please contact
+>&#13;      The Bugzilla Guide, or a section of it, is also available in
+      the following languages:
+      <A
+HREF="http://bugzilla-de.sourceforge.net/docs/html/"
+TARGET="_top"
+>German</A
+>.
+    </P
+><P
+>  
+      In addition, there are Bugzilla template localisation projects in
+      the following languages. They may have translated documentation 
+      available: 
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-be/"
+TARGET="_top"
+>Belarusian</A
+>,
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-br/"
+TARGET="_top"
+>Brazilian Portuguese</A
+>,
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-cn/"
+TARGET="_top"
+>Chinese</A
+>,
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-fr/"
+TARGET="_top"
+>French</A
+>,
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-de/"
+TARGET="_top"
+>German</A
+>,
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-kr/"
+TARGET="_top"
+>Korean</A
+>,
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-ru/"
+TARGET="_top"
+>Russian</A
+> and
+      <A
+HREF="http://sourceforge.net/projects/bugzilla-es/"
+TARGET="_top"
+>Spanish</A
+>.
+    </P
+><P
+>  
+      If you would like to volunteer to translate the Guide into additional
+      languages, please contact
       <A
 HREF="mailto:justdave@syndicomm.com"
 TARGET="_top"

docs/html/os-specific.html

 <HTML
 ><HEAD
 ><TITLE
->OS Specific Installation Notes</TITLE
+>OS-Specific Installation Notes</TITLE
 ><META
 NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
 REL="PREVIOUS"
 TITLE="Optional Additional Configuration"
 HREF="extraconfig.html"><LINK
 REL="NEXT"
-TITLE="Bugzilla Security"
-HREF="security.html"></HEAD
+TITLE="Troubleshooting"
+HREF="troubleshooting.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 4. Installation</TD
+>Chapter 2. Installing Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="security.html"
+HREF="troubleshooting.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="os-specific"
 ></A
->4.4. OS Specific Installation Notes</H1
+>2.4. OS-Specific Installation Notes</H1
 ><P
 >Many aspects of the Bugzilla installation can be affected by the
     the operating system you choose to install it on. Sometimes it can be made
@@ -100,9 +100,9 @@ CLASS="section"
 ><A
 NAME="os-win32"
 ></A
->4.4.1. Microsoft Windows</H2
+>2.4.1. Microsoft Windows</H2
 ><P
->Making Bugzilla work on windows is still a painful processes.
+>Making Bugzilla work on Windows is still a painful processes.
       The Bugzilla Team is working to make it easier, but that goal is not
       considered a top priority. If you wish to run Bugzilla, we still
       recommend doing so on a Unix based system such as GNU/Linux. As of this
@@ -114,9 +114,9 @@ NAME="os-win32"
      installing Bugzilla on Win32, here are some pointers.
      
        Because this is a development version of the guide, these instructions
-       are subject to change without notice.  In fact, the Bugzilla Team hopes
-       they do as we would like to have Bugzilla resonabally close to "out of
-       the box" compatibility by the 2.18 release.
+       are subject to change without notice. In fact, the Bugzilla Team hopes
+       to have Bugzilla reasonably close to "out of
+       the box" compatibility with Windows by the 2.18 release.
       
       </P
 ><DIV
@@ -126,7 +126,7 @@ CLASS="section"
 ><A
 NAME="win32-perl"
 ></A
->4.4.1.1. Win32 Perl</H3
+>2.4.1.1. Win32 Perl</H3
 ><P
 >Perl for Windows can be obtained from <A
 HREF="http://www.activestate.com/"
@@ -147,12 +147,12 @@ CLASS="section"
 ><A
 NAME="win32-perlmodules"
 ></A
->4.4.1.2. Perl Modules on Win32</H3
+>2.4.1.2. Perl Modules on Win32</H3
 ><P
 >Bugzilla on Windows requires the same perl modules found in
         <A
-HREF="stepbystep.html#install-perlmodules"
->Section 4.1.6</A
+HREF="installation.html#install-perlmodules"
+>Section 2.1.5</A
 >. The main difference is that
         windows uses <A
 HREF="glossary.html#gloss-ppm"
@@ -219,38 +219,6 @@ TARGET="_top"
 ></TR
 ></TABLE
 ></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->A complete list of modules that can be installed using ppm can
-          be found at <A
-HREF="http://www.activestate.com/PPMPackages/5.6plus"
-TARGET="_top"
->http://www.activestate.com/PPMPackages/5.6plus</A
->.
-          </P
-></TD
-></TR
-></TABLE
-></DIV
 ></DIV
 ><DIV
 CLASS="section"
@@ -259,11 +227,11 @@ CLASS="section"
 ><A
 NAME="win32-code-changes"
 ></A
->4.4.1.3. Code changes required to run on win32</H3
+>2.4.1.3. Code changes required to run on win32</H3
 ><P
 >As Bugzilla still doesn't run "out of the box" on
-        Windows, code has to be modified. This section is an attempt to
-        list the required changes.
+        Windows, code has to be modified. This section lists the required 
+        changes.
         </P
 ><DIV
 CLASS="section"
@@ -272,7 +240,7 @@ CLASS="section"
 ><A
 NAME="win32-code-checksetup"
 ></A
->4.4.1.3.1. Changes to <TT
+>2.4.1.3.1. Changes to <TT
 CLASS="filename"
 >checksetup.pl</TT
 ></H4
@@ -359,12 +327,12 @@ CLASS="section"
 ><A
 NAME="win32-code-bugmail"
 ></A
->4.4.1.3.2. Changes to <TT
+>2.4.1.3.2. Changes to <TT
 CLASS="filename"
 >BugMail.pm</TT
 ></H4
 ><P
->To make bug e-mail work on Win32 (until
+>To make bug email work on Win32 (until
           <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=84876"
 TARGET="_top"
@@ -426,7 +394,7 @@ $smtp-&#62;quit;
 ></TABLE
 ><P
 >Don't forget to change the name of your SMTP server and the
-          domain of the sending e-mail address (after the '@') in the above
+          domain of the sending email address (after the '@') in the above
           lines of code.</P
 ></DIV
 ></DIV
@@ -437,19 +405,19 @@ CLASS="section"
 ><A
 NAME="win32-http"
 ></A
->4.4.1.4. Serving the web pages</H3
+>2.4.1.4. Serving the web pages</H3
 ><P
 >As is the case on Unix based systems, any web server should be
         able to handle Bugzilla; however, the Bugzilla Team still recommends
         Apache whenever asked. No matter what web server you choose, be sure
         to pay attention to the security notes in <A
-HREF="security.html#security-access"
->Section 4.5.4</A
+HREF="configuration.html#security-access"
+>Section 2.2.4.4</A
 >.
         More information on configuring specific web servers can be found in
         <A
-HREF="http.html"
->Section 4.2</A
+HREF="configuration.html#http"
+>Section 2.2.4</A
 >.
         </P
 ><DIV
@@ -478,7 +446,7 @@ HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
 TARGET="_top"
 >ScriptInterpreterSource</A
 >
-          directive in your Apache config, if you don't do this, you'll have
+          directive in your Apache config to avoid having
           to modify the first line of every script to contain your path to
           perl instead of <TT
 CLASS="filename"
@@ -498,17 +466,15 @@ CLASS="section"
 ><A
 NAME="os-macosx"
 ></A
->4.4.2. <SPAN
+>2.4.2. <SPAN
 CLASS="productname"
 >Mac OS X</SPAN
 ></H2
 ><P
->There are a lot of common libraries and utilities out there that
-      Apple did not include with Mac OS X, but which run perfectly well on it.
-      The GD library, which Bugzilla needs to do bug graphs, is one of
-      these.</P
+>Apple did not include the GD library with Mac OS X. Bugzilla
+      needs this for bug graphs.</P
 ><P
->The easiest way to get a lot of these is with a program called
+>You can install it using a program called
       Fink, which is similar in nature to the CPAN installer, but installs
       common GNU utilities. Fink is available from
       <A
@@ -518,7 +484,10 @@ TARGET="_top"
 >.</P
 ><P
 >Follow the instructions for setting up Fink. Once it's installed,
-      you'll want to use it to install the gd2 package.
+      you'll want to use it to install the <TT
+CLASS="filename"
+>gd2</TT
+> package.
       </P
 ><P
 >It will prompt you for a number of dependencies, type 'y' and hit
@@ -530,7 +499,7 @@ CLASS="glossterm"
 >CPAN</I
 ></A
 > to
-      install the GD perl module.
+      install the GD Perl module.
       </P
 ><DIV
 CLASS="note"
@@ -587,7 +556,7 @@ CLASS="filename"
 ></TABLE
 ></DIV
 ><P
->Also available via Fink is expat. Once running using fink to
+>Also available via Fink is expat. After using fink to
       install the expat package you will be able to install
       XML::Parser using CPAN. There is one caveat. Unlike recent versions of
       the GD module, XML::Parser doesn't prompt for the location of the
@@ -692,7 +661,7 @@ CLASS="section"
 ><A
 NAME="os-mandrake"
 ></A
->4.4.3. Linux-Mandrake 8.0</H2
+>2.4.3. Linux-Mandrake 8.0</H2
 ><P
 >Linux-Mandrake 8.0 includes every required and optional library
       for Bugzilla. The easiest way to install them is by using the
@@ -780,7 +749,7 @@ BORDER="0"
 ALT="(1)"></A
 ></DT
 ><DD
->for Bugzilla e-mail integration</DD
+>for Bugzilla email integration</DD
 ></DL
 ></DIV
 ></DIV
@@ -819,7 +788,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="security.html"
+HREF="troubleshooting.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -835,7 +804,7 @@ WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="installation.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="U"
 >Up</A
 ></TD
@@ -843,7 +812,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Bugzilla Security</TD
+>Troubleshooting</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/parameters.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="parameters"
 ></A
->5.1. Bugzilla Configuration</H1
+>3.1. Bugzilla Configuration</H1
 ><P
 >Bugzilla is configured by changing various parameters, accessed
     from the "Edit parameters" link in the page footer. Here are

docs/html/patches.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR

docs/html/patchviewer.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="patchviewer"
 ></A
->3.7. Patch Viewer</H1
+>5.7. Patch Viewer</H1
 ><P
 >Viewing and reviewing patches in Bugzilla is often difficult due to
     lack of context, improper format and the inherent readability issues that
@@ -135,7 +135,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_view"
 ></A
->3.7.1. Viewing Patches in Patch Viewer</H2
+>5.7.1. Viewing Patches in Patch Viewer</H2
 ><P
 >The main way to view a patch in patch viewer is to click on the
       "Diff" link next to a patch in the Attachments list on a bug. You may
@@ -149,7 +149,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_diff"
 ></A
->3.7.2. Seeing the Difference Between Two Patches</H2
+>5.7.2. Seeing the Difference Between Two Patches</H2
 ><P
 >To see the difference between two patches, you must first view the
       newer patch in Patch Viewer.  Then select the older patch from the
@@ -164,7 +164,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_context"
 ></A
->3.7.3. Getting More Context in a Patch</H2
+>5.7.3. Getting More Context in a Patch</H2
 ><P
 >To get more context in a patch, you put a number in the textbox at
       the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
@@ -180,7 +180,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_collapse"
 ></A
->3.7.4. Collapsing and Expanding Sections of a Patch</H2
+>5.7.4. Collapsing and Expanding Sections of a Patch</H2
 ><P
 >To view only a certain set of files in a patch (for example, if a
       patch is absolutely huge and you want to only review part of it at a
@@ -196,7 +196,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_link"
 ></A
->3.7.5. Linking to a Section of a Patch</H2
+>5.7.5. Linking to a Section of a Patch</H2
 ><P
 >To link to a section of a patch (for example, if you want to be
       able to give someone a URL to show them which part you are talking
@@ -211,7 +211,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_bonsai_lxr"
 ></A
->3.7.6. Going to Bonsai and LXR</H2
+>5.7.6. Going to Bonsai and LXR</H2
 ><P
 >To go to Bonsai to get blame for the lines you are interested in,
       you can click the "Lines XX-YY" link on the section header you are
@@ -229,7 +229,7 @@ CLASS="section"
 ><A
 NAME="patchviewer_unified_diff"
 ></A
->3.7.7. Creating a Unified Diff</H2
+>5.7.7. Creating a Unified Diff</H2
 ><P
 >If the patch is not in a format that you like, you can turn it
       into a unified diff format by clicking the "Raw Unified" link at the top

docs/html/products.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="products"
 ></A
->5.3. Products</H1
+>3.3. Products</H1
 ><P
 >&#13;    <A
 HREF="glossary.html#gloss-product"

docs/html/programadmin.html

-<HTML
-><HEAD
-><TITLE
->Product, Component, Milestone, and Version Administration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Administering Bugzilla"
-HREF="administration.html"><LINK
-REL="PREVIOUS"
-TITLE="User Administration"
-HREF="useradmin.html"><LINK
-REL="NEXT"
-TITLE="Voting"
-HREF="voting.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="useradmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="voting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="programadmin"
-></A
->5.3. Product, Component, Milestone, and Version Administration</H1
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="products"
-></A
->5.3.1. Products</H2
-><P
->&#13;      <A
-HREF="glossary.html#gloss-product"
-><I
-CLASS="glossterm"
->&#13;      Products</I
-></A
->
-
-      are the broadest category in Bugzilla, and tend to represent real-world
-      shipping products. E.g. if your company makes computer games, 
-      you should have one product per game, perhaps a "Common" product for 
-      units of technology used in multiple games, and maybe a few special
-       products (Website, Administration...)</P
-><P
->Many of Bugzilla's settings are configurable on a per-product
-      basis. The number of "votes" available to users is set per-product, 
-      as is the number of votes
-      required to move a bug automatically from the UNCONFIRMED status to the
-      NEW status.</P
-><P
->To create a new product:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select "products" from the footer</P
-></LI
-><LI
-><P
->Select the "Add" link in the bottom right</P
-></LI
-><LI
-><P
->Enter the name of the product and a description. The
-          Description field may contain HTML.</P
-></LI
-></OL
-><P
->Don't worry about the "Closed for bug entry", "Maximum Votes
-      per person", "Maximum votes a person can put on a single bug",
-      "Number of votes a bug in this Product needs to automatically get out
-      of the UNCOMFIRMED state", and "Version" options yet. We'll cover
-      those in a few moments.
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="components"
-></A
->5.3.2. Components</H2
-><P
->Components are subsections of a Product. E.g. the computer game 
-      you are designing may have a "UI"
-      component, an "API" component, a "Sound System" component, and a
-      "Plugins" component, each overseen by a different programmer. It
-      often makes sense to divide Components in Bugzilla according to the
-      natural divisions of responsibility within your Product or
-      company.</P
-><P
->&#13;      Each component has a owner and (if you turned it on in the parameters),
-      a QA Contact. The owner should be the primary person who fixes bugs in
-      that component. The QA Contact should be the person who will ensure
-      these bugs are completely fixed. The Owner, QA Contact, and Reporter
-      will get email when new bugs are created in this Component and when
-      these bugs change. Default Owner and Default QA Contact fields only
-      dictate the 
-      <EM
->default assignments</EM
->; 
-      these can be changed on bug submission, or at any later point in
-      a bug's life.</P
-><P
->To create a new Component:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select the "Edit components" link from the "Edit product"
-          page</P
-></LI
-><LI
-><P
->Select the "Add" link in the bottom right.</P
-></LI
-><LI
-><P
->Fill out the "Component" field, a short "Description", 
-          the "Initial Owner" and "Initial QA Contact" (if enabled.) 
-          The Component and Description fields may contain HTML; 
-          the "Initial Owner" field must be a login name
-          already existing in the database. 
-          </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="versions"
-></A
->5.3.3. Versions</H2
-><P
->Versions are the revisions of the product, such as "Flinders
-      3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
-      field; the usual practice is to select the most recent version with
-      the bug.
-      </P
-><P
->To create and edit Versions:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->From the "Edit product" screen, select "Edit Versions"</P
-></LI
-><LI
-><P
->You will notice that the product already has the default
-          version "undefined". Click the "Add" link in the bottom right.</P
-></LI
-><LI
-><P
->Enter the name of the Version. This field takes text only. 
-          Then click the "Add" button.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="milestones"
-></A
->5.3.4. Milestones</H2
-><P
->Milestones are "targets" that you plan to get a bug fixed by. For
-      example, you have a bug that you plan to fix for your 3.0 release, it
-      would be assigned the milestone of 3.0.</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Milestone options will only appear for a Product if you turned
-        on the "usetargetmilestone" Param in the "Edit Parameters" screen.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->To create new Milestones, set Default Milestones, and set
-      Milestone URL:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Select "Edit milestones" from the "Edit product" page.</P
-></LI
-><LI
-><P
->Select "Add" in the bottom right corner.
-          text</P
-></LI
-><LI
-><P
->Enter the name of the Milestone in the "Milestone" field. You
-          can optionally set the "sortkey", which is a positive or negative
-          number (-255 to 255) that defines where in the list this particular
-          milestone appears. This is because milestones often do not 
-          occur in alphanumeric order For example, "Future" might be
-          after "Release 1.2". Select "Add".</P
-></LI
-><LI
-><P
->From the Edit product screen, you can enter the URL of a 
-          page which gives information about your milestones and what
-          they mean. </P
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you want your milestone document to be restricted so
-          that it can only be viewed by people in a particular Bugzilla
-          group, the best way is to attach the document to a bug in that
-          group, and make the URL the URL of that attachment.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="useradmin.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="voting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->User Administration</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="administration.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Voting</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/query.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="query"
 ></A
->3.4. Searching for Bugs</H1
+>5.4. Searching for Bugs</H1
 ><P
 >The Bugzilla Search page is is the interface where you can find
     any bug report, comment, or patch currently in the Bugzilla system. You

docs/html/reporting.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -17,8 +17,8 @@ REL="PREVIOUS"
 TITLE="User Preferences"
 HREF="userpreferences.html"><LINK
 REL="NEXT"
-TITLE="Installation"
-HREF="installation.html"></HEAD
+TITLE="The Bugzilla FAQ"
+HREF="faq.html"></HEAD
 ><BODY
 CLASS="section"
 BGCOLOR="#FFFFFF"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,13 +55,13 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="installation.html"
+HREF="faq.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="reporting"
 ></A
->3.10. Reports</H1
+>5.10. Reports</H1
 ><P
 ><EM
 >To be written</EM
@@ -117,7 +117,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="installation.html"
+HREF="faq.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -141,7 +141,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Installation</TD
+>The Bugzilla FAQ</TD
 ></TR
 ></TABLE
 ></DIV

docs/html/rewrite.html

-<HTML
-><HEAD
-><TITLE
->Apache 
-    mod_rewrite
-
-    magic</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"><LINK
-REL="PREVIOUS"
-TITLE="Useful Patches and Utilities for Bugzilla"
-HREF="patches.html"><LINK
-REL="NEXT"
-TITLE="Command-line Bugzilla Queries"
-HREF="cmdline.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="patches.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix B. Useful Patches and Utilities for Bugzilla</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="cmdline.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="rewrite"
-></A
->B.1. Apache 
-    <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
-    magic</H1
-><P
->Apache's 
-    <TT
-CLASS="filename"
->mod_rewrite</TT
->
-
-    module lets you do some truly amazing things with URL rewriting. Here are
-    a couple of examples of what you can do.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Make it so if someone types 
-        <TT
-CLASS="computeroutput"
->http://www.foo.com/12345</TT
->
-
-        , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
-        setting up your VirtualHost section for Bugzilla with a rule like
-        this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;&#60;VirtualHost 12.34.56.78&#62;
-RewriteEngine On
-RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
-&#60;/VirtualHost&#62;
-</PRE
-></FONT
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
->There are many, many more things you can do with mod_rewrite.
-        Please refer to the mod_rewrite documentation at 
-        <A
-HREF="http://www.apache.org"
-TARGET="_top"
->http://www.apache.org</A
->.
-        </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="cmdline.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Useful Patches and Utilities for Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="patches.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Command-line Bugzilla Queries</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/security.html

-<HTML
-><HEAD
-><TITLE
->Bugzilla Security</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="OS Specific Installation Notes"
-HREF="os-specific.html"><LINK
-REL="NEXT"
-TITLE="Troubleshooting"
-HREF="troubleshooting.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="os-specific.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="security"
-></A
->4.5. Bugzilla Security</H1
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Poorly-configured MySQL and Bugzilla installations have
-      given attackers full access to systems in the past. Please take these
-      guidelines seriously, even for Bugzilla machines hidden away behind
-      your firewall. 80% of all computer trespassers are insiders, not
-      anonymous crackers.</P
-><P
->This is not meant to be a comprehensive list of every possible
-      security issue pertaining to the software mentioned in this section. 
-      There is
-      no subsitute for reading the information written by the authors of any
-      software running on your system.
-      </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-networking"
-></A
->4.5.1. TCP/IP Ports</H2
-><P
->TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
-      only needs 1, or 2 if you need to use features that require e-mail such
-      as bug moving or the e-mail interface from contrib. You should audit
-      your server and make sure that you aren't listening on any ports you
-      don't need to be. You may also wish to use some kind of firewall
-      software to be sure that trafic can only be recieved on ports you
-      specify.
-      </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-mysql"
-></A
->4.5.2. MySQL</H2
-><P
->MySQL ships by default with many settings that should be changed.
-      By defaults it allows anybody to connect from localhost without a
-      password and have full administrative capabilities. It also defaults to
-      not have a root password (this is <EM
->not</EM
-> the same as
-      the system root). Also, many installations default to running
-      <SPAN
-CLASS="application"
->mysqld</SPAN
-> as the system root.
-      </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Consult the documentation that came with your system for
-          information on making <SPAN
-CLASS="application"
->mysqld</SPAN
-> run as an
-          unprivleged user.
-          </P
-></LI
-><LI
-><P
->You should also be sure to disable the anonymous user account
-          and set a password for the root user. This is accomplished using the
-          following commands:
-          </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;<TT
-CLASS="prompt"
->bash$</TT
-> mysql mysql
-<TT
-CLASS="prompt"
->mysql&#62;</TT
-> DELETE FROM user WHERE user = '';
-<TT
-CLASS="prompt"
->mysql&#62;</TT
-> UPDATE user SET password = password('<TT
-CLASS="replaceable"
-><I
->new_password</I
-></TT
->') WHERE user = 'root';
-<TT
-CLASS="prompt"
->mysql&#62;</TT
-> FLUSH PRIVILEGES;
-          </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->From this point forward you will need to use
-          <B
-CLASS="command"
->mysql -u root -p</B
-> and enter
-          <TT
-CLASS="replaceable"
-><I
->new_password</I
-></TT
-> when prompted when using the
-          mysql client.
-          </P
-></LI
-><LI
-><P
->If you run MySQL on the same machine as your httpd server, you
-          should consider disabling networking from within MySQL by adding
-          the following to your <TT
-CLASS="filename"
->/etc/my.conf</TT
->:
-          </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;[myslqd]
-# Prevent network access to MySQL.
-skip-networking
-          </PRE
-></FONT
-></TD
-></TR
-></TABLE
-></LI
-><LI
-><P
->You may also consider running MySQL, or even all of Bugzilla
-          in a chroot jail; however, instructions for doing that are beyond
-          the scope of this document.
-          </P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-daemon"
-></A
->4.5.3. Daemon Accounts</H2
-><P
->Many daemons, such as Apache's httpd and MySQL's mysqld default to
-      running as either <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> or <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
->. Running
-      as <SPAN
-CLASS="QUOTE"
->"root"</SPAN
-> introduces obvious security problems, but the
-      problems introduced by running everything as <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
-> may
-      not be so obvious. Basically, if you're running every daemon as
-      <SPAN
-CLASS="QUOTE"
->"nobody"</SPAN
-> and one of them gets compromised, they all get
-      compromised. For this reason it is recommended that you create a user
-      account for each daemon.
-      </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will need to set the <TT
-CLASS="varname"
->webservergroup</TT
-> to
-        the group you created for your webserver to run as in
-        <TT
-CLASS="filename"
->localconfig</TT
->. This will allow
-        <B
-CLASS="command"
->./checksetup.pl</B
-> to better adjust the file
-        permissions on your Bugzilla install so as to not require making
-        anything world-writable.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="security-access"
-></A
->4.5.4. Web Server Access Controls</H2
-><P
->There are many files that are placed in the Bugzilla directory
-      area that should not be accessable from the web. Because of the way
-      Bugzilla is currently laid out, the list of what should and should
-      not be accessible is rather complicated.
-      </P
-><P
->Users of Apache don't need to worry about this, however, because
-      Bugzilla ships with .htaccess files which restrict access to all the
-      sensitive files in this section. Users of other webservers, read on.
-      </P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->In the main Bugzilla directory, you should:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block:
-              <TT
-CLASS="filename"
->*.pl</TT
->, <TT
-CLASS="filename"
->*localconfig*</TT
->, <TT
-CLASS="filename"
->runtests.sh</TT
->
-              </P
-></LI
-><LI
-><P
->But allow:
-              <TT
-CLASS="filename"
->localconfig.js</TT
->, <TT
-CLASS="filename"
->localconfig.rdf</TT
->
-              </P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->data</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow:
-              <TT
-CLASS="filename"
->duplicates.rdf</TT
->
-              </P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->data/webdot</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->If you use a remote webdot server:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow
-                  <TT
-CLASS="filename"
->*.dot</TT
->
-                  only for the remote webdot server</P
-></LI
-></UL
-></LI
-><LI
-><P
->Otherwise, if you use a local GraphViz:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-><LI
-><P
->But allow:
-                  <TT
-CLASS="filename"
->*.png</TT
->, <TT
-CLASS="filename"
->*.gif</TT
->, <TT
-CLASS="filename"
->*.jpg</TT
->, <TT
-CLASS="filename"
->*.map</TT
->
-                  </P
-></LI
-></UL
-></LI
-><LI
-><P
->And if you don't use any dot:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->Bugzilla</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-><LI
-><P
->In <TT
-CLASS="filename"
->template</TT
->:</P
-><P
-></P
-><UL
-COMPACT="COMPACT"
-><LI
-><P
->Block everything</P
-></LI
-></UL
-></LI
-></UL
-><P
->You should test to make sure that the files mentioned above are
-      not accessible from the Internet, especially your
-      <TT
-CLASS="filename"
->localconfig</TT
-> file which contains your database
-      password. To test, simply point your web browser at the file; for
-      example, to test mozilla.org's installation, we'd try to access
-      <A
-HREF="http://bugzilla.mozilla.org/localconfig"
-TARGET="_top"
->http://bugzilla.mozilla.org/localconfig</A
->. You should
-      get a <SPAN
-CLASS="errorcode"
->403</SPAN
-> <SPAN
-CLASS="errorname"
->Forbidden</SPAN
->
-      error.
-      </P
-><DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Not following the instructions in this section, including
-        testing, may result in sensitive information being globally
-        accessible.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="tip"
-><P
-></P
-><TABLE
-CLASS="tip"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/tip.gif"
-HSPACE="5"
-ALT="Tip"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You should check <A
-HREF="http.html"
->Section 4.2</A
-> to see if instructions
-        have been included for your web server. You should also compare those
-        instructions with this list to make sure everything is properly
-        accounted for.
-        </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="os-specific.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="troubleshooting.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->OS Specific Installation Notes</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Troubleshooting</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/troubleshooting.html

@@ -7,15 +7,15 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
+TITLE="Installing Bugzilla"
+HREF="installing-bugzilla.html"><LINK
 REL="PREVIOUS"
-TITLE="Bugzilla Security"
-HREF="security.html"><LINK
+TITLE="OS-Specific Installation Notes"
+HREF="os-specific.html"><LINK
 REL="NEXT"
 TITLE="Administering Bugzilla"
 HREF="administration.html"></HEAD
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -47,7 +47,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="security.html"
+HREF="os-specific.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 4. Installation</TD
+>Chapter 2. Installing Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,19 +77,88 @@ CLASS="section"
 ><A
 NAME="troubleshooting"
 ></A
->4.6. Troubleshooting</H1
+>2.5. Troubleshooting</H1
 ><P
 >This section gives solutions to common Bugzilla installation
-    problems.
+    problems. If none of the section headings seems to match your
+    problem, read the general advice.
     </P
 ><DIV
 CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1206"
+NAME="general-advice"
 ></A
->4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
+>2.5.1. General Advice</H2
+><P
+>&#13;        If you can't get <TT
+CLASS="filename"
+>checksetup.pl</TT
+> to run to 
+        completion, it normally explains what's wrong and how to fix it.
+        If you can't work it out, or if it's being uncommunicative, post 
+        the errors in the 
+        <A
+HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
+TARGET="_top"
+>netscape.public.mozilla.webtools</A
+>
+        newsgroup.
+      </P
+><P
+>&#13;        If you have made it all the way through 
+        <A
+HREF="installation.html"
+>Section 2.1</A
+> (Installation) and
+        <A
+HREF="configuration.html"
+>Section 2.2</A
+> (Configuration) but 
+        accessing the Bugzilla URL doesn't work,
+        the first thing to do is to check your webserver error log. For
+        Apache, this is often located at
+        <TT
+CLASS="filename"
+>/etc/logs/httpd/error_log</TT
+>. The error messages
+        you see may be self-explanatory enough to enable you to diagnose and
+        fix the problem. If not, see below for some commonly-encountered 
+        errors. If that doesn't help, post the errors to the newsgroup.
+      </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="AEN827"
+></A
+>2.5.2. I installed a Perl module, but 
+      <TT
+CLASS="filename"
+>checksetup.pl</TT
+> claims it's not installed!</H2
+><P
+>&#13;        You have two versions of Perl on your machine. You are installing
+        modules into one, and Bugzilla is using the other. Rerun the CPAN
+        commands (or manual compile) using the full path to Perl from the 
+        top of <TT
+CLASS="filename"
+>checksetup.pl</TT
+>. This will make sure you 
+        are installing the modules in the right place.
+      </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="AEN832"
+></A
+>2.5.3. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
 ><P
 >&#13;      Try executing <B
 CLASS="command"
@@ -112,9 +181,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1211"
+NAME="AEN837"
 ></A
->4.6.2. DBD::Sponge::db prepare failed</H2
+>2.5.4. DBD::Sponge::db prepare failed</H2
 ><P
 >&#13;        The following error message may appear due to a bug in DBD::mysql
         (over which the Bugzilla team have no control):
@@ -200,7 +269,7 @@ CLASS="section"
 ><A
 NAME="paranoid-security"
 ></A
->4.6.3. cannot chdir(/var/spool/mqueue)</H2
+>2.5.5. cannot chdir(/var/spool/mqueue)</H2
 ><P
 >If you are installing Bugzilla on SuSE Linux, or some other
       distributions with 
@@ -258,28 +327,15 @@ CLASS="section"
 ><A
 NAME="trouble-filetemp"
 ></A
->4.6.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
+>2.5.6. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
 ><P
 >This is caused by a bug in the version of
       <SPAN
 CLASS="productname"
 >File::Temp</SPAN
 > that is distributed with perl
-      5.6.0. Many minor variations of this error have been reported. Examples
-      can be found in <A
-HREF="troubleshooting.html#trouble-filetemp-errors"
->Figure 4-2</A
->.
+      5.6.0. Many minor variations of this error have been reported:
       </P
-><DIV
-CLASS="figure"
-><A
-NAME="trouble-filetemp-errors"
-></A
-><P
-><B
->Figure 4-2. Other File::Temp error messages</B
-></P
 ><TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
@@ -290,42 +346,28 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
->&#13;Your vendor has not defined Fcntl macro O_NOINHERIT, used 
+>Your vendor has not defined Fcntl macro O_NOINHERIT, used 
 at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208.
 
 Your vendor has not defined Fcntl macro O_EXLOCK, used 
 at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210.
 
 Your vendor has not defined Fcntl macro O_TEMPORARY, used 
-at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
-        </PRE
+at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.</PRE
 ></FONT
 ></TD
 ></TR
 ></TABLE
-></DIV
 ><P
 >Numerous people have reported that upgrading to version 5.6.1
       or higher solved the problem for them. A less involved fix is to apply
-      the patch in <A
-HREF="troubleshooting.html#trouble-filetemp-patch"
->Figure 4-3</A
->. The patch is also
+      the following patch, which is also
       available as a <A
 HREF="../xml/filetemp.patch"
 TARGET="_top"
 >patch file</A
 >.
       </P
-><DIV
-CLASS="figure"
-><A
-NAME="trouble-filetemp-patch"
-></A
-><P
-><B
->Figure 4-3. Patch for File::Temp in Perl 5.6.0</B
-></P
 ><TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
@@ -336,7 +378,7 @@ WIDTH="100%"
 COLOR="#000000"
 ><PRE
 CLASS="programlisting"
->&#13;--- File/Temp.pm.orig   Thu Feb  6 16:26:00 2003
+>--- File/Temp.pm.orig   Thu Feb  6 16:26:00 2003
 +++ File/Temp.pm        Thu Feb  6 16:26:23 2003
 @@ -205,6 +205,7 @@
      # eg CGI::Carp
@@ -353,15 +395,13 @@ CLASS="programlisting"
 +    local *CORE::GLOBAL::die = sub {};
      $bit = &#38;$func();
      1;
-   };
-        </PRE
+   };</PRE
 ></FONT
 ></TD
 ></TR
 ></TABLE
 ></DIV
 ></DIV
-></DIV
 ><DIV
 CLASS="NAVFOOTER"
 ><HR
@@ -378,7 +418,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="security.html"
+HREF="os-specific.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -406,13 +446,13 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Bugzilla Security</TD
+>OS-Specific Installation Notes</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="installation.html"
+HREF="installing-bugzilla.html"
 ACCESSKEY="U"
 >Up</A
 ></TD

docs/html/upgrading.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="upgrading"
 ></A
->5.9. Upgrading to New Releases</H1
+>3.9. Upgrading to New Releases</H1
 ><DIV
 CLASS="warning"
 ><P
@@ -136,21 +136,21 @@ TYPE="1"
 ><P
 >Using CVS (<A
 HREF="upgrading.html#upgrade-cvs"
->Example 5-1</A
+>Example 3-1</A
 >)</P
 ></LI
 ><LI
 ><P
 >Downloading a new tarball (<A
 HREF="upgrading.html#upgrade-tarball"
->Example 5-2</A
+>Example 3-2</A
 >)</P
 ></LI
 ><LI
 ><P
 >Applying the relevant patches (<A
 HREF="upgrading.html#upgrade-patches"
->Example 5-3</A
+>Example 3-3</A
 >)</P
 ></LI
 ></OL
@@ -195,7 +195,7 @@ NAME="upgrade-cvs"
 ></A
 ><P
 ><B
->Example 5-1. Upgrading using CVS</B
+>Example 3-1. Upgrading using CVS</B
 ></P
 ><P
 >Every release of Bugzilla, whether it is a revision or a point
@@ -352,7 +352,7 @@ NAME="upgrade-tarball"
 ></A
 ><P
 ><B
->Example 5-2. Upgrading using the tarball</B
+>Example 3-2. Upgrading using the tarball</B
 ></P
 ><P
 >If you are unable or unwilling to use CVS, another option that's
@@ -508,7 +508,7 @@ NAME="upgrade-patches"
 ></A
 ><P
 ><B
->Example 5-3. Upgrading using patches</B
+>Example 3-3. Upgrading using patches</B
 ></P
 ><P
 >The Bugzilla team will normally make a patch file available for
@@ -588,7 +588,7 @@ CLASS="filename"
 > directory so it may make
           updates using CVS (<A
 HREF="upgrading.html#upgrade-cvs"
->Example 5-1</A
+>Example 3-1</A
 >) more difficult in the
           future.
           </P

docs/html/useradmin.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="useradmin"
 ></A
->5.2. User Administration</H1
+>3.2. User Administration</H1
 ><DIV
 CLASS="section"
 ><H2
@@ -85,7 +85,7 @@ CLASS="section"
 ><A
 NAME="defaultuser"
 ></A
->5.2.1. Creating the Default User</H2
+>3.2.1. Creating the Default User</H2
 ><P
 >When you first run checksetup.pl after installing Bugzilla, it
       will prompt you for the administrative username (email address) and
@@ -130,7 +130,7 @@ CLASS="section"
 ><A
 NAME="manageusers"
 ></A
->5.2.2. Managing Other Users</H2
+>3.2.2. Managing Other Users</H2
 ><DIV
 CLASS="section"
 ><H3
@@ -138,7 +138,7 @@ CLASS="section"
 ><A
 NAME="createnewusers"
 ></A
->5.2.2.1. Creating new users</H3
+>3.2.2.1. Creating new users</H3
 ><P
 >Your users can create their own user accounts by clicking the
         "New Account" link at the bottom of each page (assuming they
@@ -211,7 +211,7 @@ CLASS="section"
 ><A
 NAME="modifyusers"
 ></A
->5.2.2.2. Modifying Users</H3
+>3.2.2.2. Modifying Users</H3
 ><P
 >To see a specific user, search for their login name
         in the box provided on the "Edit Users" page. To see all users, 

docs/html/userpreferences.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="userpreferences"
 ></A
->3.9. User Preferences</H1
+>5.9. User Preferences</H1
 ><P
 >Once you have logged in, you can customise various aspects of 
     Bugzilla via the "Edit prefs" link in the page footer.
@@ -89,7 +89,7 @@ CLASS="section"
 ><A
 NAME="accountsettings"
 ></A
->3.9.1. Account Settings</H2
+>5.9.1. Account Settings</H2
 ><P
 >On this tab, you can change your basic account information,
       including your password, email address and real name. For security
@@ -114,7 +114,7 @@ CLASS="section"
 ><A
 NAME="emailsettings"
 ></A
->3.9.2. Email Settings</H2
+>5.9.2. Email Settings</H2
 ><P
 >On this tab you can reduce or increase the amount of email sent
       you from Bugzilla, opting in our out depending on your relationship to
@@ -169,7 +169,7 @@ CLASS="section"
 ><A
 NAME="permissionsettings"
 ></A
->3.9.3. Permissions</H2
+>5.9.3. Permissions</H2
 ><P
 >This is a purely informative page which outlines your current
       permissions on this installation of Bugzilla - what product groups you

docs/html/using-intro.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 3. Using Bugzilla</TD
+>Chapter 5. Using Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="using-intro"
 ></A
->3.1. Introduction</H1
+>5.1. Introduction</H1
 ><P
 >This section contains information for end-users of Bugzilla. 
     There is a Bugzilla test installation, called 

docs/html/using.html

@@ -7,12 +7,12 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="PREVIOUS"
-TITLE="Why use Bugzilla?"
-HREF="why-bugzilla.html"><LINK
+TITLE="Integrating Bugzilla with Third-Party Tools"
+HREF="integration.html"><LINK
 REL="NEXT"
 TITLE="Introduction"
 HREF="using-intro.html"></HEAD
@@ -35,7 +35,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -44,7 +44,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="why-bugzilla.html"
+HREF="integration.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -73,7 +73,7 @@ CLASS="chapter"
 ><A
 NAME="using"
 ></A
->Chapter 3. Using Bugzilla</H1
+>Chapter 5. Using Bugzilla</H1
 ><DIV
 CLASS="TOC"
 ><DL
@@ -82,134 +82,134 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->3.1. <A
+>5.1. <A
 HREF="using-intro.html"
 >Introduction</A
 ></DT
 ><DT
->3.2. <A
+>5.2. <A
 HREF="myaccount.html"
 >Create a Bugzilla Account</A
 ></DT
 ><DT
->3.3. <A
+>5.3. <A
 HREF="bug_page.html"
 >Anatomy of a Bug</A
 ></DT
 ><DT
->3.4. <A
+>5.4. <A
 HREF="query.html"
 >Searching for Bugs</A
 ></DT
 ><DT
->3.5. <A
+>5.5. <A
 HREF="list.html"
 >Bug Lists</A
 ></DT
 ><DT
->3.6. <A
+>5.6. <A
 HREF="bugreports.html"
 >Filing Bugs</A
 ></DT
 ><DT
->3.7. <A
+>5.7. <A
 HREF="patchviewer.html"
 >Patch Viewer</A
 ></DT
 ><DD
 ><DL
 ><DT
->3.7.1. <A
+>5.7.1. <A
 HREF="patchviewer.html#patchviewer_view"
 >Viewing Patches in Patch Viewer</A
 ></DT
 ><DT
->3.7.2. <A
+>5.7.2. <A
 HREF="patchviewer.html#patchviewer_diff"
 >Seeing the Difference Between Two Patches</A
 ></DT
 ><DT
->3.7.3. <A
+>5.7.3. <A
 HREF="patchviewer.html#patchviewer_context"
 >Getting More Context in a Patch</A
 ></DT
 ><DT
->3.7.4. <A
+>5.7.4. <A
 HREF="patchviewer.html#patchviewer_collapse"
 >Collapsing and Expanding Sections of a Patch</A
 ></DT
 ><DT
->3.7.5. <A
+>5.7.5. <A
 HREF="patchviewer.html#patchviewer_link"
 >Linking to a Section of a Patch</A
 ></DT
 ><DT
->3.7.6. <A
+>5.7.6. <A
 HREF="patchviewer.html#patchviewer_bonsai_lxr"
 >Going to Bonsai and LXR</A
 ></DT
 ><DT
->3.7.7. <A
+>5.7.7. <A
 HREF="patchviewer.html#patchviewer_unified_diff"
 >Creating a Unified Diff</A
 ></DT
 ></DL
 ></DD
 ><DT
->3.8. <A
+>5.8. <A
 HREF="hintsandtips.html"
 >Hints and Tips</A
 ></DT
 ><DD
 ><DL
 ><DT
->3.8.1. <A
-HREF="hintsandtips.html#AEN363"
+>5.8.1. <A
+HREF="hintsandtips.html#AEN1641"
 >Autolinkification</A
 ></DT
 ><DT
->3.8.2. <A
+>5.8.2. <A
 HREF="hintsandtips.html#quicksearch"
 >Quicksearch</A
 ></DT
 ><DT
->3.8.3. <A
+>5.8.3. <A
 HREF="hintsandtips.html#commenting"
 >Comments</A
 ></DT
 ><DT
->3.8.4. <A
+>5.8.4. <A
 HREF="hintsandtips.html#attachments"
 >Attachments</A
 ></DT
 ></DL
 ></DD
 ><DT
->3.9. <A
+>5.9. <A
 HREF="userpreferences.html"
 >User Preferences</A
 ></DT
 ><DD
 ><DL
 ><DT
->3.9.1. <A
+>5.9.1. <A
 HREF="userpreferences.html#accountsettings"
 >Account Settings</A
 ></DT
 ><DT
->3.9.2. <A
+>5.9.2. <A
 HREF="userpreferences.html#emailsettings"
 >Email Settings</A
 ></DT
 ><DT
->3.9.3. <A
+>5.9.3. <A
 HREF="userpreferences.html#permissionsettings"
 >Permissions</A
 ></DT
 ></DL
 ></DD
 ><DT
->3.10. <A
+>5.10. <A
 HREF="reporting.html"
 >Reports</A
 ></DT
@@ -232,7 +232,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="why-bugzilla.html"
+HREF="integration.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -260,7 +260,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Why use Bugzilla?</TD
+>Integrating Bugzilla with Third-Party Tools</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"

docs/html/variant-fenris.html

-<HTML
-><HEAD
-><TITLE
->Loki Bugzilla (Fenris)</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Red Hat Bugzilla"
-HREF="variant-redhat.html"><LINK
-REL="NEXT"
-TITLE="Issuezilla"
-HREF="variant-issuezilla.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-fenris"
-></A
->D.2. Loki Bugzilla (Fenris)</H1
-><P
->Fenris was a fork from Bugzilla made by Loki Games; when
-    Loki went into receivership, it died. While Loki's other code lives on,
-    its custodians recommend Bugzilla for future bug-tracker deployments.
-    </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-issuezilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Red Hat Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Issuezilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/variant-issuezilla.html

-<HTML
-><HEAD
-><TITLE
->Issuezilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Loki Bugzilla (Fenris)"
-HREF="variant-fenris.html"><LINK
-REL="NEXT"
-TITLE="Scarab"
-HREF="variant-scarab.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix D. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-issuezilla"
-></A
->D.3. Issuezilla</H1
-><P
->Issuezilla was another fork from Bugzilla, made by collab.net and
-    hosted at tigris.org. It is also dead; the primary focus of bug-tracking 
-    at tigris.org is their Java-based bug-tracker, 
-    <A
-HREF="variant-scarab.html"
->Section D.4</A
->.</P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-fenris.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Loki Bugzilla (Fenris)</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Scarab</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/variant-redhat.html

-<HTML
-><HEAD
-><TITLE
->Red Hat Bugzilla</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="NEXT"
-TITLE="Scarab"
-HREF="variant-scarab.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variants.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix C. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-redhat"
-></A
->C.1. Red Hat Bugzilla</H1
-><P
->Red Hat's has its own version of Bugzilla based on version 2.17.1. 
-    The main changes are that the 
-    back-end is modified to work with PostgreSQL instead of MySQL and they have
-    custom templates to get their desired look and feel. 
-    Dave Lawrence of Red Hat has filed 
-    <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
-TARGET="_top"
->bug 98304</A
->
-    exists to track the integration of his PostgreSQL support.
-    </P
-><P
->URL: <A
-HREF="http://bugzilla.redhat.com/bugzilla/"
-TARGET="_top"
->http://bugzilla.redhat.com/bugzilla/</A
->
-    </P
-><P
->This section last updated 24 Dec 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Scarab</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/variant-scarab.html

-<HTML
-><HEAD
-><TITLE
->Scarab</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Red Hat Bugzilla"
-HREF="variant-redhat.html"><LINK
-REL="NEXT"
-TITLE="SourceForge"
-HREF="variant-sourceforge.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix C. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-scarab"
-></A
->C.2. Scarab</H1
-><P
->Scarab is a new open source bug-tracking system built using Java
-    Servlet technology. It is currently at version 1.0 beta 13.</P
-><P
->URL: <A
-HREF="http://scarab.tigris.org/"
-TARGET="_top"
->http://scarab.tigris.org/</A
->
-    </P
-><P
->This section last updated 18 Jan 2003</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-sourceforge.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Red Hat Bugzilla</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->SourceForge</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/variant-sourceforge.html

-<HTML
-><HEAD
-><TITLE
->SourceForge</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Bugzilla Variants and Competitors"
-HREF="variants.html"><LINK
-REL="PREVIOUS"
-TITLE="Scarab"
-HREF="variant-scarab.html"><LINK
-REL="NEXT"
-TITLE="GNU Free Documentation License"
-HREF="gfdl.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Appendix C. Bugzilla Variants and Competitors</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="gfdl.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="variant-sourceforge"
-></A
->C.3. SourceForge</H1
-><P
->SourceForge is a way of coordinating geographically
-    distributed free software and open source projects over the Internet.
-    It has a built-in bug tracker, but it's not highly thought of.</P
-><P
->URL: <A
-HREF="http://www.sourceforge.net"
-TARGET="_top"
->http://www.sourceforge.net</A
->
-    </P
-><P
->This section last updated 27 Jul 2002</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="variant-scarab.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="gfdl.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Scarab</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="variants.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->GNU Free Documentation License</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/variants.html

-<HTML
-><HEAD
-><TITLE
->Bugzilla Variants and Competitors</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Command-line Bugzilla Queries"
-HREF="cmdline.html"><LINK
-REL="NEXT"
-TITLE="Red Hat Bugzilla"
-HREF="variant-redhat.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="cmdline.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="variants"
-></A
->Appendix C. Bugzilla Variants and Competitors</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->C.1. <A
-HREF="variant-redhat.html"
->Red Hat Bugzilla</A
-></DT
-><DT
->C.2. <A
-HREF="variant-scarab.html"
->Scarab</A
-></DT
-><DT
->C.3. <A
-HREF="variant-sourceforge.html"
->SourceForge</A
-></DT
-></DL
-></DIV
-><P
->I created this section to answer questions about Bugzilla competitors
-  and variants, then found a wonderful site which covers an awful lot of what
-  I wanted to discuss. Rather than quote it in its entirety, I'll simply
-  refer you here: 
-  <A
-HREF="http://linas.org/linux/pm.html"
-TARGET="_top"
->http://linas.org/linux/pm.html</A
->.
-  </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="cmdline.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="variant-redhat.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Command-line Bugzilla Queries</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
->&nbsp;</TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Red Hat Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/versions.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="versions"
 ></A
->5.5. Versions</H1
+>3.5. Versions</H1
 ><P
 >Versions are the revisions of the product, such as "Flinders
     3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select

docs/html/voting.html

@@ -7,7 +7,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
 "><LINK
 REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
+TITLE="The Bugzilla Guide - 2.17.7 
     Development Release"
 HREF="index.html"><LINK
 REL="UP"
@@ -38,7 +38,7 @@ CELLSPACING="0"
 ><TH
 COLSPAN="3"
 ALIGN="center"
->The Bugzilla Guide - 2.17.5 
+>The Bugzilla Guide - 2.17.7 
     Development Release</TH
 ></TR
 ><TR
@@ -55,7 +55,7 @@ ACCESSKEY="P"
 WIDTH="80%"
 ALIGN="center"
 VALIGN="bottom"
->Chapter 5. Administering Bugzilla</TD
+>Chapter 3. Administering Bugzilla</TD
 ><TD
 WIDTH="10%"
 ALIGN="right"
@@ -77,7 +77,7 @@ CLASS="section"
 ><A
 NAME="voting"
 ></A
->5.7. Voting</H1
+>3.7. Voting</H1
 ><P
 >Voting allows users to be given a pot of votes which they can allocate
     to bugs, to indicate that they'd like them fixed. 

docs/html/what-is-bugzilla.html

-<HTML
-><HEAD
-><TITLE
->What is Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="NEXT"
-TITLE="Why use a bug-tracking system?"
-HREF="why-tracking.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="why-tracking.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="what-is-bugzilla"
-></A
->2.1. What is Bugzilla?</H1
-><P
->&#13;    Bugzilla is a bug- or issue-tracking system. Bug-tracking
-    systems allow individual or groups of developers effectively to keep track
-    of outstanding problems with their products. 
-    </P
-><P
-><EM
->Do we need more here?</EM
-></P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="why-tracking.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Introduction</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Why use a bug-tracking system?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/whatis.html

-<HTML
-><HEAD
-><TITLE
->What is Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="NEXT"
-TITLE="Why use a bug-tracking system?"
-HREF="why.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="why.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="whatis"
-></A
->2.1. What is Bugzilla?</H1
-><P
->&#13;    Bugzilla is a bug- or issue-tracking system. Bug-tracking
-    systems allow individual or groups of developers effectively to keep track
-    of outstanding problems with their products. 
-    </P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="why.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Introduction</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Why use a bug-tracking system?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/why-bugzilla.html

-<HTML
-><HEAD
-><TITLE
->Why use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="Why use a bug-tracking system?"
-HREF="why-tracking.html"><LINK
-REL="NEXT"
-TITLE="Using Bugzilla"
-HREF="using.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="why-tracking.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="why-bugzilla"
-></A
->2.3. Why use Bugzilla?</H1
-><P
->Bugzilla is the leading open-source/free software bug tracking 
-    system. It boasts many advanced features, including: 
-    <P
-></P
-><UL
-><LI
-><P
->Powerful searching</P
-></LI
-><LI
-><P
->User-configurable email notifications of bug changes</P
-></LI
-><LI
-><P
->Full change history</P
-></LI
-><LI
-><P
->Inter-bug dependency tracking and graphing</P
-></LI
-><LI
-><P
->Excellent attachment management</P
-></LI
-><LI
-><P
->Integrated, product-based, granular security schema</P
-></LI
-><LI
-><P
->Fully security-audited, and runs under Perl's taint mode</P
-></LI
-><LI
-><P
->A robust, stable RDBMS back-end</P
-></LI
-><LI
-><P
->Completely customisable and/or localisable web user
-        interface</P
-></LI
-><LI
-><P
->Additional XML, email and console interfaces</P
-></LI
-><LI
-><P
->Extensive configurability</P
-></LI
-><LI
-><P
->Smooth upgrade pathway between versions</P
-></LI
-></UL
->
-    </P
-><P
->Bugzilla is very adaptable to various situations. Known uses
-    currently include IT support queues, Systems Administration deployment
-    management, chip design and development problem tracking (both
-    pre-and-post fabrication), and software and hardware bug tracking for
-    luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
-    Combined with systems such as 
-    <A
-HREF="http://www.cvshome.org"
-TARGET="_top"
->CVS</A
->, 
-    <A
-HREF="http://www.mozilla.org/bonsai.html"
-TARGET="_top"
->Bonsai</A
->, or 
-    <A
-HREF="http://www.perforce.com"
-TARGET="_top"
->Perforce SCM</A
->, Bugzilla
-    provides a powerful, easy-to-use configuration management solution.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="why-tracking.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Why use a bug-tracking system?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/why-tracking.html

-<HTML
-><HEAD
-><TITLE
->Why use a bug-tracking system?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="What is Bugzilla?"
-HREF="what-is-bugzilla.html"><LINK
-REL="NEXT"
-TITLE="Why use Bugzilla?"
-HREF="why-bugzilla.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="what-is-bugzilla.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="why-bugzilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="why-tracking"
-></A
->2.2. Why use a bug-tracking system?</H1
-><P
->Those who do not use a bug-tracking system tend to rely on
-    shared lists, email, spreadsheets and/or Post-It notes to monitor the 
-    status of defects. This procedure
-    is usually error-prone and tends to cause those bugs judged least 
-    significant by developers to be dropped or ignored.</P
-><P
->Integrated defect-tracking systems make sure that nothing gets
-    swept under the carpet; they provide a method of creating, storing,
-    arranging and processing defect reports and enhancement requests.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="what-is-bugzilla.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="why-bugzilla.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->What is Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Why use Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/why.html

-<HTML
-><HEAD
-><TITLE
->Why use Bugzilla?</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 
-    Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="Why use a bug-tracking system?"
-HREF="why.html"><LINK
-REL="NEXT"
-TITLE="Using Bugzilla"
-HREF="using.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5 
-    Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="why.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 2. Introduction</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="why"
-></A
->2.3. Why use Bugzilla?</H1
-><P
->Bugzilla boasts many advanced features. These include: 
-    <P
-></P
-><UL
-><LI
-><P
->Powerful searching</P
-></LI
-><LI
-><P
->User-configurable email notifications of bug changes</P
-></LI
-><LI
-><P
->Full change history</P
-></LI
-><LI
-><P
->Inter-bug dependency tracking and graphing</P
-></LI
-><LI
-><P
->Excellent attachment management</P
-></LI
-><LI
-><P
->Integrated, product-based, granular security schema</P
-></LI
-><LI
-><P
->Fully security-audited, and runs under Perl's taint mode</P
-></LI
-><LI
-><P
->A robust, stable RDBMS back-end</P
-></LI
-><LI
-><P
->Web, XML, email and console interfaces</P
-></LI
-><LI
-><P
->Completely customisable and/or localisable web user
-        interface</P
-></LI
-><LI
-><P
->Extensive configurability</P
-></LI
-><LI
-><P
->Smooth upgrade pathway between versions</P
-></LI
-></UL
->
-    </P
-><P
->Bugzilla is very adaptable to various situations. Known uses
-    currently include IT support queues, Systems Administration deployment
-    management, chip design and development problem tracking (both
-    pre-and-post fabrication), and software and hardware bug tracking for
-    luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
-    Combined with systems such as 
-    <A
-HREF="http://www.cvshome.org"
-TARGET="_top"
->CVS</A
->, 
-    <A
-HREF="http://www.mozilla.org/bonsai.html"
-TARGET="_top"
->Bonsai</A
->, or 
-    <A
-HREF="http://www.perforce.com"
-TARGET="_top"
->Perforce SCM</A
->, Bugzilla
-    provides a powerful, easy-to-use solution to configuration management and
-    replication problems.</P
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="why.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="using.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Why use a bug-tracking system?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using Bugzilla</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file

docs/html/win32.html

-<html>
-<head>
-  <title>Page has moved!!</title>
-</head>
-<body>
-<h1>Page has moved!!</h1>
-<p style="font-size: 120%">This portion of the Bugzilla guide is now located
-at <a href="os-specific.html#os-win32">os-specific.html#os-win32</a>.</p>
-</body>
-</html>
-

docs/xml/Bugzilla-Guide.xml

@@ -11,13 +11,11 @@
 <!ENTITY administration SYSTEM "administration.xml">
 <!ENTITY using SYSTEM "using.xml">
 <!ENTITY integration SYSTEM "integration.xml">
-<!ENTITY future SYSTEM "future.xml">
 <!ENTITY index SYSTEM "index.xml">
 <!ENTITY customization SYSTEM "customization.xml">
 <!ENTITY patches SYSTEM "patches.xml">
-<!ENTITY variants SYSTEM "variants.xml">
 <!ENTITY introduction SYSTEM "introduction.xml">
-<!ENTITY revhistory SYSTEM "revhistory.xml">
+<!ENTITY modules SYSTEM "modules.xml">
 
 <!-- Things to change for a stable release:
      * bz-ver to current stable
@@ -32,9 +30,9 @@
      For a devel release, simple bump bz-ver and bz-date
 -->
 
-<!ENTITY bz-ver "2.17.5">
+<!ENTITY bz-ver "2.17.7">
 <!ENTITY bz-nextver "2.18">
-<!ENTITY bz-date "2004-01-15">
+<!ENTITY bz-date "2004-01-24">
 <!ENTITY % bz-devel "INCLUDE">
 
 <!ENTITY bz "http://www.bugzilla.org/">
@@ -54,7 +52,7 @@
 <!ENTITY min-dbd-mysql-ver "2.1010">
 <!ENTITY min-dbi-ver "1.32">
 <!ENTITY min-date-format-ver "2.21">
-<!ENTITY min-cgi-ver "2.88">
+<!ENTITY min-cgi-ver "2.93">
 <!-- Optional modules -->
 <!ENTITY min-gd-ver "1.20">
 <!ENTITY min-gd-graph-ver "any">
@@ -136,12 +134,6 @@
 <!-- About This Guide -->
 &about;
 
-<!-- Introduction -->
-&introduction;
-
-<!-- Using Bugzilla -->
-&using;
-
 <!-- Installing Bugzilla -->
 &installation;
 
@@ -151,12 +143,18 @@
 <!-- Customizing Bugzilla -->
 &customization;
 
+<!-- Using Bugzilla -->
+&using;
+
 <!-- Appendix: The Frequently Asked Questions -->
 &faq;
 
 <!-- Appendix: Custom Patches -->
 &patches;
 
+<!-- Appendix: Manually Installing Perl Modules -->
+&modules;
+
 <!-- Appendix: GNU Free Documentation License -->
 &gfdl;
 

docs/xml/about.xml

@@ -6,8 +6,11 @@
 
   <section id="copyright">
     <title>Copyright Information</title>
+
+    <para>This document is copyright (c) 2000-2004 by the various
+    Bugzilla contributors who wrote it.</para>
+    
     <blockquote>
-      <attribution>Copyright (c) 2000-2004 The Bugzilla Team</attribution>
       <para>
 	Permission is granted to copy, distribute and/or modify this
 	document under the terms of the GNU Free Documentation
@@ -45,10 +48,10 @@
     </para>
     <para>
       Although the Bugzilla development team has taken great care to
-      ensure that all exploitable bugs or options have been
-      fixed, security holes surely exist. Great care should be taken both in 
+      ensure that all exploitable bugs have been fixed, security holes surely 
+      exist in any piece of code. Great care should be taken both in 
       the installation and usage of this software. The Bugzilla development
-      team members assume no liability for your use of this software. You have 
+      team members assume no liability for your use of Bugzilla. You have 
       the source code, and are responsible for auditing it yourself to ensure
       your security needs are met.
     </para>
@@ -68,16 +71,36 @@
     </para>
     <para>
       The latest version of this guide can always be found at <ulink
-      url="http://www.bugzilla.org"/>, or checked out via CVS.
-      (Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla 
+      url="http://www.bugzilla.org"/>, or checked out via CVS by
+      following the <ulink url="http://www.mozilla.org/cvs.html">Mozilla 
       CVS</ulink> instructions and check out the 
       <filename>mozilla/webtools/bugzilla/docs/</filename>
-      subtree.) However, you should read the version
+      subtree. However, you should read the version
       which came with the Bugzilla release you are using.
     </para>
     <para>
-      The Bugzilla Guide is currently only available in English. 
-      If you would like to volunteer to translate it, please contact
+      The Bugzilla Guide, or a section of it, is also available in
+      the following languages:
+      <ulink url="http://bugzilla-de.sourceforge.net/docs/html/">German</ulink>.
+    </para>
+    
+    <para>  
+      In addition, there are Bugzilla template localisation projects in
+      the following languages. They may have translated documentation 
+      available: 
+      <ulink url="http://sourceforge.net/projects/bugzilla-be/">Belarusian</ulink>,
+      <ulink url="http://sourceforge.net/projects/bugzilla-br/">Brazilian Portuguese</ulink>,
+      <ulink url="http://sourceforge.net/projects/bugzilla-cn/">Chinese</ulink>,
+      <ulink url="http://sourceforge.net/projects/bugzilla-fr/">French</ulink>,
+      <ulink url="http://sourceforge.net/projects/bugzilla-de/">German</ulink>,
+      <ulink url="http://sourceforge.net/projects/bugzilla-kr/">Korean</ulink>,
+      <ulink url="http://sourceforge.net/projects/bugzilla-ru/">Russian</ulink> and
+      <ulink url="http://sourceforge.net/projects/bugzilla-es/">Spanish</ulink>.
+    </para>
+    
+    <para>  
+      If you would like to volunteer to translate the Guide into additional
+      languages, please contact
       <ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
     </para>
   </section>
@@ -113,7 +136,7 @@
     </para>
     
     <para>
-      Last but not least, all the members of the 
+      Also, thanks are due to the members of the 
       <ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
       netscape.public.mozilla.webtools</ulink>
       newsgroup. Without your discussions, insight, suggestions, and patches,

docs/xml/customization.xml

@@ -295,7 +295,7 @@
       </para>
 
       <para>After untarring the localizations (or creating your own) in the 
-      <filename class="directory"><varname>BUGZILLA_ROOT</varname>/template</filename> directory,
+      <filename class="directory">BUGZILLA_ROOT/template</filename> directory,
       you must update the <option>languages</option> parameter to contain any
       localizations you'd like to permit. You may also wish to set the
       <option>defaultlanguage</option> parameter to something other than
@@ -345,12 +345,12 @@
       tool (e.g. <command>grep</command>) to search the standard templates
       for occurrences of <methodname>Hook.process</methodname> or browse
       the directory tree in
-      <filename><varname>BUGZILLA_ROOT</varname>/template/en/extension/hook/</filename>,
+      <filename>BUGZILLA_ROOT/template/en/extension/hook/</filename>,
       which contains a directory for each hook in the following location:
     </para>
 
     <para>
-      <filename><varname>BUGZILLA_ROOT</varname>/template/en/extension/hook/<varname>PATH_TO_STANDARD_TEMPLATE</varname>/<varname>STANDARD_TEMPLATE_NAME</varname>/<varname>HOOK_NAME</varname>/</filename>
+      <filename>BUGZILLA_ROOT/template/en/extension/hook/PATH_TO_STANDARD_TEMPLATE/STANDARD_TEMPLATE_NAME/HOOK_NAME/</filename>
     </para>
 
     <para>
@@ -375,7 +375,7 @@
       The Bugzilla reviewers will promptly review each hook request,
       name the hook, add it to the template, check the new version
       of the template into CVS, and create the corresponding directory in
-      <filename><varname>BUGZILLA_ROOT</varname>/template/en/extension/hook/</filename>.
+      <filename>BUGZILLA_ROOT/template/en/extension/hook/</filename>.
     </para>
 
     <para>
@@ -415,7 +415,7 @@
       <filename>useful-links.html.tmpl</filename>, which is located in
       the <filename>global/</filename> subdirectory on the standard Bugzilla 
       template path
-      <filename><varname>BUGZILLA_ROOT</varname>/template/en/default/</filename>.
+      <filename>BUGZILLA_ROOT/template/en/default/</filename>.
       Looking in <filename>useful-links.html.tmpl</filename>, you find
       the following hook at the end of the list of standard Bugzilla
       administration links:
@@ -429,7 +429,7 @@
 
     <para>
       The corresponding directory for this hook is
-      <filename><varname>BUGZILLA_ROOT</varname>/template/en/extension/hook/global/useful-links.html.tmpl/edit/</filename>.
+      <filename>BUGZILLA_ROOT/template/en/extension/hook/global/useful-links.html.tmpl/edit/</filename>.
     </para>
 
     <para>
@@ -454,7 +454,7 @@
         <para>
           You may want to prefix your extension template names
           with the name of your extension, e.g. 
-          <filename><literal>projman</literal>-foo.html.tmpl</filename>, 
+          <filename>projman-foo.html.tmpl</filename>, 
           so they do not conflict with the names of templates installed by
           other extensions.
         </para>
@@ -465,7 +465,7 @@
           If your extension includes entirely new templates in addition to
           extensions of standard templates, it should install those new
           templates into an extension-specific subdirectory of the
-          <filename><varname>BUGZILLA_ROOT</varname>/template/en/extension/</filename> 
+          <filename>BUGZILLA_ROOT/template/en/extension/</filename> 
           directory.  The <filename>extension/</filename> directory, like the 
           <filename>default/</filename> and <filename>custom/</filename>
           directories, is part of the template search path, so putting templates
@@ -494,9 +494,9 @@
         <para>
           Installation customizers can also take advantage of hooks when adding
           code to a Bugzilla template.  To do so, create directories in
-          <filename><varname>BUGZILLA_ROOT</varname>/template/en/custom/hook/</filename>
+          <filename>BUGZILLA_ROOT/template/en/custom/hook/</filename>
           equivalent to the directories in
-          <filename><varname>BUGZILLA_ROOT</varname>/template/en/extension/hook/</filename>          
+          <filename>BUGZILLA_ROOT/template/en/extension/hook/</filename>          
           for the hooks you want to use, then place your customization templates
           into those directories.
         </para>

docs/xml/faq.xml

@@ -217,6 +217,19 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
 	</answer>
       </qandaentry>
       
+      <qandaentry>
+	<question id="faq-mod-perl">
+	  <para>
+	    Does bugzilla run under <filename>mod_perl</filename>?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    At present, no. This is being worked on.
+	  </para>
+	</answer>
+      </qandaentry>
+      
     </qandadiv>
 
     <qandadiv id="faq-phb">

docs/xml/gfdl.xml

@@ -16,7 +16,7 @@
   </blockquote>
 
   <section label="0" id="gfdl-0">
-    <title>PREAMBLE</title>
+    <title>Preamble</title>
 
     <para>The purpose of this License is to make a manual, textbook, or other
     written document "free" in the sense of freedom: to assure everyone the
@@ -41,7 +41,7 @@
   </section>
 
   <section label="1" id="gfdl-1">
-    <title>APPLICABILITY AND DEFINITIONS</title>
+    <title>Applicability and Definition</title>
 
     <para>This License applies to any manual or other work that contains a
     notice placed by the copyright holder saying it can be distributed under
@@ -101,7 +101,7 @@
   </section>
 
   <section label="2" id="gfdl-2">
-    <title>VERBATIM COPYING</title>
+    <title>Verbatim Copying</title>
 
     <para>You may copy and distribute the Document in any medium, either
     commercially or noncommercially, provided that this License, the
@@ -118,7 +118,7 @@
   </section>
 
   <section label="3" id="gfdl-3">
-    <title>COPYING IN QUANTITY</title>
+    <title>Copying in Quantity</title>
 
     <para>If you publish printed copies of the Document numbering more than
     100, and the Document's license notice requires Cover Texts, you must
@@ -157,7 +157,7 @@
   </section>
 
   <section label="4" id="gfdl-4">
-    <title>MODIFICATIONS</title>
+    <title>Modifications</title>
 
     <para>You may copy and distribute a Modified Version of the Document
     under the conditions of sections 2 and 3 above, provided that you release
@@ -287,7 +287,7 @@
   </section>
 
   <section label="5" id="gfdl-5">
-    <title>COMBINING DOCUMENTS</title>
+    <title>Combining Documents</title>
 
     <para>You may combine the Document with other documents released under
     this License, under the terms defined in section 4 above for modified
@@ -313,7 +313,7 @@
   </section>
 
   <section label="6" id="gfdl-6">
-    <title>COLLECTIONS OF DOCUMENTS</title>
+    <title>Collections of Documents</title>
 
     <para>You may make a collection consisting of the Document and other
     documents released under this License, and replace the individual copies
@@ -329,7 +329,7 @@
   </section>
 
   <section label="7" id="gfdl-7">
-    <title>AGGREGATION WITH INDEPENDENT WORKS</title>
+    <title>Aggregation with Independent Works</title>
 
     <para>A compilation of the Document or its derivatives with other
     separate and independent documents or works, in or on a volume of a
@@ -348,7 +348,7 @@
   </section>
 
   <section label="8" id="gfdl-8">
-    <title>TRANSLATION</title>
+    <title>Translation</title>
 
     <para>Translation is considered a kind of modification, so you may
     distribute translations of the Document under the terms of section 4.
@@ -363,7 +363,7 @@
   </section>
 
   <section label="9" id="gfdl-9">
-    <title>TERMINATION</title>
+    <title>Termination</title>
 
     <para>You may not copy, modify, sublicense, or distribute the Document
     except as expressly provided for under this License. Any other attempt to
@@ -375,7 +375,7 @@
   </section>
 
   <section label="10" id="gfdl-10">
-    <title>FUTURE REVISIONS OF THIS LICENSE</title>
+    <title>Future Revisions of this License</title>
 
     <para>The Free Software Foundation may publish new, revised versions of
     the GNU Free Documentation License from time to time. Such new versions

docs/xml/modules.xml

+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
+<appendix id="install-perlmodules-manual">
+  <title>Manual Installation of Perl Modules</title>
+  
+  <section id="modules-manual-instructions">
+    <title>Instructions</title>
+    <para>If you need to install Perl modules manually, here's how it's done.
+    Download the module using the link given in the next section, and then
+    apply this magic incantation, as root:
+    </para>
+
+    <para>  
+      <screen><prompt>bash#</prompt> tar -xzvf &lt;module&gt;.tar.gz
+<prompt>bash#</prompt> cd &lt;module&gt;
+<prompt>bash#</prompt> perl Makefile.PL
+<prompt>bash#</prompt> make
+<prompt>bash#</prompt> make test
+<prompt>bash#</prompt> make install</screen>
+    </para>
+  </section>
+    
+  <section id="modules-manual-download">
+    <title>Download Locations</title>
+    
+    <para>Note: some modules are in the core distribution of
+    ActiveState Perl for Windows. Others are not available.
+    No PPM links have been provided in either of these two cases.
+    </para>
+    
+    <para>CGI:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/CGI.pm/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/CGI.zip"/>
+        Documentation: <ulink url="http://www.perldoc.com/perl5.8.0/lib/CGI.html"/>
+      </literallayout>
+    </para>
+
+    <para>TimeDate:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/TimeDate/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/TimeDate.zip"/>
+        Documentation: <ulink url="http://search.cpan.org/dist/TimeDate/lib/Date/Format.pm"/>
+      </literallayout>
+    </para>
+
+    <para>DBI:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/DBI/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBI.zip"/>
+        Documentation: <ulink url="http://dbi.perl.org/docs/"/>
+      </literallayout>
+    </para>
+
+    <para>DBD::mysql:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/DBD-mysql/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/DBD-Mysql.zip"/>
+        Documentation: <ulink url="http://search.cpan.org/dist/DBD-mysql/lib/DBD/mysql.pm"/>
+      </literallayout>
+    </para>
+
+    <para>File::Spec:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/File-Spec/"/>
+        PPM Download Page: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/File-Spec.zip"/>
+        Documentation: <ulink url="http://www.perldoc.com/perl5.8.0/lib/File/Spec.html"/>
+      </literallayout>
+    </para>
+
+    <para>File::Temp:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/File-Temp/"/>
+        Documentation: <ulink url="http://www.perldoc.com/perl5.8.0/lib/File/Temp.html"/>
+      </literallayout>
+    </para>
+
+    <para>Template Toolkit:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/Template-Toolkit/"/>
+        PPM Download Link: <ulink url="http://openinteract.sourceforge.net/ppmpackages/5.6/Template-Toolkit.tar.gz"/>
+        Documentation: <ulink url="http://www.template-toolkit.org/docs.html"/>
+      </literallayout>
+    </para>
+
+    <para>Text::Wrap:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/Text-Tabs+Wrap/"/>
+        Documentation: <ulink url="http://www.perldoc.com/perl5.8.0/lib/Text/Wrap.html"/>
+      </literallayout>
+    </para>
+ 
+    <para>GD:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/GD/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GD.zip"/>
+        Documentation: <ulink url="http://stein.cshl.org/WWW/software/GD/"/>
+      </literallayout>
+    </para>
+
+    <para>Chart::Base:
+      <!-- TODO: Chart::Base doesn't seem to have any documentation -->
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/Chart/"/>
+      </literallayout>
+    </para>
+
+     <para>GD::Graph:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/GDGraph/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDGraph.zip"/>
+        Documentation: <ulink url="http://search.cpan.org/dist/GDGraph/Graph.pm"/>
+      </literallayout>
+    </para>
+
+    <para>GD::Text::Align:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/GDTextUtil/"/>
+        PPM Download Page: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/GDTextUtil.zip"/>
+        Documentation: <ulink url="http://search.cpan.org/dist/GDTextUtil/Text/Align.pm"/>
+      </literallayout>
+    </para>
+
+    <para>MIME::Parser:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/MIME-tools/"/>
+        PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/MIME-tools.zip"/>
+        Documentation: <ulink url="http://search.cpan.org/dist/MIME-tools/lib/MIME/Parser.pm"/>
+      </literallayout>
+    </para>
+
+   <para>XML::Parser:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/dist/XML-Parser/"/>
+        Documentation: <ulink url="http://www.perldoc.com/perl5.6.1/lib/XML/Parser.html"/>
+      </literallayout>
+    </para>
+
+    <para>PatchReader:
+      <literallayout>
+        CPAN Download Page: <ulink url="http://search.cpan.org/author/JKEISER/PatchReader/"/>
+        Documentation: <ulink url="http://www.johnkeiser.com/mozilla/Patch_Viewer.html"/>
+      </literallayout>
+    </para>
+   </section>
+</appendix>