[gentoo-doc-cvs] cvs commit: handbook-ia64.xml hb-install-ia64-bootloader.xml hb-install-ia64-disk.xml hb-install-ia64-kernel.xml hb-install-ia64-medium.xml

[vapier]

vapier      06/09/03 05:02:44

  Added:                handbook-ia64.xml hb-install-ia64-bootloader.xml
                        hb-install-ia64-disk.xml hb-install-ia64-kernel.xml
                        hb-install-ia64-medium.xml
  Log:
  initial import of ia64 handbook

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

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

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

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ia64.xml,v 1.1 2006/09/03 05:02:44 vapier Exp $ -->

<book link="/doc/en/handbook/handbook-ia64.xml">
<title>Gentoo Linux/IA64 Handbook</title>

<values>
 <key id="arch">IA64</key>
 <key id="kernel-version">2.6.17-r5</key>
 <key id="kernel-name">kernel-2.6.17-gentoo-r5</key>
 <key id="genkernel-name">kernel-genkernel-ia64-2.6.17-gentoo-r5</key>
 <key id="genkernel-initrd">initramfs-genkernel-ia64-2.6.17-gentoo-r5</key>
 <key id="min-cd-name">install-ia64-minimal-2006.1.iso</key>
 <key id="min-cd-size">52</key>
 <key id="release-dir">releases/ia64/2006.1/</key>
 <key id="online-book">handbook-ia64.xml</key>
</values>

<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 IA64 developer">
   <mail link="plasmaroo@g.o">Tim Yamin</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="Gentoo * developer">
  <mail link="vapier@g.o">Mike Frysinger</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="redhatter@g.o">Stuart Longland</mail>
</author>
<author title="Editor">
  <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
</author>
<author title="Editor">
  <mail link="neysx@g.o">Xavier Neys</mail>
</author>
<author title="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="dberkholz@g.o">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
    <mail link="antifa@g.o">Ken Nowack</mail>
</author>
<author title="Contributor">
   <mail link="pylon@g.o">Lars Weiler</mail>
</author>

<abstract>
This is the Gentoo 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.5 -->
<license/>

<version>7.0</version>
<date>2006-08-30</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>
This chapter introduces you to the installation approach documented in this
part.
</abstract>
  <include href="hb-install-about.xml"/>
</chapter>

<chapter>
<title>Choosing the Right Installation Medium</title>
<abstract>
You can install Gentoo in many ways. This chapter explains how to install Gentoo
using the minimal Installation CD although installation through the Universal 
Installation CD is possible as well.
</abstract>
  <include href="hb-install-ia64-medium.xml"/>
</chapter>

<chapter>
<title>Configuring your Network</title>
<abstract>
To be able to download the latest source code, you will need to setup
networking.
</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-ia64-disk.xml"/>
</chapter>

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

<chapter>
<title>Installing the Gentoo Base System</title>
<abstract>
After installing and configuring a stage3, the eventual result is that you
have a Gentoo base system at your disposal. This chapter describes how
to progress to that stadium.
</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-ia64-kernel.xml"/>
</chapter>

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

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

<chapter>
<title>Configuring the Bootloader</title>
<abstract>
The ia64 architecture uses the elilo bootloader.
This chapter explains how to install and configure elilo.
</abstract>
  <include href="hb-install-ia64-bootloader.xml"/>
</chapter>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

</book>



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

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

Index: hb-install-ia64-bootloader.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

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

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-bootloader.xml,v 1.1 2006/09/03 05:02:44 vapier Exp $ -->

<sections>

<version>7.1</version>
<date>2006-08-30</date>

<section>
<title>Installing elilo</title>
<body>

<p>
On the IA64 platform, the boot loader is called elilo.  You may need to 
emerge it on your machine first.
</p>

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

<p>
You can find the configuration file at <path>/etc/elilo.conf</path> and a
sample file in the typical docs dir <path>/usr/share/doc/elilo-&lt;ver&gt;/</path>.
Here is another sample configuration:
</p>

<pre caption = "/etc/elilo.conf example">
boot=/dev/sda1
delay=30
timeout=50
default=Gentoo
append="console=ttyS0,9600"
prompt

image=/vmlinuz
	label=Gentoo
	root=/dev/sda2
	read-only

image=/vmlinuz.old
	label=Gentoo.old
	root=/dev/sda2
	read-only
</pre>

