[gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: handbook-ppc.xml hb-install-ppc-bootloader.xml hb-install-ppc-disk.xml hb-install-ppc-kernel.xml hb-install-ppc-medium.xml

[Joshua Saddler (nightmorph)]

nightmorph    10/07/21 00:52:41

  Modified:             handbook-ppc.xml hb-install-ppc-bootloader.xml
                        hb-install-ppc-disk.xml hb-install-ppc-kernel.xml
                        hb-install-ppc-medium.xml
  Log:
  Update the PPC handbook for the autobuilds. Major version bump for this release. Fixes bug 260403, bug 292726, and bug 234310.

Revision  Changes    Path
1.158                xml/htdocs/doc/en/handbook/handbook-ppc.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.158&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.158&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml?r1=1.157&r2=1.158

Index: handbook-ppc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v
retrieving revision 1.157
retrieving revision 1.158
diff -u -r1.157 -r1.158
--- handbook-ppc.xml	6 Jul 2008 08:00:30 -0000	1.157
+++ handbook-ppc.xml	21 Jul 2010 00:52:41 -0000	1.158
@@ -1,21 +1,24 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.157 2008/07/06 08:00:30 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.158 2010/07/21 00:52:41 nightmorph Exp $ -->
 
 <book>
 <title>Gentoo Linux PPC Handbook</title>
 
 <values>
  <key id="arch">PPC</key>
- <key id="kernel-version">2.6.24-r5</key>
- <key id="kernel-name">kernel-2.6.24-gentoo-r5</key>
- <key id="kernel-gentoo">2.6.24-gentoo-r5</key>
- <key id="online-book">handbook-ppc.xml</key>
- <key id="release-dir">releases/ppc/2008.0/</key>
- <key id="stage3">stage3-ppc-2008.0.tar.bz2</key>
- <key id="profile">default/linux/ppc/ppc32/2008.0</key>
+ <key id="genkernel-name">kernel-genkernel-ppc-2.6.33-gentoo-r2</key>
+ <key id="genkernel-initrd">initramfs-genkernel-ppc-2.6.33-gentoo-r2</key>
+ <key id="kernel-version">2.6.33-r2</key>
+ <key id="kernel-name">kernel-2.6.33-gentoo-r2</key>
+ <key id="min-cd-name">install-powerpc-minimal-&lt;release&gt;.iso</key>
+ <key id="min-cd-size">105</key>
+ <key id="release-dir">releases/ppc/autobuilds/</key>
+ <key id="stage3">stage3-ppc-&lt;release&gt;.tar.bz2</key>
+ <key id="profile">default/linux/powerpc/ppc32/10.0</key>
  <key id="CFLAGS">-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe</key>
+ <key id="online-book">handbook-ppc.xml</key>
 </values>
 
 <author title="Author">
@@ -142,8 +145,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>9.4</version>
-<date>2008-07-06</date>
+<version>10.0</version>
+<date>2010-07-20</date>
 
 <part>
 <title>Installing Gentoo</title>



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

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml?rev=1.46&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml?rev=1.46&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml?r1=1.45&r2=1.46

Index: hb-install-ppc-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- hb-install-ppc-bootloader.xml	2 May 2008 08:04:23 -0000	1.45
+++ hb-install-ppc-bootloader.xml	21 Jul 2010 00:52:41 -0000	1.46
@@ -4,23 +4,28 @@
 <!-- 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-ppc-bootloader.xml,v 1.45 2008/05/02 08:04:23 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.46 2010/07/21 00:52:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>9.1</version>
-<date>2008-05-02</date>
+<version>10.0</version>
+<date>2010-07-20</date>
 
 <section>
-<title>Choosing a Bootloader</title>
+<title>Making your Choice</title>
 <subsection>
 <title>Introduction</title>
 <body>
 
 <p>
-Now that the kernel is configured and compiled, you'll need a <e>bootloader</e>
-to start your new linux installation.  The <e>bootloader</e> that you use will 
-depend upon the type of PPC machine you have.
+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>
+The bootloader that you use will depend upon the type of PPC machine you have.
 </p>
 
 <p>
@@ -65,15 +70,16 @@
 <p>
 To set up yaboot, you can use <c>yabootconfig</c> to automatically create a
 configuration file for you. If you are installing Gentoo on a G5 (where 
-<c>yabootconfig</c> does not always work), or you plan to boot from firewire 
+<c>yabootconfig</c> does not always work), or you plan to boot from FireWire 
 or USB, you will need to manually configure yaboot.
 </p>
 
 <note>
