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

[Joseph Jezak]

josejx      07/03/16 05:31:09

  Modified:             hb-install-ppc-bootloader.xml
                        hb-install-ppc-disk.xml hb-install-ppc-kernel.xml
                        hb-install-ppc-medium.xml
  Log:
  First draft of ppc handbook update for 2007.1.

Revision  Changes    Path
1.26                 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml?r1=1.25&r2=1.26

Index: hb-install-ppc-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-install-ppc-bootloader.xml	14 Mar 2007 06:24:40 -0000	1.25
+++ hb-install-ppc-bootloader.xml	16 Mar 2007 05:31:09 -0000	1.26
@@ -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/draft/hb-install-ppc-bootloader.xml,v 1.25 2007/03/14 06:24:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml,v 1.26 2007/03/16 05:31:09 josejx Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2006-11-13</date>
+<version>7.3</version>
+<date>2007-03-15</date>
 
 <section>
 <title>Choosing a Bootloader</title>
@@ -28,7 +28,7 @@
 <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.
+<uri link="#bootcreator">bootcreator</uri> to create SmartFirmware boot menus.
 </p>
 
 </body>
@@ -72,24 +72,24 @@
 <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:
+modified as follows (using vmlinux and initrd as the name of kernel and 
+initrd image):
 </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-name
-## and initrd-name with the exact filename of your kernel
-## and initrd image.
+## kernel or set of boot options - replace vmlinux and initrd
+## with the exact filename of your kernel and initrd image.
 ###########################################################</comment>
-image=/boot/kernel-name
+image=/boot/vmlinux
   label=Linux
   root=/dev/ram0
   partition=3
-  initrd=/boot/initrd-name
-  append="real_root=/dev/hda3 init=/linuxrc"  
+  initrd=/boot/initrd
   <comment># You can add additional kernel arguments to append such as 
   # rootdelay=10 for a USB/Firewire Boot</comment>
+  append="real_root=/dev/hda3 init=/linuxrc"  
   read-only
 <comment>##########################################################</comment>
 </pre>
@@ -115,13 +115,13 @@
 <p>
 To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
 and <path>/etc/fstab</path> must be configured to reflect your Linux 
-partitions. These steps should have already been completed before, but check
-<path>/etc/fstab</path> before proceeding.  Now, ensure that you have 
-<c>yaboot</c> installed.
+partitions (note that the Bootstrap partition should <e>not</e> be in your
+fstab). These steps should have already been completed before, but check
+<path>/etc/fstab</path> before proceeding.  Now, install <c>yaboot</c>.
 </p>
 
 <pre caption = "Installing yaboot">
-# <i>emerge yaboot</i>
+# <i>emerge --usepkg yaboot</i>
 </pre>
 
 <p>
@@ -141,9 +141,11 @@
 </pre>
 
 <p>
-You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you
-make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot
-OS), make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap
+You should verify the contents of <path>/etc/yaboot.conf</path>. If you make
+changes to <path>/etc/yaboot.conf</path> (like setting the default/boot OS),
+make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap
+partition.  Whenever you make a change to yaboot.conf, like when testing a new
+kernel, always remember to run <c>ybin -v</c> to update the bootstrap
 partition.
 </p>
 
@@ -158,7 +160,7 @@
 <body>
 
 <p>
-First make sure you have <c>yaboot</c> installed on your system:
+First, install <c>yaboot</c> on your system:
 </p>
 
 <pre caption = "Installing yaboot with GRP">
@@ -355,7 +357,7 @@
 </p>
 
 <pre caption="Emerge quik">
-# <i>emerge quik</i>
+# <i>emerge --usepkg quik</i>
 </pre>
 
 <p>



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

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?r1=1.23&r2=1.24

Index: hb-install-ppc-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-ppc-disk.xml	14 Mar 2007 06:24:40 -0000	1.23
+++ hb-install-ppc-disk.xml	16 Mar 2007 05:31:09 -0000	1.24
@@ -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/draft/hb-install-ppc-disk.xml,v 1.23 2007/03/14 06:24:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml,v 1.24 2007/03/16 05:31:09 josejx Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2006-11-02</date>
+<version>7.2</version>
+<date>2007-03-15</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -18,7 +18,7 @@
 <body>
 
 <p>
