[gentoo-doc-cvs] cvs commit: handbook-alpha.xml

[swift]

swift       05/08/08 13:16:10

  Added:       xml/htdocs/doc/en/handbook/2005.1 handbook-alpha.xml
                        handbook-amd64.xml handbook-hppa.xml
                        handbook-ppc.xml handbook-sparc.xml
                        handbook-x86.xml hb-install-about.xml
                        hb-install-alpha-bootloader.xml
                        hb-install-alpha-disk.xml
                        hb-install-alpha-kernel.xml
                        hb-install-alpha-medium.xml
                        hb-install-amd64-bootloader.xml
                        hb-install-amd64-disk.xml
                        hb-install-amd64-kernel.xml
                        hb-install-amd64-medium.xml hb-install-config.xml
                        hb-install-finalise.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-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
                        hb-install-x86-bootloader.xml
                        hb-install-x86-disk.xml hb-install-x86-kernel.xml
                        hb-install-x86-medium.xml index.xml
  Log:
  Adding 2005.0 (yes, .0) as a plain copy (makes it easier for translators to update

Revision  Changes    Path
1.1                  xml/htdocs/doc/en/handbook/2005.1/handbook-alpha.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-alpha.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-alpha.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/handbook-alpha.xml,v 1.1 2005/08/08 13:16:09 swift Exp $ -->

<book link="handbook-alpha.xml">
<title>Gentoo Linux 2005.0 Alpha Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</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="Reviewer">
    <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="spyderous@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 Handbook, an effort to centralise Gentoo/Linux
information.
</abstract>

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

<version>4.1</version>
<date>2005-06-09</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-alpha-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-alpha-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-alpha-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"/>



1.1                  xml/htdocs/doc/en/handbook/2005.1/handbook-amd64.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-amd64.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-amd64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/handbook-amd64.xml,v 1.1 2005/08/08 13:16:09 swift Exp $ -->

<book link="handbook-amd64.xml">
<title>Gentoo Linux 2005.0 AMD64 Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</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="Reviewer">
    <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="spyderous@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 Handbook, an effort to centralise Gentoo/Linux
information.
</abstract>

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

<version>4.1</version>
<date>2005-06-09</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-amd64-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-amd64-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-amd64-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"/>



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-hppa.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-hppa.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/handbook-hppa.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<book link="handbook-hppa.xml">
<title>Gentoo Linux 2005.0 HPPA Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</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="Reviewer">
    <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="spyderous@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 Handbook, an effort to centralise Gentoo/Linux
information.
</abstract>

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

<version>4.1</version>
<date>2005-06-09</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"/>



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/handbook-ppc.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<book link="handbook-ppc.xml">
<title>Gentoo Linux 2005.0 PPC Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</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="Reviewer">
    <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="spyderous@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>

<abstract>
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux
information.
</abstract>

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

<version>4.1</version>
<date>2005-06-09</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



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-sparc.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-sparc.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/handbook-sparc.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<book link="handbook-sparc.xml">
<title>Gentoo Linux 2005.0 SPARC Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</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="Reviewer">
    <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="spyderous@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 Handbook, an effort to centralise Gentoo/Linux
information.
</abstract>

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

<version>4.1</version>
<date>2005-06-09</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"/>



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-x86.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-x86.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/handbook-x86.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<book link="handbook-x86.xml">
<title>Gentoo Linux 2005.0 x86 Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</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="Reviewer">
    <mail link="g2boojum@g.o">Grant Goodyear</mail>
</author>
<author title="Reviewer">
    <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
    <mail link="spyderous@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 Handbook, an effort to centralise Gentoo/Linux
information.
</abstract>

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

<version>4.1</version>
<date>2005-06-09</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-x86-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-x86-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-x86-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"/>



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-about.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-about.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-about.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.1</version>
<date>2005-03-28</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 choices and performance. Gentoo is all about choices. 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 metadistribution 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 textfiles. In other words,
openness everywhere.
</p>

<p>
It is very important that you understand that <e>choices</e> are what
makes Gentoo run. We try not to force you onto anything you don't like.
If you feel like we do, please <uri
link="http://bugs.gentoo.org">bugreport</uri> it.
</p>

</body>
</subsection>
<subsection>
<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 the Universal Installation CD, a 
bootable CD that contains everything you need to get Gentoo Linux up and 
running. You can optionally use one of our Package CDs as well to install a 
complete system in a matter of minutes after having installed the Gentoo base 
system.
</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">bugtracking
system</uri> and check if the bug is known. If not, please create a bugreport 
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>




1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-alpha-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-bootloader.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.1</version>
<date>2005-03-29</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>
Several bootloaders exist for Linux/Alpha. You must choose one of the supported
bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri>
and <uri link="#milo">MILO</uri>.
</p>

</body>
</subsection>
</section>
<section id="aboot">
<title>Default: Using aboot</title>
<body>

<p>
We first install aboot on our system. Of course we use <c>emerge</c> to
do so:
</p>

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

<p>
The next step is to make our bootdisk bootable. This will start
<c>aboot</c> when you boot your system. We make our bootdisk bootable by
writing the <c>aboot</c> bootloader to the start of the disk.
</p>

<pre caption = "Making your bootdisk bootable">
# <i>swriteboot -f3 /dev/sda /boot/bootlx</i> 
# <i>abootconf /dev/sda 2</i>
</pre>

<note>
If you use a different partitioning scheme than the one we use
throughout this chapter, you have to change the commands accordingly.
Please read the appropriate manual pages (<c>man 8 swriteboot</c> and
<c>man 8 abootconf</c>). Also, if your root filesystem uses the JFS filesystem,
make sure to pass the <c>ro</c> kernel option so that it can replay its log
before it gets mounted read-write.
</note>

<p>
Additionally, you can make Gentoo boot automatically by setting up the 
aboot configuration file and some SRM variables.  You can try setting 
these variables from Linux, but it may be easier to do so from the SRM 
console itself.
</p>

<pre caption = "Automatically booting Gentoo">
# <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' &gt; /etc/aboot.conf</i>
# <i>cd /proc/srm_environment/named_variables</i>
# <i>echo -n 0 &gt; boot_osflags</i>
# <i>echo -n '' &gt; boot_file</i>
# <i>echo -n 'BOOT' &gt; auto_action</i>
# <i>echo -n 'dkc100' &gt; bootdef_dev</i>
<comment>(Substitute dkc100 with whatever your boot device is)</comment>
</pre>

<p>
If you need to get into the SRM console again in the future (to recover 
your Gentoo install, play with some variables, or whatever), just hit 
CTRL+C to abort the automatic loading process.
</p>

<p>
If you're installing using a serial console, don't forget to include 
the serial console boot flag in <path>aboot.conf</path>.  See  
<path>/etc/aboot.conf.example</path> for some further information.
</p>

<p>
Aboot is now configured and ready to use. Continue with <uri
link="#reboot">Rebooting the System</uri>.
</p>

</body>
</section>
<section id="milo">
<title>Alternative: Using MILO</title>
<body>

<p>
Before continuing, you should decide on how to use MILO. In this
section, we will assume that you want to make a MILO boot floppy. If you
are going to boot from an MS-DOS partition on your hard disk, you should
amend the commands appropriately.
</p>

<p>
To install MILO, we use <c>emerge</c>.
</p>

<pre caption = "Installing MILO">
# <i>emerge --usepkg milo</i>
</pre>

<p>
After MILO has been installed, the MILO images should be in
<path>/opt/milo</path>. The commands below make a bootfloppy for use
with MILO. Remember to use the correct image for your Alpha-system.
</p>

<pre caption = "Installing MILO on a floppy">
<comment>(First insert a blank floppy)</comment>
# <i>fdformat /dev/fd0</i>
# <i>mformat a:</i>
# <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i>
# <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i>
<comment>(Only if you have a Ruffian:</comment>     
  # <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
<comment>)</comment>
# <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i>
</pre>

<p>
Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
set environment variables in your ARCS Firmware to get MILO to start;
this is all explained in the <uri
link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples 
on common systems, and examples of the commands to use in interactive mode.
</p>

<p>
Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> 
is a <e>bad</e> idea.
</p>

<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/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/2005.1/hb-install-alpha-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-alpha-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/2005.1/hb-install-alpha-disk.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-08-02</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>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 Alpha systems,
these are called <e>slices</e>. 
</p>

</body>
</subsection>
</section>
<section>
<title>Designing a Partitioning Scheme</title>
<subsection>
<title>Default Partitioning Scheme</title>
<body>

<p>
As an example we use the following slice layout:
</p>

<table>
<tr>
  <th>Slice</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/sda1</path></ti>
  <ti>Swap slice</ti>
</tr>
<tr>
  <ti><path>/dev/sda2</path></ti>
  <ti>Root slice</ti>
</tr>
<tr>
  <ti><path>/dev/sda3</path></ti>
  <ti>Full disk (required)</ti>
</tr>
</table>


<p>
If you are interested in knowing how big a partition should be, or even how 
many partitions (or volumes) you need, read on. Otherwise continue now with
<uri link="#fdisk_SRM">Using fdisk to Partition your Disk (SRM only)</uri> 
or <uri link="#fdisk_ARC">Using fdisk to Partition your Disk (ARC/AlphaBIOS 
only)</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.
</p>

</body>
</subsection>
</section>
<section id="fdisk_SRM">
<title>Using fdisk to Partition your Disk (SRM only)</title>
<subsection>
<body>

<p>
The following parts explain how to create the example slice layout described
previously, namely:
</p>

<table>
<tr>
  <th>Slice</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/sda1</path></ti>
  <ti>Swap slice</ti>
</tr>
<tr>
  <ti><path>/dev/sda2</path></ti>
  <ti>Root slice</ti>
</tr>
<tr>
  <ti><path>/dev/sda3</path></ti>
  <ti>Full disk (required)</ti>
</tr>
</table>

<p>
Change your slice layout according to your own preference.
</p>


</body>
</subsection>
<subsection>
<title>Identifying Available Disks</title>
<body>

<p>
To figure out what disks you have running, use the following commands:
</p>

<pre caption="Identifying available disks">
# <i>dmesg | grep 'drive$'</i>        <comment>(For IDE disks)</comment>
# <i>dmesg | grep 'scsi'</i>          <comment>(For SCSI disks)</comment>
</pre>

<p>
>From this output you should be able to see what disks were detected and their



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-alpha-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-kernel.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.6</version>
<date>2005-07-04</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 make a
symlink to <path>/etc/localtime</path> using <c>ln</c>:
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>ln -sf /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 alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel source).
</p>