-You will need to manually edit the yaboot.conf when using genkernel, even if
-yabootconfig is used.  The kernel image section of yaboot.conf should be
-modified as follows (using vmlinux and initrd as the name of kernel and 
-initrd image):
+You will need to manually edit the <path>yaboot.conf</path> when using
+<c>genkernel</c>, even if <c>yabootconfig</c> is used. The kernel image section
+of <path>yaboot.conf</path> should be modified as follows (using
+<path>vmlinux</path> and <path>initrd</path> as the name of kernel and
+<path>initrd</path> image):
 </note>
 
 <pre caption="Adding genkernel boot arguments to yaboot.conf">
@@ -82,11 +88,11 @@
 ## kernel or set of boot options - replace the image and initrd
 ## with the exact filename of your kernel and initrd image.
 ###########################################################</comment>
-image=/boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/>
+image=/boot/<keyval id="genkernel-name"/>
   label=Linux
   root=/dev/ram0
   partition=3
-  initrd=/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/>
+  initrd=/boot/<keyval id="genkernel-initrd"/>
   <comment># You can add additional kernel arguments to append such as 
   # rootdelay=10 for a USB/Firewire Boot</comment>
   append="real_root=/dev/sda3 init=/linuxrc"  
@@ -125,14 +131,15 @@
 </pre>
 
 <p>
-Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First,
-the program will confirm the location of the bootstrap partition.  If you are
-using the suggested disk partitioning scheme, your bootstrap partition should
-be /dev/sda2. Type <c>Y</c> if the output is correct. If not, double check your
-<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup, 
-create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. 
-<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install 
-the yaboot configuration file into it.  After this enter the chroot again.
+Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First, the
+program will confirm the location of the bootstrap partition. If you are using
+the suggested disk partitioning scheme, your bootstrap partition should be
+<path>/dev/sda2</path>. Type <c>Y</c> if the output is correct. If not, double
+check your <path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your
+system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for
+you.  <c>mkofboot</c> is used to format the Apple_Bootstrap partition, and
+install the yaboot configuration file into it. After this enter the chroot
+again.
 </p>
 
 <pre caption="Re-enter the chroot">
@@ -291,8 +298,8 @@
 # <i>exit</i>
 cdimage ~# <i>mkdir /mnt/mac</i>
 cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
-cdimage ~# <i>cp /mnt/gentoo/boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> "/mnt/mac/System Folder/Linux Kernels"</i>
-cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/> "/mnt/mac/System Folder"</i>
+cdimage ~# <i>cp /mnt/gentoo/boot/<keyval id="genkernel-name"/> "/mnt/mac/System Folder/Linux Kernels"</i>
+cdimage ~# <i>cp /mnt/gentoo/boot/<keyval id="genkernel-initrd"/> "/mnt/mac/System Folder"</i>
 </pre>
 
 <p>
@@ -345,14 +352,14 @@
 <body>
 
 <p>
-quik allows OldWorld Macs to boot without MacOS.  However, it isn't well
-supported and has a number of quirks.  If you have the option, it is recommended
+<c>quik</c> allows OldWorld Macs to boot without MacOS. However, it isn't well
+supported and has a number of quirks. If you have the option, it is recommended
 that you use BootX instead since it is much more reliable and easier to set up
 than quik.
 </p>
 
 <p>
-First, we'll need to install quik:
+First, we'll need to install <c>quik</c>:
 </p>
 
 <pre caption="Emerge quik">
@@ -366,7 +373,7 @@
 
 <pre caption="Configuring quik.conf">
 # Example of quik.conf
-init-message = "Gentoo 2008.0\n"
+init-message = "Gentoo Linux\n"
 <comment># This is the boot partition</comment>
 partition = 2
 root = /dev/sda4
@@ -378,9 +385,9 @@
 </pre>
 
 <p>
-Your quik.conf file <e>must</e> be on the same disk as the quik boot images,
-however it can be on a different partition on the same disk, although it is
-recommended to move it to your boot partition.
+Your <path>quik.conf</path> file <e>must</e> be on the same disk as the quik
+boot images, however it can be on a different partition on the same disk,
+although it is recommended to move it to your boot partition.
 </p>
 
 <pre caption="Moving quik.conf to /boot">
