doc/en/gentoo-x86-install.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gentoo-x86-install.xml">
  <title>Gentoo Linux 1.4_rc2 Installation Instructions</title>
  <author title="Chief Architect">
    <mail link="drobbins@gentoo.org">Daniel Robbins</mail>
  </author>
  <author title="Author">Chris Houser</author>
  <author title="Author">
    <mail link="jerry@gentoo.org">Jerry Alexandratos</mail>
  </author>
  <author title="Ghost">
    <mail link="g2boojum@gentoo.org">Grant Goodyear</mail>
  </author>
  <author title="Editor">
    <mail link="zhen@gentoo.org">John P. Davis</mail>
  </author>
  <author title="Editor">
    <mail link="Pierre-Henri.Jondot@wanadoo.fr">Pierre-Henri Jondot</mail>
  </author>
  <author title="Editor">
    <mail link="stocke2@gentoo.org">Eric Stockbridge</mail>
  </author>
  <author title="Editor">
    <mail link="rajiv@gentoo.org">Rajiv Manglani</mail>
  </author>
  <author title="Editor">
    <mail link="seo@gentoo.org">Jungmin Seo</mail>
  </author>
  <author title="Editor">
    <mail link="zhware@gentoo.org">Stoyan Zhekov</mail>
  </author>
  <abstract>These instructions step you through the process of installing Gentoo
        Linux 1.4_rc2. The Gentoo Linux installation process supports various installation
        approaches, depending upon how much of the system you want to custom-build from
        scratch.
        </abstract>
<version>2.3.14</version>
 <date>09 Feb 2003</date>
  <chapter>
    <title>About the Install</title>
    <section>
      <body>
        <p>This new boot CD will boot from nearly any modern IDE CD-ROM drive, as well
as many SCSI CD-ROM, assuming that your CD-ROM and BIOS both support booting.
Included on the CD-ROM is Linux support for IDE (and PCI IDE) (built-in to the
kernel) as well as support for all SCSI devices (available as modules.) In
addition, we provide modules for literally every kind of network card that
Linux supports, as well as tools to allow you to configure your network and
establish outbound (as well as inbound) <c>ssh</c> connections and download
files.  </p>
        <p>To install from the build CD, you will need to have a 486+ processor and
ideally at least 64 Megabytes of RAM.  (Gentoo linux has been successfully
built with 64MB of RAM + 64MB of swap space, but the build process is awfully
slow under those conditions.)</p>
        <p>Gentoo Linux can be installed using one of three &quot;stage&quot; tarball files. The
one you choose depends on how much of the system you want to compile yourself.
The stage1 tarball is used when one wants to bootstrap and build the entire
system from scratch. The stage2 tarball is used for building the entire system
from scratch, except for the bootstrap part which is already performed for you.
And the stage3 tarball already contains a basic Gentoo Linux system that has
been optimized for your system.</p>
        <p> So, how does one begin the install process? First, you'll want to decide
which one of our LiveCD ISO images to grab from
<uri>http://www.ibiblio.org/gentoo/releases/1.4_rc2/x86/</uri>. 
In this directory, you'll see several subdirectories such as <c>athlon</c>
for each of our various architecture-specific builds. Here's a low-down on
each arch directory and what it contains:</p>
        <table>
          <tr>
            <th>Architecture</th>
            <th>Description</th>
          </tr>
          <tr>
            <ti>x86</ti>
            <ti>Stage 1 tarballs and &quot;gentoo-basic&quot; liveCD -- will work on anything.</ti>
          </tr>
          <tr>
            <ti>i586</ti>
            <ti>Stage 2 and 3 tarballs, GRP packages and liveCD for i586+ CPUs</ti>
          </tr>
          <tr>
            <ti>i686</ti>
            <ti>Stage 2 and 3 tarballs, GRP packages and liveCD for i686+ CPUs</ti>
          </tr>
          <tr>
            <ti>athlon</ti>
            <ti>Stage 2 and 3 tarballs, GRP packages and liveCD for AMD Athlon CPUs</ti>
          </tr>
          <tr>
            <ti>athlon-xp</ti>
            <ti>Stage 2 and 3 tarballs, GRP packages and liveCD for AMD Athlon XP CPUs</ti>
          </tr>
          <tr>
            <ti>athlon-mp</ti>
            <ti>Stage 2 and 3 tarballs, GRP packages and liveCD for AMD Athlon MP CPUs</ti>
          </tr>
          <tr>
            <ti>pentium3</ti>
            <ti>Stage 2 and 3 tarballs, GRP packages and liveCD for Intel Pentium III and Pentium 4 CPUs</ti>
          </tr>
        </table>
        <p>Inside each of these directories,
you'll find a <path>livecd/</path> directory that contains LiveCDs. While these LiveCDs
will boot on any architecture, the install-related tarballs are optimized for a particular
CPU type and will not work on all systems, except for the &quot;gentoo-basic&quot; LiveCD in the <path>x86</path>
directory which can be used to install on anything.
</p>
        <p> The LiveCDs are full CD images that should be burned to a CDR or CD-RW
using CD burning software.  Currently, we have two types of LiveCDs. The first
carries the &quot;gentoo-basic&quot; label, and is approximately 40MB in size and lives
in the <path>x86/livecd/</path> directory. This LiveCD is of minimal size to
allow for a initial quick download and contains a stage1 tarball that can be
found in <path>/mnt/cdrom/gentoo/</path> after the CD has booted.</p>
        <p>The second flavor of LiveCD we currently offer is labelled &quot;livecd-grp.&quot;
These CDs (found in their respective <path>arch/livecd</path> directories)
contain stage1, 2 and 3 tarballs, and also contain a set of GRP packages
optimized for a specific architecture. GRP is simply precompiled packages for
very large applications, such as XFree86. KDE, GNOME, OpenOffice, etc. 
Using these LiveCDs, it will be possible
for you to install a fully-functional Gentoo Linux system very quickly. The
downside is that these ISO images are large -- around 600MB -- so they can take
a while to download.</p>
        <info>If for some reason your install gets interrupted at some point, you can
reboot and restart. For example, if you have partitioned, installed the stageX
tarball, and are ready to chroot, you can restart the install if necessary.
Just re-boot with the LiveCD, then mount your drives/partitions to
<path>/mnt</path> as normal. Basically, you can do this at about any point
during the install, just not before partitioning for obvious reasons.  </info>
        <warn>If you encounter a problem with any part of the install and wish to
report it as a bug, report it to <uri>http://bugs.gentoo.org</uri>. If the bug
needs to be moved upstream to the package maintainers (ie KDE) the
<e>developers</e> will take care of that.  </warn>
        <p>Now, let's quickly review the install process. First, we'll download, burn