-We'll take a good look at disk-oriented aspects of Gentoo Linux
+We'll start by taking 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
@@ -29,13 +29,15 @@
 To begin, we'll introduce <e>block devices</e>. The most common block device is
 the one that represents the first IDE drive in a Linux system, namely
 <path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA 
-drives, then your first hard drive would be <path>/dev/sda</path>.
+drives, then your first hard drive would be <path>/dev/sda</path>.  Additional
+drives are enumerated by the next letter in the alphabet.  As an example, the
+third IDE disk could be found at <path>/dev/hdc</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
+programs can use these block devices to interact with the disk without worrying
+about whether the 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>
@@ -64,94 +66,231 @@
 
 <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:
+you can use the partitioning scheme we use throughout this book.  Choose the
+filesystem layout that best matches the type of PowerPC system you are 
+installing on.
+</p>
+
+</body>
+</subsection>
+<subsection>
+<title>Apple New World</title>
+<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.
 </p>
 
 <note>
-If you are using an OldWorld machine, you will need to keep MacOS available.
-The layout here assumes MacOS is installed on a separate drive.
+There may be "Disk Driver" partitions on your disk such as <path>Apple_Driver63,
+Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, 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.
+</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
+can safely remove these.
 </note>
 
 <table>
 <tr>
-  <th>Partition NewWorld</th>
-  <th>Partition OldWorld</th>
-  <th>Partition Pegasos</th>
-  <th>Partition RS/6000</th>
-  <th>Filesystem</th>
+  <th>Partition</th>
   <th>Size</th>
+  <th>Filesystem</th>
   <th>Description</th>
 </tr>
 <tr>
   <ti><path>/dev/hda1</path></ti>
-  <ti><path>/dev/hda1</path></ti>
-  <ti>(Not applicable)</ti>
-  <ti>(Not applicable)</ti>
-  <ti>(Partition Map)</ti>
   <ti>32k</ti>
-  <ti>Apple_partition_map</ti>
+  <ti>None</ti>
+  <ti>Apple Partition Map</ti>
 </tr>
 <tr>
   <ti><path>/dev/hda2</path></ti>
-  <ti>(Not needed)</ti>
-  <ti>(Not applicable)</ti>
-  <ti>(Not applicable)</ti>
-  <ti>(bootstrap)</ti>
   <ti>800k</ti>
-  <ti>Apple_Bootstrap</ti>
+  <ti>HFS</ti>
+  <ti>Apple Bootstrap</ti>
 </tr>
 <tr>
-  <ti>(Not applicable)</ti>
-  <ti>(Not applicable)</ti>
-  <ti>(Not applicable)</ti>
-  <ti><path>/dev/sda1</path></ti>
-  <ti>(PReP Boot)</ti>
-  <ti>800k</ti>
-  <ti>Type 0x41</ti>
+  <ti><path>/dev/hda3</path></ti>
+  <ti>512Mb</ti>
+  <ti>Swap</ti>
+  <ti>Linux Swap</ti>
+</tr>
+<tr>
+  <ti><path>/dev/hda4</path></ti>
+  <ti>Rest of Disk</ti>
+  <ti>ext3, reiserfs, xfs</ti>
+  <ti>Linux Root</ti>
+</tr>
+</table>
+
+</body>
+</subsection>
+<subsection>
+<title>Apple Old World</title>
+<body>
+
+<p>
+Apple Old World machines are a bit more complicated 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.  If you are using
+BootX, the configuration below assumes that MacOS is installed on a seperate
+disk.  If this is not the case, there will be additional partitions for "Apple
+Disk Drivers" such as <path>Apple_Driver63, Apple_Driver_ATA, Apple_FWDriver,
+Apple_Driver_IOKit, Apple_Patches</path> and the MacOS install.  If you are 
+using Quik, you will need to create a boot partition to hold the kernel, unlike
+other Apple boot methods. 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.
+</p>
+
+<note>
+If you are using an OldWorld machine, you will need to keep MacOS available.
+The layout here assumes MacOS is installed on a separate drive.
+</note>
+
+<table>
+<tr>
+  <th>Partition</th>
+  <th>Size</th>
+  <th>Filesystem</th>
+  <th>Description</th>
 </tr>
 <tr>
