/[ddp]/manuals/trunk/quick-reference/debian-reference.raw.xml

Diff of /manuals/trunk/quick-reference/debian-reference.raw.xml

Parent Directory | Revision Log | View Patch Patch

-revision 7355 by osamu,
Tue May 18 15:35:25 2010 UTC
+revision 7629 by osamu,
Thu Sep 23 12:57:52 2010 UTC
 Line 12
        <para>This book is free; you may redistribute it and/or modify it under the terms of the GNU General Public License of any version compliant to the Debian Free Software Guidelines (DFSG).</para>
      </abstract>
      <copyright>
-       <year>2007-2009</year>
+       <year>2007-2010</year>
        <holder>Osamu Aoki</holder>
      </copyright>
      <legalnotice>
 Line 249 
 $ sensible-browse "http://www.debian.org
      <simpara>I think learning a computer system is like learning a new foreign language.  Although tutorial books and documentation are helpful, you have to practice it yourself.  In order to help you get started smoothly, I elaborate a few basic points.</simpara>
      <simpara>The powerful design of <ulink url="http://www.debian.org">Debian</ulink> <ulink url="http://en.wikipedia.org/wiki/GNU">GNU</ulink>/<ulink url="http://en.wikipedia.org/wiki/Linux">Linux</ulink> comes from the <ulink url="http://en.wikipedia.org/wiki/Unix">Unix</ulink> operating system, i.e., a <ulink url="http://en.wikipedia.org/wiki/Multi-user">multiuser</ulink>, <ulink url="http://en.wikipedia.org/wiki/Computer_multitasking">multitasking</ulink> operating system.  You must learn to take advantage of the power of these features and similarities between Unix and GNU/Linux.</simpara>
      <simpara>Don't shy away from Unix oriented texts and don't rely solely on GNU/Linux texts, as this robs you of much useful information.</simpara>
-     <simpara>"<ulink url="http://packages.debian.org/search?keywords=rutebook">Rute User's Tutorial and Exposition</ulink>", in the Debian non-free archive as the <literal>rutebook</literal> package (popcon: @-@pop-rutebook@-@), provides a good online resource to the generic system administration.</simpara>
      <note>
        <simpara>If you have been using any <ulink url="http://en.wikipedia.org/wiki/Unix-like">Unix-like</ulink> system for a while with command line tools, you probably know everything I explain here.  Please use this as a reality check and refresher.</simpara>
      </note>
-Line 399 
 This preserves some of the environment o
+Line 398 
 This preserves some of the environment o
        </section>
        <section id="_additional_package_suggestions_for_the_newbie">
          <title>Additional package suggestions for the newbie</title>
-         <simpara>Although even the minimal installation of the Debian system without any desktop environment tasks provides the basic Unix functionality, it is a good idea to install few additional commandline and curses based character terminal packages such as <literal>mc</literal> and <literal>vim</literal> with <literal>aptitude</literal>(8) for beginners to get started by the following.</simpara>
+         <simpara>Although even the minimal installation of the Debian system without any desktop environment tasks provides the basic Unix functionality, it is a good idea to install few additional commandline and curses based character terminal packages such as <literal>mc</literal> and <literal>vim</literal> with <literal>apt-get</literal>(8) for beginners to get started by the following.</simpara>
-         <screen># aptitude update
+         <screen># apt-get update
   ...
- # aptitude install mc vim sudo
+ # apt-get install mc vim sudo
   ...</screen>
          <simpara>If you already had these packages installed, no new packages are installed.</simpara>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-Line 695 
 This preserves some of the environment o
+Line 694 
 This preserves some of the environment o
      The Linux System Administrators' Guide
      </entry>
                </row>
-               <row>
-                 <entry>
-                   <literal>rutebook</literal>
-                 </entry>
-                 <entry>
-     @-@popcon1@-@
-     </entry>
-                 <entry>
-     @-@psize1@-@
-     </entry>
-                 <entry>
-     Linux: Rute User's Tutorial and Exposition (non-free)
-     </entry>
-               </row>
              </tbody>
            </tgroup>
          </table>
          <simpara>You can install some of these packages by the following.</simpara>
-         <screen># aptitude install package_name</screen>
+         <screen># apt-get install package_name</screen>
        </section>
        <section id="_an_extra_user_account">
          <title>An extra user account</title>
-Line 727 
 This preserves some of the environment o
+Line 712 
 This preserves some of the environment o
          <title>sudo configuration</title>
          <simpara>For the typical single user workstation such as the desktop Debian system on the laptop PC, it is common to deploy simple configuration of <literal>sudo</literal>(8) as follows to let the non-privileged user, e.g. <literal>penguin</literal>, to gain administrative privilege just with his user password but without the root password.</simpara>
          <screen># echo "penguin  ALL=(ALL) ALL" &gt;&gt; /etc/sudoers</screen>
+         <simpara>Alternatively, it is also common to do as follows to let the non-privileged user, e.g. <literal>penguin</literal>, to gain administrative privilege without any password.</simpara>
+         <screen># echo "penguin  ALL=(ALL) NOPASSWD:ALL" &gt;&gt; /etc/sudoers</screen>
          <simpara>This trick should only be used for the single user workstation which you administer and where you are the only user.</simpara>
          <warning>
            <simpara>Do not set up accounts of regular users on multiuser workstation like this because it would be very bad for system security.</simpara>
-Line 1729 
 crw-rw-rw- 1 root root    1,  5 2007-04-
+Line 1716 
 crw-rw-rw- 1 root root    1,  5 2007-04-
        <title>Midnight Commander (MC)</title>
        <simpara><ulink url="http://en.wikipedia.org/wiki/Midnight_Commander">Midnight Commander (MC)</ulink> is a GNU "Swiss army knife" for the Linux console and other terminal environments.  This gives newbie a menu driven console experience which is much easier to learn than standard Unix commands.</simpara>
        <simpara>You may need to install the Midnight Commander package which is titled "<literal>mc</literal>" by the following.</simpara>
-       <screen>$ sudo aptitude install mc</screen>
+       <screen>$ sudo apt-get install mc</screen>
        <simpara>Use the <literal>mc</literal>(1) command to explore the Debian system.  This is the best way to learn.  Please explore few interesting locations just using the cursor keys and Enter key.</simpara>
        <itemizedlist>
          <listitem>
-Line 2188 
 export VISUAL=mcedit</screen>
+Line 2175 
 export VISUAL=mcedit</screen>
  . /usr/share/mc/bin/mc.sh
  # set CDPATH to good one
- CDPATH=.:/usr/share/doc:~/Desktop/src:~/Desktop:~
+ CDPATH=.:/usr/share/doc:~:~/Desktop:~
  export CDPATH
  PATH="${PATH}":/usr/sbin:/sbin
-Line 2910 
 Script started, file is typescript</scre
+Line 2897 
 Script started, file is typescript</scre
                </row>
                <row>
                  <entry>
-                   <literal>tar -xvf -j &lt;foo&gt;.tar.bz2</literal>
+                   <literal>tar -xvjf &lt;foo&gt;.tar.bz2</literal>
                  </entry>
                  <entry>
      extract files from "<literal>&lt;foo&gt;.tar.bz2</literal>" archive
-Line 2974 
 Script started, file is typescript</scre
+Line 2961 
 Script started, file is typescript</scre
            <simpara>For <literal>cd</literal> command, see <literal>builtins</literal>(7).</simpara>
          </note>
          <note>
-           <simpara>The default pager of the bare bone Debian system is <literal>more</literal>(1) which cannot scroll back.  By installing the <literal>less</literal> package using command line "<literal>aptitude install less</literal>", <literal>less</literal>(1) becomes default pager and you can scroll back with cursor keys.</simpara>
+           <simpara>The default pager of the bare bone Debian system is <literal>more</literal>(1) which cannot scroll back.  By installing the <literal>less</literal> package using command line "<literal>apt-get install less</literal>", <literal>less</literal>(1) becomes default pager and you can scroll back with cursor keys.</simpara>
          </note>
          <note>
            <simpara>The "<literal>[</literal>" and "<literal>]</literal>" in the regular expression of the "<literal>ps aux | grep -e "[e]xim4*"</literal>" command above enable <literal>grep</literal> to avoid matching itself.  The "<literal>4*</literal>" in the regular expression means 0 or more repeats of character "<literal>4</literal>" thus enables <literal>grep</literal> to match both "<literal>exim</literal>" and "<literal>exim4</literal>".  Although "<literal>*</literal>" is used in the shell filename glob and the regular expression, their meanings are different.  Learn the regular expression from <literal>grep</literal>(1).</simpara>