<p>
Choose your kernel source and install it using <c>emerge</c>. 
</p>

<p>
In the next example we install the <c>vanilla-sources</c>.
Of course substitute with your choice of sources, this is merely an example:
</p>

<pre caption="Installing a kernel source">
# <i>emerge vanilla-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:
</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-2.6.11.2
</pre>

<p>
If this isn't the case (i.e. the symlink points to a different kernel source) 
change the symlink before you continue:
</p>

<pre caption="Changing the kernel source symlink">
# <i>rm /usr/src/linux</i>
# <i>cd /usr/src</i>
# <i>ln -s linux-2.6.11.2 linux</i>
</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 
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. You can 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">
Code maturity level options ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
General setup ---&gt;
  [*] Support for hot-pluggable devices
</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>, (<c>/dev file system</c> + <c>Automatically mount at boot</c> only for 2.4 kernel):
</p>

<pre caption="Selecting necessary file systems">
<comment>(With a 2.4.x kernel)</comment>
File systems ---&gt;
  [*] Virtual memory file system support (former shm fs)
  [*] /proc file system support
  [*] /dev file system support (EXPERIMENTAL)
  [*]   Automatically mount at boot
  [ ] /dev/pts file system for Unix98 PTYs

<comment>(With a 2.6.x kernel)</comment>
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [ ] /dev file system support (OBSOLETE)
    [*] 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">
<comment>(With a 2.4.x kernel)</comment>
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

<comment>(With a 2.6.x kernel)</comment>
Device Drivers ---&gt;
  Networking support ---&gt;



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-alpha-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-alpha-medium.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.3</version>
<date>2005-08-01</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>
    Please check with the <uri
    link="http://www.alphalinux.org/faq/FAQ-5.html">Alpha/Linux FAQ</uri>
  </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>
<!-- Copy/paste from the hb-install-x86-medium.xml file but no Universal
     Installation CD.
     Also s/x86/alpha -->
<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
A stage file is a tarball (compressed archive) that contains a minimal
environment.
</p>

<ul>
  <li>
     A stage1 file contains nothing more than a compiler, Portage (Gentoo's
     software management system) and a couple of packages on which the compiler
     or Portage depends.
   </li>
   <li>
     A stage2 file contains a so-called bootstrapped system, a minimal
     environment from which one can start building all other necessary
     applications that make a Gentoo environment complete.
   </li>
   <li>
     A stage3 file contains a prebuilt minimal system which is almost fully
     deployable. It only lacks a few applications where you, the Gentoo user,
     needs to choose which one you want to install.
   </li>
</ul>

<p>
We will opt for a stage3 installation throughout this document. If you want to
perform a Gentoo installation using the stage1 or stage2 files, please use the
installation instructions in the <uri
link="/doc/en/handbook/handbook-alpha.xml">Gentoo Handbook</uri>. They do
require a working Internet connection though.
</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 no Installation CD but an additional 
resource that you can exploit during the installation of your Gentoo system. It
contains prebuilt packages (the so-called GRP set) that allows 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 CD is located in 
the <path>releases/alpha/2005.0/installcd</path> directory;
the Package CD is located in the <path>releases/alpha/2005.0/packagecd</path>
directory.
</p>

<p>
Inside those directories you'll find so-called 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 pgp.mit.edu --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>




1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-amd64-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-bootloader.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.6</version>
<date>2005-06-10</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>
<subsection>
<title>Optional: Framebuffer</title>
<body>

<!--
Verbatim copy from x86 bootloader framebuffer explanation, minus the section on
vesafb-tng
-->

<p>
<e>If</e> you have configured your kernel with framebuffer support (or you used
<c>genkernel</c>'s default kernel configuration), you can activate it by adding
a <c>vga</c> and/or a <c>video</c> statement to your bootloader configuration 
file.
</p>

<p>
64-bit systems must use the the <c>vesafb</c> driver, and so will need to set
the <c>vga</c> statement. The <c>vga</c> statement controls the resolution and
color depth of your framebuffer screen for <c>vesafb</c>. As stated in
<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed
when you install a kernel source package), you need to pass the VESA number 
corresponding to the requested resolution and color depth to it.
</p>

<p>
The following table lists the available resolutions and colordepths and matches
those against the value that you need to pass on to the <c>vga</c> statement.
</p>

<table>
<tr>
  <ti></ti>
  <th>640x480</th>
  <th>800x600</th>
  <th>1024x768</th>
  <th>1280x1024</th>
</tr>
<tr>
  <th>256</th>
  <ti>0x301</ti>
  <ti>0x303</ti>
  <ti>0x305</ti>
  <ti>0x307</ti>
</tr>
<tr>
  <th>32k</th>
  <ti>0x310</ti>
  <ti>0x313</ti>
  <ti>0x316</ti>
  <ti>0x319</ti>
</tr>
<tr>
  <th>64k</th>
  <ti>0x311</ti>
  <ti>0x314</ti>
  <ti>0x317</ti>
  <ti>0x31A</ti>
</tr>
<tr>
  <th>16M</th>
  <ti>0x312</ti>
  <ti>0x315</ti>
  <ti>0x318</ti>
  <ti>0x31B</ti>
</tr>
</table>

<p>
The <c>video</c> statement controls framebuffer display options. It needs to be
given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for
2.4 kernels) followed by the control statements you wish to enable. All
variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>,
but we'll inform you about three most-used options:
</p>