@@ -493,7 +500,8 @@
 
 [SECTION]
 Local HD -> Genkernel (Normal)
-ide:0 kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> root=/dev/ram0 real_root=/dev/sda3 init=/linuxrc initrd=initramfs-genkernel-ppc<keyval id="kernel-gentoo"/>
+ide:0 <keyval id="genkernel-name"/> root=/dev/ram0
+real_root=/dev/sda3 init=/linuxrc initrd=<keyval id="genkernel-initrd"/>
 </pre>
 
 <p>



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

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml?rev=1.48&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml?rev=1.48&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml?r1=1.47&r2=1.48

Index: hb-install-ppc-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- hb-install-ppc-disk.xml	2 May 2008 08:04:23 -0000	1.47
+++ hb-install-ppc-disk.xml	21 Jul 2010 00:52:41 -0000	1.48
@@ -4,12 +4,12 @@
 <!-- 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-ppc-disk.xml,v 1.47 2008/05/02 08:04:23 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.48 2010/07/21 00:52:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>9.1</version>
-<date>2008-05-02</date>
+<version>10.0</version>
+<date>2010-07-20</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -52,34 +52,33 @@
 <body>
 
 <p>
-Apple New World machines are fairly straightforward to configure.  The first
-partition is always an <e>Apple Partition Map</e>.  This partition keeps track
-of the layout of the disk.  You cannot remove this partition.  The next
-partition should always be a bootstrap partition.  This partition contains a
-small (800k) HFS filesystem that holds a copy of the bootloader Yaboot and its
-configuration file.  This partition is <e>not</e> the same as a 
-<path>/boot</path> partition as found on other architectures.  After the boot
-partition, the usual Linux filesystems are placed, according to the scheme
-below.  The swap partition is a temporary storage place for when your system
-runs out of physical memory.  The root partition will contain the filesystem
-that Gentoo is installed on.  If you wish to dual boot, the OSX partition 
-can go anywhere after the bootstrap partition to insure that yaboot starts 
-first.
+Apple New World machines are fairly straightforward to configure. The first
+partition is always an <e>Apple Partition Map</e>. This partition keeps track of
+the layout of the disk. You cannot remove this partition. The next partition
+should always be a bootstrap partition. This partition contains a small (800k)
+HFS filesystem that holds a copy of the bootloader Yaboot and its configuration
+file. This partition is <e>not</e> the same as a <path>/boot</path> partition as
+found on other architectures. After the boot partition, the usual Linux
+filesystems are placed, according to the scheme below. The swap partition is a
+temporary storage place for when your system runs out of physical memory. The
+root partition will contain the filesystem that Gentoo is installed on. If you
+wish to dual boot, the OSX partition can go anywhere after the bootstrap
+partition to insure that yaboot starts first.
 </p>
 
 <note>
 There may be "Disk Driver" partitions on your disk such as
 <path>Apple_Driver63</path>, <path>Apple_Driver_ATA</path>,
 <path>Apple_FWDriver</path>, <path>Apple_Driver_IOKit</path>, and
-<path>Apple_Patches</path>.  These are used to boot MacOS, so if you have no
-need for this, you can remove them by initializing the disk with mac-fdisk's
-<c>i</c> option.  This will completely erase the disk!  If you are in doubt,
-just let them be.
+<path>Apple_Patches</path>. These are used to boot MacOS, so if you have no need
+for this, you can remove them by initializing the disk with <c>mac-fdisk</c>'s
+<c>i</c> option. This will completely erase the disk! If you are in doubt, just
+let them be.
 </note>
 
 <note>
 If you partitioned this disk with Apple's Disk Utility, there may be
-128Mb spaces between partitions which Apple reserves for "future use".  You
+128Mb spaces between partitions which Apple reserves for "future use". You
 can safely remove these.
 </note>
 
@@ -340,11 +339,11 @@
 
 <p>
 If you used Apple's Disk Utility to leave space for Linux, first delete the
