[gentoo-doc-cvs] cvs commit: handbook-amd64.xml handbook-hppa.xml handbook-ppc.xml handbook-ppc64.xml handbook-sparc.xml handbook-x86.xml hb-install-about.xml hb-install-config.xml hb-install-finalise.xml hb-install-gli-dialog.xml hb-install-gli-medium.xml hb-install-gtkfe.xml hb-install-hppa-bootloader.xml hb-install-hppa-disk.xml hb-install-hppa-kernel.xml hb-install-hppa-medium.xml hb-install-network.xml hb-install-next.xml hb-install-ppc-bootloader.xml hb-install-ppc-disk.xml hb-install-ppc-kernel.xml hb-install-ppc-medium.xml hb-install-ppc64-bootloader.xml hb-install-ppc64-disk.xml hb-install-ppc64-kernel.xml hb-install-ppc64-medium.xml hb-install-sparc-bootloader.xml hb-install-sparc-disk.xml hb-install-sparc-kernel.xml hb-install-sparc-medium.xml hb-install-stage.xml hb-install-system.xml hb-install-tools.xml index.xml

[Joshua Saddler]

nightmorph    08/02/27 22:46:58

  Added:                handbook-amd64.xml handbook-hppa.xml
                        handbook-ppc.xml handbook-ppc64.xml
                        handbook-sparc.xml handbook-x86.xml
                        hb-install-about.xml hb-install-config.xml
                        hb-install-finalise.xml hb-install-gli-dialog.xml
                        hb-install-gli-medium.xml hb-install-gtkfe.xml
                        hb-install-hppa-bootloader.xml
                        hb-install-hppa-disk.xml hb-install-hppa-kernel.xml
                        hb-install-hppa-medium.xml hb-install-network.xml
                        hb-install-next.xml hb-install-ppc-bootloader.xml
                        hb-install-ppc-disk.xml hb-install-ppc-kernel.xml
                        hb-install-ppc-medium.xml
                        hb-install-ppc64-bootloader.xml
                        hb-install-ppc64-disk.xml
                        hb-install-ppc64-kernel.xml
                        hb-install-ppc64-medium.xml
                        hb-install-sparc-bootloader.xml
                        hb-install-sparc-disk.xml
                        hb-install-sparc-kernel.xml
                        hb-install-sparc-medium.xml hb-install-stage.xml
                        hb-install-system.xml hb-install-tools.xml
                        index.xml
  Log:
  moved 2007.1 to 2008.0. i now officially hate cvs. bah. humbug.

Revision  Changes    Path
1.1                  xml/htdocs/doc/en/handbook/2008.0/handbook-amd64.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-amd64.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-amd64.xml?rev=1.1&content-type=text/plain

Index: handbook-amd64.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-amd64.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<book link="/doc/en/handbook/2007.1/handbook-amd64.xml" disclaimer="draft">
<title>Gentoo Linux 2007.1 AMD64 Networkless Handbook</title>

<values>
 <key id="arch">AMD64</key>
 <key id="release-dir">releases/amd64/2007.1/</key>
 <key id="online-book">2007.1/handbook-amd64.xml</key>
</values>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>
<author title="Author">
  <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Author">
  <mail link="uberlord@g.o">Roy Marples</mail>
</author>
<author title="Author">
    <mail link="drobbins@g.o">Daniel Robbins</mail>
</author>
<author title="Author">
  <mail link="chouser@g.o">Chris Houser</mail>
</author>
<author title="Author">
  <mail link="jerry@g.o">Jerry Alexandratos</mail>
</author>
<author title="Author">
  <mail link="nightmorph@g.o">Joshua Saddler</mail>
</author>
<author title="Gentoo x86 Developer">
  <mail link="seemant@g.o">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
  <mail link="taviso@g.o">Tavis Ormandy</mail>
</author>
<!-- Does not want to be listed on the rendered page
<author title="Gentoo Developer">
  Aron Griffis
</author>
-->
<author title="Gentoo AMD64 Developer">
  <mail link="jhuebel@g.o">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
  <mail link="gmsoft@g.o">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
   <mail link="pvdabeel@g.o">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
  <mail link="blademan@g.o">Joe Kallar</mail>
</author>
<author title="Editor">
    <mail link="zhen@g.o">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
    <mail link="stocke2@g.o">Eric Stockbridge</mail>
</author>
<author title="Editor">
    <mail link="rajiv@g.o">Rajiv Manglani</mail>
</author>
<author title="Editor">
    <mail link="seo@g.o">Jungmin Seo</mail>
</author>
<author title="Editor">
    <mail link="zhware@g.o">Stoyan Zhekov</mail>
</author>
<author title="Editor">
    <mail link="jhhudso@g.o">Jared Hudson</mail>
</author>
<author title="Editor">
    <mail link="peitolm@g.o">Colin Morey</mail>
</author>
<author title="Editor">
    <mail link="peesh@g.o">Jorge Paulo</mail>
</author>
<author title="Editor">
    <mail link="carl@g.o">Carl Anderson</mail>
</author>
<author title="Editor">
    <mail link="avenj@g.o">Jon Portnoy</mail>
</author>
<author title="Editor">
     <mail link="klasikahl@g.o">Zack Gilburd</mail>
</author>
<author title="Editor">
  <mail link="jmorgan@g.o">Jack Morgan</mail>
</author>
<author title="Editor">
  <mail link="bennyc@g.o">Benny Chuang</mail>
</author>
<author title="Editor">
  <mail link="erwin@g.o">Erwin</mail>
</author>
<author title="Editor">
  <mail link="kumba@g.o">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="fox2mike@g.o">Shyam Mani</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>
<author title="Contributor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>

<abstract>
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux
information. This handbook contains the installation instructions for a
networkless installation on AMD64 &amp; EM64T systems and parts about working
with Gentoo and Portage.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>9.0</version>
<date>2007-06-06</date>

<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>

<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about.
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Booting the Installer LiveCD</title>
<abstract>
Using our Installer LiveCD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
  <include href="hb-install-gli-medium.xml"/>
</chapter>

<chapter>
<title>Using the GTK+ based Gentoo Linux Installer</title>
<abstract>
You now have an option of using our graphical installer to install Gentoo.
Configure the options you need through an easy to use GUI and you're ready to
go.
</abstract>
  <include href="hb-install-gtkfe.xml" />
</chapter>

<chapter>
<title>Using the Dialog based Gentoo Linux Installer</title>
<abstract>
You also have an option of using our text based installer to install Gentoo.
Configure the options you need through an easy to use set of menus and you're
ready to go.
</abstract>
  <include href="hb-install-gli-dialog.xml" />
</chapter>

<chapter>
<title>Where to go from here?</title>
<abstract>
Now you have your Gentoo system, but what's next?
</abstract>
  <include href="hb-install-next.xml"/>
</chapter>
</part>

<part>
<title>Working with Gentoo</title>
<abstract>
Learn how to work with Gentoo: installing software, altering variables,
changing Portage behaviour etc.
</abstract>

<chapter>
<title>A Portage Introduction</title>
<abstract>
This chapter explains the "simple" steps a user definitely needs to know to
maintain the software on his system.
</abstract>
  <include href="../hb-working-portage.xml"/>
</chapter>

<chapter>
<title>USE flags</title>
<abstract>
USE flags are a very important aspect of Gentoo. In this chapter, you learn to
work with USE flags and understand how USE flags interact with your system.
</abstract>
  <include href="../hb-working-use.xml"/>
</chapter>

<chapter>
<title>Portage Features</title>
<abstract>
Discover the features Portage has, such as support for distributed compiling,
ccache and more.
</abstract>
  <include href="../hb-working-features.xml"/>
</chapter>

<chapter>
<title>Initscripts</title>
<abstract>
Gentoo uses a special initscript format which, amongst other features, allows
dependency-driven decisions and virtual initscripts. This chapter explains all
these aspects and explains how to deal with these scripts.
</abstract>
  <include href="../hb-working-rcscripts.xml"/>
</chapter>

<chapter>
<title>Environment Variables</title>
<abstract>
With Gentoo you can easily manage the environment variables for your system.
This chapter explains how you do that, and also describes frequently used
variables.
</abstract>
  <include href="../hb-working-variables.xml"/>
</chapter>
</part>

<part>
<title>Working with Portage</title>
<abstract>
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's
Software Management Tool.
</abstract>

<chapter>
<title>Files and Directories</title>
<abstract>
Once you want to know Portage in-depth you need to know where it stores its
files and data.
</abstract>
  <include href="../hb-portage-files.xml"/>
</chapter>

<chapter>
<title>Configuring through Variables</title>
<abstract>
Portage is completely configurable through various variables you can set in the
configuration file or as environment variable.
</abstract>
  <include href="../hb-portage-configuration.xml"/>
</chapter>

<chapter>
<title>Mixing Software Branches</title>
<abstract>
Gentoo provides software separated in several branches, depending on stability
and architectural support. "Mixing Software Branches" inform you how these
branches can be configured and how you can override this separation
individually.
</abstract>
  <include href="../hb-portage-branches.xml"/>
</chapter>

<chapter>
<title>Additional Portage Tools</title>
<abstract>
Portage comes with a few extra tools that might make your Gentoo experience even
better. Read on to discover how to use dispatch-conf and other tools.
</abstract>
  <include href="../hb-portage-tools.xml"/>
</chapter>

<chapter>
<title>Diverting from the Official Tree</title>
<abstract>
"Diverting from the Official Tree" gives you some tips and tricks on how to use
your own Portage tree, how to synchronise only the categories you want, inject
packages and more.
</abstract>
  <include href="../hb-portage-diverttree.xml"/>
</chapter>
</part>

<part>
<title>Gentoo Network Configuration</title>
<abstract>A comprehensive guide to Networking in Gentoo.</abstract>

<chapter>
<title>Getting Started</title>
<abstract>
A guide to quickly get your network interface up and running in most common
environments.
</abstract>
<include href="../hb-net-start.xml"/>
</chapter>

<chapter>
<title>Advanced Configuration</title>
<abstract>
Here we learn about how the configuration works - you need to know this
before we learn about modular networking.
</abstract>
<include href="../hb-net-advanced.xml"/>
</chapter>

<chapter>
<title>Modular Networking</title>
<abstract>
Gentoo provides you flexible networking - here you are told about choosing
different DHCP clients, setting up bonding, bridging, VLANs and more.
</abstract>
<include href="../hb-net-modules.xml"/>
</chapter>

<chapter>
<title>Wireless Networking</title>
<abstract>
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
<include href="../hb-net-wireless.xml"/>
</chapter>

<chapter>
<title>Adding Functionality</title>
<abstract>
If you're feeling adventurous, you can add your own functions to networking.
</abstract>
<include href="../hb-net-functions.xml"/>
</chapter>

<chapter>
<title>Network Management</title>
<abstract>
For laptop users or people who move their computer around different networks.
</abstract>
<include href="../hb-net-management.xml"/>
</chapter>
</part>

</book>



1.1                  xml/htdocs/doc/en/handbook/2008.0/handbook-hppa.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-hppa.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-hppa.xml?rev=1.1&content-type=text/plain

Index: handbook-hppa.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-hppa.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<book link="/doc/en/handbook/2007.1/handbook-hppa.xml" disclaimer="draft">
<title>Gentoo Linux 2007.1 HPPA Networkless Handbook</title>

<values>
 <key id="arch">HPPA</key>
 <key id="/boot">/dev/sda2</key>
 <key id="kernel-version">2.6.20.1-hppa</key>
 <key id="kernel-name">kernel-2.6.20.1-hppa</key>
 <key id="online-book">2007.1/handbook-hppa.xml</key>
 <key id="release-dir">releases/hppa/2007.1/hppa2.0/</key>
 <key id="stage3">stage3-hppa2.0-2007.1.tar.bz2</key>
 <key id="CFLAGS">-march=2.0 -O2 -pipe</key>
</values>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>
<author title="Author">
  <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Author">
  <mail link="uberlord@g.o">Roy Marples</mail>
</author>
<author title="Author">
    <mail link="drobbins@g.o">Daniel Robbins</mail>
</author>
<author title="Author">
  <mail link="chouser@g.o">Chris Houser</mail>
</author>
<author title="Author">
  <mail link="jerry@g.o">Jerry Alexandratos</mail>
</author>
<author title="Gentoo x86 Developer">
  <mail link="seemant@g.o">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
  <mail link="taviso@g.o">Tavis Ormandy</mail>
</author><!-- Does not want to be listed on the rendered page
<author title="Gentoo Developer">
  Aron Griffis
</author>
-->
<author title="Gentoo AMD64 Developer">
  <mail link="jhuebel@g.o">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
  <mail link="gmsoft@g.o">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
   <mail link="pvdabeel@g.o">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
  <mail link="blademan@g.o">Joe Kallar</mail>
</author>
<author title="Editor">
    <mail link="zhen@g.o">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
    <mail link="stocke2@g.o">Eric Stockbridge</mail>
</author>
<author title="Editor">
    <mail link="rajiv@g.o">Rajiv Manglani</mail>
</author>
<author title="Editor">
    <mail link="seo@g.o">Jungmin Seo</mail>
</author>
<author title="Editor">
    <mail link="zhware@g.o">Stoyan Zhekov</mail>
</author>
<author title="Editor">
    <mail link="jhhudso@g.o">Jared Hudson</mail>
</author>
<author title="Editor">
    <mail link="peitolm@g.o">Colin Morey</mail>
</author>
<author title="Editor">
    <mail link="peesh@g.o">Jorge Paulo</mail>
</author>
<author title="Editor">
    <mail link="carl@g.o">Carl Anderson</mail>
</author>
<author title="Editor">
    <mail link="avenj@g.o">Jon Portnoy</mail>
</author>
<author title="Editor">
     <mail link="klasikahl@g.o">Zack Gilburd</mail>
</author>
<author title="Editor">
  <mail link="jmorgan@g.o">Jack Morgan</mail>
</author>
<author title="Editor">
  <mail link="bennyc@g.o">Benny Chuang</mail>
</author>
<author title="Editor">
  <mail link="erwin@g.o">Erwin</mail>
</author>
<author title="Editor">
  <mail link="kumba@g.o">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="nightmorph@g.o">Joshua Saddler</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>
<author title="Contributor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>

<abstract>
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux
information. This handbook contains the installation instructions for a
networkless installation on HPPA systems and parts about working with Gentoo
and Portage.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>9.0</version>
<date>2007-06-06</date>

<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>

<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about. 
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Booting the Universal Installation CD</title>
<abstract>
Using our Universal Installation CD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
  <include href="hb-install-hppa-medium.xml"/>
</chapter>

<chapter>
<title>Configuring your Network</title>
<abstract>
If you need networking, this is the place where the network (and Internet
connection) is configured.
</abstract>
  <include href="hb-install-network.xml"/>
</chapter>

<chapter>
<title>Preparing the Disks</title>
<abstract>
To be able to install Gentoo, you must create the necessary partitions.
This chapter describes how to partition a disk for future usage.
</abstract>
  <include href="hb-install-hppa-disk.xml"/>
</chapter>

<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
Gentoo installs work through so-called stage-files. In this chapter we
describe how you extract a stage-file and configure Portage.
</abstract>
  <include href="hb-install-stage.xml"/>
</chapter>

<chapter>
<title>Chrooting into the Gentoo Base System</title>
<abstract>
Now that the stage3 file is extracted, we chroot into the new system and modify
the USE variable.
</abstract>
  <include href="hb-install-system.xml"/>
</chapter>

<chapter>
<title>Configuring the Kernel</title>
<abstract>
The Linux kernel is the core of every distribution. This chapter
explains how to configure your kernel.
</abstract>
  <include href="hb-install-hppa-kernel.xml"/>
</chapter>

<chapter>
<title>Configuring your System</title>
<abstract>
You need to edit some important configuration files. In this chapter
you receive an overview of these files and an explanation on how to
proceed.
</abstract>
  <include href="hb-install-config.xml"/>
</chapter>

<chapter>
<title>Installing Necessary System Tools</title>
<abstract>
As mentioned before, Gentoo is about customization. In this chapter we help you
choose and install some important tools.
</abstract>
  <include href="hb-install-tools.xml"/>
</chapter>

<chapter>
<title>Configuring the Bootloader</title>
<abstract>
In this chapter we'll describe the PALO bootloader
and step you through the process of configuring PALO to your
needs.
</abstract>
  <include href="hb-install-hppa-bootloader.xml"/>
</chapter>

<chapter>
<title>Finalizing your Gentoo Installation</title>
<abstract>
You're almost done. We'll just create one (or more) users for your
system and (optionally) install prebuilt packages.
</abstract>
  <include href="hb-install-finalise.xml"/>
</chapter>

<chapter>
<title>Where to go from here?</title>
<abstract>
Now you have your Gentoo system, but what's next? 
</abstract>
  <include href="hb-install-next.xml"/>
</chapter>
</part>

<part>
<title>Working with Gentoo</title>
<abstract>
Learn how to work with Gentoo: installing software, altering variables, changing
Portage behaviour etc. 
</abstract>

<chapter>
<title>A Portage Introduction</title>
<abstract>
This chapter explains the "simple" steps a user definitely needs to know to
maintain the software on his system.
</abstract>
  <include href="../hb-working-portage.xml"/>
</chapter>

<chapter>
<title>USE flags</title>
<abstract>
USE flags are a very important aspect of Gentoo. In this chapter, you learn to
work with USE flags and understand how USE flags interact with your system.
</abstract>
  <include href="../hb-working-use.xml"/>
</chapter>

<chapter>
<title>Portage Features</title>
<abstract>
Discover the features Portage has, such as support for distributed compiling,
ccache and more.
</abstract>
  <include href="../hb-working-features.xml"/>
</chapter>

<chapter>
<title>Initscripts</title>
<abstract>
Gentoo uses a special initscript format which, amongst other features, allows
dependency-driven decisions and virtual initscripts. This chapter explains all
these aspects and explains how to deal with these scripts.
</abstract>
  <include href="../hb-working-rcscripts.xml"/>
</chapter>

<chapter>
<title>Environment Variables</title>
<abstract>
With Gentoo you can easily manage the environment variables for your system.
This chapter explains how you do that, and also describes frequently used
variables.
</abstract>
  <include href="../hb-working-variables.xml"/>
</chapter>
</part>

<part>
<title>Working with Portage</title>
<abstract>
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's
Software Management Tool.
</abstract>

<chapter>
<title>Files and Directories</title>
<abstract>
Once you want to know Portage in-depth you need to know where it stores its
files and data.
</abstract>
  <include href="../hb-portage-files.xml"/>
</chapter>

<chapter>
<title>Configuring through Variables</title>
<abstract>
Portage is completely configurable through various variables you can set in the
configuration file or as environment variable.
</abstract>
  <include href="../hb-portage-configuration.xml"/>
</chapter>

<chapter>
<title>Mixing Software Branches</title>
<abstract>
Gentoo provides software separated in several branches, depending on stability
and architectural support. "Mixing Software Branches" inform you how these
branches can be configured and how you can override this separation
individually.
</abstract>
  <include href="../hb-portage-branches.xml"/>
</chapter>

<chapter>
<title>Additional Portage Tools</title>
<abstract>
Portage comes with a few extra tools that might make your Gentoo experience even
better. Read on to discover how to use dispatch-conf and other tools.
</abstract>
  <include href="../hb-portage-tools.xml"/>
</chapter>

<chapter>
<title>Diverting from the Official Tree</title>
<abstract>
"Diverting from the Official Tree" gives you some tips and tricks on how to use
your own Portage tree, how to synchronise only the categories you want, inject
packages and more.
</abstract>
  <include href="../hb-portage-diverttree.xml"/>
</chapter>
</part>

<part>
<title>Gentoo Network Configuration</title>
<abstract>A comprehensive guide to Networking in Gentoo.</abstract>

<chapter>
<title>Getting Started</title>
<abstract>
A guide to quickly get your network interface up and running in most common
environments.
</abstract>
<include href="../hb-net-start.xml"/>
</chapter>

<chapter>
<title>Advanced Configuration</title>
<abstract>
Here we learn about how the configuration works - you need to know this
before we learn about modular networking.
</abstract>
<include href="../hb-net-advanced.xml"/>
</chapter>

<chapter>
<title>Modular Networking</title>
<abstract>
Gentoo provides you flexible networking - here you are told about choosing
different DHCP clients, setting up bonding, bridging, VLANs and more.
</abstract>
<include href="../hb-net-modules.xml"/>
</chapter>

<chapter>
<title>Wireless Networking</title>
<abstract>
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
<include href="../hb-net-wireless.xml"/>
</chapter>

<chapter>
<title>Adding Functionality</title>
<abstract>
If you're feeling adventurous, you can add your own functions to networking.
</abstract>
<include href="../hb-net-functions.xml"/>
</chapter>

<chapter>
<title>Network Management</title>
<abstract>
For laptop users or people who move their computer around different networks.
</abstract>
<include href="../hb-net-management.xml"/>
</chapter>
</part>

</book>



1.1                  xml/htdocs/doc/en/handbook/2008.0/handbook-ppc.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-ppc.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-ppc.xml?rev=1.1&content-type=text/plain

Index: handbook-ppc.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-ppc.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<book link="/doc/en/handbook/2007.1/handbook-ppc.xml" disclaimer="draft">
<title>Gentoo Linux 2007.1 PPC Networkless Handbook</title>

<values>
 <key id="arch">PPC</key>
 <key id="kernel-version">2.6.19-r5</key>
 <key id="kernel-name">kernel-2.6.19-gentoo-r5</key>
 <key id="kernel-gentoo">2.6.19-gentoo-r5</key>
 <key id="online-book">2007.1/handbook-ppc.xml</key>
 <key id="release-dir">releases/ppc/2007.1/ppc32/</key>
 <key id="stage3">stage3-ppc-2007.1.tar.bz2</key>
 <key id="CFLAGS">-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe</key>
</values>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>
<author title="Author">
  <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Author">
  <mail link="uberlord@g.o">Roy Marples</mail>
</author>
<author title="Author">
    <mail link="drobbins@g.o">Daniel Robbins</mail>
</author>
<author title="Author">
  <mail link="chouser@g.o">Chris Houser</mail>
</author>
<author title="Author">
  <mail link="jerry@g.o">Jerry Alexandratos</mail>
</author>
<author title="Gentoo x86 Developer">
  <mail link="seemant@g.o">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
  <mail link="taviso@g.o">Tavis Ormandy</mail>
</author><!-- Does not want to be listed on the rendered page
<author title="Gentoo Developer">
  Aron Griffis
</author>
-->
<author title="Gentoo AMD64 Developer">
  <mail link="jhuebel@g.o">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
  <mail link="gmsoft@g.o">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
   <mail link="pvdabeel@g.o">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
  <mail link="blademan@g.o">Joe Kallar</mail>
</author>
<author title="Editor">
    <mail link="zhen@g.o">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
    <mail link="stocke2@g.o">Eric Stockbridge</mail>
</author>
<author title="Editor">
    <mail link="rajiv@g.o">Rajiv Manglani</mail>
</author>
<author title="Editor">
    <mail link="seo@g.o">Jungmin Seo</mail>
</author>
<author title="Editor">
    <mail link="zhware@g.o">Stoyan Zhekov</mail>
</author>
<author title="Editor">
    <mail link="jhhudso@g.o">Jared Hudson</mail>
</author>
<author title="Editor">
    <mail link="peitolm@g.o">Colin Morey</mail>
</author>
<author title="Editor">
    <mail link="peesh@g.o">Jorge Paulo</mail>
</author>
<author title="Editor">
    <mail link="carl@g.o">Carl Anderson</mail>
</author>
<author title="Editor">
    <mail link="avenj@g.o">Jon Portnoy</mail>
</author>
<author title="Editor">
     <mail link="klasikahl@g.o">Zack Gilburd</mail>
</author>
<author title="Editor">
  <mail link="jmorgan@g.o">Jack Morgan</mail>
</author>
<author title="Editor">
  <mail link="bennyc@g.o">Benny Chuang</mail>
</author>
<author title="Editor">
  <mail link="erwin@g.o">Erwin</mail>
</author>
<author title="Editor">
  <mail link="kumba@g.o">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>
<author title="Editor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>
<author title="Editor">
   <mail link="sejo@g.o">Jochen Maes </mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="josejx@g.o">Joseph Jezak</mail>
</author>
<author title="Editor">
  <mail link="nightmorph@g.o">Joshua Saddler</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>

<abstract>
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux
information. This handbook contains the installation instructions for a
networkless installation on PPC systems and parts about working with Gentoo and
Portage.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>9.0</version>
<date>2007-06-06</date>

<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>

<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about. 
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Booting the Universal Installation CD</title>
<abstract>
Using our Universal Installation CD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
  <include href="hb-install-ppc-medium.xml"/>
</chapter>

<chapter>
<title>Configuring your Network</title>
<abstract>
If you need networking, this is the place where the network (and Internet
connection) is configured.
</abstract>
  <include href="hb-install-network.xml"/>
</chapter>

<chapter>
<title>Preparing the Disks</title>
<abstract>
To be able to install Gentoo, you must create the necessary partitions.
This chapter describes how to partition a disk for future usage.
</abstract>
  <include href="hb-install-ppc-disk.xml"/>
</chapter>

<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
In this chapter we describe how you extract a stage3 file and how to configure
Portage.
</abstract>
  <include href="hb-install-stage.xml"/>
</chapter>

<chapter>
<title>Chrooting into the Gentoo Base System</title>
<abstract>
Now that the stage3 file is extracted, we chroot into the new system and modify
the USE variable.
</abstract>
  <include href="hb-install-system.xml"/>
</chapter>

<chapter>
<title>Configuring the Kernel</title>
<abstract>
The Linux kernel is the core of every distribution. This chapter
explains how to configure your kernel.
</abstract>
  <include href="hb-install-ppc-kernel.xml"/>
</chapter>

<chapter>
<title>Configuring your System</title>
<abstract>
You need to edit some important configuration files. In this chapter
you receive an overview of these files and an explanation on how to
proceed.
</abstract>
  <include href="hb-install-config.xml"/>
</chapter>

<chapter>
<title>Installing Necessary System Tools</title>
<abstract>
As mentioned before, Gentoo is about customization. In this chapter we help you
choose and install some important tools.
</abstract>
  <include href="hb-install-tools.xml"/>
</chapter>

<chapter>
<title>Configuring the Bootloader</title>
<abstract>
Several bootloaders exist. Each one of them has its own way of
configuration. In this chapter we'll describe all possibilities for you
and step you through the process of configuring a bootloader to your
needs.
</abstract>
  <include href="hb-install-ppc-bootloader.xml"/>
</chapter>

<chapter>
<title>Finalizing your Gentoo Installation</title>
<abstract>
You're almost done. We'll just create one (or more) users for your
system and (optionally) install prebuilt packages.
</abstract>
  <include href="hb-install-finalise.xml"/>
</chapter>

<chapter>
<title>Where to go from here?</title>
<abstract>
Now you have your Gentoo system, but what's next? 
</abstract>
  <include href="hb-install-next.xml"/>
</chapter>
</part>

<part>
<title>Working with Gentoo</title>
<abstract>
Learn how to work with Gentoo: installing software, altering variables, changing
Portage behaviour etc. 
</abstract>

<chapter>
<title>A Portage Introduction</title>
<abstract>
This chapter explains the "simple" steps a user definitely needs to know to
maintain the software on his system.
</abstract>
  <include href="../hb-working-portage.xml"/>
</chapter>

<chapter>
<title>USE flags</title>
<abstract>
USE flags are a very important aspect of Gentoo. In this chapter, you learn to
work with USE flags and understand how USE flags interact with your system.
</abstract>
  <include href="../hb-working-use.xml"/>
</chapter>

<chapter>
<title>Portage Features</title>
<abstract>
Discover the features Portage has, such as support for distributed compiling,
ccache and more.
</abstract>
  <include href="../hb-working-features.xml"/>
</chapter>

<chapter>
<title>Initscripts</title>
<abstract>
Gentoo uses a special initscript format which, amongst other features, allows
dependency-driven decisions and virtual initscripts. This chapter explains all
these aspects and explains how to deal with these scripts.
</abstract>
  <include href="../hb-working-rcscripts.xml"/>
</chapter>

<chapter>
<title>Environment Variables</title>
<abstract>
With Gentoo you can easily manage the environment variables for your system.
This chapter explains how you do that, and also describes frequently used
variables.
</abstract>
  <include href="../hb-working-variables.xml"/>
</chapter>
</part>

<part>
<title>Working with Portage</title>
<abstract>
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's
Software Management Tool.
</abstract>

<chapter>
<title>Files and Directories</title>
<abstract>
Once you want to know Portage in-depth you need to know where it stores its
files and data.
</abstract>
  <include href="../hb-portage-files.xml"/>
</chapter>

<chapter>
<title>Configuring through Variables</title>
<abstract>
Portage is completely configurable through various variables you can set in the
configuration file or as environment variable.
</abstract>
  <include href="../hb-portage-configuration.xml"/>
</chapter>

<chapter>
<title>Mixing Software Branches</title>
<abstract>
Gentoo provides software separated in several branches, depending on stability
and architectural support. "Mixing Software Branches" inform you how these
branches can be configured and how you can override this separation
individually.
</abstract>
  <include href="../hb-portage-branches.xml"/>
</chapter>

<chapter>
<title>Additional Portage Tools</title>
<abstract>
Portage comes with a few extra tools that might make your Gentoo experience even
better. Read on to discover how to use dispatch-conf and other tools.
</abstract>
  <include href="../hb-portage-tools.xml"/>
</chapter>

<chapter>
<title>Diverting from the Official Tree</title>
<abstract>
"Diverting from the Official Tree" gives you some tips and tricks on how to use
your own Portage tree, how to synchronise only the categories you want, inject
packages and more.
</abstract>
  <include href="../hb-portage-diverttree.xml"/>
</chapter>
</part>

<part>
<title>Gentoo Network Configuration</title>
<abstract>A comprehensive guide to Networking in Gentoo.</abstract>

<chapter>
<title>Getting Started</title>
<abstract>
A guide to quickly get your network interface up and running in most common
environments.
</abstract>
<include href="../hb-net-start.xml"/>
</chapter>

<chapter>
<title>Advanced Configuration</title>
<abstract>
Here we learn about how the configuration works - you need to know this
before we learn about modular networking.
</abstract>
<include href="../hb-net-advanced.xml"/>
</chapter>

<chapter>
<title>Modular Networking</title>
<abstract>
Gentoo provides you flexible networking - here you are told about choosing
different DHCP clients, setting up bonding, bridging, VLANs and more.
</abstract>
<include href="../hb-net-modules.xml"/>
</chapter>

<chapter>
<title>Wireless Networking</title>
<abstract>
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
<include href="../hb-net-wireless.xml"/>
</chapter>

<chapter>
<title>Adding Functionality</title>
<abstract>
If you're feeling adventurous, you can add your own functions to networking.
</abstract>
<include href="../hb-net-functions.xml"/>
</chapter>

<chapter>
<title>Network Management</title>
<abstract>
For laptop users or people who move their computer around different networks.
</abstract>
<include href="../hb-net-management.xml"/>
</chapter>
</part>

</book>



1.1                  xml/htdocs/doc/en/handbook/2008.0/handbook-ppc64.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-ppc64.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-ppc64.xml?rev=1.1&content-type=text/plain

Index: handbook-ppc64.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-ppc64.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<book link="/doc/en/handbook/2007.1/handbook-ppc64.xml" disclaimer="draft">
<title>Gentoo Linux 2007.1 PPC64 Networkless Handbook</title>

<values>
 <key id="arch">PPC64</key>
 <key id="kernel-version">2.6.19-r7</key>
 <key id="kernel-name">kernel-2.6.19-gentoo-r7</key>
 <key id="online-book">2007.1/handbook-ppc64.xml</key>
 <key id="release-dir">releases/ppc/2007.1/ppc64/</key>
 <key id="stage3">stage3-ppc64-32ul-2007.1.tar.bz2</key>
 <key id="CFLAGS">-O2 -pipe</key>
</values>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>
<author title="Author">
  <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Author">
  <mail link="uberlord@g.o">Roy Marples</mail>
</author>
<author title="Author">
    <mail link="drobbins@g.o">Daniel Robbins</mail>
</author>
<author title="Author">
  <mail link="chouser@g.o">Chris Houser</mail>
</author>
<author title="Author">
  <mail link="jerry@g.o">Jerry Alexandratos</mail>
</author>
<author title="Gentoo x86 Developer">
  <mail link="seemant@g.o">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
  <mail link="taviso@g.o">Tavis Ormandy</mail>
</author><!-- Does not want to be listed on the rendered page
<author title="Gentoo Developer">
  Aron Griffis
</author>
-->
<author title="Gentoo AMD64 Developer">
  <mail link="jhuebel@g.o">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
  <mail link="gmsoft@g.o">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
   <mail link="pvdabeel@g.o">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
  <mail link="blademan@g.o">Joe Kallar</mail>
</author>
<author title="Editor">
    <mail link="zhen@g.o">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
    <mail link="stocke2@g.o">Eric Stockbridge</mail>
</author>
<author title="Editor">
    <mail link="rajiv@g.o">Rajiv Manglani</mail>
</author>
<author title="Editor">
    <mail link="seo@g.o">Jungmin Seo</mail>
</author>
<author title="Editor">
    <mail link="zhware@g.o">Stoyan Zhekov</mail>
</author>
<author title="Editor">
    <mail link="jhhudso@g.o">Jared Hudson</mail>
</author>
<author title="Editor">
    <mail link="peitolm@g.o">Colin Morey</mail>
</author>
<author title="Editor">
    <mail link="peesh@g.o">Jorge Paulo</mail>
</author>
<author title="Editor">
    <mail link="carl@g.o">Carl Anderson</mail>
</author>
<author title="Editor">
    <mail link="avenj@g.o">Jon Portnoy</mail>
</author>
<author title="Editor">
     <mail link="klasikahl@g.o">Zack Gilburd</mail>
</author>
<author title="Editor">
  <mail link="jmorgan@g.o">Jack Morgan</mail>
</author>
<author title="Editor">
  <mail link="bennyc@g.o">Benny Chuang</mail>
</author>
<author title="Editor">
  <mail link="erwin@g.o">Erwin</mail>
</author>
<author title="Editor">
  <mail link="kumba@g.o">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="nightmorph@g.o">Joshua Saddler</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>
<author title="Contributor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>

<abstract>
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux
information. This handbook contains the installation instructions for a
networkless installation on PPC64 systems and parts about working with Gentoo
and Portage.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>9.0</version>
<date>2007-06-06</date>

<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>

<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about.
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Booting the Universal Installation CD</title>
<abstract>
Using our Universal Installation CD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
  <include href="hb-install-ppc64-medium.xml"/>
</chapter>

<chapter>
<title>Configuring your Network</title>
<abstract>
If you need networking, this is the place where the network (and Internet
connection) is configured.
</abstract>
  <include href="hb-install-network.xml"/>
</chapter>

<chapter>
<title>Preparing the Disks</title>
<abstract>
To be able to install Gentoo, you must create the necessary partitions.
This chapter describes how to partition a disk for future usage.
</abstract>
  <include href="hb-install-ppc64-disk.xml"/>
</chapter>

<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
In this chapter we describe how you extract a stage3 file and how to configure
Portage.
</abstract>
  <include href="hb-install-stage.xml"/>
</chapter>

<chapter>
<title>Chrooting into the Gentoo Base System</title>
<abstract>
Now that the stage3 file is extracted, we chroot into the new system and modify
the USE variable.
</abstract>
  <include href="hb-install-system.xml"/>
</chapter>

<chapter>
<title>Configuring the Kernel</title>
<abstract>
The Linux kernel is the core of every distribution. This chapter
explains how to configure your kernel.
</abstract>
  <include href="hb-install-ppc64-kernel.xml"/>
</chapter>

<chapter>
<title>Configuring your System</title>
<abstract>
You need to edit some important configuration files. In this chapter
you receive an overview of these files and an explanation on how to
proceed.
</abstract>
  <include href="hb-install-config.xml"/>
</chapter>

<chapter>
<title>Installing Necessary System Tools</title>
<abstract>
As mentioned before, Gentoo is about customization. In this chapter we help you
choose and install some important tools.
</abstract>
  <include href="hb-install-tools.xml"/>
</chapter>

<chapter>
<title>Configuring the Bootloader</title>
<abstract>
Several bootloaders exist. Each one of them has its own way of
configuration. In this chapter we'll describe all possibilities for you
and step you through the process of configuring a bootloader to your
needs.
</abstract>
  <include href="hb-install-ppc64-bootloader.xml"/>
</chapter>


<chapter>
<title>Finalizing your Gentoo Installation</title>
<abstract>
You're almost done. We'll just create one (or more) users for your
system and (optionally) install prebuilt packages.
</abstract>
  <include href="hb-install-finalise.xml"/>
</chapter>

<chapter>
<title>Where to go from here?</title>
<abstract>
Now you have your Gentoo system, but what's next? 
</abstract>
  <include href="hb-install-next.xml"/>
</chapter>
</part>

<part>
<title>Working with Gentoo</title>
<abstract>
Learn how to work with Gentoo: installing software, altering variables, changing
Portage behaviour etc. 
</abstract>

<chapter>
<title>A Portage Introduction</title>
<abstract>
This chapter explains the "simple" steps a user definitely needs to know to
maintain the software on his system.
</abstract>
  <include href="../hb-working-portage.xml"/>
</chapter>

<chapter>
<title>USE flags</title>
<abstract>
USE flags are a very important aspect of Gentoo. In this chapter, you learn to
work with USE flags and understand how USE flags interact with your system.
</abstract>
  <include href="../hb-working-use.xml"/>
</chapter>

<chapter>
<title>Portage Features</title>
<abstract>
Discover the features Portage has, such as support for distributed compiling,
ccache and more.
</abstract>
  <include href="../hb-working-features.xml"/>
</chapter>

<chapter>
<title>Initscripts</title>
<abstract>
Gentoo uses a special initscript format which, amongst other features, allows
dependency-driven decisions and virtual initscripts. This chapter explains all
these aspects and explains how to deal with these scripts.
</abstract>
  <include href="../hb-working-rcscripts.xml"/>
</chapter>

<chapter>
<title>Environment Variables</title>
<abstract>
With Gentoo you can easily manage the environment variables for your system.
This chapter explains how you do that, and also describes frequently used
variables.
</abstract>
  <include href="../hb-working-variables.xml"/>
</chapter>
</part>

<part>
<title>Working with Portage</title>
<abstract>
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's
Software Management Tool.
</abstract>

<chapter>
<title>Files and Directories</title>
<abstract>
Once you want to know Portage in-depth you need to know where it stores its
files and data.
</abstract>
  <include href="../hb-portage-files.xml"/>
</chapter>

<chapter>
<title>Configuring through Variables</title>
<abstract>
Portage is completely configurable through various variables you can set in the
configuration file or as environment variable.
</abstract>
  <include href="../hb-portage-configuration.xml"/>
</chapter>

<chapter>
<title>Mixing Software Branches</title>
<abstract>
Gentoo provides software separated in several branches, depending on stability
and architectural support. "Mixing Software Branches" inform you how these
branches can be configured and how you can override this separation
individually.
</abstract>
  <include href="../hb-portage-branches.xml"/>
</chapter>

<chapter>
<title>Additional Portage Tools</title>
<abstract>
Portage comes with a few extra tools that might make your Gentoo experience even
better. Read on to discover how to use dispatch-conf and other tools.
</abstract>
  <include href="../hb-portage-tools.xml"/>
</chapter>

<chapter>
<title>Diverting from the Official Tree</title>
<abstract>
"Diverting from the Official Tree" gives you some tips and tricks on how to use
your own Portage tree, how to synchronise only the categories you want, inject
packages and more.
</abstract>
  <include href="../hb-portage-diverttree.xml"/>
</chapter>
</part>

<part>
<title>Gentoo Network Configuration</title>
<abstract>A comprehensive guide to Networking in Gentoo.</abstract>

<chapter>
<title>Getting Started</title>
<abstract>
A guide to quickly get your network interface up and running in most common
environments.
</abstract>
<include href="../hb-net-start.xml"/>
</chapter>

<chapter>
<title>Advanced Configuration</title>
<abstract>
Here we learn about how the configuration works - you need to know this
before we learn about modular networking.
</abstract>
<include href="../hb-net-advanced.xml"/>
</chapter>

<chapter>
<title>Modular Networking</title>
<abstract>
Gentoo provides you flexible networking - here you are told about choosing
different DHCP clients, setting up bonding, bridging, VLANs and more.
</abstract>
<include href="../hb-net-modules.xml"/>
</chapter>

<chapter>
<title>Wireless Networking</title>
<abstract>
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
<include href="../hb-net-wireless.xml"/>
</chapter>

<chapter>
<title>Adding Functionality</title>
<abstract>
If you're feeling adventurous, you can add your own functions to networking.
</abstract>
<include href="../hb-net-functions.xml"/>
</chapter>

<chapter>
<title>Network Management</title>
<abstract>
For laptop users or people who move their computer around different networks.
</abstract>
<include href="../hb-net-management.xml"/>
</chapter>
</part>

</book>



1.1                  xml/htdocs/doc/en/handbook/2008.0/handbook-sparc.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-sparc.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-sparc.xml?rev=1.1&content-type=text/plain

Index: handbook-sparc.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-sparc.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<book link="/doc/en/handbook/2007.1/handbook-sparc.xml" disclaimer="draft">
<title>Gentoo Linux 2007.1 SPARC Networkless Handbook</title>

<values>
 <key id="arch">SPARC</key>
 <key id="kernel-name">kernel-2.6.22-gentoo-r9</key>
 <key id="kernel-version">2.6.22-r9</key>
 <key id="min-cd-name">install-sparc-minimal-2007.1.iso</key>
 <key id="online-book">2007.1/handbook-sparc.xml</key>
 <key id="release-dir">releases/sparc/2007.1/sparc64/</key>
 <key id="stage3">stage3-sparc64-2007.1.tar.bz2</key>
 <key id="CFLAGS">-O2 -mcpu=ultrasparc -pipe</key>
</values>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>
<author title="Author">
  <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Author">
  <mail link="uberlord@g.o">Roy Marples</mail>
</author>
<author title="Author">
    <mail link="drobbins@g.o">Daniel Robbins</mail>
</author>
<author title="Author">
  <mail link="chouser@g.o">Chris Houser</mail>
</author>
<author title="Author">
  <mail link="jerry@g.o">Jerry Alexandratos</mail>
</author>
<author title="Gentoo x86 Developer">
  <mail link="seemant@g.o">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
  <mail link="taviso@g.o">Tavis Ormandy</mail>
</author><!-- Does not want to be listed on the rendered page
<author title="Gentoo Developer">
  Aron Griffis
</author>
-->
<author title="Gentoo AMD64 Developer">
  <mail link="jhuebel@g.o">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
  <mail link="gmsoft@g.o">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
   <mail link="pvdabeel@g.o">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
  <mail link="blademan@g.o">Joe Kallar</mail>
</author>
<author title="Editor">
    <mail link="zhen@g.o">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
    <mail link="stocke2@g.o">Eric Stockbridge</mail>
</author>
<author title="Editor">
    <mail link="rajiv@g.o">Rajiv Manglani</mail>
</author>
<author title="Editor">
    <mail link="seo@g.o">Jungmin Seo</mail>
</author>
<author title="Editor">
    <mail link="zhware@g.o">Stoyan Zhekov</mail>
</author>
<author title="Editor">
    <mail link="jhhudso@g.o">Jared Hudson</mail>
</author>
<author title="Editor">
    <mail link="peitolm@g.o">Colin Morey</mail>
</author>
<author title="Editor">
    <mail link="peesh@g.o">Jorge Paulo</mail>
</author>
<author title="Editor">
    <mail link="carl@g.o">Carl Anderson</mail>
</author>
<author title="Editor">
    <mail link="avenj@g.o">Jon Portnoy</mail>
</author>
<author title="Editor">
     <mail link="klasikahl@g.o">Zack Gilburd</mail>
</author>
<author title="Editor">
  <mail link="jmorgan@g.o">Jack Morgan</mail>
</author>
<author title="Editor">
  <mail link="bennyc@g.o">Benny Chuang</mail>
</author>
<author title="Editor">
  <mail link="erwin@g.o">Erwin</mail>
</author>
<author title="Editor">
  <mail link="kumba@g.o">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="nightmorph@g.o">Joshua Saddler</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>
<author title="Contributor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>

<abstract>
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux
information. This handbook contains the installation instructions for a
networkless installation on Sparc systems and parts about working with Gentoo
and Portage.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>9.0</version>
<date>2007-06-06</date>

<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>

<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about. 
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Booting the Universal Installation CD</title>
<abstract>
Using our Universal Installation CD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
  <include href="hb-install-sparc-medium.xml"/>
</chapter>

<chapter>
<title>Configuring your Network</title>
<abstract>
If you need networking, this is the place where the network (and Internet
connection) is configured.
</abstract>
  <include href="hb-install-network.xml"/>
</chapter>

<chapter>
<title>Preparing the Disks</title>
<abstract>
To be able to install Gentoo, you must create the necessary partitions.
This chapter describes how to partition a disk for future usage.
</abstract>
  <include href="hb-install-sparc-disk.xml"/>
</chapter>

<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
In this chapter we describe how you extract a stage3 file and how to configure
Portage.
</abstract>
  <include href="hb-install-stage.xml"/>
</chapter>

<chapter>
<title>Chrooting into the Gentoo Base System</title>
<abstract>
Now that the stage3 file is extracted, we chroot into the new system and modify
the USE variable.
</abstract>
  <include href="hb-install-system.xml"/>
</chapter>

<chapter>
<title>Configuring the Kernel</title>
<abstract>
The Linux kernel is the core of every distribution. This chapter
explains how to configure your kernel.
</abstract>
  <include href="hb-install-sparc-kernel.xml"/>
</chapter>

<chapter>
<title>Configuring your System</title>
<abstract>
You need to edit some important configuration files. In this chapter
you receive an overview of these files and an explanation on how to
proceed.
</abstract>
  <include href="hb-install-config.xml"/>
</chapter>

<chapter>
<title>Installing Necessary System Tools</title>
<abstract>
As mentioned before, Gentoo is about customization. In this chapter we help you
choose and install some important tools.
</abstract>
  <include href="hb-install-tools.xml"/>
</chapter>

<chapter>
<title>Configuring the Bootloader</title>
<abstract>
The SPARC architecture uses the SILO bootloader to fire up your Linux system. In
this chapter we step you through the process of configuring this bootloader to 
your needs.
</abstract>
  <include href="hb-install-sparc-bootloader.xml"/>
</chapter>

<chapter>
<title>Finalizing your Gentoo Installation</title>
<abstract>
You're almost done. We'll just create one (or more) users for your
system and (optionally) install prebuilt packages.
</abstract>
  <include href="hb-install-finalise.xml"/>
</chapter>

<chapter>
<title>Where to go from here?</title>
<abstract>
Now you have your Gentoo system, but what's next? 
</abstract>
  <include href="hb-install-next.xml"/>
</chapter>
</part>

<part>
<title>Working with Gentoo</title>
<abstract>
Learn how to work with Gentoo: installing software, altering variables, changing
Portage behaviour etc. 
</abstract>

<chapter>
<title>A Portage Introduction</title>
<abstract>
This chapter explains the "simple" steps a user definitely needs to know to
maintain the software on his system.
</abstract>
  <include href="../hb-working-portage.xml"/>
</chapter>

<chapter>
<title>USE flags</title>
<abstract>
USE flags are a very important aspect of Gentoo. In this chapter, you learn to
work with USE flags and understand how USE flags interact with your system.
</abstract>
  <include href="../hb-working-use.xml"/>
</chapter>

<chapter>
<title>Portage Features</title>
<abstract>
Discover the features Portage has, such as support for distributed compiling,
ccache and more.
</abstract>
  <include href="../hb-working-features.xml"/>
</chapter>

<chapter>
<title>Initscripts</title>
<abstract>
Gentoo uses a special initscript format which, amongst other features, allows
dependency-driven decisions and virtual initscripts. This chapter explains all
these aspects and explains how to deal with these scripts.
</abstract>
  <include href="../hb-working-rcscripts.xml"/>
</chapter>

<chapter>
<title>Environment Variables</title>
<abstract>
With Gentoo you can easily manage the environment variables for your system.
This chapter explains how you do that, and also describes frequently used
variables.
</abstract>
  <include href="../hb-working-variables.xml"/>
</chapter>
</part>

<part>
<title>Working with Portage</title>
<abstract>
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's
Software Management Tool.
</abstract>

<chapter>
<title>Files and Directories</title>
<abstract>
Once you want to know Portage in-depth you need to know where it stores its
files and data.
</abstract>
  <include href="../hb-portage-files.xml"/>
</chapter>

<chapter>
<title>Configuring through Variables</title>
<abstract>
Portage is completely configurable through various variables you can set in the
configuration file or as environment variable.
</abstract>
  <include href="../hb-portage-configuration.xml"/>
</chapter>

<chapter>
<title>Mixing Software Branches</title>
<abstract>
Gentoo provides software separated in several branches, depending on stability
and architectural support. "Mixing Software Branches" inform you how these
branches can be configured and how you can override this separation
individually.
</abstract>
  <include href="../hb-portage-branches.xml"/>
</chapter>

<chapter>
<title>Additional Portage Tools</title>
<abstract>
Portage comes with a few extra tools that might make your Gentoo experience even
better. Read on to discover how to use dispatch-conf and other tools.
</abstract>
  <include href="../hb-portage-tools.xml"/>
</chapter>

<chapter>
<title>Diverting from the Official Tree</title>
<abstract>
"Diverting from the Official Tree" gives you some tips and tricks on how to use
your own Portage tree, how to synchronise only the categories you want, inject
packages and more.
</abstract>
  <include href="../hb-portage-diverttree.xml"/>
</chapter>
</part>

<part>
<title>Gentoo Network Configuration</title>
<abstract>A comprehensive guide to Networking in Gentoo.</abstract>

<chapter>
<title>Getting Started</title>
<abstract>
A guide to quickly get your network interface up and running in most common
environments.
</abstract>
<include href="../hb-net-start.xml"/>
</chapter>

<chapter>
<title>Advanced Configuration</title>
<abstract>
Here we learn about how the configuration works - you need to know this
before we learn about modular networking.
</abstract>
<include href="../hb-net-advanced.xml"/>
</chapter>

<chapter>
<title>Modular Networking</title>
<abstract>
Gentoo provides you flexible networking - here you are told about choosing
different DHCP clients, setting up bonding, bridging, VLANs and more.
</abstract>
<include href="../hb-net-modules.xml"/>
</chapter>

<chapter>
<title>Wireless Networking</title>
<abstract>
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
<include href="../hb-net-wireless.xml"/>
</chapter>

<chapter>
<title>Adding Functionality</title>
<abstract>
If you're feeling adventurous, you can add your own functions to networking.
</abstract>
<include href="../hb-net-functions.xml"/>
</chapter>

<chapter>
<title>Network Management</title>
<abstract>
For laptop users or people who move their computer around different networks.
</abstract>
<include href="../hb-net-management.xml"/>
</chapter>
</part>

</book>



1.1                  xml/htdocs/doc/en/handbook/2008.0/handbook-x86.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-x86.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-x86.xml?rev=1.1&content-type=text/plain

Index: handbook-x86.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/handbook-x86.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<book link="/doc/en/handbook/2007.1/handbook-x86.xml" disclaimer="draft">
<title>Gentoo Linux 2007.1 x86 Networkless Handbook</title>

<values>
 <key id="arch">x86</key>
 <key id="release-dir">releases/x86/2007.1/</key>
 <key id="online-book">2007.1/handbook-x86.xml</key>
</values>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>
<author title="Author">
  <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Author">
  <mail link="uberlord@g.o">Roy Marples</mail>
</author>
<author title="Author">
    <mail link="drobbins@g.o">Daniel Robbins</mail>
</author>
<author title="Author">
  <mail link="chouser@g.o">Chris Houser</mail>
</author>
<author title="Author">
  <mail link="jerry@g.o">Jerry Alexandratos</mail>
</author>
<author title="Author">
  <mail link="nightmorph@g.o">Joshua Saddler</mail>
</author>
<author title="Gentoo x86 Developer">
  <mail link="seemant@g.o">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
  <mail link="taviso@g.o">Tavis Ormandy</mail>
</author><!-- Does not want to be listed on the rendered page
<author title="Gentoo Developer">
  Aron Griffis
</author>
-->
<author title="Gentoo AMD64 Developer">
  <mail link="jhuebel@g.o">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
  <mail link="gmsoft@g.o">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
   <mail link="pvdabeel@g.o">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
  <mail link="blademan@g.o">Joe Kallar</mail>
</author>
<author title="Editor">
    <mail link="zhen@g.o">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
    <mail link="stocke2@g.o">Eric Stockbridge</mail>
</author>
<author title="Editor">
    <mail link="rajiv@g.o">Rajiv Manglani</mail>
</author>
<author title="Editor">
    <mail link="seo@g.o">Jungmin Seo</mail>
</author>
<author title="Editor">
    <mail link="zhware@g.o">Stoyan Zhekov</mail>
</author>
<author title="Editor">
    <mail link="jhhudso@g.o">Jared Hudson</mail>
</author>
<author title="Editor">
    <mail link="peitolm@g.o">Colin Morey</mail>
</author>
<author title="Editor">
    <mail link="peesh@g.o">Jorge Paulo</mail>
</author>
<author title="Editor">
    <mail link="carl@g.o">Carl Anderson</mail>
</author>
<author title="Editor">
    <mail link="avenj@g.o">Jon Portnoy</mail>
</author>
<author title="Editor">
     <mail link="klasikahl@g.o">Zack Gilburd</mail>
</author>
<author title="Editor">
  <mail link="jmorgan@g.o">Jack Morgan</mail>
</author>
<author title="Editor">
  <mail link="bennyc@g.o">Benny Chuang</mail>
</author>
<author title="Editor">
  <mail link="erwin@g.o">Erwin</mail>
</author>
<author title="Editor">
  <mail link="kumba@g.o">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="fox2mike@g.o">Shyam Mani</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>
<author title="Contributor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>

<abstract>
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux
information. This handbook contains the installation instructions for a
networkless installation on x86 systems and parts about working with Gentoo and
Portage.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>9.0</version>
<date>2007-06-06</date>

<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>

<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about.
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Booting the Installer LiveCD</title>
<abstract>
Using our Installer LiveCD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
  <include href="hb-install-gli-medium.xml"/>
</chapter>

<chapter>
<title>Using the GTK+ based Gentoo Linux Installer</title>
<abstract>
You now have an option of using our graphical installer to install Gentoo.
Configure the options you need through an easy to use GUI and you're ready to
go.
</abstract>
  <include href="hb-install-gtkfe.xml" />
</chapter>

<chapter>
<title>Using the Dialog based Gentoo Linux Installer</title>
<abstract>
You also have an option of using our text based installer to install Gentoo.
Configure the options you need through an easy to use set of menus and you're
ready to go.
</abstract>
  <include href="hb-install-gli-dialog.xml" />
</chapter>

<chapter>
<title>Where to go from here?</title>
<abstract>
Now you have your Gentoo system, but what's next?
</abstract>
  <include href="hb-install-next.xml"/>
</chapter>
</part>

<part>
<title>Working with Gentoo</title>
<abstract>
Learn how to work with Gentoo: installing software, altering variables,
changing Portage behaviour etc.
</abstract>

<chapter>
<title>A Portage Introduction</title>
<abstract>
This chapter explains the "simple" steps a user definitely needs to know to
maintain the software on his system.
</abstract>
  <include href="../hb-working-portage.xml"/>
</chapter>

<chapter>
<title>USE flags</title>
<abstract>
USE flags are a very important aspect of Gentoo. In this chapter, you learn to
work with USE flags and understand how USE flags interact with your system.
</abstract>
  <include href="../hb-working-use.xml"/>
</chapter>

<chapter>
<title>Portage Features</title>
<abstract>
Discover the features Portage has, such as support for distributed compiling,
ccache and more.
</abstract>
  <include href="../hb-working-features.xml"/>
</chapter>

<chapter>
<title>Initscripts</title>
<abstract>
Gentoo uses a special initscript format which, amongst other features, allows
dependency-driven decisions and virtual initscripts. This chapter explains all
these aspects and explains how to deal with these scripts.
</abstract>
  <include href="../hb-working-rcscripts.xml"/>
</chapter>

<chapter>
<title>Environment Variables</title>
<abstract>
With Gentoo you can easily manage the environment variables for your system.
This chapter explains how you do that, and also describes frequently used
variables.
</abstract>
  <include href="../hb-working-variables.xml"/>
</chapter>
</part>

<part>
<title>Working with Portage</title>
<abstract>
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's
Software Management Tool.
</abstract>

<chapter>
<title>Files and Directories</title>
<abstract>
Once you want to know Portage in-depth you need to know where it stores its
files and data.
</abstract>
  <include href="../hb-portage-files.xml"/>
</chapter>

<chapter>
<title>Configuring through Variables</title>
<abstract>
Portage is completely configurable through various variables you can set in the
configuration file or as environment variable.
</abstract>
  <include href="../hb-portage-configuration.xml"/>
</chapter>

<chapter>
<title>Mixing Software Branches</title>
<abstract>
Gentoo provides software separated in several branches, depending on stability
and architectural support. "Mixing Software Branches" inform you how these
branches can be configured and how you can override this separation
individually.
</abstract>
  <include href="../hb-portage-branches.xml"/>
</chapter>

<chapter>
<title>Additional Portage Tools</title>
<abstract>
Portage comes with a few extra tools that might make your Gentoo experience even
better. Read on to discover how to use dispatch-conf and other tools.
</abstract>
  <include href="../hb-portage-tools.xml"/>
</chapter>

<chapter>
<title>Diverting from the Official Tree</title>
<abstract>
"Diverting from the Official Tree" gives you some tips and tricks on how to use
your own Portage tree, how to synchronise only the categories you want, inject
packages and more.
</abstract>
  <include href="../hb-portage-diverttree.xml"/>
</chapter>
</part>

<part>
<title>Gentoo Network Configuration</title>
<abstract>A comprehensive guide to Networking in Gentoo.</abstract>

<chapter>
<title>Getting Started</title>
<abstract>
A guide to quickly get your network interface up and running in most common
environments.
</abstract>
<include href="../hb-net-start.xml"/>
</chapter>

<chapter>
<title>Advanced Configuration</title>
<abstract>
Here we learn about how the configuration works - you need to know this
before we learn about modular networking.
</abstract>
<include href="../hb-net-advanced.xml"/>
</chapter>

<chapter>
<title>Modular Networking</title>
<abstract>
Gentoo provides you flexible networking - here you are told about choosing
different DHCP clients, setting up bonding, bridging, VLANs and more.
</abstract>
<include href="../hb-net-modules.xml"/>
</chapter>

<chapter>
<title>Wireless Networking</title>
<abstract>
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
<include href="../hb-net-wireless.xml"/>
</chapter>

<chapter>
<title>Adding Functionality</title>
<abstract>
If you're feeling adventurous, you can add your own functions to networking.
</abstract>
<include href="../hb-net-functions.xml"/>
</chapter>

<chapter>
<title>Network Management</title>
<abstract>
For laptop users or people who move their computer around different networks.
</abstract>
<include href="../hb-net-management.xml"/>
</chapter>
</part>

</book>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-about.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-about.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-about.xml?rev=1.1&content-type=text/plain

Index: hb-install-about.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-about.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-02</date>

<section>
<title>Introduction</title>
<subsection>
<title>Welcome!</title>
<body>

<p>
First of all, <e>welcome</e> to Gentoo. You are about to enter the world
of customization and performance. When installing Gentoo, this is made clear to
you several times -- you can choose how much you want to compile yourself, how
to install Gentoo, what system logger you want, etc.
</p>

<p>
Gentoo is a fast, modern meta-distribution with a clean and flexible
design. Gentoo is built around free software and doesn't hide from its
users what is beneath the hood. Portage, the package maintenance system
which Gentoo uses, is written in Python, meaning you can easily view and
modify the source code. Gentoo's packaging system uses source code
(although support for precompiled packages is included too) and
configuring Gentoo happens through regular text files. In other words,
openness everywhere.
</p>

<p>
It is very important that you understand that <e>empowerment</e> is what makes
Gentoo run. We try not to force anything on our users and try our best to
empower you to make the choices you wish. If you feel a change should be made,
please file a <uri link="http://bugs.gentoo.org">bug report</uri> about it.
</p>

</body>
</subsection>
<!-- for all arches that DO have an installer liveCD -->
<subsection test="contains('AMD64 x86', func:keyval('arch'))">
<title>How do I go about Installing Gentoo?</title>
<body>

<p>
Gentoo Linux comes with two versions of an easy to use Installer. A GTK+ based
installer (for use with an X based environment) and a Dialog based installer for
use on the console. Chapter 3 of the handbook deals with the GTK+ based
installer while Chapter 4 is for the Dialog based one.
</p>

</body>
</subsection>
<!-- for all arches that do NOT have an installer liveCD -->
<subsection test="not(contains('AMD64 x86', func:keyval('arch')))">
<title>How is the Installation Structured?</title>
<body>

<p>
The Gentoo Installation can be seen as a 10-step procedure,
corresponding to chapters 2 - 11. Every step results in
a certain state:
</p>

<ul>
<li>
  After step 1, you are in a working environment ready to install Gentoo
</li>
<li>
  After step 2, your internet connection is prepared in case you need it (this
  is however optional)
</li>
<li>
  After step 3, your hard disks are initialized to house your Gentoo
  installation
</li>
<li>
  After step 4, your installation environment is prepared and you are
  ready to chroot into the new environment
</li>
<li>
  After step 5, core packages, which are the same on all Gentoo
  installations, are installed
</li>
<li>
  After step 6, you have compiled your Linux kernel
</li>
<li>
  After step 7, you have written most of your Gentoo system
  configuration files
</li>
<li>
  After step 8, necessary system tools (which you can choose from a nice
  list) are installed
</li>
<li>
  After step 9, your choice of bootloader has been installed and
  configured and you are logged in into your new Gentoo installation
</li>
<li>
  After step 10, your Gentoo Linux environment is ready to be explored
</li>
</ul>

<p>
When you are given a certain choice, we try our best to explain what the pros 
and cons are. We will continue then with a default
choice, identified by &quot;Default: &quot; in the title. The other
possibilities are marked by &quot;Alternative: &quot;. Do <e>not</e>
think that the default is what we recommend. It is however what we
believe most users will use.
</p>

<p>
Sometimes you can pursue an optional step. Such steps are marked as
&quot;Optional: &quot; and are therefore not needed to install Gentoo.
However, some optional steps are dependant on a previous decision you
made. We will inform you when this happens, both when you make the
decision, and right before the optional step is described.
</p>

</body>
</subsection>
<subsection>
<title>What are my Options?</title>
<body>

<p>
You can install Gentoo in many different ways. You can download and install from
one of our Installation CDs, from an existing distribution, 
from a bootable CD (such as Knoppix), from a netbooted environment, from a 
rescue floppy, etc. 
</p>

<p>
This document covers the installation using a Gentoo Linux Installation CD, a 
bootable CD that contains everything you need to get Gentoo Linux up and 
running. There are two types of Installation CDs, the InstallCD and the
Installer LiveCD. The InstallCD is a minimal environment which contains only
those packages necessary for installing Gentoo Linux. The LiveCD is a complete
Gentoo Linux environment and can be used for multiple tasks, one of which is
installing Gentoo Linux. The LiveCD is not available on all architectures at
this time. If your architecture does not have a LiveCD, then this document will
refer to the Universal InstallCD for you.
</p>

<p>
This installation approach however does not immediately use the latest version
of the available packages; if you want this you should check out the
Installation Instructions inside our <uri
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>.
</p>

<p>
For help on the other installation approaches, 
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation
Guide</uri>. We also provide a <uri
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips &amp; 
Tricks</uri> document that might be useful to read as well. If you feel that 
the current installation instructions are too elaborate, feel free to use our 
Quick Installation Guide available from our <uri 
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture
has such a document available.
</p>

</body>
</subsection>
<subsection>
<title>Troubles?</title>
<body>

<p>
If you find a problem in the installation (or in the installation
documentation), please check the errata from our <uri
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, 
visit our <uri link="http://bugs.gentoo.org">bug tracking
system</uri> and check if the bug is known. If not, please create a bug report 
for it so we can take care of it. Do not be afraid of the developers who are 
assigned to (your) bugs -- they generally don't eat people.
</p>

<p>
Note though that, although the document you are now reading is
architecture-specific, it will contain references to other architectures as
well. This is due to the fact that large parts of the Gentoo Handbook use source
code that is common for all architectures (to avoid duplication of efforts and
starvation of development resources). We will try to keep this to a minimum
to avoid confusion.
</p>

<p>
If you are uncertain if the problem is a user-problem (some error you
made despite having read the documentation carefully) or a
software-problem (some error we made despite having tested the
installation/documentation carefully) you are free to join #gentoo on
irc.freenode.net. Of course, you are welcome otherwise too :)
</p>

<p>
If you have a question regarding Gentoo, check out our <uri
link="/doc/en/faq.xml">Frequently Asked
Questions</uri>, available from the <uri
link="/doc/en/">Gentoo Documentation</uri>. You can
also view the <uri
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of
us are freaks who sit on IRC :-)
</p>

</body>
</subsection>
</section>
<section>
<title>Fast Installation using the Gentoo Reference Platform</title>
<subsection>
<title>What is the Gentoo Reference Platform?</title>
<body>

<p>
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of
prebuilt packages users (that means you!) can install during the installation
of Gentoo to speed up the installation process. The GRP consists of all
packages required to have a fully functional Gentoo installation. They are not
just the ones you need to have a base installation up to speed in no time, but
all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...)
are available as GRP packages too.
</p>

<p>
However, these prebuilt packages aren't maintained during the lifetime of the
Gentoo distribution. They are snapshots released at every Gentoo release and
make it possible to have a functional environment in a short amount of time. You
can then upgrade your system in the background while working in your Gentoo
environment.
</p>

</body>
</subsection>
<subsection>
<title>How Portage Handles GRP Packages</title>
<body>

<p>
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all 
information about a package, such as its description, homepage, sourcecode URLs,
compilation instructions, dependencies, etc.) - must be synchronised with the 
GRP set: the versions of the available ebuilds and their accompanying GRP 
packages must match.
</p>

<p>
For this reason you can only benefit from the GRP packages Gentoo provides while
performing the current installation approach. GRP is not available for those
interested in performing an installation using the latest versions of all
available packages.
</p>

</body>
</subsection>
<subsection>
<title>Is GRP Available?</title>
<body>

<p>
Not all architectures provide GRP packages. That doesn't mean GRP isn't
supported on the other architectures, but it means that we don't have the 
resources to build and test the GRP packages.
</p>

<p>
At present we provide GRP packages for the following architectures:
</p>

<ul>
  <li>
    The <b>amd64</b> architecture (amd64). Note: The packages are available on
    the Installer LiveCD.
  </li>
  <li>
    The <b>ppc</b> architecture (ppc32)
  </li>
  <li>
    The <b>sparc</b> architecture (sparc64)
  </li>
  <li>
    The <b>x86</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro,
    pentium2, pentium3, pentium4 and pentium-m) Note: The packages are for i686
    and are available on the Installer LiveCD.
  </li>
</ul>

<p>
If your architecture (or subarchitecture) isn't on this list, you are not
able to opt for a GRP installation.
</p>

<p>
Now that this introduction is over, let's continue with <uri
link="?part=1&amp;chap=2">Booting the Universal InstallCD/Installer
LiveCD</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-config.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-config.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-config.xml?rev=1.1&content-type=text/plain

Index: hb-install-config.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-config.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-08-13</date>

<section>
<title>Filesystem Information</title>
<subsection>
<title>What is fstab?</title>
<body>

<p>
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
and with what special options (automatically or not, whether users can mount
them or not, etc.)
</p>

</body>
</subsection>
<subsection>
<title>Creating /etc/fstab</title>
<body>

<p>
<path>/etc/fstab</path> uses a special syntax. Every line consists of six
fields, separated by whitespace (space(s), tabs or a mixture). Each field has
its own meaning:
</p>

<ul>
<li>
  The first field shows the <b>partition</b> described (the path to the device
  file)
</li>
<li>
  The second field shows the <b>mountpoint</b> at which the partition should be
  mounted
</li>
<li>
  The third field shows the <b>filesystem</b> used by the partition
</li>
<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 man page (<c>man mount</c>) for a full
  listing. Multiple mountoptions are comma-separated.
</li>
<li>
  The fifth field is used by <c>dump</c> to determine if the partition needs to
  be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
</li>
<li>
  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> if a filesystem check isn't necessary).
</li>
</ul>

<impo>
The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
</impo>

<pre caption="Opening /etc/fstab">
# <i>nano -w /etc/fstab</i>
</pre>

</body>
<body test="func:keyval('/boot')">

<p>
Let us take a look at how we write down the options for the <path>/boot</path>
partition. This is just an example, if you didn't or couldn't create a
<path>/boot</path>, don't copy it.
</p>

<p test="contains(func:keyval('/boot'), '/dev/hd')">
In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
usually the <path><keyval id="/boot"/></path> partition (or
<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
filesystem. It needs to be checked during boot, so we would write down:
</p>

<p test="contains(func:keyval('/boot'), '/dev/sd')">
In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
filesystem. It needs to be checked during boot, so we would write down:
</p>

<pre caption="An example /boot line for /etc/fstab">
<keyval id="/boot"/>   /boot     ext2    defaults        1 2
</pre>

<p>
Some users don't want their <path>/boot</path> partition to be mounted
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>

</body>
<body>

<p test="not(func:keyval('arch')='SPARC')">
Add the rules that match your partitioning scheme and append rules for
your CD-ROM drive(s), and of course, if you have other partitions or 
drives, for those too.
</p>

<p test="func:keyval('arch')='SPARC'">
Add the rules that match your partitioning schema and append rules for
<path>/proc/openprom</path>, for your CD-ROM drive(s), and of course, if 
you have other partitions or drives, for those too.
</p>

<p>
Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
</p>

<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
<keyval id="/boot"/>   /boot        ext2    defaults,noatime     1 2
/dev/sda3   none         swap    sw                   0 0
/dev/sda4   /            ext3    noatime              0 1

/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
</pre>

<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'">
<keyval id="/boot"/>   /boot        ext2    defaults,noatime     1 2
/dev/sda2   none         swap    sw                   0 0
/dev/sda3   /            ext3    noatime              0 1

/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
</pre>

<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
/dev/sda1   /               ext3        noatime              0 1
/dev/sda2   none            swap        sw                   0 0
/dev/sda4   /usr            ext3        noatime              0 2
/dev/sda5   /var            ext3        noatime              0 2
/dev/sda6   /home           ext3        noatime              0 2

openprom    /proc/openprom  openpromfs  defaults             0 0

/dev/cdrom  /mnt/cdrom      auto        noauto,user          0 0
</pre>

<note test="func:keyval('arch')='PPC'">
There are important variations between PPC machine types. Please make sure you
adapt the following example to your system.
</note>

<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'">
/dev/hda4   /            ext3    noatime              0 1
/dev/hda3   none         swap    sw                   0 0

/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
</pre>

<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'">
/dev/sda4   /            ext3    noatime              0 1
/dev/sda3   none         swap    sw                   0 0

/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
</pre>

<p>
<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 
removable media as they can be created with one of many filesystems) and 
<c>user</c> makes it possible for non-root users to mount the CD.
</p>

<p>
To improve performance, most users would want to add the <c>noatime</c>
mount option, which results in a faster system since access times
aren't registered (you don't need those generally anyway).
</p>

<p>
Double-check your <path>/etc/fstab</path>, save and quit to continue.
</p>

</body>
</subsection>
</section>
<section>
<title>Networking Information</title>
<subsection>
<title>Hostname, Domainname etc.</title>
<body>

<p>
One of the choices the user has to make is name his/her PC. This seems to be 
quite easy, but <e>lots</e> of users are having difficulties finding the 
appropriate name for their Linux-pc. To speed things up, know that any name you 
choose can be changed afterwards. For all we care, you can just call your system
<c>tux</c> and domain <c>homenetwork</c>. 
</p>

<p>
We use these values in the next examples. First we set the hostname:
</p>

<pre caption="Setting the hostname">
# <i>nano -w /etc/conf.d/hostname</i>

<comment>(Set the HOSTNAME variable to your hostname)</comment>
HOSTNAME="<i>tux</i>"
</pre>

<p>
Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
You only need a domain if your ISP or network administrator says so, or if you
have a DNS server but not a DHCP server. You don't need to worry about DNS or
domainnames if your networking is setup for DHCP.
</p>

<pre caption="Setting the domainname">
# <i>nano -w /etc/conf.d/net</i>

<comment>(Set the dns_domain variable to your domain name)</comment>
dns_domain_lo="<i>homenetwork</i>"
</pre>

<note>
If you choose not to set a domainname, you can get rid of the "This is
hostname.(none)" messages at your login screen by editing
<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
</note>

<p>
If you have a NIS domain (if you don't know what that is, then you don't have
one), you need to define that one too:
</p>

<pre caption="Setting the NIS domainname">
# <i>nano -w /etc/conf.d/net</i>

<comment>(Set the nis_domain variable to your NIS domain name)</comment>
nis_domain_lo="<i>my-nisdomain</i>"
</pre>

<note>
For more information on configuring DNS and NIS, please read the examples
provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
<c>resolvconf-gentoo</c> to help manage your DNS/NIS setup.
</note>

</body>
</subsection>
<subsection>
<title>Configuring your Network</title>
<body>

<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 
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 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>
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">
# <i>nano -w /etc/conf.d/net</i>
</pre>

<p>
You will see the following file:
</p>

<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>
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 via 192.168.0.1" )
</pre>

<p>
To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
<c>dhcp_eth0</c>:
</p>

<pre caption="Automatically obtaining an IP address for eth0">
config_eth0=( "dhcp" )
dhcp_eth0="nodns nontp nonis"
</pre>

<p>
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>
Now save the configuration and exit to continue.
</p>

</body>
</subsection>
<subsection>
<title>Automatically Start Networking at Boot</title>
<body>

<p>
To have your network interfaces activated at boot, you need to add them to the
default runlevel.
</p>

<pre caption="Adding net.eth0 to the default runlevel">
# <i>rc-update add net.eth0 default</i>
</pre>

<p>
If you have several network interfaces, you need to create the appropriate
<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can
use <c>ln</c> to do this:
</p>

<pre caption="Creating extra initscripts">
# <i>cd /etc/init.d</i>
# <i>ln -s net.lo net.eth1</i>
# <i>rc-update add net.eth1 default</i>
</pre>

</body>
</subsection>
<subsection>
<title>Writing Down Network Information</title>
<body>

<p>
You now need to inform Linux about your network. This is defined in
<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for
hosts that aren't resolved by your nameserver.  You need to define your system.
You may also want to define other systems on your network if you don't want to
set up your own internal DNS system.
</p>

<pre caption="Opening /etc/hosts">
# <i>nano -w /etc/hosts</i>
</pre>

<pre caption="Filling in the networking information">
<comment>(This defines the current system)</comment>
127.0.0.1     tux.homenetwork tux localhost

<comment>(Define extra systems on your network,
they need to have a static IP to be defined this way.)</comment>
192.168.0.5   jenny.homenetwork jenny
192.168.0.6   benny.homenetwork benny
</pre>

<p>
Save and exit the editor to continue.
</p>

<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
If you don't have PCMCIA, you can now continue with <uri
link="#sysinfo">System Information</uri>. PCMCIA-users should read the
following topic on PCMCIA.
</p>

</body>
</subsection>
<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
<title>Optional: Get PCMCIA Working</title>
<body>

<p>
PCMCIA users should first install the <c>pcmciautils</c> package.
</p>

<pre caption="Installing pcmciautils">
# <i>emerge pcmciautils</i>
</pre>

</body>
</subsection>
</section>

<section id="sysinfo">
<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>
Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
</p>

<pre caption="Opening /etc/rc.conf">
# <i>nano -w /etc/rc.conf</i>
</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. 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 test="substring(func:keyval('arch'),1,3)='PPC'">
PPC 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>
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>
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.
</p>

<p>
You should define the timezone that you previously copied to
<path>/etc/localtime</path> so that further upgrades of the
<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
automatically. For instance, if you used the GMT timezone, you would add
<c>TIMEZONE="GMT"</c>
</p>

<p>
When you're finished configuring <path>/etc/conf.d/clock</path>, save and
exit. 
</p>

<p test="not(func:keyval('arch')='PPC64')">
Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
Tools</uri>.
</p>

</body>
</subsection>
<subsection test="func:keyval('arch')='PPC64'">
<title>Configuring the Console</title>
<body>

<p>
If you are 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>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-finalise.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-finalise.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-finalise.xml?rev=1.1&content-type=text/plain

Index: hb-install-finalise.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-finalise.xml,v 1.1 2008/02/27 22:46:57 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>User Administration</title>
<subsection>
<title>Adding a User for Daily Use</title>
<body>

<p>
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided
as much as possible. Therefore it is <e>strongly</e> recommended to add a user 
for day-to-day use.
</p>

<p>
The groups the user is member of define what activities the user can perform.
The following table lists a number of important groups you might wish to use:
</p>

<table>
<tr>
  <th>Group</th>
  <th>Description</th>
</tr>
<tr>
  <ti>audio</ti>
  <ti>be able to access the audio devices</ti>
</tr>
<tr>
  <ti>cdrom</ti>
  <ti>be able to directly access optical devices</ti>
</tr>
<tr>
  <ti>floppy</ti>
  <ti>be able to directly access floppy devices</ti>
</tr>
<tr>
  <ti>games</ti>
  <ti>be able to play games</ti>
</tr>
<tr>
  <ti>portage</ti>
  <ti>be able to use <c>emerge --pretend</c> as a normal user</ti>
</tr>
<tr>
  <ti>usb</ti>
  <ti>be able to access USB devices</ti>
</tr>
<tr>
  <ti>plugdev</ti>
  <ti>
    Be able to mount and use pluggable devices such as cameras and USB sticks
  </ti>
</tr>
<tr>
  <ti>video</ti>
  <ti>
    be able to access video capturing hardware and doing hardware
    acceleration
  </ti>
</tr>
<tr>
  <ti>wheel</ti>
  <ti>be able to use <c>su</c></ti>
</tr>
</table>

<p>
For instance, to create a user called <c>john</c> who is member of the
<c>wheel</c>, <c>users</c> and <c>audio</c> groups, log in as root first 
(only root can create users) and run <c>useradd</c>:
</p>

<pre caption="Adding a user for day-to-day use">
Login: <i>root</i>
Password: <comment>(Your root password)</comment>

# <i>useradd -m -G users,wheel,audio -s /bin/bash john</i>
# <i>passwd john</i>
Password: <comment>(Enter the password for john)</comment>
Re-enter password: <comment>(Re-enter the password to verify)</comment>
</pre>

<p>
If a user ever needs to perform some task as root, they can use <c>su -</c>
to temporarily receive root privileges. Another way is to use the <c>sudo</c> 
package which is, if correctly configured, very secure.
</p>

</body>
</subsection>
</section>
<section>
<title>Optional: Install GRP Packages</title>
<body>

<impo>
This part is for GRP users only. Other users should skip this part and continue
with <uri link="?part=1&amp;chap=12">Where to go from here?</uri>.
</impo>

<p>
Now that your system is booted, log on as the user you created (for instance,
<c>john</c>) and use <c>su -</c> to gain root privileges:
</p>

<pre caption="Gaining root privileges">
$ <i>su -</i>
Password: <comment>(Enter your root password)</comment>
</pre>

<p>
Now we need to change the Portage configuration to look for the prebuilt 
binaries from the second CD (Gentoo Packages CD). First mount this CD:
</p>

<pre caption="Mount the Packages CD">
<comment>(Put the Gentoo Packages CD in the CD tray)</comment>
# <i>mount /mnt/cdrom</i>
</pre>

<p>
Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages:
</p>

<pre caption="Configuring Portage to use /mnt/cdrom">
# <i>ls /mnt/cdrom</i>

<comment>(If there is a /mnt/cdrom/packages directory:)</comment>
# <i>export PKGDIR="/mnt/cdrom/packages"</i>

<comment>(Otherwise:)</comment>
# <i>export PKGDIR="/mnt/cdrom"</i>
</pre>

<p>
Now install the packages you want. The Packages CD contains several prebuilt 
binaries, for instance KDE and GNOME. 
</p>

<pre caption="Installing GNOME">
# <i>emerge --usepkg gnome</i>
</pre>

<p>
To find out what prebuilt packages are available, do a quick listing of all 
the files in <path>/mnt/cdrom/All</path>. For instance, to find out if KDE is 
emergeable:
</p>

<pre caption="Finding out if KDE is installable">
# <i>ls /mnt/cdrom/All/kde*</i>
</pre>

<p>
Be sure to install the binaries now. When you do an <c>emerge --sync</c> to
update Portage (as you will learn later), the prebuilt binaries might not match
against the ebuilds in your updated Portage. You can try to circumvent this by
using <c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>.
</p>

<p>
Congratulations, your system is now fully equipped! Continue with <uri
link="?part=1&amp;chap=12">Where to go from here?</uri> to learn more about
Gentoo.
</p>

</body>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-dialog.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-dialog.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-dialog.xml?rev=1.1&content-type=text/plain

Index: hb-install-gli-dialog.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-dialog.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<!--  The content of this document is licensed under the CC-BY-SA license -->
<!--  See http://creativecommons.org/licenses/by-sa/2.5 -->

<sections>

<version>4.0</version>
<date>2007-05-07</date>

<section>
<title>Welcome</title>
<subsection>
<title>Before you begin</title>
<body>

<p>
After you boot the Gentoo Linux Installer LiveCD, it will attempt to load a
graphical desktop. If it is unable to do so, it will instead display a command
line prompt. To launch the installer, simply type:
</p>

<pre caption="Start the installer">
# <i>installer-dialog</i>
</pre>

<p>
The Gentoo Linux Installer (GLI) provides a friendly introduction to the process
of installing Gentoo on your computer. Remember to read each option carefully.
There is detailed help available for each step of installation at the top of the
screen.  We recommend that you always read the help provided before making your
choices.  Note that at any time during the installation process, you can save
your configuration progress in case you need to resume your installation at a
later time. Use the <c>Tab</c> key (on your keyboard) to move around the menus
within a screen and the <c>Enter</c> key to confirm an action.
</p>

</body>
</subsection>
</section>

<section>
<title>Partitioning</title>
<subsection>
<title>Preparing the disks</title>
<body>

<p>
In order to install Gentoo on your machine, you will need to prepare your
disks. The <c>Partitioning</c> screen will show you a list of detected disks and
allow you to specify the filesystems you would like to have on your
partitions. Selecting <c>Clear partitions</c> will erase all previous partitions on
your disk, so be careful with this option!<!-- It is also possible to resize
certain partition types. -->
</p>

<p>
If you choose to go with the <c>Recommended layout</c>, the installer will
create three partitions: 100MB for <path>/boot</path>, a <path>/swap</path>
partition up to 512MB in size, and the rest of the available space on the disk
is used for <path>/</path>, the root partition.
</p>

<warn>
As with any partitioning application, you should backup your system before
making changes to your partition table, as any possible bugs could cause data
loss.
</warn>

</body>
</subsection>
</section>

<section>
<title>System Configuration</title>
<subsection>
<title>Timezone</title>
<body>

<p>
Study the list and select the region closest to your actual location.
</p>

</body>
</subsection>
<subsection>
<title>Networking</title>
<body>

<p>
On this screen, you will be able to configure the various network interface
devices detected on your computer. Read the available options carefully.
</p>

<p>
The next screen gives you a choice between DHCP and manual IP address
configuration. Once your network interface is properly configured, you will
need to create a hostname for your system. Optionally, you may specify a
domainname and any DNS server information needed.
</p>

</body>
</subsection>
<subsection>
<title>Users and groups</title>
<body>

<p>
First set the root password for the system administrator (the <e>root</e>
user).
</p>

<p>
We <e>strongly</e> recommend that you create a regular user for daily work.
Working as root all the time is <e>dangerous</e> and should be avoided! Create
your users, set their passwords, and add them to the appropriate groups. You can
optionally change their home directories and select their login shell.
</p>

</body>
</subsection>
<subsection>
<title>Extra Packages</title>
<body>

<p>
The LiveCD contains a number of available pre-built packages. If you wish to
install any of them, check the appropriate box.
</p>

</body>
</subsection>
<subsection>
<title>Startup Services</title>
<body>

<p>
This screen allows you to choose various services to load at system boot. Study
the available options and their descriptions carefully, and then select your
desired services. For example, if you have chosen to install <c>xorg-x11</c>
and want to boot straight into a graphical desktop, then you would select
"xdm" from the list.
</p>

</body>
</subsection>
<subsection>
<title>Other Settings</title>
<body>

<p>
You now will be able to change various settings, including keyboard layout,
graphical display manager, the default editor, and whether to set your hardware
clock to UTC or local time.
</p>

</body>
</subsection>
</section>

<section>
<title>Finishing Up</title>
<subsection>
<body>

<p>
The installer will ask if you want to save your <c>installation profile</c> for
later use. The installer will alert you when it has finished. It will then
return you to the command prompt. All you need to do to reboot is type:
</p>

<pre caption="Rebooting">
# <i>shutdown -r now</i>
</pre>

<p>
Congratulations, your system is now fully equipped! Continue with <uri
link="?part=1&amp;chap=5">Where to go from here?</uri> to learn more about
Gentoo.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-medium.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-medium.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-medium.xml?rev=1.1&content-type=text/plain

Index: hb-install-gli-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gli-medium.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-29</date>

<section>
<title>Hardware Requirements</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Before we start, we first list what hardware requirements you need to
successfully install Gentoo on your box using the Installer LiveCD.
</p>

</body>
</subsection>
<subsection>
<title>Hardware Requirements</title>
<body>

<table>
<tr test="func:keyval('arch')='x86'">
  <th>CPU</th>
  <ti>i686 or later</ti>
</tr>
<tr test="func:keyval('arch')='AMD64'">
  <th>CPU</th>
  <ti>Any AMD64 or EM64T CPU</ti>
</tr>
<tr>
  <th>Memory</th>
  <ti>256 MB</ti>
</tr>
<tr>
  <th>Diskspace</th>
  <ti>1.5 GB (excluding swap space)</ti>
</tr>
<tr>
  <th>Swap space</th>
  <ti>At least 256 MB</ti>
</tr>
</table>

</body>
</subsection>
</section>
<!-- General description, propagated to other architectures as well -->
<!-- START -->
<section>
<title>The Gentoo Linux Installer LiveCD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
A LiveCD is a bootable medium which contains a self-sustained Gentoo
environment. It allows you to boot Linux from the CD. During the boot process
your hardware is detected and the appropriate drivers are loaded. The Gentoo
Installation CDs are maintained by Gentoo developers.
</p>

<p>
There currently are two Installation CDs available:
</p>

<ul>
  <li>
    The Installer LiveCD contains everything you need to install Gentoo. It
    provides a graphical environment, a graphical as well as console based
    installer which automatically carries out the installation for you, and of
    course, the installation instructions for your architecture.
  </li>
  <li>
    The Minimal Installation CD contains only a minimal environment that allows
    you to boot up and configure your network so you can connect to the
    Internet. It does not contain any additional files and cannot be used
    during the current installation approach.
  </li>
</ul>

</body>
</subsection>
</section>
<!-- STOP -->
<section>
<title>Download, Burn and Boot the Gentoo Linux Installer LiveCD</title>
<subsection>
<title>Downloading and Burning the Installer LiveCD</title>
<body>

<p>
You can download the Installer LiveCDs from one of our <uri
link="/main/en/mirrors.xml">mirrors</uri>. They are located in the
<path><keyval id="release-dir"/>livecd/</path> directory.
</p>

<p>
Inside that directory you'll find an ISO file. That is a full CD image which
you can write on a CD-R.
</p>

<p>
After downloading the file, you can verify its integrity to see if it is
corrupted or not:
</p>

<ul>
  <li>
    You can check its MD5 checksum and compare it with the MD5 checksum we
    provide (for instance with the <c>md5sum</c> tool under Linux/Unix or <uri
    link="http://www.etree.org/md5com.html">md5sum</uri> for Windows)
  </li>
  <li>
    You can verify the cryptographic signature that we provide. You need to
    obtain the public key we use (17072058) before you proceed though.
  </li>
</ul>

<p>
To fetch our public key using the GnuPG application, run the following command:
</p>

<pre caption="Obtaining the public key">
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i>
</pre>

<p>
Now verify the signature:
</p>

<pre caption="Verify the cryptographic signature">
$ <i>gpg --verify &lt;signature file&gt; &lt;downloaded iso&gt;</i>
</pre>

<p>
To burn the downloaded ISO(s), you have to select raw-burning. How you do this
is highly program-dependent. We will discuss <c>cdrecord</c> and <c>K3B</c>
here; more information can be found in our <uri
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>.
</p>

<ul>
  <li>
    With cdrecord, you simply type <c>cdrecord dev=/dev/hdc &lt;downloaded iso
    file&gt;</c> (replace <path>/dev/hdc</path> with your CD-RW drive's device
    path).
  </li>
  <li>
    With K3B, select <c>Tools</c> &gt; <c>Burn CD Image</c>. Then you can locate
    your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>.
  </li>
</ul>

</body>
</subsection>
<subsection>
<title>Booting the Installer LiveCD</title>
<body>

<impo>
Read this whole subsection before continuing, as you will probably not have the
opportunity to read it before doing things later.
</impo>

<p>
Once you have burned your LiveCD, it is time to boot it. Remove all CDs from
your CD drives, reboot your system and enter the BIOS.  This is usually done by
hitting DEL, F1 or ESC, depending on your BIOS. Inside  the BIOS, change the
boot order so that the CD-ROM is tried before the hard disk. This is often
found under "CMOS Setup". If you don't do this, your system will just reboot
from the hard disk, ignoring the CD-ROM.
</p>

<p>
Now place the LiveCD in the CD-ROM drive and reboot. You should see a boot
prompt. At this screen, you can hit Enter to begin the boot process with the
default boot options, or boot the LiveCD with custom boot options by specifying
a kernel followed by boot options and then hitting Enter.
</p>

<p>
Specifying a kernel? Yes, we provide a few kernels on our LiveCD. The default
one is <c>gentoo</c>. Other kernels are for specific hardware needs and the
<c>-nofb</c> variants which disable framebuffer.
</p>

<p>
Below you'll find a short overview on the available kernels:
</p>

<table>
<tr>
  <th>Kernel</th>
  <th>Description</th>
</tr>
<tr test="func:keyval('arch')='x86'">
  <ti>gentoo</ti>
  <ti>Default 2.6 kernel with support for multiple CPUs</ti>
</tr>
<tr test="func:keyval('arch')='x86'">
  <ti>gentoo-nofb</ti>
  <ti>Same as <c>gentoo</c> but without framebuffer support</ti>
</tr>
<tr test="func:keyval('arch')='AMD64'">
  <ti>gentoo</ti>
  <ti>
    Default kernel with support for K8 CPUS (including NUMA support) and EM64T
    CPUs
  </ti>
</tr>
<tr>
  <ti>memtest86</ti>
  <ti>Test your local RAM for errors</ti>
</tr>
</table>

<p>
You can also provide kernel options. They represent optional settings you can
(de)activate at will. The following list is the same as the one you receive
when you press F2 through F7 at the bootscreen.
</p>

<pre caption="Options available to pass to your kernel of choice">
<comment>Hardware options:</comment>

acpi=on         This loads support for ACPI and also causes the acpid daemon to
                be started by the CD on boot. This is only needed if your
                system requires ACPI to function properly.  This is not
                required for Hyperthreading support.

acpi=off        Completely disables ACPI.  This is useful on some older
                systems, and is also a requirement for using APM.  This will
                disable any Hyperthreading support of your processor.

console=X       This sets up serial console access for the CD.  The first
                option is the device, usually ttyS0 on x86, followed by any
                connection options, which are comma separated.  The default
                options are 9600,8,n,1.

dmraid=X        This allows for passing options to the device-mapper RAID
                subsystem.  Options should be encapsulated in quotes.

doapm           This loads APM driver support.  This requires you to also use
                acpi=off.

doslowusb       This adds some extra pauses into the boot process for the slow
                USB CDROM of the IBM BladeCenter.

dopcmcia        This loads support for PCMCIA and Cardbus hardware and also
                causes the pcmcia cardmgr to be started by the CD on boot.
                This is only required when booting from a PCMCIA/Cardbus device.

doscsi          This loads support for most SCSI controllers.  This is also a
                requirement for booting most USB devices, as they use the SCSI
                subsystem of the kernel.

hda=stroke      This allows you to partition the whole hard disk even when your
                BIOS is unable to handle large disks.  This option is only used
                on machines with an older BIOS.  Replace hda with the device
                that is requiring this option.

ide=nodma       This forces the disabling of DMA in the kernel and is required
                by some IDE chipsets and also by some CDROM drives.  If your
                system is having trouble reading from your IDE CDROM, try this
                option.  This also disables the default hdparm settings from
                being executed.

noapic          This disables the Advanced Programmable Interrupt Controller
                that is present on newer motherboards.  It has been known to
                cause some problems on older hardware.

nodetect        This disables all of the autodetection done by the CD,
                including device autodetection and DHCP probing.  This is
                useful for doing debugging of a failing CD or driver.

nodhcp          This disables DHCP probing on detected network cards.  This is
                useful on networks with only static addresses.

nodmraid        Disables support for device-mapper RAID, such as that used for
                on-board IDE/SATA RAID controllers.

nofirewire      This disables the loading of Firewire modules. This should only
                be necessary if your Firewire hardware is causing a problem
                with booting the CD.

nogpm           This disables gpm console mouse support.

nohotplug       This disables the loading of the hotplug and coldplug init
                scripts at boot.  This is useful for doing debugging of a
                failing CD or driver.

nokeymap        This disables the keymap selection used to select non-US
                keyboard layouts.

nolapic         This disables the local APIC on Uniprocessor kernels.

nosata          This disables the loading of Serial ATA modules.  This is
                useful if your system is having problems with the SATA subsystem.

nosmp           This disables SMP, or Symmetric Multiprocessing, on SMP-enabled
                kernels.  This is useful for debugging SMP-related issues with
                certain drivers and motherboards.

nosound         This disables sound support and volume setting.  This is useful
                for systems where sound support causes problems.

nousb           This disables the autoloading of USB modules.  This is useful
                for debugging USB issues.

<comment>Volume/Device Management:</comment>

dodevfs         This enables the deprecated device filesystem on 2.6 systems.
                You will also need to use noudev for this to take effect.
                Since devfs is the only option with a 2.4 kernel, this option
                has no effect if booting a 2.4 kernel.

doevms          This enables support for IBM's pluggable EVMS, or Enterprise
                Volume Management System. This is not safe to use with lvm.

dolvm           This enables support for Linux's Logical Volume Management.
                This is not safe to use with evms.

noudev          This disables udev support on 2.6 kernels.  This option
                requires that dodevfs is used. Since udev is not an option for
                2.4 kernels, this option has no effect if booting a 2.4
                kernel.

unionfs         Enables support for Unionfs on supported CD images.  This will
                create a writable Unionfs overlay in a tmpfs, allowing you to
                change any file on the CD.

unionfs=X       Enables support for Unionfs on supported CD images.  This will
                create a writable Unionfs overlay on the device you specify.
                The device must be formatted with a filesystem recognized and
                writable by the kernel.

<comment>Other options:</comment>

debug           Enables debugging code. This might get messy, as it displays
                a lot of data to the screen.

docache         This caches the entire runtime portion of the CD into RAM,
                which allows you to umount /mnt/cdrom and mount another CDROM.
                This option requires that you have at least twice as much
                available RAM as the size of the CD.

doload=X        This causes the initial ramdisk to load any module listed, as
                well as dependencies. Replace X with the module name. Multiple
                modules can be specified by a comma-separated list.

noload=X        This causes the initial ramdisk to skip the loading of a
                specific module that may be causing a problem.  Syntax matches
                that of doload.

nox             This causes an X-enabled LiveCD to not automatically start X,
                but rather, to drop to the command line instead.

scandelay       This causes the CD to pause for 10 seconds during certain
                portions the boot process to allow for devices that are slow to
                initialize to be ready for use.

scandelay=X     This allows you to specify a given delay, in seconds, to be
                added to certain portions of the boot process to allow for
                devices that are slow to initialize to be ready for use.
                Replace X with the number of seconds to pause.
</pre>

<p>
Now boot your CD, select a kernel (if you are not happy with the default
<c>gentoo</c> kernel) and boot options. As an example, we show you how
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel
parameters:
</p>

<pre caption="Booting an Installation CD">
boot: <i>gentoo dopcmcia</i>
</pre>

<p>
You will then be greeted with a boot screen and progress bar. If you are
installing Gentoo on a system with a non-US keyboard, make sure you
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no
selection is made in 10 seconds the default (US keyboard) will be accepted and
the boot process will continue. Once the boot process completes, Gnome will
start up and you will be automatically logged in to the "Live" Gentoo Linux
system as "gentoo" in graphical mode. You will be logged in as "root", the
superuser on the other consoles and should have a root ("#") prompt there. You
can switch to those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6.
Get back to the graphical desktop you started on by pressing Alt-F7. To switch
to other consoles from within X, you must prefix the above with Ctrl. You are
able to run commands as root from any terminal within the graphical environment
by using the <c>sudo</c> application. You can even become root within a
terminal to perform multiple tasks.
</p>

<pre caption="Using sudo to run applications">
<comment>(Example only)</comment>
<comment>(Editing the group file)</comment>
# <i>sudo vi /etc/group</i>
<comment>(Becoming root for a session)</comment>
# <i>sudo su -</i>
</pre>

</body>
</subsection>
<subsection id="hardware">
<title>Extra Hardware Configuration</title>
<body>

<p>
When the LiveCD boots, it tries to detect all your hardware devices and loads
the appropriate kernel modules to support your hardware. In the vast majority
of cases, it does a very good job. However, in some cases, it may not auto-load
the kernel modules you need. If the PCI auto-detection missed some of your
system's hardware, you will have to load the appropriate kernel modules
manually. These tasks require root access.
</p>

<p>
In the next example we try to load the <c>8139too</c> module (support for
certain kinds of network interfaces):
</p>

<pre caption="Loading kernel modules">
# <i>modprobe 8139too</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Tweaking Hard Disk Performance</title>
<body>

<p>
If you are an advanced user, you might want to tweak the IDE hard disk
performance using <c>hdparm</c>. You will need root access to use <c>hdparm</c>.
With the <c>-tT</c> options you can test the performance of your disk (execute
it several times to get a more precise impression):
</p>

<pre caption="Testing disk performance">
# <i>hdparm -tT /dev/hda</i>
</pre>

<p>
To tweak, you can use any of the following examples (or experiment
yourself) which use <path>/dev/hda</path> as disk (substitute with your
disk):
</p>

<pre caption="Tweaking hard disk performance">
<comment>(Activate DMA:)</comment>
# <i>hdparm -d 1 /dev/hda</i>
<comment>(Or with Safe Performance Options:)</comment>
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
</pre>

</body>
</subsection>
<subsection id="useraccounts">
<title>Optional: User Accounts</title>
<body>

<p>
If you plan on giving other people access to your installation environment or
you want to chat using <c>irssi</c> without root privileges (for security
reasons), you need to create the necessary user accounts and change the root
password. You need root access to change the root password and add new users.
</p>

<p>
To change the root password, use the <c>passwd</c> utility:
</p>

<pre caption="Changing the root password">
$ <i>sudo su -</i>
# <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
</pre>

<p>
To create a user account, we first enter their credentials, followed by its
password. We use <c>useradd</c> and <c>passwd</c> for these tasks. In the next
example, we create a user called "john".
</p>

<pre caption="Creating a user account">
# <i>useradd -m -G users john</i>
# <i>passwd john</i>
New password: <comment>(Enter john's password)</comment>
Re-enter password: <comment>(Re-enter john's password)</comment>
</pre>

<p>
You can change your user id from root to the newly created user by using
<c>su</c>:
</p>

<pre caption="Changing user id">
# <i>su - john</i>
</pre>

<p>
You can also change the password for the "gentoo" user in the graphical
environment. This account is already suitable for use on the Internet.
</p>

<pre caption="Changing the gentoo password">
$ <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Viewing Documentation while Installing</title>
<body>

<p>
If you want to view the Gentoo Handbook (either from-CD or online) during the
installation, you can view it with Mozilla Firefox (from the graphical
environment) or with <c>links</c> (from a terminal environment).
</p>

<pre caption="Viewing the on-CD documentation with Firefox">
# <i>firefox /mnt/cdrom/docs/handbook/html/index.html</i>
</pre>

<p>
If you would prefer to use <c>links</c> to see a text-only version of the
handbook, make sure you have created a user account (see <uri
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c>
to go to a new terminal and log in.
</p>

<pre caption="Viewing the on-CD documentation with links">
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
</pre>

<p>
You can go back to your original window by pressing <c>Alt-F7</c>.
</p>

<p>
However, it is preferred that you use the online Gentoo Handbook as it will be
more recent than the one provided on the CD. You can view it using Firefox or
<c>links</c> as well, but only after having completed the <e>Configuring your
Network</e> chapter (otherwise you won't be able to go on the Internet to view
the document):
</p>

<pre caption="Viewing the online documentation with Firefox">
# <i>firefox http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
</pre>

<pre caption="Viewing the online documentation with links">
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
</pre>

<p>
You can now choose to proceed by using the <uri link="?part=1&amp;chap=3">GTK+
based installer</uri> (which needs X) or the <uri
link="?part=1&amp;chap=4">Dialog based installer</uri> that can be run on a
console.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-gtkfe.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gtkfe.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gtkfe.xml?rev=1.1&content-type=text/plain

Index: hb-install-gtkfe.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-gtkfe.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<!--  The content of this document is licensed under the CC-BY-SA license -->
<!--  See http://creativecommons.org/licenses/by-sa/2.5 -->

<sections>

<version>4.0</version>
<date>2007-06-02</date>

<section>
<title>Welcome</title>
<subsection>
<title>Before you begin</title>
<body>

<p>
The Gentoo Linux Installer (GLI) provides a friendly introduction to the process
of installing Gentoo on your computer. Remember to read each option carefully.
There is detailed help available for each step of installation; just look to
the left of each screen. We recommend that you always read the help pages before
making your choices. Note that at any time during the installation process, you
can save your configuration progress in case you need to resume your
installation at a later time.
</p>

</body>
</subsection>
</section>

<section>
<title>Partitioning</title>
<subsection>
<title>Preparing the disks</title>
<body>

<p>
In order to install Gentoo on your machine, you will need to prepare your
disks. The <e>Partitioning</e> screen will show you a list of detected disks and
allow you to specify the filesystems you would like to have on your
partitions. Clicking <c>Clear partitions</c> will erase all previous partitions on
your disk, so be careful with this option! It is also possible to resize
certain partition types.
</p>

<p>
If you choose to go with the <c>Recommended layout</c>, the installer will erase
any previous partitions on your disk and create three partitions: 100MB for
<path>/boot</path>, a <path>/swap</path> partition up to 512MB in size, and the
rest of the available space on the disk is used for <path>/</path>, the root
partition.
</p>

<warn>
As with any partitioning application, you should backup your system before
making changes to your partition table, as any possible bugs could cause data
loss. Any changes you make to your partition table will be performed by the
installer immediately.
</warn>

</body>
</subsection>
</section>

<section>
<title>Timezone</title>
<subsection>
<title>Choose your timezone</title>
<body>

<p>
Study the map and select the region closest to your actual location. Later,
you will be asked to select if you want your clock to be set to UTC or local
time.
</p>

</body>
</subsection>
</section>

<section>
<title>Networking</title>
<subsection>
<title>Device information</title>
<body>

<p>
On this screen, you will be able to configure the various network interface
devices on your computer. Read the available options carefully.
</p>

<p>
On the <e>Hostname/Proxy Information/Other</e> tab, you will need to choose a
hostname for your machine. You may also specify proxy server and DNS settings
if needed.
</p>

</body>
</subsection>
</section>

<section>
<title>Users</title>
<subsection>
<title>Adding users and groups</title>
<body>

<p>
First set the root password for the system administrator (the <e>root</e>
user).
</p>

<p>
We <e>strongly</e> recommend that you create a regular user for daily work.
Working as root all the time is <e>dangerous</e> and should be avoided! Create
your users, add them to the appropriate groups, and set their passwords. You
can optionally change their home directories, select their login shell, and
set helpful comments.
</p>

</body>
</subsection>
</section>

<section>
<title>Extra Packages</title>
<subsection>
<title>Optional: installing extra packages</title>
<body>

<p>
The LiveCD contains a number of available pre-built packages. If you wish to
install any of them, check the appropriate box.
</p>

</body>
</subsection>
</section>

<section>
<title>Startup Services</title>
<subsection>
<body>

<p>
This screen allows you to choose various services to load at system boot.
Study the available options and their descriptions carefully, and then select
your desired services. For example, if you have chosen to install
<c>xorg-x11</c> and want to boot straight into a graphical desktop, then you
would select "xdm" from the list.
</p>

</body>
</subsection>
</section>

<section>
<title>Other Settings</title>
<subsection>
<title>Miscellaneous options</title>
<body>

<p>
Now you will be able to change various settings, including keyboard layout,
graphical display manager, the default editor, and whether to set your
hardware clock to UTC or local time.
</p>

</body>
</subsection>
</section>

<section>
<title>Finishing Up</title>
<subsection>
<body>

<p>
At this point, you're done. You can reboot into your new Gentoo system at any
time.
</p>

<p>
Congratulations, your system is now fully equipped! Continue with <uri
link="?part=1&amp;chap=5">Where to go from here?</uri> to learn more about
Gentoo.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-bootloader.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/plain

Index: hb-install-hppa-bootloader.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-bootloader.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Installing PALO</title>
<body>

<p>
On the PA-RISC platform, the boot loader is called palo. You can find the
configuration file in <path>/etc/palo.conf</path>. Here is a sample
configuration:
</p>

<pre caption = "/etc/palo.conf example">
--commandline=2/<keyval id="kernel-name"/> root=/dev/sda4
--recoverykernel=/vmlinux.old
--init-partitioned=/dev/sda
</pre>

<p>
The first line tells palo the location of the kernel and which boot parameters
it must use. <c>2/<keyval id="kernel-name"/></c> means the kernel named
<c><keyval id="kernel-name"/></c> resides on the second partition. Beware, the
path to the kernel is relative to the partition, not to the root of your
filesystem.
</p>

<p>
The second line indicates which recovery kernel to use. If it is your
first install and you do not have a recovery kernel, please comment this
out. The third line indicates on which disk palo will reside. 
</p>

<p>
When configuration is done, just run <c>palo</c>.
</p>

<pre caption = "Applying the PALO configuration">
# <i>palo</i>
</pre>

<p>
Now continue with <uri link="#reboot">Rebooting the System</uri>.
</p>

</body>
</section>
<section id="reboot">
<title>Rebooting the System</title>
<subsection>
<body>

<p>
Exit the chrooted environment and unmount all mounted partitions. Then type in 
that one magical command you have been waiting for: <c>reboot</c>.
</p>

<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
# <i>exit</i>
cdimage ~# <i>cd</i>
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
cdimage ~# <i>reboot</i>
</pre>

<p>
Of course, don't forget to remove the bootable CD, otherwise the CD will be
booted again instead of your new Gentoo system.
</p>

<p>
Once rebooted in your Gentoo installation, finish up with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml?rev=1.1&content-type=text/plain

Index: hb-install-hppa-disk.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-26</date>

<section>
<title>Introduction to Block Devices</title>
<subsection>
<title>Block Devices</title>
<body>

<p>
We'll take a good look at disk-oriented aspects of Gentoo Linux
and Linux in general, including Linux filesystems, partitions and block devices.
Then, once you're familiar with the ins and outs of disks and filesystems,
you'll be guided through the process of setting up partitions and filesystems
for your Gentoo Linux installation.
</p>

<p>
To begin, we'll introduce <e>block devices</e>. The most famous block device is
probably the one that represents the first SCSI HD in a Linux system, namely
<path>/dev/sda</path>.
</p>

<p>
The block devices above represent an abstract interface to the disk. User
programs can use these block devices to interact with your disk without worrying
about whether your drives are IDE, SCSI or something else. The program can
simply address the storage on the disk as a bunch of contiguous,
randomly-accessible 512-byte blocks.
</p>

</body>
</subsection>
<subsection>
<title>Partitions and Slices</title>
<body>

<p>
Although it is theoretically possible to use a full disk to house your Linux
system, this is almost never done in practice. Instead, full disk block devices
are split up in smaller, more manageable block devices. On most systems,
these are called <e>partitions</e>. Other architectures use a similar technique,
called <e>slices</e>.
</p>

</body>
</subsection>
</section>
<section>
<title>Designing a Partitioning Scheme</title>
<subsection>
<title>How Many and How Big?</title>
<body>

<p>
The number of partitions is highly dependent on your environment. For instance,
if you have lots of users, you will most likely want to have your
<path>/home</path> separate as it increases security and makes backups easier.
If you are installing Gentoo to perform as a mailserver, your 
<path>/var</path> should be separate as all mails are stored inside 
<path>/var</path>. A good choice of filesystem will then maximise your 
performance. Gameservers will have a separate <path>/opt</path> as most gaming 
servers are installed there. The reason is similar for <path>/home</path>: 
security and backups. You will definitely want to keep <path>/usr</path> big:
not only will it contain the majority of applications, the Portage tree alone
takes around 500 Mbyte excluding the various sources that are stored in it.
</p>

<p>
As you can see, it very much depends on what you want to achieve. Separate
partitions or volumes have the following advantages:
</p>

<ul>
<li>
  You can choose the best performing filesystem for each partition or volume
</li>
<li>
  Your entire system cannot run out of free space if one defunct tool is
  continuously writing files to a partition or volume
</li>
<li>
  If necessary, file system checks are reduced in time, as multiple checks can
  be done in parallel (although this advantage is more with multiple disks than
  it is with multiple partitions)
</li>
<li>
  Security can be enhanced by mounting some partitions or volumes read-only, 
  nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
</li>
</ul>

<p>
However, multiple partitions have one big disadvantage: if not configured
properly, you might result in having a system with lots of free space on one
partition and none on another. There is also a 15-partition limit for SCSI and
SATA.
</p>

</body>
</subsection>
</section>
<section>
<title>Using fdisk on HPPA to Partition your Disk</title>
<body>

<p>
Use <c>fdisk</c> to create the partitions you want:
</p>

<pre caption="Partitioning the disk">
# <i>fdisk /dev/sda</i>
</pre>

<p>
HPPA machines use the PC standard DOS partition tables.  To create a new 
DOS partition table, simply use the <c>o</c> command.
</p>

<pre caption="Creating a DOS partition table">
# <i>fdisk /dev/sda</i>

Command (m for help): <i>o</i>
Building a new DOS disklabel.
</pre>

<p>
PALO (the HPPA bootloader) needs a special partition to work.  You have 
to create a partition of at least 16MB at the beginning of your disk.  
The partition type must be of type <e>f0</e> (Linux/PA-RISC boot).
</p>

<impo>
If you ignore this and continue without a special PALO partition, your system
will stop loving you and fail to start. Also, if your disk is larger than 2GB,
make sure that the boot partition is in the first 2GB of your disk. PALO is
unable to read a kernel after the 2GB limit.
</impo>

<pre caption="A simple default partition schema">
# <i>cat /etc/fstab</i>
/dev/sda2    /boot   ext3    noauto,noatime   1 1
/dev/sda3    none    swap    sw               0 0
/dev/sda4    /       ext3    noatime          0 0

# <i>fdisk /dev/sda</i>

Command (m for help): <i>p</i>

Disk /dev/sda: 4294 MB, 4294816768 bytes
133 heads, 62 sectors/track, 1017 cylinders
Units = cylinders of 8246 * 512 = 4221952 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           8       32953   f0  Linux/PA-RISC boot
/dev/sda2               9          20       49476   83  Linux
/dev/sda3              21          70      206150   82  Linux swap
/dev/sda4              71        1017     3904481   83  Linux
</pre>

<p>
Now that your partitions are created, you can now continue with <uri
link="#filesystems">Creating Filesystems</uri>.
</p>

</body>
</section>
<section id="filesystems">
<title>Creating Filesystems</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your partitions are created, it is time to place a filesystem on them. 
If you don't care about what filesystem to choose and are happy with what we use
as default in this handbook, continue with <uri 
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
Otherwise read on to learn about the available filesystems...
</p>

</body>
</subsection>
<subsection>
<title>Filesystems?</title>
<body>

<p>
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable
on the HPPA architecture. The others are very experimental.
</p>

<p>
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
journaling, which means that routine ext2 filesystem checks at startup time can
be quite time-consuming. There is now quite a selection of newer-generation
journaled filesystems that can be checked for consistency very quickly and are
thus generally preferred over their non-journaled counterparts. Journaled
filesystems prevent long delays when you boot your system and your filesystem
happens to be in an inconsistent state.
</p>

<p>
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
journaling for fast recovery in addition to other enhanced journaling modes like
full data and ordered data journaling. It uses an HTree index that enables high
performance in almost all situations. In short, ext3 is a very good and reliable
filesystem.
</p>

<p>
<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
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. ReiserFS is solid and usable as
both general-purpose filesystem and for extreme cases such as the creation of
large filesystems, very large files and directories containing tens of
thousands of small files.
</p>

<p>
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
feature-set and is optimized for scalability. We only recommend using this
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
an uninterruptible power supply. Because XFS aggressively caches in-transit data
in RAM, improperly designed programs (those that don't take proper precautions
when writing files to disk and there are quite a few of them) can lose a good
deal of data if the system goes down unexpectedly.
</p>

<p>
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently 
become production-ready and there hasn't been a sufficient track record to 
comment positively nor negatively on its general stability at this point.
</p>

</body>
</subsection>
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>

<p>
To create a filesystem on a partition or volume, there are tools available for 
each possible filesystem:
</p>

<table>
<tr>
  <th>Filesystem</th>
  <th>Creation Command</th>
</tr>
<tr>
  <ti>ext2</ti>
  <ti><c>mke2fs</c></ti>
</tr>
<tr>
  <ti>ext3</ti>
  <ti><c>mke2fs -j</c></ti>
</tr>
<tr>
  <ti>reiserfs</ti>
  <ti><c>mkreiserfs</c></ti>
</tr>
<tr>
  <ti>xfs</ti>
  <ti><c>mkfs.xfs</c></ti>
</tr>
<tr>
  <ti>jfs</ti>
  <ti><c>mkfs.jfs</c></ti>
</tr>
</table>

<p>
For instance, to have the boot partition (<path>/dev/sda2</path> in our
example) in ext2 and the root partition (<path>/dev/sda4</path> in our example)
in ext3 (as in our example), you would use:
</p>

<pre caption="Applying a filesystem on a partition">
# <i>mke2fs /dev/sda2</i>
# <i>mke2fs -j /dev/sda4</i>
</pre>

<p>
Now create the filesystems on your newly created partitions (or logical
volumes).
</p>

</body>
</subsection>
<subsection>
<title>Activating the Swap Partition</title>
<body>

<p>
<c>mkswap</c> is the command that is used to initialize swap partitions:
</p>

<pre caption="Creating a Swap signature">
# <i>mkswap /dev/sda3</i>
</pre>

<p>
To activate the swap partition, use <c>swapon</c>:
</p>

<pre caption="Activating the swap partition">
# <i>swapon /dev/sda3</i>
</pre>

<p>
Create and activate the swap now.
</p>

</body>
</subsection>
</section>
<section>
<title>Mounting</title>
<subsection>
<body>

<p>
Now that your partitions are initialized and are housing a filesystem, it is
time to mount those partitions. Use the <c>mount</c> command. Don't forget to
create the necessary mount directories for every partition you created. As an
example we mount the root and boot partition:
</p>

<pre caption="Mounting partitions">
# <i>mount /dev/sda4 /mnt/gentoo</i>
# <i>mkdir /mnt/gentoo/boot</i>
# <i>mount /dev/sda2 /mnt/gentoo/boot</i>
</pre>

<note>
If you want your <path>/tmp</path> to reside on a separate partition, be sure to
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This
also holds for <path>/var/tmp</path>.
</note>

<p>
We will also have to mount the proc filesystem (a virtual interface with the
kernel) on <path>/proc</path>. But first we will need to place our files on the
partitions.
</p>

<p>
Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
Installation Files</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-kernel.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-kernel.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/plain

Index: hb-install-hppa-kernel.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-kernel.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-08-12</date>

<section>
<title>Timezone</title>
<body>

<p>
You first need to select your timezone so that your system knows where it is
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
it to <path>/etc/localtime</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact
GMT+8.
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
</pre>

</body>
</section>
<section>
<title>Installing the Sources</title>
<subsection>
<title>Choosing a Kernel</title>
<body>

<p>
The core around which all distributions are built is the Linux kernel. It is the
layer between the user programs and your system hardware. Gentoo provides its
users several possible kernel sources. A full listing with description is
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
Guide</uri>. 
</p>

<p>
For HPPA we have <c>hppa-sources</c>. By default these sources are based on the
2.6 kernel sources.
</p>

<pre caption="Installing a kernel source">
# <i>emerge hppa-sources</i>
</pre>

<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
kernel source points to <c>hppa-sources-<keyval id="kernel-version"/></c>.  Your
version may be different, so keep this in mind. 
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
</pre>

<p>
Now it is time to configure and compile your kernel source. All architectures 
can use <c>genkernel</c> for this, which will build a generic kernel as used 
by the Installation CD. We explain the "manual" configuration first though, as
it is the best way to optimize your environment.
</p>

<p>
If you want to manually configure your kernel, continue now with <uri
link="#manual">Default: Manual Configuration</uri>. If you want to use 
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using 
genkernel</uri> instead.
</p>

</body>
</subsection>
</section>
<section id="manual">
<title>Default: Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Manually configuring a kernel is often seen as the most difficult procedure a
Linux user ever has to perform. Nothing is less true -- after configuring a
couple of kernels you don't even remember that it was difficult ;)
</p>

<p>
However, one thing <e>is</e> true: you must know your system when you start
configuring a kernel manually. Most information can be gathered by emerging 
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
be able to  use <c>lspci</c> within the chrooted environment. You may safely 
ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
uses (it might provide you with a nice hint on what to enable).
</p>

<p>
Now go to your kernel source directory and execute <c>make menuconfig</c>. This
will fire up an ncurses-based configuration menu.
</p>

<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
# <i>make menuconfig</i>
</pre>

<p>
You will be greeted with several configuration sections. We'll first list some
options you must activate (otherwise Gentoo will not function, or not function
properly without additional tweaks).
</p>

</body>
</subsection>
<subsection>
<title>Activating Required Options</title>
<body>

<p>
First of all, activate the use of development and experimental code/drivers.
You need this, otherwise some very important code/drivers won't show up:
</p>

<pre caption="Selecting experimental code/drivers">
General setup ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
</pre>

<p>
Now go to <c>File Systems</c> and select support for the filesystems you use.
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
file system</c>.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [*] Virtual memory file system support (former shm fs)

<comment>(Select one or more of the following options as needed by your system)</comment>
  &lt;*&gt; Reiserfs support
  &lt;*&gt; Ext3 journalling file system support
  &lt;*&gt; JFS filesystem support
  &lt;*&gt; Second extended fs support
  &lt;*&gt; XFS filesystem support
</pre>

<p>
If you are using PPPoE to connect to the Internet or you are using a dial-up
modem, you will need the following options in the kernel:
</p>

<pre caption="Selecting PPPoE necessary drivers">
Device Drivers ---&gt;
  Networking support ---&gt;
    &lt;*&gt; PPP (point-to-point protocol) support
    &lt;*&gt;   PPP support for async serial ports
    &lt;*&gt;   PPP support for sync tty ports
</pre>

<p>
The two compression options won't harm but are not definitely needed, neither
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
when configured to do kernel mode PPPoE.
</p>

<p>
If you require it, don't forget to include support in the kernel for your
ethernet card.
</p>

<p>
If you have a HIL mouse or keyboard, do not forget to compile in support for
them.
</p>

<pre caption="Activating HIL support">
Input core support ---&gt;
  [*] Keyboard support
  [*] Mouse support
  [*] Event interface support
</pre>

<p>
If you have no mouse on your HIL port, only use the basic support:
</p>

<pre caption="Basic HIL support">
HIL support ---&gt;
  [*] HIL Keyboard (basic) support
</pre>

<p>
If you however want <e>full</e> HIL support, select the following options:
</p>

<pre caption="Full HIL support">
HIL support ---&gt;
  [*] HP System Device Controller i8042 Support
  [*] HIL MLC Support
  [*] HIL Keyboard (full) support
  [*] HIL Mouse &amp; Pointer support
</pre>

<p>
Also include display driver support:
</p>

<pre caption="Display Driver support">
Graphics support ---&gt;
  [*] Support for frame buffer devices
      [*] HP STI frame buffer device support
  Console display driver support ---&gt;
      [*] STI text console
</pre>

<p>
When you're done configuring your kernel, continue with <uri
link="#compiling">Compiling and Installing</uri>.
</p>

</body>
</subsection>
<subsection id="compiling">
<title>Compiling and Installing</title>
<body>

<impo>
If you want to compile a 64-bit kernel, you'll need to emerge <c>kgcc64</c>
<e>after</e> you've finished installing Gentoo and rebooted. However, running a
64-bit kernel is discouraged. You should only run a 64-bit kernel if you have
more than 4GB of RAM or if your server requires it, i.e. on the A500.
</impo>

<p>
Now that your kernel is configured, it is time to compile and install it. Exit 
the configuration and start the compilation process:
</p>

<pre caption="Compiling the kernel">
# <i>make &amp;&amp; make modules_install</i>
</pre>

<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel
choice and remember it as you will need it later on when you configure your
bootloader. Remember to replace <path>&lt;kernel-version&gt;</path> with the
name and version of your kernel.
</p>

<pre caption="Installing the kernel">
# <i>cp vmlinux /boot/&lt;kernel-version&gt;</i>
</pre>

<p>
Now continue with <uri link="#kernel_modules">Configuring Kernel
Modules</uri>.
</p>

</body>
</subsection>
</section>
<section id="genkernel">
<title>Alternative: Using genkernel</title>
<body>

<p>
If you are reading this section, you have chosen to use our <c>genkernel</c>
script to configure your kernel for you.
</p>

<p>
Now that your kernel source tree is installed, it's now time to compile your
kernel by using our <c>genkernel</c> script to automatically build a kernel for
you. <c>genkernel</c> works by configuring a kernel nearly identically to the
way our Installation CD kernel is configured. This means that when you use
<c>genkernel</c> to build your kernel, your system will generally detect all
your hardware at boot-time, just like our Installation CD does. Because
genkernel doesn't require any manual kernel configuration, it is an ideal
solution for those users who may not be comfortable compiling their own
kernels.
</p>

<p>
Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
</p>

<pre caption="Emerging genkernel">
# <i>emerge genkernel</i>
</pre>

<p>
Now, compile your kernel sources by running <c>genkernel all</c>.
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all 
hardware, this compilation will take quite a while to finish!
</p>

<p>
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you
need to manually configure your kernel using <c>genkernel --menuconfig all</c>
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a
module).
</p>

<pre caption="Running genkernel">
# <i>genkernel all</i>
</pre>

<p>
Once <c>genkernel</c> completes, a kernel, full set of modules and 
<e>initial root disk</e> (initrd) will be created. We will use the kernel 
and initrd when configuring a boot loader later in this document. Write
down the names of the kernel and initrd as you will need it when writing
the bootloader configuration file. The initrd will be started immediately after 
booting to perform hardware autodetection (just like on the Installation CD) 
before your "real" system starts up.
</p>

<pre caption="Checking the created kernel image name and initrd">
# <i>ls /boot/kernel* /boot/initramfs*</i>
</pre>

</body>
</section>
<section id="kernel_modules">
<title>Configuring Kernel Modules</title>
<subsection>
<title>Configuring the Modules</title>
<body>

<p>
You should list the modules you want automatically loaded in 
<path>/etc/modules.autoload.d/kernel-2.6</path>.
You can add extra options to the modules too if you want.
</p>

<p>
To view all available modules, run the following <c>find</c> command. Don't
forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
just compiled:
</p>

<pre caption="Viewing all available modules">
# <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
</pre>

<p>
For instance, to automatically load the <c>3c59x.ko</c> module, edit the
<path>kernel-2.6</path> file and enter the module
name in it.
</p>

<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
</pre>

<pre caption="/etc/modules.autoload.d/kernel-2.6">
3c59x
</pre>

<p>
Continue the installation with <uri link="?part=1&amp;chap=8">Configuring 
your System</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-medium.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-medium.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-medium.xml?rev=1.1&content-type=text/plain

Index: hb-install-hppa-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-medium.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-29</date>

<section>
<title>Hardware Requirements</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Before we start, we first list what hardware requirements you need to
successfully install Gentoo on your box. 
</p>

</body>
</subsection>
<subsection>
<title>Hardware Requirements</title>
<body>

<p>
A list of supported hardware can be found on the <uri
link="http://www.pateam.org/list.html">PA Team website</uri>. You may find
additional information about your box in the <uri
link="http://hwdb.parisc-linux.org">Parisc-Linux Hardware Database</uri> and
the <uri link="http://www.openpa.net/cpu.html">processor list</uri> on
<uri link="http://www.openpa.net">www.openpa.net</uri>.
</p>

<p>
If you don't know which version of PA-RISC your box is using, please check the
links above to find out whether you're using version 1.1 or 2.0. You will need
this information later on.
</p>

<table>
<tr>
  <th>Memory</th>
  <ti>64 MB</ti>
</tr>
<tr>
  <th>Diskspace</th>
  <ti>1.5 GB (excluding swap space)</ti>
</tr>
<tr>
  <th>Swap space</th>
  <ti>At least 256 MB</ti>
</tr>
</table>

</body>
</subsection>
</section>

<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using a <e>stage3</e> tarball file.
Such a tarball is an archive that contains a minimal environment from
which you can succesfully install Gentoo Linux onto your system.
</p>

<p>
Installations using a stage1 or stage2 tarball file are not documented in the
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo
FAQ</uri> on these matters.
</p>

</body>
</subsection>
<subsection>
<title>Gentoo Universal Installation CD</title>
<body>

<p>
An Installation CD is a bootable medium which contains a self-sustained Gentoo 
environment. It allows you to boot Linux from the CD. During the boot process 
your hardware is detected and the appropriate drivers are loaded. The Gentoo 
Installation CDs are maintained by Gentoo developers.
</p>

<p>
There currently are two Installation CDs available:
</p>

<ul>
  <li>
    The Universal Installation CD contains everything you need to install 
    Gentoo. It provides stage3 files for common architectures, source code 
    for the extra applications you need to choose from and, of course, the 
    installation instructions for your architecture.
  </li>
  <li>
    The Minimal Installation CD contains only a minimal environment that allows 
    you to boot up and configure your network so you can connect to the 
    Internet. It does not contain any additional files and cannot be used 
    during the current installation approach.
  </li>
</ul>

</body>
</subsection>
</section>
<!-- STOP -->
<section>
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title>
<subsection>
<title>Downloading and Burning the Installation CD</title>
<body>

<p>
You can download the Universal Installation CD from one of our <uri 
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in 
the <path><keyval id="release-dir"/>installcd</path> directory.
</p>

<p>
Inside those directories you'll find ISO files. Those are full CD images which
you can write on a CD-R.
</p>

<p>
After downloading the file, you can verify its integrity to see if it is 
corrupted or not:
</p>

<ul>
  <li>
    You can check its MD5 checksum and compare it with the MD5 checksum we 
    provide (for instance with the <c>md5sum</c> tool under Linux/Unix or 
    <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows)
  </li>
  <li>
    You can verify the cryptographic signature that we provide. You need to
    obtain the public key we use (17072058) before you proceed though.
  </li>
</ul>

<p>
To fetch our public key using the GnuPG application, run the following command:
</p>

<pre caption="Obtaining the public key">
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i>
</pre>

<p>
Now verify the signature:
</p>

<pre caption="Verify the cryptographic signature">
$ <i>gpg --verify &lt;signature file&gt; &lt;downloaded iso&gt;</i>
</pre>

<p>
To burn the downloaded ISO(s), you have to select raw-burning. How you
do this is highly program-dependent. We will discuss <c>cdrecord</c> and
<c>K3B</c> here; more information can be found in our <uri
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>.
</p>

<ul>
  <li>
    With cdrecord, you simply type <c>cdrecord dev=/dev/hdc &lt;downloaded iso
    file&gt;</c> (replace <path>/dev/hdc</path> with your CD-RW drive's device
    path).
  </li>
  <li>
    With K3B, select <c>Tools</c> &gt; <c>Burn CD Image</c>. Then you can locate
    your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>.
  </li>
</ul>

</body>
</subsection>
<subsection>
<title>Booting the Universal Installation CD</title>
<body>

<note>
If you have problems booting the Installation CD or any other media, please 
read the <uri 
link="http://www.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html">
PA-RISC Linux Boot HOWTO</uri>.
</note>

<p>
Boot your HPPA system. During the boot process, you will see a message similar
to the following:
</p>

<pre caption="HPPA boot message">
Searching for Potential Boot Devices.
To terminate search, press and hold the ESCAPE key.
</pre>

<p>
When this message appears, press and hold the Esc-key until an option menu
appears. This can take a while, be patient. By default, you should enter the
BOOT_ADMIN console. If you receive an option menu, choose <c>Enter Boot
Administration mode</c> to enter the BOOT_ADMIN console. You should now have an
'&gt;' prompt.
</p>

<p>
Put the Gentoo Installation CD in the CD-ROM. If you do not know the SCSI ID of 
your CD-ROM drive, your PA-RISC station will search for it when you issue the 
<c>search</c> command.
</p>

<pre caption="Searching for SCSI ID">
&gt; <i>search</i>
Searching for Devices with Bootable Media.
To terminate search, please press and hold the ESCAPE key.
</pre>

<p>
Your PA-RISC station will now display all the available boot media. This is an
example result of this command:
</p>

<pre caption="Available boot media">
Device Selection      Device Path             Device Type and Utilities
---------------------------------------------------------------------------

P0                    scsi.5.0                TOSHIBA CD-ROM XM-3301TA
                                                  IPL
P1                    scsi.2.0                COMPAQ ST32550N
                                                  IPL
P2                    lan.0010a7-06d1b6.3.6   server
                                                  IPL
</pre>

<p>
To boot from a CD-ROM you need the accompanying Device Path. For instance, if we
want to boot from the TOSHIBA CD-ROM in the above example, we would need to type
the following command:
</p>

<pre caption="Booting from a CD-ROM">
&gt; <i>boot scsi.5.0 ipl</i>

Trying scsi.5.0
</pre>

<p>
The <c>ipl</c> keyword (Initial Program Loader) tells palo (the PA-RISC boot
LOader) to enter interactive mode. This will allow you to change, for example,
the kernel boot parameters.
</p>

<p>
When the boot is successful, palo will start in interactive mode:
</p>

<pre caption="PALO Interactive Mode">
Boot path initialized.
Attempting to load IPL.


HARD Booted.
palo ipl 1.5 root@hope Sat Apr 23 18:06:47 CEST 2005

Boot image contains:
    0/vmlinux32 6241293 bytes @ 0x3904000
    0/vmlinux64 8352719 bytes @ 0x3ef8000
    0/ramdisk 1007589 bytes @ 0x105800

Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).Current command line:
0/vmlinux initrd=initrd TERM=linux root=/dev/ram0 init=/linuxrc cdroot looptype=squashfs loop=/livecd.squashfs hda=scsi console=ttyS0
 0: 0/vmlinux
 1: initrd=initrd
 2: TERM=linux
 3: root=/dev/ram0
 4: init=/linuxrc
 5: cdroot
 6: looptype=squashfs
 7: loop=/livecd.squashfs
 8: hda=scsi
 9: console=ttyS0

&lt;#&gt;    edit the numbered field
'b'    boot with this command line
'r'    restore command line
'l'    list dir
</pre>

<p>
These parameters are suitable for most situations.
</p>

<p>
If you need extra features you must add the appropriate keyword(s) to the end of
the command line. To add a keyword, edit the last field, add a space and type 
your keyword. The only implemented keywords as of now are <c>cdcache</c> which 
tells the Installation CD to load itself into RAM, allowing you to unmount the
CD, and <c>noload=module1[,module2[,...]]</c> which allows you to explicitly 
disable loading of particular modules.
</p>

<pre caption="Adding hdb=scsi as boot option">
(or 'b' to boot with this command line)? <i>9</i>
console=ttyS0 <i>hdb=scsi</i>
</pre>

<p>
Now that you have tweaked your kernel boot params, boot it.
</p>

<pre caption="Booting the kernel">
(or 'b' to boot with this command line)? <i>b</i>
</pre>

<p>
You should have a root ("#") prompt on the current console and can also switch
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you
started on by pressing Alt-F1.
</p>

<p>
Now continue with <uri link="#hardware">Extra Hardware 
Configuration</uri>.
</p>

</body>
</subsection>
<subsection id="hardware">
<title>Extra Hardware Configuration</title>
<body>

<p>
Most hppa machines have an onboard ethernet card. Old ones use the lasi driver
which is compiled in the kernel. Newer ones need the tulip driver which is
compiled as a module. To use the latter, you need to load its driver.
</p>

<p>
In the next example, we try to load the <c>tulip</c> module (support for 
certain kinds of network interfaces):
</p>

<pre caption="Loading kernel modules">
# <i>modprobe tulip</i>
</pre>

</body>
</subsection>

<subsection id="useraccounts">
<title>Optional: User Accounts</title>
<body>

<p>
If you plan on giving other people access to your installation
environment or you want to chat using <c>irssi</c> without root privileges (for
security reasons), you need to create the necessary user accounts and change 
the root password.
</p>

<p>
To change the root password, use the <c>passwd</c> utility:
</p>

<pre caption="Changing the root password">
# <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
</pre>

<p>
To create a user account, we first enter their credentials, followed by
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks.
In the next example, we create a user called &quot;john&quot;.
</p>

<pre caption="Creating a user account">
# <i>useradd -m -G users john</i>
# <i>passwd john</i>
New password: <comment>(Enter john's password)</comment>
Re-enter password: <comment>(Re-enter john's password)</comment>
</pre>

<p>
You can change your user id from root to the newly created user by using
<c>su</c>:
</p>

<pre caption="Changing user id">
# <i>su - john</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Viewing Documentation while Installing</title>
<body>

<p>
If you want to view the Gentoo Handbook (either from-CD or online) during the
installation, make sure you have created a user account (see <uri
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to
go to a new terminal and log in.
</p>

<p>
If you want to view the documentation on the CD you can immediately run
<c>links</c> to read it:
</p>

<pre caption="Viewing the on-CD documentation">
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
</pre>

<p>
However, it is preferred that you use the online Gentoo Handbook as it will be
more recent than the one provided on the CD. You can view it using <c>links</c>
as well, but only after having completed the <e>Configuring your Network</e>
chapter (otherwise you won't be able to go on the Internet to view the
document):
</p>

<pre caption="Viewing the Online Documentation">
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
</pre>

<p>
You can go back to your original terminal by pressing <c>Alt-F1</c>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Starting the SSH Daemon</title>
<body>

<p>
If you want to allow other users to access your computer during the
Gentoo installation (perhaps because those users are going to help you
install Gentoo, or even do it for you), you need to create a user
account for them and perhaps even provide them with your root password 
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
</p>

<p>
To fire up the SSH daemon, execute the following command:
</p>

<pre caption="Starting the SSH daemon">
# <i>/etc/init.d/sshd start</i>
</pre>

<p>
To be able to use sshd, you first need to set up your networking. Continue with
the chapter on <uri link="?part=1&amp;chap=3">Configuring your Network</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-network.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-network.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-network.xml?rev=1.1&content-type=text/plain

Index: hb-install-network.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-network.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Do you need Networking?</title>
<subsection>
<title>Who can do without?</title>
<body>

<p>
Generally, you don't need a working network connection to install Gentoo using
either the Universal InstallCD or the Installer LiveCD. However, there are some
circumstances where you do want to have a working Internet connection:
</p>

<ul>
  <li>
    The stage3 files that are stored in the Universal InstallCD do not 
    match your architecture and you need to download the correct stage3 file
  </li>
  <li>
    The stage3 file that is generated by the Installer LiveCD does not
    match your architecture and you need to download the correct stage3 file
  </li>
  <li>
    You need to install a specific networking application that will allow you to
    connect to the Internet which isn't available on the Universal InstallCD or
    the Installer LiveCD, but is supported by the CD (i.e. you can connect to
    the Internet using the CD but the necessary sources are not available on
    the CD)
  </li>
  <li>
    You want remote assistance during the installation (using SSH or through
    direct conversations using IRC)
  </li>
</ul>

</body>
</subsection>
<subsection>
<title>Do I need Networking?</title>
<body>

<p>
To find out if the stage3 file for your architecture is available and you are
using a Universal InstallCD, take a look inside <path>/mnt/cdrom/stages</path>
and check if one of the available stages matches your architecture. If not, you
can still opt for a stage3 file of an architecture compatible with yours.
</p>

<p>
The stage3 file built by the x86 Installer LiveCD is optimized for i686 or
better and uses NPTL.  The stage3 file built by the amd64 Installer LiveCD is
optimized for generic amd64 usage and uses NPTL.
</p>

<p>
If you, on the other hand, want to use a stage3 file optimized for your
architecture and the stage3 file of your choice is not available, then you will
need networking to download the appropriate stage3 file.
</p>

<p>
So, if you don't need networking, you can skip the rest of this chapter and 
continue with <uri link="?part=1&amp;chap=4">Preparing the Disks</uri>.
Otherwise, continue with the networking configuration sections below.
</p>

</body>
</subsection>
</section>
<section>
<title>Automatic Network Detection</title>
<subsection>
<title>Maybe it just works?</title>
<body>

<p>
If your system is plugged into an Ethernet network with a DHCP server, it is 
very likely that your networking configuration has already been set up 
automatically for you. If so, you should be able to take advantage of the many
included network-aware commands on the Installation CD such as <c>ssh</c>, 
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among 
others.
</p>

<p>
If networking has been configured for you, the <c>/sbin/ifconfig</c> command
should list some network interfaces besides lo, such as eth0:
</p>

<pre caption="/sbin/ifconfig for a working network configuration">
# <i>/sbin/ifconfig</i>
<comment>(...)</comment>
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 Base address:0xe800 
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Configure any Proxies</title>
<body>

<p>
If you access the Internet through a proxy, you might need to set up proxy
information during the installation. It is very easy to define a proxy: you just
need to define a variable which contains the proxy server information.
</p>

<p>
In most cases, you can just define the variables using the server hostname. As
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port 
is <c>8080</c>.
</p>

<pre caption="Defining proxy servers">
<comment>(If the proxy filters HTTP traffic)</comment>
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i>
<comment>(If the proxy filters FTP traffic)</comment>
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i>
<comment>(If the proxy filters RSYNC traffic)</comment>
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i>
</pre>

<p>
If your proxy requires a username and password, you should use the following
syntax for the variable:
</p>

<pre caption="Adding username/password to the proxy variable">
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080
</pre>

</body>
</subsection>
<subsection>
<title>Testing the Network</title>
<body>

<p>
You may want to try pinging your ISP's DNS server (found in
<path>/etc/resolv.conf</path>) and a Web site of your 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">
# <i>ping -c 3 www.gentoo.org</i>
</pre>

<p>
If you are now able to use your network, you can skip the rest of this
section and continue with <uri link="?part=1&amp;chap=4">Preparing the
Disks</uri>. If not, read on.
</p>

</body>
</subsection>
</section>
<section>
<title>Automatic Network Configuration</title>
<subsection>
<body>

<p>
If the network doesn't work immediately, some installation media allow you to 
use <c>net-setup</c> (for regular or wireless networks), <c>pppoe-setup</c> 
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86).
</p>

<p>
If your installation medium does not contain any of these tools or your network
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network 
Configuration</uri>.
</p>

<ul>
  <li>
    Regular Ethernet users should continue with <uri
    link="#net-setup">Default: Using net-setup</uri>
  </li>
  <li>
    ADSL users should continue with <uri link="#ppp">Alternative: Using
    PPP</uri>
  </li>
  <li>
    PPTP users should continue with <uri link="#pptp">Alternative:
    Using PPTP</uri>
  </li>
</ul>

</body>
</subsection>
<subsection id="net-setup">
<title>Default: Using net-setup</title>
<body>

<p>
The simplest way to set up networking if it didn't get configured
automatically is to run the <c>net-setup</c> script:
</p>

<pre caption="Running the net-setup script">
# <i>net-setup eth0</i>
</pre>

<p>
<c>net-setup</c> will ask you some questions about your network
environment. When all is done, you should have a working network
connection. Test your network connection as stated before. If the tests
are positive, congratulations! You are now ready to install Gentoo. Skip
the rest of this section and continue with <uri 
link="?part=1&amp;chap=4">Preparing the Disks</uri>.
</p>

<p>
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual
Network Configuration</uri>.
</p>


</body>
</subsection>
<subsection id="ppp">
<title>Alternative: Using PPP</title>
<body>

<p>
Assuming you need PPPoE to connect to the internet, the Installation CD (any
version) has made things easy for you by including <c>ppp</c>. Use the provided
<c>pppoe-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="Using ppp">
# <i>pppoe-setup</i>
# <i>pppoe-start</i>
</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. If your ethernet device doesn't exist, you will have to load
the appropriate network modules. In that case you should continue with 
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to
load the appropriate network modules there.
</p>

<p>
If everything worked, continue with <uri link="?part=1&amp;chap=4">Preparing the
Disks</uri>.
</p>

</body>
</subsection>
<subsection id="pptp">
<title>Alternative: Using PPTP</title>
<body>

<note>
PPTP support is only available for x86
</note>

<p>
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our
Installation CDs. But first you need to make sure that your configuration is 
correct. Edit <path>/etc/ppp/pap-secrets</path> or 
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password 
combination:
</p>

<pre caption="Editing /etc/ppp/chap-secrets">
# <i>nano -w /etc/ppp/chap-secrets</i>
</pre>

<p>
Then adjust <path>/etc/ppp/options.pptp</path> if necessary:
</p>

<pre caption="Editing /etc/ppp/options.pptp">
# <i>nano -w /etc/ppp/options.pptp</i>
</pre>

<p>
When all that is done, just run <c>pptp</c> (along with the options you couldn't
set in <path>options.pptp</path>) to connect the server:
</p>

<pre caption="Connection to a dial-in server">
# <i>pptp &lt;server ip&gt;</i>
</pre>

<p>
Now continue with <uri link="?part=1&amp;chap=4">Preparing the Disks</uri>.
</p>

</body>
</subsection>
</section>
<section>
<title>Manual Network Configuration</title>
<subsection>
<title>Loading the Appropriate Network Modules</title>
<body>

<p>
When the Installation CD boots, it tries to detect all your hardware devices and
loads the appropriate kernel modules (drivers) to support your hardware. In the
vast majority of cases, it does a very good job. However, in some cases,
it may not auto-load the kernel modules you need.
</p>

<p>
If <c>net-setup</c> or <c>pppoe-setup</c> failed, then it is possible that
your network card wasn't found immediately. This means you may have to load
the appropriate kernel modules manually.
</p>

<p>
To find out what kernel modules we provide for networking, use
<c>ls</c>:
</p>

<pre caption="Searching for provided modules">
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i>
</pre>

<p>
If you find a driver for your network card, use <c>modprobe</c> to load
the kernel module:
</p>

<pre caption="Using modprobe to load a kernel module">
<comment>(As an example, we load the pcnet32 module)</comment>
# <i>modprobe pcnet32</i>
</pre>

<p>
To check if your network card is now detected, use <c>ifconfig</c>. A
detected network card would result in something like this:
</p>

<pre caption="Testing availability of your network card, successful">
# <i>ifconfig eth0</i>
eth0      Link encap:Ethernet  HWaddr FE:FD:00:00:00:00  
          BROADCAST NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
</pre>

<p>
If however you receive the following error, the network card is not
detected:
</p>

<pre caption="Testing availability of your network card, failed">
# <i>ifconfig eth0</i>
eth0: error fetching interface information: Device not found
</pre>

<p>
If you have multiple network cards in your system they are named <e>eth0</e>,
<e>eth1</e>, etc. Make sure that the network card you want to use works well and
remember to use the correct naming throughout this document. We will assume that
the network card <e>eth0</e> is used.
</p>

<p>
Assuming that you now have a detected network card, you can 
retry <c>net-setup</c> or <c>pppoe-setup</c> again (which should work 
now), but for the hardcore people amongst you we explain how to configure your 
network manually.
</p>

<p>
Select one of the following sections based on your network setup:
</p>

<ul>
  <li><uri link="#install-dhcp">Using DHCP</uri> for automatic IP retrieval</li>
  <li>
    <uri link="#wireless">Preparing for Wireless Access</uri> if you have a
    wireless card
  </li>
  <li>
    <uri link="#network_term">Understanding Network Terminology</uri> explains
    what you need to know about networking
  </li>
  <li>
    <uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to
    set up your networking manually
  </li>
</ul>

</body>
</subsection>
<subsection id="install-dhcp">
<title>Using DHCP</title>
<body>

<p>
DHCP (Dynamic Host Configuration Protocol) makes it possible to
automatically receive networking information (IP address, netmask,
broadcast address, gateway, nameservers etc.). This only works if you
have a DHCP server in your network (or if your provider provides a DHCP
service). To have a network interface receive this information automatically, 
use <c>dhcpcd</c>:
</p>

<pre caption="Using dhcpcd">
# <i>dhcpcd eth0</i>
<comment>Some network admins require that you use the</comment>
<comment>hostname and domainname provided by the DHCP server.</comment>
<comment>In that case, use</comment>
# <i>dhcpcd -HD eth0</i>
</pre>

<p>
If this works (try pinging some internet server, like <uri
link="http://www.google.com">Google</uri>), then you are all set and
ready to continue. Skip the rest of this section and continue with <uri
link="?part=1&amp;chap=4">Preparing the Disks</uri>.
</p>

</body>
</subsection>
<subsection id="wireless">
<title>Preparing for Wireless Access</title>
<body>

<note>
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc
Installation CDs. You can still get the extensions working otherwise 
by following the instructions of the
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng
project</uri>.
</note>

<p>
If you are using a wireless (802.11) card, you may need to configure your
wireless settings before going any further. To see the current wireless settings
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show
something like:
</p>

<pre caption="Showing the current wireless settings">
# <i>iwconfig eth0</i>
eth0      IEEE 802.11-DS  ESSID:"GentooNode"                                   
          Mode:Managed  Frequency:2.442GHz  Access Point: 00:09:5B:11:CC:F2    
          Bit Rate:11Mb/s   Tx-Power=20 dBm   Sensitivity=0/65535               
          Retry limit:16   RTS thr:off   Fragment thr:off                       
          Power Management:off                                                  
          Link Quality:25/10  Signal level:-51 dBm  Noise level:-102 dBm        
          Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx          
          excessive retries:237 Invalid misc:350282 Missed beacon:84            
</pre>

<note>
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to
determine the correct device name.
</note>

<p>
For most users, there are only two settings that might be important to change,
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access
Point address listed are already that of your access point and you are not using
WEP, then your wireless is working. If you need to change your ESSID, or add a
WEP key, you can issue the following commands:
</p>

<pre caption="Changing ESSID and/or adding WEP key">
<comment>(This sets the network name to "GentooNode")</comment>
# <i>iwconfig eth0 essid GentooNode</i>

<comment>(This sets a hex WEP key)</comment>
# <i>iwconfig eth0 key 1234123412341234abcd</i>

<comment>(This sets an ASCII key - prefix it with "s:")</comment>
# <i>iwconfig eth0 key s:some-password</i>
</pre>

<p>
You can then confirm your wireless settings again by using <c>iwconfig</c>. 
Once you have wireless working, you can continue configuring the IP level
networking options as described in the next section (<uri
link="#network_term">Understanding Network Terminology</uri>) or use the
<c>net-setup</c> tool as described previously.
</p>

</body>
</subsection>
<subsection id="network_term">
<title>Understanding Network Terminology</title>
<body>

<note>
If you know your IP address, broadcast address, netmask and nameservers,
then you can skip this subsection and continue with <uri
link="#ifconfig_route">Using ifconfig and route</uri>.
</note>

<p>
If all of the above fails, you will have to configure your network manually.
This is not difficult at all. However, you need to be familiar with some
network terminology, as you will need it to be able to
configure your network to your satisfaction. After reading this, you
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for,
how a <e>broadcast</e> address is formed and why you need
<e>nameservers</e>.
</p>

<p>
In a network, hosts are identified by their <e>IP address</e> (Internet
Protocol address). Such an address is a combination of four numbers
between 0 and 255. Well, at least that is how we perceive it. In
reality, such an IP address consists of 32 bits (ones and zeros). Let's
view an example:
</p>

<pre caption="Example of an IP address">
IP Address (numbers):   192.168.0.2
IP Address (bits):      11000000 10101000 00000000 00000010
                        -------- -------- -------- --------
                           192      168       0        2
</pre>

<p>
Such an IP address is unique to a host as far as all accessible networks are
concerned (i.e. every host that you are able to reach must have a unique IP
address). In order to distinguish between hosts inside and outside a
network, the IP address is divided in two parts: the 
<e>network</e> part and the <e>host</e> part. 
</p>

<p>
The separation is written down with the <e>netmask</e>, a collection of
ones followed by a collection of zeros. The part of the IP that can be
mapped on the ones is the network-part, the other one is the host-part.
As usual, the netmask can be written down as an IP-address.
</p>

<pre caption="Example of network/host separation">
IP-address:    192      168      0         2
            11000000 10101000 00000000 00000010
Netmask:    11111111 11111111 11111111 00000000
               255      255     255        0
           +--------------------------+--------+
                    Network              Host
</pre>

<p>
In other words, 192.168.0.14 is still part of our example network, but
192.168.1.2 is not.
</p>

<p>
The <e>broadcast</e> address is an IP-address with the same network-part
as your network, but with only ones as host-part. Every host on your
network listens to this IP address. It is truly meant for broadcasting
packets.
</p>

<pre caption="Broadcast address">
IP-address:    192      168      0         2
            11000000 10101000 00000000 00000010
Broadcast:  11000000 10101000 00000000 11111111
               192      168      0        255
           +--------------------------+--------+
                     Network             Host
</pre>

<p>
To be able to surf on the internet, you must know which host shares the
Internet connection. This host is called the <e>gateway</e>. Since it is
a regular host, it has a regular IP address (for instance 192.168.0.1).
</p>

<p>
We previously stated that every host has its own IP address. To be able
to reach this host by a name (instead of an IP address) you need a
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP
address (such as <e>64.5.62.82</e>). Such a service is called a name
service. To use such a service, you must define the necessary <e>name
servers</e> in <path>/etc/resolv.conf</path>.
</p>

<p>
In some cases, your gateway also serves as nameserver. Otherwise you
will have to enter the nameservers provided by your ISP.
</p>

<p>
To summarise, you will need the following information before continuing:
</p>

<table>
<tr>
  <th>Network Item</th>
  <th>Example</th>
</tr>
<tr>
  <ti>Your IP address</ti>
  <ti>192.168.0.2</ti>
</tr>
<tr>
  <ti>Netmask</ti>
  <ti>255.255.255.0</ti>
</tr>
<tr>
  <ti>Broadcast</ti>
  <ti>192.168.0.255</ti>
</tr>
<tr>
  <ti>Gateway</ti>
  <ti>192.168.0.1</ti>
</tr>
<tr>
  <ti>Nameserver(s)</ti>
  <ti>195.130.130.5, 195.130.130.133</ti>
</tr>
</table>

</body>
</subsection>
<subsection id="ifconfig_route">
<title>Using ifconfig and route</title>
<body>

<p>
Setting up your network consists of three steps. First we assign
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to
the gateway using <c>route</c>. Then we finish up by placing the
nameserver IPs in <path>/etc/resolv.conf</path>.
</p>

<p>
To assign an IP address, you will need your IP address, broadcast
address and netmask. Then execute the following command, substituting
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your
broadcast address and <c>${NETMASK}</c> with your netmask:
</p>

<pre caption="Using ifconfig">
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i>
</pre>

<p>
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with
your gateway IP address:
</p>

<pre caption="Using route">
# <i>route add default gw ${GATEWAY}</i>
</pre>

<p>
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our
example, we use <c>nano</c>):
</p>

<pre caption="Creating /etc/resolv.conf">
# <i>nano -w /etc/resolv.conf</i>
</pre>

<p>
Now fill in your nameserver(s) using the following as a template. Make
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with
the appropriate nameserver addresses:
</p>

<pre caption="/etc/resolv.conf template">
nameserver ${NAMESERVER1}
nameserver ${NAMESERVER2}
</pre>

<p>
That's it. Now test your network by pinging some Internet server (like
<uri link="http://www.google.com">Google</uri>). If this works,
congratulations then. You are now ready to install Gentoo. Continue with <uri
link="?part=1&amp;chap=4">Preparing the Disks</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-next.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-next.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-next.xml?rev=1.1&content-type=text/plain

Index: hb-install-next.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-next.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Documentation</title>
<subsection>
<body>

<p>
Congratulations! You now have a working Gentoo system. But where to go from
here? What are your options now? What to explore first? Gentoo provides its
users with lots of possibilities, and therefore lots of documented (and less
documented) features.
</p>

<p>
You should definitely take a look at the next part of the Gentoo Handbook
entitled <uri link="?part=2">Working with Gentoo</uri> which explains
how to keep your software up to date, how to install more software, what USE 
flags are, how the Gentoo Init system works, etc.
</p>

<p>
If you are interested in optimizing your system for desktop use, or you want to
learn how to configure your system to be a full working desktop system, consult
our extensive <uri link="/doc/en/index.xml?catid=desktop">Gentoo Desktop
Documentation Resources</uri>. Besides, you might want to use our <uri
link="/doc/en/guide-localization.xml">localization guide</uri> to make your
system feel more at home.
</p>

<p>
We also have a <uri link="/doc/en/security/">Gentoo Security Handbook</uri>
which is worth reading.
</p>

<p>
For a full listing of all our available documentation check out our <uri
link="/doc/en/index.xml">Documentation Resources</uri> page.
</p>

</body>
</subsection>
</section>
<section>
<title>Gentoo Online</title>
<body>

<p>
You are of course always welcome on our <uri
link="http://forums.gentoo.org">Gentoo Forums</uri> or on one of our many 
<uri link="/main/en/irc.xml">Gentoo IRC channels</uri>.
</p>

<p>
We also have several <uri 
link="/main/en/lists.xml">mailinglists</uri> open to all 
our users. Information on how to join is contained in that page.
</p>

<p>
We'll shut up now and let you enjoy your installation :)
</p>

</body>
</section>
<section>
<title>Gentoo Changes since 2007.1</title>
<subsection>
<title>Changes?</title>
<body>

<p>
Gentoo is a fast-moving target. The following sections describe important
changes that affect a Gentoo installation. We only list those that have anything
in common with the installation, not with package changes that did not occur
during the installation.
</p>

<p>
There have been no significant changes since.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-bootloader.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc-bootloader.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-bootloader.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Choosing a Bootloader</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that the kernel is configured and compiled, you'll need a <e>bootloader</e>
to start your new linux installation.  The <e>bootloader</e> that you use will 
depend upon the type of PPC machine you have.
</p>

<p>
If you are using a NewWorld Apple or IBM machine, you need to use 
<uri link="#yaboot">yaboot</uri>.  OldWorld Apple machines have two options,
<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>.
The Pegasos does not require a bootloader, but you will need to emerge 
<uri link="#bootcreator">bootcreator</uri> to create SmartFirmware boot menus.
</p>

</body>
</subsection>
</section>
<section id="yaboot">
<title>Default: Using yaboot</title>
<subsection>
<title>Introduction</title>
<body>

<impo>
yaboot can only be used on NewWorld Apple and IBM systems!
</impo>

<p>
In order to find the boot devices, yaboot needs access to the device nodes
created by udev on startup and the sysfs filesystem.  These two filesystems
are found at <path>/dev</path> and <path>sys</path> respectively.  To do this,
you will need to "bind mount" these filesystems from the Installation CD's root
to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot.
If you have already bind mounted these filesystems, there is no need to do it
again.
</p>

<pre caption="Bind-mounting the device and sysfs filesystems">
# <i>exit </i> # this will exit the chroot
# <i>mount -o bind /dev /mnt/gentoo/dev</i>
# <i>mount -o bind /sys /mnt/gentoo/sys</i>
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
</pre>

<p>
To set up yaboot, you can use <c>yabootconfig</c> to automatically create a
configuration file for you. If you are installing Gentoo on a G5 (where 
<c>yabootconfig</c> does not always work), or you plan to boot from firewire 
or USB, you will need to manually configure yaboot.
</p>

<note>
You will need to manually edit the yaboot.conf when using genkernel, even if
yabootconfig is used.  The kernel image section of yaboot.conf should be
modified as follows (using vmlinux and initrd as the name of kernel and 
initrd image):
</note>

<pre caption="Adding genkernel boot arguments to yaboot.conf">
<comment>###########################################################
## This section can be duplicated if you have more than one
## kernel or set of boot options - replace the image and initrd
## with the exact filename of your kernel and initrd image.
###########################################################</comment>
image=/boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/>
  label=Linux
  root=/dev/ram0
  partition=3
  initrd=/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/>
  <comment># You can add additional kernel arguments to append such as 
  # rootdelay=10 for a USB/Firewire Boot</comment>
  append="real_root=/dev/hda3 init=/linuxrc"  
  read-only
<comment>##########################################################</comment>
</pre>

<ul>
  <li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
  <li>
    <uri link="#manual_yaboot">Alternative: Manual yaboot Configuration</uri>
  </li>
</ul>

</body>
</subsection>
<subsection id="yabootconfig">
<title>Default: Using yabootconfig</title>
<body>

<p>
<c>yabootconfig</c> will auto-detect the partitions on your machine and will
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X.
</p>

<p>
To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
and <path>/etc/fstab</path> must be configured to reflect your Linux 
partitions (note that the Bootstrap partition should <e>not</e> be in your
fstab). These steps should have already been completed before, but check
<path>/etc/fstab</path> before proceeding.  Now, install <c>yaboot</c>.
</p>

<pre caption = "Installing yaboot from GRP">
# <i>emerge --usepkg yaboot</i>
</pre>

<p>
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First,
the program will confirm the location of the bootstrap partition.  If you are
using the suggested disk partitioning scheme, your bootstrap partition should
be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your
<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup, 
create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. 
<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install 
the yaboot configuration file into it.  After this enter the chroot again.
</p>

<pre caption="Re-enter the chroot">
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i>
</pre>

<p>
You should verify the contents of <path>/etc/yaboot.conf</path>. If you make
changes to <path>/etc/yaboot.conf</path> (like setting the default/boot OS),
make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap
partition.  Whenever you make a change to yaboot.conf, like when testing a new
kernel, always remember to run <c>ybin -v</c> to update the bootstrap
partition.
</p>

<p>
Now continue with <uri link="#reboot">Rebooting the System</uri>.
</p>

</body>
</subsection>
<subsection id="manual_yaboot">
<title>Alternative: Manual yaboot Configuration</title>
<body>

<p>
First, install <c>yaboot</c> on your system:
</p>

<pre caption="Installing yaboot from GRP">
# <i>emerge --usepkg yaboot</i>
</pre>

<p>
An example <path>yaboot.conf</path> file is given below, but you will need to 
alter it to fit your needs.  G5 users and users booting from firewire and USB
should be aware that their disks are seen as SCSI disks by the Linux kernel, so 
you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>).
</p>

<pre caption = "/etc/yaboot.conf">
<comment>## /etc/yaboot.conf
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

## The bootstrap partition:</comment>

boot=/dev/hda2

<comment>## ofboot is the Open Firmware way to specify the bootstrap partition.
## If this isn't defined, yaboot fails on the G5 and some G4s (unless 
## you pass the necessary arguments to the mkofboot/ybin program).
## hd:X means /dev/sdaX (or /dev/hdaX).
## 
## G5 users should uncomment this line!!

#ofboot=hd:2

## Users booting from firewire should use something like this line:
# ofboot=fw/node/sbp-2/disk@0:

## Users booting from USB should use something like this line:
# ofboot=usb/disk@0:

## hd: is shorthand for the first hard drive Open Firmware sees</comment>
device=hd:

<comment>## Firewire and USB users will need to specify the whole OF device name
## This can be found using ofpath, which is included with yaboot.

# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0:
</comment>

delay=5
defaultos=macosx
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

<comment>###########################################################
## This section can be duplicated if you have more than one
## kernel or set of boot options - replace the image variable
## with the exact filename of your kernel.
###########################################################</comment>
image=/boot/<keyval id="kernel-name"/>
  label=Linux
  root=/dev/hda3
  partition=3
<comment>#  append="rootdelay=10"  # Required for booting USB/Firewire</comment>
  read-only
<comment>##################

## G5 users and some G4 users should set 
##   macos=hd:13
##   macosx=hd:12
## instead of the example values.</comment>
macos=/dev/hda13
macosx=/dev/hda12
enablecdboot
enableofboot
</pre>

<p>
Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format
the Apple_bootstrap partition and install the settings. If you change 
yaboot.conf after the Apple_bootstrap partition has been created, you can
update the settings by running <c>ybin -v</c>
</p>

<pre caption="Setting up the bootstrap partition">
# <i>mkofboot -v</i>
</pre>

<p>
For more information on yaboot, take a look at the <uri
link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For
now, continue the installation with <uri link="#reboot">Rebooting the
System</uri>.
</p>

</body>
</subsection>
</section>
<section id="bootx">
<title>Alternative: BootX</title>
<body>

<impo>
BootX can only be used on OldWorld Apple systems with MacOS 9 or earlier!
</impo>

<p>
Since BootX boots Linux from within MacOS, the kernel will need to be copied
from the Linux Partition to the MacOS partition.  First, mount the MacOS 
partition from outside of the chroot.  Use <c>mac-fdisk -l</c> to find the 
MacOS partition number, sda6 is used as an example here.  Once the partition is
mounted, we'll copy the kernel to the system folder so BootX can find it.
</p>

<pre caption="Copying the kernel to the MacOS partition">
# <i>exit</i>
cdimage ~# <i>mkdir /mnt/mac</i>
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels/<keyval id="kernel-name"/>"</i>
</pre>

<p>
If genkernel is used, both the kernel and initrd will need to be copied to the
MacOS partition.
</p>

<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition">
# <i>exit</i>
cdimage ~# <i>mkdir /mnt/mac</i>
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
cdimage ~# <i>cp /mnt/gentoo/boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> "/mnt/mac/System Folder/Linux Kernels"</i>
cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/> "/mnt/mac/System Folder"</i>
</pre>

<p>
Now that the kernel is copied over, we'll need to reboot to set up BootX.
</p>

<pre caption="Unmounting all partitions and rebooting">
cdimage ~# <i>cd /</i>
cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo /mnt/mac</i>
cdimage ~# <i>reboot</i>
</pre>

<p>
Of course, don't forget to remove the bootable CD, otherwise the CD will be
booted again instead of MacOS.
</p>

<p>
Once the machine has booted into MacOS, open the BootX control panel.  If you're
not using genkernel, select <c>Options</c> and uncheck <c>Use specified RAM
disk</c>.  If you are using genkernel, ensure that the genkernel initrd is 
selected instead of the Installation CD initrd.  If not using genkernel, 
there is now an option to specify the machine's Linux root disk and partition. 
Fill these in with the appropriate values.  Depending upon the kernel 
configuration, additional boot arguments may need to be applied.
</p>

<p>
BootX can be configured to start Linux upon boot. If you do this, you will first
see your machine boot into MacOS then, during startup, BootX will load and start
Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">BootX home
page</uri> for more information.
</p>

<impo>
Make sure that you have support for HFS and HFS+ filesystems in your kernel,
otherwise you will not be able to upgrade or change the kernel on your MacOS 
partition.
</impo>

<p>
Now reboot again and boot into Linux, then continue with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
</p>

</body>
</section>
<section id="quik">
<title>Alternative: quik</title>
<body>

<p>
quik allows OldWorld Macs to boot without MacOS.  However, it isn't well
supported and has a number of quirks.  If you have the option, it is recommended
that you use BootX instead since it is much more reliable and easier to set up
than quik.
</p>

<p>
First, we'll need to install quik:
</p>

<pre caption="Emerge quik from GRP">
# <i>emerge --usepkg quik</i>
</pre>

<p>
Next, we'll need to set it up. Edit <path>/etc/quik.conf</path> and set your
image to the kernel that we copied to your boot partition.
</p>

<pre caption="Configuring quik.conf">
# Example of quik.conf
init-message = "Gentoo 2007.1\n"
<comment># This is the boot partition</comment>
partition = 2
root = /dev/hda4
timeout = 30
default = gentoo
<comment># This is your kernel</comment>
image = /<keyval id="kernel-name"/>
  label = gentoo
</pre>

<p>
Your quik.conf file <e>must</e> be on the same disk as the quik boot images,
however it can be on a different partition on the same disk, although it is
recommended to move it to your boot partition.
</p>

<pre caption="Moving quik.conf to /boot">
# <i>mv /etc/quik.conf /boot/quik.conf</i>
</pre>

<p>
We will now set your boot variables so that quik loads on boot.  To do this,
we'll use a program called <c>nvsetenv</c>.  The variables that you want to
set vary from machine to machine, it's best to find your machine's 
<uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri>
before attempting this.
</p>

<pre caption="Setting the boot variables">
# <i>nvsetenv auto-boot true</i> <comment># Set to false if you want to boot into OF, not all models can display the OF output</comment>
# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment>
# <i>nvsetenv input-device kbd</i>
# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment>
# <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment>
# <i>nvsetenv boot-file /boot/<keyval id="kernel-name"/> root=/dev/hda4</i> <comment>First item is the path to the kernel, the second is the root partition.  You may append any kernel options to the end of this line.</comment>
# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment>
</pre>

<note>
It is also possible to change your boot variables from MacOS.  Depending upon
the model, either <uri
link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or
<uri
link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin">
Apple System Disk</uri> should be used.  Please see the quik quirks page above
for more information.
</note>

<p>
Now that we've set up our machine to boot, we'll need to make sure the boot
images are installed correctly.  Run <c>quik -v -C /boot/quik.conf</c>.  It 
should tell you that it has installed the first stage QUIK boot block.
</p>

<note>
If something has gone wrong, you can always reset your PRAM back to the default
values by holding down <c>command + option + p + r</c> before powering on your
machine.  This will clear the values you set with nvsetenv and should allow you
to boot either a MacOS bootdisk or a Linux bootdisk.
</note>

<p>
Now, continue the installation with 
<uri link="#reboot">Rebooting the System</uri>.
</p>

</body>
</section>
<section id="bootcreator">
<title>Alternative: BootCreator</title>
<body>

<impo>
BootCreator will build a nice SmartFirmware bootmenu written in Forth for the
Pegasos.
</impo>

<p>
First make sure you have <c>bootcreator</c> installed on your system:
</p>

<pre caption = "Installing bootcreator from GRP">
# <i>emerge --usepkg bootcreator</i>
</pre>

<p>
Now copy the file <path>/etc/bootmenu.example</path> into
<path>/etc/bootmenu</path> and edit it to suit your needs:
</p>

<pre caption = "Edit the bootcreator config file">
# <i>cp /etc/bootmenu.example /etc/bootmenu</i>
# <i>nano -w /etc/bootmenu</i>
</pre>

<p>
Below is a complete <path>/etc/bootmenu</path> config file.  vmlinux and
initrd should be replaced by your kernel and initrd image names.
</p>

<pre caption = "bootcreator config file">
<comment>#
# Example description file for bootcreator 1.1
#</comment>

[VERSION]
1

[TITLE]
Boot Menu

[SETTINGS]
AbortOnKey = false
Timeout    = 9
Default    = 1

[SECTION]
Local HD -> Morphos      (Normal)
ide:0 boot2.img ramdebug edebugflags="logkprintf"

[SECTION]
Local HD -> Linux (Normal)
ide:0 <keyval id="kernel-name"/> video=radeonfb:1024x768@70 root=/dev/hda3

[SECTION]
Local HD -> Genkernel (Normal)
ide:0 kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc initrd=initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/>
</pre>

<p>
Finally the <path>bootmenu</path> must be transferred into Forth and copied to
your boot partition, so that the SmartFirmware can read it.  Therefore you have
to call <c>bootcreator</c>:
</p>

<pre caption = "Install the bootmenu">
# <i>bootcreator /etc/bootmenu /boot/menu</i>
</pre>

<note>
Be sure to have a look into the SmartFirmware's settings when you reboot, that
<path>menu</path> is the file that will be loaded by default.
</note>

<p>
For now, continue the installation with <uri link="#reboot">Rebooting the
System</uri>.
</p>

</body>
</section>
<section id="reboot">
<title>Rebooting the System</title>
<subsection>
<body>

<p>
Exit the chrooted environment and unmount all mounted partitions. Then type in
that one magical command you have been waiting for: <c>reboot</c>.
</p>

<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
# <i>exit</i>
livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo</i>
livecd ~# <i>reboot</i>
</pre>

<p>
Once rebooted in your Gentoo installation, finish up with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc-disk.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-26</date>

<section>
<title>Introduction to Block Devices</title>
<subsection>
<title>Block Devices</title>
<body>

<p>
We'll start by taking a good look at disk-oriented aspects of Gentoo Linux
and Linux in general, including Linux filesystems, partitions and block devices.
Then, once you're familiar with the ins and outs of disks and filesystems,
you'll be guided through the process of setting up partitions and filesystems
for your Gentoo Linux installation.
</p>

<p>
To begin, we'll introduce <e>block devices</e>. The most common block device is
the one that represents the first IDE drive in a Linux system, namely
<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA 
drives, then your first hard drive would be <path>/dev/sda</path>.  Additional
drives are enumerated by the next letter in the alphabet.  As an example, the
third IDE disk could be found at <path>/dev/hdc</path>.
</p>

<p>
The block devices above represent an abstract interface to the disk. User
programs can use these block devices to interact with the disk without worrying
about whether the drives are IDE, SCSI or something else. The program can
simply address the storage on the disk as a bunch of contiguous,
randomly-accessible 512-byte blocks.
</p>

</body>
</subsection>
<subsection>
<title>Partitions</title>
<body>

<p>
Although it is theoretically possible to use a full disk to house your Linux
system, this is almost never done in practice. Instead, full disk block devices
are split up in smaller, more manageable block devices. On most systems,
these are called <e>partitions</e>.
</p>

</body>
</subsection>
</section>
<section>
<title>Designing a Partitioning Scheme</title>
<subsection>
<title>Default Partitioning Scheme</title>
<body>

<p>
If you are not interested in drawing up a partitioning scheme for your system,
you can use the partitioning scheme we use throughout this book.  Choose the
filesystem layout that best matches the type of PowerPC system you are 
installing on.
</p>

</body>
</subsection>
<subsection>
<title>Apple New World</title>
<body>

<p>
Apple New World machines are fairly straightforward to configure.  The first
partition is always an <e>Apple Partition Map</e>.  This partition keeps track
of the layout of the disk.  You cannot remove this partition.  The next
partition should always be a bootstrap partition.  This partition contains a
small (800k) HFS filesystem that holds a copy of the bootloader Yaboot and its
configuration file.  This partition is <e>not</e> the same as a 
<path>/boot</path> partition as found on other architectures.  After the boot
partition, the usual Linux filesystems are placed, according to the scheme
below.  The swap partition is a temporary storage place for when your system
runs out of physical memory.  The root partition will contain the filesystem
that Gentoo is installed on.  If you wish to dual boot, the OSX partition 
can go anywhere after the bootstrap partition to insure that yaboot starts 
first.
</p>

<note>
There may be "Disk Driver" partitions on your disk such as
<path>Apple_Driver63</path>, <path>Apple_Driver_ATA</path>,
<path>Apple_FWDriver</path>, <path>Apple_Driver_IOKit</path>, and
<path>Apple_Patches</path>.  These are used to boot MacOS, so if you have no
need for this, you can remove them by initializing the disk with mac-fdisk's
<c>i</c> option.  This will completely erase the disk!  If you are in doubt,
just let them be.
</note>

<note>
If you partitioned this disk with Apple's Disk Utility, there may be
128Mb spaces between partitions which Apple reserves for "future use".  You
can safely remove these.
</note>

<table>
<tr>
  <th>Partition</th>
  <th>Size</th>
  <th>Filesystem</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/hda1</path></ti>
  <ti>32k</ti>
  <ti>None</ti>
  <ti>Apple Partition Map</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>800k</ti>
  <ti>HFS</ti>
  <ti>Apple Bootstrap</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti>512Mb</ti>
  <ti>Swap</ti>
  <ti>Linux Swap</ti>
</tr>
<tr>
  <ti><path>/dev/hda4</path></ti>
  <ti>Rest of Disk</ti>
  <ti>ext3, reiserfs, xfs</ti>
  <ti>Linux Root</ti>
</tr>
</table>

</body>
</subsection>
<subsection>
<title>Apple Old World</title>
<body>

<p>
Apple Old World machines are a bit more complicated to configure. The first
partition is always an <e>Apple Partition Map</e>.  This partition keeps track
of the layout of the disk.  You cannot remove this partition.  If you are using
BootX, the configuration below assumes that MacOS is installed on a seperate
disk.  If this is not the case, there will be additional partitions for "Apple
Disk Drivers" such as <path>Apple_Driver63, Apple_Driver_ATA, Apple_FWDriver,
Apple_Driver_IOKit, Apple_Patches</path> and the MacOS install.  If you are 
using Quik, you will need to create a boot partition to hold the kernel, unlike
other Apple boot methods. After the boot partition, the usual Linux filesystems
are placed, according to the scheme below.  The swap partition is a temporary
storage place for when your system runs out of physical memory.  The root 
partition will contain the filesystem that Gentoo is installed on.
</p>

<note>
If you are using an OldWorld machine, you will need to keep MacOS available.
The layout here assumes MacOS is installed on a separate drive.
</note>

<table>
<tr>
  <th>Partition</th>
  <th>Size</th>
  <th>Filesystem</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/hda1</path></ti>
  <ti>32k</ti>
  <ti>None</ti>
  <ti>Apple Partition Map</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>32Mb</ti>
  <ti>ext2</ti>
  <ti>Quik Boot Partition (quik only)</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti>512Mb</ti>
  <ti>Swap</ti>
  <ti>Linux Swap</ti>
</tr>
<tr>
  <ti><path>/dev/hda4</path></ti>
  <ti>Rest of Disk</ti>
  <ti>ext3, reiserfs, xfs</ti>
  <ti>Linux Root</ti>
</tr>
</table>

</body>
</subsection>
<subsection>
<title>Pegasos</title>
<body>

<p>
The Pegasos partition layout is quite simple compared to the Apple layouts.
The first partition is a Boot Partition, which contains kernels to be booted,
along with an Open Firmware script that presents a menu on boot.  After the boot
partition, the usual Linux filesystems are placed, according to the scheme
below.  The swap partition is a temporary storage place for when your system
runs out of physical memory.  The root partition will contain the filesystem
that Gentoo is installed on.  
</p>

<table>
<tr>
  <th>Partition</th>
  <th>Size</th>
  <th>Filesystem</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/hda1</path></ti>
  <ti>32Mb</ti>
  <ti>affs1 or ext2</ti>
  <ti>Boot Partition</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>512Mb</ti>
  <ti>Swap</ti>
  <ti>Linux Swap</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti>Rest of Disk</ti>
  <ti>ext3, reiserfs, xfs</ti>
  <ti>Linux Root</ti>
</tr>
</table>

</body>
</subsection>
<subsection>
<title>IBM PReP (RS/6000)</title>
<body>

<p>
The IBM PowerPC Reference Platform (PReP) requires a small PReP boot partition
on the disk's first partition, followed by the swap and root partitions.
</p>

<table>
<tr>
  <th>Partition</th>
  <th>Size</th>
  <th>Filesystem</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/hda1</path></ti>
  <ti>800k</ti>
  <ti>None</ti>
  <ti>PReP Boot Partition (Type 0x41)</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>512Mb</ti>
  <ti>Swap</ti>
  <ti>Linux Swap (Type 0x82)</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti>Rest of Disk</ti>
  <ti>ext3, reiserfs, xfs</ti>
  <ti>Linux Root (Type 0x83)</ti>
</tr>
</table>

<warn>
<c>parted</c> is able to resize partitions including HFS+. Unfortunately there
may be issues with resizing HFS+ journaled filesystems, so, for the best 
results, switch off journaling in Mac OS X before resizing. Remember that any
resizing operation is dangerous, so attempt at your own risk! Be sure to always
have a backup of your data before resizing!
</warn>

<p>
If you are interested in knowing how big a partition should be, or even how many
partitions you need, read on. Otherwise continue now with 
<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk
</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to 
Partition your Disk</uri>.
</p>

</body>
</subsection>
<subsection>
<title>How Many and How Big?</title>
<body>

<p>
The number of partitions is highly dependent on your environment. For instance,
if you have lots of users, you will most likely want to have your
<path>/home</path> separate as it increases security and makes backups easier.
If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
should be separate as all received mail is stored in <path>/var</path>. A good
choice of filesystem will then maximise your performance. Game servers should
have a separate <path>/opt</path> as most game servers are installed there. The
reason is similar for <path>/home</path>: security and backups. Whatever layout
you chose, you will definitely want to keep <path>/usr</path> large: not only 
will it contain the majority of applications, the Portage tree alone takes 
more than 500Mb excluding the various sources that are stored in it.
</p>

<p>
As you can see, it very much depends on what you want to achieve. Separate
partitions or volumes have the following advantages:
</p>

<ul>
<li>
  You can choose the best performing filesystem for each partition or volume
</li>
<li>
  Your entire system cannot run out of free space if one defunct tool is
  continuously writing files to a partition or volume
</li>
<li>
  If necessary, file system checks are reduced in time, as multiple checks can
  be done in parallel (although this advantage is more with multiple disks than
  it is with multiple partitions)
</li>
<li>
  Security can be enhanced by mounting some partitions or volumes read-only,
  nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
</li>
</ul>

<p>
However, multiple partitions have one big disadvantage: if not configured
properly, you might result in having a system with lots of free space on one
partition and none on another. There is also a 15-partition limit for SCSI and
SATA.
</p>

</body>
</subsection>
</section>
<section id="mac-fdisk">
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title>
<body>

<p>
At this point, create your partitions using <c>mac-fdisk</c>:
</p>

<pre caption="Starting mac-fdisk">
# <i>mac-fdisk /dev/hda</i>
</pre>

<p>
If you used Apple's Disk Utility to leave space for Linux, first delete the
partitions you have created previously to make room for your new install.  Use
<c>d</c> in <c>mac-fdisk</c> to delete those partition(s).  It will ask for the
partition number to delete.  Usually the first partition on NewWorld machines
(Apple_partition_map) could not be deleted. If you would like to start with a 
clean disk, you can simply initialize the disk by pressing  <c>i</c>.  This 
will completely erase the disk, so use this with caution.
</p>

<p>
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will
ask for what block you want to start. Enter the number of your first free
partition, followed by a <c>p</c>. For instance this is <c>2p</c>.
</p>

<note>
This partition is <e>not</e> a <path>/boot</path> partition. It is not used by
Linux at all; you don't have to place any filesystem on it and you should never
mount it. Apple users don't need an extra partition for <path>/boot</path>.
</note>

<p>
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will
ask for what block you want to start this partition from. As we used <c>2</c>
before to create the Apple_Bootstrap partition, you now have to enter
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size
you want -- a minimum of 512MB is recommended, but 2 times your physical memory
is the generally accepted size). When asked for a name, enter <c>swap</c>.
</p>

<p>
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select
from what block the root partition should start. When asked for the size, enter
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available
space". When asked for the name, enter <c>root</c>.
</p>

<p>
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to
quit <c>mac-fdisk</c>.
</p>

<note>
To make sure everything is ok, you should run <c>mac-fdisk -l</c> and check
whether all the partitions are there. If you don't see any of the partitions
you created, or the changes you made, you should reinitialize your partitions
by pressing "i" in mac-fdisk. Note that this will recreate the partition map
and thus remove all your partitions.
</note>

<p>
Now that your partitions are created, you can continue with 
<uri link="#filesystems">Creating Filesystems</uri>.
</p>

</body>
</section>
<section id="parted">
<title>Using parted to Partition your Disk (Pegasos and RS/6000)</title>
<body>

<p>
<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by
Mac OS and Mac OS X.  With this tool you can resize your Mac-partitions and
create space for your Linux partitions.  Nevertheless, the example below
describes partitioning for Pegasos machines only.
</p>

<p>
To begin let's fire up <c>parted</c>:
</p>

<pre caption="Starting parted">
# <i>parted /dev/hda</i>
</pre>

<p>
If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new 
disklabel for the drive.
</p>

<p>
You can type <c>print</c> at any time in parted to display the current partition
table. If at any time you change your mind or made a mistake you can press
<c>Ctrl-c</c> to abort parted.
</p>

<p>
If you intend to also install MorphOS on your Pegasos create an affs1 filesystem
at the start of the drive. 32MB should be more than enough to store the MorphOS
kernel. If you have a Pegasos I or intend to use any filesystem besides ext2 or 
ext3, you will also have to store your Linux kernel on this partition (the 
Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the 
partition run <c>mkpart primary affs1 START END</c> where <c>START</c> and 
<c>END</c> should be replaced with the megabyte range (e.g. <c>0 32</c>) which 
creates a 32 MB partition starting at 0MB and ending at 32MB.  If you chose to
create an ext2 or ext3 partition instead, substitute ext2 or ext3 for affs1 in
the mkpart command.
</p>

<p>
You will need to create two partitions for Linux, one root filesystem and one 
swap partition. Run <c>mkpart primary START END</c> to create each partition,
replacing <c>START</c> and <c>END</c> with the desired megabyte boundries.
</p>

<p>
It is generally recommended that you create a swap partition that is two times
bigger than the amount of RAM in your computer, but at least 512Mb is 
recommended. To create the swap partition, run 
<c>mkpart primary linux-swap START END</c> with START and END again denoting
the partition boundries.
</p>

<p>
When you are done in parted simply type <c>quit</c>.
</p>

</body>
</section>
<section id="filesystems">
<title>Creating Filesystems</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your partitions are created, it is time to place a filesystem on them.
If you're not sure which filesystems to choose and are happy with our defaults,
continue with 
<uri link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
Otherwise, read on to learn about the available filesystems.
</p>

</body>
</subsection>
<subsection>
<title>Filesystems?</title>
<body>

<p>
Several filesystems are available for use on the PowerPC architecture including
ext2, ext3, ReiserFS and XFS, each with their strengths and faults.
</p>

<p>
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
journaling, which means that routine ext2 filesystem checks at startup time can
be quite time-consuming. There is now quite a selection of journaled 
filesystems that can be checked for consistency very quickly and are thus 
generally preferred over their non-journaled counterparts.
</p>

<p>
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
journaling for fast recovery in addition to other enhanced journaling modes like
full data and ordered data journaling. It uses an HTree index that enables high
performance in almost all situations. In short, ext3 is a very good and reliable
filesystem.
</p>

<p>
<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
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. ReiserFS is solid and usable as
both general-purpose filesystem and for extreme cases such as the creation of
large filesystems, very large files and directories containing tens of
thousands of small files.
</p>

<p>
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
feature-set and is optimized for scalability. We only recommend using this
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
an uninterruptible power supply. Because XFS aggressively caches in-transit data
in RAM, improperly designed programs (those that don't take proper precautions
when writing files to disk and there are quite a few of them) can lose a good
deal of data if the system goes down unexpectedly.
</p>

</body>
</subsection>
<subsection>
<title>Activating the Swap Partition</title>
<body>

<p>
<c>mkswap</c> is the command that is used to initialize swap partitions:
</p>

<pre caption="Creating a swap signature">
# <i>mkswap /dev/hda3</i>
</pre>

<p>
To activate the swap partition, use <c>swapon</c>:
</p>

<pre caption="Activating the swap partition">
# <i>swapon /dev/hda3</i>
</pre>

<p>
Create and activate the swap now before creating other filesystems.
</p>

</body>
</subsection>
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>

<p>
To create a filesystem on a partition or volume, there are tools available for 
each possible filesystem:
</p>

<table>
<tr>
  <th>Filesystem</th>
  <th>Creation Command</th>
</tr>
<tr>
  <ti>ext2</ti>
  <ti><c>mke2fs</c></ti>
</tr>
<tr>
  <ti>ext3</ti>
  <ti><c>mke2fs -j</c></ti>
</tr>
<tr>
  <ti>reiserfs</ti>
  <ti><c>mkreiserfs</c></ti>
</tr>
<tr>
  <ti>xfs</ti>
  <ti><c>mkfs.xfs</c></ti>
</tr>
</table>

<p>
For instance, to make an ext3 filesystem on the root partition 
(<path>/dev/hda4</path> in our example), you would use:
</p>

<pre caption="Applying a filesystem on a partition">
# <i>mke2fs -j /dev/hda4</i>
</pre>

<p>
Now create the filesystems on your newly created partitions (or logical
volumes).
</p>

<impo>
If you choose to use ReiserFS for <path>/</path>, do not change its default
block size if you will also be using <c>yaboot</c> as your bootloader, as
explained in <uri link="?part=1&amp;chap=10">Configuring the Bootloader</uri>.
</impo>

<note>
On the PegasosII your partition which holds the kernel must be ext2, ext3 or
affs1.  NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or
even HFS/HFS+ filesystems.  On OldWorld machines booting with BootX, the kernel
must be placed on an HFS partition, but this will be completed when you
configure your bootloader.
</note>

</body>
</subsection>
</section>
<section>
<title>Mounting</title>
<body>

<p>
Now that your partitions are initialized and are housing a filesystem, it is
time to mount those partitions. Use the <c>mount</c> command. As an example we
mount the root partition:
</p>

<pre caption="Mounting partitions">
# <i>mount /dev/hda4 /mnt/gentoo</i>
</pre>

<note>
If you want your <path>/tmp</path> to reside on a separate partition, be sure to
change its permissions after mounting and unpacking with
<c>chmod 1777 /mnt/gentoo/tmp</c>. This is also true for <path>/var/tmp</path>.
</note>

<p>
Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
Installation Files</uri>.
</p>

</body>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-kernel.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-kernel.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc-kernel.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-kernel.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-08-12</date>

<section>
<title>Timezone</title>
<body>

<p>
You first need to select your timezone so that your system knows where it is
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
it to <path>/etc/localtime</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact
GMT+8.
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
</pre>

</body>
</section>
<section>
<title>Installing the Kernel Sources</title>
<subsection>
<title>Choosing a Kernel</title>
<body>

<p>
The core around which all distributions are built is the Linux kernel. It is the
layer between the user programs and your system hardware. Gentoo provides its
users several possible kernels to choose from. A full listing with description 
is available at the 
<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. 
</p>

<p>
We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel.
</p>

<pre caption="Installing a kernel source">
# <i>emerge --usepkg gentoo-sources</i>
</pre>

<p>
If you take a look in <path>/usr/src</path> you should see a symlink named
<path>linux</path> pointing to your current kernel source. In this case, the
installed kernel source points to <c>gentoo-sources-<keyval
id="kernel-version"/></c>. Your version may be different, so keep this in mind.
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -&gt; linux-<keyval id="kernel-gentoo"/>
</pre>

<p>
Now it is time to configure and compile your kernel source. You can use 
<c>genkernel</c> for this, which will build a generic kernel as used by the 
Installation CD. We explain the "manual" configuration first though, as it is
a more efficient configuration.
</p>

<p>
If you want to manually configure your kernel, continue now with <uri
link="#manual">Default: Manual Configuration</uri>. If you want to use 
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using 
genkernel</uri> instead.
</p>

</body>
</subsection>
</section>
<section id="manual">
<title>Default: Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Manually configuring a kernel is often seen as the most difficult procedure a
Linux user ever has to perform. Nothing is less true -- after configuring a
few kernels you won't even remember that it was difficult ;)
</p>

<p>
However, one thing <e>is</e> true: you must know your system when you start
configuring a kernel manually. Most information can be gathered by emerging 
pciutils (<c>emerge --usepkg pciutils</c>) which contains the program 
<c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted
environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib:
cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively,
you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results
are the same. You can also run <c>lsmod</c> to see what kernel modules the 
Installation CD uses (it might provide you with a nice hint on what to enable).
Another place to look for clues as to what components to enable is to check the
kernel message logs from the successful boot that got you this far.  Type
<c>dmesg</c> to see these kernel messages.
</p>

<p>
Now, go to your kernel source directory, it's time to configure your kernel.
Start by configuring a kernel that will boot on most 32 Bit PowerPC machines
by first running <c>make pmac32_defconfig</c>. After the default configuration
has been generated, run <c>make menuconfig</c> to start an ncurses-based
configuration menu.
</p>

<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
# <i>make pmac32_defconfig</i>
# <i>make menuconfig</i>
</pre>

<p>
You will be greeted with several configuration sections. We'll first list some
options you must activate (otherwise Gentoo will not function, or not function
properly without additional tweaks).
</p>

</body>
</subsection>
<subsection>
<title>Activating Required Options</title>
<body>

<p>
First of all, activate the use of development and experimental code/drivers.
You need this, otherwise some very important code/drivers won't show up:
</p>

<pre caption="Selecting experimental code/drivers">
General setup ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
</pre>

<p>
Now go to <c>File Systems</c> and select support for the filesystems you use.
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
able to mount your partitions. Also select the <c>/proc file system</c> and
<c>Virtual memory</c>.  Make sure that you also enable support for Amiga
partitions if you are using a Pegasos, or Macintosh partitions if you are using
an Apple computer.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
<comment>(/proc may already be forced on by your configuration, if so, you'll see --- instead)</comment>
    [*] /proc file system support
    [*] Virtual memory file system support (former shm fs)
  Partition Types ---&gt;
    [*] Advanced partition support
    [*]   Amiga partition table support
    [*]   Macintosh partition map support

<comment>(Select one or more of the following options as needed by your system)</comment>
  &lt;*&gt; Reiserfs support
  &lt;*&gt; Ext3 journalling file system support
  &lt;*&gt; Second extended fs support
  &lt;*&gt; XFS filesystem support
</pre>

<p>
Users of NewWorld and OldWorld machines will want HFS support as well.  OldWorld
users require it for copying compiled kernels to the MacOS partition. NewWorld
users require it for configuring the special Apple_Bootstrap partition:
</p>

<pre caption="Activating HFS support">
File Systems ---&gt;
  Miscellaneous filesystems ---&gt;
    &lt;M&gt; Apple Macintosh file system support
    &lt;M&gt; Apple Extended HFS file system support
</pre>

<p>
If you are using PPPoE to connect to the Internet or you are using a dial-up
modem, you will need the following options in the kernel:
</p>

<pre caption="Selecting PPPoE necessary drivers">
Device Drivers ---&gt;
  Network device support ---&gt;
    &lt;*&gt; PPP (point-to-point protocol) support
    &lt;*&gt;   PPP support for async serial ports
    &lt;*&gt;   PPP support for sync tty ports
</pre>

<p>
The two compression options won't harm but are not always needed.  The <c>PPP
over Ethernet</c> option might only be used by <c>ppp</c> when configured to
perform kernel mode PPPoE.
</p>

<p>
Don't forget to include support in the kernel for your ethernet card!  Most
newer Apple computers use the SunGEM ethernet driver.  Older iMacs commonly use
the BMAC driver.
</p>

<pre caption="Selecting the network driver">
Device Drivers ---&gt;
  Network device support ---&gt;
    Ethernet (10 or 100Mbit) ---&gt;
      [*] Ethernet (10 or 100Mbit)
      &lt;*&gt;   Generic Media Independent Interface device support
      &lt;*&gt;   MACE (Power Mac ethernet) support
      &lt;*&gt;   BMAC (G3 ethernet) support
      &lt;*&gt;   Sun GEM support
</pre>

<p>
At this time, full kernel preemption may still be unstable on PPC and may cause
compilation failures and random segfaults.  It is <e>strongly</e> suggested
that you do not use this feature.  Both <e>Voluntary Preemption</e> and 
<e>No Forced Preemption</e> should be safe.
</p>

<pre caption="Ensure the Preemptible Kernel Option is Off">
Kernel options ---&gt;
<comment>(Select One)</comment>
  Preemption Model 
    (X) No Forced Preemption (Server)
    (X) Voluntary Kernel Preemption (Desktop)
</pre>

<p>
If you're booting from Firewire, you'll need to enable these options. If you do
not want to compile in support, you'll need to include these modules and their
dependencies in an initrd.
</p>

<pre caption="Enable support for firewire devices on boot">
Device Drivers ---&gt;
  IEEE 1394 (FireWire) support ---&gt;
    &lt;*&gt; IEEE 1394 (FireWire) support
    &lt;*&gt;   OHCI-1394 support
    &lt;*&gt;   SBP-2 support (Harddisks etc.)
</pre>

<p>
If you're booting from USB, you'll need to enable these options.  If you do not
want to compile in support, you'll need to include these modules and their
dependencies in an initrd.
</p>

<pre caption="Enable support for USB devices on boot">
Device Drivers ---&gt;
  USB support ---&gt;
    &lt;*&gt; Support for Host-side USB
    &lt;*&gt;   OHCI HCD support
    &lt;*&gt;   USB Mass Storage support
</pre>

<p>
Do not turn off kernel framebuffer support as it is required for a successful
boot.  If you are using an NVIDIA based chipset, you should use the Open Firmware
framebuffer.  If you are using an ATI based chipset, you should select the
framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon).
</p>

<pre caption="Choosing a Framebuffer Driver">
Device Drivers ---&gt;
  Graphics support ---&gt;
    &lt;*&gt; Support for frame buffer devices
    [*] Open Firmware frame buffer device support
    &lt;*&gt; ATI Radeon display support
    &lt;*&gt; ATI Rage128 display support
    &lt;*&gt; ATI Mach64 display support
    Console display driver support ---&gt;
      &lt;*&gt; Framebuffer Console support
</pre>

<note>
If you select more than one framebuffer device, it may default to a less than
optimal driver.  Either use only one framebuffer device or specify which
to use by passing the driver to use to the kernel on boot by appending a video
line such as: <c>video=radeonfb</c>.
</note>

<p>
When you're done configuring your kernel, continue with <uri
link="#compiling">Compiling and Installing</uri>.
</p>

</body>
</subsection>
<subsection id="compiling">
<title>Compiling and Installing</title>
<body>

<p>
Now that your kernel is configured, it is time to compile and install it. Exit 
the configuration menu and run the following commands:
</p>

<pre caption="Compiling the kernel">
# <i>make &amp;&amp; make modules_install</i>
</pre>

<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path> as shown below. If you have a separate boot partition, as
on Pegasos computers, be sure that it is mounted properly. If you are using 
BootX to boot, we'll copy the kernel later.
</p>

<p>
Yaboot and BootX expect to use an uncompressed kernel unlike many other
bootloaders. The uncompressed kernel is called vmlinux and it is placed in
<path>/usr/src/linux</path> after the kernel has finished compiling. If you are
using a Pegasos machine, the Pegasos firmware requires a compressed kernel
called zImage which can be found in
<path>/usr/src/linux/arch/powerpc/boot/images</path>.
</p>

<pre caption="Installing the kernel">
# <i>cd /usr/src/linux</i>
<comment>Note, your kernel version might be different</comment>
<comment>(Apple/IBM)</comment>
# <i>cp vmlinux /boot/<keyval id="kernel-name"/></i>
<comment>(Pegasos)</comment>
# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name"/></i> 
</pre>

<p>
Now continue with <uri link="#kernel_modules">Installing Separate Kernel
Modules</uri>.
</p>

</body>
</subsection>
</section>
<section id="kernel_modules">
<title>Installing Separate Kernel Modules</title>
<subsection>
<title>Configuring the Modules</title>
<body>

<p>
You should list the modules you want automatically loaded in
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
the modules if required.
</p>

<p>
To view all available modules, run the following <c>find</c> command. Don't
forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
just compiled:
</p>

<pre caption="Viewing all available modules">
# <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
</pre>

<p>
For instance, to automatically load the <c>3c59x</c> module, edit the
<path>kernel-2.6</path> file and add the module to it, one module on a line.
</p>

<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
</pre>

<pre caption="/etc/modules.autoload.d/kernel-2.6">
3c59x
</pre>

<p>
Continue the installation with <uri link="?part=1&amp;chap=8">Configuring 
your System</uri>.
</p>

</body>
</subsection>
</section>
<section id="genkernel">
<title>Alternative: Using genkernel</title>
<body>

<p>
Now that your kernel source tree is installed, it's now time to compile your
kernel by using our <c>genkernel</c> script to automatically build a kernel for
you. <c>genkernel</c> works by configuring a kernel nearly identically to the
way our Installation CD kernel is configured. This means that when you use
<c>genkernel</c> to build your kernel, your system will generally detect all
your hardware at boot-time, just like our Installation CD does. Because
genkernel doesn't require any manual kernel configuration, it is an ideal
solution for those users who may not be comfortable compiling their own
kernels.
</p>

<p>
Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
</p>

<pre caption="Emerging genkernel">
# <i>emerge --usepkg genkernel</i>
</pre>

<p>
Next, copy over the kernel configuration used by the Installation CD to the 
location where genkernel looks for the default kernel configuration:
</p>

<pre caption="Copying over the Installation CD kernel config">
# <i>zcat /proc/config.gz > /usr/share/genkernel/ppc/kernel-config-2.6</i>
</pre>

<p>
If you are using firewire or USB to boot, you'll need to add modules to the 
initrd.  Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change
<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or
<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support.
</p>

<p>
Before compiling your sources, the fstab needs a slight adjustment. The rest of
the fstab will be completed during a later step, so don't worry about the
details now. If you did not create a separate boot partition (NOT bootstrap,
that's different), remove the line referencing <path>/boot</path> from
<path>/etc/fstab</path>. This will need to be done on most Apple computers.
</p>

<pre caption="Removing /boot from /etc/fstab on machines without a boot partition">
# <i>nano -w /etc/fstab</i>
<comment>Remove this line</comment>
/dev/BOOT		/boot		ext2		noauto,noatime	1 2
</pre>

<p>
Now, compile your kernel sources by running <c>genkernel --genzimage all</c>.
For Pegasos, we will need to use a different config and create a zImage instead
of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> 
compiles a kernel that supports almost all hardware, this compilation can take 
quite a while to finish!
</p>

<p>
Note that, if your partition where the kernel should be located doesn't use ext2
or ext3 as filesystem you might need to manually configure your kernel using
<c>genkernel --menuconfig all</c> and add support for your 
filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or
LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as
well.
</p>

<pre caption="Running genkernel">
# <i>genkernel all</i>
</pre>

<pre caption="Running genkernel on the Pegasos">
# <i>genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos all</i>
</pre>

<p>
Once <c>genkernel</c> completes, a kernel, full set of modules and 
<e>initial root disk</e> (initrd) will be created. We will use the kernel 
and initrd when configuring a boot loader later in this document. Write
down the names of the kernel and initrd as you will need them when writing
the bootloader configuration file. The initrd will be started immediately after 
booting to perform hardware autodetection (just like on the Installation CD) 
before your "real" system starts up.  Be sure to also copy down the required
boot arguments, these are required for a successful boot with genkernel.
</p>

<pre caption="Checking the created kernel image name and initrd">
<comment>Note, your kernel version might be different</comment>
# <i>ls /boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> /boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/></i>
</pre>

<p>
Now continue with <uri link="?part=1&amp;chap=8">Configuring your System</uri>.
</p>

</body>
</section>
</sections>




1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-medium.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-medium.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-medium.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-medium.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-29</date>

<section>
<title>Hardware Requirements</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Before we start, we first list what hardware requirements you need to
successfully install Gentoo on your box. 
</p>

</body>
</subsection>
<subsection>
<title>Hardware Requirements</title>
<body>

<table>
<tr>
  <th>Apple NewWorld Machines</th>
  <ti>
    Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook
    PowerBook, Xserver, PowerMac
  </ti>
</tr>
<tr>
  <th>Apple OldWorld machines</th>
  <ti>
    Apple Machines with an Open Firmware revision less than 3, such as the Beige
    G3s, PCI PowerMacs and PCI PowerBooks.  PCI based Apple Clones should also 
    be supported.
  </ti>
</tr>
<tr>
  <th>Genesi</th>
  <ti>
    Pegasos I/II, Open Desktop Workstation, Efika
  </ti>
</tr>
<tr>
  <th>IBM</th>
  <ti>
    RS/6000, iSeries, pSeries
  </ti>
</tr>
<tr>
  <th>Memory</th>
  <ti>At least 64 MB</ti>
</tr>
<tr>
  <th>Diskspace</th>
  <ti>1.5 GB (excluding swap space)</ti>
</tr>
<tr>
  <th>Swap space</th>
  <ti>At least 256 MB</ti>
</tr>
</table>

<p>
Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri>
for help with some common installation related issues or if you're unsure as to
just what's in that PowerPC machine you've got sitting on your desk right now.
</p>

</body>
</subsection>
</section>

<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using a <e>stage3</e> tarball file.
Such a tarball is an archive that contains a minimal environment from
which you can succesfully install Gentoo Linux onto your system.
</p>

<p>
Installations using a stage1 or stage2 tarball file are not documented in the
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo
FAQ</uri> on these matters.
</p>

</body>
</subsection>
<subsection>
<title>Gentoo Universal Installation CD</title>
<body>

<p>
An Installation CD is a bootable medium which contains a self-sustained Gentoo 
environment. It allows you to boot Linux from the CD. During the boot process 
your hardware is detected and the appropriate drivers are loaded. The Gentoo 
Installation CDs are maintained by Gentoo developers.
</p>

<p>
There currently are two Installation CDs available:
</p>

<ul>
  <li>
    The Universal Installation CD contains everything you need to install 
    Gentoo. It provides stage3 files for common architectures, source code 
    for the extra applications you need to choose from and, of course, the 
    installation instructions for your architecture.
  </li>
  <li>
    The Minimal Installation CD contains only a minimal environment that allows 
    you to boot up and configure your network so you can connect to the 
    Internet. It does not contain any additional files and cannot be used 
    during the current installation approach.
  </li>
</ul>

<p>
Gentoo also provides a Package CD. This is not an Installation CD but an
additional resource that you can exploit during the installation of your Gentoo
system. It contains prebuilt packages (also known as the GRP set) that allow
you to easily and quickly install additional applications (such as
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and
right before you update your Portage tree.
</p>

<p>
The use of the Package CD is covered later in this document. 
</p>

</body>
</subsection>
</section>
<!-- STOP -->
<section>
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title>
<subsection>
<title>Downloading and Burning the Installation CD</title>
<body>

<p>
You can download the Universal Installation CD (and, if you want to, the
Packages CD as well) from one of our <uri
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in
the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs
are located in the <path><keyval id="release-dir"/>packagecd</path> directory.
</p>

<p>
Inside those directories you'll find ISO files. Those are full CD images which
you can write on a CD-R.
</p>

<p>
After downloading the file, you can verify its integrity to see if it is 
corrupted or not:
</p>

<ul>
  <li>
    You can check its MD5 checksum and compare it with the MD5 checksum we 
    provide (for instance with the <c>md5sum</c> tool under Linux/Unix or 
    <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows).
    Verifying MD5 checksums with Mac OS X is described in the <uri
    link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>.
  </li>
  <li>
    You can verify the cryptographic signature that we provide. You need to
    obtain the public key we use (0x17072058) before you proceed though.
  </li>
</ul>

<p>
To fetch our public key using the GnuPG application, run the following command:
</p>

<pre caption="Obtaining the public key">
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i>
</pre>

<p>
Now verify the signature:
</p>

<pre caption="Verify the cryptographic signature">
$ <i>gpg --verify &lt;signature file&gt; &lt;downloaded iso&gt;</i>
</pre>

<p>
To burn the downloaded ISO(s), you have to select raw-burning. How you
do this is highly program-dependent. We will discuss <c>cdrecord</c> and
<c>K3B</c> here; more information can be found in our <uri
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>.
</p>

<ul>
  <li>
    With cdrecord, you simply type <c>cdrecord dev=/dev/hdc &lt;downloaded iso
    file&gt;</c> (replace <path>/dev/hdc</path> with your CD-RW drive's device
    path).
  </li>
  <li>
    With K3B, select <c>Tools</c> &gt; <c>Burn CD Image</c>. Then you can locate
    your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>.
  </li>
</ul>

</body>
</subsection>
<subsection>
<title>Default: Booting the Installation CD with Yaboot</title>
<body>

<p>
On NewWorld machines place the Installation CD in the CD-ROM and reboot the 
system. When the system-start-bell sounds, simply hold down the 'C' until the
CD loads.
</p>

<p>
After the Installation CD loaded, you will be greeted by a friendly welcome 
message and a <e>boot:</e> prompt at the bottom of the screen.
</p>

<p>
We provide one generic kernel, <e>apple</e>. This kernel is built with support
for multiple CPUs, but it will boot on single processor machines as well.
</p>

<p>
You can tweak some kernel options at this prompt. The following table lists 
some of the available boot options you can add:
</p>

<table>
<tr>
  <th>Boot Option</th>
  <th>Description</th>
</tr>
<tr>
  <ti><c>video</c></ti>
  <ti>
    This option takes one of the following vendor-specific tags:
    <c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, 
    <c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution 
    refresh rate and color depth you want to use. For instance,
    <c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer
    at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of
    32 bits. If you are uncertain what to choose, and the default doesn't work,
    <c>video=ofonly</c> will most certainly work.
  </ti>
</tr>
<tr>
  <ti><c>nol3</c></ti>
  <ti>
    Disables level 3 cache on some PowerBooks (needed for at least the 17&quot;)
  </ti>
</tr>
<tr>
  <ti><c>dofirewire</c></ti>
  <ti>
    Enables support for IEEE1394 (FireWire) devices, like external harddisks.
  </ti>
</tr>
<tr>
  <ti><c>dopcmcia</c></ti>
  <ti>
    If you want to use PCMCIA devices during your installation (like PCMCIA
    network cards) you have to enable this option.
  </ti>
</tr>
</table>

<p>
To use the above options, at the <e>boot:</e> prompt, type <e>apple</e> followed
by the desired option.  In the example below, we'll force the kernel to use the
Open Firmware framebuffer instead of the device specific driver.
</p>

<pre caption="Force the use of the Open Firmware framebuffer">
boot: <i>apple video=ofonly</i>
</pre>

<p>
If you don't need to add any options, just hit enter at this prompt, and a 
complete Gentoo Linux environment will be loaded from the CD. Continue with
<uri link="#booted">And When You're Booted...</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Alternative: Booting the Installation CD on a Pegasos</title>
<body>

<p>
On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type
<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose
between several preconfigured video configs. If you need any special boot
options you can append them to the command-line just like with Yaboot above. 
For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.
The default kernel options (in case something goes wrong and you need it) are 
preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc 
looptype=squashfs loop=/image.squashfs cdroot root=/dev/ram0</c>.
</p>

</body>
</subsection>

<subsection>
<title>Alternative: Booting the Installation CD with BootX</title>
<body>

<p>
If you have an OldWorld Mac the bootable portion of the livecd can't be used.
The most simple solution is to use MacOS 9 or earlier to bootstrap into a Linux
environment with a tool called BootX.  
</p>

<p>
First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri>
and unpack the archive.  Copy the the <c>BootX Extension</c> from the unpacked
archive into <c>Extensions Folder</c> and the BootX App Control Panel into
<c>Control Panels</c>, both of which are located in your MacOS System Folder.
Next, create a folder called "Linux Kernels" in your System folder and copy the
<c>apple</c> kernel from the CD to this folder.  Finally, copy <c>apple.igz</c> 
from the Installation CD <path>boot</path> folder into the MacOS 
<c>System Folder</c>.
</p>

<p>
To prepare BootX, start the BootX App Control Panel.  First select the Options
dialog and check <c>Use Specified RAM Disk</c> and select <c>apple.igz</c> from
your System Folder.  Continue back to the initial screen and ensure that the
ramdisk size is at least <c>32000</c>.  Finally, set the kernel arguments as
shown below:
</p>

<pre caption="BootX kernel arguments">
cdroot root=/dev/ram0 init=linuxrc loop=image.squashfs looptype=squashfs console=tty0 
</pre>

<note>
The kernel parameters in the yaboot section above are also applicable here. You
can append any of those options to the kernel arguments above.
</note>

<p>
Check once more to make sure the settings are correct and then save the 
configuration.  This saves typing just in case it doesn't boot or something is
missing.  Press the Linux button at the top of the window.  If everything goes
correctly, it should boot into the Installation CD. Continue with 
<uri link="#booted">And When You're Booted...</uri>
</p>

</body>
</subsection>

<subsection id="booted">
<title>And When You're Booted...</title>
<body>

<p>
You will be greeted by a root ("#") prompt on the current console. You can also 
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get 
back to the one you started on by pressing Alt-F1.  Due to the keyboard layout,
you may need to press Alt-fn-Fx on Apple machines.
</p>

<p>
If you are installing Gentoo on a system with a non-US keyboard, use
<c>loadkeys</c> to load the keymap for your keyboard. To list the available
keymaps, execute <c>ls /usr/share/keymaps/i386</c>.  On NewWorld machines or the
Pegasos do not use the keymaps in <path>ppc</path> or <path>mac</path> as they
are for ADB-based OldWorld machines.
</p>

<pre caption="Listing available keymaps">
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided
 on the Installation CD are ADB keymaps and unusable with the Installation CD 
 kernel)</comment>
# <i>ls /usr/share/keymaps/i386</i>
</pre>

<p>
Now load the keymap of your choice:
</p>

<pre caption="Loading a keymap">
# <i>loadkeys be-latin1</i>
</pre>

<p>
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>.
</p>

</body>
</subsection>
<subsection id="hardware">
<title>Extra Hardware Configuration</title>
<body>

<p>
When the Installation CD boots, it tries to detect all your hardware devices and
loads the appropriate kernel modules to support your hardware. In the
vast majority of cases, it does a very good job. However, in some cases, it may
not auto-load the kernel modules you need. If the PCI auto-detection missed some
of your system's hardware, you will have to load the appropriate kernel modules
manually. 
</p>

<p>
In the next example we try to load the <c>airport</c> module.  This module
supports only the old Airport cards (802.11b).  Airport Extreme (802.11g) is not
supported on the InstallCD due to restrictions on firmware distribution.
</p>

<pre caption="Loading the airport module">
# <i>modprobe airport</i>
</pre>

<p>
On older iMacs, sometimes the network card is not detected properly.  These use
the BMAC driver:
</p>

<pre caption="Loading the bmac module">
# <i>modprobe bmac</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Tweaking Hard Disk Performance</title>
<body>

<p>
If you are an advanced user, you might want to tweak the IDE hard disk
performance using <c>hdparm</c>. With the <c>-tT</c> options you can
test the performance of your disk (execute it several times to get a
more precise impression):
</p>

<pre caption="Testing disk performance">
# <i>hdparm -tT /dev/hda</i>
</pre>

<p>
To tweak, you can use any of the following examples (or experiment
yourself) which use <path>/dev/hda</path> as disk (substitute with your
disk):
</p>

<pre caption="Tweaking hard disk performance">
<comment>Activate DMA:</comment>
# <i>hdparm -d 1 /dev/hda</i>
<comment>Activate DMA + Safe Performance-enhancing Options:</comment>
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
</pre>

</body>
</subsection>
<subsection id="useraccounts">
<title>Optional: User Accounts</title>
<body>

<p>
If you plan on giving other people access to your installation
environment or you want to chat using <c>irssi</c> without root privileges (for
security reasons), you need to create the necessary user accounts and change 
the root password.
</p>

<p>
To change the root password, use the <c>passwd</c> utility:
</p>

<pre caption="Changing the root password">
# <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
</pre>

<p>
To create a user account, we first enter their credentials, followed by
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks.
In the next example, we create a user called &quot;john&quot;.
</p>

<pre caption="Creating a user account">
# <i>useradd -m -G users john</i>
# <i>passwd john</i>
New password: <comment>(Enter john's password)</comment>
Re-enter password: <comment>(Re-enter john's password)</comment>
</pre>

<p>
You can change your user id from root to the newly created user by using
<c>su</c>:
</p>

<pre caption="Changing user id">
# <i>su - john</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Viewing Documentation while Installing</title>
<body>

<p>
If you want to view the Gentoo Handbook (either from-CD or online) during the
installation, make sure you have created a user account (see <uri
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to
go to a new terminal and log in.
</p>

<p>
If you want to view the documentation on the CD you can immediately run
<c>links</c> or even <c>links -g</c> for a graphical framebuffer browser to
read it:
</p>

<pre caption="Viewing the on-CD documentation">
# <i>links /mnt/cdrom/docs/html/index.html</i>
</pre>

<p>
However, it is preferred that you use the online Gentoo Handbook as it will be
more recent than the one provided on the CD. You can view it using <c>links</c>
as well, but only after having completed the <e>Configuring your Network</e>
chapter (otherwise you won't be able to go on the Internet to view the
document):
</p>

<pre caption="Viewing the Online Documentation">
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
</pre>

<p>
You can go back to your original terminal by pressing <c>Alt-F1</c>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Starting the SSH Daemon</title>
<body>

<p>
If you want to allow other users to access your computer during the
Gentoo installation (perhaps because those users are going to help you
install Gentoo, or even do it for you), you need to create a user
account for them and perhaps even provide them with your root password 
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
</p>

<p>
To fire up the SSH daemon, execute the following command:
</p>

<pre caption="Starting the SSH daemon">
# <i>/etc/init.d/sshd start</i>
</pre>

<p>
To be able to use sshd, you first need to set up your networking. Continue with
the chapter on <uri link="?part=1&amp;chap=3">Configuring your Network</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-bootloader.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc64-bootloader.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-bootloader.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Making your Choice</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your kernel is configured and compiled and the necessary system
configuration files are filled in correctly, it is time to install a
program that will fire up your kernel when you start the system. Such a
program is called a <e>bootloader</e>.
</p>

<p>
On Linux/PPC64 we have only yaBoot as a bootloader until grub2 is
finished.
</p>

</body>
</subsection>
</section>
<section id="yaboot">
<title>Using yaBoot</title>
<subsection>
<title>Introduction</title>
<body>

<impo>
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't
compile on 64bit userland systems. For a 32bit userland use yaboot as you
normally would.
</impo>

<p>
There are two ways to configure yaBoot for your system. You can use the new and
improved <c>yabootconfig</c> included with <path>yaboot-1.3.8-r1</path> and
later to automatically set up yaboot. If for some reason you do not want to run
<c>yabootconfig</c> to automatically set up <path>/etc/yaboot.conf</path> or you
are installing Gentoo on a G5 (on which <c>yabootconfig</c> does not always
work), you can just edit the sample file already installed on your system.
</p>

<pre caption="Installing Necessary File System Tools">
# <i>emerge hfsutils hfsplusutils</i>
</pre>

<pre caption="Installing the bootloader">
<comment>(64bit userland)</comment>
# <i>emerge --update yaboot-static</i>
<comment>(32bit userland)</comment>
# <i>emerge --update yaboot</i>
</pre>

<impo>
yabootconfig/ybin won't work on IBM. You have to install yaboot another way:
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri>
</impo>

<note>
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a
kernel parameter. JFS must be able to replay its log in read-only mode before it
gets mounted read-write.
</note>

<ul>
  <li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
  <li>
    <uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri>
  </li>
</ul>

</body>
</subsection>
<subsection id="yabootconfig">
<title>Default: Using yabootconfig</title>
<body>

<p>
<c>yabootconfig</c> will auto-detect the partitions on your machine and will
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS
X.
</p>

<p>
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of
these should have been done already in the steps above. To start, ensure that
you have the latest version of yaboot installed by running <c>emerge --update
yaboot-static</c>. This is necessary as the latest version will be available via
Portage, but it may not have made it into the stage files.
</p>

<p>
Now run <c>yabootconfig</c>. The program will run and it will confirm the
location of the bootstrap partition. Type <c>Y</c> if it is correct. If not,
double check <path>/etc/fstab</path>. yabootconfig will then scan your system
setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you.
<c>mkofboot</c> is used to format the bootstrap partition, and install the
yaboot configuration file into it.
</p>

<p>
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If 
you make changes to <path>/etc/yaboot.conf</path> (like setting the 
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the 
bootstrap partition.
</p>

<p>
Now continue with <uri link="#reboot">Rebooting your System</uri>.
</p>

</body>
</subsection>
<subsection id="manual_yaboot">
<title>Alternative: Manual yaBoot Configuration</title>
<body>

<p>
Below you find a completed <path>yaboot.conf</path> file. Alter it at
will.
</p>

<pre caption="/etc/yaboot.conf">
<comment>## /etc/yaboot.conf
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

## our bootstrap partition:</comment>

boot=/dev/hda2

<comment>## ofboot is the Open Firmware way to specify the bootstrap partition.
## If this isn't defined, yaboot fails on the G5 and some G4s (unless 
## you pass the necessary arguments to the mkofboot/ybin program).
## hd:X means /dev/sdaX (or /dev/hdaX).</comment>

ofboot=hd:2

<comment>## hd: is open firmware speak for hda</comment>
device=hd:

delay=5
defaultos=macosx
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

<comment>#################
## This section can be duplicated if you have more than one kernel or set of
## boot options - replace <keyval id="kernel-name"/> with your kernel-version
#################</comment>
image=/boot/<keyval id="kernel-name"/>
  label=Linux
  root=/dev/hda3
  partition=3
  read-only

macos=hd:13
macosx=hd:12
enablecdboot
enableofboot
</pre>

<p>
Once <path>yaboot.conf</path> is set up the way you want it, you run <c>mkofboot
-v</c> to install the settings in the bootstrap partition.  <e>Don't forget
this!</e> Confirm when <c>mkofboot</c> asks you to create a new filesystem.
</p>

<p>
If all goes well, and you have the same options as the sample above, your next
reboot will give you a simple, five-entry boot menu. If you update your yaboot
config later on, you'll just need to run <c>ybin -v</c> to update the bootstrap
partition - <c>mkofboot</c> is for initial setup only.
</p>

<p>
For more information on yaboot, take a look at the <uri
link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For now,
continue the installation with <uri link="#reboot">Rebooting your System</uri>.
</p>

</body>
</subsection>
</section>
<section id="yaboot-ibm">
<title>Using yaboot on IBM hardware</title>
<body>

<p>
On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the
following steps:
</p>

<ul>
  <li>Install yaboot-static</li>
  <li>
    Run <c>dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX</c> (fill in XX with
    your disk and partition for the PReP partition; this was in our example
    <path>/dev/sda1</path>)
  </li>
  <li>
    Next construct your own <path>yaboot.conf</path> file and place into
    <path>/etc</path>. (Take a look at the config above, look into the man page
    of <path>yaboot.conf</path> or look at the below <path>yaboot.conf</path>
    example.)
  </li>
  <li>
    Assuming your boot device in OF is pointing to the harddrive you prep boot
    partition is on then it'll just work, otherwise at IPL time, go into the
    multiboot menu and set the boot device to the one with your prep boot
    partition
  </li>
  <li>That's it!</li>
</ul>

<pre caption="yaboot.conf for IBM hardware">
device=disk:
partition=2
root=/dev/sda2
default=linux
timeout=50

image=/boot/<keyval id="kernel-name"/>
      label=linux
      append="console=ttyS0,9600"
      read-only
</pre>

<p>
For POWER4, POWER5, and blade-based hardware where the PReP disk partition and
the disk partition that contains your kernel are on the same physical disk, you
can use a simplified <path>yaboot.conf</path>. The following should be
sufficient:
</p>

<pre caption="yaboot.conf for PReP hardware">
default = linux
timeout = 100
image=/boot/<keyval id="kernel-name"/>
      label=linux
      read-only
      root = /dev/sda2
      append="root=/dev/sda2"
</pre>

<p>
To verify that yaboot has been copied to the PReP partition:
</p>

<pre caption="Verifying the yaboot install on PReP">
# <i>dd if=/dev/sda1 count=10 | grep ELF</i>
Binary file (standard input) matches
10+0 records in
10+0 records out
</pre>

<p>
A match signifies that yaboot was installed correctly.
</p>

</body>
</section>
<section id="reboot">
<title>Rebooting the System</title>
<subsection>
<body>

<p>
Exit the chrooted environment and unmount all mounted partitions. Then type in 
that one magical command you have been waiting for: <c>reboot</c>.
</p>

<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
# <i>exit</i>
~# <i>cd</i>
~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
~# <i>reboot</i>
</pre>

<p>
Of course, don't forget to remove the bootable CD, otherwise the CD will be
booted again instead of your new Gentoo system.
</p>

<p>
Once rebooted in your Gentoo installation, finish up with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
</p>

</body>
</subsection>
</section>

</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc64-disk.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-26</date>

<section>
<title>Introduction to Block Devices</title>
<subsection>
<title>Block Devices</title>
<body>

<p>
We'll take a good look at disk-oriented aspects of Gentoo Linux
and Linux in general, including Linux filesystems, partitions and block devices.
Then, once you're familiar with the ins and outs of disks and filesystems,
you'll be guided through the process of setting up partitions and filesystems
for your Gentoo Linux installation.
</p>

<p>
To begin, we'll introduce <e>block devices</e>. The most famous block device is
probably the one that represents the first IDE drive in a Linux system, namely
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard
drive would be <path>/dev/sda</path>. Serial ATA drives are also
<path>/dev/sda</path> even if they are IDE drives.
</p>

<p>
The block devices above represent an abstract interface to the disk. User
programs can use these block devices to interact with your disk without worrying
about whether your drives are IDE, SCSI or something else. The program can
simply address the storage on the disk as a bunch of contiguous,
randomly-accessible 512-byte blocks.
</p>

</body>
</subsection>
<subsection>
<title>Partitions and Slices</title>
<body>

<p>
Although it is theoretically possible to use a full disk to house your Linux
system, this is almost never done in practice. Instead, full disk block devices
are split up in smaller, more manageable block devices. On most systems,
these are called <e>partitions</e>. Other architectures use a similar technique,
called <e>slices</e>.
</p>

</body>
</subsection>
</section>
<section>
<title>Designing a Partitioning Scheme</title>
<subsection>
<title>Default Partitioning Scheme</title>
<body>

<p>
If you are not interested in drawing up a partitioning scheme for your system,
you can use the partitioning scheme we use throughout this book:
</p>

<table>
<tr>
  <th>Partition</th>
  <th>Filesystem</th>
  <th>Size</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/sda1</path></ti>
  <ti>Partition map</ti>
  <ti>31.5k</ti>
  <ti>Partition map</ti>
</tr>
<tr>
  <ti><path>/dev/sda2</path></ti>
  <ti>(bootstrap)</ti>
  <ti>800k</ti>
  <ti>Apple_Bootstrap</ti>
</tr>
<tr>
  <ti><path>/dev/sda3</path></ti>
  <ti>(swap)</ti>
  <ti>512M</ti>
  <ti>Swap partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda4</path></ti>
  <ti>ext3</ti>
  <ti>Rest of the disk</ti>
  <ti>Root partition</ti>
</tr>
</table>

<note>
There are some partitions named like this: <path>Apple_Driver43</path>,
<path>Apple_Driver_ATA</path>, <path>Apple_FWDriver</path>,
<path>Apple_Driver_IOKit</path>, and <path>Apple_Patches</path>. If you are not
planning to use MacOS 9 you can delete them, because MacOS X and Linux don't
need them.  You might have to use parted in order to delete them, as mac-fdisk
can't delete them yet.
</note>

<p>
If you are interested in knowing how big a partition should be, or even how 
many partitions you need, read on. Otherwise continue now with
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition
your Disk</uri>
</p>

</body>
</subsection>
<subsection>
<title>How Many and How Big?</title>
<body>

<p>
The number of partitions is highly dependent on your environment. For instance,
if you have lots of users, you will most likely want to have your
<path>/home</path> separate as it increases security and makes backups easier.
If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
should be separate as all mails are stored inside <path>/var</path>. A good
choice of filesystem will then maximise your performance. Gameservers will have
a separate <path>/opt</path> as most gaming servers are installed there. The
reason is similar for <path>/home</path>: security and backups. You will
definitely want to keep <path>/usr</path> big: not only will it contain the
majority of applications, the Portage tree alone takes around 500 Mbyte
excluding the various sources that are stored in it.
</p>

<p>
As you can see, it very much depends on what you want to achieve. Separate
partitions or volumes have the following advantages:
</p>

<ul>
<li>
  You can choose the best performing filesystem for each partition or volume
</li>
<li>
  Your entire system cannot run out of free space if one defunct tool is
  continuously writing files to a partition or volume
</li>
<li>
  If necessary, file system checks are reduced in time, as multiple checks can
  be done in parallel (although this advantage is more with multiple disks than
  it is with multiple partitions)
</li>
<li>
  Security can be enhanced by mounting some partitions or volumes read-only,
  nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
</li>
</ul>

<p>
However, multiple partitions have one big disadvantage: if not configured
properly, you might result in having a system with lots of free space on one
partition and none on another. There is also a 15-partition limit for SCSI and
SATA.
</p>

</body>
</subsection>
</section>
<section id="mac-fdisk">
<title>Default: Using mac-fdisk (Apple G5) to Partition your Disk</title>
<body>

<p>
At this point, create your partitions using <c>mac-fdisk</c>:
</p>

<pre caption="Starting mac-fdisk">
# <i>mac-fdisk /dev/sda</i>
</pre>

<p>
First delete the partitions you have cleared previously to make room for your
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s).
It will ask for the partition number to delete.
</p>

<p>
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will
ask for what block you want to start. Enter the number of your first free
partition, followed by a <c>p</c>. For instance this is <c>2p</c>.
</p>

<note>
This partition is <e>not</e> a "boot" partition. It is not used by Linux at all;
you don't have to place any filesystem on it and you should never mount it. PPC
users don't need an extra partition for <path>/boot</path>.
</note>

<p>
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will
ask for what block you want to start this partition from. As we used <c>2</c>
before to create the Apple_Bootstrap partition, you now have to enter
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size
you want). When asked for a name, enter <c>swap</c> (mandatory).
</p>

<p>
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select
from what block the root partition should start. When asked for the size, enter
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available
space". When asked for the name, enter <c>root</c> (mandatory).
</p>

<p>
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to
quit <c>mac-fdisk</c>.
</p>
    
<note>
To make sure everything is ok, you should run mac-fdisk once more and check
whether all the partitions are there. If you don't see any of the partitions you
created, or the changes you made, you should reinitialize your partitions by
pressing <c>i</c> in mac-fdisk. Note that this will recreate the partition map
and thus remove all your partitions. 
</note>
    
<p>
Now that your partitions are created, you can now continue with <uri
link="#filesystems">Creating Filesystems</uri>.
</p>

</body>
</section>
<section id="fdisk">
<title>IBM pSeries, iSeries and OpenPower: using fdisk to Partition your Disk</title>
<subsection>
<body>

<note>
If you are planning to use a RAID disk array for your Gentoo installation and 
you are using POWER5-based hardware, you should now run <c>iprconfig</c> to 
format the disks to Advanced Function format and create the disk array. You
should emerge <c>iprutils</c> after your install is complete.
</note>

<p>
If you have an ipr-based SCSI adapter, you should start the ipr utilities now.
</p>

<pre caption="Starting ipr utilities">
# <i>/etc/init.d/iprinit start</i>
</pre>

<p>
The following parts explain how to create the example partition layout
described previously, namely:
</p>

<table>
<tr>
  <th>Partition</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/sda1</path></ti>
  <ti>PPC PReP Boot partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda2</path></ti>
  <ti>Swap partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda3</path></ti>
  <ti>Root partition</ti>
</tr>
</table>

<p>
Change your partition layout according to your own preference.
</p>

</body>
</subsection>
<subsection>
<title>Viewing the Current Partition Layout</title>
<body>

<p>
<c>fdisk</c> is a popular and powerful tool to split your disk into
partitions.  Fire up <c>fdisk</c> on your disk (in our example, we
use <path>/dev/sda</path>):
</p>

<pre caption="Starting fdisk">
# <i>fdisk /dev/sda</i>
</pre>

<p>
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like
this:
</p>

<pre caption="fdisk prompt">
Command (m for help):
</pre>

<p>
Type <c>p</c> to display your disk's current partition configuration:
</p>

<pre caption="An example partition configuration">
Command (m for help): p

Disk /dev/sda: 30.7 GB, 30750031872 bytes
141 heads, 63 sectors/track, 6761 cylinders
Units = cylinders of 8883 * 512 = 4548096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          12       53266+  83  Linux
/dev/sda2              13         233      981571+  82  Linux swap
/dev/sda3             234         674     1958701+  83  Linux
/dev/sda4             675        6761    27035410+   5  Extended
/dev/sda5             675        2874     9771268+  83  Linux
/dev/sda6            2875        2919      199836   83  Linux
/dev/sda7            2920        3008      395262   83  Linux
/dev/sda8            3009        6761    16668918   83  Linux

Command (m for help):
</pre>

<p>
This particular disk is configured to house six Linux filesystems
(each with a corresponding partition listed as "Linux") as well as a
swap partition (listed as "Linux swap").
</p>

</body>
</subsection>
<subsection>
<title>Removing all Partitions</title>
<body>

<p>
We will first remove all existing partitions from the disk. Type
<c>d</c> to delete a partition. For instance, to delete an existing
<path>/dev/sda1</path>:
</p>

<note>
If you don't want to delete all partitions just delete those you
want to delete. At this point the author recommends a backup of your
data to avoid the lose of it.
</note>

<pre caption="Deleting a partition">
Command (m for help): <i>d</i>
Partition number (1-4): <i>1</i>
</pre>

<p>
The partition has been scheduled for deletion. It will no longer show up
if you type <c>p</c>, but it will not be erased until your changes have
been saved. If you made a mistake and want to abort without saving your
changes, type <c>q</c> immediately and hit enter and your partition will
not be deleted.
</p>

<p>
Now, assuming that you do indeed want to wipe out all the partitions on
your system, repeatedly type <c>p</c> to print out a partition listing
and then type <c>d</c> and the number of the partition to delete it.
Eventually, you'll end up with a partition table with nothing in it:
</p>

<pre caption="An empty partition table">
Disk /dev/sda: 30.7 GB, 30750031872 bytes
141 heads, 63 sectors/track, 6761 cylinders
Units = cylinders of 8883 * 512 = 4548096 bytes

Device Boot    Start       End    Blocks   Id  System

Command (m for help):
</pre>

<p>
Now that the in-memory partition table is empty, we're ready to create
the partitions. We will use a default partitioning scheme as discussed
previously. Of course, don't follow these instructions to the letter if
you don't want the same partitioning scheme!
</p>

</body>
</subsection>
<subsection>
<title>Creating the PPC PReP boot partition</title>
<body>

<p>
We first create a small PReP boot partition. Type <c>n</c> to create a new
partition, then <c>p</c> to select a primary partition, followed by
<c>1</c> to select the first primary partition. When prompted for the
first cylinder, hit enter. When prompted for the last cylinder, type
<c>+7M</c> to create a partition 7 Mbyte in size. After you've done
this, type <c>t</c> to set the partition type, <c>1</c> to select the
partition you just created and then type in <c>41</c> to set the
partition type to "PPC PReP Boot".  Finally, you'll need to mark the PReP
partition as bootable.
</p>

<note>
The PReP partition has to be smaller than 8 MByte!
</note>

<pre caption="Creating the PReP boot partition">
Command (m for help): <i>p</i>

Disk /dev/sda: 30.7 GB, 30750031872 bytes
141 heads, 63 sectors/track, 6761 cylinders
Units = cylinders of 8883 * 512 = 4548096 bytes

   Device Boot      Start         End      Blocks   Id  System

Command (m for help): <i>n</i>
Command action
      e   extended
      p   primary partition (1-4)
<i>p</i>
Partition number (1-4): <i>1</i>
First cylinder (1-6761, default 1): 
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-6761, default
6761): <i>+8M</i>

Command (m for help): <i>t</i>
Selected partition 1
Hex code (type L to list codes): <i>41</i>
Changed system type of partition 1 to 41 (PPC PReP Boot)

Command (m for help): <i>a</i>
Partition number (1-4): <i>1</i>
Command (m for help):
</pre>

<p>
Now, when you type <c>p</c>, you should see the following partition information:
</p>

<pre caption="Created boot partition">
Command (m for help): <i>p</i>

Disk /dev/sda: 30.7 GB, 30750031872 bytes
141 heads, 63 sectors/track, 6761 cylinders
Units = cylinders of 8883 * 512 = 4548096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1  *            1           3       13293   41  PPC PReP Boot

Command (m for help):
</pre>
</body>
</subsection>
<subsection>
<title>Creating the Swap Partition</title>
<body>

<p>
Let's now create the swap partition. To do this, type <c>n</c> to create
a new partition, then <c>p</c> to tell fdisk that you want a primary
partition. Then type <c>2</c> to create the second primary partition,
<path>/dev/sda2</path> in our case. When prompted for the first
cylinder, hit enter. When prompted for the last cylinder, type
<c>+512M</c> to create a partition 512MB in size. After you've done
this, type <c>t</c> to set the partition type, <c>2</c> to select the
partition you just created and then type in <c>82</c> to set the
partition type to "Linux Swap". After completing these steps, typing
<c>p</c> should display a partition table that looks similar to this:
</p>

<pre caption="Partition listing after creating a swap partition">
Command (m for help): <i>p</i>

Disk /dev/sda: 30.7 GB, 30750031872 bytes
141 heads, 63 sectors/track, 6761 cylinders
Units = cylinders of 8883 * 512 = 4548096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           3       13293   41  PPC PReP Boot
/dev/sda2               4         117      506331   82  Linux swap

Command (m for help):
</pre>

</body>
</subsection>
<subsection>
<title>Creating the Root Partition</title>
<body>

<p>
Finally, let's create the root partition. To do this, type <c>n</c> to
create a new partition, then <c>p</c> to tell fdisk that you want a
primary partition. Then type <c>3</c> to create the third primary
partition, <path>/dev/sda3</path> in our case. When prompted for the
first cylinder, hit enter. When prompted for the last cylinder, hit
enter to create a partition that takes up the rest of the remaining
space on your disk. After completing these steps, typing <c>p</c> should
display a partition table that looks similar to this:
</p>

<pre caption="Partition listing after creating the root partition">
Command (m for help): p

Disk /dev/sda: 30.7 GB, 30750031872 bytes
141 heads, 63 sectors/track, 6761 cylinders
Units = cylinders of 8883 * 512 = 4548096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           3       13293   41  PPC PReP Boot
/dev/sda2               4         117      506331   82  Linux swap
/dev/sda3             118        6761    29509326   83  Linux

Command (m for help):
</pre>
</body>
</subsection>
<subsection>
<title>Saving the Partition Layout</title>
<body>

<p>
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>.
</p>

<pre caption="Save and exit fdisk">
Command (m for help): <i>w</i>
</pre>

<p>
Now that your partitions are created, you can now continue with <uri
link="#filesystems">Creating Filesystems</uri>.
</p>

</body>
</subsection>
</section>
<section id="filesystems">
<title>Creating Filesystems</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your partitions are created, it is time to place a filesystem on them. 
If you don't care about what filesystem to choose and are happy with what we use
as default in this handbook, continue with <uri 
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
Otherwise read on to learn about the available filesystems...
</p>

</body>
</subsection>
<subsection>
<title>Filesystems?</title>
<body>

<note>
Several filesystems are available. ext2, ext3 and ReiserFS support is built in
the Installation CD kernels. JFS and XFS support is available through kernel
modules.
</note>

<p>
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
journaling, which means that routine ext2 filesystem checks at startup time can
be quite time-consuming. There is now quite a selection of newer-generation
journaled filesystems that can be checked for consistency very quickly and are
thus generally preferred over their non-journaled counterparts. Journaled
filesystems prevent long delays when you boot your system and your filesystem
happens to be in an inconsistent state.
</p>

<p>
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
journaling for fast recovery in addition to other enhanced journaling modes like
full data and ordered data journaling. It uses an HTree index that enables high
performance in almost all situations. In short, ext3 is a very good and reliable
filesystem.
</p>

<p>
<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
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. ReiserFS is solid and usable as
both general-purpose filesystem and for extreme cases such as the creation of
large filesystems, very large files and directories containing tens of
thousands of small files.
</p>

<p>
<b>XFS</b> is a filesystem with metadata journaling that is fully supported 
under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and
is optimized for scalability. We only recommend using this filesystem on Linux
systems with high-end SCSI and/or fibre channel storage and a uninterruptible
power supply. Because XFS aggressively caches in-transit data in RAM, improperly
designed programs (those that don't take proper precautions when writing files
to disk and there are quite a few of them) can lose a good deal of data if the
system goes down unexpectedly.
</p>

<p>
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently 
become production-ready. 
</p>

</body>
</subsection>
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>

<p>
To create a filesystem on a partition or volume, there are tools available for 
each possible filesystem:
</p>

<table>
<tr>
  <th>Filesystem</th>
  <th>Creation Command</th>
</tr>
<tr>
  <ti>ext2</ti>
  <ti><c>mke2fs</c></ti>
</tr>
<tr>
  <ti>ext3</ti>
  <ti><c>mke2fs -j</c></ti>
</tr>
<tr>
  <ti>reiserfs</ti>
  <ti><c>mkreiserfs</c></ti>
</tr>
<tr>
  <ti>xfs</ti>
  <ti><c>mkfs.xfs</c></ti>
</tr>
<tr>
  <ti>jfs</ti>
  <ti><c>mkfs.jfs</c></ti>
</tr>
</table>

<p>
For instance, to have the root partition (<path>/dev/sda4</path> in our example)
in ext3 (as in our example), you would use:
</p>

<pre caption="Applying a filesystem on a partition">
# <i>mke2fs -j /dev/sda4</i>
</pre>

<p>
Now create the filesystems on your newly created partitions (or logical
volumes).
</p>

<impo>
If you choose to use ReiserFS for <path>/</path>, do not change its default
block size if you will also be using <c>yaboot</c> as your bootloader, as
explained in <uri link="?part=1&amp;chap=10">Configuring the Bootloader</uri>.
</impo>

</body>
</subsection>
<subsection>
<title>Activating the Swap Partition</title>
<body>

<p>
<c>mkswap</c> is the command that is used to initialize swap partitions:
</p>

<pre caption="Creating a Swap signature">
# <i>mkswap /dev/sda3</i>
</pre>

<p>
To activate the swap partition, use <c>swapon</c>:
</p>

<pre caption="Activating the swap partition">
# <i>swapon /dev/sda3</i>
</pre>

<p>
Create and activate the swap with the commands mentioned above.
</p>

</body>
</subsection>
</section>
<section>
<title>Mounting</title>
<body>

<p>
Now that your partitions are initialized and are housing a filesystem, it is
time to mount those partitions. Use the <c>mount</c> command. Don't forget to
create the necessary mount directories for every partition you created. As an
example we create a mount point and mount the root partition:
</p>

<pre caption="Mounting partitions">
# <i>mkdir /mnt/gentoo</i>
# <i>mount /dev/sda4 /mnt/gentoo</i> 
</pre>

<note>
If you want your <path>/tmp</path> to reside on a separate partition, be sure to
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This
also holds for <path>/var/tmp</path>.
</note>

<p>
Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
Installation Files</uri>.
</p>

</body>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-kernel.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-kernel.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc64-kernel.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-kernel.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-08-12</date>

<section>
<title>Timezone</title>
<body>

<p>
You first need to select your timezone so that your system knows where it is
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
it to <path>/etc/localtime</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact
GMT+8.
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
</pre>

</body>
</section>
<section>
<title>Installing the Sources</title>
<subsection>
<title>Choosing a Kernel</title>
<body>

<p>
The core around which all distributions are built is the Linux kernel.
It is the layer between the user programs and your system hardware.
Gentoo provides its users several possible kernel sources. A full
listing with description is available at the <uri
link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>.
</p>

<p>
For PPC64 you should use <c>gentoo-sources</c>.
</p>

<pre caption="Installing a kernel source">
# <i>emerge gentoo-sources</i>
</pre>

<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
Your version may be different, so keep this in mind.
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root    root       12 Aug 10 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
</pre>

<p>
Now it is time to configure and compile your kernel source. There is the
ability to use "genkernel" which would create a generic kernel like the
ones used on the installation CDs, but it is not fully functional for PPC64 at
the moment.
</p>

<p>
Continue now with <uri link="#manual">Manual Configuration</uri>. 
</p>

</body>
</subsection>
</section>
<section id="manual">
<title>Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Manually configuring a kernel is often seen as the most difficult procedure a
Linux user ever has to perform. Nothing is less true -- after configuring a
couple of kernels you don't even remember that it was difficult ;)
</p>

<p>
However, one thing <e>is</e> true: you must know your system when you
configuring a kernel manually. Most information can be gathered by emerging 
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
be able to  use <c>lspci</c> within the chrooted environment. You may safely 
ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
uses (it might provide you with a nice hint on what to enable).
</p>

<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
<comment>Important: In case you are in 32-bit userland, you must edit the top
level Makefile in /usr/src/linux and change the CROSS_COMPILE option to
CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run
make menuconfig or it may result in kernel compilation problems.</comment>
# <i>make menuconfig</i>
</pre>

<p>
You will be greeted with several configuration sections. We'll first
list some options you must activate (otherwise Gentoo will not function,
or not function properly without additional tweaks).
</p>

</body>
</subsection>
<subsection>
<title>Activating Required Options</title>
<body>

<p>
First of all, activate the use of development and experimental
code/drivers. You need this, otherwise some very important code/drivers
won't show up:
</p>

<pre caption="Selecting experimental code/drivers">
General setup ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
</pre>

<p>
Now go to <c>File Systems</c> and select support for the filesystems you use.
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc file
system</c>, and <c>/dev/pts file system for Unix98 PTYs</c>:
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  [*] Virtual memory file system support (former shm fs)
  [*] /proc file system support
  [*] /dev/pts file system for Unix98 PTYs

<comment>(Select one or more of the following options as needed by your system)</comment>
  &lt;*&gt; Reiserfs support
  &lt;*&gt; Ext3 journalling file system support
  &lt;*&gt; JFS filesystem support
  &lt;*&gt; Second extended fs support
  &lt;*&gt; XFS filesystem support
</pre>

<note>
You will find some of the mentioned options under <c>Pseudo
filesystems</c> which is a subpart of <c>File systems</c>.
</note>

<p>
If you are using PPPoE to connect to the Internet or you are using a
dial-up modem, you will need the following options in the kernel (you
will find the mentioned options under <c>Networking support</c> which is
a subpart of <c>Device Drivers</c>):
</p>

<pre caption="Selecting PPPoE necessary drivers">
Network device support ---&gt;
  &lt;*&gt; PPP (point-to-point protocol) support
  &lt;*&gt;   PPP support for async serial ports
  &lt;*&gt;   PPP support for sync tty ports
</pre>

<p>
The two compression options won't harm but are not definitely needed, neither
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
when configured to do kernel mode PPPoE.
</p>

<p>
If you require it, don't forget to include support in the kernel for your
ethernet card.
</p>

<p>
Disable ADB raw keycodes:
</p>

<pre caption="Disabling ADB raw keycodes">
Macintosh Device Drivers ---&gt;
  [ ] Support for ADB raw keycodes
</pre>

<p>
When you're done configuring your kernel, continue with <uri
link="#compiling">Compiling and Installing</uri>.
</p>

</body>
</subsection>
<subsection id="compiling">
<title>Compiling and Installing</title>
<body>

<p>
Now that your kernel is configured, it is time to compile and install it. Exit 
the configuration and start the compilation process:
</p>

<pre caption="Compiling the kernel">
# <i>make &amp;&amp; make modules_install</i>
</pre>

<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path>. Remember to replace <path>&lt;kernel-version&gt;</path>
with your actual kernel version: 
</p>

<pre caption="Installing the kernel">
# <i>cp vmlinux /boot/&lt;kernel-version&gt;</i>
</pre>

<p>
Now continue with <uri link="#kernel_modules">Configuring the Modules</uri>.
</p>

</body>
</subsection>
</section>
<section id="kernel_modules">
<title>Configuring the Modules</title>
<body>

<p>
You should list the modules you want automatically loaded in 
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra
options to the modules too if you want.
</p>

<p>
To view all available modules, run the following <c>find</c> command. Don't
forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
just compiled:
</p>

<pre caption="Viewing all available modules">
# <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
</pre>

<p>
For instance, to automatically load the <c>3c59x.ko</c> module, edit the
<path>kernel-2.6</path> file and enter the module name in it.
</p>

<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
</pre>

<pre caption="/etc/modules.autoload.d/kernel-2.6">
3c59x
</pre>

<p>
Continue the installation with <uri link="?part=1&amp;chap=8">Configuring 
your System</uri>.
</p>

</body>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-medium.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-medium.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/plain

Index: hb-install-ppc64-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-medium.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-29</date>

<section>
<title>Hardware Requirements</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Before we start, we first list what hardware requirements you need to
successfully install Gentoo on your box. 
</p>

</body>
</subsection>
<subsection>
<title>Hardware Requirements</title>
<body>

<table>
<tr>
  <th>CPU</th>
  <ti>Any PowerPC64 CPU</ti>
</tr>
<tr>
  <th>Systems</th>
  <ti>
    IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower
  </ti>
</tr>
<tr>
  <th>Memory</th>
  <ti>64 MB</ti>
</tr>
<tr>
  <th>Diskspace</th>
  <ti>1.5 GB (excluding swap space)</ti>
</tr>
<tr>
  <th>Swap space</th>
  <ti>At least 256 MB</ti>
</tr>
</table>

<p>
For a full list of supported systems, please go to 
<uri>http://www.linuxppc64.org/hardware.shtml</uri>.
</p>

</body>
</subsection>
</section>

<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using a <e>stage3</e> tarball file.
Such a tarball is an archive that contains a minimal environment from
which you can succesfully install Gentoo Linux onto your system.
</p>

<p>
Installations using a stage1 or stage2 tarball file are not documented in the
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo
FAQ</uri> on these matters.
</p>

</body>
</subsection>
<subsection>
<title>Gentoo Universal Installation CD</title>
<body>
  
<p> 
An Installation CD is a bootable medium which contains a self-sustained Gentoo
environment. It allows you to boot Linux from the CD. During the boot process
your hardware is detected and the appropriate drivers are loaded. The Gentoo
Installation CDs are maintained by Gentoo developers.
</p>

<p>
There currently are two Installation CDs available:
</p>

<ul>
  <li>
    The Universal Installation CD contains everything you need to install
    Gentoo. It provides stage3 files for common architectures, source code
    for the extra applications you need to choose from and, of course, the
    installation instructions for your architecture.
  </li>
  <li>
    The Minimal Installation CD contains only a minimal environment that allows
    you to boot up and configure your network so you can connect to the
    Internet. It does not contain any additional files and cannot be used
    during the current installation approach.
  </li>
</ul>

<p>
Gentoo also provides a Package CD. This is not an Installation CD but an
additional resource that you can exploit during the installation of your Gentoo
system. It contains prebuilt packages (also known as the GRP set) that allow
you to easily and quickly install additional applications immediately after the
Gentoo installation and right before you update your Portage tree.
</p>

<p>
The use of the Package CD is covered later in this document.
</p>

</body> 
</subsection>
<subsection>
<title>Choosing a userland</title>
<body>

<p>
On PPC64, the kernel is 64-bit and the <e>userland</e> can be 32-bit or 64-bit. The
userland is basically the applications you are running, such as
<c>bash</c> or <c>mozilla-firefox</c>. They can be compiled and run in either
64-bit or 32-bit modes. The Gentoo/PPC64 team provides both 32-bit and 64-bit
userlands, so which one should you use?
</p>

<p>
You may have heard that 64-bit applications are better, but in fact, 32-bit
applications take up slightly less memory and often run a little bit faster than
64-bit applications.
</p>

<p>
You really only need 64-bit applications when you need more memory than a 32-bit
userland allows, or if you do a lot of 64-bit number crunching. If you run
applications that require more than 4GB of memory or you run scientific
applications, you should choose the 64-bit userland. Otherwise, choose the
32-bit userland, as it is recommended by the Gentoo/PPC64 developers.
</p>

<p>
Additionally, the 32-bit userland has been available in Portage longer than the
64-bit userland has. This means that there are more applications tested in the
32-bit userland that just work "out of the box." Many applications compiled for
the 64-bit userland may be just as stable as the 32-bit version, but they
haven't been tested yet. Though testing isn't difficult to do, it can be
annoying and time consuming if you want to use many untested 64-bit
applications. Also, some programs just won't run in the 64-bit userland until
their code is fixed, such as OpenOffice.
</p>

<p>
The Gentoo/PPC64 team provides stages and Package CDs for both 32-bit and 64-bit
userlands, so no matter which one you choose, you'll be able to successfully
install Gentoo and get a full system up and running with minimal fuss.
</p>

</body>
</subsection>
</section>
<!-- STOP -->
<section>
<title>Download, Burn and Boot a Gentoo Installation CD</title>
<subsection>
<title>Downloading and Burning the Installation CDs</title>
<body>

<p>
You can download the Universal Installation CD (and, if you want to, the
Packages CD as well) from one of our <uri
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in
the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs
are located in the <path><keyval id="release-dir"/>packagecd</path> directory.
</p>

<p>
Inside those directories you'll find ISO files. Those are full CD images which
you can write on a CD-R.
</p>

<p>
After downloading the file, you can verify its integrity to see if it is
corrupted or not:
</p>

<ul>
  <li>
    You can check its MD5 checksum and compare it with the MD5 checksum we
    provide (for instance with the <c>md5sum</c> tool under Linux/Unix or
    <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows).  How
    to verify MD5 checksums with Mac OS X is described in the <uri
    link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>.
  </li>
  <li>
    You can verify the cryptographic signature that we provide. You need to
    obtain the public key we use (0x17072058) before you proceed though.
  </li>
</ul>

<p>
To fetch our public key using the GnuPG application, run the following command:
</p>

<pre caption="Obtaining the public key">
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i>
</pre>

<p>
Now verify the signature:
</p>

<pre caption="Verify the cryptographic signature">
$ <i>gpg --verify &lt;signature file&gt; &lt;downloaded iso&gt;</i>
</pre>
    
<p> 
To burn the downloaded ISO(s), you have to select raw-burning. How you
do this is highly program-dependent. We will discuss <c>cdrecord</c> and
<c>K3B</c> here; more information can be found in our <uri
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>.
</p>

<ul>
  <li>
    With cdrecord, you simply type <c>cdrecord dev=/dev/hdc &lt;downloaded iso
    file&gt;</c> (replace <path>/dev/hdc</path> with your CD-RW drive's device
    path).
  </li>
  <li>
    With K3B, select <c>Tools</c> &gt; <c>Burn CD Image</c>. Then you can locate
    your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>.
  </li>
</ul>

</body>
</subsection>
<subsection>
<title>Booting the Installation CD on an Apple</title>
<body>

<p>
Please check the <path>README.kernel</path> on the Installation CD for the
latest information on how to boot various kernels and getting hardware support.
</p>

<p>
Place the Installation CD in the CD-ROM and reboot the system. Hold down the 
'C' key at bootup. You will be greeted by a friendly welcome message and a 
<e>boot:</e> prompt at the bottom of the screen.
</p>

<p>
You are also able to tweak some kernel options at this prompt. The following
table lists the available boot options you can add:
</p>

<table>
<tr>
  <th>Boot Option</th>
  <th>Description</th>
</tr>
<tr>
  <ti><c>video</c></ti>
  <ti>
    This option takes one of the following vendor-specific tags:
    <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>, <c>nvidiafb</c>
    or <c>ofonly</c>. You can follow this tag with the resolution and
    refreshrate you want to use. For instance
    <c>video=radeonfb:1280x1024@75</c>. If you are uncertain what to choose,
    <c>ofonly</c> will most certainly work.
  </ti>
</tr>
<tr>
  <ti><c>nol3</c></ti>
  <ti>
    Disables level 3 cache on some powerbooks (needed for at least the 17")
  </ti>
</tr>
<tr>
  <ti><c>debug</c></ti>
  <ti>
    Enables verbose booting, spawns an initrd shell that can be used to debug
    the Installation CD
  </ti>
</tr>
<tr>
  <ti><c>sleep=X</c></ti>
  <ti>
    Wait X seconds before continuing; this can be needed by some very old SCSI
    CD-ROMs which don't speed up the CD quick enough
  </ti>
</tr>
<tr>
  <ti><c>bootfrom=X</c></ti>
  <ti>
    Boot from a different device
  </ti>
</tr>
</table>

<p>
At this prompt, hit enter, and a complete Gentoo Linux environment will be
loaded from the CD. Continue with <uri link="#booted">And When You're
Booted...</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Booting the Installation CD on an IBM pSeries, OpenPower and Power5
iSeries servers</title>
<body>

<p>
Please check the <path>README.kernel</path> on the Installation CD for the
latest information on how to boot various kernels and getting hardware support.
</p>

<p>
Most modern pSeries servers can boot from the CDROM drive through SMS ('1' when
the “IBM IBM IBM” messages flash across the console). On some older  pSeries
boxes, sometimes the cds might not autoboot. You might have to set up your
cdrom as a bootable device in the multi-boot menu. (F1 at startup) The other
option is to jump into OF and do it from there:
</p>

<ol>
  <li>
    Boot into OF  (this is 8 from the serial cons or F8 from a graphics
    cons, start hitting the key when you see the keyboard mouse etc etc
    messages.
  </li>
  <li>Run the command 0> boot cdrom:1,yaboot</li>
  <li>Stand back and enjoy!</li>
</ol>

</body>
</subsection>
<subsection id="booted">
<title>And When You're Booted...</title>
<body>

<p>
You will be greeted by a root ("#") prompt on the current console. You can also 
switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get 
back to the one you started on by pressing Alt-fn-F1.
</p>

<p>
If you are installing Gentoo on a system with a non-US keyboard, use
<c>loadkeys</c> to load the keymap for your keyboard. To list the available
keymaps, execute <c>ls /usr/share/keymaps/i386</c>.
</p>

<pre caption="Listing available keymaps">
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided
 on the Installation CD are ADB keymaps and unusable with the 
 Installation CD kernel)</comment>
# <i>ls /usr/share/keymaps/i386</i>
</pre>

<p>
Now load the keymap of your choice:
</p>

<pre caption="Loading a keymap">
# <i>loadkeys be-latin1</i>
</pre>

<p>
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>.
</p>

</body>
</subsection>
<subsection id="hardware">
<title>Extra Hardware Configuration</title>
<body>

<p>
When the Installation CD boots, it tries to detect all your hardware devices and
loads the appropriate kernel modules to support your hardware. In the vast
majority of cases, it does a very good job. However, in some cases it may not
auto-load the kernel modules you need. If the PCI auto-detection missed some of
your system's hardware, you will have to load the appropriate kernel modules
manually. 
</p>

<p>
In the next example we try to load the <c>8139too</c> module (support for 
certain kinds of network interfaces):
</p>

<pre caption="Loading kernel modules">
# <i>modprobe 8139too</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Tweaking Hard Disk Performance</title>
<body>

<p>
If you are an advanced user, you might want to tweak the IDE hard disk
performance using <c>hdparm</c>. With the <c>-tT</c> options you can
test the performance of your disk (execute it several times to get a
more precise impression):
</p>

<pre caption="Testing disk performance">
# <i>hdparm -tT /dev/hda</i>
</pre>

<p>
To tweak, you can use any of the following examples (or experiment
yourself) which use <path>/dev/hda</path> as disk (substitute with your
disk):
</p>

<pre caption="Tweaking hard disk performance">
<comment>Activate DMA:</comment>
# <i>hdparm -d 1 /dev/hda</i>
<comment>Activate DMA + Safe Performance-enhancing Options:</comment>
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
</pre>

</body>
</subsection>
<subsection id="useraccounts">
<title>Optional: User Accounts</title>
<body>

<p>
If you plan on giving other people access to your installation
environment or you want to chat using <c>irssi</c> without root privileges (for
security reasons), you need to create the necessary user accounts and change 
the root password.
</p>

<p>
To change the root password, use the <c>passwd</c> utility:
</p>

<pre caption="Changing the root password">
# <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
</pre>

<p>
To create a user account, we first enter their credentials, followed by
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks.
In the next example, we create a user called &quot;john&quot;.
</p>

<pre caption="Creating a user account">
# <i>useradd -m -G users john</i>
# <i>passwd john</i>
New password: <comment>(Enter john's password)</comment>
Re-enter password: <comment>(Re-enter john's password)</comment>
</pre>

<p>
You can change your user id from root to the newly created user by using
<c>su</c>:
</p>

<pre caption="Changing user id">
# <i>su - john</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Viewing Documentation while Installing</title>
<body>

<p>
If you want to view the Gentoo Handbook during the installation, make sure you
have created a user account (see <uri link="#useraccounts">Optional: User
Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in.
</p>

<p>
If you want to view the documentation on the CD you can immediately run
<c>links</c> to read it:
</p>

<pre caption="Viewing the on-CD documentation">
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
</pre>

<p>
However, it is preferred that you use the online Gentoo Handbook as it will be
more recent than the one provided on the CD.
</p>

<pre caption="Viewing the Online Documentation">
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
</pre>

<p>
You can go back to your original terminal by pressing <c>Alt-F1</c>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Starting the SSH Daemon</title>
<body>

<p>
If you want to allow other users to access your computer during the
Gentoo installation (perhaps because those users are going to help you
install Gentoo, or even do it for you), you need to create a user
account for them and perhaps even provide them with your root password 
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
</p>

<p>
To fire up the SSH daemon, execute the following command:
</p>

<pre caption="Starting the SSH daemon">
# <i>/etc/init.d/sshd start</i>
</pre>

<p>
To be able to use sshd, you first need to set up your networking. Continue with
the chapter on <uri link="?part=1&amp;chap=3">Configuring your Network</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-bootloader.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/plain

Index: hb-install-sparc-bootloader.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-bootloader.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Making your Choice</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your kernel is configured and compiled and the necessary system
configuration files are filled in correctly, it is time to install a
program that will fire up your kernel when you start the system. Such a
program is called a <e>bootloader</e>.
</p>

</body>
</subsection>
</section>
<section>
<title>Installing the SPARC Bootloader: SILO</title>
<body>

<p>
It is now time to install and configure <uri
link="http://www.sparc-boot.org">SILO</uri>, the Sparc Improved boot
LOader.
</p>

<pre caption = "Installing SILO">
# <i>emerge silo</i>
</pre>

<p>
Now open up your favorite editor (we use <c>nano</c> as an example) and
create <path>/etc/silo.conf</path>.
</p>

<pre caption = "Creating /etc/silo.conf">
# <i>nano -w /etc/silo.conf</i>
</pre>

<p>
Below you'll find an example <path>silo.conf</path> file. It uses the
partitioning scheme we use throughout this book and
<path>kernel-<keyval id="kernel-version"/></path> as kernelimage.
</p>

<pre caption = "Example /etc/silo.conf">
partition = 1         <comment># Boot partition (= root partition)</comment>
root = /dev/sda1      <comment># Root partition</comment>
timeout = 150         <comment># Wait 15 seconds before booting the default section</comment>

image = /boot/kernel-<keyval id="kernel-version"/>
  label = linux
</pre>

<p>
If you use the example <path>silo.conf</path> delivered by Portage, be
sure to comment out <e>all</e> lines that you do not need.
</p>

<p>
If the physical disk on which you want to install SILO (as bootloader) differs
from the physical disk on which <path>/etc/silo.conf</path> resides, you must
copy over <path>/etc/silo.conf</path> to a partition on that disk. Assuming that
<path>/boot</path> is a separate partition on that disk, copy over the
configuration file to <path>/boot</path> and run <c>/sbin/silo -f</c>:
</p>

<pre caption = "Only if /boot and the SILO destination are not on the same disk">
# <i>cp /etc/silo.conf /boot</i>
# <i>/sbin/silo -f -C /boot/silo.conf</i>
/boot/silo.conf appears to be valid
</pre>

<p>
Otherwise just run <c>/sbin/silo -f</c>:
</p>

<pre caption = "Run silo">
# <i>/sbin/silo -f</i>
/etc/silo.conf appears to be valid
</pre>

<note>
You have to run <c>silo</c> (with parameters) again each time you update or
reinstall the <c>sys-boot/silo</c> package.
</note>

<p>
Now continue with <uri link="#reboot">Rebooting the System</uri>.
</p>

</body>
</section>
<section id="reboot">
<title>Rebooting the System</title>
<subsection>
<body>

<p>
Exit the chrooted environment and unmount all mounted partitions. Then type in 
that one magical command you have been waiting for: <c>reboot</c>.
</p>

<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
# <i>exit</i>
cdimage ~# <i>cd</i>
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
cdimage ~# <i>reboot</i>
</pre>

<p>
Of course, don't forget to remove the bootable CD, otherwise the CD will be
booted again instead of your new Gentoo system.
</p>

<p>
Once rebooted in your Gentoo installation, finish up with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml?rev=1.1&content-type=text/plain

Index: hb-install-sparc-disk.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-26</date>

<section>
<title>Introduction to Block Devices</title>
<subsection>
<title>Block Devices</title>
<body>

<p>
We'll take a good look at some of the disk-oriented aspects of Gentoo Linux
and Linux in general, including Linux filesystems, partitions, and block
devices. Then, once you're familiar with the ins and outs of disks and
filesystems, you'll be guided through the process of setting up partitions
and filesystems for your Gentoo Linux installation.
</p>

<p>
To begin, we introduce <e>block devices</e>. The most typical block device is
probably the one that represents the first SCSI hard disk in a Linux system,
namely <path>/dev/sda</path>.
</p>

<p>
Block devices represent an abstract interface to the disk. User programs can
use these block devices to interact with your disk without worrying about
whether your drives are IDE, SCSI, or something else. The program can simply
address the storage on the disk as a bunch of contiguous, randomly-accessible
512-byte blocks.
</p>

<p>
Block devices show up as entries in <path>/dev/</path>. Typically, the first
SCSI drive is named <path>/dev/sda</path>, the second <path>/dev/sdb</path>,
and so on.  IDE drives are named similarly, however, they are prefixed by hd-
instead of sd-. If you are using IDE drives, the first one will be named
<path>/dev/hda</path>, the second <path>/dev/hdb</path>, and so on.
</p>

</body>
</subsection>
<subsection>
<title>Partitions</title>
<body>

<p>
Although it is theoretically possible to use the entire disk to house your Linux
system, this is almost never done in practice. Instead, full disk block devices
are split up in smaller, more manageable block devices. These are known as
<e>partitions</e> or <e>slices</e>.
</p>

<p>
The first partition on the first SCSI disk is <path>/dev/sda1</path>, the second
<path>/dev/sda2</path> and so on.  Similarly, the first two partitions on the
first IDE disk are <path>/dev/hda1</path> and <path>/dev/hda2</path>.
</p>

<p>
The third partition on Sun systems is set aside as a special "whole disk"
slice. This partition must not contain a file system.
</p>

<p>
Users who are used to the DOS partitioning scheme should note that Sun
disklabels do not have "primary" and "extended" partitions. Instead, up to
eight partitions are available per drive, with the third of these being
reserved.
</p>

</body>
</subsection>
</section>
<section>
<title>Designing a Partitioning Scheme</title>
<subsection>
<title>Default Partitioning Scheme</title>
<body>

<p>
If you are not interested in drawing up a partitioning scheme,
the table below suggests a suitable starting point for most systems. For
IDE-based systems, substitute <c>hda</c> for <c>sda</c> in the following.
</p>

<p>
Note that a separate <path>/boot</path> partition is generally <e>not</e>
recommended on SPARC, as it complicates the bootloader configuration.
</p>

<table>
<tr>
  <th>Partition</th>
  <th>Filesystem</th>
  <th>Size</th>
  <th>Mount Point</th>
  <th>Description</th>
</tr>
<tr>
    <ti>/dev/sda1</ti>
    <ti>ext3</ti>
    <ti>&lt;2 GByte</ti>
    <ti>/</ti>
    <ti>
      Root partition. For sparc64 systems with older OBP versions, this
      <e>must</e> be less than 2 GBytes in size, and the first partition on the
      disk.
    </ti>
</tr>
<tr>
    <ti>/dev/sda2</ti>
    <ti>swap</ti>
    <ti>512 MBytes</ti>
    <ti>none</ti>
    <ti>
      Swap partition. For bootstrap and certain larger compiles, at least 512
      MBytes of RAM (including swap) is required.
    </ti>
</tr>
<tr>
    <ti>/dev/sda3</ti>
    <ti>none</ti>
    <ti>Whole disk</ti>
    <ti>none</ti>
    <ti>Whole disk partition. This is required on SPARC systems.</ti>
</tr>
<tr>
    <ti>/dev/sda4</ti>
    <ti>ext3</ti>
    <ti>at least 2 GBytes</ti>
    <ti>/usr</ti>
    <ti>
      /usr partition. Applications are installed here. By default this partition
      is also used for Portage data (which takes around 500 Mbyte excluding
      source code).
    </ti>
</tr>
<tr>
    <ti>/dev/sda5</ti>
    <ti>ext3</ti>
    <ti>at least 1GByte</ti>
    <ti>/var</ti>
    <ti>
      /var partition. Used for program-generated data. By default Portage uses
      this partition for temporary space whilst compiling. Certain larger
      applications such as Mozilla and OpenOffice.org can require over 1 GByte
      of temporary space here when building.
    </ti>
</tr>
<tr>
    <ti>/dev/sda6</ti>
    <ti>ext3</ti>
    <ti>remaining space</ti>
    <ti>/home</ti>
    <ti>/home partition. Used for users' home directories.</ti>
</tr>
</table>

</body>
</subsection>
</section>

<section id="fdisk">
<title>Using fdisk to Partition your Disk</title>
<subsection>
<body>

<p>
The following parts explain how to create the example partition layout described
previously, namely:
</p>

<table>
<tr>
  <th>Partition</th>
  <th>Description</th>
</tr>
<tr>
    <ti>/dev/sda1</ti>
    <ti>/</ti>
</tr>
<tr>
    <ti>/dev/sda2</ti>
    <ti>swap</ti>
</tr>
<tr>
    <ti>/dev/sda3</ti>
    <ti>whole disk slice</ti>
</tr>
<tr>
    <ti>/dev/sda4</ti>
    <ti>/usr</ti>
</tr>
<tr>
    <ti>/dev/sda5</ti>
    <ti>/var</ti>
</tr>
<tr>
    <ti>/dev/sda6</ti>
    <ti>/home</ti>
</tr>
</table>

<p>
Change the partition layout as required. Remember to keep the root partition
entirely within the first 2 GBytes of the disk for older systems. There is also
a 15-partition limit for SCSI and SATA.
</p>

</body>
</subsection>
<subsection>
<title>Firing up fdisk</title>
<body>

<p>
Start <c>fdisk</c> with your disk as argument:
</p>

<pre caption="Starting fdisk">
# <i>fdisk /dev/sda</i>
</pre>

<p>
You should be greeted with the fdisk prompt:
</p>

<pre caption="The fdisk prompt">
Command (m for help):
</pre>

<p>
To view the available partitions, type in <c>p</c>:
</p>

<pre caption="Listing available partitions">
Command (m for help): <i>p</i>

Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda1             0       488    499712   83  Linux native
/dev/sda2           488       976    499712   82  Linux swap
/dev/sda3             0      8635   8842240    5  Whole disk
/dev/sda4           976      1953   1000448   83  Linux native
/dev/sda5          1953      2144    195584   83  Linux native
/dev/sda6          2144      8635   6646784   83  Linux native
</pre>

<p>
Note the <c>Sun disk label</c> in the output. If this is missing, the disk is
using the DOS-partitioning, not the Sun partitioning. In this case, use <c>s</c>
to ensure that the disk has a sun partition table:
</p>

<pre caption="Creating a Sun Disklabel">
Command (m for help): s
Building a new sun disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Drive type
   ?   auto configure
   0   custom (with hardware detected defaults)
   a   Quantum ProDrive 80S
   b   Quantum ProDrive 105S
   c   CDC Wren IV 94171-344
   d   IBM DPES-31080
   e   IBM DORS-32160
   f   IBM DNES-318350
   g   SEAGATE ST34371
   h   SUN0104
   i   SUN0207
   j   SUN0327
   k   SUN0340
   l   SUN0424
   m   SUN0535
   n   SUN0669
   o   SUN1.0G
   p   SUN1.05
   q   SUN1.3G
   r   SUN2.1G
   s   IOMEGA Jaz
Select type (? for auto, 0 for custom): <i>0</i>
Heads (1-1024, default 64): 
Using default value 64
Sectors/track (1-1024, default 32): 
Using default value 32
Cylinders (1-65535, default 8635): 
Using default value 8635
Alternate cylinders (0-65535, default 2): 
Using default value 2
Physical cylinders (0-65535, default 8637): 
Using default value 8637
Rotation speed (rpm) (1-100000, default 5400): <i>10000</i>
Interleave factor (1-32, default 1): 
Using default value 1
Extra sectors per cylinder (0-32, default 0): 
Using default value 0
</pre>

<p>
You can find the correct values in your disk's documentation. The
'auto configure' option does not usually work.
</p>

</body>
</subsection>
<subsection>
<title>Deleting Existing Partitions</title>
<body>

<p>
It's time to delete any existing partitions. To do this, type <c>d</c> and hit 
Enter. You will then be prompted for the partition number you would like to 
delete. To delete a pre-existing <path>/dev/sda1</path>, you would type:
</p>

<pre caption="Deleting a partition">
Command (m for help): <i>d</i>
Partition number (1-4): <i>1</i>
</pre>

<p>
<e>You should not delete partition 3 (whole disk).</e> This is required. If
this partition does not exist, follow the "Creating a Sun Disklabel"
instructions above.
</p>

<p>
After deleting all partitions except the Whole disk slice, you should have a
partition layout similar to the following:
</p>

<pre caption="View an empty partition scheme">
Command (m for help): <i>p</i>

Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda3             0      8635   8842240    5  Whole disk
</pre>


</body>
</subsection>

<subsection>
<title>Creating the Root Partition</title>
<body>

<p>
We're ready to create the root partition. To do this, type <c>n</c> to create a
new partition, then type <c>1</c> to create the partition. When prompted for
the first cylinder, hit enter. When prompted for the last cylinder, type
<c>+512M</c> to create a partition <c>512MBytes</c> in size. Make sure that the
entire root partition fits within the first 2GBytes of the disk. You can see
output from these steps below:
</p>

<pre caption="Creating a root partition">
Command (m for help): <i>n</i>
Partition number (1-8): <i>1</i>
First cylinder (0-8635): <i>(press Enter)</i>
Last cylinder or +size or +sizeM or +sizeK (0-8635, default 8635): <i>+512M</i>
</pre>

<p>
Now, when you type <c>p</c>, you should see the following partition printout:
</p>

<pre caption="Listing the partition layout">
Command (m for help): <i>p</i>

Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda1             0       488    499712   83  Linux native
/dev/sda3             0      8635   8842240    5  Whole disk
</pre>

</body>
</subsection>
<subsection>
<title>Creating a swap partition</title>
<body>

<p>
Next, let's create the swap partition. To do this, type <c>n</c> to create a new
partition, then <c>2</c> to create the second partition, <path>/dev/sda2</path>
in our case. When prompted for the first cylinder, hit enter. When prompted for 
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After 
you've done this, type <c>t</c> to set the partition type, and then type in 
<c>82</c> to set the partition type to "Linux Swap". After completing these 
steps, typing <c>p</c> should display a partition table that looks similar to 
this:
</p>

<pre caption="Listing of available partitions">
Command (m for help): <i>p</i>

Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda1             0       488    499712   83  Linux native
/dev/sda2           488       976    499712   82  Linux swap
/dev/sda3             0      8635   8842240    5  Whole disk
</pre>

</body>
</subsection>
<subsection>
<title>Creating the /usr, /var and /home partitions</title>
<body>

<p>
Finally, let's create the /usr, /var and /home partitions. As before,
type <c>n</c> to create a new partition, then type <c>4</c> to create the
third partition, <path>/dev/sda4</path> in our case. When prompted for the
first cylinder, hit enter. When prompted for the last cylinder, enter 
<c>+2048M</c> to create a partition 2 GBytes in size. Repeat this process
for <path>sda5</path> and <path>sda6</path>, using the desired sizes. Once
you're done, you should see something like this:
</p>

<pre caption="Listing complete partition table">
Command (m for help): <i>p</i>

Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda1             0       488    499712   83  Linux native
/dev/sda2           488       976    499712   82  Linux swap
/dev/sda3             0      8635   8842240    5  Whole disk
/dev/sda4           976      1953   1000448   83  Linux native
/dev/sda5          1953      2144    195584   83  Linux native
/dev/sda6          2144      8635   6646784   83  Linux native
</pre>

</body>
</subsection>
<subsection>
<title>Save and Exit</title>
<body>

<p>
To save your partition layout and exit <c>fdisk</c>, type <c>w</c>:
</p>

<pre caption="Save and exit fdisk">
Command (m for help): <i>w</i>
</pre>

<p>
Now that your partitions are created, you can now continue with <uri
link="#filesystems">Creating Filesystems</uri>.
</p>

</body>
</subsection>
</section>
<section id="filesystems">
<title>Creating Filesystems</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Now that your partitions are created, it is time to place a filesystem on them. 
If you don't care about what filesystem to choose and are happy with what is
used as default in this handbook, continue with <uri 
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
Otherwise, read on to learn about the available filesystems...
</p>

</body>
</subsection>
<subsection>
<title>Filesystems?</title>
<body>

<p>
Several filesystems are available, some are known to be stable on the
SPARC architecture.  Ext2 and ext3, for example, are known to work well.
Alternate filesystems may not function correctly.
</p>

<p>
<b>ext2</b> is the tried-and-true Linux filesystem. It does not support
journaling, which means that periodic checks of ext2 filesystems at startup
can be quite time-consuming. There is quite a selection of newer-generation
journaled filesystems that can be checked for consistency very quickly at
startup, and are therefore generally preferred over their non-journaled
counterparts. In general, journaled filesystems prevent long delays when a
system is booted and the filesystem is in an inconsistent state.
</p>

<p>
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
journaling for fast recovery in addition to other enhanced journaling modes like
full data and ordered data journaling. It uses an HTree index that enables high
performance in almost all situations. In short, ext3 is a very good and reliable
filesystem.
</p>

</body>
</subsection>
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>

<p>
To create a filesystem on a partition or volume, tools specific to the chosen
filesystem are available:
</p>

<table>
<tr>
  <th>Filesystem</th>
  <th>Creation Command</th>
</tr>
<tr>
  <ti>ext2</ti>
  <ti><c>mke2fs</c></ti>
</tr>
<tr>
  <ti>ext3</ti>
  <ti><c>mke2fs -j</c></ti>
</tr>
</table>

<p>
For instance, to create the root partition (<path>/dev/sda1</path> in our
example) as ext2, and the <path>/usr</path>, <path>/var</path>, and
<path>/home</path> partitions (<path>/dev/sda4</path>, <path>5</path>
and <path>6</path> in our example, respectively) as ext3, you would use:
</p>

<pre caption="Applying a filesystem on a partition">
# <i>mke2fs /dev/sda1</i>
# <i>mke2fs -j /dev/sda4</i>
# <i>mke2fs -j /dev/sda5</i>
# <i>mke2fs -j /dev/sda6</i>
</pre>

</body>
</subsection>
<subsection>
<title>Activating the Swap Partition</title>
<body>

<p>
<c>mkswap</c> is the command used to initialize swap partitions:
</p>

<pre caption="Creating a Swap signature">
# <i>mkswap /dev/sda2</i>
</pre>

<p>
To activate the swap partition, use <c>swapon</c>:
</p>

<pre caption="Activating the swap partition">
# <i>swapon /dev/sda2</i>
</pre>

<p>
Create and activate the swap with the commands mentioned above.
</p>

</body>
</subsection>
</section>
<section>
<title>Mounting</title>
<body>

<p>
Now that your partitions are initialized and are housing a filesystem, it is
time to mount them using the <c>mount</c> command. Don't forget to first
create the necessary mount directories for every partition you created. For
example:
</p>

<pre caption="Mounting partitions">
# <i>mount /dev/sda1 /mnt/gentoo</i>
# <i>mkdir /mnt/gentoo/usr</i>
# <i>mount /dev/sda4 /mnt/gentoo/usr</i>
# <i>mkdir /mnt/gentoo/var</i>
# <i>mount /dev/sda5 /mnt/gentoo/var</i>
# <i>mkdir /mnt/gentoo/home</i>
# <i>mount /dev/sda6 /mnt/gentoo/home</i>
</pre>

<note>
If you want your <path>/tmp</path> to reside on a separate partition, be sure
to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>.
This also holds for <path>/var/tmp</path>.
</note>

<p>
We will also have to mount the proc filesystem (a virtual interface with the 
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions.
</p>

<p>
Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
Installation Files</uri>.
</p>

</body>
</section>
</sections>




1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-kernel.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-kernel.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/plain

Index: hb-install-sparc-kernel.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-kernel.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-08-12</date>

<section>
<title>Timezone</title>
<body>

<p>
You first need to select your timezone so that your system knows where it is
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
it to <path>/etc/localtime</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact
GMT+8.
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
</pre>

</body>
</section>
<section>
<title>Installing the Sources</title>
<subsection>
<title>Choosing a Kernel</title>
<body>

<p>
The core around which all distributions are built is the Linux kernel. It is the
layer between the user programs and your system hardware. Gentoo provides its
users several possible kernel sources. A full listing with description is
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
Guide</uri>. 
</p>

<p>
For sparc-based systems we have <c>gentoo-sources</c> (recommended 2.6 kernel
sources).
</p>

<p>
In the next example we install <c>gentoo-sources</c>.
</p>

<pre caption="Installing a kernel source">
# <i>emerge gentoo-sources</i>
</pre>

<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
kernel source points to <c>linux-<keyval id="kernel-version"/></c>. Your version
may be different, so keep this in mind.
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root     root       12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
</pre>

<p>
Now it is time to configure and compile your kernel source. 
</p>

</body>
</subsection>
</section>
<section>
<title>Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Manually configuring a kernel is often seen as the most difficult procedure a
Linux user ever has to perform. Nothing is less true -- after configuring a
couple of kernels you don't even remember that it was difficult ;)
</p>

<p>
However, one thing <e>is</e> true: you must know your system when you start
configuring a kernel manually. Most information can be gathered by emerging 
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
be able to  use <c>lspci</c> within the chrooted environment. You may safely 
ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
You can also run <c>lsmod</c> to see what kernel modules the Installation CD 
uses (it might provide you with a nice hint on what to enable).
</p>

<p>
Now go to your kernel source directory and execute <c>make menuconfig</c>. This
will fire up an ncurses-based configuration menu.
</p>

<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
# <i>make menuconfig</i>
</pre>

<p>
You will be greeted with several configuration sections. We'll first list some
options you must activate (otherwise Gentoo will not function, or not function
properly without additional tweaks).
</p>

</body>
</subsection>
<subsection>
<title>Activating Required Options</title>
<body>

<p>
First of all, activate the use of development and experimental code/drivers.
You need this, otherwise some very important code/drivers won't show up:
</p>

<pre caption="Selecting experimental code/drivers">
General setup ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
</pre>

<p>
Now go to <c>File Systems</c> and select support for the filesystems you use.
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
file system</c>:
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [*] Virtual memory file system support (former shm fs)

<comment>(Select one or more of the following options as needed by your system)</comment>
  &lt;*&gt; Ext3 journalling file system support
  &lt;*&gt; Second extended fs support
</pre>

<p>
If you are using PPPoE to connect to the Internet or you are using a dial-up
modem, you will need the following options in the kernel:
</p>

<pre caption="Selecting PPPoE necessary drivers">
Device Drivers ---&gt;
  Networking support ---&gt;
    &lt;*&gt; PPP (point-to-point protocol) support
    &lt;*&gt;   PPP support for async serial ports
    &lt;*&gt;   PPP support for sync tty ports
</pre>

<p>
The two compression options won't harm but are not definitely needed, neither
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
when configured to do kernel mode PPPoE.
</p>

<p>
Now activate the correct bus-support:
</p>

<pre caption="Activating SBUS/UPA">
Console drivers ---&gt;
  Frame-buffer support ---&gt;
    [*] SBUS and UPA framebuffers             
      [*] Creator/Creator3D support     <comment>(Only for UPA slot adapter used in many Ultras)</comment>
    [*] CGsix (GX,TurboGX) support      <comment>(Only for SBUS slot adapter used in many SPARCStations)</comment>
</pre>

<p>
Of course you want support for the OBP:
</p>

<pre caption="Activating OBP Support">
Misc Linux/SPARC drivers ---&gt;
  [*]  /dev/openprom device support
</pre>

<p>
You will also need SCSI-specific support:
</p>

<pre caption="Activating SCSI-specific support">
SCSI support ---&gt;
  SCSI low-level drivers ---&gt;
    &lt;*&gt; Sparc ESP Scsi Driver             <comment>(Only for SPARC ESP on-board SCSI adapter)</comment>
    &lt;*&gt; PTI Qlogic, ISP Driver            <comment>(Only for SBUS SCSI controllers from PTI or QLogic)</comment>
    &lt;*&gt; SYM53C8XX Version 2 SCSI support  <comment>(Only for Ultra 60 on-board SCSI adapter)</comment>
</pre>

<p>
To support your network card, select one of the following:
</p>

<pre caption="Activating networking support">
Network device support ---&gt;
  Ethernet (10 or 100Mbit) ---&gt;
    &lt;*&gt; Sun LANCE support                   <comment>(Only for SPARCStation, older Ultra systems, and as Sbus option)</comment>
    &lt;*&gt; Sun Happy Meal 10/100baseT support  <comment>(Only for Ultra; also supports "qfe" quad-ethernet on PCI and Sbus)</comment>
    &lt;*&gt; DECchip Tulip (dc21x4x) PCI support <comment>(For some Netras, like N1)</comment>
  Ethernet (1000Mbit) ---&gt;
    &lt;*&gt; Broadcom Tigon3 support <comment>(Modern Netra, Sun Fire machines)</comment>
</pre>

<p>
When you have a 4-port Ethernet machine (10/100 or 10/100/1000) the port order
is different from the one used by Solaris. You can use <c>sys-apps/ethtool</c>
to check the port link status.
</p>

<p>
When you're done configuring your kernel, continue with <uri
link="#compiling">Compiling and Installing</uri>. However, after having
compiled the kernel, check its size:
</p>

<pre caption="Check kernel size">
# <i>ls -lh vmlinux</i>
-rw-r--r--    1 root     root         2.4M Oct 25 14:38 vmlinux
</pre>

<p>
If the (uncompressed) size is bigger than 7.5 MB, reconfigure your kernel until
it doesn't exceed these limits. One way of accomplishing this is by having most
kernel drivers compiled as modules.  Ignoring this can lead to a non-booting
kernel.
</p>

<p>
Also, if your kernel is just a tad too big, you can try stripping it using the
<c>strip</c> command:
</p>

<pre caption="Stripping the kernel">
# <i>strip -R .comment -R .note vmlinux</i>
</pre>

</body>
</subsection>
<subsection id="compiling">
<title>Compiling and Installing</title>
<body>

<p>
Now that your kernel is configured, it is time to compile and install it. Exit 
the configuration and start the compilation process:
</p>

<pre caption="Compiling the kernel">
# <i>make &amp;&amp; make image modules_install</i>
</pre>

<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path>. Remember to replace <path>&lt;kernel-version&gt;</path>
with your actual kernel version.
</p>

<pre caption="Installing the kernel">
# <i>cp arch/sparc64/boot/image /boot/&lt;kernel-version&gt;</i>
</pre>

<p>
Now continue with <uri link="#kernel_modules">Installing Separate Kernel
Modules</uri>.
</p>

</body>
</subsection>
</section>
<section id="kernel_modules">
<title>Installing Separate Kernel Modules</title>
<subsection>
<title>Configuring the Modules</title>
<body>

<p>
You should list the modules you want automatically loaded in
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
the modules too if you want.
</p>

<p>
To view all available modules, run the following <c>find</c> command. Don't
forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
just compiled:
</p>

<pre caption="Viewing all available modules">
# <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
</pre>

<p>
For instance, to automatically load the <c>3c59x.ko</c> module, edit the
<path>kernel-2.6</path> file and enter the module name in it.
</p>

<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
</pre>

<pre caption="/etc/modules.autoload.d/kernel-2.6">
3c59x
</pre>

<p>
Continue the installation with <uri link="?part=1&amp;chap=8">Configuring 
your System</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-medium.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-medium.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-medium.xml?rev=1.1&content-type=text/plain

Index: hb-install-sparc-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-medium.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-06-29</date>

<section>
<title>Hardware Requirements</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Before we start, we first list what hardware requirements you need to
successfully install Gentoo on your box.
</p>

</body>
</subsection>
<subsection>
<title>Hardware Requirements</title>
<body>

<table>
<tr>
  <th>Sparc System</th>
  <ti>
    Please check the <uri link="/proj/en/base/sparc/sunhw.xml">Gentoo
    Linux/SPARC64 Compatibility list</uri> or the <uri
    link="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri>
  </ti>
</tr>
<tr>
  <th>CPU</th>
  <ti>
    We currently only support sparc64 CPUs
  </ti>
</tr>
<tr>
  <th>Memory</th>
  <ti>64 MB</ti>
</tr>
<tr>
  <th>Diskspace</th>
  <ti>1.5 GB (excluding swap space)</ti>
</tr>
<tr>
  <th>Swap space</th>
  <ti>At least 256 MB</ti>
</tr>
</table>

</body>
</subsection>
</section>

<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using a <e>stage3</e> tarball file.
Such a tarball is an archive that contains a minimal environment from
which you can succesfully install Gentoo Linux onto your system.
</p>

<p>
Installations using a stage1 or stage2 tarball file are not documented in the
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo
FAQ</uri> on these matters.
</p>

</body>
</subsection>
<subsection>
<title>Gentoo Universal Installation CD</title>
<body>

<p>
An Installation CD is a bootable medium which contains a self-sustained Gentoo 
environment. It allows you to boot Linux from the CD. During the boot process 
your hardware is detected and the appropriate drivers are loaded. The Gentoo 
Installation CDs are maintained by Gentoo developers.
</p>

<p>
There currently are two Installation CDs available:
</p>

<ul>
  <li>
    The Universal Installation CD contains everything you need to install 
    Gentoo. It provides stage3 files for common architectures, source code 
    for the extra applications you need to choose from and, of course, the 
    installation instructions for your architecture.
  </li>
  <li>
    The Minimal Installation CD contains only a minimal environment that allows 
    you to boot up and configure your network so you can connect to the 
    Internet. It does not contain any additional files and cannot be used 
    during the current installation approach.
  </li>
</ul>
<!--
<p>
Gentoo also provides a Package CD. This is not an Installation CD but an
additional resource that you can exploit during the installation of your Gentoo
system. It contains prebuilt packages (also known as the GRP set) that allow
you to easily and quickly install additional applications (such as
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and
right before you update your Portage tree.
</p>

<p>
The use of the Package CD is covered later in this document. 
</p>
-->
</body>
</subsection>
</section>
<!-- STOP -->
<section>
<title>Download, Burn and Boot a Gentoo Installation CD</title>
<subsection>
<title>Downloading and Burning the Installation CDs</title>
<body>

<p>
You can download the Universal Installation CD <!--(and, if you want to, the
Packages CD as well) -->from one of our <uri
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in
the <path><keyval id="release-dir"/>installcd</path> directory<!-- ; the Package
CDs are located in the <path><keyval id="release-dir"/>packagecd</path>
directory -->.
</p>

<p>
Inside those directories you'll find ISO files. Those are full CD images which
you can write on a CD-R.
</p>

<p>
In case you wonder if your downloaded file is corrupted or not, you can check
its MD5 checksum and compare it with the MD5 checksum we provide (such as
<path><keyval id="min-cd-name"/>.DIGESTS</path>). You can check the MD5 checksum
with the <c>md5sum</c> tool under Linux/Unix or <uri
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows.
</p>

<p>
Another way to check the validity of the downloaded file is to use GnuPG to
verify the cryptographic signature that we provide (the file ending with
<path>.asc</path>). Download the signature file and obtain the public key:
</p>

<pre caption="Obtaining the public key">
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i>
</pre>

<p>
Now verify the signature:
</p>

<pre caption="Verify the cryptographic signature">
$ <i>gpg --verify &lt;signature file&gt; &lt;downloaded iso&gt;</i>
</pre>

<p>
To burn the downloaded ISO(s), you have to select raw-burning. How you
do this is highly program-dependent. We will discuss <c>cdrecord</c> and
<c>K3B</c> here; more information can be found in our <uri
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>.
</p>

<ul>
  <li>
    With cdrecord, you simply type <c>cdrecord dev=/dev/hdc &lt;downloaded
    iso&gt;</c> (replace <path>/dev/hdc</path> with your CD-RW drive's device
    path).
  </li>
  <li>
    With K3B, select <c>Tools</c> &gt; <c>Burn CD Image</c>. Then you can locate
    your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>.
  </li>
</ul>

</body>
</subsection>
<subsection>
<title>Booting the Universal Installation CD</title>
<body>

<p>
Insert the Gentoo Installation CD in the CD-ROM and boot your system. During 
startup, press Stop-A to enter OpenBootPROM (OBP). Once you are in the OBP, 
boot from the CD-ROM:
</p>

<pre caption="Booting the Installation CD">
ok <i>boot cdrom</i>
</pre>

<p>
You will be greeted by the SILO boot manager (on the Installation CD). You can
hit Enter for more help if you want. Type in <c>gentoo</c> and press enter to
continue booting the system:
</p>

<pre caption="Continue booting from the Installation CD">
boot: <i>gentoo</i>
</pre>

<p>
Once the Installation CD is booted, you will be automatically logged on to the 
system. 
</p>

<p>
You should have a root ("#") prompt on the current console. You will also find a
root prompt on the serial console (<path>ttyS0</path>).
</p>

<p>
Continue with <uri link="#hardware">Extra Hardware Configuration</uri>.
</p>

</body>
</subsection>
<subsection id="hardware">
<title>Extra Hardware Configuration</title>
<body>

<p>
If not all hardware is supported out-of-the-box, you will need to load the
appropriate kernel modules.
</p>

<p>
In the next example we try to load the <c>8139too</c> module (support for 
certain kinds of network interfaces):
</p>

<pre caption="Loading kernel modules">
# <i>modprobe 8139too</i>
</pre>

</body>
</subsection>
<subsection id="useraccounts">
<title>Optional: User Accounts</title>
<body>

<p>
If you plan on giving other people access to your installation
environment or you want to chat using <c>irssi</c> without root privileges (for
security reasons), you need to create the necessary user accounts and change 
the root password.
</p>

<p>
To change the root password, use the <c>passwd</c> utility:
</p>

<pre caption="Changing the root password">
# <i>passwd</i>
New password: <comment>(Enter your new password)</comment>
Re-enter password: <comment>(Re-enter your password)</comment>
</pre>

<p>
To create a user account, we first enter their credentials, followed by
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks.
In the next example, we create a user called &quot;john&quot;.
</p>

<pre caption="Creating a user account">
# <i>useradd -m -G users john</i>
# <i>passwd john</i>
New password: <comment>(Enter john's password)</comment>
Re-enter password: <comment>(Re-enter john's password)</comment>
</pre>

<p>
You can change your user id from root to the newly created user by using
<c>su</c>:
</p>

<pre caption="Changing user id">
# <i>su - john</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Viewing Documentation while Installing</title>
<body>

<p>
If you want to view the Gentoo Handbook (either from-CD or online) during the
installation, make sure you have created a user account (see <uri
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to
go to a new terminal and log in.
</p>

<p>
If you want to view the documentation on the CD you can immediately run
<c>links</c> to read it:
</p>

<pre caption="Viewing the on-CD documentation">
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
</pre>

<p>
However, it is preferred that you use the online Gentoo Handbook as it will be
more recent than the one provided on the CD. You can view it using <c>links</c>
as well, but only after having completed the <e>Configuring your Network</e>
chapter (otherwise you won't be able to go on the Internet to view the
document):
</p>

<pre caption="Viewing the Online Documentation">
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
</pre>

<p>
You can go back to your original terminal by pressing <c>Alt-F1</c>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Starting the SSH Daemon</title>
<body>

<p>
If you want to allow other users to access your computer during the
Gentoo installation (perhaps because those users are going to help you
install Gentoo, or even do it for you), you need to create a user
account for them and perhaps even provide them with your root password 
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
</p>

<p>
To fire up the SSH daemon, execute the following command:
</p>

<pre caption="Starting the SSH daemon">
# <i>/etc/init.d/sshd start</i>
</pre>

<p>
To be able to use sshd, you first need to set up your networking. Continue with
the chapter on <uri link="?part=1&amp;chap=3">Configuring your Network</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-stage.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-stage.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-stage.xml?rev=1.1&content-type=text/plain

Index: hb-install-stage.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-stage.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Installing a Stage Tarball</title>
<subsection>
<title>Setting the Date/Time Right</title>
<body>

<p>
Before you continue you need to check your date/time and update it. A
misconfigured clock may lead to strange results in the future!
</p>

<p>
To verify the current date/time, run <c>date</c>:
</p>

<pre caption="Verifying the date/time">
# <i>date</i>
Fri Mar 29 16:21:18 UTC 2005
</pre>

<p>
If the date/time displayed is wrong, update it using the <c>date
MMDDhhmmYYYY</c> syntax (<b>M</b>onth, <b>D</b>ay, <b>h</b>our, <b>m</b>inute
and <b>Y</b>ear). At this stage, you should use UTC time. You will be able to
define your timezone later on. For instance, to set the date to March 29th,
16:21 in the year 2005:
</p>

<pre caption="Setting the UTC date/time">
# <i>date 032916212005</i>
</pre>

</body>
</subsection>
</section>
<section id="available">
<title>Default: Using a Stage from the Installation CD</title>
<subsection>
<title>Extracting the Stage Tarball</title>
<body>

<p>
The stages on the CD reside in the <path>/mnt/cdrom/stages</path> directory. To
see a listing of available stages, use <c>ls</c>:
</p>

<pre caption="List all available stages">
# <i>ls /mnt/cdrom/stages</i>
</pre>

<p>
If the system replies with an error, you may need to mount the CD-ROM first:
</p>

<pre caption="Mounting the CD-ROM">
# <i>ls /mnt/cdrom/stages</i>
ls: /mnt/cdrom/stages: No such file or directory
# <i>mount /dev/cdroms/cdrom0 /mnt/cdrom</i>
# <i>ls /mnt/cdrom/stages</i>
</pre>

<p>
Now go into your Gentoo mountpoint (usually <path>/mnt/gentoo</path>):
</p>

<pre caption="Changing directory to /mnt/gentoo">
# <i>cd /mnt/gentoo</i>
</pre>

<p>
We will now extract the stage tarball of your choice. We will do this with the
<c>tar</c> tool. Make sure you use the same options (<c>xvjpf</c>)! The <c>x</c>
stands for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens
during the extraction process (this one is optional), the <c>j</c> for
<e>Decompress with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and
the <c>f</c> to denote that we want to extract a file, not standard input. In
the next example, we extract the stage tarball <path><keyval
id="stage3"/></path>. Be sure to substitute the tarball filename with your
stage.
</p>

<pre caption="Extracting the stage tarball">
# <i>tar xvjpf /mnt/cdrom/stages/<keyval id="stage3"/></i>
</pre>

<p>
Now that the stage is installed, continue with <uri
link="#installing_portage">Installing Portage</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Unpacking the Stage Tarball</title>
<body>

<p>
Now unpack your downloaded stage onto your system. We use <c>tar</c> to proceed
as it is the easiest method:
</p>

<pre caption="Unpacking the stage">
# <i>tar xvjpf stage3-*.tar.bz2</i>
</pre>

<p>
Make sure that you use the same options (<c>xvjpf</c>). The <c>x</c> stands
for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens during
the extraction process (this one is optional), the <c>j</c> for <e>Decompress
with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and the <c>f</c>
to denote that we want to extract a file, not standard input.
</p>

<p>
Now that the stage is installed, continue with <uri
link="#installing_portage">Installing Portage</uri>.
</p>

</body>
</subsection>
</section>
<section id="installing_portage">
<title>Installing Portage</title>
<subsection>
<title>Unpacking a Portage Snapshot</title>
<body>

<p>
You now have to install a Portage snapshot, a collection of files that inform
Portage what software titles you can install, which profiles are available, etc.
</p>

</body>
</subsection>
<subsection id="installing_from_InstallCD">
<title>Unpack the Snapshot from the Installation CD</title>
<body>

<p>
To install the snapshot, take a look inside <path>/mnt/cdrom/snapshots/</path> 
to see what snapshot is available:
</p>

<pre caption="Checking the /mnt/cdrom/snapshots content">
# <i>ls /mnt/cdrom/snapshots</i>
</pre>

<p>
Now extract the snapshot using the following construct. Again, make sure you
use the correct options with <c>tar</c>. Also, the <c>-C</c> is with a capital
<c>C</c>, not <c>c</c>. In the next example we use
<path>portage-&lt;date&gt;.tar.bz2</path> as the snapshot filename. Be sure to
substitute with the name of the snapshot that is on your Installation CD.
</p>

<pre caption="Extracting a Portage snapshot">
# <i>tar xvjf /mnt/cdrom/snapshots/portage-&lt;date&gt;.tar.bz2 -C /mnt/gentoo/usr</i>
</pre>

</body>
</subsection>
<subsection id="copysources">
<title>Copy Source Code Archives</title>
<body>

<p>
You also need to copy over all source code from the Universal Installation CD. 
</p>

<pre caption="Copy over source code">
# <i>mkdir /mnt/gentoo/usr/portage/distfiles</i>
# <i>cp /mnt/cdrom/distfiles/* /mnt/gentoo/usr/portage/distfiles/</i>
</pre>

</body>
</subsection>
</section>
<section id="compile_options">
<title>Configuring the Compile Options</title>
<subsection>
<title>Introduction</title>
<body>

<p>
To optimize Gentoo, you can set a couple of variables which impact Portage 
behaviour. All those variables can be set as environment variables (using
<c>export</c>) but that isn't permanent. To keep your settings, Portage provides
you with <path>/etc/make.conf</path>, a configuration file for Portage. It is
this file we will edit now. 
</p>

<note>
A commented listing of all possible variables can be found in
<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo 
installation you'll only need to set the variables which are mentioned beneath.
</note>

<p>
Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter
the optimization variables we will discuss hereafter. 
</p>

<pre caption="Opening /etc/make.conf">
# <i>nano -w /mnt/gentoo/etc/make.conf</i>
</pre>

<p>
As you probably noticed, the <path>make.conf.example</path> file is
structured in a generic way: commented lines start with "#", other lines define
variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path>
file uses the same syntax. Several of those variables are discussed next. 
</p>

<warn>
Do not make any modifications to the USE variable if you are performing a stage3
with GRP installation. You can alter the USE variable after having installed the
packages you want. Gremlins are known to attack your system if you ignore this
warning!
</warn>

</body>
</subsection>
<subsection>
<title>CHOST</title>
<body>

<p>
The <c>CHOST</c> variable declares the target build host for your system. This
variable should already be set to the correct value. <brite>Do not edit
it</brite> as that might break your system. If the <c>CHOST</c> variable does
not look correct to you, you might be using the wrong stage3 tarball.
</p>

</body>
</subsection>
<subsection>
<title>CFLAGS and CXXFLAGS</title>
<body>

<p>
The <c>CFLAGS</c> and <c>CXXFLAGS</c> variables define the optimization flags 
for the <c>gcc</c> C and C++ compiler respectively. Although we define those
generally here, you will only have maximum performance if you optimize these
flags for each program separately. The reason for this is because every program
is different.
</p>

<p>
In <path>make.conf</path> you should define the optimization flags you think
will make your system the most responsive <e>generally</e>. Don't place
experimental settings in this variable; too much optimization can make 
programs behave bad (crash, or even worse, malfunction).
</p>

<p>
We cannot explain all possible optimization options here, but if you want to 
investigate them all, read the <uri link="http://gcc.gnu.org/onlinedocs/">GNU 
Online Manual(s)</uri> or the <c>gcc</c> info page (<c>info gcc</c> -- only
works on a working Linux system). For common optimizations and architecture
specific settings, please read <path>/etc/make.conf.example</path>.  This
file also contains lots of examples and information; don't forget to read it
too.
</p>

<p>
A first setting is the <c>-march=</c> or <c>-mcpu=</c> flag, which specifies
the name of the target architecture. Possible options are described in the
<path>make.conf.example</path> file (as comments).
</p>

<p>
A second one is the <c>-O</c> flag (that is a capital O, not a zero),
which specifies the <c>gcc</c> optimization
class flag. Possible classes are <c>s</c> (for size-optimized),
<c>0</c> (zero - for no optimizations), <c>1</c>, <c>2</c> or <c>3</c> for more
speed-optimization flags (every class has the same flags as the one before, plus
some extras). <c>-O2</c> is the recommended default.
</p>

<p>
Another popular optimization flag is <c>-pipe</c> (use pipes rather than
temporary files for communication between the various stages of compilation).
It has no impact on the generated code.
</p>

<p>
Using <c>-fomit-frame-pointer</c> (which doesn't keep the frame pointer in a
register for functions that don't need one) might have serious repercussions on
the debugging of applications.
</p>

<p>
When you define the <c>CFLAGS</c> and <c>CXXFLAGS</c>, you should combine
several optimization flags. The default values contained in the stage3 archive
you unpacked should be good enough. The following example is just an example:
</p>

<pre caption="Defining the CFLAGS and CXXFLAGS variable">
CFLAGS="<keyval id="CFLAGS"/>"
<comment># Use the same settings for both variables</comment>
CXXFLAGS="${CFLAGS}"
</pre>

</body>
</subsection>
<subsection>
<title>MAKEOPTS</title>
<body>

<p>
With <c>MAKEOPTS</c> you define how many parallel compilations should occur when
you install a package. A good choice is the number of CPUs in your system plus 
one, but this guideline isn't always perfect.
</p>

<pre caption="MAKEOPTS for a regular, 1-CPU system">
MAKEOPTS="-j2"
</pre>

</body>
</subsection>
<subsection>
<title>Ready, Set, Go!</title>
<body>

<p>
Update your <path>/mnt/gentoo/etc/make.conf</path> to your own preference and
save (<c>nano</c> users would hit <c>Ctrl-X</c>). You are now ready to continue
with <uri link="?part=1&amp;chap=6">Chrooting into the Gentoo Base System</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-system.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-system.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-system.xml?rev=1.1&content-type=text/plain

Index: hb-install-system.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-system.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>Chrooting</title>
<subsection>
<title>Mounting the /proc and /dev Filesystems</title>
<body>

<p>
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to
allow the installation to use the kernel-provided information within the
chrooted environment, and then mount-bind the <path>/dev</path> filesystem.
</p>

<pre caption="Mounting /proc and /dev">
# <i>mount -t proc none /mnt/gentoo/proc</i>
# <i>mount -o bind /dev /mnt/gentoo/dev</i>
</pre>

</body>
</subsection>
<subsection>
<title>Entering the new Environment</title>
<body>

<p>
Now that all partitions are initialized and the base environment
installed, it is time to enter our new installation environment by
<e>chrooting</e> into it. This means that we change from the current
installation environment to your installation system (namely the 
initialized partitions).
</p>

<p>
This chrooting is done in three steps. First we will change the root
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> 
(on your partitions) using <c>chroot</c>. Then we will create a new environment
using <c>env-update</c>, which essentially creates environment variables.
Finally, we load those variables into memory using <c>source</c>.
</p>

<pre caption="Chrooting into the new environment">
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>env-update</i>
>>> Regenerating /etc/ld.so.cache...
# <i>source /etc/profile</i>
# <i>export PS1="(chroot) $PS1"</i>
</pre>

<p>
Congratulations! You are now inside your own Gentoo Linux environment.
Of course it is far from finished, which is why the installation still
has some sections left :-)
</p>

</body>
</subsection>
<subsection>
<title>Creating the Portage cache</title>
<body>

<p>
You have already installed the Portage tree, but you should now build the
Portage cache to speed up future emerges. <c>emerge --metadata</c> does this
for you.
</p>

<pre caption="Creating the Portage cache">
# <i>emerge --metadata</i>
</pre>

</body>
</subsection>
</section>

<section id="configure_USE">
<title>Configuring the USE Variable</title>
<subsection>
<title>What is the USE Variable?</title>
<body>

<p>
<c>USE</c> is one of the most powerful variables Gentoo provides to its users.
Several programs can be compiled with or without optional support for certain
items. For instance, some programs can be compiled with gtk-support, or with
qt-support. Others can be compiled with or without SSL support. Some programs
can even be compiled with framebuffer support (svgalib) instead of X11 support
(X-server).
</p>

<p>
Most distributions compile their packages with support for as much as possible,
increasing the size of the programs and startup time, not to mention an enormous
amount of dependencies. With Gentoo you can define what options a package 
should be compiled with. This is where <c>USE</c> comes into play.
</p>

<p>
In the <c>USE</c> variable you define keywords which are mapped onto
compile-options. For instance, <e>ssl</e> will compile ssl-support in the
programs that support it. <e>-X</e> will remove X-server support (note the
minus sign in front). <e>gnome gtk -kde -qt3 -qt4</e> will compile your
programs with gnome (and gtk) support, and not with kde (and qt) support,
making your system fully tweaked for GNOME.
</p>

</body>
</subsection>
<subsection>
<title>Modifying the USE Variable</title>
<body>

<warn>
Do not make any modifications to the USE variable yet if you plan to use our
prebuilt packages (GRP set). You can alter the USE variable after having
installed the packages you want. Gremlins are known to attack your system 
if you ignore this warning!
</warn>

<p>
The default <c>USE</c> settings are placed in
<path>/etc/make.profile/make.defaults</path>. What you place in
<path>/etc/make.conf</path> is calculated against these defaults settings. If
you add something to the <c>USE</c> setting, it is added to the default list. If
you remove something from the <c>USE</c> setting (by placing a minus sign in
front of it) it is removed from the default list (if it was in the default list
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path>
directory; it gets overwritten when you update Portage!
</p>

<p>
A full description on <c>USE</c> can be found in the second part of the Gentoo
Handbook, <uri link="?part=2&amp;chap=2">USE flags</uri>. A full description on
the available USE flags can be found on your system in
<path>/usr/portage/profiles/use.desc</path>. 
</p>

<pre caption="Viewing available USE flags">
# <i>less /usr/portage/profiles/use.desc</i>
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment>
</pre>

<p>
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA
and CD Recording support:
</p>

<pre caption="Opening /etc/make.conf">
# <i>nano -w /etc/make.conf</i>
</pre>

<pre caption="USE setting">
USE="-gtk -gnome qt3 qt4 kde dvd alsa cdr"
</pre>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/hb-install-tools.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-tools.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-tools.xml?rev=1.1&content-type=text/plain

Index: hb-install-tools.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!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/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-tools.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<sections>

<version>9.0</version>
<date>2007-05-07</date>

<section>
<title>System Logger</title>
<body>

<p>
Some tools are missing from the <e>stage3</e> archive because several packages
provide the same functionality. It is now up to you to choose which ones you
want to install.
</p>

<p>
The first tool you need to decide on has to provide logging facilities for your
system. Unix and Linux have an excellent history of logging capabilities -- if
you want you can log everything that happens on your system in logfiles. This
happens through the <e>system logger</e>.
</p>

<p>
Gentoo offers several system loggers to choose from. There are <c>sysklogd</c>,
which is the traditional set of system logging daemons, <c>syslog-ng</c>, an 
advanced system logger, and <c>metalog</c> which is a highly-configurable 
system logger. Others might be available through Portage as well - our number of
available packages increases on a daily basis.
</p>

<p>
If you plan on using <c>sysklogd</c> or <c>syslog-ng</c> you might want to
install <c>logrotate</c> afterwards as those system loggers don't provide any 
rotation mechanism for the log files.
</p>

<!--
  Even though syslog-ng does not rotate the logs, it does conform to the syslog
  RFC (http://www.faqs.org/rfcs/rfc3164.html) and is far more powerful than most  other system loggers. That and some architectures really prefer syslog-ng
  above others (metalog for instance doesn't work nicely with sparc all the
  time).
-->

<p>
To install the system logger of your choice, <c>emerge</c> it and have it added
to the default runlevel using <c>rc-update</c>. The following example installs
<c>syslog-ng</c>. Of course substitute with your system logger:
</p>

<pre caption="Installing a system logger">
# <i>emerge syslog-ng</i>
# <i>rc-update add syslog-ng default</i>
</pre>

</body>
</section>
<section>
<title>Optional: Cron Daemon</title>
<body>

<p>
Next is the cron daemon. Although it is optional and not required for your
system, it is wise to install one. But what is a cron daemon? A cron daemon 
executes scheduled commands. It is very handy if you need to execute some 
command regularly (for instance daily, weekly or monthly).
</p>

<p>
We only provide <c>vixie-cron</c> for networkless installations. If you want
another cron daemon you can wait and install it later on.
</p>

<pre caption="Installing a cron daemon">
# <i>emerge vixie-cron</i>
# <i>rc-update add vixie-cron default</i>
</pre>

</body>
</section>
<section>
<title>Optional: File Indexing</title>
<body>

<p>
If you want to index your system's files so you are able to quickly
locate them using the <c>locate</c> tool, you need to install
<c>sys-apps/slocate</c>. 
</p>

<pre caption="Installing slocate">
# <i>emerge slocate</i>
</pre>

</body>
</section>
<section>
<title>File System Tools</title>
<subsection>
<body>

<p>
Depending on what file systems you are using, you need to install the necessary
file system utilities (for checking the filesystem integrity, creating 
additional file systems etc.).
</p>

<p>
The following table lists the tools you need to install if you use a certain
file system. Not all filesystems are available for each and every architecture
though.
</p>

<table>
<tr>
  <th>File System</th>
  <th>Tool</th>
  <th>Install Command</th>
</tr>
<tr>
  <ti>XFS</ti>
  <ti>xfsprogs</ti>
  <ti><c>emerge xfsprogs</c></ti>
</tr>
<tr>
  <ti>ReiserFS</ti>
  <ti>reiserfsprogs</ti>
  <ti><c>emerge reiserfsprogs</c></ti>
</tr>
<tr>
  <ti>JFS</ti>
  <ti>jfsutils</ti>
  <ti><c>emerge jfsutils</c></ti>
</tr>
</table>

<p>
If you are an EVMS user, you need to install <c>emvs</c>:
</p>

<pre caption="Installing EVMS utilities">
# <i>USE="-gtk" emerge evms</i>
</pre>

<p>
The <c>USE="-gtk"</c> will prevent the installation of dependencies. If you
want to enable the <c>evms</c> graphical tools, you can recompile <c>evms</c>
later on.
</p>

</body>
</subsection>
<subsection test="contains('PPC PPC64', func:keyval('arch'))">
<title>Optional: RAID utilities for IBM hardware</title>
<body>

<p>
If you are using SCSI RAID on a POWER5-based system, you should consider 
installing the <c>iprutils</c> which will allow you to work with the RAID disk 
array, get status on the disks in the arrays, and update microcode among other 
functions.
</p>

<pre caption="Installing iprutils">
# <i>emerge iprutils</i>
</pre>

</body>
</subsection>
</section>
<section>
<title>Networking Tools</title>
<subsection>
<body>

<p>
If you don't require any additional networking-related tools (such as <c>ppp</c>
or a dhcp client) continue with <uri link="?part=1&amp;chap=10">Configuring the
Bootloader</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Installing a DHCP Client</title>
<body>

<p>
If you require Gentoo to automatically obtain an IP address for your network
interface(s), you need to install <c>dhcpcd</c> (or any other DHCP Client) 
on your system. If you don't do this now, you might not be able to connect 
to the internet after the installation!
</p>

<pre caption="Installing dhcpcd">
# <i>emerge dhcpcd</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Installing a PPPoE Client</title>
<body>

<p>
If you need <c>ppp</c> to connect to the net, you need to install it.
</p>

<pre caption="Installing ppp">
# <i>emerge ppp</i>
</pre>

<p>
Now continue with <uri link="?part=1&amp;chap=10">Configuring the
Bootloader</uri>.
</p>

</body>
</subsection>
</section>
</sections>



1.1                  xml/htdocs/doc/en/handbook/2008.0/index.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/index.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/index.xml?rev=1.1&content-type=text/plain

Index: index.xml
===================================================================
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/index.xml,v 1.1 2008/02/27 22:46:58 nightmorph Exp $ -->

<guide link="/doc/en/handbook/2007.1/index.xml">
<title>Gentoo 2007.1 Networkless Handbook</title>

<author title="Author">
  <mail link="swift"/>
</author>

<abstract>
The Gentoo 2007.1 Networkless Handbook is an effort to centralize documentation
into a coherent handbook. It contains the networkless installation instructions
for the 2007.1 release and parts on working with Gentoo and Portage.
</abstract>

<license/>

<version>9.0</version>
<date>2007-06-06</date>

<chapter>
<title>The Gentoo Linux 2007.1 Networkless Handbooks</title>

<section>
<title>Available languages</title>
<body>

<p>
The Gentoo Linux 2007.1 Networkless Handbook is available in the following
languages:
</p>

<p>
<uri link="/doc/en/handbook/2007.1/">English</uri> | 
<uri link="/doc/id/handbook/2007.1/">Indonesian</uri> |
<uri link="/doc/it/handbook/2007.1/">Italian</uri> |
<uri link="/doc/pl/handbook/2007.1/">Polish</uri> |
<uri link="/doc/zh_cn/handbook/2007.1/">Simplified Chinese</uri>
</p>

</body>
</section>
<section>
<title>Introduction</title>
<body>

<p>
Welcome to the Gentoo Linux 2007.1 Networkless Handbooks. These handbooks are
released together with the Gentoo Linux releases and contain the necessary
installation instructions to install Gentoo Linux 2007.1 <brite>without an
internet connection.</brite>
</p>

<p>
However, if you want to install Gentoo Linux using the latest versions of all
available packages, please use the Installation Instructions in the <uri
link="/doc/en/handbook/">Gentoo Linux Handbook</uri> for your architecture.
</p>

</body>
</section>
</chapter>
<chapter>
<title>View the Handbook</title>
<section>
<body>

<table>
<tr>
  <th>Format</th>
  <th>Description</th>
  <th>Links</th>
</tr>
<tr>
  <ti>HTML</ti>
  <ti>One page per chapter, perfect for online viewing</ti>
  <ti>
    <uri link="handbook-x86.xml">x86</uri>, 
    <uri link="handbook-sparc.xml">sparc</uri>,
    <uri link="handbook-amd64.xml">amd64</uri>, 
    <uri link="handbook-ppc.xml">ppc</uri>, 
    <uri link="handbook-ppc64.xml">ppc64</uri>, 
    <uri link="handbook-hppa.xml">hppa</uri>
  </ti>
</tr>
<tr>
  <ti>HTML</ti>
  <ti>All in one page</ti>
  <ti>
    <uri link="handbook-x86.xml?full=1">x86</uri>, 
    <uri link="handbook-sparc.xml?full=1">sparc</uri>,
    <uri link="handbook-amd64.xml?full=1">amd64</uri>, 
    <uri link="handbook-ppc.xml?full=1">ppc</uri>, 
    <uri link="handbook-ppc64.xml?full=1">ppc64</uri>, 
    <uri link="handbook-hppa.xml?full=1">hppa</uri>
  </ti>
</tr>
<tr>
  <ti>HTML</ti>
  <ti>All in one page, printable version</ti>
  <ti>
    <uri link="handbook-x86.xml?style=printable&amp;full=1">x86</uri>, 
    <uri link="handbook-sparc.xml?style=printable&amp;full=1">sparc</uri>,
    <uri link="handbook-amd64.xml?style=printable&amp;full=1">amd64</uri>, 
    <uri link="handbook-ppc.xml?style=printable&amp;full=1">ppc</uri>, 
    <uri link="handbook-ppc64.xml?style=printable&amp;full=1">ppc64</uri>, 
    <uri link="handbook-hppa.xml?style=printable&amp;full=1">hppa</uri>
  </ti>
</tr>
</table>

</body>
</section>
</chapter>
</guide>



-- 
gentoo-doc-cvs@l.g.o mailing list