<p>
The <c>boot</c> line tells elilo the location of the boot partition (in this
case, <path>/dev/sda1</path>).  The <c>delay</c> line sets the number of 10th
of seconds before automatically booting the default when in non-interactive
mode.  The <c>timeout</c> line is just like the delay line but for interactive
mode.  The <c>default</c> line sets the default kernel entry (which is defined
below).  The <c>append</c> line adds extra options to the kernel cmdline.  The
<c>prompt</c> sets the default elilo behavior to interactive.
</p>

<p>
The sections that start with <c>image</c> defines different bootable images.
Each image has a nice <c>label</c>, a <c>root</c> filesystem, and will only
mount the root filesystem <c>read-only</c>.
</p>

<p>
When configuration is done, just run <c>elilo --efiboot</c>. The <c>--efiboot
</c> option adds a menu entry for Gentoo Linux to the EFI Boot Manager.
</p>

<pre caption = "Applying the elilo configuration">
# <i>elilo --efiboot</i>
</pre>

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

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

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

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

<p>
When you reboot you should see a new Gentoo Linux menu option in the
EFI Boot Manager which will boot Gentoo.  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/hb-install-ia64-disk.xml

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

Index: hb-install-ia64-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/hb-install-ia64-disk.xml,v 1.1 2006/09/03 05:02:44 vapier Exp $ -->

<sections>

<version>2.2</version>
<date>2005-06-10</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 <keyval id="arch"/>
systems, these are called <e>partitions</e>. 
</p>

<p>
Itanium systems use EFI, the Extensible Firmware Interface, for booting.  The
partition table format that EFI understands is called GPT, or GUID Partition
Table.  The partitioning program that understands GPT is called "parted", so
that is the tool we will use below.  Additionally, EFI can only read FAT
filesystems, so that is the format to use for the EFI boot partition, where the
kernel will be installed by "elilo".
</p>

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

<p>
The <keyval id="arch"/> 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/sda1</path></ti>
  <ti>vfat</ti>
  <ti>32M</ti>
  <ti>EFI Boot partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda2</path></ti>
  <ti>(swap)</ti>
  <ti>512M</ti>
  <ti>Swap partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda3</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="#parted">Using parted 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">
$ <i>df -h</i>
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
/dev/hda6     swap    516M   12M  504M   2% &lt;not mounted&gt;
<comment>(Unpartitioned space for future usage: 2 GB)</comment>
</pre>

<p>
<path>/usr</path> is rather full (83% used) here, but once
all software is installed, <path>/usr</path> doesn't tend to grow that much.
Although allocating a few gigabytes of disk space for <path>/var</path> may
seem excessive, remember that Portage uses this partition by default for
compiling packages. If you want to keep <path>/var</path> at a more reasonable
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable
in <path>/etc/make.conf</path> to point to the partition with enough free space
for compiling extremely large packages such as OpenOffice.
</p>

</body>
</subsection>
</section>
<section id="parted">
<title>Using parted 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><path>/dev/sda1</path></ti>
  <ti>EFI Boot partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda2</path></ti>
  <ti>Swap partition</ti>
</tr>
<tr>
  <ti><path>/dev/sda3</path></ti>
  <ti>Root partition</ti>
</tr>
</table>

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

</body>
</subsection>
<subsection>
<title>Viewing the Current Partition Layout</title>
<body>

<p>
<c>parted</c> is the GNU partition editor.
Fire up <c>parted</c> on your disk (in our example, we use
<path>/dev/sda</path>):
</p>

<pre caption="Starting parted">
# <i>parted /dev/sda</i>
</pre>

<p>
Once in <c>parted</c>, you'll be greeted with a prompt that looks like this:
</p>

<pre caption="parted prompt">
GNU Parted 1.6.22
Copyright (C) 1998 - 2005 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
General Public License for more details.

Using /dev/sda
(parted)
</pre>

<p>
At this point one of the available commands is <c>help</c>, which you should use
if you want to see the other available commands.  Another command is
<c>print</c> which you should type next to display your disk's current partition
configuration:
</p>

<pre caption="An example partition configuration">
(parted) <i>print</i>
Disk geometry for /dev/sda: 0.000-34732.890 megabytes
Disk label type: gpt
Minor    Start       End     Filesystem  Name                  Flags
1          0.017    203.938  fat32                             boot
2        203.938   4243.468  linux-swap
3       4243.469  34724.281  ext3
</pre>

