--- xml/htdocs/doc/en/handbook/hb-install-config.xml	2004/08/01 11:20:51	1.39
+++ xml/htdocs/doc/en/handbook/hb-install-config.xml	2006/03/28 10:35:59	1.76
@@ -2,11 +2,15 @@
 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.39 2004/08/01 11:20:51 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.76 2006/03/28 10:35:59 neysx Exp $ -->
 
 <sections>
+
+<version>2.18</version>
+<date>2006-03-28</date>
+
 <section>
 <title>Filesystem Information</title>
 <subsection>
@@ -17,8 +21,8 @@
 Under Linux, all partitions used by the system must be listed in
 <path>/etc/fstab</path>. This file contains the mountpoints of those partitions
 (where they are seen in the file system structure), how they should be mounted
-(special options) and when (automatically or not, can users mount those or not,
-etc.).
+and with what special options (automatically or not, whether users can mount
+them or not, etc.)
 </p>
 
 </body>
@@ -48,7 +52,7 @@
 <li>
   The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it
   wants to mount the partition. As every filesystem has its own mountoptions,
-  you are encouraged to read the mount manpage (<c>man mount</c>) for a full
+  you are encouraged to read the mount man page (<c>man mount</c>) for a full
   listing. Multiple mountoptions are comma-separated.
 </li>
 <li>
@@ -59,12 +63,13 @@
   The sixth field is used by <c>fsck</c> to determine the order in which 
   filesystems should be <b>check</b>ed if the system wasn't shut down properly. 
   The root filesystem should have <c>1</c> while the rest should have <c>2</c> 
-  (or <c>0</c> in case a filesystem check isn't necessary).
+  (or <c>0</c> if a filesystem check isn't necessary).
 </li>
 </ul>
 
 <p>
-So start <c>nano</c> (or your favorite editor) to create your 
+The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
+file</e>, so start <c>nano</c> (or your favorite editor) to create your 
 <path>/etc/fstab</path>:
 </p>
 
@@ -75,7 +80,8 @@
 <p>
 Let us take a look at how we write down the options for the <path>/boot</path>
 partition. This is just an example, so if your architecture doesn't require a
-<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
+<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it
+verbatim.
 </p>
 
 <p>
@@ -90,9 +96,9 @@
 
 <p>
 Some users don't want their <path>/boot</path> partition to be mounted
-automatically. Those people should substitute <c>defaults</c> with
-<c>noauto</c>. This does mean that you need to manually mount this partition
-every time you want to use it.
+automatically to improve their system's security. Those people should 
+substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 
+manually mount this partition every time you want to use it.
 </p>
 
 <p>
@@ -102,7 +108,7 @@
 </p>
 
 <pre caption="An improved /boot line for /etc/fstab">
-/dev/hda1   /boot     ext2    noauto,noatime    1 2
+/dev/hda1   /boot     ext2    defaults,noatime    1 2
 </pre>
 
 <p>
@@ -111,7 +117,7 @@
 </p>
 
 <pre caption="Three /etc/fstab lines">
-/dev/hda1   /boot     ext2    noauto,noatime    1 2
+/dev/hda1   /boot     ext2    defaults,noatime  1 2
 /dev/hda2   none      swap    sw                0 0
 /dev/hda3   /         ext3    noatime           0 1
 </pre>
@@ -123,12 +129,12 @@
 </p>
 
 <pre caption="A full /etc/fstab example">
-/dev/hda1   /boot     ext2    noauto,noatime    1 2
-/dev/hda2   none      swap    sw                0 0
-/dev/hda3   /         ext3    noatime           0 1
+/dev/hda1   /boot     ext2    defaults,noatime     1 2
+/dev/hda2   none      swap    sw                   0 0
+/dev/hda3   /         ext3    noatime              0 1
 
-none        /proc     proc    defaults          0 0
-none        /dev/shm  tmpfs   defaults          0 0
+none        /proc     proc    defaults             0 0
+none        /dev/shm  tmpfs   nodev,nosuid,noexec  0 0
 
 /dev/cdroms/cdrom0    /mnt/cdrom    auto      noauto,user    0 0
 </pre>
@@ -151,14 +157,6 @@
 </pre>
 
 <p>
-If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
-</p>
-
-<pre caption="Adding usbfs filesystem to /etc/fstab">
-none        /proc/bus/usb   usbfs         defaults      0 0
-</pre>
-
-<p>
 Double-check your <path>/etc/fstab</path>, save and quit to continue.
 </p>
 
@@ -184,7 +182,10 @@
 </p>
 
 <pre caption="Setting the hostname">
-# <i>echo tux &gt; /etc/hostname</i>
+# <i>nano -w /etc/conf.d/hostname</i>
+
+<comment>(Set the HOSTNAME variable to your hostname)</comment>
+HOSTNAME="<i>tux</i>"
 </pre>
 
 <p>
@@ -192,7 +193,10 @@
 </p>
 
 <pre caption="Setting the domainname">
-# <i>echo homenetwork &gt; /etc/dnsdomainname</i>
+# <i>nano -w /etc/conf.d/domainname</i>
+
+<comment>(Set the DNSDOMAIN variable to your domain name)</comment>
+DNSDOMAIN="<i>homenetwork</i>"
 </pre>
 
 <p>
@@ -201,15 +205,10 @@
 </p>
 
 <pre caption="Setting the NIS domainname">
-# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
-</pre>
-
-<p>
-Now add the <c>domainname</c> script to the default runlevel:
-</p>
+# <i>nano -w /etc/conf.d/domainname</i>
 
-<pre caption="Adding domainname to the default runlevel">
-# <i>rc-update add domainname default</i>
+<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
+NISDOMAIN="<i>my-nisdomain</i>"
 </pre>
 
 </body>
@@ -220,20 +219,34 @@
 
 <p>
 Before you get that "Hey, we've had that already"-feeling, you should remember
-that the networking you set up in the beginning of the gentoo installation was 
+that the networking you set up in the beginning of the Gentoo installation was 
 just for the installation. Right now you are going to configure networking for 
 your Gentoo system permanently.
 </p>
 
+<note>
+More detailed information about networking, including advanced topics like
+bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
+link="?part=4">Gentoo Network Configuration</uri> section.
+</note>
+
 <p>
 All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
-a straightforward yet not intuitive syntax if you don't know how to setup
-networking manually. But don't fear, we'll explain everything :)
+a straightforward yet not intuitive syntax if you don't know how to set up
+networking manually. But don't fear, we'll explain everything. A fully
+commented example that covers many different configurations is available in
+<path>/etc/conf.d/net.example</path>.
 </p>
 
 <p>
-First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>
-is used in this example):
+DHCP is used by default and does not require any further configuration.
+</p>
+
+<p>
+If you need to configure your network connection either because you need
+specific DHCP options or because you do not use DHCP at all, open
+<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
+this example):
 </p>
 
 <pre caption="Opening /etc/conf.d/net for editing">