-  <ti>(Not applicable)</ti>
-  <ti><path>/dev/hda2</path> (If using quik)</ti>
   <ti><path>/dev/hda1</path></ti>
-  <ti>(Not applicable)</ti>
+  <ti>32k</ti>
+  <ti>None</ti>
+  <ti>Apple Partition Map</ti>
+</tr>
+<tr>
+  <ti><path>/dev/hda2</path></ti>
+  <ti>32Mb</ti>
   <ti>ext2</ti>
-  <ti>32MB</ti>
-  <ti>Boot partition</ti>
+  <ti>Quik Boot Partition (quik only)</ti>
 </tr>
 <tr>
   <ti><path>/dev/hda3</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>
-  <ti>512M</ti>
-  <ti>Swap partition, Type 0x82</ti>
+  <ti>512Mb</ti>
+  <ti>Swap</ti>
+  <ti>Linux Swap</ti>
 </tr>
 <tr>
   <ti><path>/dev/hda4</path></ti>
-  <ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti>
+  <ti>Rest of Disk</ti>
+  <ti>ext3, reiserfs, xfs</ti>
+  <ti>Linux Root</ti>
+</tr>
+</table>
+
+</body>
+</subsection>
+<subsection>
+<title>Pegasos</title>
+<body>
+
+<p>
+The Pegaos partition layout is quite simple compared to the Apple layouts.
+The first partition is a Boot Partition, which contains kernels to be booted,
+along with an OpenFirmware script that presents a menu on boot.  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.  
+</p>
+
+<table>
+<tr>
+  <th>Partition</th>
+  <th>Size</th>
+  <th>Filesystem</th>
+  <th>Description</th>
+</tr>
+<tr>
+  <ti><path>/dev/hda1</path></ti>
+  <ti>32Mb</ti>
+  <ti>affs1 or ext2</ti>
+  <ti>Boot Partition</ti>
+</tr>
+<tr>
+  <ti><path>/dev/hda2</path></ti>
+  <ti>512Mb</ti>
+  <ti>Swap</ti>
+  <ti>Linux Swap</ti>
+</tr>
+<tr>
   <ti><path>/dev/hda3</path></ti>
-  <ti><path>/dev/sda3</path></ti>
-  <ti>ext3, xfs</ti>
-  <ti>Rest of the disk</ti>
-  <ti>Root partition, Type 0x83</ti>
+  <ti>Rest of Disk</ti>
+  <ti>ext3, reiserfs, xfs</ti>
+  <ti>Linux Root</ti>
 </tr>
 </table>
 
-<note>
-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 
-initializing the partition map.
-</note>
+</body>
+</subsection>
+<subsection>
+<title>IBM PReP (RS/6000)</title>
+<body>
+
+<p>
+The Pegaos partition layout is quite simple compared to the Apple layouts.
+The first partition is a Boot Partition, which contains kernels to be booted,
+along with an OpenFirmware script that presents a menu on boot.  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.  
+</p>
+
+<table>
+<tr>
+  <th>Partition</th>
+  <th>Size</th>
+  <th>Filesystem</th>
+  <th>Description</th>
+</tr>
+<tr>
+  <ti><path>/dev/hda1</path></ti>
+  <ti>800k</ti>
+  <ti>None</ti>
+  <ti>PReP Boot Partition (Type 0x41)</ti>
+</tr>
+<tr>
+  <ti><path>/dev/hda2</path></ti>
+  <ti>512Mb</ti>
+  <ti>Swap</ti>
+  <ti>Linux Swap (Type 0x82)</ti>
+</tr>
+<tr>
+  <ti><path>/dev/hda3</path></ti>
+  <ti>Rest of Disk</ti>
+  <ti>ext3, reiserfs, xfs</ti>
+  <ti>Linux Root (Type 0x83)</ti>
+</tr>
+</table>
 
 <warn>