<table>
<tr>
  <th>Control</th>
  <th>Description</th>
</tr>
<tr>
  <ti>ywrap</ti>
  <ti>
    Assume that the graphical card can wrap around its memory (i.e. continue at
    the beginning when it has approached the end)
  </ti>
</tr>
<tr>
  <ti>mtrr</ti>
  <ti>
    Setup MTRR registers
  </ti>
</tr>
</table>

<p>
The result of those two statements could be something like <c>vga=0x318
video=vesafb:mtrr,ywrap</c> or <c>video=vesafb:mtrr,ywrap,1024x768-32@85</c>. 
Remember (or write down) this setting; you will need it shortly.
</p>

<p>
Now continue by installing GRUB.
</p>

</body>
</subsection>
</section>
<section>
<title>Using GRUB</title>
<subsection>
<title>Understanding GRUB's terminology</title>
<body>

<p>
The most critical part of understanding GRUB is getting comfortable with
how GRUB refers to hard drives and partitions. Your Linux partition
<path>/dev/hda1</path> will most likely be called <path>(hd0,0)</path> under 
GRUB. Notice the parenthesis around the <path>hd0,0</path> - they are required.
</p>

<p>
Hard drives count from zero rather than "a" and partitions start at zero 
rather than one. Be aware too that with the hd devices, only hard drives are 
counted, not atapi-ide devices such as cdrom players and burners.  Also, the 
same construct is used with scsi drives. (Normally they get higher numbers 
than ide drives except when the bios is configured to boot from scsi devices.)
When you ask the BIOS to boot from a different hard disk (for instance your
primary slave), <e>that</e> harddisk is seen as <path>hd0</path>.
</p>

<p>
Assuming you have a hard drive on <path>/dev/hda</path>, a cdrom player on 
<path>/dev/hdb</path>, a burner on <path>/dev/hdc</path>, a second hard drive 
on <path>/dev/hdd</path> and no SCSI hard drive, <path>/dev/hdd7</path> gets 
translated to <path>(hd1,6)</path>. It might sound tricky and tricky it is 
indeed, but as we will see, GRUB offers a tab completion mechanism
that comes handy for those of you having a lot of hard drives and
partitions and who are a little lost in the GRUB numbering scheme.
</p>

<p>
Having gotten the feel for that, it is time to install GRUB.
</p>

</body>
</subsection>
<subsection>
<title>Installing GRUB</title>
<body>

<p>
To install GRUB, let's first emerge it. 
</p>

<pre caption = "Installing GRUB">
# <i>emerge grub</i>
</pre>

<p>
Although GRUB is now installed, we still need to write up a
configuration file for it and install GRUB in the MBR so that GRUB 
automatically boots your newly created kernel. Create 
<path>/boot/grub/grub.conf</path> with <c>nano</c> (or, if applicable, another 
editor):
</p>

<pre caption = "Creating /boot/grub/grub.conf">
# <i>nano -w /boot/grub/grub.conf</i>
</pre>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-amd64-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/2005.1/hb-install-amd64-disk.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-08-02</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>.
</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 amd64 systems,
these are called <e>partitions</e>. 
</p>

</body>
</subsection>
<subsection>
<title>Partitions</title>
<body>

<p>
Partitions are divided in three types:
<e>primary</e>, <e>extended</e> and <e>logical</e>.
</p>

<p>
A <e>primary</e> partition is a partition which has its information stored in
the MBR (master boot record). As an MBR is very small (512 bytes) only four
primary partitions can be defined (for instance, <path>/dev/hda1</path> to
<path>/dev/hda4</path>).
</p>

<p>
An <e>extended</e> partition is a special primary partition (meaning the
extended partition must be one of the four possible primary partitions) which
contains more partitions. Such a partition didn't exist originally, but as
four partitions were too few, it was brought to life to extend the formatting
scheme without losing backward compatibility.
</p>

<p>
A <e>logical</e> partition is a partition inside the extended partition. Their
definitions aren't placed inside the MBR, but are declared inside the extended
partition.
</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/hda1</path></ti>
  <ti>ext2</ti>
  <ti>32M</ti>
  <ti>Boot partition</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>(swap)</ti>
  <ti>512M</ti>
  <ti>Swap partition</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti>ext3</ti>
  <ti>Rest of the disk</ti>
  <ti>Root partition</ti>
</tr>
</table>

<p>
If you are interested in knowing how big a partition (or logical 
volume) should be, or even how many partitions (or volumes) you need, read on. 
Otherwise continue with <uri link="#fdisk">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>

<p>
As an example partitioning, we show you one for a 20GB disk, used as a
demonstration laptop (containing webserver, mailserver, gnome, ...):
</p>

<pre caption="Filesystem usage example">
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/hda5     ext3    509M  132M  351M  28% /
/dev/hda2     ext3    5.0G  3.0G  1.8G  63% /home
/dev/hda7     ext3    7.9G  6.2G  1.3G  83% /usr
/dev/hda8     ext3   1011M  483M  477M  51% /opt
/dev/hda9     ext3    2.0G  607M  1.3G  32% /var
/dev/hda1     ext2     51M   17M   31M  36% /boot



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-amd64-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-kernel.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.8</version>
<date>2005-07-04</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 make a
symlink to <path>/etc/localtime</path> using <c>ln</c>:
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>ln -sf /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 AMD64-based systems we have <c>gentoo-sources</c> (kernel v2.6 source
patched with amd64 specific fixes for stability, performance and hardware
support). 
</p>

<p>
Choose your kernel source and install it using <c>emerge</c>. 
</p>

<note>
Running <c>emerge gentoo-sources</c> will fail due to a bug with the Universal
Installation CD. Please make sure you run <c>emerge
=gentoo-sources-2.6.11-r1</c> instead. This has no further effect on your
environment as Portage will automatically download a more recent kernel source 
when updating your system (after the installation).
</note>

<pre caption="Installing a kernel source">
# <i>echo "=sys-kernel/gentoo-sources-2.6.11-r1 ~amd64" &gt;&gt; /etc/portage/package.keywords</i>
# <i>emerge =gentoo-sources-2.6.11-r1</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:
</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-2.6.11-gentoo-r1
</pre>

<p>
If this isn't the case (i.e. the symlink points to a different kernel source) 
change the symlink before you continue:
</p>

<pre caption="Changing the kernel source symlink">
# <i>rm /usr/src/linux</i>
# <i>cd /usr/src</i>
# <i>ln -s linux-2.6.11-gentoo-r1 linux</i>
</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 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">
Code maturity level options ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
General setup ---&gt;
  [*] Support for hot-pluggable devices
</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>. Do <e>not</e> select <c>/dev file system</c> since 2005.0/AMD64
uses <c>udev</c> by default.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    &lt;*&gt; /proc file system support
    &lt; &gt; /dev file system support (OBSOLETE)
    &lt;*&gt; 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



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-amd64-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-amd64-medium.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.21</version>
<date>2005-05-06</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 AMD64 CPU *</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>

<note>
* Intel processors with EM64T extensions <e>might</e> work as well, but are
untested.
</note>

<p>
You should check the <uri link="http://amd64.gentoo.org">Gentoo
AMD64 Project Page</uri> before proceeding.
</p>

</body>
</subsection>
</section>
<!-- Copy/paste from hb-install-x86-medium.xml (with s/x86/amd64/) -->
<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. A
stage file is a tarball (compressed archive) that contains a minimal
environment.
</p>

<ul>
  <li>
    A stage1 file contains nothing more than a compiler, Portage (Gentoo's
    software management system) and a couple of packages on which the 
    compiler or Portage depends. 
  </li>
  <li>
    A stage2 file contains a so-called bootstrapped system, a minimal
    environment from which one can start building all other necessary 
    applications that make a Gentoo environment complete.
  </li>
  <li>
    A stage3 file contains a prebuilt minimal system which is almost fully
    deployable. It only lacks a few applications where you, the Gentoo user, 
    needs to choose which one you want to install.
  </li>