and boot a LiveCD. After getting a root prompt, we'll create partitions, create
our filesystems, and extract either a stage1, stage2 or stage3 tarball.  If we
are using a stage1 or stage2 tarball, we will take the appropriate steps to get
our systems to stage3.  Once our systems are at stage3, we can configure them
(tweaking config files, installing a bootloader, etc) and boot them and have a
fully-functional Gentoo Linux system.  Depending on what stage of the build
process you're starting from, here's what's required for installation: </p>
        <table>
          <tr>
            <th>stage tarball</th>
            <th>requirements for installation</th>
          </tr>
          <tr>
            <ti>1</ti>
            <ti>partition/filesystem setup, emerge sync, bootstrap, emerge system, emerge linux sources, final configuration</ti>
          </tr>
          <tr>
            <ti>2</ti>
            <ti>partition/filesystem setup, emerge sync, emerge system, emerge linux sources, final configuration</ti>
          </tr>
          <tr>
            <ti>3</ti>
            <ti>partition/filesystem setup, emerge sync, final configuration</ti>
          </tr>
        </table>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Booting</title>
    <section>
      <body>
        <p>Start by booting the LiveCD. If detected properly, you should see a fancy boot screen
                with the Gentoo Linux logo on it. At this screen, you can hit Enter to begin the boot process,
                hit F2 for help, or pass kernel boot options by typing <c>gentoo opt1 opt2</c>, etc.
                Once you hit Enter, you'll be
                        greeted with a lot of  text output 
                        followed by the normal Gentoo Linux boot sequence.
                        You will be automatically logged in as &quot;root&quot; and the root password will be 
                        set to a random string for security purposes.
                        You should have a root (&quot;<c>#</c>&quot;) prompt on the current
                        console, and can also open new root consoles by pressing Alt-F2, Alt-F3 and Alt-F4.
                        Get back to the one you started on by pressing (you guessed it) Alt-F1.
                        </p>
        <p>You've probably also noticed that above your <c>#</c> prompt is a bunch of help text
                        explaining how to do things like configure your network devices and where you can find
                        the Gentoo Linux stage tarballs and packages on your CD.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Load Kernel Modules</title>
    <section>
      <body>
        <p>If the PCI autodetection missed some of your hardware, you 
                        will have to load the appropriate modules manually.
                        To view a list of all available network card modules, type <c>ls
                        /lib/modules/*/kernel/drivers/net/*</c>.  To load a particular module,
                        type:
                        </p>
        <pre caption="PCI Modules Configuration">
# <c>modprobe pcnet32</c>
<comment>(replace pcnet32 with your NIC module)</comment>
                        </pre>
        <p>Now, if you want to be able to access any SCSI hardware that wasn't detected
                        during the initial boot autodetection process, you'll need to load the appropriate
                        modules from /lib/modules, again using <c>modprobe</c>:
                        </p>
        <pre caption="Loading SCSI Modules">
# <c>modprobe aic7xxx</c>
# <c>modprobe sd_mod</c>
                        </pre>
        <p><c>aic7xxx</c> supports your SCSI controller and <c>sd_mod</c> supports SCSI hard disks. </p> 
                        <note>
                        Support for a SCSI CD-ROMs and disks are built-in in the kernel.
                        </note>
        <p>If you are using hardware RAID, you'll need to load the 
                        ATA-RAID modules for your RAID controller.
                        </p>
        <pre caption="Loading RAID Modules">    
# <c>modprobe ataraid</c>    
# <c>modprobe pdcraid</c>            
      <comment>(Promise Raid Controller)</comment>    
# <c>modprobe hptraid</c>            
      <comment>(Highpoint Raid Controller)</comment>    
                        </pre>
        <p>The Gentoo LiveCD should have enabled DMA on your disks, but if it did not,
                        <c>hdparm</c> can be used to set DMA on your drives. </p>
        <pre caption="Setting DMA"><comment>Replace hdX with your disk device.</comment>
# hdparm -d 1 /dev/hdX <comment>Enables DMA </comment>
# hdparm -d1 -A1 -m16 -u1 -a64 /dev/hdX <comment>Enables DMA and other safe performance-enhancing options</comment>
# hdparm -X66 /dev/hdX <comment>Force-enables Ultra-DMA -- dangerous -- may cause some drives to mess up</comment></pre>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Loading PCMCIA Kernel Modules</title>
    <section>
      <body>
        <p>If you have a PCMCIA network card, you will need to do some additional 
                        trickery.
                        </p>
        <warn>To avoid problems with <c>cardmgr</c>, you <e>must</e> run it <e>before</e> you enter the chroot
                        portion of the install. </warn>
        <pre caption="Loading PCMCIA Modules">
# <i>modprobe pcmcia_core</i>
# <i>modprobe i82365</i>
# <i>modprobe ds</i>
# <i>cardmgr -f</i>
                        </pre>
        <p>As <c>cardmgr</c> detects which hardware is present, your speaker should emit a
                        few reassuring beeps, and your PCMCIA network card should hum to life. You can
                        of course insert the PCMCIA card after loading <c>cardmgr</c> too, if that's 
                        preferable. (Technically, you need not run 
                        <c>cardmgr</c> if you know exactly which module your PCMCIA card requires. 
                        But if you don't, loading all PCMCIA modules and see which sticks won't work,
                        as all PCMCIA modules load obligingly and hang around for a PCMCIA card to 
                        drop by. <c>cardmgr</c> will also unload the module(s) for any card when you
                        remove it). </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Configuring Networking</title>
    <section>
      <title> PPPoE configuration</title>
      <body>
        <p>Assuming you need PPPoE to connect to the internet, the livecd (any version) has
                        made things easy for you by including <c>rp-pppoe</c>. Use the provided <c>adsl-setup</c>
                        script to configure your connection. You will be prompted for the ethernet
                        device that is connected to your adsl modem, your username and password,
                        the IPs of your DNS servers, and if you need a basic firewall or not. </p>
        <pre caption="Configuring PPPoE">
# <c> adsl-setup </c>
# <c> adsl-start </c>
                        </pre>
        <p>If something goes wrong,  double-check that you correctly typed
                        your username and password by looking at <path>/etc/ppp/pap-secrets</path> or
                        <path>/etc/ppp/chap-secrets</path>, and make sure you are using the right ethernet device. </p>
      </body>
    </section>
    <section>
      <title> Automatic Network Configuration </title>
      <body>
        <p>The Gentoo Linux install lets you configure a working network, allowing you to use
                <c>ssh</c>, <c>scp</c>, <c>lynx</c>, <c>irssi</c> or <c>wget</c> as needed before even beginning the installation process. 
                Even if you don't need to do these things now, you should go ahead and set up networking now.
                Once networking is up, Portage will be able to use your configured network once you are inside
                the chroot environment (required for installing Gentoo Linux). 
                The simplest way to set up networking is to run our new <c>net-setup</c>
                script. </p>
        <pre caption="Net-Setup Script">
# <c>net-setup eth0</c>
                </pre>
        <p>Of course, if you prefer, you may still set up networking manually. </p>
      </body>
    </section>
    <section>
      <title>Manual DHCP Configuration</title>
      <body>
        <p>Network configuration is simple with DHCP; If your ISP is not using
                DHCP, skip down to the static configuration section below. </p>
        <pre caption="Network configuration with DHCP">
# <c>dhcpcd eth0</c> 
                </pre>
        <note>Some ISPs require you to provide a hostname.  To do that,
                add a <c>-h myhostname</c> flag to the dhcpcd command line above.
                </note>
        <p>If you receive <i>dhcpConfig</i> warnings, don't panic; the errors
                are most likely cosmetic.  Skip down to Network testing below.</p>
      </body>
    </section>
    <section>
      <title>Manual Static Configuration</title>
      <body>
        <p>We need to setup just enough networking so that we can download
                sources for the system build, as well as the required localhost interface.
                Type in the following commands, replacing
                $IFACE with your network interface (typically <c>eth0</c>), $IPNUM
                with your IP address, $BCAST with your broadcast address, and $NMASK
                with your network mask.  For the <c>route</c> command, replace 
                $GTWAY with your default gateway.
                </p>
        <pre caption="Static IP Network Configuration">
# <c>ifconfig $IFACE $IPNUM broadcast $BCAST netmask $NMASK</c>
# <c>/sbin/route add -net default gw $GTWAY netmask 0.0.0.0 metric 1</c>
                </pre>
        <p>Now it's time to create the <path>/etc/resolv.conf</path>
                file so that name resolution (finding Web/FTP sites by name, rather than just by IP address) will work.</p>
        <p>Here's a template to follow for creating your /etc/resolv.conf file: </p>
        <pre caption="/etc/resolv.conf template">
domain mydomain.com
nameserver 10.0.0.1
nameserver 10.0.0.2
                </pre>
        <p>Replace <c>10.0.0.1</c> and <c>10.0.0.2</c> with the IP addresses of your
                primary and secondary DNS servers respectively.</p>
      </body>
    </section>
    <section>
      <title>Proxy Configuration</title>
      <body>
        <p>If you are behind a proxy, it is necessary to configure your proxy before
                you continue. We will export some variables to set up the proxy accordingly. 
                </p>
        <pre caption="Setting a Proxy">
# <c>export http_proxy=&quot;machine.company.com:1234&quot; </c>
# <c>export ftp_proxy=&quot;$http_proxy&quot; </c>
# <c>export RSYNC_PROXY=&quot;$http_proxy&quot; </c>
                </pre>
      </body>
    </section>
    <section>
      <title>Network Testing</title>
      <body>
        <p>Now that your network has been configured, the <c>/sbin/ifconfig -a</c> command should show
                that your network card is working (look for <e>UP</e> and <e>RUNNING</e> in the output). </p>
        <pre caption="/sbin/ifconfig for a working network card">
eth0      Link encap:Ethernet  HWaddr 00:50:BA:8F:61:7A
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::50:ba8f:617a/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1984 txqueuelen:100
          RX bytes:485691215 (463.1 Mb)  TX bytes:123951388 (118.2 Mb)
          Interrupt:11
                </pre>
        <p>You may want to also try pinging your ISP's DNS server (found in <path>/etc/resolv.conf</path>),
                and a website of choice, just to make sure that your packets are reaching the net, DNS name
                resolution is working correctly, etc.
                </p>
        <pre caption="Further Network Testing">
# <c>ping www.some_website.com </c>
                </pre>
      </body>
    </section>
    <section>
      <title>Networking is go!</title>
      <body>
        <p>Networking should now be configured and useable.  You should be able to use the included
                <c>ssh</c>, <c>scp</c>, <c>lynx</c>, <c>irssi</c> and <c>wget</c> commands to connect to other machines on your LAN or the Internet.</p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Partition Configuration</title>
    <section>
      <body>
        <p>Now that the kernel can see the network card and disk controllers, it's time
                                to set up disk partitions for Gentoo Linux.
                                </p>
        <p>Here's a quick overview of the standard Gentoo Linux partition layout.
                                We're going to create at least three partitions: a swap partition, a root
                                partition (to hold the bulk of Gentoo Linux), and a special boot partition.
                                The boot partition is designed to hold the GRUB or LILO  boot loader information as well as
                                your Linux kernel(s).  The boot partition gives us a safe place to store
                                everything related to booting Linux. During normal day-to-day Gentoo Linux use,
                                your boot partition should remain <e>unmounted</e>.  This prevents your kernel
                                from being made unavailable to GRUB (due to filesystem corruption) in the event
                                of a system crash, preventing the chicken-and-egg problem where GRUB can't read
                                your kernel (since your filesystem isn't consistent) but you can't bring your
                                filesystem back to a consistent state (since you can't boot!)
                                </p>
        <p>Now, on to filesystem types.  Right now, you have five filesystem options:
                                XFS, ext2, ext3 (journaling), jfs,  and ReiserFS.  ext2 is the tried and true Linux
                                filesystem but doesn't have metadata journaling.  ext3 is the new version of
                                ext2 with both metadata journaling and ordered data writes, effectively
                                providing data journaling as well.  ReiserFS is a B*-tree based filesystem
                                that has very good small file performance, and greatly outperforms both ext2 and
                                ext3 when dealing with small files (files less than 4k), often by a factor of
                                10x-15x. ReiserFS also scales extremely well and has metadata journaling.
                                As of kernel 2.4.18+, ReiserFS is finally rock-solid and highly recommended.
                                XFS is a filesystem with metadata journaling that
                                is fully supported under Gentoo Linux's <path>xfs-sources</path> kernel, but 
                                is generally not recommended due to its tendency to lose recently-modified
                                data if your system locks up or unexpectedly reboots (due to a power failure, for instance.)
                                Finially, jfs is IBM's own high performance journaling filesystem. Since it is obscure, we cannot comment either positvely nor negatively on its stability.</p>
        <p>If you're looking for the most standard filesystem, use ext2.  If you're looking
                                for the most rugged journalled filesystem, use ext3.  If you're looking for a
                                high-performance filesystem with journaling support, use ReiserFS;  both ext3 and ReiserFS are 
                                mature and refined.  
                                Here are our basic recommended filesystem
                                sizes and types:
                                </p>
        <table>
          <tr>
            <th>Partition</th>
            <th>Size</th>
            <th>Type</th>
            <th>example device</th>
          </tr>
          <tr>
            <ti>boot partition, containing kernel(s) and boot information</ti>
            <ti>100 Megabytes</ti>
            <ti>ext2/3 highly recommended (easiest); if ReiserFS then mount with <c>-o notail</c></ti>
            <ti>/dev/hda1</ti>
          </tr>
          <tr>
            <ti>swap partition (no longer a 128 Megabyte limit)</ti>
            <ti>Generally, unless you are running a server, swapspace can be pretty flexible. Please consult the 
            below table for some loose guidelines on swap space.</ti>
            <ti>Linux swap</ti>
            <ti>/dev/hda2</ti>
          </tr>
          <tr>
            <ti>root partition, containing main filesystem (/usr, /home, etc)</ti>
            <ti>&gt;=1.5 Gigabytes</ti>
            <ti>ReiserFS, ext3 recommended; ext2 ok</ti>
            <ti>/dev/hda3</ti>
          </tr>
        </table>

        <table>
        <tr>
        <th>Physical RAM</th>
        <th>Swapspace Size</th>
        </tr>
        <tr>
        <ti>0-48MB RAM</ti>
        <ti>048-064MB RAM</ti>
        <ti>064MB-128MB RAM</ti>
        <ti>128-256MB RAM</ti>
        <ti>256-512MB RAM</ti>
        </tr>
        <tr>
        <ti>720MB</ti>
        <ti>702MB</ti>
        <ti>640MB</ti>
        <ti>256MB</ti>
        </tr>
        </table>
                
        <p>Before creating filesystems, you may want to initialize the
                        beginning of your HD using <c>dd</c>. Doing this will ensure that your new filesystem
                        will not be mis-indentified by Linux's mounting code.
                        This can be done as follows:    
                        </p>
        <pre caption="Initializing first 1024 Sectors of HD">
# <c>dd if=/dev/zero of=/dev/hdxy bs=1K count=1</c>
<comment>Replace /dev/hdxy with the device you wish to &quot;clean.&quot;</comment>
                        </pre>
        <warn>The command above will destroy all data from <path>/dev/hdxy</path>. 
        Be careful and check twice which partition you specify for zeroing.
        If you make a mistake it might result in a loss of data.
        </warn>
        <p>At this point, create your partitions using <c>fdisk</c>.  Note that your partitions
                        should be of type 82 if swap and 83 for regular filesystems (whether ReiserFS, ext2/3 or other). </p>
        <note><c>cfdisk</c> is included on the install CD, and it is <i>considerably</i> easier to use than
                        <c>fdisk</c>. Just type <c>cfdisk</c> to run it; by default, cfdisk will work with <b>/dev/hda</b>. If /dev/hda is not the hard disk you want to partition, give the right value to cfdisk as a parameter. For example: <c>cfdisk /dev/hde</c></note>
        <note>If <c>fdisk</c> or <c>cfdisk</c> instruct you to do so, please reboot to allow your system to detect the
new partition configuration.</note>
        <note>If you are using RAID your partitions will be a little different.  You
will have the partitions like this: <path>/dev/ataraid/discX/partY</path> X is
the arrays you have made, so if you only have made 1 array, then it will be
disc0.Y is the partition number as in <path>/dev/hdaY</path> </note>
        <p>Once you've created your partitions, it's time to initialize
                        the filesystems that will be used to house our data.  Initialize swap as follows:</p>
        <pre caption="Initializing Swap">
# <c>mkswap /dev/hda2</c>
                        </pre>
        <p>You can use the <c>mke2fs</c> command to create ext2 filesystems.</p>
        <pre caption="Creating an ext2 Filesystem">
# <i>mke2fs /dev/hda1</i>
                        </pre>
        <p>To create an XFS filesystem, use the <c>mkfs.xfs</c> command.</p>
        <pre caption="Creating a XFS Filesystem">
# <c>mkfs.xfs /dev/hda3</c>
                        </pre>
        <note>
                        You may want to add a couple of additional flags to the <c>mkfs.xfs</c> command: <c>-d agcount=3 -l size=32m</c>. 
                        The <c>-d agcount=3</c> command will lower
                        the number of allocation groups.  XFS will insist on using at least 1 allocation group per 4 GB of your partition,
                        so, for example, if you hava a 20 GB partition you will need a minimum agcount of 5.
                        The <c>-l size=32m</c> command increases the journal size to 32 Mb, increasing performance.
                        </note>
        <warn>
                        If you are installing an XFS partition over a previous ReiserFS partition,
                        later attempts to mount may fail without an explicit <c>mount -t xfs</c>. 
                        The solution is to zero out the partition before creating the XFS filesystem:
                        <c>dd if=/dev/zero of=/dev/hd<comment>x</comment> bs=1k</c>. 
                        </warn>
        <p>If you'd like to use ext3, you can create ext3 filesystems using <c>mke2fs -j</c>.</p>
        <pre caption="Creating an ext3 Filesystem">
# <c>mke2fs -j /dev/hda3</c>
                        </pre>
        <note>You can find out more about using ext3 under Linux 2.4 at
                        <uri>http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html</uri>.
                        </note>
        <p>To create ReiserFS filesystems, use the <c>mkreiserfs</c> command.</p>
        <pre caption="Creating a ReiserFS Filesystem">
# <c>mkreiserfs /dev/hda3</c>
                        </pre>

        <p>To create JFS filesystems, use the <c>mkfs.jfs</c> comamnd.</p>
        <pre caption="Creating a JFS Filesystem">
# <c>mkfs.jfs /dev/hda3</c>
        </pre>
        
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Mount Partitions</title>
    <section>
      <body>
        <p>Now, we'll activate our new swap, since we may need the additional virtual memory that
                        provides later:
                        </p>
        <pre caption="Activating Swap">
# <c>swapon /dev/hda2</c>
                        </pre>
        <p>Next, we'll create the <path>/mnt/gentoo</path> and <path>/mnt/gentoo/boot</path> mountpoints,
                        and we'll mount our filesystems to these mountpoints. </p>
        <pre caption="Creating Mount Points">
# <c>mkdir /mnt/gentoo</c>
# <c>mount /dev/hda3 /mnt/gentoo</c>
# <c>mkdir /mnt/gentoo/boot</c>
# <c>mount /dev/hda1 /mnt/gentoo/boot</c>
                        </pre>
        <p>
                        If you are setting up Gentoo
                        Linux with a separate <path>/usr</path> or <path>/var</path>, these would get mounted to
                        <path>/mnt/gentoo/usr</path> and <path>/mnt/gentoo/var</path>, respectively.
                        </p>
                <impo>If your <e>boot</e> partition (the one holding the kernel) is ReiserFS, be sure to mount it
                        with the <c>-o notail</c> option so GRUB gets properly installed.  Make sure 
                        that <c>notail</c> ends up in your new <path>/etc/fstab</path> boot partition entry, too.
                        We'll get to that in a bit.
                        </impo>
        <impo>If you are having problems mounting your boot partition with ext2, try using
                        <c>mount /dev/hXX /mnt/gentoo/boot -t ext2 </c> </impo>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Obtaining the Desired 'stage-x' Tarball</title>
    <section>
      <body>
        <p>If you want to start from a stage1 tarball, then you're already set
                        to go; you can find the stage1 tarball in <path>/mnt/cdrom/gentoo/</path>.
                        On the other hand, if you would prefer to start from a stage2 or stage3
                        tarball that has been optimized for your architecture you can download it
                        (into <path>/mnt/gentoo</path> would be the simplest)
                        from one of the Gentoo mirror sites. </p>

        <pre caption="Downloading Required Stages">
# <c>cd /mnt/gentoo</c>
<comment>Use lynx to get the URL for your tarball:</comment>
# <c>lynx http://www.ibiblio.org/pub/Linux/distributions/gentoo/releases/1.4_rc2/x86/</c>
<comment>Use <c>Up</c> and <c>Down</c> arrows keys (or the <c>TAB</c> key) to go to the right directory
Highlight the appropriate stage you want to download
Press <c>d</c> which will initiate the download
Save the file and quit the browser

<b>OR</b> use wget from the command line:</comment>
# <c>wget <comment>insert URL to the required stage tarball here.</comment></c>
                        </pre>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Unpacking the Stage Tarballs</title>
    <section>
      <body>
        <p>Now it's time to extract the compressed stage tarball of your choice to <path>/mnt/gentoo</path>.
                        Then, we'll <c>chroot</c> over to the new Gentoo Linux build installation to &quot;enter&quot; the new
                        Gentoo Linux system.
                        </p>
        <impo>Be sure to use the <c>p</c> option with <c>tar</c>.  Forgetting to do this will
                        cause certain files to have incorrect permissions.</impo>
        <p>If you are using the &quot;from scratch, build everything&quot; install method,
                        you will want to use the <path>stage1-ix86-1.4_beta.tbz2</path> image.
                        If you're using one of our bigger CDs, you'll also have a choice of a stage2 and stage3 image.
                        These images allow you to save time at the expense of configurability (we've already chosen
                        compiler optimizations and default USE variables for you.)  
                        </p>
        <pre caption="Unpacking the Stages">
# <c>cd /mnt/gentoo</c>
# <c>tar -xvjpf /mnt/cdrom/gentoo/stage?-*.tbz2</c>
# <c>mount -o bind /proc /mnt/gentoo/proc</c>

<!--# <c>mount -o bind /dev /mnt/gentoo/dev</c>
<comment>The /dev bind-mount is required for perl to build properly for some people.</comment>
-->
# <c>cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</c>
                        </pre>
<p>If you are going to use GRP, now would be a good time to execute the following commands:
</p>

<pre caption="Getting ready for GRP">
# <c>mkdir /mnt/gentoo/GRP</c>
# <c>mount -o bind /mnt/cdrom/gentoo/packages /mnt/gentoo/GRP</c>
</pre>
                        
        <pre caption="Entering the chroot Environment">
# <c>chroot /mnt/gentoo /bin/bash</c>
# <c>env-update</c>
Regenerating /etc/ld.so.cache...
# <c>source /etc/profile</c>
<comment>The above points your shell to the new paths and updated binaries. </comment>
                        </pre>
        <p>After you execute these commands, you'll be &quot;inside&quot; your new Gentoo Linux environment.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Getting the Current Portage Tree using Rsync</title>
    <section>
      <body>
        <p>Now, you'll need to run <c>emerge sync</c>.  This will make sure that
                        you have the most current copy of the Portage tree. </p>
        <pre caption="Updating Using Rsync">
# <c>emerge sync</c>
                        </pre>
        <p>The Portage tree will be downloaded and stored in <path>/usr/portage</path>;
                        it's about 90Mb in size without tarballs.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Setting Gentoo optimizations (make.conf)</title>
    <section>
      <body>
        <p>Now that you have a working copy of the Portage tree, people using stage1 to
                        install will need to bootstrap their Gentoo Linux system as follows.  First 
                        edit the file <path>/etc/make.conf</path>.  In this file, you should set your 
                        <c>USE</c> flags, which specify optional functionality that you would 
                        like to be built into packages; generally, the defaults (an <e>empty</e>
                        or unset <c>USE</c> variable) are fine.  
                        More information on <c>USE</c> flags can be found
                        <uri link="http://www.gentoo.org/doc/en/use-howto.xml">here</uri>.
                        A complete list of current USE flags can be found
                        <uri link="http://www.gentoo.org/dyn/use-index.xml">here</uri>.
                        </p>
        <p>You also should set appropriate <c>CHOST</c>, <c>CFLAGS</c> and 
                        <c>CXXFLAGS</c> settings for the kind of system that you are creating 
                        (commented examples can be found further down in the file.)  Your best friend 
                        is <path>man gcc</path> to figure out what additional <c>CFLAGS</c> and 
                        <code>CXXFLAGS</code> are available.  Search for 'Optimization'.
                        </p>
        <p>If necessary, you can also set proxy information here if you are behind a 
                        firewall.
                        </p>
        <pre caption="Setting make.conf Options">
# <c>nano -w /etc/make.conf</c> <comment>(Adjust these settings)</comment>
                        </pre>
        <note>
                        People who need to substantially tweak the build process should take a look at
                        the <path>/etc/make.globals</path> file.  This file comprises gentoo defaults and
                        should never be touched.  If the defaults do not suffice, then new values should
                        be put in <path>/etc/make.conf</path>, as entries in <path>make.conf</path>
                        <comment>override</comment> the entries in <path>make.globals</path>.  If you're
                        interested in tweaking USE settings, look in <path>/etc/make.profile/make.defaults</path>.
                        If you want to turn off any USE settings found here, add an appropriate <c>USE=&quot;-foo&quot;</c>
                        in /etc/make.conf (to turn off the <c>foo</c> USE setting.)
                        </note>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Starting from Stage1</title>
    <section>
      <body>
        <p>The stage1 tarball is for ultimate tweakage. If you have picked this tarball, 
                you are most likely looking to have an uber-optimized system. Have fun, because optimization
                is what Gentoo Linux is all about!
                </p>
        <p>Now, it's time to start the &quot;bootstrap&quot; process.  This process takes about two hours on
                        my 1200Mhz AMD Athlon system.  During this time, the extracted build image will be prepped
                        for compiling the rest of the system.  The GNU compiler suite will be built, as well as the GNU C library.
                        These are time consuming builds and make up the bulk of the bootstrap process.
                        </p>
        <pre caption="Bootstrapping">
# <c>cd /usr/portage</c>
# <c>scripts/bootstrap.sh</c>
                        </pre>
        <p>The &quot;bootstrap&quot; process will now begin.
                        </p>
        <note>
                        Portage by default uses <c>/var/tmp</c> during package building, often
                        using several hundred megabytes of temporary storage. If you would like to
                        change where Portage stores these temporary files, set a new PORTAGE_TMPDIR <e>before</e>
                        starting the bootstrap process, as follows:
                        </note>
        <pre caption="Changing Portage's Storage Path">
# <c>export PORTAGE_TMPDIR=&quot;/otherdir/tmp&quot;</c>
                        </pre>
        <p><c>bootstrap.sh</c> will build <c>binutils</c>, <c>gcc</c>, <c>gettext</c>,
                        and <c>glibc</c>, rebuilding <c>binutils</c>, <c>gcc</c>, and <c>gettext</c>
                        after <c>glibc</c>. Needless to say, this process takes a while.
                        Have a nice nap.  Once this process completes, your system will be equivalent to a &quot;stage2&quot; system,
                        which means you can now move on to the stage2 instructions.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Starting from Stage2</title>
    <section>
      <body>
        <p>The stage2 tarball already has the bootstrapping done for you. All that you have
                to do is install the rest of the system.
                        </p>
        <note>
                        If you haven't done so, please edit <path>/etc/make.conf</path> to your flavor.
                        </note>
        <pre caption="Installing the Rest of the System">
# <c>export CONFIG_PROTECT=&quot;-*&quot;</c>
# <c>emerge -p system</c>
        <comment>[lists the packages to be installed]</comment>
# <c>emerge system</c>
                        </pre>
        <note>The <c>export CONFIG_PROTECT=&quot;-*&quot;</c> line ensures that any new scripts
                        installed to <path>/etc</path> will overwrite the old scripts (stored in
                        <path>sys-apps/baselayout</path>), bypassing Portage's new config file
                        management support.  Type <c>emerge --help config</c> for more details.</note>
        <p>It's going to take a while
                        to finish building the entire base system.  Your reward is that it will be
                        thoroughly optimized for your system.  The drawback is that you have to find a
                        way to keep yourself occupied for some time to come.  The author suggests &quot;Star
                        Wars - Super Bombad Racing&quot; for the PS2. 
                        </p>
                        <p>When this process completes, your system     will be the equivalent of a stage3 system. You have
                        a couple of choices on how to continue
                        at this point. You can move onto the stage3 instructions and complete those. Doing that will
                        get your system right up to date with what is in the current Portage tree. This is not necessary,
                        but it is highly recommended. If you do not choose to get up to date with the stage3 instructions,
                        you can move onto the GRP install section. If you do not wish to use GRP, you can move
                        onto <uri link="http://www.gentoo.org/doc/en/gentoo-x86-install.xml#doc_chp16">Chapter 16: Final Steps</uri>.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Starting from Stage3</title>
    <section>
      <body>
        <p>The stage3 tarball is already configured for your system. There is not much to do for this stage,
        but it is a very good idea to update your system to the newest available packages. </p>

        <p>Since many packages will be downloaded for the update world, you may want to emerge <i>mirrorselect</i>.
        <i>Mirrorselect</i> is a nice ncurses GUI app that will assist you in picking a Gentoo distfiles mirror. </p>

        <pre caption="Emerging mirrorselect">
# <c>emerge mirrorselect</c>
        </pre>
                
        <note>If you have not already edited <path>/etc/make.conf</path> to fit your specifications,
        now would be a good time to do so. </note>
        <pre caption="Getting up-to-date">
        # <c>emerge sync</c>
        # <c>emerge -up world</c>
        <comment>lists [<i>packages</i>] to be installed</comment>
        # <c>emerge -u world</c>
        </pre>
        <p>Once you complete this step, you have some options on how to continue. If you are going to be using GRP,
        please move onto the GRP section. If you are not going to use GRP, you may continue onto 
        <uri link="http://www.gentoo.org/doc/en/gentoo-x86-install.xml#doc_chp16">Chapter 16: Final Steps</uri>.
        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Using GRP</title>
    <section>
      <body>
        <p>You can take advantage of pre-built GRP package sets to avoid compiling certain popular and large packages. Currently, we provide full builds of everything you need for <c>openoffice-bin</c>,
<c>GNOME</c>, <c>KDE</c> and <c>xfree</c>. 
</p>
<p>First, you will need to <c>cd</c> to the location of the packages directory. We have already
mounted the directory at <path>/GRP</path>.  In that directory you
will find the <c>grp-install.sh</c> script, an <i>All</i> directory that contains all of the binary
packages, and a list of available GRP packages.  To install any/all of these
package sets you should do the following: </p>
        <pre caption="Using GRP">
# <c>cd /GRP</c>
# <c>sh grp-install.sh &lt;list of package lists&gt;</c>
<comment>where &lt;list of package lists&gt; may be any of the *-list.txt files found in the same directory.</comment>
</pre>
        <p><c>grp-install.sh</c> can be run multiple times without replacing existing installations. You can
do a <c>sh grp-install.sh</c> for a basic usage description if you are still a bit foggy.
</p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final Steps: Timezone</title>
    <section>
      <body>
        <p>At this point, you should have system that's ready for final configuration.
                        We'll start the configuration process by setting the timezone. By setting the timezone before building
                        the kernel we ensure that users get reasonable <c>uname -a</c> output.
                        </p>
        <p>Look for your timezone (or GMT if you using Greenwich Mean Time) in 
                        <path>/usr/share/zoneinfo</path>.  Then, make a symbolic link by typing:
                        </p>
        <pre caption="Creating a symbolic link for timezome">
# <c>ln -sf /usr/share/zoneinfo/path/to/timezonefile /etc/localtime</c>
                        </pre>
        <p>You might also want to check <path>/etc/rc.conf</path> to make sure your timezone settings
                        are correct.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: kernel and system logger</title>
    <section>
      <body>
        <note>
                        If you haven't done so, please edit <path>/etc/make.conf</path> to your flavor.
                        </note>
        <p>You now need to merge Linux source ebuilds.  Here are the ones we currently
                        offer:
                        </p>
        <table>
          <tr>
            <th>ebuild</th>
            <th>description</th>
          </tr>
          <tr>
            <ti>
              <path>gentoo-sources</path>
            </ti>
            <ti>Our own performance and functionality-enhanced kernel does not include XFS support.</ti>
          </tr>
          <tr>
            <ti>
              <path>xfs-sources</path>
            </ti>
            <ti>Highly-compatible kernel with XFS support.</ti>
          </tr>
          <tr>
            <ti>
              <path>openmosix-sources</path>
            </ti>
            <ti>A stock Linux kernel source tree patched with support for the GPL <uri link="http://www.openmosix.com">openMosix</uri> load-balancing/clustering technology</ti>
          </tr>
          <tr>
            <ti>
              <path>usermode-sources</path>
            </ti>
            <ti>A stock Linux kernel source tree patched with support for User-Mode Linux.  (&quot;Linux inside Linux&quot; technology)</ti>
          </tr>
          <tr>
            <ti>
              <path>vanilla-sources</path>
            </ti>
            <ti>A stock Linux kernel source tree, just like you'd get from kernel.org</ti>
          </tr>
        </table>
        <warn>
                        If you are configuring your own kernel, be careful with the <i>grsecurity</i> option. Being too aggressive with your
                        security settings can cause certain programs (such as X) to not run properly. If in doubt, leave it out.
                        </warn>
        <p>Choose a kernel and then merge as follows:</p>
        <pre caption="Emerging Kernel Sources">
# <c>emerge sys-kernel/gentoo-sources</c>
                        </pre>
        <p>Once you have a Linux kernel source tree available, it's time to compile your own custom kernel. 
                        </p>
                <p>Please note that <path>/usr/src/linux</path> is a symlink to your current emerged kernel source package,
                which is set automatically by Portage at emerge time.
                If you have multiple kernel source packages, it is necessary to set the <path>/usr/src/linux</path> symlink
                to the correct one before proceeding.
                </p>
        <pre caption="Compiling the Linux Kernel">
# <c>cd /usr/src/linux</c>
# <c>source /etc/profile</c>
<comment>Again, this updates your paths. If you get an error saying gcc is not found,
this is what you may have to do. </comment>
# <c>make menuconfig</c>
# <c>make dep &amp;&amp; make clean bzImage modules modules_install</c>
# <c>mv /boot/bzImage /boot/bzImage.orig</c>
<comment>[if bzImage already exists]</comment>
# <c>cp /usr/src/linux/arch/i386/boot/bzImage /boot</c>
                        </pre>
        <warn>For your kernel to function properly, there are several options that you will
                        need to ensure are in the kernel proper -- that is, they should <i>be enabled and not
                        compiled as modules</i>.  You will need to enable the <i>&quot;Code maturity
                        level options --&gt; Prompt for development and/or incomplete code/drivers&quot;</i>
                        option to see several of these selections.
                        Under the &quot;File systems&quot; section, be sure to enable the <i>&quot;/dev&quot; file system support</i> (note that
                        you <e>don't</e> need to enable the &quot;/dev/pts file system support&quot; option). You'll also
                        need to enable the <i>&quot;Virtual Memory Filesystem&quot;</i>.  Be sure to enable &quot;ReiserFS&quot; if you have
                        any ReiserFS partitions; the same goes for &quot;Ext3&quot;.  If you're using XFS, enable the 
                        &quot;SGI XFS filesystem support&quot;
                        option.  It's always a good idea to leave ext2
                        enabled whether you are using it or not.    Also, most people using IDE hard drives will
                        want to enable the &quot;USE DMA by default&quot; option; otherwise, your IDE drives may perform
                        very poorly.  Of course, remember to enable &quot;IDE disk&quot; support as well -- otherwise your
                        kernel won't be able to see your IDE disks.
                        </warn>
        <p>If you are using hardware RAID you will need to enable a couple more options in the kernel:    
                        For Highpoint RAID controllers select hpt366 chipset support, support for IDE RAID controllers and Highpoint    
                        370 software RAID.For Promise RAID controllers select PROMISE PDC202{46|62|65|67|68|69|70} support,
                        support for IDE RAID    
                        controllers and Support Promise software RAID (Fasttrak(tm))
                        </p>
        <p>If you use PPPoE to connect to Internet, you will need the following
                        options in the kernel (built-in or as preferably as modules) :
                        &quot;PPP (point-to-point protocol) support&quot;, &quot;PPP support for async serial ports&quot;,
                        &quot;PPP support for sync tty ports&quot;. The two compression options won't harm but
                        are not definitely needed, neither does the &quot;PPP over Ethernet&quot; option,
                        that might only be used by <i>rp-pppoe</i> when configured to do kernel mode PPPoE.
                        </p>
        <p>If you have an IDE cd burner, then you need to enable SCSI emulation in the
                        kernel.  Turn on &quot;ATA/IDE/MFM/RLL support&quot; ---&gt; &quot;IDE, ATA and ATAPI Block 
                        devices&quot; ---&gt; &quot;SCSI emulation support&quot; (I usually make it a module), then
                        under &quot;SCSI support&quot; enable &quot;SCSI support&quot;, &quot;SCSI CD-ROM support&quot; and
                        &quot;SCSI generic support&quot; (again, I usually compile them as modules).  If you
                        also choose to use modules, then <c>echo -e &quot;ide-scsi\nsg\nsr_mod&quot;
                        &gt;&gt; /etc/modules.autoload</c> to have them automatically added at boot time. 
                        </p>
        <note>
                        For those who prefer it, 
                        it is now possible to install Gentoo Linux with a 2.2 kernel.
                        However, doing this comes at a price: 
                        you will lose many of the nifty features that
                        are new to the 2.4 series kernels (such as XFS and tmpfs
                        filesystems, iptables, and more), although the 2.2 kernel sources can be
                        patched with ReiserFS and devfs support.  
                        Gentoo linux boot scripts require either tmpfs or ramdisk support in the kernel, so 
                        2.2 kernel users need to make sure that ramdisk support is compiled in (ie, not a module).
                        It is <comment>vital</comment> that a <e>gentoo=notmpfs</e> flag be added to the kernel
                        line in <path>/boot/grub/grub.conf</path> for the 2.2 kernel so that a ramdisk is mounted
                        for the bootscripts instead of tmpfs.  If you choose not to use devfs, then
                        <e>gentoo=notmpfs,nodevfs</e> should be used instead.
                        </note>
        <p>Your new custom kernel (and modules) are now installed.  Now you need to choose a system
                        logger that you would like to install.  We offer sysklogd, which is the traditional set
                        of system logging daemons.  We also have msyslog and syslog-ng as well as metalog.  Power users seem
                        to gravitate away from sysklogd (not very good performance) and towards the
                        newer alternatives.  
                        If in doubt, you may want to try metalog, since it seems to be quite popular.
                        To merge your logger of choice, type <e>one</e> of the next four lines: 
                        </p>
        <pre caption="Emerging System Logger of Choice">
# <c>emerge app-admin/sysklogd</c>
# <c>rc-update add sysklogd default</c>
<comment>or</comment>
# <c>emerge app-admin/syslog-ng</c>
# <c>rc-update add syslog-ng default</c>
<comment>or</comment>
# <c>emerge app-admin/metalog</c>
# <c>rc-update add metalog default</c>
<comment>or</comment>
# <c>emerge app-admin/msyslog</c>
# <c>rc-update add msyslog default</c>
                        </pre>
        <warn>
                        In the case of syslog-ng you need to create 
                        <path>/etc/syslog-ng/syslog-ng.conf</path>.
                        See <path>/etc/syslog-ng</path> 
                        for a sample configuration file.
                        </warn>
        <impo>
                        Metalog flushes output to the disk in blocks, so messages aren't immediately recorded into
                        the system logs.  If you are trying to debug a daemon, this performance-enhancing behavior
                        is less than helpful.  When your Gentoo Linux system is up and running, you can send
                        metalog a USR1 signal to temporarily turn off this message buffering (meaning that 
                        <i>tail -f <path>/var/log/everything/current</path></i> will now work 
                        in real time, as expected), 
                        and a USR2 signal to turn buffering back on
                        again. If you want to disable buffering permanently, you can change METALOG_OPTS="-B" to METALOG_OPTS="-B -s"
                        in <path>/etc/conf.d/metalog</path>. 
                        </impo>
        <p>Now, you may optionally choose a cron package that you'd like to use.
                        Right now, we offer dcron, fcron and vcron. If you don't know which one to choose,
                        you might as well grab vcron.  They can be installed as follows:
                        </p>
        <pre caption="Choosing a CRON Daemon">
# <c>emerge sys-apps/dcron</c>
# <c>crontab /etc/crontab</c>
<comment>or</comment>
# <c>emerge sys-apps/fcron</c>
# <c>crontab /etc/crontab</c>
<comment>or</comment>
# <c>emerge sys-apps/vcron</c>
<comment>You do not need to run <c>crontab /etc/crontab</c> if using vcron. </comment>
<comment>Don't forget to add your *cron to the proper init level. </comment>
# <c>rc-update add *cron default </c>
                        </pre>
<!--<p>For more information how how cron works under Gentoo Linux,
                        see <uri link="http://lists.gentoo.org/pipermail/gentoo-announce/2002-April/000151.html">this announcement</uri>.</p>-->
        <p>For more information on starting programs and daemons at startup, see the
                        <uri link="/doc/en/rc-scripts.xml">rc-script guide</uri>. 
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: Install Additional Packages</title>
    <section>
      <body>
        <p>If you need rp-pppoe to connect to the net, be aware that at this point
                        it has not been installed. It would be the good time to do it. </p>
        <pre caption="Installing rp-pppoe">
# <c>USE="-X" emerge rp-pppoe</c>
                        </pre>

                <note>The <i>USE="-X"</i> prevents pppoe from installing its optional X interface, which is a good thing,
                because X and its dependencies would also be emerged. You can always recompile <i>rp-pppoe</i> with
                X support later.
                </note>
        <note> Please note that the rp-pppoe is built but not configured.
                        You will have to do it again using <c>adsl-setup</c> when you boot into your Gentoo system
                        for the first time.
                        </note>
        <p>You may need to install some additional packages in the Portage tree
                        if you are using any optional features like XFS, ReiserFS or LVM.  If you're
                        using XFS, you should emerge the <c>xfsprogs</c> package: 
                        </p>
        <pre caption="Emerging Filesystem Tools">
# <c>emerge sys-apps/xfsprogs</c>
<comment>If you'd like to use ReiserFS, you should emerge the ReiserFS tools: </comment>
# <c>emerge sys-apps/reiserfsprogs</c>
<comment>If you'd like to use JFS, you should emerge the JFS tools: </comment>
# <c>emerge jfsutils</c>
<comment>If you're using LVM, you should emerge the <c>lvm-user</c> package: </comment>
# <c>emerge sys-apps/lvm-user</c>
                        </pre>
        <p>If you're a laptop user and wish to use your PCMCIA slots on your first
                        real reboot, you'll want to make sure you install the <i>pcmcia-cs</i> package.
                        </p>
        <pre caption="Emerging PCMCIA-cs">
# <c>emerge sys-apps/pcmcia-cs</c>
                        </pre>
        <warn>You will have to re-emerge <i>pcmcia-cs</i> after installation to get PCMCIA
                        to work.
                        </warn>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: /etc/fstab</title>
    <section>
      <body>
        <p>Your Gentoo Linux system is almost ready for use.  All we need to do now is configure
                        a few important system files and install the GRUB boot loader. 
                        The first file we need to
                        configure is <path>/etc/fstab</path>.  Remember that you should use
                        the <c>notail</c> option for your boot partition if you chose to create a ReiserFS filesystem on it.
                        Remember to specify <c>ext2</c>, <c>ext3</c> or <c>reiserfs</c> filesystem types as appropriate.
                        </p>
        <p>Use something like the <path>/etc/fstab</path> listed below, but of course be sure to replace &quot;BOOT&quot;,
                        &quot;ROOT&quot; and &quot;SWAP&quot; with the actual block devices you are using (such as <c>hda1</c>, etc.)</p>
        <pre caption="Editing fstab"><comment>
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency).  It's safe to drop the noatime options if you want and to 
# switch between notail and tail freely.

# &lt;fs&gt;           &lt;mountpoint&gt;   &lt;type&gt;   &lt;opts&gt;          &lt;dump/pass&gt;

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
</comment>
/dev/BOOT           /boot       ext2     noauto,noatime  1 2
/dev/ROOT           /           ext3     noatime         0 1
/dev/SWAP           none        swap     sw              0 0
/dev/cdroms/cdrom0  /mnt/cdrom  iso9660  noauto,ro       0 0
proc                /proc       proc     defaults        0 0
                        </pre>
        <warn>Please notice that <i>/boot</i> is NOT mounted at boottime.
                        This is to protect the data in <i>/boot</i> from
                        corruption. If you need to access <i>/boot</i>, please mount it!
                        </warn>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: Root Password</title>
    <section>
      <body>
        <p>Before you forget, set the root password by typing: </p>
        <pre caption="Setting the root Password">
# <c>passwd</c>
        </pre>

        <p>You will also want to add a non-root user for everyday use. Please consult
        the <uri link="http://www.gentoo.org/doc/en/faq.xml">Gentoo FAQ</uri>.
        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: /etc/hostname</title>
    <section>
      <body>
        <p>Edit this file so that it contains your fully-qualified domain name on a single line,
                        i.e. <c>mymachine.mydomain.com</c>. 
                        </p>
        <pre caption="Configuring Hostname">
# <c>echo mymachine.mydomain.com &gt; /etc/hostname</c>
                        </pre>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: /etc/hosts</title>
    <section>
      <body>
        <p>This file contains a list of ip addresses and their associated hostnames. 
                        It's used by the system to resolve the IP addresses
                        of any hostnames that may not be in your nameservers.  Here's a template for this file:
                        </p>
        <pre caption="Hosts Template">
127.0.0.1      localhost
<comment># the next line contains your IP for your local LAN, and your associated machine name</comment>
192.168.1.1    mymachine.mydomain.com   mymachine
                        </pre>
        <note>If you are on a DHCP network, it might be helpful to set <i>localhost</i> to your machine's
                        actual hostname. This will help GNOME and many other programs in name resolution.
                        </note>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final Network Configuration</title>
    <section>
      <body>
        <p>Add the names of any modules that are necessary for the proper functioning of your system to 
                        <path>/etc/modules.autoload</path> file (you can also add any options you
                        need to the same line.) When Gentoo Linux boots, these modules will be automatically
                        loaded.  Of particular importance is your ethernet card module, if you happened to compile
                        it as a module:
                        </p>
        <pre caption="/etc/modules.autoload"><comment>This is assuming that you are using a 3com card. 
                Check <path>/lib/modules/`uname -r`/kernel/drivers/net</path> for your card. </comment>
3c59x
                        </pre>
        <p>Edit the <path>/etc/conf.d/net</path> script to get your network configured for your
                        first boot: </p>
        <pre caption="Boottime Network Configuration">
# <c>nano -w /etc/conf.d/net</c>
# <c>rc-update add net.eth0 default</c>
                        </pre>
        <p>If you have multiple network cards you need to create additional <path>net.eth<comment>x</comment></path>
                        scripts for each one (<comment>x</comment> = 1, 2, ...): </p>
        <pre caption="Multiple Network Interfaces">
# <c>cd /etc/init.d</c>
# <c>cp net.eth0 net.eth<comment>x</comment></c>
# <c>rc-update add net.eth<comment>x</comment> default</c>
                        </pre>
        <p>If you have a PCMCIA card installed, have a quick look into 
                        <path>/etc/init.d/pcmcia</path> to verify that things seem all right for your setup,
                        then add this line to the top of <path>/etc/init.d/net.ethx</path>:
                        </p>
        <pre caption="PCMCIA depend in /etc/init.d/net.ethx">
depend() {
        need pcmcia
}
                        </pre>
        <p>This makes sure that the PCMCIA drivers are autoloaded whenever your network is loaded.
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: Configure Basic Settings (including the international keymap setting)</title>
    <section>
      <body>
        <pre caption="Basic Configuration">
# <c>nano -w /etc/rc.conf</c>
                        </pre>
        <p>Follow the directions in the file to configure the basic settings.  
                        All users will want to make sure that <c>CLOCK</c> is set to his/her
                        liking.  International keyboard users will want to set the <c>KEYMAP</c>
                        variable (browse <path>/usr/share/keymaps</path> to see the various
                        possibilities).
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: Configure a Bootloader</title>
        <section>
        <title>Notes</title>
        <body>
        <p> In the spirit of Gentoo, users now have more than one bootloader to choose from.
        Using our virtual package system, users are now able to choose between both GRUB and
        LILO as their bootloaders.
        </p>
        <p> Please keep in mind that having both bootloaders installed is not necessary.
        In fact, it can be a hinderance, so please only choose one.
        </p>
        </body>
        </section>
    <section>
        <title>Configuring GRUB</title>
      <body>
        <p>The most critical part of understanding GRUB is getting comfortable with how GRUB
                        refers to hard drives and partitions. Your Linux partition <path>/dev/hda1</path> is called
                        <path>(hd0,0)</path> under GRUB.  Notice the parenthesis around the hd0,0 - they are required.  
                        Hard drives count from zero rather than &quot;a&quot;, and partitions start at zero rather than one.
                        Be aware too that with the hd devices, only harddrives are counted, not atapi-ide devices such as
                        cdrom players, burners, and that the same construct can be used with scsi drives.
                        (Normally they get higher numbers than ide drives except when the bios is configured
                        to boot from scsi devices.) Assuming you have a harddrive on /dev/hda, a cdrom player on /dev/hdb,
                        a burner on /dev/hdc and a second hardrive on /dev/hdd, for example, and no scsi harddrive
                        <path>/dev/hdd7</path> gets translated to <path>(hd1,6)</path>.

                        It might sound tricky, and tricky it is indeed, but as we will see, grub
                        offers a tab completion mechanism that comes handy for those of you having
                        a lot of harddrives and partitions and who are a little lost in the
                        grub numbering scheme. Having gotten the feel for that,
                        it's time to install GRUB.
                        </p>
        <p>The easiest way to install GRUB is to simply type <c>grub</c> at your chrooted shell prompt: </p>
        <pre caption="Installing GRUB">
# <c>emerge grub</c>
# <c>grub</c>
                        </pre>
        <impo>If you are using hardware RAID this part will not work at
                        this time.
                        Skip to the section on making your <path>grub.conf</path>. After that we will complete the
                        grub setup for RAID controllers
                        </impo>
        <p>You'll be presented with the <c>grub&gt;</c> grub
                        command-line prompt.  Now, you need to type in the
                        right commands to install the GRUB boot record onto your hard drive.  In my example configuration,
                        I want to install the GRUB boot record on my hard drive's MBR (master boot record), so that 
                        the first thing I see when I turn on the computer is the GRUB prompt.  In my case, the commands
                        I want to type are:
                        </p>
        <pre caption="GRUB Commands">
grub&gt; <c>root (hd0,0)</c>
grub&gt; <c>setup (hd0)</c>
<comment>Alternatively, if you wanted to install the bootloader somewhere other than the MBR</comment>
grub&gt; <c>setup (hd0) (hd0,4) </c>
<codenote>The second parameter above identifies the boot partition</codenote>
grub&gt; <c>quit</c>
                        </pre>
        <p>Here's how the two commands work.  The first <c>root ( )</c> command tells GRUB
                        the location of your boot partition (in our example, <path>/dev/hda1</path> or 
                        <path>(hd0,0)</path> in GRUB terminology.  Then, the second <c>setup ( )
                        </c> command tells GRUB where to install the
                        boot record - it will be configured to look for its special files at the <c>root
                        ( )</c> location that you specified.  In my case, I want the boot record on the
                        MBR of the hard drive, so I simply specify <path>/dev/hda</path> (also known as <path>(hd0)</path>). 
                        If I were using another boot loader and wanted to set up GRUB as a secondary boot-loader, I
                        could install GRUB to the boot record of a particular partition.  In that case,
                        I'd specify a particular partition rather than the entire disk.  Once the GRUB
                        boot record has been successfully installed, you can type <c>quit</c> to quit GRUB.  
                        </p>

                        <note> The tab completion mechanism of grub can be used from within grub, 
                        assuming you wrote <c> root (</c> and that you hit the TAB key, you would
                        be prompted with a list of the available devices (not only harddrives), 
                        hitting the TAB key having written <c> root (hd</c>, grub would print the
                        available harddrives and hitting the TAB key after writing <c> root (hd0,</c>
                        would make grub print the list of partitions on the first harddrive.

                        Checking the syntax of the grub location with completion should really help
                        to make the right choice.
                        </note>
                        
                        <p>
                        Gentoo Linux is now
                        installed, but we need to create the <path>/boot/grub/grub.conf</path> file so that
                        we get a nice GRUB boot menu when the system reboots.  Here's how to do it.
                        </p>
        <impo>To ensure backwards compatibility with GRUB, make sure to make a link from
                        <i>grub.conf</i> to <i>menu.lst</i>. You can do this by doing
                        <c>ln -s /boot/grub/grub.conf /boot/grub/menu.lst </c>. </impo>
        <p>Now, create the grub.conf file (<c>nano -w /boot/grub/grub.conf</c>), and add the following to it:
                        </p>
        <pre caption="Grub.conf for GRUB">
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title=My example Gentoo Linux
root (hd0,0) 
kernel (hd0,0)/boot/bzImage root=/dev/hda3 

<comment> #Below is for setup using hardware RAID</comment>
title=My Gentoo Linux on RAID
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/ataraid/discX/partY

<comment># Below needed only for people who dual-boot</comment>
title=Windows NT Workstation
root (hd0,5) 
chainloader +1
                        </pre>
        <note>
                        (hd0,0) should be written without any spaces inside the parentheses.
                        </note>
        <impo>
                        If you set up scsi emulation for an IDE cd burner earlier, then to get it to
                        actually work you need to add an &quot;hdx=ide-scsi&quot; fragment to the kernel
                        line in grub.conf (where &quot;hdx&quot; should be the device for your cd burner).
                        </impo>
        <p>After saving this file, Gentoo Linux installation is complete.  Selecting the first option will
                        tell GRUB to boot Gentoo Linux without a fuss.  The second part of the grub.conf file is optional,
                        and shows you how to use GRUB to boot a bootable Windows partition.
                        </p>
        <note>Above, <path>(hd0,0)</path> should point to your &quot;boot&quot; partition
                        (<path>/dev/hda1</path> in our example config) and <path>/dev/hda3</path> should point to
                        your root filesystem.  <path>(hd0,5)</path> contains the NT boot
                        loader.
                        </note>
        <note>
                        The path to the kernel image is relative to the boot partition. If for example you have separated boot partition <path>(hd0,0)</path> and root partition <path>(hd0,1)</path>, all paths in the grub.conf file above will become <path>/bzImage</path>.
                        </note>
        <p>If you need to pass any additional options to the kernel, simply
                        add them to the end of the <c>kernel</c> command.  We're already passing one option
                        (<c>root=/dev/hda3</c>), but you can pass others as well.  In particular, you can
                        turn off devfs by default (not recommended unless you know what you're doing) by
                        adding the <c>gentoo=nodevfs</c> option to the <c>kernel</c> command.
                        </p>
        <note>Unlike in earlier versions of Gentoo Linux, you no longer have to add 
                        <c>devfs=mount</c> to the end of the <c>kernel</c> line to enable devfs.  In rc6
                        devfs is enabled by default.
                        </note>
      </body>
    </section>
        <section>
    <title>Configuring LILO</title>
      <body>
        <p>While GRUB may be the new alternative for most people, it is not always the best choice.
        LILO, the LInuxLOader, is the tried and true workhorse of Linux bootloaders. Here's how to install
        LILO if you would like to use it instead of GRUB:
        </p>
        <p>The first step is to emerge LILO: 
        </p>
        <pre caption="Emerging LILO">
# <c>emerge lilo</c>
        </pre>
        <p>Now it is time to configure LILO. I will give you a small <i>lilo.conf</i> to use, and I will explain
        the different parts of the file.
        </p>
        <pre caption="Example lilo.conf">
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
lba32
default=linux

image=/boot/vmlinuz-2.4.20
        label=linux
        initrd=/boot/initrd-2.4.20.img
        read-only
        root=/dev/hda5
        
#For dual booting windows/other OS
other=/dev/hda1
        label=dos

        </pre>
        <ul>
        <li><i>boot=/dev/hda</i> tells LILO to install itself on the first hard disk on the first IDE controller. </li>
        <li><i>map=/boot/map</i> states the map file. In normal use, this should not be modified. </li>
        <li><i>install=/boot/boot.b</i> tells LILO to install the specified file as the new boot sector.
        In normal use, this should not be altered. If the install line is missing, LILO will
        assume a default of /boot/boot.b as the file to be used. </li>
        <li>The existence of <i>prompt</i> tells LILO to show you whatever is referenced in the message line.
        While it is not recommended that you remove the prompt line, if you do remove it, you can still
        get a prompt by holding down the [Shift] key while your machine starts to boot. </li>
        <li><i>timeout=50</i> sets the amount of time that LILO will wait for user input before proceeding 
        with booting the default line entry. This is measured in tenths of a second, with 50 as the default. </li>
        <li><i>message=/boot/message</i> refers to the screen that LILO displays to let you select the
        operating system or kernel to boot. </li>
        <li><i>lba32</i> describes the hard disk geometry to LILO. Another common entry here is linear. You should
        not change this line unless you are very aware of what you are doing. Otherwise, you could put
        your system in an unbootable state. </li>
        <li><i>default=linux</i> refers to the default operating system for LILO to boot from the
        options listed below this line. The name linux refers to the label line below in each of the boot options. </li>
        <li><i>image=/boot/vmlinuz-2.4.20</i> specifies the linux kernel to boot with this particular boot option. </li>
        <li><i>label=linux</i> names the operating system option in the LILO screen. In this case,
        it is also the name referred to by the default line. </li>
        <li><i>initrd=/boot/initrd-2.4.20.img</i> refers to the initial ram disk image that is used at boot time
        to actually initialize and start the devices that makes booting the kernel possible. The initial
        ram disk is a collection of machine-specific drivers necessary to operate a SCSI card, hard drive, or any
        other device needed to load the kernel. You should never try to share initial ram disks between machines. </li>
        <li><i>read-only</i> specifies that the root partition (see the root line below) is read-only and cannot be
        altered during the boot process. </li>
        <li><i>root=/dev/hda5</i> tells LILO what disk partition to use as the root partition. </li>
        </ul>
        <note>Thanks to <uri link="http://www.redhat.com">Redhat.com</uri> for this information.
        </note>
        <p>After you have edited your <i>lilo.conf</i> file, it is time to run LILO to load the information
        into the MBR:
        </p>
        <pre caption="Running LILO">
# <c>/sbin/lilo</c>
        </pre>
        <p>LILO is configured, and now your machine is ready to boot into Gentoo Linux!
        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Final steps: Bootdisks</title>
    <section>
      <title>GRUB Bootdisks</title>
      <body>
        <p>It is always a good idea to make a boot disk the first
        time you install any Linux distribution. This is a security
        blanket, and generally not a bad thing to do. If you are using some kinds of hardware RAID, you may <e>need</e> make a GRUB boot
                        disk. With these types of hardware RAID,
                        if you try to install grub from your chrooted shell it will fail. If you are in this camp,
                        make a GRUB
                        boot disk, and when you reboot the first time you can install GRUB
                        to the MBR. Make your
                        bootdisk like this:
                        </p>
        <pre caption="Creating a GRUB Bootdisk">
# <c>mke2fs /dev/fd0</c>
# <c>mount /dev/fd0 /mnt/floppy</c>
# <c>mkdir -p /mnt/floppy/boot/grub</c>
# <c>cp /usr/share/grub/i386-pc/stage1 /mnt/floppy/boot/grub/</c>
# <c>cp /usr/share/grub/i386-pc/stage2 /mnt/floppy/boot/grub/</c>

# <c>grub</c>

grub&gt; <c>root (fd0)</c>
grub&gt; <c>setup (fd0)</c>
grub&gt; <c>quit</c>
                        </pre>
        <p>Now reboot and load the floppy. At the floppy's <c>grub&gt;</c> prompt, you can now execute the necessary <c>root</c>
                and <c>setup</c> commands.</p>
      </body>
    </section>
    <section>
      <title>LILO Bootdisks</title>
      <body>
        <p>If you are using LILO, it is also a good idea to make a bootdisk:
                </p>
        <pre caption="Making a LILO Bootdisk">
# <c>dd if=/boot/your_kernel of=/dev/fd0 </c>
<comment>This will only work if your kernel is smaller than 1.4MB</comment>
                </pre>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Installation Complete!</title>
    <section>
      <body>
        <p>Now, Gentoo Linux is installed.  The only remaining step is to exit the chrooted shell, 
                        udpate necessary configuration files,
                        safely unmount your partitions
                        and reboot the system:
                        </p>
        <pre caption="Rebooting the System">
# <c>etc-update</c>
# <c>exit</c> 
<codenote>This exits the chrooted shell; you can also type <c>^D</c></codenote>
# <c>cd / </c>
# <c>umount /mnt/gentoo/boot</c>
# <c>umount /mnt/gentoo/proc</c>
# <c>umount /mnt/gentoo/dev</c>
# <c>umount /mnt/gentoo</c>
# <c>reboot</c>
                        </pre>
        <note>
                        After rebooting, it is a good idea to run the <c>update-modules</c> command to create
                        the <path>/etc/modules.conf</path> file.  Instead of modifying this file directly, you should
                        generally make changes to the files in <path>/etc/modules.d</path>.
                        </note>
        <impo>Remember if you are running hardware RAID, you must
                        use the bootdisk for the first reboot.
                        then go back and install grub the way everyone else did the first
                        time. You are done --  congratulations!</impo>
        <p>If you have any questions or would like to get involved with Gentoo Linux development, 
                        consider joining our gentoo-user and gentoo-dev mailing lists
                        (there's a &quot;click to subscribe&quot; link on our <uri link="http://www.gentoo.org">main page</uri>).
                        We also have a handy <uri link="http://www.gentoo.org/doc/en/desktop.xml">Desktop configuration guide</uri>
                        that will
                        help you to continue configuring your new Gentoo Linux system, and a useful
                        <uri link="http://www.gentoo.org/doc/en/portage-user.xml">Portage user guide</uri>
                        to help familiarize you with Portage basics. You can find the rest of the Gentoo Documentation
                        <uri link="http://www.gentoo.org/main/en/docs.xml">here</uri>. If you have any other questions
                        involving installation or anything for that matter, please check the Gentoo Linux
                        <uri link="http://www.gentoo.org/doc/en/faq.xml">FAQ</uri>.
                        Enjoy and welcome to Gentoo Linux!
                        </p>
      </body>
    </section>
  </chapter>
  <chapter>
    <title>Gentoo-Stats</title>
    <section>
      <body>
        <p>The Gentoo Linux usage statistics program was started as an attempt to give the developers
                a way to find out about their user base. It collects information about Gentoo Linux usage to help
                us in set priorities our development. Installing it is completely optional, and it would be greatly
                appreciated if you decide to use it. Compiled statistics can be viewed at <uri>http://stats.gentoo.org/</uri>.
                </p>
        <p>The gentoo-stats server will assign a unique ID to your system.
                This ID is used to make sure that each system is counted only once. The ID will not be used
                to individually identify your system, nor will it be mached against an IP address or
                other personal information. Every precaution has been taken to assure your privacy in the
                development of this system. The following are the things that we are monitoring
                right now through our &quot;gentoo-stats&quot; program:
                </p>
        <ul>
          <li>installed packages and their version numbers</li>
          <li>CPU information: speed (MHz), vendor name, model name, CPU flags (like &quot;mmx&quot; or &quot;3dnow&quot;)</li>
          <li>memory information (total available physical RAM, total available swap space)</li>
          <li>PCI cards and network controller chips</li>
          <li>the Gentoo Linux profile your machine is using (that is, where the /etc/make.profile link is pointing to).</li>
        </ul>
        <p>We are aware that disclosure of sensitive information is a threat to most Gentoo Linux users
                (just as it is to the developers).
                </p>
        <ul>
          <li>Unless you modify the gentoo-stats program, it will never transmit sensitive
                information such as your passwords, configuration data, shoe size...</li>
          <li>Transmission of your e-mail addresses is optional and turned off by default.</li>
          <li>The IP address your data transmission originates from will never be logged
                in such a way that we can identify you. There are no &quot;IP address/system ID&quot; pairs.</li>
        </ul>
        <p>The installation is easy - just run the following commands:
                </p>
        <pre caption="Installing gentoo-stats">
# <c>emerge gentoo-stats</c>   <codenote>Installs gentoo-stats</codenote>
# <c>gentoo-stats --new</c>    <codenote>Obtains a new system ID</codenote>
                </pre>
        <p>The second command above will request a new system ID and enter it into
                <path>/etc/gentoo-stats/gentoo-stats.conf</path> automatically. You can view this file
                to see additional configuration options.
                </p>
        <p>After that, the program should be run on a regular schedule
                (gentoo-stats does not have to be run as root). Add this line to your <path>crontab</path>:
                </p>
        <pre caption="Updating gentoo-stats with cron">
          <c>0 0 * * 0,4 /usr/sbin/gentoo-stats --update &gt; /dev/null</c>
        </pre>
        <p>The <c>gentoo-stats</c> program is a simple perl script which can be
                viewed with your favortive pager or editor: <path>/usr/sbin/gentoo-stats</path>.        </p>
      </body>
    </section>
  </chapter>
</guide>