<p>
This particular configuration is very similar to the one that we recommend
above.  Note on the second line that the partition table is type is GPT.  If it
is different, then the ia64 system will not be able to boot from this disk.
For the sake of this guide we'll remove the partitions and create them anew.
</p>

</body>
</subsection>
<subsection>
<title>Removing all Partitions</title>
<body>

<note>
Unlike fdisk and some other partitioning programs which postpone committing
changes until you give the write instruction, parted commands take effect
immediately.  So once you start adding and removing partitions, you can't
simply quit without writing them... they've already been written.
</note>

<p>
The easy way to remove all partitions and start fresh, which guarantees that we
are using the correct partition type, is to make a new partition table using the
<c>mklabel</c> command.  After you do this, you will have an empty GPT partition
table.
</p>

<pre caption="Creating a new partition table">
(parted) <i>mklabel gpt</i>
(parted) <i>print</i>
Disk geometry for /dev/sda: 0.000-34732.890 megabytes
Disk label type: gpt
Minor    Start       End     Filesystem  Name                  Flags
</pre>

<p>
Now that the partition table is empty, we're ready to create the
partitions. We will use a default partitioning scheme as discussed previously.
Of course, don't follow these instructions to the letter if you don't want the
same partitioning scheme!
</p>

</body>
</subsection>
<subsection>
<title>Creating the EFI Boot Partition</title>
<body>

<p>
We first create a small EFI boot partition. This is required to be a FAT
filesystem in order for the ia64 firmware to read it.  Our example makes this
32 megabytes, which is appropriate for storing kernels and elilo configuration.
You can expect each ia64 kernel to be around 5 megabytes, so this configuration
leaves you some room to grow and experiment.
</p>

<pre caption="Creating the boot partition">
(parted) <i>mkpart primary fat32 0 32</i>
(parted) <i>print</i>
Disk geometry for /dev/sda: 0.000-34732.890 megabytes
Disk label type: gpt
Minor    Start       End     Filesystem  Name                  Flags
1          0.017     32.000  fat32
</pre>

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

<p>
Let's now create the swap partition.  The classic size to make the swap
partition was twice the amount of RAM in the system.  In modern systems with
lots of RAM, this is no longer necessary.  For most desktop systems, a 512
megabyte swap partition is sufficient.  For a server, you should consider
something larger to reflect the anticipated needs of the server.
</p>

<pre caption="Creating the swap partition">
(parted) <i>mkpart primary linux-swap 32 544</i>
(parted) <i>print</i>
Disk geometry for /dev/sda: 0.000-34732.890 megabytes
Disk label type: gpt
Minor    Start       End     Filesystem  Name                  Flags
1          0.017     32.000  fat32
2         32.000    544.000
</pre>

</body>
</subsection>
<subsection>
<title>Creating the Root Partition</title>
<body>

<p>
Finally, let's create the root partition.  Our configuration will make the root
partition to occupy the rest of the disk.  We default to ext3, but you can use
ext2, jfs, reiserfs or xfs if you prefer.  The actual filesystem is not created
in this step, but the partition table contains an indication of what kind of
filesystem is stored on each partition, and it's a good idea to make the table
match your intentions.
</p>

<pre caption="Creating the root partition">
(parted) <i>mkpart primary ext3 544 34732.890</i>
(parted) <i>print</i>
Disk geometry for /dev/sda: 0.000-34732.890 megabytes
Disk label type: gpt
Minor    Start       End     Filesystem  Name                  Flags
1          0.017     32.000  fat32
2         32.000    544.000
3        544.000  34732.874
</pre>

</body>
</subsection>
<subsection>
<title>Exiting parted</title>
<body>

<p>
To quit from parted, type <c>quit</c>.  There's no need to take a separate step
to save your partition layout since parted has been saving it all along.  As you
leave, parted gives you reminder to update your <c>/etc/fstab</c>, which we'll
do later in this guide.
</p>

<pre caption="Quit from parted">
(parted) <i>quit</i>
Information: Don't forget to update /etc/fstab, if necessary.
</pre>

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

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

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

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

<p>
The Linux kernel supports various filesystems. We'll explain ext2, ext3,
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux
systems.
</p>

<p>
<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames.  It is
also the only filesystem type that the EFI firmware on ia64 systems understand.
The boot partition on ia64 systems should always be vfat, but for your data
partitions you should use one of the other filesystems listed below.
</p>

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