@@ -241,54 +254,44 @@
 </pre>
 
 <p>
-The first variable you'll find is <c>iface_eth0</c>. It uses the following
-syntax:
+You will see the following file:
 </p>
 
-<pre caption="iface_eth0 syntaxis">
-iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
+<pre caption="Default /etc/conf.d/net">
+# This blank configuration will automatically use DHCP for any net.*
+# scripts in /etc/init.d.  To create a more complete configuration,
+# please review /etc/conf.d/net.example and save your configuration
+# in /etc/conf.d/net (this file :]!).
 </pre>
 
 <p>
-If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
-to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 
-If you need to setup your network manually and you're 
-not familiar with all the above terms, please read the section on <uri
-link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
-Terminology</uri> if you haven't done so already.
+To enter your own IP address, netmask and gateway, you need
+to set both <c>config_eth0</c> and <c>routes_eth0</c>:
 </p>
 
+<pre caption="Manually setting IP information for eth0">
+config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
+routes_eth0=( "default gw 192.168.0.1" )
+</pre>
+
 <p>
-So let us give three examples; the first one uses DHCP, the second one a static 
-IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 
-gateway 192.168.0.1 while the third one just activates the interface for
-rp-pppoe usage:
+To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
+<c>dhcp_eth0</c>:
 </p>
 
-<pre caption="Examples for /etc/conf.d/net">
-<comment>(For DHCP)</comment>
-iface_eth0="dhcp"
-<comment># Some network admins require that you use the</comment>
-<comment># hostname and domainname provided by the DHCP server.</comment>
-<comment># In that case, add the following to let dhcpcd use them.</comment>
-<comment># That will override your own hostname and domainname definitions.</comment>
-dhcpcd_eth0="-HD"
-<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
-<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
-dhcpcd_eth0="-N"
-
-<comment>(For static IP)</comment>
-iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
-gateway="eth0/192.168.0.1"
-
-<comment>(For rp-pppoe)</comment>
-iface_eth0="up"
+<pre caption="Automatically obtaining an IP address for eth0">
+config_eth0=( "dhcp" )
+dhcp_eth0="nodns nontp nonis"
 </pre>
 
 <p>
-If you have several network interfaces, create extra <c>iface_eth</c> variables,
-like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
-shouldn't be reproduced as you can only set one gateway per computer.
+Please read <path>/etc/conf.d/net.example</path> for a list of all available
+options.
+</p>
+
+<p>
+If you have several network interfaces repeat the above steps for 
+<c>config_eth1</c>, <c>config_eth2</c>, etc.
 </p>
 
 <p>
