From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.43)
id 1DyBSi-0006Ap-VZ
for garchives@archives.gentoo.org; Thu, 28 Jul 2005 16:42:26 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6SGfmDp007128;
Thu, 28 Jul 2005 16:41:48 GMT
Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30])
by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6SGflgC005964
for <gentoo-doc-cvs@lists.gentoo.org>; Thu, 28 Jul 2005 16:41:48 GMT
Message-Id: <200507281641.j6SGflgC005964@robin.gentoo.org>
Received: from lark.gentoo.osuosl.org ([140.211.166.177] helo=lark.gentoo.org)
by smtp.gentoo.org with smtp (Exim 4.43)
id 1DyBSb-0000b8-3S
for gentoo-doc-cvs@lists.gentoo.org; Thu, 28 Jul 2005 16:42:17 +0000
Received: by lark.gentoo.org (sSMTP sendmail emulation); Thu, 28 Jul 2005 16:42:03 +0000
From: "Joseph Jezak" <josejx@lark.gentoo.org>
Date: Thu, 28 Jul 2005 16:42:03 +0000
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: hb-install-ppc-bootloader.xml
Precedence: bulk
List-Post: <mailto:gentoo-doc-cvs@lists.gentoo.org>
List-Help: <mailto:gentoo-doc-cvs+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-doc-cvs+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-doc-cvs+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-doc-cvs.gentoo.org>
X-BeenThere: gentoo-doc-cvs@gentoo.org
Reply-to: docs-team@lists.gentoo.org
X-Archives-Salt: b69d5198-b68b-4e0c-808b-dc4cda5dd582
X-Archives-Hash: 68a7a9d9fe53d50af7c1f3c4ed35cc82
josejx 05/07/28 16:42:03
Modified: xml/htdocs/doc/en/handbook/draft/2005.1
hb-install-ppc-bootloader.xml
hb-install-ppc-disk.xml hb-install-ppc-medium.xml
Log:
Yoswink, please don't stab me. (PPC 2005.1 handbook updates.)
Revision Changes Path
1.2 +195 -51 xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: hb-install-ppc-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-ppc-bootloader.xml 5 Jul 2005 08:02:04 -0000 1.1
+++ hb-install-ppc-bootloader.xml 28 Jul 2005 16:42:03 -0000 1.2
@@ -4,7 +4,7 @@
<!-- 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/draft/2005.1/hb-install-ppc-bootloader.xml,v 1.1 2005/07/05 08:02:04 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml,v 1.2 2005/07/28 16:42:03 josejx Exp $ -->
<sections>
@@ -12,25 +12,23 @@
<date>2005-03-19</date>
<section>
-<title>Making your Choice</title>
+<title>Choosing a Bootloader</title>
<subsection>
<title>Introduction</title>
<body>
<p>
-Now that your kernel is configured and compiled and the necessary system
-configuration files are filled in correctly, it is time to install a
-program that will fire up your kernel when you start the system. Such a
-program is called a <e>bootloader</e>. But before you start, consider
-your options...
+Now that the kernel is configured and compiled, you'll need a <e>bootloader</e>
+to start your new linux installation. The <e>bootloader</e> that you use will
+depend upon the type of PPC machine you have.
</p>
<p>
-Several bootloaders exist for Linux/PPC. We have <uri link="#yaboot">yaboot</uri>
-(for NewWorld Apple and IBM machines) and <uri link="#bootx">BootX</uri> (for
-OldWorld Apple and IBM machines). The Pegasos does not require a bootloader, but
-we included the <uri link="#bootcreator">BootCreator</uri> for creating a
-SmartFirmware bootmenu.
+If you are using a NewWorld Apple or IBM machine, you need to use
+<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options,
+<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>.
+The Pegasos does not require a bootloader, but you will need to emerge
+<uri link="#bootcreator">BootCreator</uri> to create SmartFirmware bootmenus.
</p>
</body>
@@ -47,9 +45,9 @@
</impo>
<p>
-First we have to create the <path>/dev</path> files in our new home, which is
-needed during the bootloader installation. This could be done by "bind"-mapping
-the <path>/dev</path>-filesystem from the Installation CD:
+In order to find the boot devices, yaboot needs access to the <path>/dev</path>
+filesystem. To do this, you will need to "bind-map" the <path>/dev</path>
+filesystem from the Installation CD to <path>/dev</path> inside of the chroot.
</p>
<pre caption="Bind-mounting the /dev-filesystem">
@@ -60,14 +58,35 @@
</pre>
<p>
-There are two ways to configure yaboot for your system. You can use the
-included <c>yabootconfig</c> to automatically set up yaboot. If
-for some reason you do not want to run <c>yabootconfig</c> to
-automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo
-on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit
-the sample file already installed on your system.
+To set up yaboot, you can use <c>yabootconfig</c> to automatically create a
+configuration file for you. If you are installing Gentoo on a G5 (where
+<c>yabootconfig</c> does not always work), or you plan to boot from firewire
+or USB, you will need to manually configure yaboot.
</p>
+<note>
+You will need to manually edit the yaboot.conf when using genkernel, even if
+yabootconfig is used. The kernel image section of yaboot.conf should be
+modified as follows:
+</note>
+
+<pre caption="Adding genkernel boot arguments to yaboot.conf">
+<comment>###########################################################
+## This section can be duplicated if you have more than one
+## kernel or set of boot options - replace kernel-2.6.12
+## with the exact filename of your kernel.
+###########################################################</comment>
+image=/boot/kernel-2.6.12
+ label=Linux
+ root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment>
+ partition=3
+ append="real_root=/dev/hda3 init=/linuxrc"
+ <comment># You can add additional kernel arguments to append such as
+ # rootdelay=10 for a USB/Firewire Boot</comment>
+ read-only
+<comment>##########################################################</comment>
+</pre>
+
<ul>
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
<li>
@@ -138,10 +157,10 @@
</pre>
<p>
-Below you find a completed <path>yaboot.conf</path> file. Alter it at
-will. G5 users should be aware that their disks are Serial ATA disks which are
-seen as SCSI disks by the Linux kernel (so substitute <path>/dev/hda</path> with
-<path>/dev/sda</path>).
+An example <path>yaboot.conf</path> file is given below, but you will need to
+alter it to fit your needs. G5 users and users booting from firewire and USB
+should be aware that their disks are seen as SCSI disks by the Linux kernel, so
+you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>).
</p>
<pre caption = "/etc/yaboot.conf">
@@ -166,9 +185,21 @@
#ofboot=hd:2
-## hd: is open firmware speak for hda</comment>
+## Users booting from firewire should use something like this line:
+# ofboot=fw/node/sbp-2/disk@0:
+
+## Users booting from USB should use something like this line:
+# ofboot=usb/disk@0:
+
+## hd: is shorthand for the first hard drive OpenFirmware sees</comment>
device=hd:
+<comment>## Firewire and USB users will need to specify the whole OF device name
+## This can be found using ofpath, which is included with yaboot.
+
+# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0:
+</comment>
+
delay=5
defaultos=macosx
timeout=30
@@ -183,7 +214,7 @@
label=Linux
root=/dev/hda3
partition=3
- sysmap=/boot/System.map-2.6.9
+<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment>
read-only
<comment>##################
@@ -198,17 +229,10 @@
</pre>
<p>
-Once <path>yaboot.conf</path> is set up the way you want it, you run
-<c>mkofboot -v</c> to install the settings in the bootstrap partition. <e>Don't
-forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new
-filesystem.
-</p>
-
-<p>
-If all goes well, and you have the same options as the sample
-above, your next reboot will give you a simple, five-entry boot menu. If you
-update your yaboot config later on, you'll just need to run <c>ybin -v</c> to
-update the bootstrap partition - <c>mkofboot</c> is for initial setup only.
+Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format
+the Apple_bootstrap partition and install the settings. If you change
+yaboot.conf after the Apple_bootstrap partition has been created, you can
+update the settings by running <c>ybin -v</c>
</p>
<p>
@@ -226,22 +250,44 @@
<body>
<impo>
-BootX can only be used on OldWorld Apple and IBM systems!
+BootX can only be used on OldWorld Apple systems!
</impo>
<p>
-BootX requires that you reboot first. So, let's reboot shall we :)
+Since BootX boots Linux from within MacOS, the kernel will need to be copied
+from the Linux Partition to the MacOS partition. First, mount the MacOS
+partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the
+MacOS partition number, sda6 is used as an example here. Once the partition is
+mounted, we'll copy the kernel to the system folder so BootX can find it.
</p>
+<pre caption="Copying the kernel to the MacOS partition">
+# <i>exit</i>
+cdimage ~# <i>mkdir /mnt/mac</i>
+cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
+cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i>
+</pre>
1.2 +24 -25 xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: hb-install-ppc-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-ppc-disk.xml 5 Jul 2005 08:02:04 -0000 1.1
+++ hb-install-ppc-disk.xml 28 Jul 2005 16:42:03 -0000 1.2
@@ -4,7 +4,7 @@
<!-- 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/draft/2005.1/hb-install-ppc-disk.xml,v 1.1 2005/07/05 08:02:04 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml,v 1.2 2005/07/28 16:42:03 josejx Exp $ -->
<sections>
@@ -43,15 +43,14 @@
</body>
</subsection>
<subsection>
-<title>Partitions and Slices</title>
+<title>Partitions</title>
<body>
<p>
Although it is theoretically possible to use a full disk to house your Linux
system, this is almost never done in practice. Instead, full disk block devices
are split up in smaller, more manageable block devices. On most systems,
-these are called <e>partitions</e>. Other architectures use a similar technique,
-called <e>slices</e>.
+these are called <e>partitions</e>.
</p>
</body>
@@ -106,8 +105,8 @@
<ti>Type 0x41</ti>
</tr>
<tr>
- <ti>(Not needed)</ti>
- <ti>(Not needed)</ti>
+ <ti>(Not applicable)</ti>
+ <ti><path>/dev/hda2</path> (If using quik)</ti>
<ti><path>/dev/hda1</path></ti>
<ti>(Not needed)</ti>
<ti>ext2</ti>
@@ -116,7 +115,7 @@
</tr>
<tr>
<ti><path>/dev/hda3</path></ti>
- <ti><path>/dev/hda2</path></ti>
+ <ti><path>/dev/hda2</path> (<path>/dev/hda3</path> if using quik)</ti>
<ti><path>/dev/hda2</path></ti>
<ti><path>/dev/sda2</path></ti>
<ti>(swap)</ti>
@@ -125,7 +124,7 @@
</tr>
<tr>
<ti><path>/dev/hda4</path></ti>
- <ti><path>/dev/hda3</path></ti>
+ <ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti>
<ti><path>/dev/hda3</path></ti>
<ti><path>/dev/sda3</path></ti>
<ti>ext3, xfs</ti>
@@ -135,11 +134,11 @@
</table>
<note>
-There are some partitions named like this: <path>Apple_Driver43,
-Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If
-you are not planning to use MacOS 9 you can delete them, because MacOS X and
-Linux don't need them. You might have to use <c>parted</c> in order to delete
-them, as mac-fdisk can't delete them yet.
+There are some partitions named: <path>Apple_Driver63, 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. To delete them, either use parted or erase the whole disk by
+initialing the partition map.
</note>
<warn>
@@ -152,9 +151,9 @@
<p>
If you are interested in knowing how big a partition should be, or even how many
-partitions you need, read on. Otherwise continue now with <uri
-link="#fdisk">Default: Using mac-fdisk (Apple/IBM) to Partition your Disk</uri>
-or <uri link="#parted">Alternative: Using parted (especially Pegasos) to
+partitions you need, read on. Otherwise continue now with
+<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk
+</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to
Partition your Disk</uri>.
</p>
@@ -212,7 +211,7 @@
</body>
</subsection>
</section>
-<section id="fdisk">
+<section id="mac-fdisk">
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title>
<body>
@@ -372,9 +371,8 @@
<body>
<p>
-Several filesystems are available. ext2, ext3 and XFS are found stable on the
-PPC architecture. jfs is unsupported, ReiserFS still has some problems on ppc
-and is not supported.
+Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found
+stable on the PPC architecture.
</p>
<p>
@@ -403,8 +401,7 @@
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. Unfortunately we still have some
-issues with ReiserFS on ppc. We do not encourage people to use this filesystem.
+files and directories containing tens of thousands of files.
</p>
<p>
@@ -466,9 +463,11 @@
</p>
<note>
-On OldWorld machines and the PegasosII your partition which holds the kernel must
-be ext2 or ext3. NewWorld machines can boot from any of ext2, ext3, XFS,
-ReiserFS or even HFS/HFS+ filesystems.
+On the PegasosII your partition which holds the kernel must be ext2 or ext3.
+NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or even
+HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel must
+be placed on an HFS partition, but this will be completed when you configure
+your bootloader.
</note>
</body>
1.3 +73 -28 xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: hb-install-ppc-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hb-install-ppc-medium.xml 5 Jul 2005 09:07:02 -0000 1.2
+++ hb-install-ppc-medium.xml 28 Jul 2005 16:42:03 -0000 1.3
@@ -4,7 +4,7 @@
<!-- 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/draft/2005.1/hb-install-ppc-medium.xml,v 1.2 2005/07/05 09:07:02 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml,v 1.3 2005/07/28 16:42:03 josejx Exp $ -->
<sections>
@@ -30,16 +30,30 @@
<table>
<tr>
- <th>NewWorld machines</th>
+ <th>Apple NewWorld Machines</th>
<ti>
Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook
- PowerBook, Xserver, PowerMac, Genesi's Pegasos II
+ PowerBook, Xserver, PowerMac
</ti>
</tr>
<tr>
- <th>OldWorld machines</th>
+ <th>Apple OldWorld machines</th>
<ti>
- Limited support for IBM (RS/6000, iSeries, pSeries) and Amiga systems
+ Apple Machines with an OpenFirmware revision less than 3, such as the Beige
+ G3s, PCI PowerMacs and PCI PowerBooks. PCI based Apple Clones should also
+ be supported.
+ </ti>
+</tr>
+<tr>
+ <th>Genesi's Pegasos</th>
+ <ti>
+ Pegasos I/II, Open Desktop Workstation
+ </ti>
+</tr>
+<tr>
+ <th>IBM</th>
+ <ti>
+ RS/6000, iSeries, pSeries
</ti>
</tr>
<tr>
@@ -182,8 +196,8 @@
<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
+ <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows).
+ Verifying MD5 checksums with Mac OS X is described in the <uri
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>.
</li>
<li>
@@ -231,7 +245,7 @@
</body>
</subsection>
<subsection>
-<title>Default: Booting the Universal Installation CD on an Apple/IBM</title>
+<title>Default: Booting the Installation CD with Yaboot</title>
<body>
<p>
@@ -241,25 +255,6 @@
</p>
<p>
-If you have an OldWorld Mac the bootable portion of the Installation CD can't
-be used. Instead you need to download <uri
-link="http://penguinppc.org/projects/bootx/">BootX</uri> and have a working
-MacOS installed on your system. You need to copy the <c>BootX Extension</c> from
-the unpacked archive-file into the <c>Extensions Folder</c> and make a new
-directory called <c>Linux Kernels</c> in the System Folder. In the next step you
-need to copy the files <c>G3G4</c> and <c>G3G4.igz</c> from the
-Installation CD <path>boot</path> folder into the <c>Linux Kernels</c>
-directory. Then reboot the system and wait for BootX to load. After BootX
-loaded you still have to set up a few items. In the options dialog you need
-to check <c>Use Specified RAM Disk</c> and select the <c>G3G4.igz</c>
-which you put in the <c>Linux Kernels</c> directory. The ramdisk size should
-be set to at least <c>32000</c>.
-Furthermore the kernel argument needs to be set to <c>rw init=/linuxrc
-cdroot</c>. Eventually you are able to boot the Installation CD when you
-select Linux on Startup.
-</p>
-
-<p>
After the Installation CD loaded, you will be greeted by a friendly welcome
message and a <e>boot:</e> prompt at the bottom of the screen.
</p>
@@ -321,7 +316,7 @@
</body>
</subsection>
<subsection>
-<title>Alternative: Booting the Universal Installation CD on a Pegasos</title>
+<title>Alternative: Booting the Installation CD on a Pegasos</title>
<body>
<p>
@@ -337,6 +332,56 @@
</body>
</subsection>
+
+<subsection>
+<title>Alternative: Booting the Installation CD with BootX</title>
+<body>
+
+<p>
+If you have an OldWorld Mac the bootable portion of the livecd can't be used.
+The most simple solution is to use MacOS to bootstrap into a Linux environment
+with a tool called BootX. Boot floppies are being prepared for Macs without
+MacOS, but they are not available at this time.
+</p>
+
+<p>
+First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri>
+and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked
+archive into <c>Extensions Folder</c> and the BootX App Control Panel into
+<c>Control Panels</c>, both of which are located in your MacOS System Folder.
+Next, create a folder called "Linux Kernels" in your System folder and copy the
+<c>G3G4</c> kernel from the CD to this folder. Finally, copy <c>G3G4.igz</c>
+from the Installation CD <path>boot</path> folder into the MacOS
+<c>System Folder</c>.
+</p>
+
+<p>
+To prepare BootX, start the BootX App Control Panel. First select the Options
+dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from
+your System Folder. Continue back to the initial screen and ensure that the
+ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as
+shown below:
+</p>
+
+<pre caption="BootX kernel arguments">
+cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev
+</pre>
+
+<note>
+The kernel parameters in the yaboot section above are also applicable here.
+</note>
+
+<p>
+Check once more to make sure the settings are correct and then save the
+configuration. This saves typing just in case it doesn't boot or something is
+missing. Press the Linux button at the top of the window to boot into the
+Installation CD and continue with <uri link="#booted">And When
+You're Booted...</uri>
+</p>
+
+</body>
+</subsection>
+
<subsection id="booted">
<title>And When You're Booted...</title>
<body>
--
gentoo-doc-cvs@gentoo.org mailing list