-<c>parted</c> is able to resize partitions including HFS+. Unfortunately it is
-not possible to resize HFS+ journaled filesystems, so switch off journaling in
-Mac OS X before resizing. Remember that any resizing operation is dangerous,
-so attempt at your own risk! Be sure to always have a backup of your data 
-before resizing!
+<c>parted</c> is able to resize partitions including HFS+. Unfortunately there
+may be issues with resizing HFS+ journaled filesystems, so, for the best 
+results, switch off journaling in Mac OS X before resizing. Remember that any
+resizing operation is dangerous, so attempt at your own risk! Be sure to always
+have a backup of your data before resizing!
 </warn>
 
 <p>
@@ -173,13 +312,13 @@
 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.
+should be separate as all received mail is stored in <path>/var</path>. A good
+choice of filesystem will then maximise your performance. Game servers should
+have a separate <path>/opt</path> as most game servers are installed there. The
+reason is similar for <path>/home</path>: security and backups. Whatever layout
+you chose, you will definitely want to keep <path>/usr</path> large: not only 
+will it contain the majority of applications, the Portage tree alone takes 
+more than 500Mb excluding the various sources that are stored in it.
 </p>
 
 <p>
@@ -229,10 +368,13 @@
 </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.  Usually the first partition on
-NewWorld machines (Apple_partition_map) could not be deleted.
+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 
+will completely erase the disk, so use this with caution.
 </p>
 
 <p>
@@ -252,15 +394,15 @@
 ask for what block you want to start this partition from. As we used <c>2</c>
 before to create the Apple_Bootstrap partition, you now have to enter
 <c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size
-you want -- 512MB is recommended though). When asked for a name, enter <c>swap</c>
-(mandatory).
+you want -- a minimum of 512MB is recommended, but 2 times your physical memory
+is the generally accepted size). When asked for a name, enter <c>swap</c>.
 </p>
 
 <p>
 To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select
 from what block the root partition should start. When asked for the size, enter
 <c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available
-space". When asked for the name, enter <c>root</c> (mandatory).
+space". When asked for the name, enter <c>root</c>.
 </p>
 
 <p>
@@ -269,7 +411,7 @@
 </p>
 
 <note>
-To make sure everything is ok, you should run mac-fdisk once more and check
+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
@@ -277,14 +419,14 @@
 </note>
 
 <p>
-Now that your partitions are created, you can continue with <uri
-link="#filesystems">Creating Filesystems</uri>.
+Now that your partitions are created, you can continue with 
+<uri link="#filesystems">Creating Filesystems</uri>.
 </p>
 
 </body>
 </section>
 <section id="parted">
-<title>Using parted (especially Pegasos) to Partition your Disk</title>
+<title>Using parted to Partition your Disk (Pegasos and RS/6000)</title>
 <body>
 
 <p>
@@ -303,7 +445,7 @@
 </pre>
 
 <p>
-If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new
+If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new 
 disklabel for the drive.
 </p>
 
@@ -315,42 +457,33 @@
 
 <p>
 If you intend to also install MorphOS on your Pegasos create an affs1 filesystem