-partitions you have created previously to make room for your new install.  Use
-<c>d</c> in <c>mac-fdisk</c> to delete those partition(s).  It will ask for the
-partition number to delete.  Usually the first partition on NewWorld machines
-(Apple_partition_map) could not be deleted. If you would like to start with a 
-clean disk, you can simply initialize the disk by pressing  <c>i</c>.  This 
+partitions you have created previously to make room for your new install. Use
+<c>d</c> in <c>mac-fdisk</c> to delete those partition(s). It will ask for the
+partition number to delete. Usually the first partition on NewWorld machines
+(Apple_partition_map) cannot be deleted. If you would like to start with a 
+clean disk, you can simply initialize the disk by pressing <c>i</c>. This 
 will completely erase the disk, so use this with caution.
 </p>
 
@@ -383,10 +382,10 @@
 
 <note>
 To make sure everything is ok, you should run <c>mac-fdisk -l</c> and check
-whether all the partitions are there. If you don't see any of the partitions
-you created, or the changes you made, you should reinitialize your partitions
-by pressing "i" in mac-fdisk. Note that this will recreate the partition map
-and thus remove all your partitions.
+whether all the partitions are there. If you don't see any of the partitions you
+created, or the changes you made, you should reinitialize your partitions by
+pressing <c>i</c> in <c>mac-fdisk</c>. Note that this will recreate the
+partition map and thus remove all your partitions.
 </note>
 
 <p>
@@ -402,7 +401,7 @@
 
 <p>
 <c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by
-Mac OS and Mac OS X.  With this tool you can resize your Mac-partitions and
+Mac OS and Mac OS X.  With this tool you can resize your Mac partitions and
 create space for your Linux partitions.  Nevertheless, the example below
 describes partitioning for Pegasos machines only.
 </p>
@@ -423,7 +422,7 @@
 <p>
 You can type <c>print</c> at any time in parted to display the current partition
 table. If at any time you change your mind or made a mistake you can press
-<c>Ctrl-c</c> to abort parted.
+<c>Ctrl-c</c> to abort <c>parted</c>.
 </p>
 
 <p>
@@ -436,7 +435,7 @@
 <c>END</c> should be replaced with the megabyte range (e.g. <c>0 32</c>) which
 creates a 32 MB partition starting at 0MB and ending at 32MB.  If you chose to
 create an ext2 or ext3 partition instead, substitute ext2 or ext3 for affs1 in
-the mkpart command.
+the <c>mkpart</c> command.
 </p>
 
 <p>
@@ -454,7 +453,7 @@
 </p>
 
 <p>
-When you are done in parted simply type <c>quit</c>.
+When you are done in <c>parted</c> simply type <c>quit</c>.
 </p>
 
 </body>



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

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.61&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.61&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?r1=1.60&r2=1.61

Index: hb-install-ppc-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- hb-install-ppc-kernel.xml	21 Aug 2008 14:47:23 -0000	1.60
+++ hb-install-ppc-kernel.xml	21 Jul 2010 00:52:41 -0000	1.61
@@ -4,12 +4,12 @@
 <!-- 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-ppc-kernel.xml,v 1.60 2008/08/21 14:47:23 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.61 2010/07/21 00:52:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>9.1</version>
-<date>2008-08-21</date>
+<version>10.0</version>
+<date>2010-07-20</date>
 
 <section>
 <title>Timezone</title>
@@ -41,13 +41,18 @@
 <p>
 The core around which all distributions are built is the Linux kernel. It is the
 layer between the user programs and your system hardware. Gentoo provides its
-users several possible kernels to choose from. A full listing with description
-is available at the
-<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>.
+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>
-We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel.
+For <keyval id="arch"/>-based systems we have <c>gentoo-sources</c>
+(kernel source patched for extra features).
+</p>
+
+<p>
+Choose your kernel source and install it using <c>emerge</c>.
 </p>
 
 <pre caption="Installing a kernel source">
@@ -55,22 +60,22 @@
 </pre>
 
 <p>
-If you take a look in <path>/usr/src</path> you should see a symlink named
-<path>linux</path> pointing to your current kernel source. In this case, the
-installed kernel source points to <c>gentoo-sources-<keyval
-id="kernel-version"/></c>. Your version may be different, so keep this in mind.
+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           22  Mar 18 16:23 /usr/src/linux -&gt; linux-<keyval id="kernel-gentoo"/>
+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
-a more efficient configuration.
+the best way to optimize your environment.
 </p>
 
 <p>
@@ -97,17 +102,14 @@
 
 <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 the program