<p>
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
journaling for fast recovery in addition to other enhanced journaling modes like
full data and ordered data journaling. ext3 is a very good and reliable
filesystem.
</p>

<p>
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall 
performance and greatly outperforms both ext2 and ext3 when dealing with small 
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales 
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is 
solid and usable as both general-purpose filesystem and for extreme cases such 
as the creation of large filesystems, the use of many small files, very large 
files and directories containing tens of thousands of files. 
</p>

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

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

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

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

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

<p>
For instance, to have the boot partition (<path>/dev/sda1</path> in our
example) as vfat and the root partition (<path>/dev/sda3</path> in our example)
as ext3, you would run the following commands:
</p>

<pre caption="Applying a filesystem on a partition">
# <i>mkdosfs /dev/sda1</i>
mkdosfs 2.10 (22 Sep 2003)

# <i>mke2fs -j /dev/sda3</i>
mke2fs 1.36 (05-Feb-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
4382336 inodes, 8752348 blocks
437617 blocks (5.00%) reserved for the super user
First data block=0
268 block groups
32768 blocks per group, 32768 fragments per group
16352 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624

Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
</pre>

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

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

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

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

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

<p>
Create and activate the swap with the commands mentioned above.
</p>

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

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

<pre caption="Mounting the root partition">
# <i>mount /dev/sda3 /mnt/gentoo</i>
</pre>

<note>
Unlike some of the other architectures supported by Gentoo, <path>/boot</path>
is not mounted on ia64.  The reason for this is that the EFI boot partition will
be automatically mounted and written by the elilo command each time that you run
it.  Because of this, /boot resides on the root filesystem and is the storage
place for the kernels referenced by your elilo configuration.
</note>

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

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

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

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



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

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

Index: hb-install-ia64-kernel.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

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

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v 1.1 2006/09/03 05:02:44 vapier Exp $ -->

<sections>

<version>7.1</version>
<date>2006-08-30</date>

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

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

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

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

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

<p>
For IA64 systems, the available kernels are <c>vanilla-sources</c> (the default
kernel source as distributed from <uri link="http://kernel.org/">kernel.org</uri>
and <c>gentoo-sources</c> (contains additional patches for performance and
stability).
</p>

<p>
Choose your kernel source and install it using <c>emerge</c>. The
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new
install, but ensures proper creation of the <path>/usr/src/linux</path>
symlink.
</p>

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

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

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

<p>
Now it is time to configure and compile your kernel source. 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>
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 system type and processor type. If you don't know what
kind of IA64 system type you have, <c>DIG-compliant</c> is a good default
choice. If you are installing on an SGI system make sure you select the
SGI system type, your kernel may just lock up and refuse to boot otherwise.
</p>

<pre caption="Selecting correct system type">
System type ---&gt;
  <comment>(Change according to your system)</comment>
  <i>DIG-compliant</i>
Processor type ---&gt;
  <comment>(Change according to your system)</comment>
  <i>Itanium 2</i>
</pre>

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

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

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

<comment>(Be sure to enable VFAT support for the EFI partition)</comment>
DOS/FAT/NT Filesystems  --->
  &lt;*&gt; VFAT (Windows-95) fs support
</pre>

<p>
Do not forget to enable DMA for your drives:
</p>

<pre caption="Activating DMA">
Device Drivers ---&gt;
  ATA/ATAPI/MFM/RLL support ---&gt;
    [*] Generic PCI bus-master DMA support
    [*]   Use PCI DMA by default when available
</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>

<p>
If you have an Intel CPU that supports HyperThreading (tm), or you have a
multi-CPU system, you should activate "Symmetric multi-processing support":
</p>

<pre caption="Activating SMP support">
Processor type and features  ---&gt;
  [*] Symmetric multi-processing support
</pre>

<p>
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
those as well:
</p>

<pre caption="Activating USB Support for Input Devices">
Device Drivers ---&gt;
  USB Support ---&gt;
    &lt;*&gt;   USB Human Interface Device (full HID) support
</pre>

<p>
When you've finished configuring the kernel, continue with <uri 
link="#compiling">Compiling and Installing</uri>.
</p>

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

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

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

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

<pre caption="Installing the kernel">
# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
</pre>

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

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

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

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

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

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

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

<note>
Users of EVMS2 or LVM2 will probably want to add
<c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line.
</note>

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

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

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

<p>
Now, let's perform one more step to get our system to be more like the
Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects 
hardware that is needed to boot your system, <c>coldplug</c> autodetects 
everything else. To emerge and enable <c>coldplug</c>, type the following:
</p>

<pre caption="Emerging and enabling coldplug">
# <i>emerge coldplug</i>
# <i>rc-update add coldplug boot</i>
</pre>

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

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

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

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

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

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

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

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

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



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

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

Index: hb-install-ia64-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

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

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-medium.xml,v 1.1 2006/09/03 05:02:44 vapier Exp $ -->

<sections>

<version>4.0</version>
<date>2006-08-30</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>
Pretty much every IA64 should be able to boot Gentoo.  At the moment we only
have LiveCDs, so your machine must have a CDROM drive installed.
</p>

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

<section>
<title>The Gentoo Installation CDs</title>
<subsection>
<title>Introduction</title>
<body>

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

<p>
All Installation CDs allow you to boot, set up networking, initialize your
partitions and start installing Gentoo from the Internet. We currently provide
two Installation CDs which are equaly suitable to install Gentoo from, as long
as you're planning on performing an Internet-based installation using the 
latest version of the available packages.
</p>

<impo>
If you wish to install Gentoo without a working Internet connection, or would
like to use one of the provided installers, please use the installation
instructions described in the <uri link="2006.1/">Gentoo 2006.1
Handbooks</uri>.
</impo>

<p>
The Installation CD that we currently provide for IA64:
</p>

<ul>
  <li>
    The Gentoo <e>Minimal</e> Installation CD, a small, no-nonsense, bootable 
    CD which sole purpose is to boot the system, prepare the networking and 
    continue with the Gentoo installation.
  </li>
</ul>

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

<p>
The Minimal Installation CD is called <c><keyval id="min-cd-name"/></c> and
takes up only <keyval id="min-cd-size"/> MB of diskspace. You can use this
Installation CD to install Gentoo, but <e>only</e> with a working Internet
connection.
</p>

<table>
<tr>
  <th>Minimal Installation CD</th>
  <th>Pros and Cons</th>
</tr>
<tr>
  <th>+</th>
  <ti>Smallest download</ti>
</tr>
<tr>
  <th>-</th>
  <ti>
    Contains no stage3 tarball, no Portage snapshot, no prebuilt packages and
    is therefore not suitable for networkless installation
  </ti>
</tr>
</table>

</body>
</subsection>
<subsection>
<title>The Stage3 Tarball</title>
<body>

<p>
A stage3 tarball is an archive containing a minimal Gentoo environment,
suitable to continue the Gentoo installation using the instructions in this
manual. Previously, the Gentoo Handbook described the installation using one of
three stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the
official installation method uses the stage3 tarball. If you are interested in
performing a Gentoo installation using a stage1 or stage2 tarball, please read
the Gentoo FAQ on <uri link="/doc/en/faq.xml#stage12">How do I Install Gentoo
Using a Stage1 or Stage2 Tarball?</uri>
</p>

<p>
Stage3 tarballs can be downloaded from <path><keyval
id="release-dir"/>stages/</path> on any of the <uri
link="/main/en/mirrors.xml">Official Gentoo Mirrors</uri> and are not provided
on the LiveCD.
</p>

</body>
</subsection>
</section>
<section>
<title>Download, Burn and Boot a Gentoo Installation CD</title>
<subsection>
<title>Downloading and Burning the Installation CDs</title>
<body>

<p>
You have chosen to use a Gentoo Installation CD. We'll first start by 
downloading and burning the chosen Installation CD. We previously discussed 
the several available Installation CDs, but where can you find them? 
</p>

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

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

<p>
In case you wonder if your downloaded file is corrupted or not, you can check
its MD5 checksum and compare it with the MD5 checksum we provide (such as
<path><keyval id="min-cd-name"/>.DIGESTS</path>). You can check the MD5
checksum with the <c>md5sum</c> tool under Linux/Unix or <uri
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows.
</p>

<p>
Another way to check the validity of the downloaded file is to use GnuPG to
verify the cryptographic signature that we provide (the file ending with
<path>.asc</path>). Download the signature file and obtain the public key:
</p>

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

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

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

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

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

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

<p>
Once you have burnt your installation CD, it is time to boot it.
Remove all CDs from your CD drives, and insert the Gentoo
InstallCD. Reboot your system and wait for the EFI firmware to load on
the console. The exact option to select will differ depending on your
hardware.
</p>

<p>
Most implementations usually present an option directly on the first
menu (the EFI Boot Manager). The exact wording would differ but would
usually be something like &quot;CD Boot&quot;, &quot;Removable Media
Boot&quot; or &quot;Internal Bootable DVD&quot;. Select this option.
</p>

<p>
If your EFI implementation does not present such an option, you can
boot the CD using the EFI Shell. All implementations will present an
option to enter the shell on the Boot Manager menu. Select this
option. The EFI Shell will display a list of usable block devices
(<c>blk<b>n</b>:</c>) and also a list of filesystems the EFI Shell
can actually access (<c>fs<b>n</b>:</c>).
</p>

<p>
In most cases the option you want will be the <c>fs0:</c> choice;
regardless, (provided the CD drive recognizes the CD), you should
see one <c>fs<b>n</b></c> entry for your CD drive (the CD drive's
EFI device path will contain <c>CDROM</c> in the wording). Enter
<c>fs<b>n</b>:</c>, replacing <b>n</b> as required and including
the colon, followed by the Enter key. Next just type <c>elilo</c>
followed by the Enter key.
</p>

<p>
You will now be greeted by the ELILO boot message and asked to
enter a kernel to boot as well as any additional options to pass
to the kernel command line. In most cases just hit the Enter key
or wait five seconds. Only one kernel is supplied on the IA64
InstallCD, the <c>gentoo</c> kernel.
</p>

<p>
Several kernel aliases are provided which add extra options to
the kernel command line, which you may have to use instead of
the default <c>gentoo</c> option depending on your hardware:
</p>

<p>
The <c>gentoo-serial</c> option forces a serial console on the first
serial port (ttyS0) at 9600bps. This may be required on some older EFI
implementations where the kernel can't detect what console to use. You
should try this option if booting the default <c>gentoo</c> kernel
produces no output and if you are using a serial console. If you use a
serial console which is not connected to the first serial port you
must manually select the console by typing <c>gentoo
console=ttyS#,9600</c> where <c>#</c> is the number of the serial
port. You should <b>not</b> have to do this in normal circumstances,
this is only sometimes required for quirky EFI implementations.
</p>

<p>
The <c>gentoo-sgi</c> option forces a serial console on the <c>ttySG0</c>
serial port at 115200bps. This should only be needed on SGI hardware, and
if the console is properly selected in the default EFI settings, or if you
are using a video console this option should not be required.
</p>

</body>
<body>

<p>
You can also provide kernel options. They represent optional settings
you can (de)activate at will.
</p>

<pre caption="Options available to pass to your kernel of choice">
- agpgart       loads agpgart (use if you have graphic problems,lockups)
- ide=nodma     force disabling of DMA for malfunctioning IDE devices
- doscsi        scan for scsi devices (breaks some ethernet cards)
- dopcmcia      starts pcmcia service for PCMCIA cdroms
- nofirewire    disables firewire modules in initrd (for firewire cdroms,etc)
- nokeymap      disables keymap selection for non-us keyboard layouts
- docache       cache the entire runtime portion of CD in RAM, allows you
                to umount /mnt/cdrom to mount another CD.
- nodetect      causes hwsetup/kudzu and hotplug not to run
- nousb         disables usb module load from initrd, disables hotplug
- nodhcp        dhcp does not automatically start if nic detected
- nohotplug     disables loading hotplug service
- noapic        disable apic (try if having hardware problems nics,scsi,etc)
- noevms        disable loading of EVMS2 modules
- nolvm2        disable loading of LVM2 modules
- noload=module1,[module2,[...]]
                disable loading of specific kernel modules
</pre>

<p>
You will then be greeted with a boot screen. If you are installing
Gentoo on a system with a non-US keyboard, make sure you select the
layout at the prompt. If no selection is made in 10 seconds the
default (US keyboard) will be accepted and the boot process will
continue. Once the boot process completes, you will be automatically
logged in to the "Live" Gentoo Linux as "root", the super user. You
should have a root ("#") prompt on the current console. If you are
using a video console and have a keyboard connected you can also
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get
back to the one you started on by pressing Alt-F1.
</p>

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

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

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

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

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

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

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

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

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

<pre caption="Tweaking hard disk performance">
<comment>(Activate DMA:)</comment>
# <i>hdparm -d 1 /dev/hda</i>

<comment>(Activate Safe Performance Options:)</comment>
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
</pre>

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

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

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

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

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

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

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

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

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

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

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

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

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

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



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