</ul>

<p>
We will opt for a stage3 installation throughout this document. If you want to
perform a Gentoo installation using the stage1 or stage2 files, please use the
installation instructions in the <uri
link="/doc/en/handbook/handbook-amd64.xml">Gentoo Handbook</uri>. They do
require a working Internet connection though.
</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 no Installation CD but an additional 
resource that you can exploit during the installation of your Gentoo system. It
contains prebuilt packages (the so-called GRP set) that allows 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 CD is located in 
the <path>releases/amd64/2005.0/installcd</path> directory;
the Package CD is located in the <path>releases/amd64/2005.0/packagecd</path>
directory.
</p>

<p>
Inside those directories you'll find so-called 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 pgp.mit.edu --recv-keys 17072058</i>
</pre>

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



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-config.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-config.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-config.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-05-23</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>

<p>
The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
file</e>, so start <c>nano</c> (or your favorite editor) to create your 
<path>/etc/fstab</path>:
</p>

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

<p>
Let us take a look at how we write down the options for the <path>/boot</path>
partition. This is just an example, so if your architecture doesn't require a
<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
</p>

<p>
In our default x86 partitioning example <path>/boot</path> is the
<path>/dev/hda1</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">
/dev/hda1   /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>

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

<pre caption="An improved /boot line for /etc/fstab">
/dev/hda1   /boot     ext2    defaults,noatime    1 2
</pre>

<p>
If we continue with this, we would end up with the following three lines (for
<path>/boot</path>, <path>/</path> and the swap partition):
</p>

<pre caption="Three /etc/fstab lines">
/dev/hda1   /boot     ext2    defaults,noatime  1 2
/dev/hda2   none      swap    sw                0 0
/dev/hda3   /         ext3    noatime           0 1
</pre>

<p>
To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
(required) and for your CD-ROM drive (and of course, if you have other 
partitions or drives, for those too):
</p>

<pre caption="A full /etc/fstab example">
/dev/hda1   /boot     ext2    defaults,noatime     1 2
/dev/hda2   none      swap    sw                   0 0
/dev/hda3   /         ext3    noatime              0 1

none        /proc     proc    defaults             0 0
none        /dev/shm  tmpfs   nodev,nosuid,noexec  0 0

/dev/cdroms/cdrom0    /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>
Now use the above example to create your <path>/etc/fstab</path>. If you are a
<b>SPARC</b>-user, you should add the following line to your 
<path>/etc/fstab</path>
too:
</p>

<pre caption="Adding openprom filesystem to /etc/fstab">
none        /proc/openprom  openpromfs    defaults      0 0
</pre>

<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>echo tux &gt; /etc/hostname</i>
</pre>

<p>
Second we set the domainname:
</p>

<pre caption="Setting the domainname">
# <i>echo homenetwork &gt; /etc/dnsdomainname</i>
</pre>

<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>




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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-finalise.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-finalise.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-finalise.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.00</version>
<date>2005-03-21</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>usb</ti>
  <ti>be able to access USB devices</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:
</p>

<pre caption="Installing KDE">
# <i>emerge --usepkg 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/2005.1/hb-install-hppa-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-bootloader.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.00</version>
<date>2004-09-24</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/vmlinux root=/dev/sdb2 HOME=/
--recoverykernel=/vmlinux.old
--init-partitioned=/dev/sdb
</pre>

<p>
The first line tells palo the location of the kernel and which boot
parameters it must use. <c>2/vmlinux</c> means the kernel named <c>/vmlinux</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/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/2005.1/hb-install-hppa-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/hb-install-hppa-disk.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-08-02</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 



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-kernel.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.3</version>
<date>2005-06-09</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 make a
symlink to <path>/etc/localtime</path> using <c>ln</c>:
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>ln -sf /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>. Default these sources are based on
the 2.6 kernel sources. If you want to install a 2.4 kernel, you will need
to install Gentoo from a working Internet connection as we do not supply those
sources on our Installation CD. Continue by installing the kernel source:
</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:
</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-2.6.10_p11
</pre>

<p>
If this isn't the case (i.e. the symlink points to a different kernel source) 
change the symlink before you continue:
</p>

<pre caption="Changing the kernel source symlink">
# <i>rm /usr/src/linux</i>
# <i>cd /usr/src</i>
# <i>ln -s linux-2.6.10_p11 linux</i>
</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">
Code maturity level options ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
General setup --->
  [*] Support for hot-pluggable devices
</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>, <c>/dev file system</c> + <c>Automatically mount at boot</c>:
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [*] /dev file system support (OBSOLETE)
    [*]   Automatically mount at boot
    [*] 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>rp-pppoe</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>




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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-hppa-medium.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-05-24</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>.
</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>
<!-- Copy/paste from hb-install-x86-medium.xml -->
<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. A
stage file is a tarball (compressed archive) that contains a minimal
environment.
</p>

<ul>
  <li>
    A stage1 file contains nothing more than a compiler, Portage (Gentoo's
    software management system) and a couple of packages on which the 
    compiler or Portage depends. 
  </li>
  <li>
    A stage2 file contains a so-called bootstrapped system, a minimal
    environment from which one can start building all other necessary 
    applications that make a Gentoo environment complete.
  </li>
  <li>
    A stage3 file contains a prebuilt minimal system which is almost fully
    deployable. It only lacks a few applications where you, the Gentoo user, 
    needs to choose which one you want to install.
  </li>
</ul>

<p>
We will opt for a stage3 installation throughout this document. If you want to
perform a Gentoo installation using the stage1 or stage2 files, please use the
installation instructions in the <uri
link="/doc/en/handbook/handbook-hppa.xml">Gentoo Handbook</uri>. They do
require a working Internet connection though.
</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 no Installation CD but an additional 
resource that you can exploit during the installation of your Gentoo system. It
contains prebuilt packages (the so-called GRP set) that allows 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 CD is located in 
the <path>releases/hppa/2005.0/installcd</path> directory;
the Package CD is located in the <path>releases/hppa/2005.0/packagecd</path>
directory.
</p>