-<c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted
-environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib:
-cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively,
-you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results
-are the same. You can also run <c>lsmod</c> to see what kernel modules the
-Installation CD uses (it might provide you with a nice hint on what to enable).
-Another place to look for clues as to what components to enable is to check the
-kernel message logs from the successful boot that got you this far.  Type
-<c>dmesg</c> to see these kernel messages.
+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>
@@ -140,7 +142,7 @@
 First go to <c>File Systems</c> and select support for the filesystems you use.
 <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
 able to mount your partitions. Also select the <c>/proc file system</c> and
-<c>Virtual memory</c>.  Make sure that you also enable support for Amiga
+<c>Virtual memory</c>. Make sure that you also enable support for Amiga
 partitions if you are using a Pegasos, or Macintosh partitions if you are using
 an Apple computer.
 </p>
@@ -164,7 +166,7 @@
 </pre>
 
 <p>
-Users of NewWorld and OldWorld machines will want HFS support as well.  OldWorld
+Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld
 users require it for copying compiled kernels to the MacOS partition. NewWorld
 users require it for configuring the special Apple_Bootstrap partition:
 </p>
@@ -196,8 +198,8 @@
 </p>
 
 <p>
-Don't forget to include support in the kernel for your ethernet card!  Most
-newer Apple computers use the SunGEM ethernet driver.  Older iMacs commonly use
+Don't forget to include support in the kernel for your ethernet card! Most
+newer Apple computers use the SunGEM ethernet driver. Older iMacs commonly use
 the BMAC driver.
 </p>
 
@@ -214,8 +216,8 @@
 
 <p>
 At this time, full kernel preemption may still be unstable on PPC and may cause
-compilation failures and random segfaults.  It is <e>strongly</e> suggested
-that you do not use this feature.  Both <e>Voluntary Preemption</e> and
+compilation failures and random segfaults. It is <e>strongly</e> suggested
+that you do not use this feature. Both <e>Voluntary Preemption</e> and
 <e>No Forced Preemption</e> should be safe.
 </p>
 
@@ -228,12 +230,12 @@
 </pre>
 
 <p>
-If you're booting from Firewire, you'll need to enable these options. If you do
+If you're booting from FireWire, you'll need to enable these options. If you do
 not want to compile in support, you'll need to include these modules and their
 dependencies in an initrd.
 </p>
 
-<pre caption="Enable support for firewire devices on boot">
+<pre caption="Enable support for FireWire devices on boot">
 Device Drivers ---&gt;
   IEEE 1394 (FireWire) support ---&gt;
     &lt;*&gt; IEEE 1394 (FireWire) support
@@ -257,8 +259,8 @@
 
 <p>
 Do not turn off kernel framebuffer support as it is required for a successful
-boot.  If you are using an NVIDIA based chipset, you should use the Open
-Firmware framebuffer.  If you are using an ATI based chipset, you should select
+boot. If you are using an NVIDIA based chipset, you should use the Open
+Firmware framebuffer. If you are using an ATI based chipset, you should select
 the framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon).
 </p>
 
@@ -276,9 +278,9 @@
 
 <note>
 If you select more than one framebuffer device, it may default to a less than
-optimal driver.  Either use only one framebuffer device or specify which
-to use by passing the driver to use to the kernel on boot by appending a video
-line such as: <c>video=radeonfb</c>.
+optimal driver. Either use only one framebuffer device or specify which to use
+by passing the driver to use to the kernel on boot by appending a video line
+such as: <c>video=radeonfb</c>.
 </note>
 
 <p>
@@ -323,7 +325,7 @@
 <comment>(Apple/IBM)</comment>
 # <i>cp vmlinux /boot/<keyval id="kernel-name"/></i>
 <comment>(Pegasos)</comment>
-# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name" /></i>
+# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name"/></i>
 </pre>
 
 <p>
@@ -367,9 +369,9 @@
 </pre>
 
 <p>
-If you are using firewire or USB to boot, you'll need to add modules to the
-initrd.  Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change
-<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or
+If you are using FireWire or USB to boot, you'll need to add modules to the
+initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change
+<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for FireWire support or
 <c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support.
 </p>
 
@@ -425,7 +427,7 @@
 
 <pre caption="Checking the created kernel image name and initrd">
 <comment>Note, your kernel version might be different</comment>