-Line 3340 
 dimanche 3 juin 2007, 10:27:33 (UTC+0900
+Line 3327 
 dimanche 3 juin 2007, 10:27:33 (UTC+0900
            </tgroup>
          </table>
          <tip>
-           <simpara>Shell expands "<literal>~/</literal>" to current user’s home directory, i.e., "<literal>$HOME/</literal>". Shell expands "<literal>~foo/</literal>" to <literal>foo</literal>'s home directory, i.e., "<literal>/home/foo/</literal>".</simpara>
+           <simpara>Shell expands "<literal>~/</literal>" to current user's home directory, i.e., "<literal>$HOME/</literal>". Shell expands "<literal>~foo/</literal>" to <literal>foo</literal>'s home directory, i.e., "<literal>/home/foo/</literal>".</simpara>
          </tip>
        </section>
        <section id="_command_line_options">
-Line 4427 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4414 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      <simpara><ulink url="http://www.debian.org">Debian</ulink> is a volunteer organization which builds <emphasis role="strong">consistent</emphasis> distributions of pre-compiled binary packages of free software and distributes them from its archive.</simpara>
      <simpara><ulink url="http://ftp.us.debian.org/debian/">The Debian archive</ulink> is offered by <ulink url="http://www.debian.org/mirror/">many remote mirror sites</ulink> for access through HTTP and FTP methods. It is also available as <ulink url="http://www.debian.org/CD/">CD-ROM/DVD</ulink>.</simpara>
      <simpara>The Debian package management system, <emphasis role="strong">when used properly</emphasis>, offers the user to install <emphasis role="strong">consistent sets of binary packages</emphasis> to the system from the archive.  Currently, there are @-@all-packages@-@ packages available for the @-@arch@-@ architecture.</simpara>
-     <simpara>The Debian package management system has a rich history and many choices for the front end user program and back end archive access method to be used.  Currently, we recommend <literal>aptitude</literal>(8) as the main front end program for the Debian package management activity.</simpara>
+     <simpara>The Debian package management system has a rich history and many choices for the front end user program and back end archive access method to be used.  Currently, we recommend the following.</simpara>
+     <itemizedlist>
+       <listitem>
+         <simpara><literal>apt-get</literal>(8) for all commandline operations, including package installation and removal, and dist-upgrades.
+ </simpara>
+       </listitem>
+       <listitem>
+         <simpara><literal>aptitude</literal>(8) for an interactive text interface to manage the installed packages and to search the available packages.
+ </simpara>
+       </listitem>
+       <listitem>
+         <simpara><literal>update-manager</literal>(8) for keeping your system up-to-date if you're running the default GNOME desktop.
+ </simpara>
+       </listitem>
+     </itemizedlist>
      <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
        <title>List of Debian package management tools</title>
        <tgroup cols="4">
-         <colspec colwidth="119pt" align="left"/>
+         <colspec colwidth="124pt" align="left"/>
          <colspec colwidth="76pt" align="left"/>
          <colspec colwidth="70pt" align="left"/>
          <colspec colwidth="483pt" align="left"/>
-Line 4454 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4455 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
          <tbody>
            <row>
              <entry>
-               <literal>aptitude</literal>
+               <literal>apt</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4463 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4464 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     terminal-based package manager (current standard, front-end for <literal>apt</literal>)
+     Advanced Packaging Tool (APT), front-end for <literal>dpkg</literal> providing "<literal>http</literal>", "<literal>ftp</literal>", and "<literal>file</literal>" archive access methods (<literal>apt-get</literal>/<literal>apt-cache</literal> commands included)
      </entry>
            </row>
            <row>
              <entry>
-               <literal>apt</literal>
+               <literal>aptitude</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4477 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4478 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     Advanced Packaging Tool (APT), front-end for <literal>dpkg</literal> providing "<literal>http</literal>", "<literal>ftp</literal>", and "<literal>file</literal>" archive access methods (<literal>apt-get</literal>/<literal>apt-cache</literal> commands included)
+     interactive terminal-based package manager with <literal>aptitude</literal>(8)
      </entry>
            </row>
            <row>
              <entry>
-               <literal>tasksel</literal>
+               <literal>update-manager-gnome</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4491 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4492 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     tool for selecting tasks for installation on Debian system (front-end for APT)
+     GNOME application that manages software updates with <literal>update-manager</literal>(8)
      </entry>
            </row>
            <row>
              <entry>
-               <literal>unattended-upgrades</literal>
+               <literal>tasksel</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4505 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4506 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     enhancement package for APT to enable automatic installation of security upgrades
+     tool for selecting tasks for installation on Debian system (front-end for APT)
      </entry>
            </row>
            <row>
              <entry>
-               <literal>dselect</literal>
+               <literal>unattended-upgrades</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4519 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4520 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     terminal-based package manager (previous standard, front-end for APT and other old access methods)
+     enhancement package for APT to enable automatic installation of security upgrades
      </entry>
            </row>
            <row>
              <entry>
-               <literal>dpkg</literal>
+               <literal>dselect</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4533 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4534 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     package management system for Debian
+     terminal-based package manager (previous standard, front-end for APT and other old access methods)
      </entry>
            </row>
            <row>
              <entry>
-               <literal>synaptic</literal>
+               <literal>dpkg</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4547 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4548 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     graphical package manager (GNOME front-end for APT)
+     package management system for Debian
      </entry>
            </row>
            <row>
              <entry>
-               <literal>kpackage</literal>
+               <literal>synaptic</literal>
              </entry>
              <entry>
      @-@popcon1@-@
-Line 4561 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4562 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
      @-@psize1@-@
      </entry>
              <entry>
-     graphical package manager (KDE front-end for APT)
+     graphical package manager (GNOME front-end for APT)
      </entry>
            </row>
            <row>
-Line 4637 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
+Line 4638 
 Sat, 23 Aug 2003 08:30:50 +0200</screen>
          </tbody>
        </tgroup>
      </table>
-     <note>
-       <simpara>The annoying <ulink url="http://bugs.debian.org/411123">bug #411123</ulink> for the mixed use of <literal>aptitude</literal>(8) and <literal>apt-get</literal>(8) commands has been resolved.  If this kept you from using <literal>aptitude</literal>, please reconsider.</simpara>
-     </note>
      <section id="_debian_package_management_prerequisites">
        <title>Debian package management prerequisites</title>
        <section id="_package_configuration">
-Line 4832 
 The 2nd argument is the distribution nam
+Line 4830 
 The 2nd argument is the distribution nam
            </listitem>
            <listitem>
              <simpara>
- The 3rd and following arguments are the list of valid archive component names of the Debian archive.
+ The 3rd and following arguments are the list of valid archive area names of the Debian archive.
  </simpara>
            </listitem>
          </itemizedlist>
          <simpara>The "<literal>deb-src</literal>" lines can safely be omitted (or commented out by placing "#" at the start of the line) if it is just for <literal>aptitude</literal> which does not access source related meta data. It speeds up the updates of the archive meta data. The URL can be "<literal>http://</literal>", "<literal>ftp://</literal>", "<literal>file://</literal>", ….</simpara>
          <tip>
-           <simpara>If "<literal>sid</literal>" is used in the above example instead of "<literal>@-@codename-stable@-@</literal>", the "<literal>deb: <ulink url="http://security.debian.org/">http://security.debian.org/</ulink> …</literal>" line for security updates in the "<literal>/etc/apt/sources.list</literal>" is not required.   This is because "<literal>sid</literal>" (<literal>unstable</literal>) is always updated whenever security issues are fixed.  There is no need to have a separate security update archive for "<literal>sid</literal>".</simpara>
+           <simpara>If "<literal>sid</literal>" is used in the above example instead of "<literal>@-@codename-stable@-@</literal>", the "<literal>deb: <ulink url="http://security.debian.org/">http://security.debian.org/</ulink> …</literal>" line for security updates in the "<literal>/etc/apt/sources.list</literal>" is not required.   This is because there is no security update archive for "<literal>sid</literal>" (<literal>unstable</literal>).</simpara>
          </tip>
          <simpara>Here is the list of URL of the Debian archive sites and suite name or codename used in the configuration file.</simpara>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
            <title>List of Debian archive sites</title>
            <tgroup cols="3">
-             <colspec colwidth="483pt" align="left"/>
+             <colspec colwidth="504pt" align="left"/>
              <colspec colwidth="211pt" align="left"/>
              <colspec colwidth="103pt" align="left"/>
              <thead>
-Line 4959 
 The 3rd and following arguments are the
+Line 4957 
 The 3rd and following arguments are the
                </row>
                <row>
                  <entry>
-                   <ulink url="http://backports.org/debian/">http://backports.org/debian/</ulink>
+                   <ulink url="http://backports.debian.org/debian-backports/">http://backports.debian.org/debian-backports/</ulink>
                  </entry>
                  <entry>
                    <literal>@-@codename-stable@-@-backports</literal>
                  </entry>
                  <entry>
-     newer backported packages for @-@codename-stable@-@ (non-official, optional)
+     newer backported packages for @-@codename-stable@-@ (official, optional)
      </entry>
                </row>
              </tbody>
            </tgroup>
          </table>
          <caution>
-           <simpara>Only pure <emphasis role="strong"><literal>stable</literal></emphasis> release with security updates provides the best stability. Running mostly <emphasis role="strong"><literal>stable</literal></emphasis> release mixed with some packages from <emphasis role="strong"><literal>testing</literal></emphasis> or <emphasis role="strong"><literal>unstable</literal></emphasis> release is riskier than running pure <emphasis role="strong"><literal>unstable</literal></emphasis> release.  If you really need the latest version of some programs under <emphasis role="strong"><literal>stable</literal></emphasis> release, please use packages from <ulink url="http://www.debian.org/volatile/">the debian-volatile project</ulink> and <ulink url="http://backports.org">backports.org</ulink> (see <xref linkend="_volatile_and_backports_org"/>) services.  These services must be used with extra care.</simpara>
+           <simpara>Only pure <emphasis role="strong"><literal>stable</literal></emphasis> release with security updates provides the best stability. Running mostly <emphasis role="strong"><literal>stable</literal></emphasis> release mixed with some packages from <emphasis role="strong"><literal>testing</literal></emphasis> or <emphasis role="strong"><literal>unstable</literal></emphasis> release is riskier than running pure <emphasis role="strong"><literal>unstable</literal></emphasis> release for library version mismatch etc.  If you really need the latest version of some programs under <emphasis role="strong"><literal>stable</literal></emphasis> release, please use packages from <ulink url="http://www.debian.org/volatile/">the debian-volatile project</ulink> and <ulink url="http://backports.debian.org">http://backports.debian.org</ulink> (see <xref linkend="_volatile_and_backports"/>) services.  These services must be used with extra care.</simpara>
          </caution>
          <caution>
            <simpara>You should basically list only one of <literal>stable</literal>, <literal>testing</literal>, or <literal>unstable</literal> suites in the "<literal>deb</literal>" line.  If you list any combination of <literal>stable</literal>, <literal>testing</literal>, and <literal>unstable</literal> suites in the "<literal>deb</literal>" line, APT programs slow down while only the latest archive is effective.  Multiple listing makes sense for these when the "<literal>/etc/apt/preferences</literal>" file is used with clear objectives (see <xref linkend="_tweaking_candidate_version"/>).</simpara>
          </caution>
-         <note>
+         <tip>
            <simpara>For the Debian system with the <literal>stable</literal> and <literal>testing</literal> suites, it is a good idea to include lines with "<literal>http://security.debian.org/</literal>" in the "<literal>/etc/apt/sources.list</literal>" to enable security updates as in the example above.</simpara>
+         </tip>
+         <note>
+           <simpara>The security bugs for the <literal>stable</literal> archive are fixed by the Debian security team.  This activity has been quite rigorous and reliable.  Those for the <literal>testing</literal> archive may be fixed by the Debian testing security team.  For <ulink url="http://lists.debian.org/debian-testing-security-announce/2008/12/msg00019.html">several</ulink> <ulink url="http://lists.debian.org/debian-testing-security-announce/2010/01/msg00000.html">reasons</ulink>, this activity is not as rigorous as that for <literal>stable</literal> and you may need to wait for the migration of fixed <literal>unstable</literal> packages.  Those for the <literal>unstable</literal> archive are fixed by the individual maintainer.  Actively maintained <literal>unstable</literal> packages are usually in a fairly good shape by leveraging latest upstream security fixes.  See <ulink url="http://www.debian.org/security/faq">Debian security FAQ</ulink> for how Debian handles security bugs.</simpara>
          </note>
-         <simpara>Each Debian archive consists of 3 components. Components are alternatively called <ulink url="http://www.debian.org/doc/debian-policy/ch-archive#s-sections">categories in "Debian Policy"</ulink> or areas in <ulink url="http://www.debian.org/social_contract">"Debian Social Contract"</ulink>.  The component is grouped by the compliance to <ulink url="http://www.debian.org/social_contract#guidelines">"The Debian Free Software Guidelines" (DFSG)</ulink>.</simpara>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-           <title>List of Debian archive components</title>
+           <title>List of Debian archive area</title>
            <tgroup cols="3">
              <colspec colwidth="59pt" align="left"/>
              <colspec colwidth="130pt" align="left"/>
 Line 4990 
 The 3rd and following arguments are the
              <thead>
                <row>
                  <entry>
-     component
+     area
      </entry>
                  <entry>
      number of packages
      </entry>
                  <entry>
-     criteria of package
+     criteria of package component
      </entry>
                </row>
              </thead>
 Line 5037 
 The 3rd and following arguments are the
              </tbody>
            </tgroup>
          </table>
-         <simpara>Here the number of packages in the above is for the @-@arch@-@ architecture.  Strictly speaking, only the <literal>main</literal> component archive shall be considered as the Debian system.</simpara>
+         <simpara>Here the number of packages in the above is for the @-@arch@-@ architecture.  Strictly speaking, only the <literal>main</literal> area archive shall be considered as the Debian system.</simpara>
          <simpara>The Debian archive organization can be studied best by pointing your browser to the each archive URL appended with <literal>dists</literal> or <literal>pool</literal>.</simpara>
          <simpara>The distribution is referred by two ways, the suite or <ulink url="http://www.debian.org/doc/manuals/developers-reference/resources.html#codenames">codename</ulink>. The word distribution is alternatively used as the synonym to the suite in many documentations. The relationship between the suite and the codename can be summarized as the following.</simpara>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
 Line 5096 
 The 3rd and following arguments are the
            </tgroup>
          </table>
          <simpara>The history of codenames are described in <ulink url="http://www.debian.org/doc/manuals/debian-faq/ch-ftparchives#s-oldcodenames">Debian FAQ: 6.3.1 Which other codenames have been used in the past?</ulink></simpara>
-         <simpara>In the stricter Debian archive terminology, the word "section" is specifically used for the categorization of packages by the application area.  (Although, the word "main section" may sometimes be used to describe the Debian archive section which provides the main component.)</simpara>
+         <simpara>In the stricter Debian archive terminology, the word "section" is specifically used for the categorization of packages by the application area.  (Although, the word "main section" may sometimes be used to describe the Debian archive area named as "main".)</simpara>
          <simpara>Every time a new upload is done by the Debian developer (DD) to the <literal>unstable</literal> archive (via <ulink url="http://incoming.debian.org/">incoming</ulink> processing), DD is required to ensure uploaded packages to be compatible with the latest set of packages in the latest <literal>unstable</literal> archive.</simpara>
          <simpara>If DD breaks this compatibility intentionally for important library upgrade etc, there is usually announcement to <ulink url="http://lists.debian.org/debian-devel/">the debian-devel mailing list</ulink> etc.</simpara>
          <simpara>Before a set of packages are moved by the Debian archive maintenance script from the <literal>unstable</literal> archive to the <literal>testing</literal> archive, the archive maintenance script not only checks the maturity (about 10 days old) and the status of the RC bug reports for the packages but also tries to ensure them to be compatible with the latest set of packages in the <literal>testing</literal> archive. This process makes the <literal>testing</literal> archive very current and usable.</simpara>
 Line 5221 
 This declares a week dependency like Sug
            </listitem>
            <listitem>
              <simpara>
+ "Breaks"
+ </simpara>
+             <itemizedlist>
+               <listitem>
+                 <simpara>
+ This declares a package incompatibility usually with some version specification.  Generally the resolution is to upgrade all of the packages listed in this field.
+ </simpara>
+               </listitem>
+             </itemizedlist>
+           </listitem>
+           <listitem>
+             <simpara>
  "Conflicts"
  </simpara>
              <itemizedlist>
-Line 5485 
 $ mc</screen>
+Line 5497 
 $ mc</screen>
      </section>
      <section id="_basic_package_management_operations">
        <title>Basic package management operations</title>
-       <simpara>Aptitude is the current preferred package management tool for the Debian system.  It can be used as the commandline alternative to <literal>apt-get</literal> / <literal>apt-cache</literal> and also as the full screen interactive package management tool.</simpara>
+       <simpara>Basic package management operations on the Debian system can be performed by any package management tools available on the Debian system.  Here, we explain basic package management tools: <literal>apt-get</literal> / <literal>apt-cache</literal> and <literal>aptitude</literal>.</simpara>
        <simpara>For the package management operation which involves package installation or updates package metadata, you need to have root privilege.</simpara>
-       <section id="_basic_package_management_operations_with_commandline">
+       <section id="_literal_apt_get_literal_literal_apt_cache_literal_vs_literal_aptitude_literal">
-         <title>Basic package management operations with commandline</title>
+         <title><literal>apt-get</literal> / <literal>apt-cache</literal> vs. <literal>aptitude</literal></title>
-         <simpara>Here are basic package management operations with commandline using <literal>aptitude</literal>(8) and <literal>apt-get</literal>(8) /<literal>apt-cache</literal>(8).</simpara>
+         <simpara>The <literal>apt-get</literal> and <literal>apt-cache</literal> commands are the most <emphasis role="strong">basic</emphasis> package management tool.</simpara>
+         <itemizedlist>
+           <listitem>
+             <simpara><literal>apt-get</literal> and <literal>apt-cache</literal> offer only the commandline user interface.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>apt-get</literal> is most suitable for the <emphasis role="strong">major system upgrade</emphasis> between releases, etc.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>apt-get</literal> offers a <emphasis role="strong">robust and stable</emphasis> package resolver which uses the common package state data.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>apt-get</literal> has been updated to support autoinstall and autoremove of recommended packages.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>apt-get</literal> has been updated to support logging of package activities.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>apt-cache</literal> offers a <emphasis role="strong">standard</emphasis> regex based search on the package name and description.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>apt-get</literal> and <literal>apt-cache</literal> can manage multiple versions of packages using <literal>/etc/apt/preferences</literal> but it is quite cumbersome.
+ </simpara>
+           </listitem>
+         </itemizedlist>
+         <simpara>The <literal>aptitude</literal> command is the most <emphasis role="strong">versatile</emphasis> package management tool.</simpara>
+         <itemizedlist>
+           <listitem>
+             <simpara><literal>aptitude</literal> offers the fullscreen interactive text user interface.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> offers the commandline user interface, too.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> is most suitable for the <emphasis role="strong">daily interactive package management</emphasis> such as inspecting installed packages and searching available packages.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> offers an <emphasis role="strong">enhanced</emphasis> package resolver which also uses an extra package state data used only by <literal>aptitude</literal>.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> supports autoinstall and autoremove of recommended packages.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> supports logging of package activities.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> offers an <emphasis role="strong">enhanced</emphasis> regex based search on all of the package metadata.
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara><literal>aptitude</literal> can manage multiple versions of packages without using <literal>/etc/apt/preferences</literal> and it is quite intuitive.
+ </simpara>
+           </listitem>
+         </itemizedlist>
+         <note>
+           <simpara>Although the <literal>aptitude</literal> command comes with rich features such as its enhanced package resolver, this complexity has caused (or may still causes) some regressions such as <ulink url="http://bugs.debian.org/411123">Bug #411123</ulink>, <ulink url="http://bugs.debian.org/514930">Bug #514930</ulink>, and <ulink url="http://bugs.debian.org/570377">Bug #570377</ulink>.  In case of doubt, please use the <literal>apt-get</literal> and <literal>apt-cache</literal> commands over the <literal>aptitude</literal> command.</simpara>
+         </note>
+       </section>
+       <section id="_basic_package_management_operations_with_the_commandline">
+         <title>Basic package management operations with the commandline</title>
+         <simpara>Here are basic package management operations with the commandline using <literal>aptitude</literal>(8) and <literal>apt-get</literal>(8) /<literal>apt-cache</literal>(8).</simpara>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-           <title>Basic package management operations with commandline using <literal>aptitude</literal>(8) and <literal>apt-get</literal>(8) /<literal>apt-cache</literal>(8)</title>
+           <title>Basic package management operations with the commandline using <literal>aptitude</literal>(8) and <literal>apt-get</literal>(8) /<literal>apt-cache</literal>(8)</title>
            <tgroup cols="3">
              <colspec colwidth="146pt" align="left"/>
              <colspec colwidth="179pt" align="left"/>
-Line 5654 
 $ mc</screen>
+Line 5738 
 $ mc</screen>
              </tbody>
            </tgroup>
          </table>
-         <simpara>Although it is now safe to mix different package tools on the Debian system, it is best to continue using <literal>aptitude</literal> as much as possible.</simpara>
+         <note>
+           <simpara>Since <literal>apt-get</literal> and <literal>aptitude</literal> share auto-installed package status (see <xref linkend="_the_package_state_for_apt"/>) after <literal>lenny</literal>, you can mix these tools without major troubles (see <ulink url="http://bugs.debian.org/594490">Bug #594490</ulink>).</simpara>
+         </note>
          <simpara>The difference between "<literal>safe-upgrade</literal>"/"<literal>upgrade</literal>" and "<literal>full-upgrade</literal>"/"<literal>dist-upgrade</literal>" only appears when new versions of packages stand in different dependency relationships from old versions of those packages.  The "<literal>aptitude safe-upgrade</literal>" command does not install new packages nor remove installed packages.</simpara>
          <simpara>The "<literal>aptitude why &lt;regex&gt;</literal>" can list more information by "<literal>aptitude -v why &lt;regex&gt;</literal>".  Similar information can be obtained by "<literal>apt-cache rdepends &lt;package&gt;</literal>".</simpara>
          <simpara>When <literal>aptitude</literal> command is started in the commandline mode and faces some issues such as package conflicts, you can switch to the full screen interactive mode by pressing "<literal>e</literal>"-key later at the prompt.</simpara>
-Line 6031 
 The candidate version of the package
+Line 6117 
 The candidate version of the package
                    <literal>Upgradable Packages</literal>
                  </entry>
                  <entry>
-     list packages organized as <literal>section</literal> → <literal>component</literal> → <literal>package</literal>
+     list packages organized as <literal>section</literal> → <literal>area</literal> → <literal>package</literal>
      </entry>
                </row>
                <row>
-Line 6519 
 The default relation type is "depends".
+Line 6605 
 The default relation type is "depends".
          </table>
          <simpara>In reality, it is not so easy to get meaningful understanding quickly out from these logs.  See <xref linkend="_recording_changes_in_configuration_files"/> for easier way.</simpara>
        </section>
-       <section id="_aptitude_advantages">
-         <title>Aptitude advantages</title>
-         <simpara>Aptitude has advantages over other APT based packaging systems (apt-get, apt-cache, synaptic, …).</simpara>
-         <itemizedlist>
-           <listitem>
-             <simpara><literal>aptitude</literal> removes unused auto installed packages automatically using its own extra layer of package state file (<literal>/var/lib/aptitude/pkgstates</literal>). (For new "<literal>lenny</literal>", other APT does the same.)
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>aptitude</literal> makes it easy to resolve package conflicts and to add recommended packages.
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>aptitude</literal> makes it easy to keep track of obsolete software by listing under "Obsolete and Locally Created Packages".
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>aptitude</literal> gives a log of its history in "<literal>/var/log/aptitude</literal>".
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>aptitude</literal> offers access to all versions of the package if available.
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>aptitude</literal> includes a fairly powerful regex based system for searching particular packages and limiting the package display.
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>aptitude</literal> in the full screen mode has <literal>su</literal> functionality embedded and can be run from normal user until you really need administrative privileges.
- </simpara>
-           </listitem>
-         </itemizedlist>
-         <simpara>For the old <literal>etch</literal> release version, <literal>synaptic</literal> also gives you the history log; <literal>apt-get</literal> did not but you can rely on the log of <literal>dpkg</literal>.</simpara>
-         <simpara>Anyway, <literal>aptitude</literal> is nice for interactive console use.</simpara>
-       </section>
      </section>
      <section id="_examples_of_aptitude_operations">
        <title>Examples of aptitude operations</title>
-Line 6645 
 Start "<literal>apt-get autoremove|less<
+Line 6695 
 Start "<literal>apt-get autoremove|less<
          </orderedlist>
          <simpara>The "<literal>m</literal>" action over "<literal>Tasks</literal>" is an optional one to prevent mass package removal situation in future.</simpara>
        </section>
-       <section id="_system_wide_upgrade_with_aptitude">
+       <section id="_system_wide_upgrade">
-         <title>System wide upgrade with aptitude</title>
+         <title>System wide upgrade</title>
          <note>
            <simpara>When moving to a new release etc, you should consider to perform a clean installation of new system even though Debian is upgradable as described below.  This provides you a chance to remove garbages collected and exposes you to the best combination of latest packages.  Of course, you should make a full backup of system to a safe place (see <xref linkend="_backup_and_recovery"/>) before doing this. I recommend to make a dual boot configuration using different partition to have the smoothest transition.</simpara>
          </note>
-         <simpara>You can perform system wide upgrade to a newer release by changing contents of the "<literal>/etc/apt/sources.list</literal>" file pointing to a new release and running the "<literal>aptitude update; aptitude full-upgrade</literal>" command.</simpara>
+         <simpara>You can perform system wide upgrade to a newer release by changing contents of the "<literal>/etc/apt/sources.list</literal>" file pointing to a new release and running the "<literal>apt-get update; apt-get dist-upgrade</literal>" command.</simpara>
          <simpara>To upgrade from <literal>stable</literal> to <literal>testing</literal> or <literal>unstable</literal>, you replace "<literal>@-@codename-stable@-@</literal>" in the "<literal>/etc/apt/sources.list</literal>" example of <xref linkend="_debian_archive_basics"/> with "<literal>@-@codename-testing@-@</literal>" or "<literal>sid</literal>".</simpara>
          <simpara>In reality, you may face some complications due to some package transition issues, mostly due to package dependencies.  The larger the difference of the upgrade, the more likely you face larger troubles.  For the transition from the old <literal>stable</literal> to the new <literal>stable</literal> after its release, you can read its new <ulink url="http://www.debian.org/releases/stable/releasenotes">Release Notes</ulink> and follow the exact procedure described in it to minimize troubles.</simpara>
          <simpara>When you decide to move from <literal>stable</literal> to <literal>testing</literal> before its formal release, there are no <ulink url="http://www.debian.org/releases/stable/releasenotes">Release Notes</ulink> to help you. The difference between <literal>stable</literal> and <literal>testing</literal> could have grown quite large after the previous <literal>stable</literal> release and makes upgrade situation complicated.</simpara>
-Line 6713 
 Install, optionally, new <emphasis role=
+Line 6763 
 Install, optionally, new <emphasis role=
            </listitem>
            <listitem>
              <simpara>
- Run the "<literal>aptitude full-upgrade -s</literal>" command to assess impact.
+ Run the "<literal>apt-get -s dist-upgrade</literal>" command to assess impact.
  </simpara>
            </listitem>
            <listitem>
              <simpara>
- Run the "<literal>aptitude full-upgrade</literal>" command at last.
+ Run the "<literal>apt-get dist-upgrade</literal>" command at last.
  </simpara>
            </listitem>
          </orderedlist>
-Line 6893 
 Run the "<literal>aptitude full-upgrade<
+Line 6943 
 Run the "<literal>aptitude full-upgrade<
                    <literal>dpkg-source -x &lt;package_name&gt;_&lt;version&gt;-&lt;debian_version&gt;.dsc</literal>
                  </entry>
                  <entry>
-     build a source tree from a set of source packages ("<literal>*.tar.gz</literal>" and "<literal>*.diff.gz</literal>")
+     build a source tree from a set of source packages ("<literal>*.orig.tar.gz</literal>" and "<literal>*.debian.tar.gz</literal>"/"<literal>*.diff.gz</literal>")
      </entry>
                </row>
                <row>
-Line 6952 
 Run the "<literal>aptitude full-upgrade<
+Line 7002 
 Run the "<literal>aptitude full-upgrade<
      set <literal>dpkg</literal> level package selection state information
      </entry>
                </row>
+               <row>
+                 <entry>
+                   <literal>echo &lt;package_name&gt; hold | dpkg --set-selection</literal>
+                 </entry>
+                 <entry>
+     set <literal>dpkg</literal> level package selection state for a package to <emphasis role="strong">hold</emphasis>  (equivalent to "<literal>aptitude hold &lt;package_name&gt;</literal>")
+     </entry>
+               </row>
              </tbody>
            </tgroup>
          </table>
-Line 7006 
 See <xref linkend="_making_debian_packag
+Line 7064 
 See <xref linkend="_making_debian_packag
  </simpara>
            </listitem>
          </itemizedlist>
-         <tip>
-           <simpara>The source package format described here as a set of source packages ("<literal>*.tar.gz</literal>" and "<literal>*.diff.gz</literal>") is format 1.0 which is still popular.  See more on <literal>dpkg-source</literal>(1) for other newer formats.</simpara>
-         </tip>
        </section>
        <section id="_verification_of_installed_package_files">
          <title>Verification of installed package files</title>
-Line 7042 
 See <xref linkend="_making_debian_packag
+Line 7097 
 See <xref linkend="_making_debian_packag
            <title>The content of the Debian archive meta data</title>
            <tgroup cols="3">
              <colspec colwidth="141pt" align="left"/>
-             <colspec colwidth="363pt" align="left"/>
+             <colspec colwidth="336pt" align="left"/>
              <colspec colwidth="244pt" align="left"/>
              <thead>
                <row>
-Line 7096 
 See <xref linkend="_making_debian_packag
+Line 7151 
 See <xref linkend="_making_debian_packag
                    <literal>Release</literal>
                  </entry>
                  <entry>
-     top of each distribution/component/architecture combination
+     top of each distribution/area/architecture combination
      </entry>
                  <entry>
      archive description used for the rule of <literal>apt_preferences</literal>(5)
-Line 7107 
 See <xref linkend="_making_debian_packag
+Line 7162 
 See <xref linkend="_making_debian_packag
                    <literal>Packages</literal>
                  </entry>
                  <entry>
-     top of each distribution/component/binary-architecture combination
+     top of each distribution/area/binary-architecture combination
      </entry>
                  <entry>
      concatenated <literal>debian/control</literal> for binary packages
-Line 7118 
 See <xref linkend="_making_debian_packag
+Line 7173 
 See <xref linkend="_making_debian_packag
                    <literal>Sources</literal>
                  </entry>
                  <entry>
-     top of each distribution/component/source combination
+     top of each distribution/area/source combination
      </entry>
                  <entry>
      concatenated <literal>debian/control</literal> for source packages
-Line 7148 
 MD5Sum:
+Line 7203 
 MD5Sum:
 d07f7fa21b10f472c426db66168  6561398 main/binary-alpha/Packages.gz
  ...</screen>
          <note>
-           <simpara>Here, you can find my rationale to use the "suite", "codeneme", and "components" in <xref linkend="_debian_archive_basics"/>.  The "distribution" is used when referring to both "suite" and "codeneme".</simpara>
+           <simpara>Here, you can find my rationale to use the "suite", and "codeneme" in <xref linkend="_debian_archive_basics"/>.  The "distribution" is used when referring to both "suite" and "codeneme".  All archive "area" names offered by the archive are listed under "Component".</simpara>
          </note>
          <simpara>The integrity of the top level "<literal>Release</literal>" file is verified by cryptographic infrastructure called the <ulink url="http://wiki.debian.org/SecureApt">secure apt</ulink>.</simpara>
          <itemizedlist>
-Line 7208 
 Architecture: amd64</screen>
+Line 7263 
 Architecture: amd64</screen>
        </section>
        <section id="_fetching_of_the_meta_data_for_the_package">
          <title>Fetching of the meta data for the package</title>
-         <simpara>When APT tools, such as <literal>aptitude</literal>, <literal>apt-get</literal>, <literal>synaptic</literal>, <literal>apt-file</literal>, <literal>auto-apt</literal>…, are used, we need to update the local copies of the meta data containing the Debian archive information. These local copies have following file names corresponding to the specified <literal>distribution</literal>, <literal>component</literal>, and <literal>architecture</literal> names in the "<literal>/etc/apt/sources.list</literal>" (see <xref linkend="_debian_archive_basics"/>).</simpara>
+         <simpara>When APT tools, such as <literal>aptitude</literal>, <literal>apt-get</literal>, <literal>synaptic</literal>, <literal>apt-file</literal>, <literal>auto-apt</literal>…, are used, we need to update the local copies of the meta data containing the Debian archive information. These local copies have following file names corresponding to the specified <literal>distribution</literal>, <literal>area</literal>, and <literal>architecture</literal> names in the "<literal>/etc/apt/sources.list</literal>" (see <xref linkend="_debian_archive_basics"/>).</simpara>
          <itemizedlist>
            <listitem>
              <simpara>
-Line 7222 
 Architecture: amd64</screen>
+Line 7277 
 Architecture: amd64</screen>
            </listitem>
            <listitem>
              <simpara>
- "<literal>/var/lib/apt/lists/ftp.us.debian.org_debian_dists_&lt;distribution&gt;_&lt;component&gt;_binary-&lt;architecture&gt;_Packages</literal>"
+ "<literal>/var/lib/apt/lists/ftp.us.debian.org_debian_dists_&lt;distribution&gt;_&lt;area&gt;_binary-&lt;architecture&gt;_Packages</literal>"
  </simpara>
            </listitem>
            <listitem>
              <simpara>
- "<literal>/var/lib/apt/lists/ftp.us.debian.org_debian_dists_&lt;distribution&gt;_&lt;component&gt;_source_Sources</literal>"
+ "<literal>/var/lib/apt/lists/ftp.us.debian.org_debian_dists_&lt;distribution&gt;_&lt;area&gt;_source_Sources</literal>"
  </simpara>
            </listitem>
            <listitem>
-Line 7259 
 Architecture: amd64</screen>
+Line 7314 
 Architecture: amd64</screen>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
            <title>The name structure of Debian packages</title>
            <tgroup cols="2">
-             <colspec colwidth="309pt" align="left"/>
+             <colspec colwidth="271pt" align="left"/>
-             <colspec colwidth="439pt" align="left"/>
+             <colspec colwidth="401pt" align="left"/>
              <thead>
                <row>
                  <entry>
-Line 7274 
 Architecture: amd64</screen>
+Line 7329 
 Architecture: amd64</screen>
              <tbody>
                <row>
                  <entry>
-     The binary package (a.k.a deb)
+     The binary package (a.k.a <literal>deb</literal>)
      </entry>
                  <entry>
                    <literal>&lt;package-name&gt;_&lt;epoch&gt;:&lt;upstream-version&gt;-&lt;debian.version&gt;-&lt;architecture&gt;.deb</literal>
-Line 7282 
 Architecture: amd64</screen>
+Line 7337 
 Architecture: amd64</screen>
                </row>
                <row>
                  <entry>
-     The binary package for the debian-installer (a.k.a udeb)
+     The binary package (a.k.a <literal>udeb</literal>)
      </entry>
                  <entry>
                    <literal>&lt;package-name&gt;_&lt;epoch&gt;:&lt;upstream-version&gt;-&lt;debian.version&gt;-&lt;architecture&gt;.udeb</literal>
-Line 7293 
 Architecture: amd64</screen>
+Line 7348 
 Architecture: amd64</screen>
      The source package (upstream source)
      </entry>
                  <entry>
-                   <literal>&lt;package-name&gt;_&lt;epoch&gt;:&lt;upstream-version&gt;-&lt;debian.version&gt;.tar.gz</literal>
+                   <literal>&lt;package-name&gt;_&lt;epoch&gt;:&lt;upstream-version&gt;-&lt;debian.version&gt;.orig.tar.gz</literal>
                  </entry>
                </row>
                <row>
                  <entry>
-     The source package (Debian changes)
+     The <literal>1.0</literal> source package (Debian changes)
      </entry>
                  <entry>
                    <literal>&lt;package-name&gt;_&lt;epoch&gt;:&lt;upstream-version&gt;-&lt;debian.version&gt;.diff.gz</literal>
-Line 7306 
 Architecture: amd64</screen>
+Line 7361 
 Architecture: amd64</screen>
                </row>
                <row>
                  <entry>
+     The <literal>3.0 (quilt)</literal> source package (Debian changes)
+     </entry>
+                 <entry>
+                   <literal>&lt;package-name&gt;_&lt;epoch&gt;:&lt;upstream-version&gt;-&lt;debian.version&gt;.debian.tar.gz</literal>
+                 </entry>
+               </row>
+               <row>
+                 <entry>
      The source package (description)
      </entry>
                  <entry>
-Line 7315 
 Architecture: amd64</screen>
+Line 7378 
 Architecture: amd64</screen>
              </tbody>
            </tgroup>
          </table>
+         <tip>
+           <simpara>Here only the basic source package formats are described.  See more on <literal>dpkg-source</literal>(1).</simpara>
+         </tip>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
            <title>The usable characters for each component in the Debian package names</title>
            <tgroup cols="3">
-Line 7872 
 C++ <ulink url="http://en.wikipedia.org/
+Line 7938 
 C++ <ulink url="http://en.wikipedia.org/
        </section>
        <section id="_tweaking_candidate_version">
          <title>Tweaking candidate version</title>
-         <warning>
-           <simpara>In <literal>lenny</literal>, <literal>aptitude</literal>(8) has a bug for handling "<literal>/etc/apt/preferences</literal>" file. (<ulink url="http://bugs.debian.org/514930">Bug#514930</ulink>)</simpara>
-         </warning>
          <simpara>Without the "<literal>/etc/apt/preferences</literal>" file, APT system choses the latest available version as the <emphasis role="strong">candidate version</emphasis> using the version string.  This is the normal state and most recommended usage of APT system.  All officially supported combinations of archives do not require the "<literal>/etc/apt/preferences</literal>" file since some archives which should not be used as the automatic source of upgrades are marked as <emphasis role="strong">NotAutomatic</emphasis> and dealt properly.</simpara>
          <tip>
            <simpara>The version string comparison rule can be verified with, e.g., "<literal>dpkg  --compare-versions ver1.1 gt ver1.1~1; echo $?</literal>" (see <literal>dpkg</literal>(1)).</simpara>
-Line 7983 
 The Pin-Priority value associated just w
+Line 8046 
 The Pin-Priority value associated just w
            </listitem>
            <listitem>
              <simpara>
- The Pin-Priority values of archives (defined as "<literal>Package: *</literal>" in the "<literal>/etc/apt/preferences</literal>" file) are listed left side of all archive paths, e.g., "<literal>200 http://backports.org etch-backports/main Packages</literal>".
+ The Pin-Priority values of archives (defined as "<literal>Package: *</literal>" in the "<literal>/etc/apt/preferences</literal>" file) are listed left side of all archive paths, e.g., "<literal>200 http://backports.debian.org/debian-backports/ @-@codename-stable@-@-backports/main Packages</literal>".
  </simpara>
            </listitem>
          </itemizedlist>
-Line 8001 
 Pin: release a=unstable
+Line 8064 
 Pin: release a=unstable
  Pin-Priority: 200</screen>
          <simpara>When you wish to install a package named "<literal>&lt;package-name&gt;</literal>" with its dependencies from <literal>unstable</literal> archive under this configuration, you issue the following command which switches target release with "<literal>-t</literal>" option (Pin-Priority of <literal>unstable</literal> becomes 990.).</simpara>
          <screen>$ sudo apt-get install -t unstable &lt;package-name&gt;</screen>
-         <simpara>With this configuration, usual execution of "<literal>apt-get upgrade</literal>" and "<literal>apt-get dist-upgrade</literal>" (or "<literal>aptitude safe-upgrade</literal>" and "<literal>aptitude full-upgrade</literal>" for <literal>squeeze</literal>) upgrades packages which were installed from <literal>testing</literal> archive using current <literal>testing</literal> archive and packages which were installed from <literal>unstable</literal> archive using current <literal>unstable</literal> archive.</simpara>
+         <simpara>With this configuration, usual execution of "<literal>apt-get upgrade</literal>" and "<literal>apt-get dist-upgrade</literal>" (or "<literal>aptitude safe-upgrade</literal>" and "<literal>aptitude full-upgrade</literal>") upgrades packages which were installed from <literal>testing</literal> archive using current <literal>testing</literal> archive and packages which were installed from <literal>unstable</literal> archive using current <literal>unstable</literal> archive.</simpara>
          <caution>
            <simpara>Be careful not to remove "<literal>testing</literal>" entry from the "<literal>/etc/apt/sources.list</literal>" file.  Without "<literal>testing</literal>" entry in it, APT system upgrades packages using newer <literal>unstable</literal> archive.</simpara>
          </caution>
-Line 8036 
 deb http://ftp.us.debian.org/debian/ exp
+Line 8099 
 deb http://ftp.us.debian.org/debian/ exp
  deb http://security.debian.org/ testing/updates main contrib</screen>
          <simpara>The default Pin-Priority value for <literal>experimental</literal> archive is always 1 (&lt;&lt;100) since it is <emphasis role="strong">NotAutomatic</emphasis> archive (see <xref linkend="_archive_level_release_files"/>).  There is no need to set Pin-Priority value explicitly in the "<literal>/etc/apt/preferences</literal>" file just to use <literal>experimental</literal> archive unless you wish to track particular packages in it automatically for next upgrading.</simpara>
        </section>
-       <section id="_volatile_and_backports_org">
+       <section id="_volatile_and_backports">
-         <title>Volatile and Backports.org</title>
+         <title>Volatile and Backports</title>
-         <simpara>There are <ulink url="http://www.debian.org/volatile/">debian-volatile project</ulink> and <ulink url="http://backports.org">backports.org</ulink> archives which provide updgrade packages for <literal>stable</literal>.</simpara>
+         <simpara>There are <ulink url="http://www.debian.org/volatile/">debian-volatile project</ulink> and <ulink url="http://backports.debian.org">backports.debian.org</ulink> archives which provide updgrade packages for <literal>stable</literal>.</simpara>
          <warning>
            <simpara>Do not use all packages available in the <emphasis role="strong">NotAutomatic</emphasis> archives such as <literal>@-@codename-stable@-@-backports</literal> and <literal>volatile-sloppy</literal>.  Use only selected packages which fits your needs.</simpara>
          </warning>
          <caution>
-           <simpara><ulink url="http://backports.org">backports.org</ulink> is a non-Debian archive, although its packages are signed by Debian developers.</simpara>
-         </caution>
-         <caution>
            <simpara>Archive level Release files (see <xref linkend="_archive_level_release_files"/>) are used for the rule of <literal>apt_preferences</literal>(5).  Thus apt-pinning works only with "code" name for <ulink url="http://volatile.debian.org/debian-volatile/dists/">volatile Debian archives</ulink>. This is different from other Debian archives.  For example, you can do "<literal>Pin: release a=@-@codename-stable@-@</literal>" but can not do "<literal>Pin: release a=stable</literal>" in the "<literal>/etc/apt/preferences</literal>" file for volatile Debian archives.</simpara>
          </caution>
          <simpara>Here is an example of <emphasis role="strong">apt-pinning</emphasis> technique to include specific newer upstream version packages found in <literal>@-@codename-stable@-@-backports</literal> while tracking <literal>@-@codename-stable@-@</literal> and <literal>volatile</literal>.  You list all required archives in the "<literal>/etc/apt/sources.list</literal>" file as the following.</simpara>
-Line 8053 
 deb http://security.debian.org/ testing/
+Line 8113 
 deb http://security.debian.org/ testing/
  deb http://security.debian.org/ @-@codename-stable@-@/updates main contrib
  deb http://volatile.debian.org/debian-volatile/ @-@codename-stable@-@/volatile main contrib non-free
  deb http://volatile.debian.org/debian-volatile/ @-@codename-stable@-@/volatile-sloppy main contrib non-free
- deb http://backports.org/debian/ @-@codename-stable@-@-backports main contrib non-free</screen>
+ deb http://backports.debian.org/debian-backports/ @-@codename-stable@-@-backports main contrib non-free</screen>
-         <simpara>The default Pin-Priority value for <ulink url="http://backports.org">backports.org</ulink> and <literal>volatile-sloppy</literal> archives are always 1 (&lt;&lt;100) since they are <emphasis role="strong">NotAutomatic</emphasis> archive (see <xref linkend="_archive_level_release_files"/>).  There is no need to set Pin-Priority value explicitly in the "<literal>/etc/apt/preferences</literal>" file just to use for <ulink url="http://backports.org">backports.org</ulink> and <literal>volatile-sloppy</literal> archive unless you wish to track packages automatically for next upgrading.</simpara>
+         <simpara>The default Pin-Priority value for <ulink url="http://backports.debian.org">backports.debian.org</ulink> and <literal>volatile-sloppy</literal> archives are always 1 (&lt;&lt;100) since they are <emphasis role="strong">NotAutomatic</emphasis> archive (see <xref linkend="_archive_level_release_files"/>).  There is no need to set Pin-Priority value explicitly in the "<literal>/etc/apt/preferences</literal>" file just to use for <ulink url="http://backports.debian.org">backports.debian.org</ulink> and <literal>volatile-sloppy</literal> archive unless you wish to track packages automatically for next upgrading.</simpara>
          <simpara>So whenever you wish to install a package named "<literal>&lt;package-name&gt;</literal>" with its dependency from <literal>@-@codename-stable@-@-backports</literal> archive, you use following command while switching target release with "<literal>-t</literal>" option.</simpara>
          <screen>$ sudo apt-get install -t @-@codename-stable@-@-backports &lt;package-name&gt;</screen>
          <simpara>If you wish to upgrade particular packages, you must create the "<literal>/etc/apt/preferences</literal>" file and explicitly lists all packages in it as the following.</simpara>
-Line 8081 
 Pin-Priority: 200
+Line 8141 
 Pin-Priority: 200
  Package: *
  Pin: release a=@-@codename-stable@-@-sloppy, o=volatile.debian.org
  Pin-Priority: 200</screen>
-         <simpara>Execution of "<literal>apt-get upgrade</literal>" and "<literal>apt-get dist-upgrade</literal>" (or "<literal>aptitude safe-upgrade</literal>" and "<literal>aptitude full-upgrade</literal>" for <literal>squeeze</literal>) upgrades packages which were installed from <literal>stable</literal> archive using current <literal>stable</literal> archive and packages which were installed from other archives using current corresponding archive for all archives in the "<literal>/etc/apt/sources.list</literal>" file.</simpara>
+         <simpara>Execution of "<literal>apt-get upgrade</literal>" and "<literal>apt-get dist-upgrade</literal>" (or "<literal>aptitude safe-upgrade</literal>" and "<literal>aptitude full-upgrade</literal>") upgrades packages which were installed from <literal>stable</literal> archive using current <literal>stable</literal> archive and packages which were installed from other archives using current corresponding archive for all archives in the "<literal>/etc/apt/sources.list</literal>" file.</simpara>
        </section>
        <section id="_automatic_download_and_upgrade_of_packages">
          <title>Automatic download and upgrade of packages</title>
-Line 8567 
 The kernel code of the target OS if it f
+Line 8627 
 The kernel code of the target OS if it f
                  <ulink url="http://en.wikipedia.org/wiki/GNU_GRUB">GRUB Legacy</ulink>
                </entry>
                <entry>
-     grub
+     grub-legacy
      </entry>
                <entry>
      @-@popcon2@-@
-Line 9224 
 The Debian system goes into one of the s
+Line 9284 
 The Debian system goes into one of the s
            <simpara><emphasis role="strong">The Debian system does not pre-assign any special meaning differences among the <ulink url="http://en.wikipedia.org/wiki/Runlevel">runlevels</ulink> between 2 and 5.</emphasis> The system administrator on the Debian system may change this.  (I.e., Debian is not <ulink url="http://en.wikipedia.org/wiki/Red_Hat_Linux">Red Hat Linux</ulink> nor <ulink url="http://en.wikipedia.org/wiki/Solaris_(operating_system)">Solaris by Sun Microsystems</ulink> nor <ulink url="http://en.wikipedia.org/wiki/HP-UX">HP-UX by Hewlett Packard</ulink> nor <ulink url="http://en.wikipedia.org/wiki/IBM_AIX">AIX by IBM</ulink> nor …)</simpara>
          </caution>
          <caution>
-           <simpara>The Debian system does not populate directories for the <ulink url="http://en.wikipedia.org/wiki/Runlevel">runlevels</ulink> between 7 and 9 when the package is installed.  Traditional <ulink url="http://en.wikipedia.org/wiki/Unix-like">Unix variants</ulink> don’t use these <ulink url="http://en.wikipedia.org/wiki/Runlevel">runlevels</ulink>.</simpara>
+           <simpara>The Debian system does not populate directories for the <ulink url="http://en.wikipedia.org/wiki/Runlevel">runlevels</ulink> between 7 and 9 when the package is installed.  Traditional <ulink url="http://en.wikipedia.org/wiki/Unix-like">Unix variants</ulink> don't use these <ulink url="http://en.wikipedia.org/wiki/Runlevel">runlevels</ulink>.</simpara>
          </caution>
        </section>
        <section id="_the_configuration_of_the_runlevel">
          <title>The configuration of the runlevel</title>
+         <note>
+           <simpara>In Debian <literal>squeeze</literal>, dependency based boot order provided by the <literal>insserv</literal> package is used instead of classical alphabetical one.  The "<literal>CONCURRENCY</literal>" value in "<literal>/etc/default/rcS</literal>" controls its concurrency: "<literal>none</literal>" for no concurrency, "<literal>startpar</literal>" for concurrency within the same sequence number, or "<literal>makefile</literal>" for full concurrency.  See "<literal>/usr/share/doc/insserv/README.Debian</literal>".</simpara>
+         </note>
          <simpara>The name of the symlink in each runlevel directory has the form "<literal>S&lt;2-digit-number&gt;&lt;original-name&gt;</literal>" or "<literal>K&lt;2-digit-number&gt;&lt;original-name&gt;</literal>". The 2-digit-number is used to determine the order in which to run the scripts. "<literal>S</literal>" is for "Start" and "<literal>K</literal>" is for "Kill".</simpara>
-         <simpara>When <literal>init</literal>(8) or <literal>telinit</literal>(8) commands goes into the runlevel to "&lt;n&gt;", it execute following scripts.</simpara>
+         <simpara>For "<literal>CONCURRENCY=none</literal>", when <literal>init</literal>(8) or <literal>telinit</literal>(8) commands goes into the runlevel to "&lt;n&gt;", it execute following scripts.</simpara>
          <orderedlist>
            <listitem>
              <simpara>
-Line 9244 
 The script names starting with an "<lite
+Line 9307 
 The script names starting with an "<lite
            </listitem>
          </orderedlist>
          <simpara>For example, if you had the links "<literal>S10sysklogd</literal>" and "<literal>S20exim4</literal>" in a runlevel directory, "<literal>S10sysklogd</literal>" which is symlinked to "<literal>../init.d/sysklogd</literal>" would run before "<literal>S20exim4</literal>" which is symlinked to "<literal>../init.d/exim4</literal>".</simpara>
+         <simpara>For "<literal>CONCURRENCY=makefile</literal>" (new default), package dependency defined in the header of init scripts are used to order them.</simpara>
          <warning>
            <simpara>It is not advisable to make any changes to symlinks in "<literal>/etc/rcS.d/</literal>" unless you know better than the maintainer.</simpara>
          </warning>
-         <note>
-           <simpara>In Debian <literal>squeeze</literal>, dependency based boot order provided by the <literal>insserv</literal> package is used instead of classical alphabetical one.  The "<literal>CONCURRENCY</literal>" value in "<literal>/etc/default/rcS</literal>" controls its concurrency: "<literal>none</literal>" for no concurrency, "<literal>startpar</literal>" for concurrency within the same sequence number, or "<literal>makefile</literal>" for full concurrency.  See "<literal>/usr/share/doc/insserv/README.Debian</literal>".</simpara>
-         </note>
        </section>
        <section id="_the_runlevel_management_example">
          <title>The runlevel management example</title>
-Line 10726 
 Reboot system.
+Line 10787 
 Reboot system.
      <tip>
        <simpara>For general guide to the GNU/Linux networking, read the <ulink url="http://www.tldp.org/LDP/nag2/">Linux Network Administrators Guide</ulink>.</simpara>
      </tip>
-     <simpara>The traditional <ulink url="http://en.wikipedia.org/wiki/Internet_Protocol_Suite">TCP/IP network</ulink> setup on Debian system uses <literal>ifupdown</literal> package as a high level tool.  There are 2 typical cases.</simpara>
-     <itemizedlist>
-       <listitem>
-         <simpara>
- For <emphasis role="strong">dynamic IP</emphasis> system such as mobile PCs, you should setup TCP/IP network <emphasis role="strong">with</emphasis> the <literal>resolvconf</literal> package and enable you to switch your network configuration easily (see <xref linkend="_the_network_interface_served_by_the_dhcp"/>).
- </simpara>
-       </listitem>
-       <listitem>
-         <simpara>
- For <emphasis role="strong">static IP</emphasis> system such as servers, you should setup TCP/IP network <emphasis role="strong">without</emphasis> the <literal>resolvconf</literal> package and keep your system simple (see <xref linkend="_the_network_interface_with_the_static_ip"/>).
- </simpara>
-       </listitem>
-     </itemizedlist>
-     <simpara>We describe these traditional cases in detail here.</simpara>
-     <simpara>We also touch on some alternative high level tools such as <literal>network-manager</literal> and <literal>wicd</literal> which ease configuration of wireless networks (see <xref linkend="_automatic_network_configuration"/>).</simpara>
      <section id="_the_basic_network_infrastructure">
        <title>The basic network infrastructure</title>
        <simpara>Let's review the basic network infrastructure on the modern Debian system.</simpara>
-       <section id="_the_domain_name">
+       <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-         <title>The domain name</title>
+         <title>List of network configuration tools</title>
-         <simpara>The naming for the domain name is a tricky one for the normal PC workstation users.  The PC workstation may be mobile one hopping around the network or located behind the NAT firewall inaccessible from the Internet. For such case, you may not want the domain name to be a valid domain name to avoid name collision.</simpara>
+         <tgroup cols="5">
-         <simpara>According to <ulink url="http://tools.ietf.org/html/rfc2606">rfc2606</ulink>, "<literal>invalid</literal>" seems to be a choice for the <ulink url="http://en.wikipedia.org/wiki/Top-level_domain">top level domain (TLD)</ulink> to construct domain names that are sure to be invalid from the Internet.</simpara>
+           <colspec colwidth="130pt" align="left"/>
-         <simpara>The <ulink url="http://en.wikipedia.org/wiki/MDNS">mDNS</ulink> network discovery protocol (<ulink url="http://en.wikipedia.org/wiki/Bonjour_(software)">Apple Bonjour / Apple Rendezvous</ulink>, Avahi on Debian) uses <ulink url="http://en.wikipedia.org/wiki/.local">"local"</ulink> as the <ulink url="http://en.wikipedia.org/wiki/Pseudo-top-level_domain">pseudo-top-level domain</ulink>.  <ulink url="http://support.microsoft.com/kb/296250">Microsoft also seems to promote "local" for the TLD of local area network</ulink>.</simpara>
+           <colspec colwidth="76pt" align="left"/>
-         <warning>
+           <colspec colwidth="70pt" align="left"/>
-           <simpara>If the DNS service on your LAN uses "<literal>local</literal>" as TLD for your LAN, it may interfare with mDNS.</simpara>
+           <colspec colwidth="97pt" align="left"/>
-         </warning>
+           <colspec colwidth="374pt" align="left"/>
-         <simpara>Other popular choices for the invalid TLD seem to be "<literal>localdomain</literal>", "<literal>lan</literal>", "<literal>localnet</literal>", or "<literal>home</literal>" according to my incoming mail analysis.</simpara>
+           <thead>
-       </section>
+             <row>
-       <section id="_the_hostname_resolution">
+               <entry>
-         <title>The hostname resolution</title>
-         <simpara>The hostname resolution is currently supported by the <ulink url="http://en.wikipedia.org/wiki/Name_Service_Switch">NSS (Name Service Switch)</ulink> mechanism too.  The flow of this resolution is the following.</simpara>
-         <orderedlist>
-           <listitem>
-             <simpara>
- The "<literal>/etc/nsswitch.conf</literal>" file with stanza like "<literal>hosts: files dns</literal>" dictates the hostname resolution order. (This replaces the old functionality of the "<literal>order</literal>" stanza in "<literal>/etc/host.conf</literal>".)
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara>
- The <literal>files</literal> method is invoked first.  If the hostname is found in the "<literal>/etc/hosts</literal>" file, it returns all valid addresses for it and exits. (The "<literal>/etc/host.conf</literal>" file contains "<literal>multi on</literal>".)
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara>
- The <literal>dns</literal> method is invoked.  If the hostname is found by the query to the <ulink url="http://en.wikipedia.org/wiki/Domain_Name_System">Internet Domain Name System (DNS)</ulink> identified by the "<literal>/etc/resolv.conf</literal>" file, it returns all valid addresses for it and exits.
- </simpara>
-           </listitem>
-         </orderedlist>
-         <simpara>The "<literal>/etc/hosts</literal>" file <ulink url="http://bugs.debian.org/316099">associates IP addresses with hostnames</ulink> contains the following.</simpara>
-         <screen>127.0.0.1 localhost
-.0.1.1 &lt;host_name&gt;.&lt;domain_name&gt; &lt;host_name&gt;
- # The following lines are desirable for IPv6 capable hosts
- ::1     ip6-localhost ip6-loopback
- fe00::0 ip6-localnet
- ff00::0 ip6-mcastprefix
- ff02::1 ip6-allnodes
- ff02::2 ip6-allrouters
- ff02::3 ip6-allhosts</screen>
-         <simpara>Here the &lt;host_name&gt; in this matches the own hostname defined in the "<literal>/etc/hostname</literal>".  The &lt;domain_name&gt; in this is the <ulink url="http://en.wikipedia.org/wiki/FQDN">fully qualified domain name (FQDN)</ulink> of this host.</simpara>
-         <tip>
-           <simpara>For &lt;domain_name&gt; of the mobile PC without the real FQDN, you may pick a bogus and safe TLD such as "<literal>lan</literal>", "<literal>home</literal>", "<literal>invalid</literal>", "<literal>localdomain</literal>", "<literal>none</literal>", and "<literal>private</literal>".</simpara>
-         </tip>
-         <simpara>The "<literal>/etc/resolv.conf</literal>" is a static file if the <literal>resolvconf</literal> package is not installed.  If installed, it is a symbolic link.  Either way, it contains information that initialize the resolver routines. If the DNS is found at IP="<literal>192.168.11.1</literal>", it contains the following.</simpara>
-         <screen>nameserver 192.168.11.1</screen>
-         <simpara>The <literal>resolvconf</literal> package makes this "<literal>/etc/resolv.conf</literal>" into a symbolic link and manages its contents by the hook scripts automatically.</simpara>
-         <simpara>The hostname resolution via Multicast DNS (using <ulink url="http://en.wikipedia.org/wiki/Zeroconf">Zeroconf</ulink>, aka <ulink url="http://en.wikipedia.org/wiki/Bonjour_(software)">Apple Bonjour / Apple Rendezvous</ulink>) which effectively allows name resolution by common Unix/Linux programs in the ad-hoc mDNS domain "<literal>local</literal>", can be provided by installing the <literal>libnss-mdns</literal> package.  The "<literal>/etc/nsswitch.conf</literal>" file should have stanza like "<literal>hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4</literal>" to enable this functionality.</simpara>
-       </section>
-       <section id="_the_network_interface_name">
-         <title>The network interface name</title>
-         <simpara>The network interface name, e.g. <literal>eth0</literal>, is assigned to each hardware in the Linux kernel through the user space configuration mechanism, <literal>udev</literal> (see <xref linkend="_the_udev_system"/>), as it is found.  The network interface name is referred as <emphasis role="strong">physical interface</emphasis> in <literal>ifup</literal>(8) and <literal>interfaces</literal>(5).</simpara>
-         <simpara>In order to ensure each network interface to be named persistently for each reboot using <ulink url="http://en.wikipedia.org/wiki/MAC_address">MAC address</ulink> etc., there is a record file "<literal>/etc/udev/rules.d/70-persistent-net.rules</literal>".  This file is automatically generated by the "<literal>/lib/udev/write_net_rules</literal>" program, probably run by the "<literal>persistent-net-generator.rules</literal>" rules file. You can modify it to change naming rule.</simpara>
-         <caution>
-           <simpara>When editing the "<literal>/etc/udev/rules.d/70-persistent-net.rules</literal>" rules file, you must keep each rule on a single line and the <ulink url="http://en.wikipedia.org/wiki/MAC_address">MAC address</ulink> in lowercase. For example, if you find "Firewire device" and "PCI device" in this file, you probably want to name "PCI device" as <literal>eth0</literal> and configure it as the primary network interface.</simpara>
-         </caution>
-       </section>
-       <section id="_the_network_address_range_for_the_lan">
-         <title>The network address range for the LAN</title>
-         <simpara>Let us be reminded of the IPv4 32 bit address ranges in each class reserved for use on the <ulink url="http://en.wikipedia.org/wiki/Local_area_network">local area networks (LANs)</ulink> by <ulink url="http://tools.ietf.org/html/rfc1918">rfc1918</ulink>.  These addresses are guaranteed not to conflict with any addresses on the Internet proper.</simpara>
-         <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-           <title>List of network address ranges</title>
-           <tgroup cols="5">
-             <colspec colwidth="32pt" align="left"/>
-             <colspec colwidth="157pt" align="left"/>
-             <colspec colwidth="76pt" align="left"/>
-             <colspec colwidth="81pt" align="left"/>
-             <colspec colwidth="70pt" align="left"/>
-             <thead>
-               <row>
-                 <entry>
-     Class
-     </entry>
-                 <entry>
-     network addresses
-     </entry>
-                 <entry>
-     net mask
-     </entry>
-                 <entry>
-     net mask /bits
-     </entry>
-                 <entry>
-     # of subnets
-     </entry>
-               </row>
-             </thead>
-             <tbody>
-               <row>
-                 <entry>
-     A
-     </entry>
-                 <entry>
-.x.x.x
-     </entry>
-                 <entry>
-.0.0.0
-     </entry>
-                 <entry>
-     /8
-     </entry>
-                 <entry>
-     </entry>
-               </row>
-               <row>
-                 <entry>
-     B
-     </entry>
-                 <entry>
-.16.x.x — 172.31.x.x
-     </entry>
-                 <entry>
-.255.0.0
-     </entry>
-                 <entry>
-     /16
-     </entry>
-                 <entry>
-     </entry>
-               </row>
-               <row>
-                 <entry>
-     C
-     </entry>
-                 <entry>
-.168.0.x — 192.168.255.x
-     </entry>
-                 <entry>
-.255.255.0
-     </entry>
-                 <entry>
-     /24
-     </entry>
-                 <entry>
-     </entry>
-               </row>
-             </tbody>
-           </tgroup>
-         </table>
-         <note>
-           <simpara>If one of these addresses is assigned to a host, then that host must not access the Internet directly but must access it through a gateway that acts as a proxy for individual services or else does <ulink url="http://en.wikipedia.org/wiki/Network_address_translation">Network Address Translation(NAT)</ulink>.  The broadband router usually performs NAT for the consumer LAN environment.</simpara>
-         </note>
-       </section>
-       <section id="_the_network_configuration_infrastructure">
-         <title>The network configuration infrastructure</title>
-         <simpara>There are 2 types of low level networking programs for Linux networking system (see <xref linkend="_iproute2_commands"/>).</simpara>
-         <itemizedlist>
-           <listitem>
-             <simpara>
- Old <ulink url="http://www.linuxfoundation.org/en/Net:Net-tools">net-tools</ulink> programs (<literal>ifconfig</literal>(8), …) are from the Linux NET-3 networking system. Most of these are obsolete now.
- </simpara>
-           </listitem>
-           <listitem>
-             <simpara>
- New <ulink url="http://www.linuxfoundation.org/en/Net:Iproute2">Linux iproute2</ulink> programs (<literal>ip</literal>(8), …) are the current Linux networking system.
- </simpara>
-           </listitem>
-         </itemizedlist>
-         <simpara>Although these low level networking programs are powerful, they are cumbersome to use.  So high level network configuration systems have been created.</simpara>
-         <simpara>The <literal>ifupdown</literal> package is the de facto standard for such high level network configuration system on Debian.  It enables you to bring up network simply by doing , e.g., "<literal>ifup eth0</literal>".  Its configuration file is the "<literal>/etc/network/interfaces</literal>" file and its typical contents are the following.</simpara>
-         <screen>auto lo
- iface lo inet loopback
- auto eth0
- iface eth0 inet dhcp</screen>
-         <simpara>The <literal>resolvconf</literal> package was created to supplement <literal>ifupdown</literal> system to support smooth reconfiguration of network address resolution by automating rewrite of resolver configuration file "<literal>/etc/resolv.conf</literal>".  Now, most Debian network configuration packages are modified to use <literal>resolvconf</literal> package (see "<literal>/usr/share/doc/resolvconf/README.Debian</literal>").</simpara>
-         <simpara>Helper scripts to the <literal>ifupdown</literal> package such as <literal>ifplugd</literal>, <literal>guessnet</literal>, <literal>ifscheme</literal>, etc. are created to automate dynamic configuration of network environment such as one for mobile PC on wired LAN.  These are relatively difficult to use but play well with existing <literal>ifupdown</literal> system.</simpara>
-         <simpara>Alternative high level network configuration systems, independent of <literal>ifupdown</literal> system, such as <literal>network-manager</literal>, <literal>wicd</literal>, etc. are created to ease configuration of network environment even for mobile PC on wireless network.  Since these are relatively new system and their integration to Debian system is in progress, you may still need to disable the corresponding network interface configuration manually in "<literal>/etc/network/interfaces</literal>" to avoid conflicts between these and <literal>ifupdown</literal> (see <xref linkend="_automatic_network_configuration"/>).</simpara>
-         <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-           <title>List of network configuration tools</title>
-           <tgroup cols="5">
-             <colspec colwidth="130pt" align="left"/>
-             <colspec colwidth="76pt" align="left"/>
-             <colspec colwidth="70pt" align="left"/>
-             <colspec colwidth="97pt" align="left"/>
-             <colspec colwidth="374pt" align="left"/>
-             <thead>
-               <row>
-                 <entry>
      packages
      </entry>
-                 <entry>
+               <entry>
      popcon
      </entry>
-                 <entry>
+               <entry>
      size
      </entry>
-                 <entry>
+               <entry>
      type
      </entry>
-                 <entry>
+               <entry>
      description
      </entry>
-               </row>
+             </row>
-             </thead>
+           </thead>
-             <tbody>
+           <tbody>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifupdown</literal>
+                 <literal>ifupdown</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      config::ifupdown
      </entry>
-                 <entry>
+               <entry>
      standardized tool to bring up and down the network (Debian specific)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifplugd</literal>
+                 <literal>ifplugd</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      manage the wired network automatically
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifupdown-extra</literal>
+                 <literal>ifupdown-extra</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network testing script to enhance "<literal>ifupdown</literal>" package
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifmetric</literal>
+                 <literal>ifmetric</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      set routing metrics for a network interface
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>guessnet</literal>
+                 <literal>guessnet</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      mapping script to enhance "<literal>ifupdown</literal>" package via "<literal>/etc/network/interfaces</literal>" file
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifscheme</literal>
+                 <literal>ifscheme</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      mapping scripts to enhance "<literal>ifupdown</literal>" package
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifupdown-scripts-zg2</literal>
+                 <literal>ifupdown-scripts-zg2</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      Zugschlus' interface scripts for ifupdown's manual method
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>network-manager</literal>
+                 <literal>network-manager</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      config::NM
      </entry>
-                 <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (daemon): manage the network automatically
+               <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (daemon): manage the network automatically
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>network-manager-gnome</literal>
+                 <literal>network-manager-gnome</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (GNOME frontend)
+               <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (GNOME frontend)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>network-manager-kde</literal>
+                 <literal>network-manager-kde</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (KDE frontend)
+               <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (KDE frontend)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>wicd</literal>
+                 <literal>cnetworkmanager</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
+     , ,
+     </entry>
+               <entry><ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> (command-line client)
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>wicd</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
      config::wicd
      </entry>
-                 <entry>
+               <entry>
-     wired and wireless network manager
+     wired and wireless network manager (metapackage)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>iptables</literal>
+                 <literal>wicd-cli</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     wired and wireless network manager (command-line client)
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>wicd-curses</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     wired and wireless network manager (Curses client)
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>wicd-daemon</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     wired and wireless network manager (daemon)
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>wicd-gtk</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     wired and wireless network manager (GTK+ client)
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>iptables</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
      config::Netfilter
      </entry>
-                 <entry>
+               <entry>
      administration tools for packet filtering and NAT (<ulink url="http://en.wikipedia.org/wiki/Netfilter">Netfilter</ulink>)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>iproute</literal>
+                 <literal>iproute</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      config::iproute2
      </entry>
-                 <entry><ulink url="http://www.linuxfoundation.org/en/Net:Iproute2">iproute2</ulink>, IPv6 and other advanced network configuration: <literal>ip</literal>(8), <literal>tc</literal>(8), etc
+               <entry><ulink url="http://www.linuxfoundation.org/en/Net:Iproute2">iproute2</ulink>, IPv6 and other advanced network configuration: <literal>ip</literal>(8), <literal>tc</literal>(8), etc
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ifrename</literal>
+                 <literal>ifrename</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      rename network interfaces based on various static criteria: <literal>ifrename</literal>(8)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ethtool</literal>
+                 <literal>ethtool</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      display or change Ethernet device settings
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>iputils-ping</literal>
+                 <literal>iputils-ping</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      test::iproute2
      </entry>
-                 <entry>
+               <entry>
      test network reachability of a remote host by <ulink url="http://en.wikipedia.org/wiki/Hostname">hostname</ulink> or <ulink url="http://en.wikipedia.org/wiki/IP_address">IP address</ulink> (<ulink url="http://www.linuxfoundation.org/en/Net:Iproute2">iproute2</ulink>)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>iputils-arping</literal>
+                 <literal>iputils-arping</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      test network reachability of a remote host specified by the <ulink url="http://en.wikipedia.org/wiki/Address_Resolution_Protocol">ARP</ulink> address
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>iputils-tracepath</literal>
+                 <literal>iputils-tracepath</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      trace the network path to a remote host
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>net-tools</literal>
+                 <literal>net-tools</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      config::net-tools
      </entry>
-                 <entry>
+               <entry>
      NET-3 networking toolkit (<ulink url="http://www.linuxfoundation.org/en/Net:Net-tools">net-tools</ulink>, IPv4 network configuration):  <literal>ifconfig</literal>(8) etc.
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>inetutils-ping</literal>
+                 <literal>inetutils-ping</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      test::net-tools
      </entry>
-                 <entry>
+               <entry>
      test network reachability of a remote host by <ulink url="http://en.wikipedia.org/wiki/Hostname">hostname</ulink> or <ulink url="http://en.wikipedia.org/wiki/IP_address">IP address</ulink> (legacy, GNU)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>arping</literal>
+                 <literal>arping</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      test network reachability of a remote host specified by the <ulink url="http://en.wikipedia.org/wiki/Address_Resolution_Protocol">ARP</ulink> address (legacy)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>traceroute</literal>
+                 <literal>traceroute</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      trace the network path to a remote host (legacy, console)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>dhcp3-client</literal>
+                 <literal>dhcp3-client</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      config::low-level
      </entry>
-                 <entry>
+               <entry>
      DHCP client
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>wpasupplicant</literal>
+                 <literal>wpasupplicant</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      client support for WPA and WPA2 (IEEE 802.11i)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>wireless-tools</literal>
+                 <literal>wireless-tools</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      tools for manipulating Linux Wireless Extensions
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>ppp</literal>
+                 <literal>ppp</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      PPP/PPPoE connection with <literal>chat</literal>
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>pppoeconf</literal>
+                 <literal>pppoeconf</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      config::helper
      </entry>
-                 <entry>
+               <entry>
      configuration helper for PPPoE connection
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>pppconfig</literal>
+                 <literal>pppconfig</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      configuration helper for PPP connection with <literal>chat</literal>
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>wvdial</literal>
+                 <literal>wvdial</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      configuration helper for PPP connection with <literal>wvdial</literal> and <literal>ppp</literal>
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>mtr-tiny</literal>
+                 <literal>mtr-tiny</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      test::low-level
      </entry>
-                 <entry>
+               <entry>
      trace the network path to a remote host (curses)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>mtr</literal>
+                 <literal>mtr</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      trace the network path to a remote host (curses and GTK+)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>gnome-nettool</literal>
+                 <literal>gnome-nettool</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      tools for common network information operations (GNOME)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>nmap</literal>
+                 <literal>nmap</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network mapper / port scanner (<ulink url="http://en.wikipedia.org/wiki/Nmap">Nmap</ulink>, console)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>zenmap</literal>
+                 <literal>zenmap</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network mapper / port scanner (GTK+)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>knmap</literal>
+                 <literal>knmap</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network mapper / port scanner (KDE)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>tcpdump</literal>
+                 <literal>tcpdump</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network traffic analyzer (<ulink url="http://en.wikipedia.org/wiki/Tcpdump">Tcpdump</ulink>, console)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>wireshark</literal>
+                 <literal>wireshark</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network traffic analyzer (<ulink url="http://en.wikipedia.org/wiki/Wireshark">Wireshark</ulink>, GTK+)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>tshark</literal>
+                 <literal>tshark</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      network traffic analyzer (console)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>nagios3</literal>
+                 <literal>nagios3</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      monitoring and management system for hosts, services and networks (<ulink url="http://en.wikipedia.org/wiki/Nagios">Nagios</ulink>)
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>tcptrace</literal>
+                 <literal>tcptrace</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      produce a summarization of the connections from <literal>tcpdump</literal> output
      </entry>
-               </row>
+             </row>
-               <row>
+             <row>
-                 <entry>
+               <entry>
-                   <literal>snort</literal>
+                 <literal>snort</literal>
-                 </entry>
+               </entry>
-                 <entry>
+               <entry>
      @-@popcon1@-@
      </entry>
-                 <entry>
+               <entry>
      @-@psize1@-@
      </entry>
-                 <entry>
+               <entry>
      , ,
      </entry>
-                 <entry>
+               <entry>
      flexible network intrusion detection system (<ulink url="http://en.wikipedia.org/wiki/Snort_(software)">Snort</ulink>)
      </entry>
-               </row>
+             </row>
+             <row>
+               <entry>
+                 <literal>ntop</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     display network usage in web browser
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>dnsutils</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     network clients provided with <ulink url="http://en.wikipedia.org/wiki/BIND">BIND</ulink>: <literal>nslookup</literal>(8), <literal>nsupdate</literal>(8), <literal>dig</literal>(8)
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>dlint</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     check <ulink url="http://en.wikipedia.org/wiki/Domain_Name_System">DNS</ulink> zone information using nameserver lookups
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>dnstracer</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
+     trace a chain of <ulink url="http://en.wikipedia.org/wiki/Domain_Name_System">DNS</ulink> servers to the source
+     </entry>
+             </row>
+           </tbody>
+         </tgroup>
+       </table>
+       <section id="_the_domain_name">
+         <title>The domain name</title>
+         <simpara>The naming for the domain name is a tricky one for the normal PC workstation users.  The PC workstation may be mobile one hopping around the network or located behind the NAT firewall inaccessible from the Internet. For such case, you may not want the domain name to be a valid domain name to avoid name collision.</simpara>
+         <tip>
+           <simpara>When you use an invalid domain name, you need to spoof the domain name used by some programs such as MTA for their proper operation.  See <xref linkend="_the_mail_address_configuration"/>.</simpara>
+         </tip>
+         <simpara>According to <ulink url="http://tools.ietf.org/html/rfc2606">rfc2606</ulink>, "<literal>invalid</literal>" seems to be a choice for the <ulink url="http://en.wikipedia.org/wiki/Top-level_domain">top level domain (TLD)</ulink> to construct domain names that are sure to be invalid from the Internet.</simpara>
+         <simpara>The <ulink url="http://en.wikipedia.org/wiki/MDNS">mDNS</ulink> network discovery protocol (<ulink url="http://en.wikipedia.org/wiki/Bonjour_(software)">Apple Bonjour / Apple Rendezvous</ulink>, Avahi on Debian) uses <ulink url="http://en.wikipedia.org/wiki/.local">"local"</ulink> as the <ulink url="http://en.wikipedia.org/wiki/Pseudo-top-level_domain">pseudo-top-level domain</ulink>.  <ulink url="http://support.microsoft.com/kb/296250">Microsoft also seems to promote "local" for the TLD of local area network</ulink>.</simpara>
+         <warning>
+           <simpara>If the DNS service on your LAN uses "<literal>local</literal>" as TLD for your LAN, it may interfare with mDNS.</simpara>
+         </warning>
+         <simpara>Other popular choices for the invalid TLD seem to be "<literal>localdomain</literal>", "<literal>lan</literal>", "<literal>localnet</literal>", or "<literal>home</literal>" according to my incoming mail analysis.</simpara>
+       </section>
+       <section id="_the_hostname_resolution">
+         <title>The hostname resolution</title>
+         <simpara>The hostname resolution is currently supported by the <ulink url="http://en.wikipedia.org/wiki/Name_Service_Switch">NSS (Name Service Switch)</ulink> mechanism too.  The flow of this resolution is the following.</simpara>
+         <orderedlist>
+           <listitem>
+             <simpara>
+ The "<literal>/etc/nsswitch.conf</literal>" file with stanza like "<literal>hosts: files dns</literal>" dictates the hostname resolution order. (This replaces the old functionality of the "<literal>order</literal>" stanza in "<literal>/etc/host.conf</literal>".)
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara>
+ The <literal>files</literal> method is invoked first.  If the hostname is found in the "<literal>/etc/hosts</literal>" file, it returns all valid addresses for it and exits. (The "<literal>/etc/host.conf</literal>" file contains "<literal>multi on</literal>".)
+ </simpara>
+           </listitem>
+           <listitem>
+             <simpara>
+ The <literal>dns</literal> method is invoked.  If the hostname is found by the query to the <ulink url="http://en.wikipedia.org/wiki/Domain_Name_System">Internet Domain Name System (DNS)</ulink> identified by the "<literal>/etc/resolv.conf</literal>" file, it returns all valid addresses for it and exits.
+ </simpara>
+           </listitem>
+         </orderedlist>
+         <simpara>The "<literal>/etc/hosts</literal>" file <ulink url="http://bugs.debian.org/316099">associates IP addresses with hostnames</ulink> contains the following.</simpara>
+         <screen>127.0.0.1 localhost
+.0.1.1 &lt;host_name&gt;.&lt;domain_name&gt; &lt;host_name&gt;
+ # The following lines are desirable for IPv6 capable hosts
+ ::1     ip6-localhost ip6-loopback
+ fe00::0 ip6-localnet
+ ff00::0 ip6-mcastprefix
+ ff02::1 ip6-allnodes
+ ff02::2 ip6-allrouters
+ ff02::3 ip6-allhosts</screen>
+         <simpara>Here the &lt;host_name&gt; in this matches the own hostname defined in the "<literal>/etc/hostname</literal>".  The &lt;domain_name&gt; in this is the <ulink url="http://en.wikipedia.org/wiki/FQDN">fully qualified domain name (FQDN)</ulink> of this host.</simpara>
+         <tip>
+           <simpara>For &lt;domain_name&gt; of the mobile PC without the real FQDN, you may pick a bogus and safe TLD such as "<literal>lan</literal>", "<literal>home</literal>", "<literal>invalid</literal>", "<literal>localdomain</literal>", "<literal>none</literal>", and "<literal>private</literal>".</simpara>
+         </tip>
+         <simpara>The "<literal>/etc/resolv.conf</literal>" is a static file if the <literal>resolvconf</literal> package is not installed.  If installed, it is a symbolic link.  Either way, it contains information that initialize the resolver routines. If the DNS is found at IP="<literal>192.168.11.1</literal>", it contains the following.</simpara>
+         <screen>nameserver 192.168.11.1</screen>
+         <simpara>The <literal>resolvconf</literal> package makes this "<literal>/etc/resolv.conf</literal>" into a symbolic link and manages its contents by the hook scripts automatically.</simpara>
+         <simpara>The hostname resolution via Multicast DNS (using <ulink url="http://en.wikipedia.org/wiki/Zeroconf">Zeroconf</ulink>, aka <ulink url="http://en.wikipedia.org/wiki/Bonjour_(software)">Apple Bonjour / Apple Rendezvous</ulink>) which effectively allows name resolution by common Unix/Linux programs in the ad-hoc mDNS domain "<literal>local</literal>", can be provided by installing the <literal>libnss-mdns</literal> package.  The "<literal>/etc/nsswitch.conf</literal>" file should have stanza like "<literal>hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4</literal>" to enable this functionality.</simpara>
+       </section>
+       <section id="_the_network_interface_name">
+         <title>The network interface name</title>
+         <simpara>The network interface name, e.g. <literal>eth0</literal>, is assigned to each hardware in the Linux kernel through the user space configuration mechanism, <literal>udev</literal> (see <xref linkend="_the_udev_system"/>), as it is found.  The network interface name is referred as <emphasis role="strong">physical interface</emphasis> in <literal>ifup</literal>(8) and <literal>interfaces</literal>(5).</simpara>
+         <simpara>In order to ensure each network interface to be named persistently for each reboot using <ulink url="http://en.wikipedia.org/wiki/MAC_address">MAC address</ulink> etc., there is a record file "<literal>/etc/udev/rules.d/70-persistent-net.rules</literal>".  This file is automatically generated by the "<literal>/lib/udev/write_net_rules</literal>" program, probably run by the "<literal>persistent-net-generator.rules</literal>" rules file. You can modify it to change naming rule.</simpara>
+         <caution>
+           <simpara>When editing the "<literal>/etc/udev/rules.d/70-persistent-net.rules</literal>" rules file, you must keep each rule on a single line and the <ulink url="http://en.wikipedia.org/wiki/MAC_address">MAC address</ulink> in lowercase. For example, if you find "Firewire device" and "PCI device" in this file, you probably want to name "PCI device" as <literal>eth0</literal> and configure it as the primary network interface.</simpara>
+         </caution>
+       </section>
+       <section id="_the_network_address_range_for_the_lan">
+         <title>The network address range for the LAN</title>
+         <simpara>Let us be reminded of the IPv4 32 bit address ranges in each class reserved for use on the <ulink url="http://en.wikipedia.org/wiki/Local_area_network">local area networks (LANs)</ulink> by <ulink url="http://tools.ietf.org/html/rfc1918">rfc1918</ulink>.  These addresses are guaranteed not to conflict with any addresses on the Internet proper.</simpara>
+         <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
+           <title>List of network address ranges</title>
+           <tgroup cols="5">
+             <colspec colwidth="32pt" align="left"/>
+             <colspec colwidth="157pt" align="left"/>
+             <colspec colwidth="76pt" align="left"/>
+             <colspec colwidth="81pt" align="left"/>
+             <colspec colwidth="70pt" align="left"/>
+             <thead>
                <row>
                  <entry>
-                   <literal>ntop</literal>
+     Class
-                 </entry>
+     </entry>
                  <entry>
-     @-@popcon1@-@
+     network addresses
      </entry>
                  <entry>
-     @-@psize1@-@
+     net mask
      </entry>
                  <entry>
-     , ,
+     net mask /bits
      </entry>
                  <entry>
-     display network usage in web browser
+     # of subnets
      </entry>
                </row>
+             </thead>
+             <tbody>
                <row>
                  <entry>
-                   <literal>dnsutils</literal>
+     A
-                 </entry>
+     </entry>
                  <entry>
-     @-@popcon1@-@
+.x.x.x
      </entry>
                  <entry>
-     @-@psize1@-@
+.0.0.0
      </entry>
                  <entry>
-     , ,
+     /8
      </entry>
                  <entry>
-     network clients provided with <ulink url="http://en.wikipedia.org/wiki/BIND">BIND</ulink>: <literal>nslookup</literal>(8), <literal>nsupdate</literal>(8), <literal>dig</literal>(8)
      </entry>
                </row>
                <row>
                  <entry>
-                   <literal>dlint</literal>
+     B
-                 </entry>
+     </entry>
                  <entry>
-     @-@popcon1@-@
+.16.x.x — 172.31.x.x
      </entry>
                  <entry>
-     @-@psize1@-@
+.255.0.0
      </entry>
                  <entry>
-     , ,
+     /16
      </entry>
                  <entry>
-     check <ulink url="http://en.wikipedia.org/wiki/Domain_Name_System">DNS</ulink> zone information using nameserver lookups
      </entry>
                </row>
                <row>
                  <entry>
-                   <literal>dnstracer</literal>
+     C
-                 </entry>
+     </entry>
                  <entry>
-     @-@popcon1@-@
+.168.0.x — 192.168.255.x
      </entry>
                  <entry>
-     @-@psize1@-@
+.255.255.0
      </entry>
                  <entry>
-     , ,
+     /24
      </entry>
                  <entry>
-     trace a chain of <ulink url="http://en.wikipedia.org/wiki/Domain_Name_System">DNS</ulink> servers to the source
      </entry>
                </row>
              </tbody>
            </tgroup>
          </table>
+         <note>
+           <simpara>If one of these addresses is assigned to a host, then that host must not access the Internet directly but must access it through a gateway that acts as a proxy for individual services or else does <ulink url="http://en.wikipedia.org/wiki/Network_address_translation">Network Address Translation(NAT)</ulink>.  The broadband router usually performs NAT for the consumer LAN environment.</simpara>
+         </note>
        </section>
        <section id="_the_network_device_support">
          <title>The network device support</title>
          <simpara>Although most hardware devices are supported by the Debian system, there are some network devices which require <ulink url="http://www.debian.org/social_contract#guidelines">DSFG</ulink> non-free external hardware drivers to support them.  Please see <xref linkend="_non_free_hardware_drivers"/>.</simpara>
        </section>
      </section>
-     <section id="_the_network_connection_method">
+     <section id="_the_modern_network_configuration_for_desktop">
-       <title>The network connection method</title>
+       <title>The modern network configuration for desktop</title>
+       <simpara>Debian <literal>squeeze</literal> systems can manage the network connection via management <ulink url="http://en.wikipedia.org/wiki/Daemon_(computer_software)">daemon</ulink> software such as <ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager (NM)</ulink> (network-manager and associated packages) or <ulink url="http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)">Wicd</ulink> (wicd and associated packages).</simpara>
+       <itemizedlist>
+         <listitem>
+           <simpara>
+ They come with their own <ulink url="http://en.wikipedia.org/wiki/Graphical_user_interface">GUI</ulink> and command-line programs as their user interfaces.
+ </simpara>
+         </listitem>
+         <listitem>
+           <simpara>
+ They come with their own <ulink url="http://en.wikipedia.org/wiki/Daemon_(computer_software)">daemon</ulink> as their backend system.
+ </simpara>
+         </listitem>
+         <listitem>
+           <simpara>
+ They allow easy connection of your system to the Internet.
+ </simpara>
+         </listitem>
+         <listitem>
+           <simpara>
+ They allow easy management of wired and wireless network configuration.
+ </simpara>
+         </listitem>
+         <listitem>
+           <simpara>
+ They allow us to configure network independent of the legacy <literal>ifupdown</literal> package.
+ </simpara>
+         </listitem>
+       </itemizedlist>
+       <note>
+         <simpara>Do not use these automatic network configuration tools for servers.  These are aimed primarily for mobile desktop users on laptops.</simpara>
+       </note>
+       <simpara>These modern network configuration tools need to be configured properly to avoid conflicting with the legacy <literal>ifupdown</literal> package and its configuration file "<literal>/etc/network/interfaces</literal>".</simpara>
+       <note>
+         <simpara>Some features of these automatic network configuration tools may suffer regressions.  These are not as robust as the legacy <literal>ifupdown</literal> package.  Check <ulink url="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=network-manager">BTS of network-manager</ulink> and <ulink url="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=wicd">BTS of wicd</ulink> for current issues and limitations.</simpara>
+       </note>
+       <section id="_gui_network_configuration_tools">
+         <title>GUI network configuration tools</title>
+         <simpara>Official documentations for NM and Wicd on Debian are provided in "<literal>/usr/share/doc/network-manager/README.Debian</literal>" and "<literal>/usr/share/doc/wicd/README.Debian</literal>", respectively.</simpara>
+         <simpara>Essentially, the network configuration for desktop is done as follows.</simpara>
+         <orderedlist>
+           <listitem>
+             <simpara>
+ Make desktop user, e.g. <literal>foo</literal>, belong to group "<literal>netdev</literal>" by the following (Alternatively, do it automatically via <ulink url="http://en.wikipedia.org/wiki/D-Bus">D-bus</ulink> under modern desktop environments such as GNOME and KDE).
+ </simpara>
+             <screen>$ sudo adduser foo netdev</screen>
+           </listitem>
+           <listitem>
+             <simpara>
+ Keep configuration of "<literal>/etc/network/interfaces</literal>" as simple as the the following.
+ </simpara>
+             <screen>auto lo
+ iface lo inet loopback</screen>
+           </listitem>
+           <listitem>
+             <simpara>
+ Restart NM or Wicd by the following.
+ </simpara>
+             <screen>$ sudo /etc/init.d/network-manager restart</screen>
+             <screen>$ sudo /etc/init.d/wicd restart</screen>
+           </listitem>
+           <listitem>
+             <simpara>
+ Configure your network via GUI.
+ </simpara>
+           </listitem>
+         </orderedlist>
+         <note>
+           <simpara>Only interfaces which are <emphasis role="strong">not</emphasis> listed in "<literal>/etc/network/interfaces</literal>" or which have been configured with "<literal>auto …</literal>" or "<literal>allow-hotplug …</literal>" and "<literal>iface … inet dhcp</literal>" (with no other options) are managed by NM to avoid conflict with <literal>ifupdown</literal>.</simpara>
+         </note>
+         <tip>
+           <simpara>If you wish to extend network configuration capabilities of NM, please seek appropriate plug-in modules and supplemental packages such as <literal>network-manager-openconnect</literal>, <literal>network-manager-openvpn-gnome</literal>, <literal>network-manager-pptp-gnome</literal>, <literal>mobile-broadband-provider-info</literal>, <literal>gnome-bluetooth</literal>, etc.   The same goes for those of Wicd.</simpara>
+         </tip>
+         <caution>
+           <simpara>These automatic network configuration tools may not be compatible with esoteric configurations of legacy <literal>ifupdown</literal> in "<literal>/etc/network/interfaces</literal>" such as ones in <xref linkend="_the_basic_network_configuration_with_ifupdown_legacy"/> and <xref linkend="_the_advanced_network_configuration_with_ifupdown_legacy"/>.  Check <ulink url="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=network-manager">BTS of network-manager</ulink> and <ulink url="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=wicd">BTS of wicd</ulink> for current issues and limitations.</simpara>
+         </caution>
+       </section>
+     </section>
+     <section id="_the_legacy_network_connection_and_configuration">
+       <title>The legacy network connection and configuration</title>
+       <simpara>When the method described in <xref linkend="_the_modern_network_configuration_for_desktop"/> does not suffice your needs, you should use the legacy network connection and configuration method which combines many simpler tools.</simpara>
+       <simpara>The legacy network connection is specific for each method (see <xref linkend="_the_network_connection_method_legacy"/>).</simpara>
+       <simpara>There are 2 types of programs for the low level network configuration on Linux (see <xref linkend="_iproute2_commands"/>).</simpara>
+       <itemizedlist>
+         <listitem>
+           <simpara>
+ Old <ulink url="http://www.linuxfoundation.org/en/Net:Net-tools">net-tools</ulink> programs (<literal>ifconfig</literal>(8), …) are from the Linux NET-3 networking system. Most of these are obsolete now.
+ </simpara>
+         </listitem>
+         <listitem>
+           <simpara>
+ New <ulink url="http://www.linuxfoundation.org/en/Net:Iproute2">Linux iproute2</ulink> programs (<literal>ip</literal>(8), …) are the current Linux networking system.
+ </simpara>
+         </listitem>
+       </itemizedlist>
+       <simpara>Although these low level networking programs are powerful, they are cumbersome to use.  So high level network configuration systems have been created.</simpara>
+       <simpara>The <literal>ifupdown</literal> package is the de facto standard for such high level network configuration system on Debian.  It enables you to bring up network simply by doing , e.g., "<literal>ifup eth0</literal>".  Its configuration file is the "<literal>/etc/network/interfaces</literal>" file and its typical contents are the following.</simpara>
+       <screen>auto lo
+ iface lo inet loopback
+ auto eth0
+ iface eth0 inet dhcp</screen>
+       <simpara>The <literal>resolvconf</literal> package was created to supplement <literal>ifupdown</literal> system to support smooth reconfiguration of network address resolution by automating rewrite of resolver configuration file "<literal>/etc/resolv.conf</literal>".  Now, most Debian network configuration packages are modified to use <literal>resolvconf</literal> package (see "<literal>/usr/share/doc/resolvconf/README.Debian</literal>").</simpara>
+       <simpara>Helper scripts to the <literal>ifupdown</literal> package such as <literal>ifplugd</literal>, <literal>guessnet</literal>, <literal>ifscheme</literal>, etc. are created to automate dynamic configuration of network environment such as one for mobile PC on wired LAN.  These are relatively difficult to use but play well with existing <literal>ifupdown</literal> system.</simpara>
+       <simpara>These are explained in detail with examples (see <xref linkend="_the_basic_network_configuration_with_ifupdown_legacy"/> and <xref linkend="_the_advanced_network_configuration_with_ifupdown_legacy"/>).</simpara>
+     </section>
+     <section id="_the_network_connection_method_legacy">
+       <title>The network connection method (legacy)</title>
        <caution>
-         <simpara>The connection test method described in this section are meant for testing purposes.  It is not meant to be used directly for the daily network connection.  You are advised to use them via the <literal>ifupdown</literal> package (see <xref linkend="_the_basic_network_configuration_with_ifupdown"/>).</simpara>
+         <simpara>The connection test method described in this section are meant for testing purposes.  It is not meant to be used directly for the daily network connection.  You are advised to use them via NM, Wicd, or the <literal>ifupdown</literal> package (see <xref linkend="_the_modern_network_configuration_for_desktop"/> and <xref linkend="_the_basic_network_configuration_with_ifupdown_legacy"/>).</simpara>
        </caution>
        <simpara>The typical network connection method and connection path for a PC can be summarized as the following.</simpara>
        <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
-Line 12226 
 $ sudo /sbin/ifconfig eth0 down</screen>
+Line 12440 
 $ sudo /sbin/ifconfig eth0 down</screen>
          <simpara>See "<literal>/usr/share/doc/pppoeconf/README.Debian</literal>".</simpara>
        </section>
      </section>
-     <section id="_the_basic_network_configuration_with_ifupdown">
+     <section id="_the_basic_network_configuration_with_ifupdown_legacy">
-       <title>The basic network configuration with ifupdown</title>
+       <title>The basic network configuration with ifupdown (legacy)</title>
+       <simpara>The traditional <ulink url="http://en.wikipedia.org/wiki/Internet_Protocol_Suite">TCP/IP network</ulink> setup on Debian system uses <literal>ifupdown</literal> package as a high level tool.  There are 2 typical cases.</simpara>
+       <itemizedlist>
+         <listitem>
+           <simpara>
+ For <emphasis role="strong">dynamic IP</emphasis> system such as mobile PCs, you should setup TCP/IP network <emphasis role="strong">with</emphasis> the <literal>resolvconf</literal> package and enable you to switch your network configuration easily (see <xref linkend="_the_network_interface_served_by_the_dhcp"/>).
+ </simpara>
+         </listitem>
+         <listitem>
+           <simpara>
+ For <emphasis role="strong">static IP</emphasis> system such as servers, you should setup TCP/IP network <emphasis role="strong">without</emphasis> the <literal>resolvconf</literal> package and keep your system simple (see <xref linkend="_the_network_interface_with_the_static_ip"/>).
+ </simpara>
+         </listitem>
+       </itemizedlist>
+       <simpara>These traditional setup methods are quite useful if you wish to set up advanced configuration (see <xref linkend="_the_basic_network_configuration_with_ifupdown_legacy"/>).</simpara>
        <simpara>The <literal>ifupdown</literal> package provides the standardized framework for the high level network configuration in the Debian system. In this section, we learn the basic network configuration with <literal>ifupdown</literal> with simplified introduction and many typical examples.</simpara>
        <section id="_the_command_syntax_simplified">
          <title>The command syntax simplified</title>
-Line 12637 
 Record results in the "<literal>/var/log
+Line 12865 
 Record results in the "<literal>/var/log
          </tip>
        </section>
      </section>
-     <section id="_the_advanced_network_configuration_with_ifupdown">
+     <section id="_the_advanced_network_configuration_with_ifupdown_legacy">
-       <title>The advanced network configuration with ifupdown</title>
+       <title>The advanced network configuration with ifupdown (legacy)</title>
-       <simpara>The functionality of the <literal>ifupdown</literal> package can be improved beyond what was described in <xref linkend="_the_basic_network_configuration_with_ifupdown"/> with the advanced knowledge.</simpara>
+       <simpara>The functionality of the <literal>ifupdown</literal> package can be improved beyond what was described in <xref linkend="_the_basic_network_configuration_with_ifupdown_legacy"/> with the advanced knowledge.</simpara>
        <simpara>The functionalities described here are completely optional.  I, being lazy and minimalist, rarely bother to use these.</simpara>
        <caution>
-         <simpara>If you could not set up network connection by information in <xref linkend="_the_basic_network_configuration_with_ifupdown"/>, you make situation worse by using information below.</simpara>
+         <simpara>If you could not set up network connection by information in <xref linkend="_the_basic_network_configuration_with_ifupdown_legacy"/>, you make situation worse by using information below.</simpara>
        </caution>
        <section id="_the_ifplugd_package">
          <title>The ifplugd package</title>
-         <simpara>The <literal>ifplugd</literal> package is older automatic network configuration tool which can manage only Ethernet connections. This solves unplugged/replugged Ethernet cable issues for mobile PC etc.   If you have <ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> or <ulink url="http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)">Wicd</ulink> (see <xref linkend="_automatic_network_configuration"/>) installed, you do not need this package.</simpara>
+         <simpara>The <literal>ifplugd</literal> package is older automatic network configuration tool which can manage only Ethernet connections. This solves unplugged/replugged Ethernet cable issues for mobile PC etc.   If you have <ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager</ulink> or <ulink url="http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)">Wicd</ulink> (see <xref linkend="_the_modern_network_configuration_for_desktop"/>) installed, you do not need this package.</simpara>
          <simpara>This package runs <ulink url="http://en.wikipedia.org/wiki/Daemon_(computer_software)">daemon</ulink> and replaces <emphasis role="strong">auto</emphasis> or <emphasis role="strong">allow-hotplug</emphasis> functionalities (see <xref linkend="list-of-stanzas-in-eni"/>) and starts interfaces upon their connection to the network.</simpara>
          <simpara>Here is how to use the <literal>ifplugd</literal> package for the internal Ethernet port, e.g. <literal>eth0</literal>.</simpara>
          <orderedlist>
-Line 13095 
 Mapping choses the <emphasis role="stron
+Line 13323 
 Mapping choses the <emphasis role="stron
          </note>
        </section>
      </section>
-     <section id="_the_network_configuration_for_desktop">
-       <title>The network configuration for desktop</title>
-       <section id="_gui_network_configuration_tools">
-         <title>GUI network configuration tools</title>
-         <simpara>The capability of default GUI network configuration tools for each desktop environments such as GNOME tends to be limited to basic configurations such as static IP or DHCP.  They actually overwrite contents of "<literal>/etc/network/interfaces</literal>" file behind you. Please check how they change "<literal>/etc/network/interfaces</literal>" file by yourself.</simpara>
-         <caution>
-           <simpara>They may not understand complicated advanced configuration done manually in "<literal>/etc/network/interfaces</literal>" file.</simpara>
-         </caution>
-       </section>
-       <section id="_automatic_network_configuration">
-         <title>Automatic network configuration</title>
-         <simpara>There are independent automatic network configuration tools, such as <ulink url="http://en.wikipedia.org/wiki/NetworkManager">NetworkManager (NM)</ulink> (<literal>network-manager</literal> and associated packages) and <ulink url="http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)">Wicd</ulink> (<literal>wicd</literal> package) which manage network connection via <ulink url="http://en.wikipedia.org/wiki/Daemon_(computer_software)">daemon</ulink> independent of the <literal>ifupdown</literal> package. They allow easy management of wireless connections.  These come with its own nice GUI user interfaces.</simpara>
-         <warning>
-           <simpara>Do not use these automatic network configuration tools for servers.  These are aimed primarily for mobile desktop users on laptops.</simpara>
-         </warning>
-         <warning>
-           <simpara>These automatic network configuration tools are moving targets and documentation here is likely to be incorrect for <literal>squeeze</literal>.  So be warned.</simpara>
-         </warning>
-         <caution>
-           <simpara>These automatic network configuration tools may not be compatible with esoteric configurations of <literal>ifupdown</literal> in "<literal>/etc/network/interfaces</literal>" such as ones in <xref linkend="_the_basic_network_configuration_with_ifupdown"/> and <xref linkend="_the_advanced_network_configuration_with_ifupdown"/>.  Having even "<literal>hostname</literal>" stanza for DHCP controlled interface as described in <xref linkend="_the_network_interface_served_by_the_dhcp"/> caused NM to ignore such interface in <literal>lenny</literal>. Check <ulink url="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=network-manager">BTS of network-manager</ulink> and <ulink url="http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=wicd">BTS of wicd</ulink> for current issues and limitations.</simpara>
-         </caution>
-         <simpara>The configuration of NM is described in "<literal>/usr/share/doc/network-manager/README.Debian</literal>".  Essentially this is as follows.</simpara>
-         <orderedlist>
-           <listitem>
-             <simpara>
- Make desktop user, e.g. <literal>foo</literal>, belong to group "<literal>netdev</literal>" by the following.
- </simpara>
-             <screen>$ sudo adduser foo netdev</screen>
-           </listitem>
-           <listitem>
-             <simpara>
- Keep configuration of "<literal>/etc/network/interfaces</literal>" as simple as the the following.
- </simpara>
-             <screen>auto lo
- iface lo inet loopback
- auto eth0
- iface eth0 inet dhcp</screen>
-           </listitem>
-           <listitem>
-             <simpara>
- Restart NM by the following.
- </simpara>
-             <screen>$ sudo /etc/init.d/network-manager restart</screen>
-           </listitem>
-         </orderedlist>
-         <note>
-           <simpara>Only interfaces which are <emphasis role="strong">not</emphasis> listed in "<literal>/etc/network/interfaces</literal>" or which have been configured with "<literal>auto …</literal>" or "<literal>allow-hotplug …</literal>" and "<literal>iface … inet dhcp</literal>" (with no other options) are managed by NM to avoid conflict with <literal>ifupdown</literal>.</simpara>
-         </note>
-         <simpara>The configuration of <ulink url="http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)">Wicd</ulink> is described in "<literal>/usr/share/doc/wicd/README.Debian</literal>".  Essentially, this is as follows.</simpara>
-         <orderedlist>
-           <listitem>
-             <simpara>
- Make configuration in "<literal>/etc/network/interfaces</literal>" only as the following.
- </simpara>
-             <screen>auto lo
- iface lo inet loopback</screen>
-           </listitem>
-           <listitem>
-             <simpara>
- Restart Wicd as the following.
- </simpara>
-             <screen>$ sudo /etc/init.d/wicd restart</screen>
-           </listitem>
-         </orderedlist>
-       </section>
-     </section>
      <section id="_the_low_level_network_configuration">
        <title>The low level network configuration</title>
        <section id="_iproute2_commands">
-Line 14084 
 MSS = MTU - 60 for IPv6
+Line 14245 
 MSS = MTU - 60 for IPv6
  </simpara>
            </listitem>
          </itemizedlist>
-         <simpara>Debian offers many free browser plugin packages in the main component which can handle not only <ulink url="http://en.wikipedia.org/wiki/Java_(software_platform)">Java (software platform)</ulink> and <ulink url="http://en.wikipedia.org/wiki/Adobe_Flash">Flash</ulink> but also <ulink url="http://en.wikipedia.org/wiki/MPEG-1">MPEG</ulink>, <ulink url="http://en.wikipedia.org/wiki/MPEG-2">MPEG2</ulink>, <ulink url="http://en.wikipedia.org/wiki/MPEG-4">MPEG4</ulink>, <ulink url="http://en.wikipedia.org/wiki/DivX">DivX</ulink>, <ulink url="http://en.wikipedia.org/wiki/Windows_Media_Video">Windows Media Video (.wmv)</ulink>, <ulink url="http://en.wikipedia.org/wiki/QuickTime">QuickTime (.mov)</ulink>, <ulink url="http://en.wikipedia.org/wiki/MP3">MP3 (.mp3)</ulink>, <ulink url="http://en.wikipedia.org/wiki/Vorbis">Ogg/Vorbis</ulink> files, DVDs, VCDs, etc.  Debian also offers helper programs to install non-free browser plugin packages as contrib or non-free components.</simpara>
+         <simpara>Debian offers many free browser plugin packages in the main archive area which can handle not only <ulink url="http://en.wikipedia.org/wiki/Java_(software_platform)">Java (software platform)</ulink> and <ulink url="http://en.wikipedia.org/wiki/Adobe_Flash">Flash</ulink> but also <ulink url="http://en.wikipedia.org/wiki/MPEG-1">MPEG</ulink>, <ulink url="http://en.wikipedia.org/wiki/MPEG-2">MPEG2</ulink>, <ulink url="http://en.wikipedia.org/wiki/MPEG-4">MPEG4</ulink>, <ulink url="http://en.wikipedia.org/wiki/DivX">DivX</ulink>, <ulink url="http://en.wikipedia.org/wiki/Windows_Media_Video">Windows Media Video (.wmv)</ulink>, <ulink url="http://en.wikipedia.org/wiki/QuickTime">QuickTime (.mov)</ulink>, <ulink url="http://en.wikipedia.org/wiki/MP3">MP3 (.mp3)</ulink>, <ulink url="http://en.wikipedia.org/wiki/Vorbis">Ogg/Vorbis</ulink> files, DVDs, VCDs, etc.  Debian also offers helper programs to install non-free browser plugin packages as contrib or non-free archive area.</simpara>
          <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
            <title>List of browser plugin packages</title>
            <tgroup cols="5">
-Line 14105 
 MSS = MTU - 60 for IPv6
+Line 14266 
 MSS = MTU - 60 for IPv6
      size
      </entry>
                  <entry>
-     component
+     area
      </entry>
                  <entry>
      description
-Line 14149 
 MSS = MTU - 60 for IPv6
+Line 14310 
 MSS = MTU - 60 for IPv6
                </row>
                <row>
                  <entry>
-                   <literal>swfdec-mozilla</literal>
-                 </entry>
-                 <entry>
-     @-@popcon1@-@
-     </entry>
-                 <entry>
-     @-@psize1@-@
-     </entry>
-                 <entry>
-     main
-     </entry>
-                 <entry>
-     Flash plugin based on libswfdec
-     </entry>
-               </row>
-               <row>
-                 <entry>
                    <literal>mozilla-plugin-gnash</literal>
                  </entry>
                  <entry>
-Line 14285 
 MSS = MTU - 60 for IPv6
+Line 14429 
 MSS = MTU - 60 for IPv6
        <caution>
          <simpara>If you are to set up the mail server to exchange mail directly with the Internet, you should be better than reading this elementary document.</simpara>
        </caution>
+       <note>
+         <simpara>The following configuration examples are only valid for the typical mobile workstation on consumer grade Internet connections.</simpara>
+       </note>
        <section id="_modern_mail_service_basics">
          <title>Modern mail service basics</title>
-         <simpara>In order to contain spam (unwanted and unsolicited e-mail) problems, many ISPs which provide consumer grade Internet connection are implementing counter measures.</simpara>
+         <simpara>In order to contain spam (unwanted and unsolicited email) problems, many ISPs which provide consumer grade Internet connections are implementing counter measures.</simpara>
          <itemizedlist>
            <listitem>
              <simpara>
-Line 14326 
 The incoming mail is accessible at the T
+Line 14473 
 The incoming mail is accessible at the T
        <section id="_the_mail_configuration_strategy_for_workstation">
          <title>The mail configuration strategy for workstation</title>
          <simpara>The most simple mail configuration is that the mail is sent to the ISP's smarthost and received from ISP's POP3 server by the MUA (see <xref linkend="_mail_user_agent_mua"/>) itself. This type of configuration is popular with full featured GUI based MUA such as <literal>icedove</literal>(1), <literal>evolution</literal>(1), etc. If you need to filter mail by their types, you use MUA's filtering function. For this case, the local MTA (see <xref linkend="_mail_transport_agent_mta"/>) need to do local delivery only.</simpara>
-         <simpara>The alternative mail configuration is that the mail is sent via local MTA to the ISP's smarthost and received from ISP's POP3 by the mail retriever (see <xref linkend="_the_remote_mail_retrieval_and_forward_utility"/>) to the local mailbox.  If you need to filter mail by their types, you use MDA with filter (see <xref linkend="_mail_delivery_agent_mda_with_filter"/>) to filter mail into separate mailboxes.  This type of configuration is popular with simple console based MUA such as <literal>mutt</literal>(1), <literal>gnus</literal>(1), etc., although this is possible with any MUAs (see <xref linkend="_mail_user_agent_mua"/>). For this case, the local MTA (see <xref linkend="_mail_transport_agent_mta"/>) need to do both smarthost delivery and local delivery.</simpara>
+         <simpara>The alternative mail configuration is that the mail is sent via local MTA to the ISP's smarthost and received from ISP's POP3 by the mail retriever (see <xref linkend="_the_remote_mail_retrieval_and_forward_utility"/>) to the local mailbox.  If you need to filter mail by their types, you use MDA with filter (see <xref linkend="_mail_delivery_agent_mda_with_filter"/>) to filter mail into separate mailboxes.  This type of configuration is popular with simple console based MUA such as <literal>mutt</literal>(1), <literal>gnus</literal>(1), etc., although this is possible with any MUAs (see <xref linkend="_mail_user_agent_mua"/>). For this case, the local MTA (see <xref linkend="_mail_transport_agent_mta"/>) need to do both smarthost delivery and local delivery.  Since mobile workstation does not have valid FQDN, you must configure the local MTA to hide and spoof the real local mail name in outgoing mail to avoid mail delivery errors (see <xref linkend="_the_mail_address_configuration"/>).</simpara>
+         <tip>
+           <simpara>You may wish to configure MUA/MDA to use <ulink url="http://en.wikipedia.org/wiki/Maildir">Maildir</ulink> for storing email messages somewhere under your home directory.</simpara>
+         </tip>
        </section>
      </section>
      <section id="_mail_transport_agent_mta">
-Line 14687 
 The incoming mail is accessible at the T
+Line 14837 
 The incoming mail is accessible at the T
          <title>The configuration of exim4</title>
          <simpara>For the Internet mail via smarthost, you (re)configure <literal>exim4-*</literal> packages as the following.</simpara>
          <screen>$ sudo /etc/init.d/exim4 stop
- $ sudo dpkg-reconfigure exim4-conf</screen>
+ $ sudo dpkg-reconfigure exim4-config</screen>
-         <simpara>Chose "mail sent by smarthost; received via SMTP or fetchmail".</simpara>
+         <simpara>Select "mail sent by smarthost; received via SMTP or fetchmail" for "General type of mail configuration".</simpara>
+         <simpara>Set "System mail name:" to its default as the FQDN (see <xref linkend="_the_hostname_resolution"/>).</simpara>
+         <simpara>Set "IP-addresses to listen on for incoming SMTP connections:" to its default as "127.0.0.1 ; ::1".</simpara>
+         <simpara>Unset contents of "Other destinations for which mail is accepted:".</simpara>
+         <simpara>Unset contents of "Machines to relay mail for:".</simpara>
          <simpara>Set "IP address or host name of the outgoing smarthost:" to "smtp.hostname.dom:587".</simpara>
+         <simpara>Select "&lt;No&gt;" for "Hide local mail name in outgoing mail?". (Use "<literal>/etc/email-addresses</literal>" as in <xref linkend="_the_mail_address_configuration"/>, instead.)</simpara>
          <simpara>Reply to "Keep number of DNS-queries minimal (Dial-on-Demand)?" as one of the following.</simpara>
          <itemizedlist>
            <listitem>
-Line 14703 
 $ sudo dpkg-reconfigure exim4-conf</scre
+Line 14858 
 $ sudo dpkg-reconfigure exim4-conf</scre
  </simpara>
            </listitem>
          </itemizedlist>
-         <simpara>Create password entries for the smarthost by editing "<literal> /etc/exim4/passwd.client</literal>"</simpara>
+         <simpara>Set "Delivery method for local mail:" to "mbox format in /var/mail/".</simpara>
+         <simpara>Select "&lt;Yes&gt;" for "Split configuration into small files?:".</simpara>
+         <simpara>Create password entries for the smarthost by editing "<literal>/etc/exim4/passwd.client</literal>".</simpara>
          <screen>$ sudo vim /etc/exim4/passwd.client
   ...
  $ cat /etc/exim4/passwd.client
-Line 14728 
 smtp99.hostname.dom has address 123.234.
+Line 14885 
 smtp99.hostname.dom has address 123.234.
            <simpara>Local customization file "<literal>/etc/exim4/exim4.conf.localmacros</literal>" may be created to set MACROs.  For example, <ulink url="http://www.yahoo.com/">Yahoo</ulink>'s mail service is said to require "<literal>MAIN_TLS_ENABLE = true</literal>" and "<literal>AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS = yes</literal>" in it.</simpara>
          </tip>
          <tip>
-           <simpara>If you are looking for a light weight MTA that respects "<literal>/etc/aliases</literal>" for your laptop PC, you should consider to configure <literal>exim4</literal>(8) with "<literal>QUEUERUNNER='nodaemon'</literal>" etc. in "<literal>/etc/default/exim4</literal>".</simpara>
+           <simpara>If you are looking for a light weight MTA that respects "<literal>/etc/aliases</literal>" for your laptop PC, you should consider to configure <literal>exim4</literal>(8) with "<literal>QUEUERUNNER='queueonly'</literal>", "<literal>QUEUERUNNER='nodaemon'</literal>", etc. in "<literal>/etc/default/exim4</literal>".</simpara>
          </tip>
        </section>
        <section id="_the_configuration_of_postfix_with_sasl">
-Line 14878 
 $ sudo postmap hush:/etc/postfix/sasl_pa
+Line 15035 
 $ sudo postmap hush:/etc/postfix/sasl_pa
          <tip>
            <simpara>The contents of "<literal>/etc/mailname</literal>" is used by many non-MTA programs for their default behavior. For <literal>mutt</literal>, set "<literal>hostname</literal>" and "<literal>from</literal>" variables in <literal>~/muttrc</literal> file to override the <emphasis role="strong">mailname</emphasis> value.  For programs in the <literal>devscripts</literal> package, such as <literal>bts</literal>(1) and <literal>dch</literal>(1), export environment variables "<literal>$DEBFULLNAME</literal>" and "<literal>$DEBEMAIL</literal>" to override it.</simpara>
          </tip>
+         <tip>
+           <simpara>The <literal>popularity-contest</literal> package normally send mail from root account with FQDN.  You need to set <literal>MAILFROM</literal> in <literal>/etc/popularity-contest.conf</literal> as described in the <literal>/usr/share/popularity-contest/default.conf</literal> file.  Otherwise, your mail will be rejected by the smarthost SMTP server. Although this is tedious, this approach is safer than rewriting the source address for all mails from root by MTA and should be used for other daemons and cron scripts.</simpara>
+         </tip>
          <simpara>When setting the <emphasis role="strong">mailname</emphasis> to "<literal>hostname -f</literal>", the spoofing of the source mail address via MTA can be realized by the following.</simpara>
          <itemizedlist>
            <listitem>
-Line 14895 
 $ sudo postmap hush:/etc/postfix/sasl_pa
+Line 15055 
 $ sudo postmap hush:/etc/postfix/sasl_pa
          <screen># postmap hash:/etc/postfix/generic
  # postconf -e 'smtp_generic_maps = hash:/etc/postfix/generic'
  # postfix reload</screen>
-         <simpara>You check filters using the following.</simpara>
+         <simpara>You can test mail address configuration using the following.</simpara>
          <itemizedlist>
            <listitem>
              <simpara><literal>exim</literal>(8) with <literal>-brw, -bf, -bF, -bV, …</literal> options
-Line 15143 
 $ sudo postmap hush:/etc/postfix/sasl_pa
+Line 15303 
 $ sudo postmap hush:/etc/postfix/sasl_pa
        <section id="_basic_mua_8212_mutt">
          <title>Basic MUA  — Mutt</title>
          <simpara>Customize "<literal>~/.muttrc</literal>" as the following to use <literal>mutt</literal> as the mail user agent (MUA) in combination with <literal>vim</literal>.</simpara>
-         <screen># use visual mode and "gq" to reformat quotes
+         <screen>#
- set editor="vim -c 'set tw=72 et ft=mail'"
+ # User configuration file to override /etc/Muttrc
- #
- # header weeding taken from the manual (Sven's Draconian header weeding)
  #
- ignore *
+ # spoof source mail address
- unignore from: date subject to cc
+ set use_from
- unignore user-agent x-mailer
+ set hostname=example.dom
- hdr_order from subject to cc date user-agent x-mailer
+ set from="Name Surname &lt;username@example.dom&gt;"
- set hostname=spoof.example.org
+ set signature="~/.signature"
- set from="First Last &lt;username@example.org&gt;"
- ....</screen>
+ # vim: "gq" to reformat quotes
+ set editor="vim -c 'set tw=72 et ft=mail'"
+ # "mutt" goes to Inbox, while "mutt -y" lists mailboxes
+ set mbox_type=Maildir           # use qmail Maildir format for creating mbox
+ set mbox=~/Mail                 # keep all mail boxes in $HOME/Mail/
+ set spoolfile=+Inbox            # mail delivered to $HOME/Mail/Inbox
+ set record=+Outbox              # save fcc mail to $HOME/Mail/Outbox
+ set postponed=+Postponed        # keep postponed in $HOME/Mail/postponed
+ set move=no                     # do not move Inbox items to mbox
+ set quit=ask-yes                # do not quit by "q" only
+ set delete=yes                  # always delete w/o asking while exiting
+ set fcc_clear                   # store fcc as non encrypted
+ # Mailboxes in Maildir (automatic update)
+ mailboxes `cd ~/Mail; /bin/ls -1|sed -e 's/^/+/' | tr "\n" " "`
+ unmailboxes Maillog *.ev-summary
+ ## Default
+ #set index_format="%4C %Z %{%b %d} %-15.15L (%4l) %s"
+ ## Thread index with senders (collapse)
+ set index_format="%4C %Z %{%b %d} %-15.15n %?M?(#%03M)&amp;(%4l)? %s"
+ ## Default
+ #set folder_format="%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
+ ## just folder names
+ set folder_format="%2C %t %N %f"</screen>
          <simpara>Add the following to "<literal>/etc/mailcap</literal>" or "<literal>~/.mailcap</literal>" to display HTML mail and MS Word attachments inline.</simpara>
          <screen>text/html; lynx -force_html %s; needsterminal;
  application/msword; /usr/bin/antiword '%s'; copiousoutput; description="Microsoft Word Text"; nametemplate=%s.doc</screen>
+         <tip>
+           <simpara>Mutt can be used as the <ulink url="http://en.wikipedia.org/wiki/Internet_Message_Access_Protocol">IMAP</ulink> client and the mailbox format converter.  You can tag messages with "<literal>t</literal>", "<literal>T</literal>", etc.  These tagged messages can be copied with "<literal>;C</literal>" between different mailboxes and deleted with "<literal>;d</literal>" in one action.</simpara>
+         </tip>
        </section>
      </section>
      <section id="_the_remote_mail_retrieval_and_forward_utility">
-Line 15252 
 application/msword; /usr/bin/antiword '%
+Line 15439 
 application/msword; /usr/bin/antiword '%
          <simpara>Create "<literal>/usr/local/bin/getmails</literal>" as the following.</simpara>
          <screen>#!/bin/sh
  set -e
+ if [ -f $HOME/.getmail/running ]; then
+   echo "getmail is already running ... (if not, remove $HOME/.getmail/running)" &gt;&amp;2
+   pgrep -l "getmai[l]"
+   exit 1
+ else
+   echo "getmail has not been running ... " &gt;&amp;2
+ fi
+ if [ -f $HOME/.getmail/stop ]; then
+   echo "do not run getmail ... (if not, remove $HOME/.getmail/stop)" &gt;&amp;2
+   exit
+ fi
+ if [ "x$1" = "x-l" ]; then
+   exit
+ fi
  rcfiles="/usr/bin/getmail"
  for file in $HOME/.getmail/config/* ; do
    rcfiles="$rcfiles --rcfile $file"
  done
- exec $rcfiles $@</screen>
+ date -u &gt; $HOME/.getmail/running
+ eval "$rcfiles $@"
+ rm $HOME/.getmail/running</screen>
          <simpara>Configure it as the following.</simpara>
          <screen>$ sudo chmod 755 /usr/local/bin/getmails
  $ mkdir -m 0700 $HOME/.getmail
-Line 15368 
 message_log = ~/.getmail/log/pop3_name.l
+Line 15571 
 message_log = ~/.getmail/log/pop3_name.l
        <section id="_maildrop_configuration">
          <title>maildrop configuration</title>
          <simpara><literal>maildrop</literal>(1) configuration is described in <ulink url="http://www.courier-mta.org/maildrop/maildropfilter.html">maildropfilter documentation</ulink>.  Here is a configuration example for "<literal>$HOME/.mailfilter</literal>".</simpara>
-         <screen>logfile $HOME/.maildroplog
+         <screen># Local configuration
- # clearly bad looking mails: drop them into X-trash and exit
+ MAILROOT="$HOME/Mail"
- if (    /^X-Advertisement/ ||\
+ # set this to /etc/mailname contents
-         /^Subject:.*BUSINESS PROPOSAL/ ||\
+ MAILHOST="example.dom"
-         /^Subject:.*URGENT.*ASISSTANCE/ ||\
+ logfile $HOME/.maildroplog
-         /^Subject: *I NEED YOUR ASSISTANCE/ )
-     to "$HOME/Maildir/X-trash/"
- # Delivering mailinglist messages using automatically generated mailbox
+ # rules are made to override the earlier value by the later one.
- if (    /^Precedence:.*list/ || /^Precedence:.*bulk/ )
+ # mailing list mails ?
+ if (     /^Precedence:.*list/:h || /^Precedence:.*bulk/:h )
+ {
+     # rules for mailing list mails
+     # default mailbox for mails from mailing list
+     MAILBOX="Inbox-list"
+     # default mailbox for mails from debian.org
+     if ( /^(Sender|Resent-From|Resent-Sender): .*debian.org/:h )
+     {
+         MAILBOX="service.debian.org"
+     }
+     # default mailbox for mails from bugs.debian.org (BTS)
+     if ( /^(Sender|Resent-From|Resent-sender): .*@bugs.debian.org/:h )
+     {
+         MAILBOX="bugs.debian.org"
+     }
+     # mailbox for each properly maintained mailing list with "List-Id: foo" or "List-Id: ...&lt;foo.bar&gt;"
+     if ( /^List-Id: ([^&lt;]*&lt;)?([^&lt;&gt;]*)&gt;?/:h )
+     {
+         MAILBOX="$MATCH2"
+     }
+ }
+ else
  {
-     if ( /^List-Id:[ &lt;]*([^&lt;&gt;]*)[ &gt;]*/)
+     # rules for non-mailing list mails
+     # default incoming box
+     MAILBOX="Inbox-unusual"
+     # local mails
+     if ( /Envelope-to: .*@$MAILHOST/:h )
+     {
+         MAILBOX="Inbox-local"
+     }
+     # html mails (99% spams)
+     if ( /DOCTYPE html/:b ||\
+          /^Content-Type: text\/html/ )
+     {
+         MAILBOX="Inbox-html"
+     }
+     # blacklist rule for spams
+     if ( /^X-Advertisement/:h ||\
+          /^Subject:.*BUSINESS PROPOSAL/:h ||\
+          /^Subject:.*URGENT.*ASISSTANCE/:h ||\
+          /^Subject: *I NEED YOUR ASSISTANCE/:h )
+     {
+         MAILBOX="Inbox-trash"
+     }
+     # whitelist rule for normal mails
+     if ( /^From: .*@debian.org/:h ||\
+          /^(Sender|Resent-From|Resent-Sender): .*debian.org/:h ||\
+          /^Subject: .*(debian|bug|PATCH)/:h )
      {
-         MAILBOX="$MATCH1"
+         MAILBOX="Inbox"
      }
-     else
+     # whiltelist rule for BTS related mails
+     if ( /^Subject: .*Bug#.*/:h ||\
+          /^(To|Cc): .*@bugs.debian.org/:h )
      {
-         if ( /^X-Loop: *(.*)@(.*)/)
+         MAILBOX="bugs.debian.org"
-         {
-             MAILBOX="$MATCH1.$MATCH2"
-         }
-         else
-         {
-             if (    /Return-Path:.*\.debian\.org/ )
-             {
-                 MAILBOX="automatic.debian.org"
-             }
-             else
-             {
-                 MAILBOX="unknown-list"
-             }
-         }
      }
-     `test -d $MAILROOT/$MAILBOX`
+     # whitelist rule for getmails cron mails
-     if ( $RETURNCODE == 1 )
+     if ( /^Subject: Cron .*getmails/:h )
-         `maildirmake $MAILROOT/$MAILBOX`
+     {
-     to "$MAILROOT/$MAILBOX/"
+         MAILBOX="Inbox-getmails"
+     }
+ }
+ # check existance of $MAILBOX
+ `test -d $MAILROOT/$MAILBOX`
+ if ( $RETURNCODE == 1 )
+ {
+     # create maildir mailbox for $MAILBOX
+     `maildirmake $MAILROOT/$MAILBOX`
  }
- to "$HOME/Maildir/Inbox/"
+ # deliver to maildir $MAILBOX
+ to "$MAILROOT/$MAILBOX/"
  exit</screen>
          <warning>
            <simpara>Unlike <literal>procmail</literal>, <literal>maildrop</literal> does not create missing maildir directories automatically.  You must create them manually using <literal>maildirmake</literal>(1) in advance as in the example "<literal>$HOME/.mailfilter</literal>".</simpara>
-Line 15414 
 exit</screen>
+Line 15661 
 exit</screen>
        </section>
        <section id="_procmail_configuration">
          <title>procmail configuration</title>
-         <simpara>Here is an equivalent configuration with "<literal>$HOME/.procmailrc</literal>" for <literal>procmail</literal>(1).</simpara>
+         <simpara>Here is a similar configuration with "<literal>$HOME/.procmailrc</literal>" for <literal>procmail</literal>(1).</simpara>
          <screen>MAILDIR=$HOME/Maildir
  DEFAULT=$MAILDIR/Inbox/
  LOGFILE=$MAILDIR/Maillog
-Line 16610 
 Identity added: /home/&lt;username&gt;/.
+Line 16857 
 Identity added: /home/&lt;username&gt;/.
              </row>
              <row>
                <entry>
-                 <literal>stunnel4</literal>
+                 <literal>openssl</literal>
                </entry>
                <entry>
      @-@popcon1@-@
-Line 16622 
 Identity added: /home/&lt;username&gt;/.
+Line 16869 
 Identity added: /home/&lt;username&gt;/.
                  <ulink url="http://en.wikipedia.org/wiki/Transport_Layer_Security">SSL</ulink>
                </entry>
                <entry>
+     Secure Socket Layer (SSL) binary and related cryptographic tools
+     </entry>
+             </row>
+             <row>
+               <entry>
+                 <literal>stunnel4</literal>
+               </entry>
+               <entry>
+     @-@popcon1@-@
+     </entry>
+               <entry>
+     @-@psize1@-@
+     </entry>
+               <entry>
+     , ,
+     </entry>
+               <entry>
      universal SSL Wrapper
      </entry>
              </row>
-Line 16867 
 Identity added: /home/&lt;username&gt;/.
+Line 17131 
 Identity added: /home/&lt;username&gt;/.
      <section id="_the_diagnosis_of_the_system_daemons">
        <title>The diagnosis of the system daemons</title>
        <simpara>The <literal>telnet</literal> program enables manual connection to the system daemons and its diagnosis.</simpara>
-       <simpara>For example, try the following</simpara>
+       <simpara>For testing plain <ulink url="http://en.wikipedia.org/wiki/Post_Office_Protocol">POP3</ulink> service, try the following</simpara>
        <screen>$ telnet mail.ispname.net pop3</screen>
+       <simpara>For testing the <ulink url="http://en.wikipedia.org/wiki/Transport_Layer_Security">TLS</ulink>/SSL enabled <ulink url="http://en.wikipedia.org/wiki/Post_Office_Protocol">POP3</ulink> service by some ISPs, you need TLS/SSL enabled <literal>telnet</literal> client by the <literal>telnet-ssl</literal> or <literal>openssl</literal> packages.</simpara>
+       <screen>$ telnet -z ssl pop.gmail.com 995</screen>
+       <screen>$ openssl s_client -connect pop.gmail.com:995</screen>
        <simpara>The following <ulink url="http://www.ietf.org/rfc.html">RFCs</ulink> provide required knowledge to each system daemon.</simpara>
        <table pgwide="0" frame="topbot" rowsep="1" colsep="1">
          <title>List of popular RFCs</title>
-Line 16945 
 Identity added: /home/&lt;username&gt;/.
+Line 17212 
 Identity added: /home/&lt;username&gt;/.
          </tgroup>
        </table>
        <simpara>The port usage is described in "<literal>/etc/services</literal>".</simpara>
-       <note>
-         <simpara>For testing <ulink url="http://en.wikipedia.org/wiki/Transport_Layer_Security">TLS</ulink>/SSL services such as <ulink url="http://en.wikipedia.org/wiki/Https">HTTPS</ulink>, you need TLS/SSL enabled <literal>telnet</literal> program.</simpara>
-       </note>
      </section>
    </chapter>
    <chapter id="_the_x_window_system">
-Line 17122 
 Identity added: /home/&lt;username&gt;/.
+Line 17386 
 Identity added: /home/&lt;username&gt;/.
              </row>
              <row>
                <entry>
-                 <literal>kde-core</literal>
+                 <literal>kde-standard</literal>
                </entry>
                <entry>
      @-@popcon1@-@
-Line 17645 
 Type=Application</screen>
+Line 17909 
 Type=Application</screen>
      </section>
      <section id="_fonts_in_the_x_window">
        <title>Fonts in the X Window</title>
-       <simpara>The font configuration on Debian system can be summarized with historical perspective as follows.</simpara>
+       <simpara><ulink url="http://en.wikipedia.org/wiki/Fontconfig">Fontconfig 2.0</ulink> was created to provide a distribution independent library for configuring and customizing font access in 2002.  Debian after <literal>squeeze</literal> uses <ulink url="http://en.wikipedia.org/wiki/Fontconfig">Fontconfig 2.0</ulink> for its font configuration.</simpara>
-       <itemizedlist>
-         <listitem>
-           <simpara>
- Each application used to require specific manual operation to configure installed fonts before <literal>woody</literal>.
- </simpara>
-         </listitem>
-         <listitem>
-           <simpara><ulink url="http://packages.debian.org/sid/defoma">Debian Font Manager (defoma)</ulink> was created to automate this font configuration by providing a Debian specific glue layer in 2000.
- </simpara>
-           <itemizedlist>
-             <listitem>
-               <simpara>
- Each font package publishes application independent font data to defoma.
- </simpara>
-             </listitem>
-             <listitem>
-               <simpara>
- Each application package uses these data to configure each installed font via its package script.
- </simpara>
-             </listitem>
-             <listitem>
-               <simpara>
- For X server, the actual program to configure TrueType fonts and CID fonts (as well as CMaps) was packaged as <ulink url="http://packages.debian.org/sid/x-ttcidfont-conf">x-ttcidfont-conf</ulink>.
- </simpara>
-             </listitem>
-           </itemizedlist>
-         </listitem>
-         <listitem>
-           <simpara><ulink url="http://en.wikipedia.org/wiki/Fontconfig">Fontconfig 2.0</ulink> was created to provide a distribution independent library for configuring and customizing font access in 2002.
- </simpara>
-           <itemizedlist>
-             <listitem>
-               <simpara>
- As of <literal>lenny</literal> release, almost all programs which access font data seem to use this system.
- </simpara>
-             </listitem>
-             <listitem>
-               <simpara>
- After <literal>squeeze</literal>, Debian solely uses <ulink url="http://en.wikipedia.org/wiki/Fontconfig">Fontconfig 2.0</ulink> and drops <ulink url="http://packages.debian.org/sid/defoma">Debian Font Manager (defoma)</ulink>.
- </simpara>
-             </listitem>
-           </itemizedlist>
-         </listitem>
-       </itemizedlist>
        <simpara>Font supports on X Window System can be summarized as follows.</simpara>
        <itemizedlist>
          <listitem>
-Line 17835 
 The <ulink url="http://en.wikipedia.org/
+Line 18055 
 The <ulink url="http://en.wikipedia.org/
                <entry><ulink url="http://en.wikipedia.org/wiki/Fontconfig">Fontconfig</ulink>, a generic font configuration library — configuration data
      </entry>
              </row>
-             <row>
-               <entry>
-                 <literal>defoma</literal>
-               </entry>
-               <entry>
-     @-@popcon1@-@
-     </entry>
-               <entry>
-     @-@psize1@-@
-     </entry>
-               <entry>
-     Debian Font Manager — automatic font configuration framework (lenny)
-     </entry>
-             </row>
-             <row>
-               <entry>
-                 <literal>x-ttcidfont-conf</literal>
-               </entry>
-               <entry>
-     @-@popcon1@-@
-     </entry>
-               <entry>
-     @-@psize1@-@
-     </entry>
-               <entry>
-     TrueType and CID fonts configuration for X (with <ulink url="http://en.wikipedia.org/wiki/CJK_characters">CJK</ulink> support)
-     </entry>
-             </row>
            </tbody>
          </tgroup>
        </table>
-Line 17887 
 The <ulink url="http://en.wikipedia.org/
+Line 18079 
 The <ulink url="http://en.wikipedia.org/
        <tip>
          <simpara>"<ulink url="http://unifont.org/iuc27/html/ICUPresentation.html">The Penguin and Unicode</ulink>" is a good overview of modern X Window System. Other documentations at <ulink url="http://unifont.org/">http://unifont.org/</ulink> should provide good information on Unicode fonts, Unicode-enabled software, internationalization, and Unicode usability issues on <ulink url="http://en.wikipedia.org/wiki/Free_and_open_source_software">free/libre/open source (FLOSS)</ulink> operating systems.</simpara>
        </tip>
-       <tip>
-         <simpara>You should rely on <ulink url="http://en.wikipedia.org/wiki/Fontconfig">fontconfig</ulink> infrastructure to configure fonts on the Debian system.  Debian Font Manager (<literal>defoma</literal>(1)) is only useful for font installation and <ulink url="http://en.wikipedia.org/wiki/X_logical_font_description">X logical font description (XLFD)</ulink> data registration for lenny.</simpara>
-       </tip>
        <section id="_basic_fonts">
          <title>Basic fonts</title>
          <simpara>There are 2 major types of <ulink url="http://en.wikipedia.org/wiki/Computer_font">computer fonts</ulink>.</simpara>
-Line 18344 
 The filtered flat package list of the Tr
+Line 18533 
 The filtered flat package list of the Tr
      sans-serif
      </entry>
                  <entry>
-     gothic, ゴチック     hei,
+     gothic, ゴチック
      </entry>