-named "BI0" (BI zero) at the start of the drive. 32MB should be more than enough
-to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs or
-xfs, you will also have to store your Linux kernel on this partition (the
-Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the partition run
-<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should
-be replaced with the megabyte range (e.g. <c>0 32</c> creates a 32 MB partition
-starting at 0MB and ending at 32MB.
-</p>
-
-<p>
-You need to create two partitions for Linux, one root filesystem for all your
-program files etc, and one swap partition. To create the root filesystem you
-must first decide which filesystem to use. Possible options are ext2, ext3,
-reiserfs and xfs. Unless you know what you are doing, use ext3. Run
-<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace
-<c>START</c> and <c>END</c> with the megabyte start and stop marks for the
-partition.
+at the start of the drive. 32MB should be more than enough to store the MorphOS
+kernel. If you have a Pegasos I or intend to use any filesystem besides ext2 or 
+ext3, you will also have to store your Linux kernel on this partition (the 
+Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the 
+partition run <c>mkpart primary affs1 START END</c> where <c>START</c> and 
+<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.
 </p>
 
 <p>
-It is generally recommended that you create a swap partition the same size as
-the amount of RAM in your computer times two. You will probably get away with a
-smaller swap partition unless you intend to run a lot of applications at the
-same time (although at least 512MB is recommended). To create the swap
-partition, run <c>mkpart primary linux-swap START END</c>.
+You will need to create two partitions for Linux, one root filesystem and one 
+swap partition. Run <c>mkpart primary START END</c> to create each partition,
+replacing <c>START</c> and <c>END</c> with the desired megabyte boundries.
 </p>
 
 <p>
-Write down the partition minor numbers as they are required during the
-installation process. To display the minor numbers run <c>print</c>. Your drives
-are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number
-of the partition.
+It is generally recommended that you create a swap partition that is two times
+bigger than the amount of RAM in your computer, but at least 512Mb is 
+recommended. To create the swap partition, run 
+<c>mkpart primary linux-swap START END</c> with START and END again denoting
+the partition boundries.
 </p>
 
 <p>
-When you are done in parted simply run <c>quit</c>.
+When you are done in parted simply type <c>quit</c>.
 </p>
 
 </body>
@@ -363,10 +496,10 @@
 
 <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...
+If you're not sure which filesystems to choose and are happy with our defaults,
+continue with 
+<uri link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
+Otherwise, read on to learn about the available filesystems.
 </p>
 
 </body>
@@ -376,18 +509,16 @@
 <body>
 
 <p>
-Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found 
-stable on the PPC architecture.
+Several filesystems are available for use on the PowerPC architecture including
+ext2, ext3, ReiserFS and XFS, each with their strengths and faults.
 </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.
+be quite time-consuming. There is now quite a selection of journaled 
+filesystems that can be checked for consistency very quickly and are thus 
+generally preferred over their non-journaled counterparts.
 </p>
 
 <p>
@@ -395,7 +526,7 @@
 journaling for fast recovery in addition to other enhanced journaling modes
 like full data and ordered data journaling. It uses a hashed B*-tree index that
 enables high performance in almost all situations. In short, ext3 is a very
-good and reliable filesystem.
+good and reliable filesystem and is highly recommended for most installs.
 </p>
 
 <p>
@@ -420,6 +551,32 @@
 
 </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/hda3</i>
+</pre>
+
+<p>
+To activate the swap partition, use <c>swapon</c>:
+</p>
+
+<pre caption="Activating the swap partition">
+# <i>swapon /dev/hda3</i>
+</pre>
+
+<p>
+Create and activate the swap now before creating other filesystems.
+</p>
+
+</body>
+</subsection>
 <subsection id="filesystems-apply">
 <title>Applying a Filesystem to a Partition</title>
 <body>
@@ -453,8 +610,8 @@
 </table>
 
 <p>
-For instance, to have the root partition (<path>/dev/hda4</path> in our example)
-in ext3 (as in our example), you would use:
+For instance, to make an ext3 filesystem on the root partition 
+(<path>/dev/hda4</path> in our example), you would use:
 </p>
 
 <pre caption="Applying a filesystem on a partition">
@@ -467,7 +624,7 @@
 </p>
 
 <note>
-On the PegasosII your partition which holds the kernel must be ext2/ext3 or
+On the PegasosII your partition which holds the kernel must be ext2, ext3 or
 affs1.  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
@@ -476,41 +633,17 @@
 
 </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/hda3</i>
-</pre>
-
-<p>
-To activate the swap partition, use <c>swapon</c>:
-</p>
-
-<pre caption="Activating the swap partition">
-# <i>swapon /dev/hda3</i>
-</pre>
-
-<p>
-Create and activate the swap now.
-</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. As an example we
-mount the root partition:
+Now that your partitions are initialized and contain valid filesystems, it is
+time to mount them since disks are not usable in Linux until they are mounted.
+When you mount a filesystem, the contents are inserted into the directory 
+specified by the <c>mount</c> command.  As an example we wil mount the root 
+partition in a directory on the InstallCD filesystem:
 </p>
 
 <pre caption="Mounting partitions">
@@ -519,17 +652,11 @@
 
 <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>.
+change its permissions after mounting and unpacking with
+<c>chmod 1777 /mnt/gentoo/tmp</c>. This is also true for <path>/var/tmp</path>.
 </note>
 
 <p>
-We will 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>



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

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.29&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.29&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?r1=1.28&r2=1.29

Index: hb-install-ppc-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- hb-install-ppc-kernel.xml	14 Mar 2007 06:24:40 -0000	1.28
+++ hb-install-ppc-kernel.xml	16 Mar 2007 05:31:09 -0000	1.29
@@ -4,21 +4,21 @@
 <!-- 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/hb-install-ppc-kernel.xml,v 1.28 2007/03/14 06:24:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v 1.29 2007/03/16 05:31:09 josejx Exp $ -->
 
 <sections>
 
-<version>7.5</version>
-<date>2007-02-12</date>
+<version>7.6</version>
+<date>2007-03-15</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
+First, 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>
@@ -32,7 +32,7 @@
 </body>
 </section>
 <section>
-<title>Installing the Sources</title>
+<title>Installing the Kernel Sources</title>
 <subsection>
 <title>Choosing a Kernel</title>
 <body>
@@ -40,36 +40,36 @@
 <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>. 
+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>. 
 </p>
 
 <p>
-We suggest using <c>gentoo-sources</c> on PPC, which is a 2.6 kernel.
+We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel.
 </p>
 
 <pre caption="Installing a kernel source">
-# <i>emerge gentoo-sources</i>
+# <i>emerge --usepkg gentoo-sources</i>
 </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-2.6.15</c>. Your version
-may be different, so keep this in mind.
+<path>linux</path> pointing to your newly emerged kernel source. In this case, 
+the installed kernel source points to <c>gentoo-sources-2.6.19-r7</c>. Your 
+installed 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-2.6.15
+lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -&gt; linux-2.6.19-gentoo-r7
 </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.
+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.
 </p>
 
 <p>
@@ -91,29 +91,29 @@
 <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 ;)
+few kernels you won'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).  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 the kernel messages.
+pciutils (<c>emerge --usepkg 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.
 </p>
 
 <p>
 Now, go to your kernel source directory, it's time to configure your kernel.
-It is recommended that you add the default settings to your configuration by
-first running <c>make pmac32_defconfig</c>. After the default configuration has
-been generated, run <c>make menuconfig</c> which will fire up an ncurses-based
+Start by configuring a kernel that will boot on most 32 Bit PowerPC machines
+by first running <c>make pmac32_defconfig</c>. After the default configuration
+has been generated, run <c>make menuconfig</c> to start an ncurses-based
 configuration menu.
 </p>
 
@@ -171,6 +171,17 @@
 </pre>
 
 <p>
+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>
+
+<pre caption="Activating HFS support">
+File Systems ---&gt;
+  [*] HFS Support
+</pre>
+
+<p>
 If you are using PPPoE to connect to the Internet or you are using a dial-up
 modem, you will need the following options in the kernel:
 </p>
@@ -184,28 +195,18 @@
 </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.
+The two compression options won't harm but are not always needed.  The 
+<c>PPP over Ethernet</c> option might only be used by <c>rp-pppoe</c> when 
+configured to perform kernel mode PPPoE.
 </p>
 
 <p>
-If you require it, don't forget to include support in the kernel for your
-ethernet card.
+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>
 
 <p>
-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>
-
-<pre caption="Activating HFS support">
-File Systems ---&gt;
-  [*] HFS Support
-</pre>
-
-<p>
 At this time, kernel preemption is still unstable on PPC and may cause 
 compilation failures and random segfaults.  It is <e>strongly</e> suggested
 that you do not use this feature.
@@ -266,8 +267,8 @@
 <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 such as 
-<c>video=radeonfb</c>.
+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>
@@ -283,7 +284,7 @@
 
 <p>
 Now that your kernel is configured, it is time to compile and install it. Exit 
-the configuration and run the commands which will compile the kernel:
+the configuration menu and run the following commands:
 </p>
 
 <pre caption="Compiling the kernel">
@@ -292,8 +293,9 @@
 
 <p>
 When the kernel has finished compiling, copy the kernel image to
-<path>/boot</path> (be sure that it is mounted properly on Pegasos computers).
-If you are using BootX to boot, we'll copy the kernel later.
+<path>/boot</path> as shown below.   If you have a seperate boot partition, as
+on Pegasos computers, be sure that it is mounted properly.  If you are using 
+BootX to boot, we'll copy the kernel later.
 </p>
 
 <p>
@@ -301,8 +303,8 @@
 bootloaders.  The uncompressed kernel is called vmlinux and it is placed in
 <path>/usr/src/linux</path> after the kernel has finished compiling.  If you
 are using a Pegasos machine, the Pegasos firmware requires a compressed
-kernel called zImage.chrp which can be found in 
-<path>/usr/src/linux/arch/ppc/boot/images</path>.
+kernel called zImage which can be found in 
+<path>/usr/src/linux/arch/powerpc/boot/images</path>.
 </p>
 
 <pre caption="Installing the kernel">
@@ -311,7 +313,7 @@
 <comment>(Apple/IBM)</comment>
 # <i>cp vmlinux /boot/&lt;kernel-version&gt;</i> 
 <comment>(Pegasos)</comment>
-# <i>cp arch/ppc/boot/images/zImage.chrp /boot/&lt;kernel-version&gt;</i> 
+# <i>cp arch/powerpc/boot/images/zImage /boot/&lt;kernel-version&gt;</i> 
 </pre>
 
 <p>
@@ -331,7 +333,7 @@
 <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.
+You can add extra options to the modules if required.
 </p>
 
 <p>
@@ -345,9 +347,8 @@
 </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.
+For instance, to automatically load the <c>3c59x</c> module, edit the
+<path>kernel-2.6</path> file and add the module to it, one module on a line.
 </p>
 
 <pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
@@ -371,17 +372,12 @@
 <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 
+kernel by using the <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 
+your hardware at boot-time, just like the Installation CD does. Since
 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>
@@ -391,7 +387,7 @@
 </p>
 
 <pre caption="Emerging genkernel">
-# <i>emerge genkernel</i>
+# <i>emerge --usepkg genkernel</i>
 </pre>
 
 <p>
@@ -425,11 +421,9 @@
 </pre>
 
 <p>
-Now, compile your kernel sources by running <c>genkernel --genzimage all</c>.
-For Pegasos, we will need to use a different config and create a zImage instead
-of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> 
-compiles a kernel that supports almost all hardware, this compilation can take 
-quite a while to finish!
+Now, compile your kernel sources by running <c>genkernel all</c>. Be aware, 
+since <c>genkernel</c> compiles a kernel that supports almost all hardware, 
+this compilation can take quite a while to finish!
 </p>
 
 <p>
@@ -445,15 +439,11 @@
 # <i>genkernel all</i>
 </pre>
 
-<pre caption="Running genkernel on the Pegasos">
-# <i>genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos 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
+down the names of the kernel and initrd as you will need them 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.  Be sure to also copy down the required
@@ -465,21 +455,10 @@
 </pre>
 
 <p>
-If you want your system to react to hotplugging events, you will need to install
-and setup <c>hotplug</c>:
-</p>
-
-<pre caption="Emerging and enabling hotplug">
-# <i>emerge hotplug</i>
-# <i>rc-update add hotplug default</i>
-</pre>
-
-<p>
 Now continue with <uri link="?part=1&amp;chap=8">Configuring your System</uri>.
 </p>
 
 </body>
 </section>
-
 </sections>
 



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

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml?rev=1.38&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml?rev=1.38&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml?r1=1.37&r2=1.38

Index: hb-install-ppc-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-ppc-medium.xml	14 Mar 2007 06:24:40 -0000	1.37
+++ hb-install-ppc-medium.xml	16 Mar 2007 05:31:09 -0000	1.38
@@ -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/hb-install-ppc-medium.xml,v 1.37 2007/03/14 06:24:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml,v 1.38 2007/03/16 05:31:09 josejx Exp $ -->
 
 <sections>
 
@@ -45,9 +45,9 @@
   </ti>
 </tr>
 <tr>
-  <th>Genesi's Pegasos</th>
+  <th>Genesi</th>
   <ti>
-    Pegasos I/II, Open Desktop Workstation
+    Pegasos I/II, Open Desktop Workstation, Efika
   </ti>
 </tr>
 <tr>



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