swift 05/08/08 13:21:15
Added: xml/htdocs/doc/en/handbook/2005.1 handbook-ppc64.xml
hb-install-ppc64-bootloader.xml
hb-install-ppc64-disk.xml
hb-install-ppc64-kernel.xml
hb-install-ppc64-medium.xml
Log:
New architecture for 2005.1: ppc64
Revision Changes Path
1.1 xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.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-ppc64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: handbook-ppc64.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">
<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.xml,v 1.1
2005/08/08 13:21:15 swift Exp $ -->
<book link="handbook-ppc64.xml">
<title>Gentoo Linux 2005.1 PPC64 Handbook</title>
<author title="Author">
<mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
</author>
<author title="Author">
<mail link="[EMAIL PROTECTED]">Roy Marples</mail>
</author>
<author title="Author">
<mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
</author>
<author title="Author">
<mail link="[EMAIL PROTECTED]">Chris Houser</mail>
</author>
<author title="Author">
<mail link="[EMAIL PROTECTED]">Jerry Alexandratos</mail>
</author>
<author title="Gentoo x86 Developer">
<mail link="[EMAIL PROTECTED]">Seemant Kulleen</mail>
</author>
<author title="Gentoo Alpha Developer">
<mail link="[EMAIL PROTECTED]">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="[EMAIL PROTECTED]">Jason Huebel</mail>
</author>
<author title="Gentoo HPPA developer">
<mail link="[EMAIL PROTECTED]">Guy Martin</mail>
</author>
<author title="Gentoo PPC developer">
<mail link="[EMAIL PROTECTED]">Pieter Van den Abeele</mail>
</author>
<author title="Gentoo SPARC developer">
<mail link="[EMAIL PROTECTED]">Joe Kallar</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">John P. Davis</mail>
</author>
<author title="Editor">Pierre-Henri Jondot</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Eric Stockbridge</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Rajiv Manglani</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Jungmin Seo</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Stoyan Zhekov</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Jared Hudson</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Colin Morey</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Jorge Paulo</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Carl Anderson</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Jon Portnoy</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Zack Gilburd</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Jack Morgan</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Benny Chuang</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Erwin</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Joshua Kinard</mail>
</author>
<author title="Reviewer">
<mail link="[EMAIL PROTECTED]">Grant Goodyear</mail>
</author>
<author title="Reviewer">
<mail link="[EMAIL PROTECTED]">Gerald J. Normandin Jr.</mail>
</author>
<author title="Reviewer">
<mail link="[EMAIL PROTECTED]">Donnie Berkholz</mail>
</author>
<author title="Reviewer">
<mail link="[EMAIL PROTECTED]">Ken Nowack</mail>
</author>
<author title="Contributor">
<mail link="[EMAIL PROTECTED]">Lars Weiler</mail>
</author>
<author title="Editor">
<mail link="[EMAIL PROTECTED]">Tobias Scherbaum</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>5.0</version>
<date>2005-08-08</date>
<part>
<title>Installing Gentoo</title>
<abstract>
In this part you learn how to install Gentoo on your system.
</abstract>
<chapter>
<title>About the Gentoo Linux Installation</title>
<abstract>
Users not familiar with Gentoo do not always know that choice is what
Gentoo is all about.
</abstract>
<include href="hb-install-about.xml"/>
</chapter>
<chapter>
<title>Booting the Universal Installation CD</title>
<abstract>
Using our Universal Installation CD you can boot up your system into a running
environment that allows you to install Gentoo.
</abstract>
<include href="hb-install-ppc64-medium.xml"/>
</chapter>
<chapter>
<title>Configuring your Network</title>
<abstract>
If you need networking, this is the place where the network (and Internet
connection) is configured.
</abstract>
<include href="hb-install-network.xml"/>
</chapter>
<chapter>
<title>Preparing the Disks</title>
<abstract>
To be able to install Gentoo, you must create the necessary partitions.
This chapter describes how to partition a disk for future usage.
</abstract>
<include href="hb-install-ppc64-disk.xml"/>
</chapter>
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
In this chapter we describe how you extract a stage3 file and how to configure
Portage.
</abstract>
<include href="hb-install-stage.xml"/>
</chapter>
<chapter>
<title>Chrooting into the Gentoo Base System</title>
<abstract>
Now that the stage3 file is extracted, we chroot into the new system and modify
the USE variable.
</abstract>
<include href="hb-install-system.xml"/>
</chapter>
<chapter>
<title>Configuring the Kernel</title>
<abstract>
The Linux kernel is the core of every distribution. This chapter
explains how to configure your kernel.
</abstract>
<include href="hb-install-ppc64-kernel.xml"/>
</chapter>
<chapter>
<title>Configuring your System</title>
<abstract>
You need to edit some important configuration files. In this chapter
you receive an overview of these files and an explanation on how to
proceed.
</abstract>
<include href="hb-install-config.xml"/>
1.1
xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-bootloader.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-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-ppc64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: hb-install-ppc64-bootloader.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-bootloader.xml,v
1.1 2005/08/08 13:21:15 swift Exp $ -->
<sections>
<version>5.0</version>
<date>2005-08-08</date>
<section>
<title>Making your Choice</title>
<subsection>
<title>Introduction</title>
<body>
<p>
Now that your kernel is configured and compiled and the necessary system
configuration files are filled in correctly, it is time to install a
program that will fire up your kernel when you start the system. Such a
program is called a <e>bootloader</e>.
</p>
<p>
On Linux/PPC64 we have only yaBoot as a bootloader untill grub2 is
finished.
</p>
</body>
</subsection>
</section>
<section id="yaboot">
<title>Using yaBoot</title>
<subsection>
<title>Introduction</title>
<body>
<impo>
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't
compile on 64bit userland systems. For a 32bit userland use yaboot as you
normally would.
</impo>
<p>
There are two ways to configure yaBoot for your system. You can use the
new and improved <c>yabootconfig</c> included with
<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If
for some reason you do not want to run <c>yabootconfig</c> to
automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo
on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit
the sample file already installed on your system.
</p>
<impo>
If you are installing on a G5 using an online install and have not used the
G5 optimized stages you must change what profile you are linked to now. If you
do not you will not get dependencies necessary for yaboot to run on Apple
equipment. In the command below replace <c>(userland)</c> with your chosen
userland bit level. If you are installing on a G5 using an offline install
you have to install these packages by hand.
</impo>
<pre caption = "(ONLINE INSTALL FOR G5 USERS ONLY) Changing your profile">
# <i>rm /etc/make.profile</i>
# <i>ln -sf
/usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/970/pmac
/etc/make.profile</i>
</pre>
<pre caption = "(OFFLINE INSTALL FOR G5 USERS ONLY) Installing Necessary File
System Tools">
# <i>emerge hfsutils hfsplusutils</i>
</pre>
<pre caption = "Installing the bootloader">
<comment>(64bit userland)</comment>
# <i>emerge --update yaboot-static</i>
<comment>(32bit userland)</comment>
# <i>emerge --update yaboot</i>
</pre>
<impo>
yabootconfig/ybin won't work on IBM. You have to install yaboot another way:
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri>
</impo>
<note>
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a
kernel parameter. JFS must be able to replay its log in read-only mode before it
gets mounted read-write.
</note>
<ul>
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
<li>
<uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri>
</li>
</ul>
</body>
</subsection>
<subsection id="yabootconfig">
<title>Default: Using yabootconfig</title>
<body>
<p>
<c>yabootconfig</c> will auto-detect the partitions on your machine and will
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS
X.
</p>
<p>
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of
these should have been done already in the steps above. To start, ensure that
you have the latest version of yaboot installed by running <c>emerge --update
yaboot-static</c>. This is necessary as the latest version will be available via
Portage, but it may not have made it into the stage files.
</p>
<p>
Now run <c>yabootconfig</c>. The program will run and it will confirm
the location of the bootstrap partition. Type <c>Y</c> if it is correct. If
not, double check <path>/etc/fstab</path>. yabootconfig will then scan your
system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for
you. <c>mkofboot</c> is used to format the bootstrap partition, and install
the yaboot configuration file into it.
</p>
<p>
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If
you make changes to <path>/etc/yaboot.conf</path> (like setting the
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the
bootstrap partition.
</p>
<p>
Now continue with <uri link="#reboot">Rebooting your System</uri>.
</p>
</body>
</subsection>
<subsection id="manual_yaboot">
<title>Alternative: Manual yaBoot Configuration</title>
<body>
<p>
Below you find a completed <path>yaboot.conf</path> file. Alter it at
will.
</p>
<pre caption = "/etc/yaboot.conf">
<comment>## /etc/yaboot.conf
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ
## our bootstrap partition:</comment>
boot=/dev/hda2
<comment>## ofboot is the 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).</comment>
ofboot=hd:2
<comment>## hd: is open firmware speak for hda</comment>
device=hd:
delay=5
defaultos=macosx
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
<comment>#################
## This section can be duplicated if you have more than one kernel or set of
## boot options - replace 2.6.12-gentoo-r4 with your kernel-version
#################</comment>
image=/boot/kernel-2.6.12-gentoo-r4
label=Linux
root=/dev/hda3
partition=3
read-only
macos=hd:13
macosx=hd:12
enablecdboot
enableofboot
</pre>
<p>
Once <path>yaboot.conf</path> is set up the way you want it, you run
<c>mkofboot -v</c> to install the settings in the bootstrap partition.
1.1 xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-disk.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-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-ppc64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: hb-install-ppc64-disk.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-disk.xml,v
1.1 2005/08/08 13:21:15 swift Exp $ -->
<sections>
<version>5.0</version>
<date>2005-08-08</date>
<section>
<title>Introduction to Block Devices</title>
<subsection>
<title>Block Devices</title>
<body>
<p>
We'll take a good look at disk-oriented aspects of Gentoo Linux
and Linux in general, including Linux filesystems, partitions and block devices.
Then, once you're familiar with the ins and outs of disks and filesystems,
you'll be guided through the process of setting up partitions and filesystems
for your Gentoo Linux installation.
</p>
<p>
To begin, we'll introduce <e>block devices</e>. The most famous block device is
probably the one that represents the first IDE drive in a Linux system, namely
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard
drive would be <path>/dev/sda</path>. Serial ATA drives are also
<path>/dev/sda</path> even if they are IDE drives.
</p>
<p>
The block devices above represent an abstract interface to the disk. User
programs can use these block devices to interact with your disk without worrying
about whether your drives are IDE, SCSI or something else. The program can
simply address the storage on the disk as a bunch of contiguous,
randomly-accessible 512-byte blocks.
</p>
</body>
</subsection>
<subsection>
<title>Partitions and Slices</title>
<body>
<p>
Although it is theoretically possible to use a full disk to house your Linux
system, this is almost never done in practice. Instead, full disk block devices
are split up in smaller, more manageable block devices. On most systems,
these are called <e>partitions</e>. Other architectures use a similar technique,
called <e>slices</e>.
</p>
</body>
</subsection>
</section>
<section>
<title>Designing a Partitioning Scheme</title>
<subsection>
<title>Default Partitioning Scheme</title>
<body>
<p>
If you are not interested in drawing up a partitioning scheme for your system,
you can use the partitioning scheme we use throughout this book:
</p>
<table>
<tr>
<th>Partition</th>
<th>Filesystem</th>
<th>Size</th>
<th>Description</th>
</tr>
<tr>
<ti><path>/dev/sda1</path></ti>
<ti>Partition map</ti>
<ti>31.5k</ti>
<ti>Partition map</ti>
</tr>
<tr>
<ti><path>/dev/sda2</path></ti>
<ti>(bootstrap)</ti>
<ti>800k</ti>
<ti>Apple_Bootstrap</ti>
</tr>
<tr>
<ti><path>/dev/sda3</path></ti>
<ti>(swap)</ti>
<ti>512M</ti>
<ti>Swap partition</ti>
</tr>
<tr>
<ti><path>/dev/sda4</path></ti>
<ti>ext3</ti>
<ti>Rest of the disk</ti>
<ti>Root partition</ti>
</tr>
</table>
<note>
There are some partitions named like this: <path>Apple_Driver43,
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 parted in order to delete them, as mac-fdisk can't delete
them yet.
</note>
<p>
If you are interested in knowing how big a partition should be, or even how
many partitions you need, read on. Otherwise continue now with
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition
your Disk</uri>
</p>
</body>
</subsection>
<subsection>
<title>How Many and How Big?</title>
<body>
<p>
The number of partitions is highly dependent on your environment. For instance,
if you have lots of users, you will most likely want to have your
<path>/home</path> separate as it increases security and makes backups easier.
If you are installing Gentoo to perform as a mailserver, your
<path>/var</path> should be separate as all mails are stored inside
<path>/var</path>. A good choice of filesystem will then maximise your
performance. Gameservers will have a separate <path>/opt</path> as most gaming
servers are installed there. The reason is similar for <path>/home</path>:
security and backups. You will definitely want to keep <path>/usr</path> big:
not only will it contain the majority of applications, the Portage tree alone
takes around 500 Mbyte excluding the various sources that are stored in it.
</p>
<p>
As you can see, it very much depends on what you want to achieve. Separate
partitions or volumes have the following advantages:
</p>
<ul>
<li>
You can choose the best performing filesystem for each partition or volume
</li>
<li>
Your entire system cannot run out of free space if one defunct tool is
continuously writing files to a partition or volume
</li>
<li>
If necessary, file system checks are reduced in time, as multiple checks can
be done in parallel (although this advantage is more with multiple disks than
it is with multiple partitions)
</li>
<li>
Security can be enhanced by mounting some partitions or volumes read-only,
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
</li>
</ul>
<p>
However, multiple partitions have one big disadvantage: if not configured
properly, you might result in having a system with lots
of free space on one partition and none on another. There is also a 15-partition
limit for SCSI and SATA.
</p>
</body>
</subsection>
</section>
<section id="mac-fdisk">
<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title>
<body>
<p>
At this point, create your partitions using <c>mac-fdisk</c>:
</p>
<pre caption="Starting mac-fdisk">
# <i>mac-fdisk /dev/sda</i>
</pre>
<p>
First delete the partitions you have cleared previously to make room for your
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s).
It will ask for the partition number to delete.
</p>
<p>
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will
ask for what block you want to start. Enter the number of your first free
partition, followed by a <c>p</c>. For instance this is <c>2p</c>.
</p>
<note>
1.1
xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-kernel.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-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-ppc64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: hb-install-ppc64-kernel.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-kernel.xml,v
1.1 2005/08/08 13:21:15 swift Exp $ -->
<sections>
<version>5.0</version>
<date>2005-08-08</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 PPC64 you should use <c>gentoo-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>
<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
-> linux-2.6.12-gentoo-r4
</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.12-gentoo-r4 linux</i>
</pre>
<p>
Now it is time to configure and compile your kernel source. There is the
ability to use "genkernel" which would create a generic kernel like the
ones used on the live cds, but it is not fully functional for PPC64 at
the moment.
</p>
<p>
Continue now with <uri link="#manual">Manual Configuration</uri>.
</p>
</body>
</subsection>
</section>
<section id="manual">
<title>Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>
<p>
Manually configuring a kernel is often seen as the most difficult procedure a
Linux user ever has to perform. Nothing is less true -- after configuring a
couple of kernels you don't even remember that it was difficult ;)
</p>
<p>
However, one thing <e>is</e> true: you must know your system when you
configuring a kernel manually. Most information can be gathered by emerging
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now
be able to use <c>lspci</c> within the chrooted environment. You may safely
ignore any <e>pcilib</e> warnings (like pcilib: cannot open
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same.
You can also run <c>lsmod</c> to see what kernel modules the Installation CD
uses (it might provide you with a nice hint on what to enable).
</p>
<p>
Now go to your kernel source directory and execute <c>make
menuconfig</c>. This will fire up an ncurses-based configuration menu.
</p>
<p>
When compiling the kernel on a 32bit userland system add the following to
the bottom of /etc/profile:
</p>
<pre caption="32bit userland make alias">
# <i>echo 'alias ppc64make="make ARCH=ppc64
CROSS_COMPILE=powerpc64-unknown-linux-gnu-"' >> /etc/profile</i>
# <i>source /etc/profile</i>
</pre>
<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
(64bit userland) # <i>make menuconfig</i>
(32bit userland) # <i>ppc64make 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 --->
[*] 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>, and <c>/dev/pts file system for
Unix98 PTYs</c>:
</p>
<pre caption="Selecting necessary file systems">
File systems --->
[*] Virtual memory file system support (former shm fs)
[*] /proc file system support
[*] /dev/pts file system for Unix98 PTYs
<comment>(Select one or more of the following options as needed by your
system)</comment>
<*> Reiserfs support
<*> Ext3 journalling file system support
<*> JFS filesystem support
<*> Second extended fs support
<*> XFS filesystem support
</pre>
<note>
You will find some of the mentioned options under <c>Pseudo
filesystems</c> which is a subpart of <c>File systems</c>.
</note>
<p>
If you are using PPPoE to connect to the Internet or you are using a
dial-up modem, you will need the following options in the kernel (you
will find the mentioned options under <c>Networking support</c> which is
a subpart of <c>Device Drivers</c>):
</p>
<pre caption="Selecting PPPoE necessary drivers">
Network device support --->
<*> PPP (point-to-point protocol) support
<*> PPP support for async serial ports
1.1
xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-medium.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-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-ppc64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: hb-install-ppc64-medium.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-medium.xml,v
1.1 2005/08/08 13:21:15 swift Exp $ -->
<sections>
<version>5.0</version>
<date>2005-08-08</date>
<section>
<title>Hardware Requirements</title>
<subsection>
<title>Introduction</title>
<body>
<p>
Before we start, we first list what hardware requirements you need to
successfully install Gentoo on your box.
</p>
</body>
</subsection>
<subsection>
<title>Hardware Requirements</title>
<body>
<table>
<tr>
<th>CPU</th>
<ti>Any PowerPC64 CPU</ti>
</tr>
<tr>
<th>Systems</th>
<ti>
IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower
</ti>
</tr>
<tr>
<th>Memory</th>
<ti>64 MB</ti>
</tr>
<tr>
<th>Diskspace</th>
<ti>1.5 GB (excluding swap space)</ti>
</tr>
<tr>
<th>Swap space</th>
<ti>At least 256 MB</ti>
</tr>
</table>
<p>
For a full list of supported systems, please go to
<uri>http://www.linuxppc64.org/hardware.shtml</uri>.
</p>
</body>
</subsection>
</section>
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ -->
<!-- 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>
<p>
The Gentoo/PPC64 team provides you with additional options at this point.
You have the choice to use a 32bit or a 64bit userland; a full set of stages
is provided for both options.
</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-ppc64.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 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/ppc/2005.1/ppc64/installcd</path> directory;
the Package CDs are located in the
<path>releases/ppc/2005.1/ppc64/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>
--
[email protected] mailing list