-# <i>ls /boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> /boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/></i>
+# <i>ls /boot/<keyval id="genkernel-name"/> /boot/<keyval id="genkernel-initrd"/></i>
 </pre>
 
 <p>



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

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml?rev=1.63&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml?rev=1.63&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml?r1=1.62&r2=1.63

Index: hb-install-ppc-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- hb-install-ppc-medium.xml	5 Aug 2009 15:25:23 -0000	1.62
+++ hb-install-ppc-medium.xml	21 Jul 2010 00:52:41 -0000	1.63
@@ -4,12 +4,12 @@
 <!-- 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-ppc-medium.xml,v 1.62 2009/08/05 15:25:23 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.63 2010/07/21 00:52:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>9.2</version>
-<date>2009-08-05</date>
+<version>10.0</version>
+<date>2010-07-20</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -40,7 +40,7 @@
   <th>Apple OldWorld machines</th>
   <ti>
     Apple Machines with an Open Firmware revision less than 3, such as the Beige
-    G3s, PCI PowerMacs and PCI PowerBooks.  PCI based Apple Clones should also
+    G3s, PCI PowerMacs and PCI PowerBooks. PCI-based Apple Clones should also
     be supported.
   </ti>
 </tr>
@@ -82,53 +82,48 @@
 
 <!-- START -->
 <section>
-<title>The Gentoo Universal Installation CD</title>
+<title>The Gentoo Installation CDs</title>
 <subsection>
 <title>Introduction</title>
 <body>
 
 <p>
-Gentoo Linux can be installed using a <e>stage3</e> tarball file.
-Such a tarball is an archive that contains a minimal environment from
-which you can succesfully install Gentoo Linux onto your system.
+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>
-Installations using a stage1 or stage2 tarball file are not documented in the
-Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo
-FAQ</uri> on these matters.
+All Installation CDs allow you to boot, set up networking, initialize your
+partitions and start installing Gentoo from the Internet.
 </p>
 
-</body>
-</subsection>
-<subsection>
-<title>Gentoo Universal Installation CD</title>
-<body>
-
+<!--
+<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="2008.0/">Gentoo 2008.0
+Handbooks</uri>.
+</impo>
+-->
+<!--
 <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:
+The Installation CDs that we currently provide are:
 </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>
+  <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>
@@ -143,63 +138,118 @@
 <p>
 The use of the Package CD is covered later in this document. 
 </p>
+-->
+</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"/>current-stage3/</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>
+
+
 <!-- STOP -->
 <section>
-<title>Download, Burn and Boot the Gentoo Universal Installation CD</title>
+<title>Download, Burn and Boot a Gentoo Installation CD</title>
 <subsection>
-<title>Downloading and Burning the Installation CD</title>
+<title>Downloading and Burning the Installation CDs</title>
 <body>
 
 <p>
-You can download the Universal Installation CD (and, if you want to, the
-Packages CD as well) from one of our <uri
-link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in
-the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs
-are located in the <path><keyval id="release-dir"/>packagecd</path> directory.
+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>
-Inside those directories you'll find ISO files. Those are full CD images which
-you can write on a CD-R.
+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"/>current-iso/</path> directory.
 </p>
 
 <p>
-After downloading the file, you can verify its integrity to see if it is 
-corrupted or not:
+Inside that directory you'll find ISO files. Those are full CD images which you
+can write on a CD-R.
 </p>
 
-<ul>
-  <li>
-    You can check its MD5 checksum and compare it with the MD5 checksum we 
-    provide (for instance with the <c>md5sum</c> tool under Linux/Unix or 
-    <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows).
-    Verifying MD5 checksums with Mac OS X is described in the <uri
-    link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>.
-  </li>
-  <li>
-    You can verify the cryptographic signature that we provide. You need to
-    obtain the public key we use (0x17072058) before you proceed though.
-  </li>
-</ul>
+<p>
+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>
-To fetch our public key using the GnuPG application, run the following command:
+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 0x17072058</i>
+$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 2D182910</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 caption="Verify the files">
+<comment>(Verify the cryptographic signature)</comment>
+$ <i>gpg --verify &lt;downloaded iso.DIGESTS.asc&gt;</i>
+<comment>(Verify the checksum)</comment>
+$ <i>sha1sum -c &lt;downloaded iso.DIGESTS.asc&gt;</i>
 </pre>
 
 <p>