<p>
Inside those directories you'll find so-called 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 pgp.mit.edu --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



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-network.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-network.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-network.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.1</version>
<date>2005-07-28</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
the Universal Installation CD. 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 Installation CD do 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 Installation 
    CD but is supported by the Installation CD (i.e. you can connect to the 
    Internet using the Installation CD but the necessary sources are not 
    available on the Installation 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, 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>
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 Proxy</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 <e>proxy.gentoo.org</e> and the port
is 8080.
</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 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.yahoo.com</i>
</pre>

<p>
Are you able to use your network? If so, you can skip the rest of this
section and continue with <uri link="?part=1&amp;chap=4">Preparing the
Disks</uri>. If not, bad luck, you'll have to work on it a bit more.
</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>adsl-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_chap4">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="#rp-pppoe">Alternative:
    Using RP-PPPoE</uri>
  </li>
  <li>
    PPTP users should continue with <uri link="#pptp">Alternative:
    Using PPTP</uri> (x86 only)
  </li>
</ul>




1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-next.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-next.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-next.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-next.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-06-09</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&amp;chap=0">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>.
</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 2005.0</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>
The following changes need to happen right after having updated your system (and
before rebooting):
</p>

<ul>
  <li>
    The <c>baselayout</c> package has received major updates, including on the
    <uri link="?part=4">Gentoo Network Configuration</uri> aspect. The changes
    include a new syntax for the <path>/etc/conf.d/net</path> file although the
    old syntax is still supported. You are advised to change to the new one in
    time.
  </li>
</ul>

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



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-bootloader.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.00</version>
<date>2005-03-19</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>. But before you start, consider
your options...
</p>

<p>
Several bootloaders exist for Linux/PPC. We have <uri link="#yaboot">yaboot</uri>
(for NewWorld Apple and IBM machines) and <uri link="#bootx">BootX</uri> (for 
OldWorld Apple and IBM machines). The Pegasos does not require a bootloader, but
we included the <uri link="#bootcreator">BootCreator</uri> for creating a
SmartFirmware bootmenu.
</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>
First we have to create the <path>/dev</path> files in our new home, which is
needed during the bootloader installation.  This could be done by "bind"-mapping
the <path>/dev</path>-filesystem from the Installation CD:
</p>

<pre caption="Bind-mounting the /dev-filesystem">
# <i>exit </i> # this will exit the chroot
# <i>mount -o bind /dev /mnt/gentoo/dev</i>
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
</pre>

<p>
There are two ways to configure yaboot for your system. You can use the
included <c>yabootconfig</c> 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>

<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 with your Linux partitions. Both
of these should have been done already in the steps above. To start, ensure that
you have the latest <c>yaboot</c> installed.
</p>

<pre caption = "Installing yaboot with GRP">
# <i>emerge --usepkg --update yaboot</i>
</pre>

<p>
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</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 Apple_Bootstrap partition, and install the yaboot
configuration file into it.  After this enter the chroot again.
</p>
<pre caption="enter chroot">
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i>
</pre>

<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 Apple_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 make sure you have the latest <c>yaboot</c> installed on your
system:
</p>

<pre caption = "Installing yaboot">
# <i>emerge --usepkg --update yaboot</i>
</pre>

<p>
Below you find a completed <path>yaboot.conf</path> file. Alter it at
will. G5 users should be aware that their disks are Serial ATA disks which are
seen as SCSI disks by the Linux kernel (so 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

## our bootstrap partition:</comment>

boot=/dev/hda2

<comment>## ofboot is the openfirmware 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

## 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 2.6.9 with your kernel-version
#################</comment>
image=/boot/kernel-2.6.9
  label=Linux
  root=/dev/hda3
  partition=3
  sysmap=/boot/System.map-2.6.9
  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>




1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/hb-install-ppc-disk.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-08-02</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 or SATA drives, then your first
hard drive would be <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>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 NewWorld</th>
  <th>Partition OldWorld</th>
  <th>Partition Pegasos</th>
  <th>Partition RS/6000</th>
  <th>Filesystem</th>
  <th>Size</th>
  <th>Description</th>
</tr>
<tr>
  <ti><path>/dev/hda1</path></ti>
  <ti><path>/dev/hda1</path></ti>
  <ti>(Not applicable)</ti>
  <ti>(Not applicable)</ti>
  <ti>(Partition Map)</ti>
  <ti>32k</ti>
  <ti>Apple_partition_map</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>(Not needed)</ti>
  <ti>(Not applicable)</ti>
  <ti>(Not applicable)</ti>
  <ti>(bootstrap)</ti>
  <ti>800k</ti>
  <ti>Apple_Bootstrap</ti>
</tr>
<tr>
  <ti>(Not applicable</ti>
  <ti>(Not applicable)</ti>
  <ti>(Not applicable)</ti>
  <ti><path>/dev/sda1</path></ti>
  <ti>(PReP Boot)</ti>
  <ti>800k</ti>
  <ti>Type 0x41</ti>
</tr>
<tr>
  <ti>(Not needed)</ti>
  <ti>(Not needed)</ti>
  <ti><path>/dev/hda1</path></ti>
  <ti>(Not needed)</ti>
  <ti>ext2</ti>
  <ti>32MB</ti>
  <ti>Boot partition</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti><path>/dev/hda2</path></ti>
  <ti><path>/dev/hda2</path></ti>
  <ti><path>/dev/sda2</path></ti>
  <ti>(swap)</ti>
  <ti>512M</ti>
  <ti>Swap partition, Type 0x82</ti>
</tr>
<tr>
  <ti><path>/dev/hda4</path></ti>
  <ti><path>/dev/hda3</path></ti>
  <ti><path>/dev/hda3</path></ti>
  <ti><path>/dev/sda3</path></ti>
  <ti>ext3, xfs</ti>
  <ti>Rest of the disk</ti>
  <ti>Root partition, Type 0x83</ti>
</tr>
</table>

<note>
There are some partitions named like this: <path>Apple_Driver43,
Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, 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 <c>parted</c> in order to delete
them, as mac-fdisk can't delete them yet.
</note>

<warn>
<c>parted</c> is able to resize partitions.  On the Installation CD there 
are patches included to resize HFS+ filesystem.  Unfortunately it is not 
possible to resize HFS+ journaled filesystems, even if the journaling has been 
switchedoff in Mac OS X.  Everything you do with resizing in parted you do it 
on your own risk!  Be sure to have a backup of your data!
</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="#fdisk">Default: Using mac-fdisk (Apple/IBM) to Partition your Disk</uri>
or <uri link="#parted">Alternative: Using parted (especially 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 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>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-kernel.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.9</version>
<date>2005-07-04</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 make a
symlink to <path>/etc/localtime</path> using <c>ln</c>:
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>ln -sf /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 PPC you can choose between <c>vanilla-sources</c> and
<c>gentoo-sources</c> (both 2.6 kernels). The latter is available when you
perform a networkless installation.  Beside those there is a special
kernel-2.6-patchset for the Pegasos: <c>pegasos-sources</c>.  So let's
continue with <c>emerge</c>'ing the kernel sources:
</p>

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

<note>
The PowerPC sources are based on a 2.6.10-kernel with security patches from
2.6.11 backported.  As the time of the release the 2.6.11 kernel produced
several problems on different PowerPC machines.
</note>

<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. We will assume the kernel
source installed is <c>gentoo-sources-2.6.10-r8</c>:
</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-2.6.10-gentoo-r8
</pre>

<p>
If the symlink doesn't point to the kernel source of your choice (note that
<c>linux-2.6.10-gentoo-r8</c> is merely an example) you should change it to the
right kernel:
</p>

<pre caption="Changing the kernel source symlink">
# <i>rm /usr/src/linux</i>
# <i>cd /usr/src</i>
# <i>ln -s linux-2.6.10-gentoo-r8 linux</i>
</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 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">
Code maturity level options ---&gt;
  [*] Prompt for development and/or incomplete code/drivers
General setup --->
  [*] Support for hot-pluggable devices
</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>/proc file system</c> and
<c>Virtual memory</c>. Do <e>not</e> select the <c>/dev file system</c>.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [ ] /dev file system support (OBSOLETE)
    [*] 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; 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>rp-pppoe</c> when configured to do kernel mode PPPoE.



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc-medium.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.01</version>
<date>2005-05-06</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>NewWorld machines</th>
  <ti>
    Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook
    PowerBook, Xserver, PowerMac, Genesi's Pegasos II
  </ti>
</tr>
<tr>
  <th>OldWorld machines</th>
  <ti>
    Limited support for IBM (RS/6000, iSeries, pSeries) and Amiga systems
  </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 up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo 
PPC FAQ</uri> before you begin.
</p>

</body>
</subsection>
</section>
<!-- Copy/paste of hb-install-x86-medium.xml, with s/x86/ppc/ -->
<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. A
stage file is a tarball (compressed archive) that contains a minimal
environment.
</p>

<ul>
  <li>
    A stage1 file contains nothing more than a compiler, Portage (Gentoo's
    software management system) and a couple of packages on which the 
    compiler or Portage depends. 
  </li>
  <li>
    A stage2 file contains a so-called bootstrapped system, a minimal
    environment from which one can start building all other necessary 
    applications that make a Gentoo environment complete.
  </li>
  <li>
    A stage3 file contains a prebuilt minimal system which is almost fully
    deployable. It only lacks a few applications where you, the Gentoo user, 
    needs to choose which one you want to install.
  </li>
</ul>

<p>
We will opt for a stage3 installation throughout this document. If you want to
perform a Gentoo installation using the stage1 or stage2 files, please use the
installation instructions in the <uri
link="/doc/en/handbook/handbook-ppc.xml">Gentoo Handbook</uri>. They do
require a working Internet connection though.
</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 no Installation CD but an additional 
resource that you can exploit during the installation of your Gentoo system. It
contains prebuilt packages (the so-called GRP set) that allows 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>releases/ppc/2005.0/installcd</path> directory;
the Package CDs are located in the <path>releases/ppc/2005.0/packagecd</path>
directory.
</p>

<p>
Inside those directories you'll find so-called 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">



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-bootloader.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.00</version>
<date>2005-01-22</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-2.4.29</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-2.4.29
  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</c>:
</p>

<pre caption = "Only if /boot and the SILO destination are on the same disk">
# <i>cp /etc/silo.conf /boot</i>
# <i>/sbin/silo -C /boot/silo.conf</i>
/boot/silo.conf appears to be valid
</pre>

<p>
Otherwise just run <c>/sbin/silo</c>:
</p>

<pre caption = "Run silo">
# <i>/sbin/silo</i>
/etc/silo.conf appears to be valid
</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/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/2005.1/hb-install-sparc-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/hb-install-sparc-disk.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-08-02</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 all sparc32 systems, and 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>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-kernel.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-06-02</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 make a
symlink to <path>/etc/localtime</path> using <c>ln</c>:
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>ln -sf /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>sparc-sources</c> (kernel source optimized
for SPARC users) and <c>vanilla-sources</c> (the default kernel source as 
developed by the linux-kernel developers).
</p>

<p>
Choose your kernel source and install it using <c>emerge</c>. 
</p>

<p>
In the next example we install the <c>sparc-sources</c>.
Of course substitute with your choice of sources, this is merely an example:
</p>

<pre caption="Installing a kernel source">
# <i>emerge sparc-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:
</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-2.4.29-sparc
</pre>

<p>
If this isn't the case (i.e. the symlink points to a different kernel source) 
change the symlink before you continue:
</p>

<pre caption="Changing the kernel source symlink">
# <i>rm /usr/src/linux</i>
# <i>cd /usr/src</i>
# <i>ln -s linux-2.4.29-sparc linux</i>
</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">
Code maturity level options ---&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>, <c>/dev file system</c> + <c>Automatically mount at boot</c>:
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  [*] Virtual memory file system support (former shm fs)
  [*] /proc file system support
  [*] /dev file system support (EXPERIMENTAL)
  [*]   Automatically mount at boot
  [ ] /dev/pts file system for Unix98 PTYs

<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">
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>rp-pppoe</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>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-sparc-medium.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-05-23</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="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri>
  </ti>
</tr>
<tr>
  <th>CPU</th>
  <ti>
    Although sparc64 is the only officially supported platform, experimental
    support for sparc32 is available as well
  </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>
We currently only provide Installation CDs for the sparc64 architecture. Users 
of sparc32 can use the experimental netboot images to install Gentoo from. 
More information about netbooting can be found in our <uri 
link="/doc/en/gentoo-sparc-netboot-howto.xml">Gentoo Linux based Netboot
HOWTO</uri>.
</p>

</body>
</subsection>
</section>
<!-- Copy/Paste from hb-install-x86-medium.xml -->
<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. A
stage file is a tarball (compressed archive) that contains a minimal
environment.
</p>

<ul>
  <li>
    A stage1 file contains nothing more than a compiler, Portage (Gentoo's
    software management system) and a couple of packages on which the 
    compiler or Portage depends. 
  </li>
  <li>
    A stage2 file contains a so-called bootstrapped system, a minimal
    environment from which one can start building all other necessary 
    applications that make a Gentoo environment complete.
  </li>
  <li>
    A stage3 file contains a prebuilt minimal system which is almost fully
    deployable. It only lacks a few applications where you, the Gentoo user, 
    needs to choose which one you want to install.
  </li>
</ul>

<p>
We will opt for a stage3 installation throughout this document. If you want to
perform a Gentoo installation using the stage1 or stage2 files, please use the
installation instructions in the <uri
link="/doc/en/handbook/handbook-sparc.xml">Gentoo Handbook</uri>. They do
require a working Internet connection though.
</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 no Installation CD but an additional 
resource that you can exploit during the installation of your Gentoo system. It
contains prebuilt packages (the so-called GRP set) that allows 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>releases/sparc/2005.0/installcd/sparc64</path> 
directory; the Package CDs are located in the 
<path>releases/sparc/2005.0/packagecd/sparc64</path> directory.
</p>

<p>
Inside those directories you'll find so-called 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>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-stage.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-stage.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-stage.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-stage.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-05-04</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 CEST 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). For instance, to set the date to Mar 29th, 16:21 in the
year 2005:
</p>

<pre caption="Setting the date/time">
# <i>date 032916212005</i>
</pre>

</body>
</subsection>
<subsection>
<title>Locating the Stage3 File</title>
<body>

<p>
If you have configured networking because you need to download a stage3 file for
your architecture, continue with  <uri link="#download">Alternative: Using a
Stage3 from the Internet</uri>. Otherwise read <uri link="#available">Default:
Using a Stage3 from the Installation CD</uri>.
</p>

</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
GNU <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>stage3-&lt;subarch&gt;-2005.0.tar.bz2</path>.  Be sure to substitute the
tarball filename with your stage.
</p>

<pre caption="Extracting the stage tarball">
# <i>tar -xvjpf /mnt/cdrom/stages/stage3-&lt;subarch&gt;-2005.0.tar.bz2</i>
</pre>

<p>
Now that the stage is installed, continue with <uri
link="#installing_portage">Installing Portage</uri>.
</p>

</body>
</subsection>
</section>
<section id="download">
<title>Alternative: Using a Stage from the Internet</title>
<subsection>
<title>Downloading the Stage Tarball</title>
<body>

<p>
Go to the Gentoo mountpoint at which you mounted your filesystems
(most likely <path>/mnt/gentoo</path>):
</p>

<pre caption="Going to the Gentoo mountpoint">
# <i>cd /mnt/gentoo</i>
</pre>

<p>
Depending on your installation medium, you have a couple of tools available to
download a stage. If you have <c>links2</c> available, then you can immediately
surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and 
choose a mirror close to you.
</p>

<p>
If you don't have <c>links2</c> available you should have <c>lynx</c> at your 
disposal. If you need to go through a proxy, export the <c>http_proxy</c> and
<c>ftp_proxy</c> variables:
</p>

<pre caption="Setting proxy information for lynx">
# <i>export http_proxy="http://proxy.server.com:port"</i>
# <i>export ftp_proxy="http://proxy.server.com:port"</i>
</pre>

<p>
We will now assume that you have <c>links2</c> at your disposal.
</p>

<p>
Pick the <path>releases/</path> directory, followed by your architecture (for 
instance <path>x86/</path>) and the Gentoo version (<path>2005.0/</path>) 
to finish up with the <path>stages/</path> directory. There you should see all 
available stage files for your architecture (they might be stored within
subdirectories named to the individual sub architectures). Select one and 
press <c>D</c> to download. When you're finished, press <c>Q</c> to quit the 
browser.
</p>

<pre caption="Surfing to the mirror listing with links2">
# <i>links2 http://www.gentoo.org/main/en/mirrors.xml</i>

<comment>(If you need proxy support with links2:)</comment>
# <i>links2 -http-proxy proxy.server.com:8080 http://www.gentoo.org/main/en/mirrors.xml</i>
</pre>

<p>
If you want to check the integrity of the downloaded stage tarball, use
<c>md5sum</c> and compare the output with the MD5 checksum provided on the
mirror. For instance, to check the validity of the x86 stage tarball:
</p>

<pre caption="Example checking integrity of a stage tarball">
# <i>md5sum -c stage3-x86-2005.0.tar.bz2.md5</i>
stage3-x86-2005.0.tar.bz2: OK
</pre>

</body>
</subsection>
<subsection>
<title>Unpacking the Stage Tarball</title>
<body>

<p>
Now unpack your downloaded stage onto your system. We use GNU's <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>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-system.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-system.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-system.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-system.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.00</version>
<date>2005-01-07</date>

<section>
<title>Chrooting</title>
<subsection>
<title>Mounting the proc Filesystem</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 even within the
chrooted environment.
</p>

<pre caption="Mounting /proc">
# <i>mount -t proc none /mnt/gentoo/proc</i>
</pre>

</body>
</subsection>
<subsection>
<title>Optional: Copy over DNS Information</title>
<body>

<p>
If you configured your network to fetch the appropriate stage file later on from
the Internet, you need to copy over the DNS information stored in
<path>/etc/resolv.conf</path> to <path>/mnt/gentoo/etc/resolv.conf</path>. This
file contains the nameservers your system will use to resolve names to IP
addresses.
</p>

<pre caption="Copy over DNS Information">
# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</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>
 * Caching service dependencies...
# <i>source /etc/profile</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>
</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 -qt</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 qt kde dvd alsa cdr"
</pre>

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



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-tools.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-tools.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-tools.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-tools.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.00</version>
<date>2005-02-04</date>

<section>
<title>System Logger</title>
<body>

<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>
<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 don't require any additional networking-related tools (such as rp-pppoe
or a dhcp client) continue with <uri link="?part=1&amp;chap=10">Configuring the
Bootloader</uri>.
</p>

</body>
</section>
<section>
<title>Networking Tools</title>
<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>rp-pppoe</c> to connect to the net, you need to install it.
</p>

<pre caption="Installing rp-pppoe">
# <i>USE="-X" emerge rp-pppoe</i>
</pre>

<p>
The <c>USE="-X"</c> will prohibit xorg-x11 to be installed as a dependency
(<c>rp-pppoe</c> has graphical tools; if you want those enabled, you can
recompile <c>rp-pppoe</c> later on or have xorg-x11 installed now -- which takes a
long time to compile).
</p>

<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/2005.1/hb-install-x86-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-x86-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-bootloader.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.4</version>
<date>2005-04-16</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>. For x86, Gentoo Linux provides <uri
link="#grub">GRUB</uri> and <uri link="#lilo">LILO</uri>. But before we
install one of these two bootloaders, we inform you how to configure framebuffer
(assuming you want it of course). With framebuffer you can run the Linux command
line with (limited) graphical features (such as using the nice bootsplash
image Gentoo provides).
</p>

</body>
</subsection>
<subsection>
<title>Optional: Framebuffer</title>
<body>

<p>
<e>If</e> you have configured your kernel with framebuffer support (or you used
<c>genkernel</c>'s default kernel configuration), you can activate it by adding
a <c>vga</c> and/or a <c>video</c> statement to your bootloader configuration 
file.
</p>

<p>
First of all you need to know what type of framebuffer device you're using. If
you use a Gentoo patched kernel tree (such as <c>gentoo-sources</c>) you will
have had the possibility of selecting <c>vesafb-tng</c> as the <e>VESA driver
type</e> (which is default for these kernel sources). If this is the case, you
are using <c>vesafb-tng</c> and do not need to set a <c>vga</c> statement.
Otherwise you are using the <c>vesafb</c> driver and need to set the <c>vga</c>
statement.
</p>

<p>
The <c>vga</c> statement controls the resolution and color depth of your
framebuffer screen for <c>vesafb</c>. As stated in
<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed
when you install a kernel source package), you need to pass the VESA number 
corresponding to the requested resolution and color depth to it.
</p>

<p>
The following table lists the available resolutions and colordepths and matches
those against the value that you need to pass on to the <c>vga</c> statement.
</p>

<table>
<tr>
  <ti></ti>
  <th>640x480</th>
  <th>800x600</th>
  <th>1024x768</th>
  <th>1280x1024</th>
</tr>
<tr>
  <th>256</th>
  <ti>0x301</ti>
  <ti>0x303</ti>
  <ti>0x305</ti>
  <ti>0x307</ti>
</tr>
<tr>
  <th>32k</th>
  <ti>0x310</ti>
  <ti>0x313</ti>
  <ti>0x316</ti>
  <ti>0x319</ti>
</tr>
<tr>
  <th>64k</th>
  <ti>0x311</ti>
  <ti>0x314</ti>
  <ti>0x317</ti>
  <ti>0x31A</ti>
</tr>
<tr>
  <th>16M</th>
  <ti>0x312</ti>
  <ti>0x315</ti>
  <ti>0x318</ti>
  <ti>0x31B</ti>
</tr>
</table>

<p>
The <c>video</c> statement controls framebuffer display options. It needs to be
given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for
2.4 kernels) followed by the control statements you wish to enable. All
variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>,
but we'll inform you about three most-used options:
</p>

<table>
<tr>
  <th>Control</th>
  <th>Description</th>
</tr>
<tr>
  <ti>ywrap</ti>
  <ti>
    Assume that the graphical card can wrap around its memory (i.e. continue at
    the beginning when it has approached the end)
  </ti>
</tr>
<tr>
  <ti>mtrr</ti>
  <ti>
    Setup MTRR registers
  </ti>
</tr>
<tr>
  <ti><c>mode</c></ti>
  <ti>
    (<c>vesafb-tng</c> only)<br/>
    Set up the resolution, color depth and refresh rate. For instance,
    <c>1024x768-32@85</c> for a resolution of 1024x768, 32 bit color depth and a
    refresh rate of 85 Hz.
  </ti>
</tr>
</table>

<p>
The result of those two statements could be something like <c>vga=0x318
video=vesafb:mtrr,ywrap</c> or <c>video=vesafb:mtrr,ywrap,1024x768-32@85</c>. 
Remember (or write down) this setting; you will need it shortly.
</p>

<p>
Now continue by installing <uri link="#grub">GRUB</uri> <e>or</e> <uri
link="#lilo">LILO</uri>.
</p>

</body>
</subsection>
</section>
<section id="grub">
<title>Default: Using GRUB</title>
<subsection>
<title>Understanding GRUB's terminology</title>
<body>

<p>
The most critical part of understanding GRUB is getting comfortable with
how GRUB refers to hard drives and partitions. Your Linux partition
<path>/dev/hda1</path> will most likely be called <path>(hd0,0)</path> under 
GRUB. Notice the parenthesis around the <path>hd0,0</path> - they are required.
</p>

<p>
Hard drives count from zero rather than "a" and partitions start at zero 
rather than one. Be aware too that with the hd devices, only hard drives are 
counted, not atapi-ide devices such as cdrom players and burners.  Also, the 
same construct is used with scsi drives. (Normally they get higher numbers 
than ide drives except when the bios is configured to boot from scsi devices.)
When you ask the BIOS to boot from a different hard disk (for instance your
primary slave), <e>that</e> harddisk is seen as <path>hd0</path>.
</p>

<p>
Assuming you have a hard drive on <path>/dev/hda</path>, a cdrom player on 
<path>/dev/hdb</path>, a burner on <path>/dev/hdc</path>, a second hard drive 
on <path>/dev/hdd</path> and no SCSI hard drive, <path>/dev/hdd7</path> gets 
translated to <path>(hd1,6)</path>. It might sound tricky and tricky it is 
indeed, but as we will see, GRUB offers a tab completion mechanism
that comes handy for those of you having a lot of hard drives and
partitions and who are a little lost in the GRUB numbering scheme.
</p>

<p>
Having gotten the feel for that, it is time to install GRUB.
</p>

</body>
</subsection>
<subsection>
<title>Installing GRUB</title>
<body>




1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-x86-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/2005.1/hb-install-x86-disk.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-08-02</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 or SATA drives, then your 
first hard drive would be <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</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 x86 systems,
these are called <e>partitions</e>. 
</p>

<p>
Partitions are divided in three types:
<e>primary</e>, <e>extended</e> and <e>logical</e>.
</p>

<p>
A <e>primary</e> partition is a partition which has its information stored in
the MBR (master boot record). As an MBR is very small (512 bytes) only four
primary partitions can be defined (for instance, <path>/dev/hda1</path> to
<path>/dev/hda4</path>).
</p>

<p>
An <e>extended</e> partition is a special primary partition (meaning the
extended partition must be one of the four possible primary partitions) which
contains more partitions. Such a partition didn't exist originally, but as
four partitions were too few, it was brought to life to extend the formatting
scheme without losing backward compatibility.
</p>

<p>
A <e>logical</e> partition is a partition inside the extended partition. Their
definitions aren't placed inside the MBR, but are declared inside the extended
partition. 
</p>

</body>
</subsection>
<subsection>
<title>Advanced Storage</title>
<body>

<p>
The x86 Installation CDs provide support for EVMS and LVM2. EVMS and LVM2 
increase the flexibility offered by your partitioning setup. During the 
installation instructions, we will focus on "regular" partitions, but it is 
still good to know EVMS and LVM2 are supported as well.
</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/hda1</path></ti>
  <ti>ext2</ti>
  <ti>32M</ti>
  <ti>Boot partition</ti>
</tr>
<tr>
  <ti><path>/dev/hda2</path></ti>
  <ti>(swap)</ti>
  <ti>512M</ti>
  <ti>Swap partition</ti>
</tr>
<tr>
  <ti><path>/dev/hda3</path></ti>
  <ti>ext3</ti>
  <ti>Rest of the disk</ti>
  <ti>Root partition</ti>
</tr>
</table>

<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 partitioning 
your disk by reading <uri link="#fdisk">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>

<p>
As an example partitioning, we show you one for a 20GB disk, used as a
demonstration laptop (containing webserver, mailserver, gnome, ...):
</p>

<pre caption="Filesystem usage example">



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-x86-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-kernel.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.9</version>
<date>2005-07-04</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 make a
symlink to <path>/etc/localtime</path> using <c>ln</c>:
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>ln -sf /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 x86-based systems, our main supported kernel is named
<c>gentoo-sources</c>. This kernel is based on the official Linux sources, but
has security, stability, compatibility and bug fixes applied on top.
Alternatively, the plain and unpatched Linux sources are supplied through the
<c>vanilla-sources</c> package.
</p>

<p>
Both kernel sources are based on the official 2.6 kernel sources. If you
want to install a 2.4-based kernel, you will need to install Gentoo with a
working Internet connection as we do not supply these sources on our
Installation CD.
</p>

<p>
Choose your kernel source and install it using <c>emerge</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. We will assume the kernel
source installed is <c>gentoo-sources-2.6.11-r3</c>:
</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-2.6.11-gentoo-r3
</pre>

<p>
If the symlink doesn't point to the kernel source of your choice (note that
<c>linux-2.6.11-gentoo-r3</c> is merely an example) you should change it to the
right kernel:
</p>