@@ -302,7 +305,7 @@
 <body>
 
 <p>
-To have your network interfaces activated at boot, you need to add those to the
+To have your network interfaces activated at boot, you need to add them to the
 default runlevel. If you have PCMCIA interfaces you should skip this action as
 the PCMCIA interfaces are started by the PCMCIA init script.
 </p>
@@ -352,11 +355,11 @@
 <p>
 If your system is the only system (or the nameservers handle all name
 resolution) a single line is sufficient. For instance, if you want to call your
-system <c>tux.homenetwork</c>:
+system <c>tux</c>:
 </p>
 
 <pre caption="/etc/hosts for lonely or fully integrated PCs">
-127.0.0.1     tux.homenetwork tux localhost
+127.0.0.1     localhost tux
 </pre>
 
 <p>
@@ -380,8 +383,10 @@
 </note>
 
 <p>
-PCMCIA-users should first install the <c>pcmcia-cs</c> package. The
-<c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment:
+PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
+includes users who will be working with a 2.6 kernel (even though they won't be
+using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary 
+to avoid installing xorg-x11 at this moment:
 </p>
 
 <pre caption="Installing pcmcia-cs">
@@ -402,6 +407,31 @@
 </section>
 <section>
 <title>System Information</title>
+<subsection>
+<title>Root Password</title>
+<body>
+
+<p>
+First we set the root password by typing:
+</p>
+
+<pre caption="Setting the root password">
+# <i>passwd</i>
+</pre>
+
+<p>
+If you want root to be able to log on through the serial console, add 
+<c>tts/0</c> to <path>/etc/securetty</path>:
+</p>
+
+<pre caption="Adding tts/0 to /etc/securetty">
+# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
+</pre>
+
+</body>
+</subsection>
+<subsection>
+<title>System Information</title>
 <body>
 
 <p>
@@ -414,28 +444,100 @@
 </pre>
 
 <p>
+When you're finished configuring <path>/etc/rc.conf</path>, save and exit. 
+</p>
+
+<p>
 As you can see, this file is well commented to help you set up the necessary
-configuration variables. Take special care with the <c>KEYMAP</c> setting: if
-you select the wrong <c>KEYMAP</c> you will get weird results when typing on
-your keyboard.
+configuration variables. You can configure your system to use unicode and
+define your default editor and your display manager (like gdm or kdm).
+</p>
+
+<p>
+Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
+Edit it to configure your keyboard.
+</p>
+
+<pre caption="Opening /etc/conf.d/keymaps">
+# <i>nano -w /etc/conf.d/keymaps</i>
+</pre>
+
+<p>
+Take special care with the <c>KEYMAP</c> variable. If you select the wrong
+<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
 </p>
 
 <note>
 Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 
-select an i386 keymap (such as "us") instead of "sunkeymap".
+select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
+keymaps on most systems. Users who want to be able to use ADB keymaps on boot
+have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
+keymap in <path>/etc/conf.d/keymaps</path>.
 </note>
 
 <p>
-<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 
-ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
-to set a mac/ppc keymap in <path>rc.conf</path>.
+When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
+exit. 
+</p>
+
+<p>
+Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
+according to your needs.
 </p>
 
+<pre caption="Opening /etc/conf.d/clock">
+# <i>nano -w /etc/conf.d/clock</i>
+</pre>
+
 <p>
-When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 
-continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
+If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
+the file. Otherwise you will notice some clock skew. Furthermore, Windows
+assumes that your hardware clock uses local time, so if you want to dualboot,
+you should set this variable appropriately, otherwise your clock will go crazy.
+</p>
+
+<p>
+When you're finished configuring <path>/etc/conf.d/clock</path>, save and
+exit. 
+</p>
+
+<p>
+If you are not installing Gentoo on IBM PPC64 hardware, continue with
+<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>.
 </p>
 
 </body>
+</subsection>
+<subsection>
+<title>Configuring the Console</title>
+<body>
+
+<note>
+The following section applies to the IBM PPC64 hardware platforms.
+</note>
+
+<p>
+If you are running Gentoo on IBM PPC64 hardware and using a virtual console 
+you must uncomment the appropriate line in <path>/etc/inittab</path> for the 
+virtual console to spawn a login prompt.
+</p>
+
+<pre caption="Enabling hvc or hvsi support in /etc/inittab">
+hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
+hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
+</pre>
+
+<p>
+You should also take this time to verify that the appropriate console is 
+listed in <path>/etc/securetty</path>.
+</p>
+
+<p>
+You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary 
+System Tools</uri>.
+</p>
+
+</body>
+</subsection>
 </section>
 </sections>