<pre caption="Changing the kernel source symlink">
# <i>rm /usr/src/linux</i>
# <i>cd /usr/src</i>
# <i>ln -s linux-2.6.11-gentoo-r3 linux</i>
</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 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>
Make sure that every driver that is vital to the booting of your system (such as
SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module,
otherwise your system will not be able to boot completely.
</p>

<p>
Now select the correct processor family:
</p>

<pre caption="General Support and processor family">
General setup  ---&gt;
	[*] Support for hot-pluggable devices
Processor type and features ---&gt;
    Subarchitecture Type (PC-compatible)  ---&gt;
  <comment>(Change according to your system)</comment>
  (<i>Athlon/Duron/K7</i>) Processor family
</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>/proc file system</c> and
<c>Virtual memory</c>. Do <e>not</e> select the <c>/dev file system</c>.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    &lt;*&gt; /proc file system support
    &lt; &gt; /dev file system support (OBSOLETE)
    &lt;*&gt; 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>
Do not forget to enable DMA for your drives:
</p>



1.1                  xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-x86-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/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-x86-medium.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<sections>

<version>4.2</version>
<date>2005-05-23</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>i486 or later</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>
<!-- General description, propagated to other architectures as well -->
<!-- START -->
<section>
<title>The Gentoo Universal Installation CD</title>
<subsection>
<title>Introduction</title>
<body>

<p>
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. A
stage file is a tarball (compressed archive) that contains a minimal
environment.
</p>

<ul>
  <li>
    A stage1 file contains nothing more than a compiler, Portage (Gentoo's
    software management system) and a couple of packages on which the 
    compiler or Portage depends. 
  </li>
  <li>
    A stage2 file contains a so-called bootstrapped system, a minimal
    environment from which one can start building all other necessary 
    applications that make a Gentoo environment complete.
  </li>
  <li>
    A stage3 file contains a prebuilt minimal system which is almost fully
    deployable. It only lacks a few applications where you, the Gentoo user, 
    needs to choose which one you want to install.
  </li>
</ul>

<p>
We will opt for a stage3 installation throughout this document. If you want to
perform a Gentoo installation using the stage1 or stage2 files, please use the
installation instructions in the <uri
link="/doc/en/handbook/handbook-x86.xml">Gentoo Handbook</uri>. They do
require a working Internet connection though.
</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 no Installation CD but an additional 
resource that you can exploit during the installation of your Gentoo system. It
contains prebuilt packages (the so-called GRP set) that allows 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 CDs (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>releases/x86/2005.0/installcd</path> directory;
the Package CDs are located in the <path>releases/x86/2005.0/packagecd</path>
directory.
</p>

<p>
i686, athlon-xp, pentium3 and pentium4 Package CDs are available via 
<uri link="http://torrents.gentoo.org">BitTorrent</uri>.
</p>

<p>
Inside those directories you'll find so-called 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 pgp.mit.edu --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>



1.1                  xml/htdocs/doc/en/handbook/2005.1/index.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/index.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/index.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

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/2005.1/index.xml,v 1.1 2005/08/08 13:16:10 swift Exp $ -->

<guide link="index.xml">
<title>Gentoo 2005.0 Handbook</title>

<author title="Author">
  <mail link="swift@g.o">Sven Vermeulen</mail>
</author>

<abstract>
The Gentoo 2005.0 Handbook contains the networkless installation instructions
for the 2005.0 release and parts on working with Gentoo and Portage.
</abstract>

<license/>

<version>4.2</version>
<date>2005-07-26</date>

<chapter>
<title>The Gentoo Linux 2005.0 Handbooks</title>
<!-- Uncomment when needed, probably for the 2005.0 versions -->
<!-- 
<section>
<title>Available languages</title>
<body>

<p>
The Gentoo Linux 2005.0 Handbook is available in the following languages:
</p>

<p>
<uri link="/doc/da/handbook">Danish</uri> | 
<uri link="/doc/de/handbook">German</uri> |
<uri link="/doc/en/handbook">English</uri> | 
<uri link="/doc/fr/handbook">French</uri> | 
<uri link="/doc/id/handbook">Indonesian</uri> |
<uri link="/doc/it/handbook">Italian</uri> |
<uri link="/doc/ja/handbook">Japanese</uri> |
<uri link="/doc/pl/handbook">Polish</uri> | 
<uri link="/doc/ro/handbook">Romanian</uri> |
<uri link="/doc/es/handbook">Spanish</uri> |
<uri link="/doc/zh_tw/handbook">Traditional Chinese</uri>
</p>

</body>
</section>
-->
<section>
<title>Introduction</title>
<body>

<p>
Welcome to the Gentoo Linux 2005.0 Handbooks. These handbooks are released
together with the Gentoo Linux releases and contain the necessary installation
instructions to install Gentoo Linux 2005.0 <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/index.xml">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-alpha.xml">alpha</uri>,
    <uri link="handbook-amd64.xml">amd64</uri>, 
    <uri link="handbook-ppc.xml">ppc</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-alpha.xml?full=1">alpha</uri>,
    <uri link="handbook-amd64.xml?full=1">amd64</uri>, 
    <uri link="handbook-ppc.xml?full=1">ppc</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-alpha.xml?style=printable&amp;full=1">alpha</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-hppa.xml?style=printable&amp;full=1">hppa</uri> -->
  </ti>
</tr>
</table>


</body>
</section>
</chapter>
</guide>



-- 
gentoo-doc-cvs@g.o mailing list