[gentoo-doc-cvs] cvs commit: handbook-alpha.xml handbook-amd64.xml handbook-arm.xml handbook-hppa.xml handbook-ia64.xml handbook-mips.xml handbook-ppc.xml handbook-ppc64.xml handbook-sparc.xml handbook-x86.xml hb-install-about.xml hb-install-alpha-bootloader.xml hb-install-alpha-disk.xml hb-install-alpha-kernel.xml hb-install-alpha-medium.xml hb-install-arm-bootloader.xml hb-install-arm-disk.xml hb-install-arm-kernel.xml hb-install-arm-medium.xml hb-install-config.xml hb-install-finalise.xml hb-install-hppa-bootloader.xml hb-install-hppa-disk.xml hb-install-hppa-kernel.xml hb-install-hppa-medium.xml hb-install-ia64-disk.xml hb-install-ia64-kernel.xml hb-install-ia64-medium.xml hb-install-mips-bootloader.xml hb-install-mips-disk.xml hb-install-mips-kernel.xml hb-install-mips-medium.xml hb-install-mips-stage.xml hb-install-mips-system.xml hb-install-network.xml hb-install-next.xml hb-install-ppc-bootloader.xml hb-install-ppc-disk.xml hb-install-ppc-kernel.xml hb-insta! ll-ppc-medium.xml hb-install-ppc64-bootloader.xml hb-install-ppc64-disk.xml hb-install-ppc64-kernel.xml hb-install-ppc64-medium.xml hb-install-sparc-bootloader.xml hb-install-sparc-disk.xml hb-install-sparc-kernel.xml hb-install-sparc-medium.xml hb-install-stage.xml hb-install-system.xml hb-install-tools.xml hb-install-x86+amd64-bootloader.xml hb-install-x86+amd64-disk.xml hb-install-x86+amd64-kernel.xml hb-install-x86+amd64-medium.xml hb-net-advanced.xml hb-net-functions.xml hb-net-management.xml hb-net-start.xml hb-net-wireless.xml index.xml

[Josh Saddler]

nightmorph    07/05/07 18:11:41

  Modified:             handbook-alpha.xml handbook-amd64.xml
                        handbook-arm.xml handbook-hppa.xml
                        handbook-ia64.xml handbook-mips.xml
                        handbook-ppc.xml handbook-ppc64.xml
                        handbook-sparc.xml handbook-x86.xml
                        hb-install-about.xml
                        hb-install-alpha-bootloader.xml
                        hb-install-alpha-disk.xml
                        hb-install-alpha-kernel.xml
                        hb-install-alpha-medium.xml
                        hb-install-arm-bootloader.xml
                        hb-install-arm-disk.xml hb-install-arm-kernel.xml
                        hb-install-arm-medium.xml hb-install-config.xml
                        hb-install-finalise.xml
                        hb-install-hppa-bootloader.xml
                        hb-install-hppa-disk.xml hb-install-hppa-kernel.xml
                        hb-install-hppa-medium.xml hb-install-ia64-disk.xml
                        hb-install-ia64-kernel.xml
                        hb-install-ia64-medium.xml
                        hb-install-mips-bootloader.xml
                        hb-install-mips-disk.xml hb-install-mips-kernel.xml
                        hb-install-mips-medium.xml
                        hb-install-mips-stage.xml
                        hb-install-mips-system.xml hb-install-network.xml
                        hb-install-next.xml hb-install-ppc-bootloader.xml
                        hb-install-ppc-disk.xml hb-install-ppc-kernel.xml
                        hb-install-ppc-medium.xml
                        hb-install-ppc64-bootloader.xml
                        hb-install-ppc64-disk.xml
                        hb-install-ppc64-kernel.xml
                        hb-install-ppc64-medium.xml
                        hb-install-sparc-bootloader.xml
                        hb-install-sparc-disk.xml
                        hb-install-sparc-kernel.xml
                        hb-install-sparc-medium.xml hb-install-stage.xml
                        hb-install-system.xml hb-install-tools.xml
                        hb-install-x86+amd64-bootloader.xml
                        hb-install-x86+amd64-disk.xml
                        hb-install-x86+amd64-kernel.xml
                        hb-install-x86+amd64-medium.xml hb-net-advanced.xml
                        hb-net-functions.xml hb-net-management.xml
                        hb-net-start.xml hb-net-wireless.xml index.xml
  Log:
  2007.0 release is here; final changes and new docs

Revision  Changes    Path
1.133                xml/htdocs/doc/en/handbook/handbook-alpha.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml?rev=1.133&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml?rev=1.133&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml?r1=1.132&r2=1.133

Index: handbook-alpha.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v
retrieving revision 1.132
retrieving revision 1.133
diff -u -r1.132 -r1.133
--- handbook-alpha.xml	10 Mar 2007 17:14:15 -0000	1.132
+++ handbook-alpha.xml	7 May 2007 18:11:40 -0000	1.133
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v 1.132 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v 1.133 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-alpha.xml">
 <title>Gentoo Linux Alpha Handbook</title>
@@ -9,8 +9,11 @@
 <values>
  <key id="arch">Alpha</key>
  <key id="/boot">/dev/sda1</key>
- <key id="release-dir">releases/alpha/2006.1/</key>
- <key id="stage3">stage3-alpha-2006.1.tar.bz2</key>
+ <key id="kernel-version">2.6.19-r5</key>
+ <key id="kernel-name">kernel-2.6.19-gentoo-r5</key>
+ <key id="online-book">handbook-alpha.xml</key>
+ <key id="release-dir">releases/alpha/2007.0/</key>
+ <key id="stage3">stage3-alpha-2007.0.tar.bz2</key>
  <key id="CFLAGS">-mieee -pipe -O2 -mcpu=ev6</key>
 </values>
 
@@ -106,6 +109,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -129,8 +135,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.2</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.141                xml/htdocs/doc/en/handbook/handbook-amd64.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.141&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.141&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml?r1=1.140&r2=1.141

Index: handbook-amd64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v
retrieving revision 1.140
retrieving revision 1.141
diff -u -r1.140 -r1.141
--- handbook-amd64.xml	10 Mar 2007 17:14:15 -0000	1.140
+++ handbook-amd64.xml	7 May 2007 18:11:40 -0000	1.141
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.140 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.141 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-amd64.xml">
 <title>Gentoo Linux AMD64 Handbook</title>
@@ -10,16 +10,16 @@
  <key id="arch">AMD64</key>
  <key id="arch-sub">x86_64</key>
  <key id="/boot">/dev/hda1</key>
- <key id="kernel-version">2.6.17-r5</key>
- <key id="kernel-name">kernel-2.6.17-gentoo-r5</key>
- <key id="genkernel-name">kernel-genkernel-amd64-2.6.17-gentoo-r5</key>
- <key id="genkernel-initrd">initramfs-genkernel-amd64-2.6.17-gentoo-r5</key>
- <key id="min-cd-name">install-amd64-minimal-2006.1.iso</key>
+ <key id="kernel-version">2.6.19-r5</key>
+ <key id="kernel-name">kernel-2.6.19-gentoo-r5</key>
+ <key id="genkernel-name">kernel-genkernel-amd64-2.6.19-gentoo-r5</key>
+ <key id="genkernel-initrd">initramfs-genkernel-amd64-2.6.19-gentoo-r5</key>
+ <key id="min-cd-name">install-amd64-minimal-2007.0.iso</key>
  <key id="min-cd-size">50</key>
- <key id="live-cd-name">livecd-amd64-installer-2006.1.iso</key>
+ <key id="live-cd-name">livecd-amd64-installer-2007.0.iso</key>
  <key id="live-cd-size">696</key>
- <key id="release-dir">releases/amd64/2006.1/</key>
- <key id="stage3">stage3-amd64-2006.1.tar.bz2</key>
+ <key id="release-dir">releases/amd64/2007.0/</key>
+ <key id="stage3">stage3-amd64-2007.0.tar.bz2</key>
  <key id="CFLAGS">-march=k8 -O2 -pipe</key>
  <key id="online-book">handbook-amd64.xml</key>
 </values>
@@ -116,6 +116,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -139,8 +142,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.3</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.69                 xml/htdocs/doc/en/handbook/handbook-arm.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-arm.xml?rev=1.69&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-arm.xml?rev=1.69&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-arm.xml?r1=1.68&r2=1.69

Index: handbook-arm.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-arm.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- handbook-arm.xml	29 Nov 2006 15:35:24 -0000	1.68
+++ handbook-arm.xml	7 May 2007 18:11:40 -0000	1.69
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-arm.xml,v 1.68 2006/11/29 15:35:24 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-arm.xml,v 1.69 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-arm.xml">
 <title>Gentoo Linux ARM Handbook</title>
@@ -133,8 +133,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.1</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.130                xml/htdocs/doc/en/handbook/handbook-hppa.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml?rev=1.130&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml?rev=1.130&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml?r1=1.129&r2=1.130

Index: handbook-hppa.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v
retrieving revision 1.129
retrieving revision 1.130
diff -u -r1.129 -r1.130
--- handbook-hppa.xml	10 Mar 2007 17:14:15 -0000	1.129
+++ handbook-hppa.xml	7 May 2007 18:11:40 -0000	1.130
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v 1.129 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v 1.130 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-hppa.xml">
 <title>Gentoo Linux HPPA Handbook</title>
@@ -9,8 +9,11 @@
 <values>
  <key id="arch">HPPA</key>
  <key id="/boot">/dev/sda2</key>
- <key id="release-dir">releases/hppa/2006.1/hppa2.0/</key>
- <key id="stage3">stage3-hppa2.0-2006.1.tar.bz2</key>
+ <key id="kernel-version">2.6.20.1-hppa</key>
+ <key id="kernel-name">kernel-2.6.20.1-hppa</key>
+ <key id="online-book">handbook-hppa.xml</key>
+ <key id="release-dir">releases/hppa/2007.0/hppa2.0/</key>
+ <key id="stage3">stage3-hppa2.0-2007.0.tar.bz2</key>
  <key id="CFLAGS">-march=2.0 -O2 -pipe</key>
 </values>
 
@@ -106,6 +109,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -129,8 +135,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.2</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.8                  xml/htdocs/doc/en/handbook/handbook-ia64.xml

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

Index: handbook-ia64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ia64.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- handbook-ia64.xml	10 Mar 2007 17:14:15 -0000	1.7
+++ handbook-ia64.xml	7 May 2007 18:11:40 -0000	1.8
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ia64.xml,v 1.7 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ia64.xml,v 1.8 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-ia64.xml">
 <title>Gentoo Linux/IA64 Handbook</title>
@@ -12,10 +12,10 @@
  <key id="kernel-name">kernel-2.6.17-gentoo-r5</key>
  <key id="genkernel-name">kernel-genkernel-ia64-2.6.17-gentoo-r5</key>
  <key id="genkernel-initrd">initramfs-genkernel-ia64-2.6.17-gentoo-r5</key>
- <key id="min-cd-name">install-ia64-minimal-2006.1.iso</key>
+ <key id="min-cd-name">install-ia64-minimal-2007.0.iso</key>
  <key id="min-cd-size">52</key>
- <key id="release-dir">releases/ia64/2006.1/</key>
- <key id="stage3">stage3-ia64-2006.1.tar.bz2</key>
+ <key id="release-dir">releases/ia64/2007.0/</key>
+ <key id="stage3">stage3-ia64-2007.0.tar.bz2</key>
  <key id="CFLAGS">-O2 -pipe</key>
  <key id="online-book">handbook-ia64.xml</key>
 </values>
@@ -121,6 +121,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -142,8 +145,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.2</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -215,7 +218,7 @@
 The ia64 architecture uses the elilo bootloader.
 This chapter explains how to install and configure elilo.
 </abstract>
-  <include href="hb-install-ia64-bootloader.xml"/>
+  <include href="hb-install-x86+amd64-bootloader.xml"/>
 </chapter>
 
 <chapter>



1.121                xml/htdocs/doc/en/handbook/handbook-mips.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml?rev=1.121&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml?rev=1.121&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml?r1=1.120&r2=1.121

Index: handbook-mips.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v
retrieving revision 1.120
retrieving revision 1.121
diff -u -r1.120 -r1.121
--- handbook-mips.xml	29 Nov 2006 15:35:24 -0000	1.120
+++ handbook-mips.xml	7 May 2007 18:11:40 -0000	1.121
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v 1.120 2006/11/29 15:35:24 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v 1.121 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-mips.xml">
 <title>Gentoo Linux/MIPS Handbook</title>
@@ -9,6 +9,8 @@
 <values>
  <key id="arch">MIPS</key>
  <key id="/boot">/dev/sda1</key>
+ <key id="kernel-version">2.6.17.10-mips</key>
+ <key id="kernel-name">kernel-2.6.17.10-mips</key>
 </values>
 
 <author title="Author">
@@ -106,6 +108,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -129,8 +134,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.2</version>
-<date>2006-10-08</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.151                xml/htdocs/doc/en/handbook/handbook-ppc.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.151&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.151&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml?r1=1.150&r2=1.151

Index: handbook-ppc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v
retrieving revision 1.150
retrieving revision 1.151
diff -u -r1.150 -r1.151
--- handbook-ppc.xml	10 Mar 2007 17:14:15 -0000	1.150
+++ handbook-ppc.xml	7 May 2007 18:11:40 -0000	1.151
@@ -1,16 +1,19 @@
 <?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.150 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.151 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-ppc.xml">
 <title>Gentoo Linux PPC Handbook</title>
 
 <values>
  <key id="arch">PPC</key>
- <key id="/boot">/dev/hda1</key>
- <key id="release-dir">releases/ppc/2006.1/ppc32/</key>
- <key id="stage3">stage3-ppc-2006.1.tar.bz2</key>
+ <key id="kernel-version">2.6.19-r5</key>
+ <key id="kernel-name">kernel-2.6.19-gentoo-r5</key>
+ <key id="kernel-gentoo">2.6.19-gentoo-r5</key>
+ <key id="online-book">handbook-ppc.xml</key>
+ <key id="release-dir">releases/ppc/2007.0/ppc32/</key>
+ <key id="stage3">stage3-ppc-2007.0.tar.bz2</key>
  <key id="CFLAGS">-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe</key>
 </values>
 
@@ -115,6 +118,9 @@
 <author title="Editor">
   <mail link="josejx@g.o">Joseph Jezak</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -135,8 +141,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.2</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.72                 xml/htdocs/doc/en/handbook/handbook-ppc64.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?rev=1.72&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?rev=1.72&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?r1=1.71&r2=1.72

Index: handbook-ppc64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- handbook-ppc64.xml	10 Mar 2007 17:14:15 -0000	1.71
+++ handbook-ppc64.xml	7 May 2007 18:11:40 -0000	1.72
@@ -1,15 +1,18 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v 1.71 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v 1.72 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-ppc64.xml">
 <title>Gentoo Linux PPC64 Handbook</title>
 
 <values>
  <key id="arch">PPC64</key>
- <key id="release-dir">releases/ppc/2006.1/ppc64/</key>
- <key id="stage3">stage3-ppc64-64ul-2006.1.tar.bz2</key>
+ <key id="kernel-version">2.6.19-r7</key>
+ <key id="kernel-name">kernel-2.6.19-gentoo-r7</key>
+ <key id="online-book">handbook-ppc64.xml</key>
+ <key id="release-dir">releases/ppc/2007.0/ppc64/</key>
+ <key id="stage3">stage3-ppc64-32ul-2007.0.tar.bz2</key>
  <key id="CFLAGS">-O2 -pipe</key>
 </values>
 
@@ -102,6 +105,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -128,8 +134,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.2</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.134                xml/htdocs/doc/en/handbook/handbook-sparc.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml?rev=1.134&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml?rev=1.134&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml?r1=1.133&r2=1.134

Index: handbook-sparc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -r1.133 -r1.134
--- handbook-sparc.xml	19 Apr 2007 21:05:58 -0000	1.133
+++ handbook-sparc.xml	7 May 2007 18:11:40 -0000	1.134
@@ -1,15 +1,18 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v 1.133 2007/04/19 21:05:58 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v 1.134 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-sparc.xml">
 <title>Gentoo Linux SPARC Handbook</title>
 
 <values>
  <key id="arch">SPARC</key>
- <key id="release-dir">releases/sparc/2006.1/sparc64/</key>
- <key id="stage3">stage3-sparc64-2006.1.tar.bz2</key>
+ <key id="kernel-name">kernel-2.6.20-gentoo-r5</key>
+ <key id="kernel-version">2.6.20-r5</key>
+ <key id="online-book">handbook-sparc.xml</key>
+ <key id="release-dir">releases/sparc/2007.0/sparc64/</key>
+ <key id="stage3">stage3-sparc64-2007.0.tar.bz2</key>
  <key id="CFLAGS">-O2 -mcpu=ultrasparc -pipe</key>
 </values>
 
@@ -105,6 +108,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="nightmorph@g.o">Joshua Saddler</mail>
+</author>
 <author title="Reviewer">
     <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail>
 </author>
@@ -128,8 +134,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.3</version>
-<date>2007-04-19</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.160                xml/htdocs/doc/en/handbook/handbook-x86.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.160&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.160&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml?r1=1.159&r2=1.160

Index: handbook-x86.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v
retrieving revision 1.159
retrieving revision 1.160
diff -u -r1.159 -r1.160
--- handbook-x86.xml	10 Mar 2007 17:14:15 -0000	1.159
+++ handbook-x86.xml	7 May 2007 18:11:40 -0000	1.160
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.159 2007/03/10 17:14:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.160 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <book link="/doc/en/handbook/handbook-x86.xml">
 <title>Gentoo Linux x86 Handbook</title>
@@ -10,16 +10,16 @@
  <key id="arch">x86</key>
  <key id="arch-sub">i386</key>
  <key id="/boot">/dev/hda1</key>
- <key id="kernel-version">2.6.17-r5</key>
- <key id="kernel-name">kernel-2.6.17-gentoo-r5</key>
- <key id="genkernel-name">kernel-genkernel-x86-2.6.17-gentoo-r5</key>
- <key id="genkernel-initrd">initramfs-genkernel-x86-2.6.17-gentoo-r5</key>
- <key id="min-cd-name">install-x86-minimal-2006.1.iso</key>
+ <key id="kernel-version">2.6.19-r5</key>
+ <key id="kernel-name">kernel-2.6.19-gentoo-r5</key>
+ <key id="genkernel-name">kernel-genkernel-x86-2.6.19-gentoo-r5</key>
+ <key id="genkernel-initrd">initramfs-genkernel-x86-2.6.19-gentoo-r5</key>
+ <key id="min-cd-name">install-x86-minimal-2007.0.iso</key>
  <key id="min-cd-size">49</key>
- <key id="live-cd-name">livecd-i686-installer-2006.1.iso</key>
+ <key id="live-cd-name">livecd-i686-installer-2007.0.iso</key>
  <key id="live-cd-size">697</key>
- <key id="release-dir">releases/x86/2006.1/</key>
- <key id="stage3">stage3-i686-2006.1.tar.bz2</key>
+ <key id="release-dir">releases/x86/2007.0/</key>
+ <key id="stage3">stage3-i686-2007.0.tar.bz2</key>
  <key id="online-book">handbook-x86.xml</key>
  <key id="CFLAGS">-O2 -march=i686 -pipe</key>
 </values>
@@ -142,8 +142,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>7.3</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <part>
 <title>Installing Gentoo</title>



1.42                 xml/htdocs/doc/en/handbook/hb-install-about.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-about.xml?rev=1.42&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-about.xml?rev=1.42&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-about.xml?r1=1.41&r2=1.42

Index: hb-install-about.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-about.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- hb-install-about.xml	28 Oct 2006 09:17:54 -0000	1.41
+++ hb-install-about.xml	7 May 2007 18:11:40 -0000	1.42
@@ -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/hb-install-about.xml,v 1.41 2006/10/28 09:17:54 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-about.xml,v 1.42 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 handbook.
 </abstract>
 
-<version>7.1</version>
-<date>2006-09-01</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction</title>
@@ -134,7 +134,7 @@
 certain cases, NetBooting. This installation assumes that you want to install
 the latest available version of each package. If you want to perform a
 networkless installation, you should read the <uri
-link="/doc/en/handbook/2006.1/">Gentoo 2006.1 Handbooks</uri> which contain the
+link="/doc/en/handbook/2007.0/">Gentoo 2007.0 Handbooks</uri> which contain the
 installation instructions for a networkless environment. 
 </p>
 
@@ -142,7 +142,7 @@
 Also note that, if you plan on using GRP (the Gentoo Reference Platform, a
 collection of prebuilt packages meant for immediate use after a Gentoo
 installation), you <e>must</e> follow the instructions in the <uri
-link="/doc/en/handbook/2006.1/">Gentoo 2006.1 Handbooks</uri>.
+link="/doc/en/handbook/2007.0/">Gentoo 2007.0 Handbooks</uri>.
 </p>
 
 <p>



1.20                 xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml

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

Index: hb-install-alpha-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-install-alpha-bootloader.xml	30 Aug 2006 22:52:28 -0000	1.19
+++ hb-install-alpha-bootloader.xml	7 May 2007 18:11:40 -0000	1.20
@@ -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-alpha-bootloader.xml,v 1.19 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml,v 1.20 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Making your Choice</title>
@@ -123,7 +123,7 @@
 </p>
 
 <pre caption="Installing MILO">
-# <i>emerge --usepkg milo</i>
+# <i>emerge milo</i>
 </pre>
 
 <p>



1.25                 xml/htdocs/doc/en/handbook/hb-install-alpha-disk.xml

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

Index: hb-install-alpha-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-disk.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- hb-install-alpha-disk.xml	16 Feb 2007 13:45:39 -0000	1.24
+++ hb-install-alpha-disk.xml	7 May 2007 18:11:40 -0000	1.25
@@ -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-alpha-disk.xml,v 1.24 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-disk.xml,v 1.25 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2007-02-16</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -738,7 +738,7 @@
 </p>
 
 <pre caption="Applying a filesystem on a partition">
-# <i>mke2fs -j -O dir_index /dev/sda2</i>
+# <i>mke2fs -j /dev/sda2</i>
 </pre>
 
 <p>



1.38                 xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml

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

Index: hb-install-alpha-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-alpha-kernel.xml	13 Mar 2007 00:30:09 -0000	1.37
+++ hb-install-alpha-kernel.xml	7 May 2007 18:11:40 -0000	1.38
@@ -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-alpha-kernel.xml,v 1.37 2007/03/13 00:30:09 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v 1.38 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.3</version>
-<date>2007-03-12</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,7 +26,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -46,45 +47,37 @@
 </p>
 
 <p>
-For alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel source).
-</p>
-
-<p>
-Choose your kernel source and install it using <c>emerge</c>. 
-</p>
-
-<p>
-In the next example we install <c>vanilla-sources</c>. Of course substitute with
-your choice of sources, this is merely an example.
+For alpha-based systems we have <c>gentoo-sources</c> (the default 2.6 kernel
+source).
 </p>
 
 <pre caption="Installing a kernel source">
-# <i>emerge vanilla-sources</i>
+# <i>emerge gentoo-sources</i>
 </pre>
 
 <p>
 When you take a look in <path>/usr/src</path> you should see a symlink called
 <path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>vanilla-sources-2.6.16.19</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
+Your version may be different, so keep this in mind.
 </p>
 
 <pre caption="Viewing the kernel source symlink">
 # <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.16.19
+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 
+Now it is time to configure and compile your kernel source. You can use
+<c>genkernel</c> for this, which will build a generic kernel as used by the
+Installation CD. We explain the "manual" configuration first though, as it is
 the best way to optimize your environment.
 </p>
 
 <p>
 If you want to manually configure your kernel, continue now with <uri
-link="#manual">Default: Manual Configuration</uri>. If you want to use 
-<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using 
+link="#manual">Default: Manual Configuration</uri>. If you want to use
+<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
 genkernel</uri> instead.
 </p>
 
@@ -153,21 +146,10 @@
 Now go to <c>File Systems</c> and select support for the filesystems you use.
 <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
 able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
-file system</c>.  If you are using a 2.4 kernel, you should also select the 
-<c>/dev file system</c> and <c>Automatically mount at boot</c> options, and 
-you should make sure to <c>emerge devfsd</c>.
+file system</c>.
 </p>
 
 <pre caption="Selecting necessary file systems">
-<comment>(With a 2.4.x kernel)</comment>
-File systems ---&gt;
-  [*] Virtual memory file system support (former shm fs)
-  [*] /proc file system support
-  [*] /dev file system support (EXPERIMENTAL)
-  [*]   Automatically mount at boot
-  [ ] /dev/pts file system for Unix98 PTYs
-
-<comment>(With a 2.6.x kernel)</comment>
 File systems ---&gt;
   Pseudo Filesystems ---&gt;
     [*] /proc file system support
@@ -187,13 +169,6 @@
 </p>
 
 <pre caption="Selecting PPPoE necessary drivers">
-<comment>(With a 2.4.x kernel)</comment>
-Network device support ---&gt;
-  &lt;*&gt; PPP (point-to-point protocol) support
-  &lt;*&gt;   PPP support for async serial ports
-  &lt;*&gt;   PPP support for sync tty ports
-
-<comment>(With a 2.6.x kernel)</comment>
 Device Drivers ---&gt;
   Networking support ---&gt;
     &lt;*&gt; PPP (point-to-point protocol) support
@@ -203,8 +178,8 @@
 
 <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.
+does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
+when configured to do kernel mode PPPoE.
 </p>
 
 <p>
@@ -287,13 +262,7 @@
 </p>
 
 <pre caption="Compiling the kernel">
-<comment>(For 2.4 kernel)</comment>
-# <i>make dep &amp;&amp; make vmlinux modules modules_install</i>
-
-<comment>(For 2.6 kernel)</comment>
 # <i>make &amp;&amp; make modules_install</i>
-
-<comment>(For all kernels)</comment>
 # <i>make boot</i>
 </pre>
 
@@ -325,14 +294,15 @@
 </p>
 
 <p>
-Now that your kernel source tree is installed, it's now time to compile your 
-kernel by using our <c>genkernel</c> script to automatically build a kernel for 
-you. <c>genkernel</c> works by configuring a kernel nearly identically to the 
-way our Installation CD kernel is configured. This means that when you use 
-<c>genkernel</c> to build your kernel, your system will generally detect all 
-your hardware at boot-time, just like our Installation CD does. Because genkernel 
-doesn't require any manual kernel configuration, it is an ideal solution for 
-those users who may not be comfortable compiling their own kernels.
+Now that your kernel source tree is installed, it's now time to compile your
+kernel by using our <c>genkernel</c> script to automatically build a kernel for
+you. <c>genkernel</c> works by configuring a kernel nearly identically to the
+way our Installation CD kernel is configured. This means that when you use
+<c>genkernel</c> to build your kernel, your system will generally detect all
+your hardware at boot-time, just like our Installation CD does. Because
+genkernel doesn't require any manual kernel configuration, it is an ideal
+solution for those users who may not be comfortable compiling their own
+kernels.
 </p>
 
 <p>
@@ -358,41 +328,16 @@
 
 <pre caption="Running genkernel">
 # <i>genkernel all</i>
-* Gentoo Linux Genkernel; Version 3.4.0
-* Running with options: all
-
-* Linux Kernel 2.6.16.19 for alpha...
-* kernel: >> Running mrproper...
-<comment>(Output removed to increase readability)</comment>
-* Kernel compiled successfully!
-*
-* Required Kernel Parameters:
-*     real_root=/dev/$ROOT
-*
-*     Where $ROOT is the device node for your root partition as the
-*     one specified in /etc/fstab
-*
-* If you require Genkernel's hardware detection features; you MUST
-* tell your bootloader to use the provided INITRAMFS file. Otherwise;
-* substitute the root argument for the real_root argument if you are
-* not planning to use the initrd...
-
-* WARNING... WARNING... WARNING...
-* Additional kernel cmdline arguments that *may* be required to boot properly...
-* Do NOT report kernel bugs as genkernel bugs unless your bug
-* is about the default genkernel configuration...
-*
-* Make sure you have the latest genkernel before reporting bugs.
 </pre>
 
 <p>
-Once <c>genkernel</c> completes, a kernel, full set of modules and 
-<e>initial root disk</e> (initrd) will be created. We will use the kernel 
-and initrd when configuring a boot loader later in this document. Write
-down the names of the kernel and initrd as you will need it when writing
-the bootloader configuration file. The initrd will be started immediately after 
-booting to perform hardware autodetection (just like on the Installation CD) before 
-your "real" system starts up.
+Once <c>genkernel</c> completes, a kernel, full set of modules and <e>initial
+root disk</e> (initrd) will be created. We will use the kernel and initrd when
+configuring a boot loader later in this document. Write down the names of the
+kernel and initrd as you will need it when writing the bootloader configuration
+file. The initrd will be started immediately after booting to perform hardware
+autodetection (just like on the Installation CD) before your "real" system
+starts up.
 </p>
 
 <pre caption="Checking the created kernel image name and initrd">
@@ -404,55 +349,13 @@
 <section id="kernel_modules">
 <title>Installing Separate Kernel Modules</title>
 <subsection>
-<title>Installing Extra Modules</title>
-<body>
-
-<p>
-If appropriate, you should emerge ebuilds for any additional hardware that is 
-on your system. Here is a list of kernel-related ebuilds that you could emerge:
-</p>
-
-<table>
-<tcolumn width="1in"/>
-<tcolumn width="4in"/>
-<tcolumn width="2in"/>
-<tr>
-  <th>Ebuild</th>
-  <th>Purpose</th>
-  <th>Command</th>
-</tr>
-<tr>
-  <ti>x11-drm</ti>
-  <ti>
-    Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and
-    other cards for xorg-x11. Please check the <c>IUSE_VIDEO_CARDS</c> variable
-    in the <path>/usr/portage/x11-base/x11-drm</path> ebuilds to see what you
-    need to fill in as <c>yourcard</c>. 
-  </ti>
-  <ti><c>VIDEO_CARDS="yourcard" emerge x11-drm</c></ti>
-</tr>
-</table>
-
-<p>
-Beware though, some of these ebuilds might deal with big dependencies. To verify
-what packages will be installed by emerging an ebuild, use <c>emerge 
---pretend</c>. For instance, for the <c>x11-drm</c> package:
-</p>
-
-<pre caption="View full installation package listing">
-# <i>emerge --pretend x11-drm</i>
-</pre>
-
-</body>
-</subsection>
-<subsection>
 <title>Configuring the Modules</title>
 <body>
 
 <p>
-You should list the modules you want automatically loaded in 
-<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). 
-You can add extra options to the modules too if you want.
+You should list the modules you want automatically loaded in
+<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
+the modules too if you want.
 </p>
 
 <p>
@@ -467,16 +370,14 @@
 
 <p>
 For instance, to automatically load the <c>3c59x.o</c> module, edit the
-<path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module
-name in it.
+<path>kernel-2.6</path> file and enter the module name in it.
 </p>
 
-<pre caption="Editing /etc/modules.autoload.d/kernel-2.4">
-<comment>(Example for 2.4 kernels)</comment>
-# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i>
+<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
+# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
 </pre>
 
-<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
+<pre caption="/etc/modules.autoload.d/kernel-2.6">
 3c59x
 </pre>
 



1.43                 xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml

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

Index: hb-install-alpha-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- hb-install-alpha-medium.xml	5 Sep 2006 06:50:30 -0000	1.42
+++ hb-install-alpha-medium.xml	7 May 2007 18:11:40 -0000	1.43
@@ -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-alpha-medium.xml,v 1.42 2006/09/05 06:50:30 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml,v 1.43 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2006-09-04</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -80,7 +80,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2006.1/index.xml">Gentoo 2006.1 Handbooks</uri>. 
+link="2007.0/index.xml">Gentoo 2007.0 Handbooks</uri>. 
 </p>
 
 <p>
@@ -112,7 +112,7 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-alpha-minimal-2006.1.iso</c>
+The Minimal Installation CD is called <c>install-alpha-minimal-2007.0.iso</c>
 and takes up only 65 MB of diskspace. You can use this Installation CD to 
 install Gentoo, but always with a working Internet connection only.
 </p>
@@ -142,7 +142,7 @@
 <body>
 
 <p>
-The Universal Installation CD is called <c>install-alpha-universal-2006.1.iso</c>
+The Universal Installation CD is called <c>install-alpha-universal-2007.0.iso</c>
 and consumes about 316 MB on a CD. You can use this Installation CD to install
 Gentoo, and you can even use it to install Gentoo without a working internet
 connection, just in case you want to bring Gentoo to another PC than the one
@@ -171,7 +171,7 @@
 
 </body>
 </subsection>
-<!-- No package CDs for Alpha - 2006.1
+
 <subsection>
 <title>Other CDs</title>
 <body>
@@ -191,7 +191,7 @@
 </p>
 
 </body>
-</subsection>-->
+</subsection>
 <subsection>
 <title>The Stage3 Tarball</title>
 <body>
@@ -224,10 +224,10 @@
 </p>
 
 <p>
-You can download any of the Installation CDs (and, if you want to, a Packages 
-CD as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The
-Installation CDs are located in the <path>releases/alpha/2006.1/installcd</path>
-directory.
+You can download any of the Installation CDs (and, if you want to, a 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.
 </p>
 
 <p>
@@ -238,7 +238,7 @@
 <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>install-alpha-minimal-2006.1.iso.DIGESTS</path>). You can check the MD5 
+<path>install-alpha-minimal-2007.0.iso.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>
@@ -319,13 +319,6 @@
 link="http://dev.gentoo.org/~taviso/milo/">taviso's homepage</uri>.
 </p>
 
-<p>
-This release also includes two entries for people who want to use a serial
-console during the installation, possibly boxes with no keyboard and
-screen attached. One allows you to boot 2.6 using the serial console and
-the other will do the same with our 2.4 kernel.
-</p>
-
 <pre caption="Booting a CD-ROM using SRM">
 <comment>(List available hardware drives)</comment>
 &gt;&gt;&gt; <i>show device</i>
@@ -333,25 +326,15 @@
 <comment>(...)</comment>
 <comment>(Substitute dkb0 with your CD-ROM drive device)</comment>
 &gt;&gt;&gt; <i>boot dkb0 -flags 0</i>
-<comment>To boot the 2.4 kernel instead of the default 2.6 kernel use:</comment>
-&gt;&gt;&gt; <i>boot dkb -flags 1</i>
 <comment>(If you need serial console support)</comment>
-<comment>To boot the 2.6 kernel with serial console support use:</comment>
 &gt;&gt;&gt; <i>boot dkb0 -flags 2</i>
-<comment>To boot the 2.4 kernel with serial console support use:</comment>
-&gt;&gt;&gt; <i>boot dkb0 -flags 3</i>
 </pre>
 
 <pre caption="Booting a CD-ROM using MILO">
 <comment>(Substitute hdb with your CD-ROM drive device)</comment>
 MILO&gt; <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i>
-<comment>To boot the 2.4 kernel instead of the default 2.6 kernel use:</comment>
-MILO&gt; <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i>
 <comment>(If you need serial console support)</comment>
-<comment>To boot the 2.6 kernel with serial console support use:</comment>
 MILO&gt; <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs console=ttyS0 cdroot</i>
-<comment>To boot the 2.4 kernel with serial console support use:</comment>
-MILO&gt; <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs console=ttyS0 cdroot</i>
 </pre>
 
 <p>
@@ -412,8 +395,10 @@
 </p>
 
 <pre caption="Tweaking hard disk performance">
-<comment>Activate DMA:</comment>                                       # <i>hdparm -d 1 /dev/hda</i>
-<comment>Activate DMA + Safe Performance-enhancing Options:</comment>  # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
+<comment>Activate DMA:</comment>
+# <i>hdparm -d 1 /dev/hda</i>
+<comment>Activate DMA + Safe Performance-enhancing Options:</comment>
+# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
 </pre>
 
 </body>
@@ -492,7 +477,7 @@
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>lynx http://www.gentoo.org/doc/en/handbook/handbook-alpha.xml</i>
+# <i>lynx http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
 </pre>
 
 <p>



1.3                  xml/htdocs/doc/en/handbook/hb-install-arm-bootloader.xml

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

Index: hb-install-arm-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-bootloader.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hb-install-arm-bootloader.xml	2 Sep 2006 09:01:29 -0000	1.2
+++ hb-install-arm-bootloader.xml	7 May 2007 18:11:40 -0000	1.3
@@ -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-arm-bootloader.xml,v 1.2 2006/09/02 09:01:29 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-bootloader.xml,v 1.3 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Making your Choice</title>
@@ -62,7 +62,7 @@
 NetWinder machines. No other board uses this and due to its history, the source
 code is no longer available. However, there are firmware images of the last
 release still floating around, so the first thing you want to do is update to
-the last release of 2.3.3. This section is meant as a quickstart not as a
+the last release of 2.3.3. This section is meant as a quickstart, not as a
 replacement for the full <uri
 link="http://www.netwinder.org/howto/Firmware-HOWTO-3.html">Firmware Upgrade
 HOWTO</uri>.
@@ -82,30 +82,30 @@
 <warn>
 If the flashing of your firmware goes wrong, then you will be unable to recover
 via software means. Make sure you've taken all precautions against power
-failure and you read the flashwrite(8) man page.
+failure and you read the <c>flashwrite(8)</c> man page.
 </warn>
 
 <p>
 Now that you have the latest firmware, you've installed the flash utilities,
-your kernel has flash write support, and you've read the flashwrite(8) man
-page, let's flash that sucker!
+your kernel has flash write support, and you've read the <c>flashwrite(8)</c>
+man page, let's flash that sucker!
 </p>
 
 <pre caption="Flashing the NetWinder firmware">
-<comment>First back up your existing firmware</comment>
+<comment>(First back up your existing firmware)</comment>
 # <i>dd if=/dev/nwflash of=/boot/nettrom.old bs=1</i>
 
-<comment>Then write the new firmware</comment>
+<comment>(Then write the new firmware)</comment>
 # <i>flashwrite /boot/nettrom</i>
 
-<comment>Finally verify that the write worked (replace BYTESIZE with the actual byte size of nettrom)</comment>
+<comment>(Finally, verify that the write worked (replace BYTESIZE with the actual byte size of nettrom))</comment>
 # <i>dd if=/dev/nwflash of=/boot/nettrom.new bs=1 count=BYTESIZE</i>
 # <i>cmp /boot/nettrom /boot/nettrom.new</i>
 </pre>
 
 <p>
 If all goes well, you should be able to reboot and not be left with a brick.
-So lets move on to actually booting a kernel.
+Let's move on to actually booting a kernel.
 </p>
 
 </body>
@@ -120,9 +120,9 @@
 </p>
 
 <p>
-Embedding the kernel into flash is pretty easy with the nwlilo utility. Simply
-specify the path to the kernel you wish to embed as well as the kernel
-commandline (note that the root= value is important), and you're done!
+Embedding the kernel into flash is pretty easy with the <c>nwlilo</c> utility.
+Simply specify the path to the kernel you wish to embed as well as the kernel
+commandline (note that the <c>root=</c> value is important), and you're done!
 </p>
 
 <pre caption="Installing the kernel into flash">
@@ -130,7 +130,7 @@
 </pre>
 
 <p>
-The other method is copying the vmlinux ELF to your ext2 boot partition and
+The other method is copying the vmlinuz ELF to your ext2 boot partition and
 configuring NeTTrom to load that. Once you've copied your kernel over, reboot
 the machine as the only way to configure NeTTrom is from inside NeTTrom itself.
 Halt the autoboot process by pressing <c>*</c> twice followed by the return



1.5                  xml/htdocs/doc/en/handbook/hb-install-arm-disk.xml

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

Index: hb-install-arm-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-disk.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- hb-install-arm-disk.xml	16 Feb 2007 13:45:39 -0000	1.4
+++ hb-install-arm-disk.xml	7 May 2007 18:11:40 -0000	1.5
@@ -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-arm-disk.xml,v 1.4 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-disk.xml,v 1.5 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>4.2</version>
-<date>2007-02-16</date>
+<version>5.0</version>
+<date>2007-05-07</date>
 
 <!-- TODO: Add section about MTD and such -->
 
@@ -596,7 +596,7 @@
 
 <pre caption="Applying a filesystem on a partition">
 # <i>mke2fs /dev/hda1</i>
-# <i>mke2fs -j -O dir_index /dev/hda3</i>
+# <i>mke2fs -j /dev/hda3</i>
 </pre>
 
 <p>



1.4                  xml/htdocs/doc/en/handbook/hb-install-arm-kernel.xml

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

Index: hb-install-arm-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-kernel.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- hb-install-arm-kernel.xml	26 Feb 2007 08:54:53 -0000	1.3
+++ hb-install-arm-kernel.xml	7 May 2007 18:11:40 -0000	1.4
@@ -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-arm-kernel.xml,v 1.3 2007/02/26 08:54:53 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-kernel.xml,v 1.4 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2007-02-26</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,7 +26,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -275,6 +276,7 @@
 # <i>make &amp;&amp; make modules_install</i>
 </pre>
 
+
 <p>
 When the kernel has finished compiling, copy the kernel image to
 <path>/boot</path>. Use whatever name you feel is appropriate for your kernel



1.8                  xml/htdocs/doc/en/handbook/hb-install-arm-medium.xml

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

Index: hb-install-arm-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-medium.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-install-arm-medium.xml	2 Sep 2006 09:00:04 -0000	1.7
+++ hb-install-arm-medium.xml	7 May 2007 18:11:40 -0000	1.8
@@ -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/hb-install-arm-medium.xml,v 1.7 2006/09/02 09:00:04 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-arm-medium.xml,v 1.8 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
@@ -30,7 +30,7 @@
 
 <p>
 Generally if you have an ARMv4 or later, it can run Gentoo.  This is pretty
-much a given, so below we'll cover the CPU's that have actually been tested.
+much a given, so below we'll cover the CPUs that have actually been tested.
 </p>
 
 <table>
@@ -63,7 +63,7 @@
 <section>
 <title>Installation Notes</title>
 <subsection>
-<title>A note ABIs</title>
+<title>A note about ABIs</title>
 <body>
 
 <p>
@@ -74,13 +74,12 @@
 
 <p>
 Also, another important concept to grasp is the concept of <b>endianness</b>.
-Endianness refers to the way that a CPU reads words from main memory. A word
-can be read as either <e>big</e> endian (most significant byte first), or
+Endianness refers to the way that a CPU reads words from main memory. A word can
+be read as either <e>big</e> endian (most significant byte first), or
 <e>little</e> endian (least significant byte first). Intel x86 machines are
-generally Little endian, whilst Apple and Sparc machines are Big Endian. On
-ARM, they can be either. To separate them apart, we append <c>eb</c> to the
-architecture name to denote big endian as little endian tends to be more
-common in practice.
+generally Little Endian, whilst Apple and Sparc machines are Big Endian. On ARM,
+they can be either. To separate them, we append <c>eb</c> to the architecture
+name to denote big endian as little endian tends to be more common in practice.
 </p>
 
 </body>



1.90                 xml/htdocs/doc/en/handbook/hb-install-config.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml?rev=1.90&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml?rev=1.90&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml?r1=1.89&r2=1.90

Index: hb-install-config.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- hb-install-config.xml	12 Mar 2007 08:12:38 -0000	1.89
+++ hb-install-config.xml	7 May 2007 18:11:40 -0000	1.90
@@ -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/hb-install-config.xml,v 1.89 2007/03/12 08:12:38 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.90 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
@@ -14,8 +14,8 @@
 proceed.
 </abstract>
 
-<version>7.7</version>
-<date>2007-03-11</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Filesystem Information</title>
@@ -75,7 +75,7 @@
 
 <impo>
 The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
-fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>.
+fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
 </impo>
 
 <pre caption="Opening /etc/fstab">
@@ -139,7 +139,7 @@
 /dev/hda2   none         swap    sw                   0 0
 /dev/hda3   /            ext3    noatime              0 1
 
-proc        /proc        proc    defaults             0 0
+proc        /proc        proc    nodev,nosuid,noexec  0 0
 shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
 
 /dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
@@ -150,7 +150,7 @@
 /dev/sda3   none         swap    sw                   0 0
 /dev/sda4   /            ext3    noatime              0 1
 
-proc        /proc        proc    defaults             0 0
+proc        /proc        proc    nodev,nosuid,noexec  0 0
 shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
 
 /dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
@@ -161,7 +161,7 @@
 /dev/sda2   none         swap    sw                   0 0
 /dev/sda3   /            ext3    noatime              0 1
 
-proc        /proc        proc    defaults             0 0
+proc        /proc        proc    nodev,nosuid,noexec  0 0
 shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
 
 /dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
@@ -175,7 +175,7 @@
 /dev/sda6   /home           ext3        noatime              0 2
 
 openprom    /proc/openprom  openpromfs  defaults             0 0
-proc        /proc           proc        defaults             0 0
+proc        /proc           proc        nodev,nosuid,noexec  0 0
 shm         /dev/shm        tmpfs       nodev,nosuid,noexec  0 0
 
 /dev/cdrom  /mnt/cdrom      auto        noauto,user          0 0
@@ -190,7 +190,7 @@
 /dev/hda4   /            ext3    noatime              0 1
 /dev/hda3   none         swap    sw                   0 0
 
-proc        /proc        proc    defaults             0 0
+proc        /proc        proc    nodev,nosuid,noexec  0 0
 shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
 
 /dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
@@ -200,7 +200,7 @@
 /dev/sda4   /            ext3    noatime              0 1
 /dev/sda3   none         swap    sw                   0 0
 
-proc        /proc        proc    defaults             0 0
+proc        /proc        proc    nodev,nosuid,noexec  0 0
 shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
 
 /dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0
@@ -347,7 +347,7 @@
 
 <pre caption="Manually setting IP information for eth0">
 config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
-routes_eth0=( "default gw 192.168.0.1" )
+routes_eth0=( "default via 192.168.0.1" )
 </pre>
 
 <p>
@@ -382,8 +382,7 @@
 
 <p>
 To have your network interfaces activated at boot, you need to add them to the
-default runlevel. If you have PCMCIA interfaces you should skip this action as
-the PCMCIA interfaces are started by the PCMCIA init script.
+default runlevel.
 </p>
 
 <pre caption="Adding net.eth0 to the default runlevel">
@@ -447,23 +446,11 @@
 <body>
 
 <p>
-PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
-includes users who will be working with a 2.6 kernel (even though they won't be
-using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary 
-to avoid installing xorg-x11 at this moment:
+PCMCIA users should first install the <c>pcmciautils</c> package.
 </p>
 
-<pre caption="Installing pcmcia-cs">
-# <i>USE="-X" emerge pcmcia-cs</i>
-</pre>
-
-<p>
-When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> 
-runlevel:
-</p>
-
-<pre caption="Adding pcmcia to the default runlevel">
-# <i>rc-update add pcmcia default</i>
+<pre caption="Installing pcmciautils">
+# <i>emerge pcmciautils</i>
 </pre>
 
 </body>
@@ -532,11 +519,6 @@
 <c>KEYMAP</c>, you will get weird results when typing on your keyboard.
 </p>
 
-<note test="func:keyval('arch')='SPARC'">
-Users of USB-based SPARC systems and SPARC clones might need to select an i386
-keymap (such as "us") instead of "sunkeymap".
-</note>
-
 <note test="substring(func:keyval('arch'),1,3)='PPC'">
 PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
 keymaps on boot have to enable ADB keycode sendings in their kernel and have to



1.48                 xml/htdocs/doc/en/handbook/hb-install-finalise.xml

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

Index: hb-install-finalise.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-finalise.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- hb-install-finalise.xml	3 Dec 2006 23:05:54 -0000	1.47
+++ hb-install-finalise.xml	7 May 2007 18:11:40 -0000	1.48
@@ -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/hb-install-finalise.xml,v 1.47 2006/12/03 23:05:54 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-finalise.xml,v 1.48 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 system.
 </abstract>
 
-<version>7.1</version>
-<date>2006-12-03</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>User Administration</title>
@@ -115,7 +115,7 @@
 <p>
 Now that you've finished installing Gentoo and rebooted, if everything has gone
 well, you can remove the downloaded stage3 tarball and Portage snapshot from
-your hard disk. Remember that they were downloaded to your root (<path>/</path>)
+your hard disk. Remember that they were downloaded to your <path>/</path>
 directory.
 </p>
 



1.16                 xml/htdocs/doc/en/handbook/hb-install-hppa-bootloader.xml

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

Index: hb-install-hppa-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-bootloader.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- hb-install-hppa-bootloader.xml	30 Aug 2006 23:08:59 -0000	1.15
+++ hb-install-hppa-bootloader.xml	7 May 2007 18:11:40 -0000	1.16
@@ -4,20 +4,20 @@
 <!-- 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-hppa-bootloader.xml,v 1.15 2006/08/30 23:08:59 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-bootloader.xml,v 1.16 2007/05/07 18:11:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Installing PALO</title>
 <body>
 
 <p>
-On the PA-RISC platform, the boot loader is called palo.  You may need to 
-emerge it on your machine first.
+On the PA-RISC platform, the boot loader is called palo. You may need to emerge
+it on your machine first.
 </p>
 
 <pre caption="Installing palo">
@@ -25,28 +25,28 @@
 </pre>
 
 <p>
-You can find the configuration file in <path>/etc/palo.conf</path>.  Here is a 
+You can find the configuration file in <path>/etc/palo.conf</path>. Here is a 
 sample configuration:
 </p>
 
 <pre caption = "/etc/palo.conf example">
---commandline=2/kernel-2.6.16.18-pa11 root=/dev/sda4
+--commandline=2/<keyval id="kernel-name"/> root=/dev/sda4
 --recoverykernel=/vmlinux.old
 --init-partitioned=/dev/sda
 </pre>
 
 <p>
 The first line tells palo the location of the kernel and which boot parameters
-it must use.  <c>2/kernel-2.6.16.18-pa11</c> means the kernel named
-<c>/kernel-2.6.16.18-pa11</c> resides on the second partition.  Beware, the
+it must use. <c>2/<keyval id="kernel-name"/></c> means the kernel named
+<c>/<keyval id="kernel-name"/></c> resides on the second partition. Beware, the
 path to the kernel is relative to the boot partition, not to the root
 partition.
 </p>
 
 <p>
-The second line indicates which recovery kernel to use.  If it is your
+The second line indicates which recovery kernel to use. If it is your
 first install and you do not have a recovery kernel, please comment this
-out.  The third line indicates on which disk palo will reside. 
+out. The third line indicates on which disk palo will reside. 
 </p>
 
 <p>



1.22                 xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml

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

Index: hb-install-hppa-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- hb-install-hppa-disk.xml	16 Feb 2007 13:45:39 -0000	1.21
+++ hb-install-hppa-disk.xml	7 May 2007 18:11:41 -0000	1.22
@@ -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-hppa-disk.xml,v 1.21 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v 1.22 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2007-02-16</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -290,7 +290,7 @@
 
 <pre caption="Applying a filesystem on a partition">
 # <i>mke2fs /dev/sda2</i>
-# <i>mke2fs -j -O dir_index /dev/sda4</i>
+# <i>mke2fs -j /dev/sda4</i>
 </pre>
 
 <p>



1.38                 xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml

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

Index: hb-install-hppa-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-hppa-kernel.xml	13 Mar 2007 00:30:09 -0000	1.37
+++ hb-install-hppa-kernel.xml	7 May 2007 18:11:41 -0000	1.38
@@ -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-hppa-kernel.xml,v 1.37 2007/03/13 00:30:09 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v 1.38 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.5</version>
-<date>2007-03-12</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,7 +26,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -47,9 +48,7 @@
 
 <p>
 For HPPA we have <c>hppa-sources</c>. By default, these sources are based on the
-2.6 kernel sources. If you want to install a 2.4 kernel, you will need to
-install Gentoo from a working Internet connection as we do not supply those
-sources on our Installation CD. Continue by installing the kernel source.
+2.6 kernel sources.
 </p>
 
 <pre caption="Installing a kernel source">
@@ -59,13 +58,13 @@
 <p>
 When you take a look in <path>/usr/src</path> you should see a symlink called
 <path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>hppa-sources-2.6.16.18-pa11</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>hppa-sources-<keyval id="kernel-version"/></c>. Your
+version may be different, so keep this in mind.
 </p>
 
 <pre caption="Viewing the kernel source symlink">
 # <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.16.18-pa11
+lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
 </pre>
 
 <p>
@@ -179,8 +178,8 @@
 
 <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.
+does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
+when configured to do kernel mode PPPoE.
 </p>
 
 <p>
@@ -290,14 +289,15 @@
 </p>
 
 <p>
-Now that your kernel source tree is installed, it's now time to compile your 
-kernel by using our <c>genkernel</c> script to automatically build a kernel for 
-you. <c>genkernel</c> works by configuring a kernel nearly identically to the 
-way our Installation CD kernel is configured. This means that when you use 
-<c>genkernel</c> to build your kernel, your system will generally detect all 
-your hardware at boot-time, just like our Installation CD does. Because genkernel 
-doesn't require any manual kernel configuration, it is an ideal solution for 
-those users who may not be comfortable compiling their own kernels.
+Now that your kernel source tree is installed, it's now time to compile your
+kernel by using our <c>genkernel</c> script to automatically build a kernel for
+you. <c>genkernel</c> works by configuring a kernel nearly identically to the
+way our Installation CD kernel is configured. This means that when you use
+<c>genkernel</c> to build your kernel, your system will generally detect all
+your hardware at boot-time, just like our Installation CD does. Because
+genkernel doesn't require any manual kernel configuration, it is an ideal
+solution for those users who may not be comfortable compiling their own
+kernels.
 </p>
 
 <p>
@@ -323,22 +323,6 @@
 
 <pre caption="Running genkernel">
 # <i>genkernel all</i>
-<comment>(Output removed to increase readability)</comment>
-* Kernel compiled successfully!
-* Required Kernel Params:
-*   : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT
-*     where $ROOT is the devicenode for your root partition as
-*     you should have specified in /etc/fstab
-*              
-* You MUST tell your bootloader to use the generated initrd
-*              
-* Recommended Kernel Params:
-*   : vga=0x317 splash=verbose
-*              
-* Do NOT report kernel bugs (configs included) as genkernel bugs.
-* Make sure you have the latest genkernel before reporting bugs
-*              
-* For more info see /usr/share/genkernel/README
 </pre>
 
 <p>



1.44                 xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml

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

Index: hb-install-hppa-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- hb-install-hppa-medium.xml	28 Mar 2007 16:34:19 -0000	1.43
+++ hb-install-hppa-medium.xml	7 May 2007 18:11:41 -0000	1.44
@@ -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-hppa-medium.xml,v 1.43 2007/03/28 16:34:19 cam Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml,v 1.44 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2007-03-28</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -34,7 +34,7 @@
 additional information about your box in the <uri
 link="http://hwdb.parisc-linux.org">Parisc-Linux Hardware Database</uri> and
 the <uri link="http://www.openpa.net/cpu.html">processor list</uri> on
-<uri link="http://www.openpa.net">www.openpa.net</uri>.
+<uri>www.openpa.net</uri>.
 </p>
 
 <p>
@@ -87,7 +87,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2006.1/index.xml">Gentoo 2006.1 Handbooks</uri>.
+link="2007.0/index.xml">Gentoo 2007.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -119,7 +119,7 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-hppa-minimal-2006.1.iso</c> 
+The Minimal Installation CD is called <c>install-hppa-minimal-2007.0.iso</c> 
 and takes up only 75 MB of diskspace. You can use this Installation CD to 
 install Gentoo, but always with a working Internet connection only.
 </p>
@@ -149,7 +149,7 @@
 <body>
 
 <p>
-The Universal Installation CD is called <c>install-hppa-universal-2006.1.iso</c>
+The Universal Installation CD is called <c>install-hppa-universal-2007.0.iso</c>
 and consumes about 339 MB on a CD. You can use this Installation CD to install
 Gentoo, and you can even use it to install Gentoo without a working internet
 connection, just in case you want to bring Gentoo to another PC than the one
@@ -230,7 +230,7 @@
 <p>
 You can download any of the Installation CDs (and, if you want to, a Packages 
 CD as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The
-Installation CDs are located in the <path>releases/hppa/2006.1/installcd</path> 
+Installation CDs are located in the <path><keyval id="release-dir"/>installcd</path> 
 directory.
 </p>
 
@@ -542,7 +542,7 @@
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
 </pre>
 
 <p>



1.4                  xml/htdocs/doc/en/handbook/hb-install-ia64-disk.xml

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

Index: hb-install-ia64-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-disk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- hb-install-ia64-disk.xml	16 Feb 2007 13:45:39 -0000	1.3
+++ hb-install-ia64-disk.xml	7 May 2007 18:11:41 -0000	1.4
@@ -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-ia64-disk.xml,v 1.3 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-disk.xml,v 1.4 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>2.4</version>
-<date>2007-02-16</date>
+<version>3.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -557,30 +557,7 @@
 
 <pre caption="Applying a filesystem on a partition">
 # <i>mkdosfs /dev/sda1</i>
-mkdosfs 2.10 (22 Sep 2003)
-
-# <i>mke2fs -j -O dir_index /dev/sda3</i>
-mke2fs 1.36 (05-Feb-2005)
-Filesystem label=
-OS type: Linux
-Block size=4096 (log=2)
-Fragment size=4096 (log=2)
-4382336 inodes, 8752348 blocks
-437617 blocks (5.00%) reserved for the super user
-First data block=0
-268 block groups
-32768 blocks per group, 32768 fragments per group
-16352 inodes per group
-Superblock backups stored on blocks: 
-        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
-        4096000, 7962624
-
-Writing inode tables: done                            
-Creating journal (8192 blocks): done
-Writing superblocks and filesystem accounting information: done
-
-This filesystem will be automatically checked every 26 mounts or
-180 days, whichever comes first.  Use tune2fs -c or -i to override.
+# <i>mke2fs -j /dev/sda3</i>
 </pre>
 
 </body>



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

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

Index: hb-install-ia64-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- hb-install-ia64-kernel.xml	13 Mar 2007 00:30:09 -0000	1.4
+++ hb-install-ia64-kernel.xml	7 May 2007 18:11:41 -0000	1.5
@@ -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-ia64-kernel.xml,v 1.4 2007/03/13 00:30:09 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v 1.5 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.4</version>
-<date>2007-03-12</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,7 +26,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -218,8 +219,8 @@
 
 <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.
+does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
+when configured to do kernel mode PPPoE.
 </p>
 
 <p>



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

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

Index: hb-install-ia64-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-medium.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-ia64-medium.xml	3 Sep 2006 05:02:44 -0000	1.1
+++ hb-install-ia64-medium.xml	7 May 2007 18:11:41 -0000	1.2
@@ -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-ia64-medium.xml,v 1.1 2006/09/03 05:02:44 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-medium.xml,v 1.2 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>4.0</version>
-<date>2006-08-30</date>
+<version>5.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -61,7 +61,7 @@
 <impo>
 If you wish to install Gentoo without a working Internet connection, or would
 like to use one of the provided installers, please use the installation
-instructions described in the <uri link="2006.1/">Gentoo 2006.1
+instructions described in the <uri link="2007.0/">Gentoo 2007.0
 Handbooks</uri>.
 </impo>
 
@@ -373,7 +373,6 @@
 <pre caption="Tweaking hard disk performance">
 <comment>(Activate DMA:)</comment>
 # <i>hdparm -d 1 /dev/hda</i>
-
 <comment>(Activate Safe Performance Options:)</comment>
 # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
 </pre>



1.18                 xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml

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

Index: hb-install-mips-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- hb-install-mips-bootloader.xml	7 Feb 2007 15:12:43 -0000	1.17
+++ hb-install-mips-bootloader.xml	7 May 2007 18:11:41 -0000	1.18
@@ -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-mips-bootloader.xml,v 1.17 2007/02/07 15:12:43 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.18 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2007-02-08</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section id="sgi">
 <title>Silicon Graphics Machines -- Setting Up arcload</title>
@@ -136,11 +136,12 @@
 </pre>
 
 <p>
-Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may
-reside either in the volume header, or on an EXT2/3 partition.  If you wish to
-utilise this newer feature, you may instead place the files in your
-<path>/boot</path> partition (or <path>/</path> if your boot partition is not
-separate).
+Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may reside
+either in the volume header, or on a partition. If you wish to utilise this
+newer feature, you may instead place the files in your <path>/boot</path>
+partition (or <path>/</path> if your boot partition is not separate).
+<c>arcload</c> uses the filesystem driver code from the popular <c>grub</c>
+bootloader, and thus supports the same range of filesystems.
 </p>
 
 <pre caption="Placing arc.cf and kernel in the volume header">
@@ -173,7 +174,7 @@
 <ul>
   <li>
     There's a 675kB (approximate) limit on kernels. The current size of Linux
-    2.4 makes it damn near impossible to make a kernel this size. Linux 2.6 is
+    2.4 makes it nearly impossible to make a kernel this size. Linux 2.6 is
     totally out of the question.
   </li>
   <li>
@@ -436,8 +437,8 @@
 # <i>exit</i>
 
 <comment>(Unmount the drives)</comment>
-# <i>umount /gentoo/boot</i>
-# <i>umount /gentoo</i>
+# <i>umount /mnt/gentoo/boot</i>
+# <i>umount /mnt/gentoo</i>
 
 <comment>(Reboot)</comment>
 # <i>reboot</i>
@@ -552,7 +553,7 @@
 
 <p>
 Starting with <c>arcload-0.5</c>, files no longer need to be placed in the
-volume header -- they may be placed in an EXT2/3 partition instead.  To tell
+volume header -- they may be placed in a partition instead.  To tell
 <c>arcload</c> where to look for its configuration file and kernels, one must
 set the <c>OSLoadPartition</c> PROM variable.  The exact value here will depend
 on where your disk resides on the SCSI bus.  Use the <c>SystemPartition</c> PROM



1.23                 xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml

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

Index: hb-install-mips-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- hb-install-mips-disk.xml	16 Feb 2007 13:45:39 -0000	1.22
+++ hb-install-mips-disk.xml	7 May 2007 18:11:41 -0000	1.23
@@ -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-mips-disk.xml,v 1.22 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v 1.23 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>1.16</version>
-<date>2007-02-16</date>
+<version>2.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -223,15 +223,6 @@
 image allowed eight-character names.
 </p>
 
-<note>
-On SGI systems, there are two bootloaders available: <c>arcboot</c> and
-<c>arcload</c>. Currently, only the Indy, Indigo2 (R4k variety), Challenge S
-and O2 are capable of using <c>arcboot</c> as a bootloader, whereas
-<c>arcload</c> runs on all the Linux-supported SGI machines. Unlike
-<c>arcboot</c> however, <c>arcload</c> cannot presently read EXT2/3 partitions,
-and thus, loads its kernels from the volume header.
-</note>
-
 <p>
 The process of making the volume header larger isn't exactly straight-forward;
 there's a bit of a trick to it. One cannot simply delete and re-add the volume
@@ -640,7 +631,7 @@
 
 <pre caption="Applying a filesystem on a partition">
 # <i>mke2fs /dev/sda1</i>
-# <i>mke2fs -j -O dir_index /dev/sda3</i>
+# <i>mke2fs -j /dev/sda3</i>
 </pre>
 
 <p>
@@ -655,13 +646,6 @@
 partition using the command: <c>mke2fs -r 0 /dev/hda1</c>.
 </warn>
 
-<warn>
-Also, be aware that arcboot currently is not able to read any filesystem other
-than EXT2, EXT3 and ISO9660 (recent versions). For that reason,
-<path>/boot</path> on SGI machines must also reside on an EXT2 or EXT3
-partition.
-</warn>
-
 </body>
 </subsection>
 <subsection>



1.24                 xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml

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

Index: hb-install-mips-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-mips-kernel.xml	26 Feb 2007 08:54:53 -0000	1.23
+++ hb-install-mips-kernel.xml	7 May 2007 18:11:41 -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/hb-install-mips-kernel.xml,v 1.23 2007/02/26 08:54:53 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml,v 1.24 2007/05/07 18:11:41 nightmorph Exp $ -->
 <!-- :vim:ts=2:sts=2:et:tw=80: -->
 <sections>
 
-<version>7.1</version>
-<date>2007-02-26</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,14 +17,17 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</path>. Please avoid the
 <path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
 indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8.
 </p>
 
-<pre caption="Setting the timezone information to GMT">
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+<pre caption="Setting the timezone information">
+# <i>ls /usr/share/zoneinfo</i>
+<comment>(Suppose you want to use GMT)</comment>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -46,97 +49,35 @@
 
 <p>
 MIPS-based systems have just the one kernel tree to choose from,
-<c>mips-sources</c>. <!--Special patches are needed to make certain systems work.
-The table below displays the USE flags required to enable the patchsets. Note
-that Indy, Indigo2 (R4k) and Challenge S systems do not require any additional
-patchsets.-->  This patchset differs from the ones available for other
-architectures, in that it has lots of patches specific to the MIPS architecture.
+<c>mips-sources</c>. This patchset differs from the ones available for other
+architectures, in that it has lots of patches specific to the MIPS
+architecture.
 </p>
 
-<!--
-<table>
-<tr>
-  <th>USE flag</th>
-  <th>System</th>
-</tr>
-<tr>
-  <ti><c>cobalt</c></ti>
-  <ti>Cobalt Qube/RaQ support</ti>
-</tr>
-<tr>
-  <ti><c>ip27</c></ti>
-  <ti>SGI Origin 200/2000 support (1)</ti>
-</tr>
-<tr>
-  <ti><c>ip28</c></ti>
-  <ti>SGI Indigo2 Impact (R10000) support (1,2)</ti>
-</tr>
-<tr>
-  <ti><c>ip30</c></ti>
-  <ti>SGI Octane/Octane2 support (1)</ti>
-</tr>
-</table>-->
-
 <pre caption="Merging kernel sources...">
-<!-- Done by profile?
-<comment>(Substitute cobalt with the appropriate USE flag for your system if required)</comment>
-# <i>mkdir /etc/portage</i>
-# <i>echo "sys-kernel/mips-sources cobalt" &gt;&gt; /etc/portage/package.use</i>
--->
-<comment>(Unpack &amp; install the kernel sources)</comment>
 # <i>emerge mips-sources</i>
 </pre>
 
 <impo>
-<!--(1)--> On the Origin 200/2000, Indigo2 Impact (R10000), Octane/Octane2 and
-O2, a 64-bit kernel is required to boot these systems. For these machines, you
-should <!--switch to the <path>default-linux/mips/mips64/RELEASE</path>
-profile by altering the <path>/etc/make.profile</path> symlink.
-Then you can --><c>emerge
-kgcc64</c> to create a cross-compiler for building 64-bit kernels.
+On the Origin 200/2000, Indigo2 Impact (R10000), Octane/Octane2 and O2, a 64-bit
+kernel is required to boot these systems. For these machines, you should
+<c>emerge kgcc64</c> to create a cross-compiler for building 64-bit kernels.
 </impo>
 
-<!--<impo>
-(2) The Indigo2 Impact is a special case in that it requires special patch to
-be applied to <c>gcc</c> before it will build an IP28 kernel correctly. This
-patch adds support for the <c>-mip28-cache-barriers</c> CFLAG, which is used
-when building kernels to work around the inherent hardware bug brought on by
-speculative execution. This USE flag can be set in <path>/etc/make.conf</path>.
-This is done for you by setting your profile to
-<path>default-linux/mips/mips64/ip28/RELEASE</path>, which also takes care of
-(1).
-</impo>-->
-
 <pre caption="Installing kgcc64...">
-<!--<comment>(This assumes PORTDIR is in the usual location; /usr/portage)</comment>
-# <i>rm /etc/make.profile</i>
-# <i>ln -s /usr/portage/profiles/default-linux/mips/mips64/2005.0</i> <comment>(or .../mips64/ip28/2005.0)</comment>
-
-<comment>(Install the 64-bit kernel toolchain)</comment>
---># <i>emerge kgcc64</i>
+# <i>emerge kgcc64</i>
 </pre>
 
 <p>
 When you take a look in <path>/usr/src</path> you should see a symlink called
 <path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>mips-sources-2.6.13.4</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>mips-sources-<keyval id="kernel-version"/></c>. Your
+version may be different, so keep this in mind.
 </p>
 
 <pre caption="Viewing the kernel source symlink">
 # <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.13.4
-</pre>
-
-<p>
-If this isn't the case (i.e. the symlink points to a different kernel source)
-change the symlink before you continue:
-</p>
-
-<pre caption="Changing the kernel source symlink">
-# <i>rm /usr/src/linux</i>
-# <i>cd /usr/src</i>
-# <i>ln -s linux-2.6.13.4 linux</i>
+lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
 </pre>
 
 <p>
@@ -190,7 +131,7 @@
 <tr>
   <ti>Indigo2 Impact (R10k)</ti>
   <ti>
-    <c>make ip28_defconfig</c> (requires <c>mips-sources-2.6.14.5</c> or later)
+    <c>make ip28_defconfig</c>
   </ti>
 </tr>
 <tr>
@@ -303,19 +244,16 @@
 </note>
 
 <pre caption="Compiling the kernel">
-<comment>(For 2.4 kernel only)</comment>
-# <i>make dep</i>
-
-<comment>(2.4 and 2.6 kernels -- compiling natively)</comment>
+<comment>(Compiling natively)</comment>
 # <i>make vmlinux modules modules_install</i>
 
-<comment>(2.4 and 2.6 kernels -- cross-compiling on target machine)</comment>
-<comment>(    Adjust the mips64-unknown-linux-gnu- accordingly    )</comment>
+<comment>(Cross-compiling on target machine)</comment>
+<comment>(Adjust the mips64-unknown-linux-gnu- accordingly)</comment>
 # <i>make vmlinux modules modules_install CROSS_COMPILE=mips64-unknown-linux-gnu-</i>
 
-<comment>(When compiling on another machine, such as an x86 box... use the)</comment>
-<comment>( following commands to compile the kernel &amp; install modules into)</comment>
-<comment>(  a specific directory to be transferred to the target machine. )</comment>
+<comment>(When compiling on another machine, such as an x86 box, use the)</comment>
+<comment>(following commands to compile the kernel &amp; install modules into)</comment>
+<comment>(a specific directory to be transferred to the target machine.)</comment>
 # <i>make vmlinux modules CROSS_COMPILE=mips64-unknown-linux-gnu-</i>
 # <i>make modules_install INSTALL_MOD_PATH=/somewhere</i>
 </pre>
@@ -343,10 +281,10 @@
 </note>
 
 <pre caption="Installing the kernel">
-# <i>cp vmlinux /boot/kernel-2.6.13.4</i>
+# <i>cp vmlinux /boot/kernel-<keyval id="kernel-version"/></i>
 
 <comment>(Cobalt Servers -- Compressing the kernel image)</comment>
-# <i>gzip -9v /boot/kernel-2.6.13.4</i>
+# <i>gzip -9v /boot/kernel-<keyval id="kernel-version"/></i>
 </pre>
 
 </body>
@@ -359,21 +297,9 @@
 <body>
 
 <p>
-You should list the modules you want automatically loaded in one of the
-relevant files listed below. You can add extra options to the modules too if
-you want.
-</p>
-
-<ul>
-  <li><path>/etc/modules.autoload.d/kernel-2.4</path> - Kernel 2.4 only</li>
-  <li><path>/etc/modules.autoload.d/kernel-2.6</path> - Kernel 2.6 only</li>
-  <li><path>/etc/modules.autoload</path> - All Kernels</li>
-</ul>
-
-<p>
-Therefore, if you have a kernel module that you want to load -- which is common
-to both 2.4 and 2.6, then place it in <path>/etc/modules.autoload</path>.
-Otherwise it can be placed in the appropriate file.
+You should list the modules you want automatically loaded in
+<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
+the modules too if you want.
 </p>
 
 <p>
@@ -388,27 +314,18 @@
 
 <p>
 For instance, to automatically load the <c>3c59x.o</c> module, edit the
-appropriate file and enter the module name in it.
+<path>kernel-2.6</path> file and enter the module name in it.
 </p>
 
-<pre caption="Editing /etc/modules.autoload.d/kernel-2.4">
-# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i>
+<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
+# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
 </pre>
 
-<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
+<pre caption="/etc/modules.autoload.d/kernel-2.6">
 3c59x
 </pre>
 
 <p>
-This can be also done in a one-liner:
-</p>
-
-<pre caption="Adding a module -- the one-liner method">
-# <i>echo '3c59x' >> /etc/modules.autoload.d/kernel-2.4</i>
-<comment>(or kernel-2.6, or /etc/modules.autoload...)</comment>
-</pre>
-
-<p>
 Continue the installation with <uri link="?part=1&amp;chap=8">Configuring your
 System</uri>.
 </p>



1.22                 xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml

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

Index: hb-install-mips-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- hb-install-mips-medium.xml	30 Aug 2006 22:52:28 -0000	1.21
+++ hb-install-mips-medium.xml	7 May 2007 18:11:41 -0000	1.22
@@ -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-mips-medium.xml,v 1.21 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml,v 1.22 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -39,11 +39,11 @@
 </tr>
 <tr>
   <th>Memory</th>
-  <ti>64 MB</ti>
+  <ti>128 MB</ti>
 </tr>
 <tr>
   <th>Diskspace</th>
-  <ti>1.5 GB (excluding swap space)</ti>
+  <ti>3.0 GB (excluding swap space)</ti>
 </tr>
 <tr>
   <th>Swap space</th>
@@ -133,14 +133,16 @@
     <ti>MIPS32</ti>
     <ti>32-bit</ti>
     <ti>
-      AMD Alchemy series, 4kc, 4km, many others...
+      AMD Alchemy series, 4kc, 4km, many others... There are a few revisions in
+      the MIPS32 ISA.
     </ti>
   </tr>
   <tr>
     <ti>MIPS64</ti>
     <ti>64-bit</ti>
     <ti>
-      Broadcom SiByte SB1, 5kc ... etc...
+      Broadcom SiByte SB1, 5kc ... etc... There are a few revisions in the
+      MIPS64 ISA.
     </ti>
   </tr>
 </table>
@@ -186,7 +188,7 @@
     <ti><c>mipsel</c></ti>
     <ti>32-bit</ti>
     <ti>Little Endian</ti>
-    <ti>DECStations, Cobalt Servers, PlayStation 2</ti>
+    <ti>Cobalt Servers</ti>
   </tr>
   <tr>
     <ti><c>mips64</c></ti>
@@ -198,7 +200,7 @@
     <ti><c>mips64el</c></ti>
     <ti>64-bit</ti>
     <ti>Little Endian</ti>
-    <ti>Cobalt Servers, PlayStation 2</ti>
+    <ti>Cobalt Servers</ti>
   </tr>
 </table>
 
@@ -273,7 +275,8 @@
   <li>
     In General:
     <ul>
-      <li>DHCP/BOOTP server (ISC DHCPd recommended)</li>
+      <li>DHCP/BOAMD Alchemy series, 4kc, 4km, many others... There are a few revisions in
+      the MIPS32 ISA.OTP server (ISC DHCPd recommended)</li>
       <li>Patience -- and lots of it</li>
     </ul>
   </li>
@@ -284,7 +287,10 @@
       <li>
         If you want/need to use serial console:
         <ul>
-          <li>MiniDIN8 --&gt; RS-232 serial cable</li>
+          <li>
+	    MiniDIN8 --&gt; RS-232 serial cable (only needed for IP22 and IP28
+	    systems)
+	  </li>
           <li>Null-modem cable</li>
           <li>VT100 or ANSI compatible terminal capable of 9600 baud</li>
         </ul>
@@ -437,7 +443,7 @@
   </tr>
   <tr>
     <ti>IP22</ti>
-    <ti>Indy, *Indigo 2, **Challenge S</ti>
+    <ti>Indy, *Indigo 2, Challenge S</ti>
   </tr>
   <tr>
     <ti>IP26</ti>
@@ -469,19 +475,12 @@
 in mind that these are different machines.
 </note>
 
-<note>
-** On the Challenge S, the UTP network port is hung off a WD33C95 SCSI card,
-which is currently unsupported on Linux. Because of this limitation, you'll
-need to use an AUI--&gt;UTP transceiver connected to the AUI port.
-</note>
-
 <p>
-Also in the filename, r4k refers to R4000-series processors, r5k for R5000,
-rm5k for the RM5200 and r10k for R10000. You will find the images available at
-<uri link="http://dev.gentoo.org/~kumba/mips/netboot">
-http://dev.gentoo.org/~kumba/mips/netboot.
-</uri>
+Also in the filename, r4k refers to R4000-series processors, r5k for R5000, rm5k
+for the RM5200 and r10k for R10000. You will find the images available on the
+Gentoo <uri link="/main/en/mirrors.xml">mirrors</uri>.
 </p>
+
 </body>
 </subsection>
 
@@ -707,13 +706,12 @@
 </p>
 
 <warn>
-These CDs are highly experimental at this time. They may or may not work at
-this time. You can report success or failures either on
-<uri link="http://bugs.gentoo.org">Bugzilla</uri>,
-<uri link="http://forums.gentoo.org/viewtopic.php?t=242518">this forum
-thread</uri> or in the <c>#gentoo-mips</c>
-<uri link="http://www.gentoo.org/main/en/irc.xml">IRC channel</uri>. We would
-love to hear from you.
+These CDs are highly experimental at this time. They may or may not work at this
+time. You can report success or failures either on <uri
+link="http://bugs.gentoo.org">Bugzilla</uri>, <uri
+link="http://forums.gentoo.org/viewtopic.php?t=242518">this forum thread</uri>
+or in the <c>#gentoo-mips</c> <uri link="/main/en/irc.xml">IRC channel</uri>. We
+would love to hear from you.
 </warn>
 
 </body>



1.8                  xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml?r1=1.7&r2=1.8

Index: hb-install-mips-stage.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-install-mips-stage.xml	30 Mar 2007 12:01:19 -0000	1.7
+++ hb-install-mips-stage.xml	7 May 2007 18:11:41 -0000	1.8
@@ -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-mips-stage.xml,v 1.7 2007/03/30 12:01:19 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml,v 1.8 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2007-03-26</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Installing a Stage Tarball</title>
@@ -51,39 +51,23 @@
 <p>
 The next step you need to perform is to install the <e>stage</e> tarball of
 your choice onto your system. 
-<!--You have the option of downloading the required
-tarball from the Internet or, if you are booted from one of the Gentoo
-Universal Installation CDs, copy it over from the CD itself. If you have a 
-Universal CD and the stage you want to use is on the CD, downloading it from 
-the Internet is just a waste of bandwidth as the stage files are the same. In 
-most cases, the command <c>uname -m</c> can be used to help you decide which 
-stage file to download. -->
-</p>
-
-<!--
-<ul>
-<li><uri link="#doc_chap2">Default: Using a Stage from the Internet</uri></li>
-<li>
-  <uri link="#doc_chap3">Alternative: Using a Stage from the Installation CD</uri>
-</li>
-</ul>-->
+</p>
 
 </body>
 </subsection>
 </section>
 <section>
 <title>Downloading the Stage Tarball</title>
-<!--<title>Default: Using a Stage from the Internet</title>-->
 <subsection>
 <body>
 
 <p>
 Go to the Gentoo mountpoint at which you mounted your filesystems
-(most likely <path>/gentoo</path>):
+(most likely <path>/mnt/gentoo</path>):
 </p>
 
 <pre caption="Going to the Gentoo mountpoint">
-# <i>cd /gentoo</i>
+# <i>cd /mnt/gentoo</i>
 </pre>
 
 <p>
@@ -137,8 +121,25 @@
   </ti>
   <ti><c>cobalt/stage#-mipsel4-RELEASE.tar.bz2</c></ti>
 </tr>
+<tr>
+  <ti>
+    Little Endian<br />
+    <e>(Others)</e>
+  </ti>
+  <ti>
+    All Standard CPU Types
+  </ti>
+  <ti><c>cobalt/stage#-mipsel1-RELEASE.tar.bz2</c></ti>
+</tr>
 </table>
 
+<warn>
+Although we provide stages for little-endian MIPS1, support for little endian
+MIPS systems is still restricted to the Cobalt server range. They are provided
+for those who may wish to experiment with Gentoo on presently unsupported
+platforms, thus it is assumed that you know what you're doing.
+</warn>
+
 <p>
 If you need to go through a proxy, export the <c>http_proxy</c> and
 <c>ftp_proxy</c> variables:
@@ -156,18 +157,21 @@
 </p>
 
 <pre caption="Fetching the tarball via wget">
-# <i>wget -c http://distfiles.gentoo.org/releases/mips/2006.1/stages/mips4/stage3-mips4-2006.1.tar.bz2</i>
+# <i>wget -c http://distfiles.gentoo.org/releases/mips/mips4/stage3-mips4-2007.0.tar.bz2</i>
 </pre>
 
 <p>
 If you want to check the integrity of the downloaded stage tarball, use
-<c>md5sum</c> and compare the output with the MD5 checksum provided on the
-mirror. For instance, to check the validity of the mips4 stage tarball:
+<c>md5sum</c> or <c>sha1sum</c> and compare the output with the MD5 checksum
+provided on the mirror. For instance, to check the validity of the mips4 stage
+tarball:
 </p>
 
 <pre caption="Example checking integrity of a stage tarball">
-# <i>md5sum -c stage3-mips4-2006.1.tar.bz2.md5</i>
-stage3-mips4-2006.1.tar.bz2: OK
+# <i>md5sum -c stage3-mips4-2007.0.tar.bz2.DIGESTS</i>
+stage3-mips4-2007.0.tar.bz2: OK
+# <i>sha1sum -c stage3-mips4-2007.0.tar.bz2.DIGESTS</i>
+stage3-mips4-2007.0.tar.bz2: OK
 </pre>
 
 </body>
@@ -220,11 +224,11 @@
 
 <p>
 Go to the mountpoint where you mounted your filesystem (most likely
-<path>/gentoo</path>):
+<path>/mnt/gentoo</path>):
 </p>
 
 <pre caption="Going to the Gentoo mountpoint">
-# <i>cd /gentoo</i>
+# <i>cd /mnt/gentoo</i>
 </pre>
 
 <p>
@@ -235,7 +239,7 @@
 </p>
 
 <pre caption="Extracting the Portage snapshot">
-# <i>tar -xjf portage-*.tar.bz2 -C /gentoo/usr</i>
+# <i>tar -xjf portage-*.tar.bz2 -C /mnt/gentoo/usr</i>
 </pre>
 
 </body>
@@ -258,7 +262,7 @@
 
 <note>
 A commented listing of all possible variables can be found in
-<path>/gentoo/etc/make.conf.example</path>. For a successful Gentoo 
+<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo 
 installation you'll only need to set the variables which are mentioned beneath.
 </note>
 
@@ -269,7 +273,7 @@
 </p>
 
 <pre caption="Opening /etc/make.conf">
-# <i>nano -w /gentoo/etc/make.conf</i>
+# <i>nano -w /mnt/gentoo/etc/make.conf</i>
 </pre>
 
 <p>
@@ -343,13 +347,13 @@
 </pre>
 
 <p>
-A very important setting in the MIPS world, is the <c>-mabi=</c> flag.  MIPS has
-3 different ABIs; <c>32</c> (pure 32-bit, aka <c>o32</c>), <c>64</c> (full
+A very important setting in the MIPS world is the <c>-mabi=</c> flag.  MIPS has
+3 different ABIs: <c>32</c> (pure 32-bit, aka <c>o32</c>), <c>64</c> (full
 64-bit, aka <c>n64</c>) and <c>n32</c>
 (a mix of 32-bit data structures with 64-bit instructions).  This
 flag selects which of these you wish to use.  Note you need libraries for the
 ABI you select.  In layman's terms, this means, for example, you can't use
-<c>-mabi=64</c> on a 32-bit userland (or even a <c>n32</c> userland).
+<c>-mabi=64</c> on a 32-bit userland (or even an <c>n32</c> userland).
 </p>
 
 <p>
@@ -396,7 +400,7 @@
 <body>
 
 <p>
-Update your <path>/gentoo/etc/make.conf</path> to your own preference and
+Update your <path>/mnt/gentoo/etc/make.conf</path> to your own preference and
 save (<c>nano</c> users would hit <c>Ctrl-X</c>). You are now ready to continue
 with <uri link="?part=1&amp;chap=6">Installing the Gentoo Base System</uri>.
 </p>



1.4                  xml/htdocs/doc/en/handbook/hb-install-mips-system.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-system.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-system.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-system.xml?r1=1.3&r2=1.4

Index: hb-install-mips-system.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-system.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- hb-install-mips-system.xml	9 Nov 2006 07:39:39 -0000	1.3
+++ hb-install-mips-system.xml	7 May 2007 18:11:41 -0000	1.4
@@ -4,56 +4,15 @@
 <!-- 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-mips-system.xml,v 1.3 2006/11/09 07:39:39 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-system.xml,v 1.4 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2006-11-08</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Chrooting</title>
-<!--<subsection>	MIPS install media doesn't include mirrorselect
-<title>Optional: Selecting Mirrors</title>
-<body>
-
-<p>
-In order to download source code quickly it is recommended to select a fast
-mirror. Portage will look in your <path>make.conf</path> file for the
-GENTOO_MIRRORS variable and use the mirrors listed therein. You can surf to
-our <uri link="/main/en/mirrors.xml">mirror list</uri> and search
-for a mirror (or mirrors) close to you (as those are most frequently the 
-fastest ones), but we provide a nice tool called <c>mirrorselect</c> which
-provides you with a nice interface to select the mirrors you want.
-</p>
-  
-<pre caption="Using mirrorselect for the GENTOO_MIRRORS variable">
-# <i>mirrorselect -i -o &gt;&gt; /mnt/gentoo/etc/make.conf</i>
-</pre>
-
-<warn>
-Do not select any IPv6 mirrors. Our stages currently do not support IPv6.
-</warn>
-
-<p>
-A second important setting is the SYNC setting in <path>make.conf</path>. This
-variable contains the rsync server you want to use when updating your Portage
-tree (the collection of ebuilds, scripts containing all the information Portage
-needs to download and install software). Although you can manually enter a SYNC
-server for yourself, <c>mirrorselect</c> can ease that operation for you:
-</p>
-
-<pre caption="Selecting an rsync mirror using mirrorselect">
-# <i>mirrorselect -i -r -o &gt;&gt; /mnt/gentoo/etc/make.conf</i>
-</pre>
-
-<p>
-After running <c>mirrorselect</c> it is adviseable to double-check the settings
-in <path>/mnt/gentoo/etc/make.conf</path> !
-</p>
-
-</body>
-</subsection>-->
 <subsection>
 <title>Copy DNS Info</title>
 <body>
@@ -188,7 +147,7 @@
 
 <p>
 Thus, care needs to be taken to ensure the correct profile is selected for your
-system type.  As of Gentoo/MIPS 2006.1, the profiles are:
+system type.  As of Gentoo/MIPS 2007.0, the profiles are:
 </p>
 
 <table>
@@ -198,95 +157,90 @@
     <th>Userland</th>
     <th>Status/Notes</th>
   </tr>
-
   <tr>
     <ti>Cobalt Qube/RaQ</ti>
-    <ti>default-linux/mips/2006.1/cobalt/o32</ti>
+    <ti>default-linux/mips/2007.0/cobalt/o32</ti>
     <ti>32-bit Linuxthreads</ti>
     <ti>Recommended</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/cobalt/o32/nptl</ti>
+    <ti>default-linux/mips/2007.0/cobalt/o32/nptl</ti>
     <ti>32-bit NPTL</ti>
     <ti>In Testing (1)</ti>
   </tr>
-
   <tr>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
   </tr>
-
   <tr>
     <ti>
       Generic Big Endian<br />
       <e>Including SGI Indy, Indigo2 (R4x00), Challenge S and O2</e>
     </ti>
-    <ti>default-linux/mips/2006.1/generic-be/o32</ti>
+    <ti>default-linux/mips/2007.0/generic-be/o32</ti>
     <ti>32-bit Linuxthreads</ti>
     <ti>Recommended</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/generic-be/o32/nptl</ti>
+    <ti>default-linux/mips/2007.0/generic-be/o32/nptl</ti>
     <ti>32-bit NPTL</ti>
     <ti>In Testing (1)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/generic-be/n32</ti>
+    <ti>default-linux/mips/2007.0/generic-be/n32</ti>
     <ti>N32 Linuxthreads</ti>
     <ti>Highly Experimental (2)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/generic-be/n32/nptl</ti>
+    <ti>default-linux/mips/2007.0/generic-be/n32/nptl</ti>
     <ti>N32 NPTL</ti>
     <ti>Highly Experimental (1) (2)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/generic-be/n64</ti>
+    <ti>default-linux/mips/2007.0/generic-be/n64</ti>
     <ti>N64 Linuxthreads</ti>
     <ti>Unsupported (3)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/generic-be/n64/nptl</ti>
+    <ti>default-linux/mips/2007.0/generic-be/n64/nptl</ti>
     <ti>N64 NPTL</ti>
     <ti>Unsupported (1) (3)</ti>
   </tr>
-
   <tr>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
   </tr>
-
   <tr>
     <ti>SGI Origin 200/2000</ti>
-    <ti>default-linux/mips/2006.1/ip27/o32</ti>
+    <ti>default-linux/mips/2007.0/ip27/o32</ti>
     <ti>32-bit Linuxthreads</ti>
     <ti>Recommended</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip27/o32/nptl</ti>
+    <ti>default-linux/mips/2007.0/ip27/o32/nptl</ti>
     <ti>32-bit NPTL</ti>
     <ti>In Testing (1)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip27/n32</ti>
+    <ti>default-linux/mips/2007.0/ip27/n32</ti>
     <ti>N32 Linuxthreads</ti>
     <ti>Highly Experimental (2)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip27/n32/nptl</ti>
+    <ti>default-linux/mips/2007.0/ip27/n32/nptl</ti>
     <ti>N32 NPTL</ti>
     <ti>Highly Experimental (1) (2)</ti>
   </tr>
@@ -297,70 +251,67 @@
     <th>&nbsp;</th>
     <th>&nbsp;</th>
   </tr>
-
   <tr>
     <ti>SGI Indigo2 Impact R10000</ti>
-    <ti>default-linux/mips/2006.1/ip28/o32</ti>
+    <ti>default-linux/mips/2007.0/ip28/o32</ti>
     <ti>32-bit Linuxthreads</ti>
     <ti>Recommended</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip28/o32/nptl</ti>
+    <ti>default-linux/mips/2007.0/ip28/o32/nptl</ti>
     <ti>32-bit NPTL</ti>
     <ti>In Testing (1)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip28/n32</ti>
+    <ti>default-linux/mips/2007.0/ip28/n32</ti>
     <ti>N32 Linuxthreads</ti>
     <ti>Highly Experimental (2)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip28/n32/nptl</ti>
+    <ti>default-linux/mips/2007.0/ip28/n32/nptl</ti>
     <ti>N32 NPTL</ti>
     <ti>Highly Experimental (1) (2)</ti>
   </tr>
-
   <tr>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
     <th>&nbsp;</th>
   </tr>
-  
   <tr>
     <ti>SGI Octane/Octane2</ti>
-    <ti>default-linux/mips/2006.1/ip30/o32</ti>
+    <ti>default-linux/mips/2007.0/ip30/o32</ti>
     <ti>32-bit Linuxthreads</ti>
     <ti>Recommended</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip30/o32/nptl</ti>
+    <ti>default-linux/mips/2007.0/ip30/o32/nptl</ti>
     <ti>32-bit NPTL</ti>
     <ti>In Testing (1)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip30/n32</ti>
+    <ti>default-linux/mips/2007.0/ip30/n32</ti>
     <ti>N32 Linuxthreads</ti>
     <ti>Highly Experimental (2)</ti>
   </tr>
   <tr>
     <ti>"</ti>
-    <ti>default-linux/mips/2006.1/ip30/n32/nptl</ti>
+    <ti>default-linux/mips/2007.0/ip30/n32/nptl</ti>
     <ti>N32 NPTL</ti>
     <ti>Highly Experimental (1) (2)</ti>
   </tr>
 </table>
 
 <impo>
-(1) NPTL is in-testing on MIPS at this stage, requiring 
-<c>gcc-4.1</c> and <c>glibc-2.4</c>.  These profiles
-are a work-in-progress, and are not guaranteed to work.  It is recommended that
-people do not use these profiles until all the issues have been resolved.
+(1) NPTL is in-testing on MIPS at this stage, requiring <c>gcc-4.1</c> and
+<c>glibc-2.4</c>. It is believed that NPTL should be safe enough now for people
+to use, and is planned to be the default in future releases. Brave users are
+welcomed to try these profiles out and report back.
 </impo>
 
 <warn>
@@ -383,7 +334,7 @@
 
 <pre caption="Verifying system profile">
 # <i>ls -FGg /etc/make.profile</i>
-lrwxrwxrwx  1 48 Apr  8 18:51 /etc/make.profile -> ../usr/portage/profiles/default-linux/mips/2006.1/generic-be/o32/
+lrwxrwxrwx  1 48 Apr  8 18:51 /etc/make.profile -> ../usr/portage/profiles/default-linux/mips/2007.0/generic-be/o32/
 </pre>
 
 <p>
@@ -400,7 +351,7 @@
 
 <comment>(Create a new symlink pointing to your chosen profile     )
 (For example, this is what one would use on an Indy or O2.)</comment>
-# <i>ln -s /usr/portage/profiles/default-linux/mips/2006.1/generic-be/o32</i>
+# <i>ln -s /usr/portage/profiles/default-linux/mips/2007.0/generic-be/o32</i>
 </pre>
 
 <note>
@@ -516,11 +467,6 @@
 have specified in the <path>/etc/locale.gen</path> file.
 </p>
 
-<note>
-<c>locale-gen</c> is available in <c>glibc-2.3.6-r4</c> and newer. If you have
-an older version of glibc, you should update it now.
-</note>
-
 <p>
 Now continue with <uri link="?part=1&amp;chap=7">Configuring the Kernel</uri>.
 </p>



1.52                 xml/htdocs/doc/en/handbook/hb-install-network.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-network.xml?rev=1.52&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-network.xml?rev=1.52&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-network.xml?r1=1.51&r2=1.52

Index: hb-install-network.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-network.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- hb-install-network.xml	10 Nov 2006 11:09:42 -0000	1.51
+++ hb-install-network.xml	7 May 2007 18:11:41 -0000	1.52
@@ -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/hb-install-network.xml,v 1.51 2006/11/10 11:09:42 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-network.xml,v 1.52 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 networking.
 </abstract>
 
-<version>3.1</version>
-<date>2006-11-10</date>
+<version>4.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Automatic Network Detection</title>
@@ -136,8 +136,8 @@
     link="#net-setup">Default: Using net-setup</uri>
   </li>
   <li>
-    ADSL users should continue with <uri link="#rp-pppoe">Alternative:
-    Using RP-PPPoE</uri>
+    ADSL users should continue with <uri link="#ppp">Alternative:
+    Using PPP</uri>
   </li>
   <li>
     PPTP users should continue with <uri link="#pptp">Alternative:
@@ -177,20 +177,19 @@
 
 </body>
 </subsection>
-<subsection id="rp-pppoe">
-<title>Alternative: Using RP-PPPoE</title>
+<subsection id="ppp">
+<title>Alternative: Using PPP</title>
 <body>
 
 <p>
-Assuming you need PPPoE to connect to the internet, the Installation CD (any 
-version) has made things easy for you by including <c>rp-pppoe</c>. Use the 
-provided <c>pppoe-setup</c> script to configure your connection. You will be 
-prompted for the ethernet device that is connected to your adsl modem, your
-username and password, the IPs of your DNS servers and if you need a basic 
-firewall or not.
+Assuming you need PPPoE to connect to the internet, the Installation CD (any
+version) has made things easy for you by including <c>ppp</c>. Use the provided
+<c>pppoe-setup</c> script to configure your connection. You will be prompted for
+the ethernet device that is connected to your adsl modem, your username and
+password, the IPs of your DNS servers and if you need a basic firewall or not.
 </p>
 
-<pre caption="Using rp-pppoe">
+<pre caption="Using ppp">
 # <i>pppoe-setup</i>
 # <i>pppoe-start</i>
 </pre>
@@ -216,10 +215,6 @@
 <title>Alternative: Using PPTP</title>
 <body>
 
-<note>
-PPTP support is only available for x86
-</note>
-
 <p>
 If you need PPTP support, you can use <c>pptpclient</c> which is provided by our
 Installation CDs. But first you need to make sure that your configuration is 



1.26                 xml/htdocs/doc/en/handbook/hb-install-next.xml

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

Index: hb-install-next.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-next.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-install-next.xml	28 Oct 2006 09:17:54 -0000	1.25
+++ hb-install-next.xml	7 May 2007 18:11:41 -0000	1.26
@@ -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/hb-install-next.xml,v 1.25 2006/10/28 09:17:54 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-next.xml,v 1.26 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -12,8 +12,8 @@
 Now you have your Gentoo system, but what's next? 
 </abstract>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Documentation</title>
@@ -68,12 +68,12 @@
 
 <p>
 We also have several <uri 
-link="/main/en/lists.xml">mailinglists</uri> open to all 
+link="/main/en/lists.xml">mailing lists</uri> open to all 
 our users. Information on how to join is contained in that page.
 </p>
 
 <p>
-We'll shut up now and let you enjoy your installation :)
+We'll shut up now and let you enjoy your installation. :)
 </p>
 
 </body>



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

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

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.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- hb-install-ppc-bootloader.xml	13 Nov 2006 09:56:55 -0000	1.40
+++ hb-install-ppc-bootloader.xml	7 May 2007 18:11:41 -0000	1.41
@@ -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-bootloader.xml,v 1.40 2006/11/13 09:56:55 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.41 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2006-11-13</date>
+<version>8.0</version>
+<date>2007-05-07</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 the image and initrd
+## with the exact filename of your kernel and initrd image.
 ###########################################################</comment>
-image=/boot/kernel-name
+image=/boot/kenrel-genkernel-ppc-<keyval id="kernel-gentoo"/>
   label=Linux
   root=/dev/ram0
   partition=3
-  initrd=/boot/initrd-name
-  append="real_root=/dev/hda3 init=/linuxrc"  
+  initrd=/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/>
   <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,9 +115,9 @@
 <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">
@@ -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,11 +160,11 @@
 <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">
-# <i>emerge --usepkg yaboot</i>
+<pre caption="Installing yaboot">
+# <i>emerge yaboot</i>
 </pre>
 
 <p>
@@ -215,11 +217,12 @@
 install=/usr/lib/yaboot/yaboot
 magicboot=/usr/lib/yaboot/ofboot
 
-<comment>#################
-## This section can be duplicated if you have more than one kernel or set of
-## boot options - replace kernel-name with your kernel-version
-#################</comment>
-image=/boot/kernel-name
+<comment>############################################################
+## This section can be duplicated if you have more than one
+## kernel or set of boot options - replace the image variable
+## with the exact filename of your kernel.
+###########################################################</comment>
+image=/boot/<keyval id="kernel-name"/>
   label=Linux
   root=/dev/hda3
   partition=3
@@ -228,7 +231,7 @@
 <comment>##################
 
 ## G5 users and some G4 users should set 
-##   macos=hd:13
+##   macos=hd:13/
 ##   macosx=hd:12
 ## instead of the example values.</comment>
 macos=/dev/hda13
@@ -278,7 +281,7 @@
 # <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>
+cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels/<keyval id="kernel-name"/>"</i>
 </pre>
 
 <p>
@@ -290,8 +293,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-* "/mnt/mac/System Folder/Linux Kernels"</i>
-cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-* "/mnt/mac/System Folder"</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>
 </pre>
 
 <p>
@@ -359,19 +362,21 @@
 </pre>
 
 <p>
-Next, we'll need to set it up.  Edit /etc/quik.conf and set your image to the
-kernel that we copied to your boot partition.
+Next, we'll need to set it up. Edit <path>/etc/quik.conf</path> and set your
+image to the kernel that we copied to your boot partition.
 </p>
 
 <pre caption="Configuring quik.conf">
 # Example of quik.conf
-init-message = "Gentoo 2006.1\n"
-partition = 2		<comment># This is the boot partition</comment>
+init-message = "Gentoo 2007.0\n"
+<comment># This is the boot partition</comment>
+partition = 2
 root = /dev/hda4
 timeout = 30
 default = gentoo
-image = /vmlinux	<comment># This is your kernel</comment>
-	label = gentoo
+<comment># This is your kernel</comment>
+image = /<keyval id="kernel-name"/>
+  label = gentoo
 </pre>
 
 <p>
@@ -398,17 +403,18 @@
 # <i>nvsetenv input-device kbd</i>
 # <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment>
 # <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment>
-# <i>nvsetenv boot-file /boot/vmlinux-2.6.17 root=/dev/hda4</i> <comment>First item is the path to the kernel, the second is the root partition.  You may append any kernel options to the end of this line.</comment>
+# <i>nvsetenv boot-file /boot/<keyval id="kernel-name"/> root=/dev/hda4</i> <comment>First item is the path to the kernel, the second is the root partition.  You may append any kernel options to the end of this line.</comment>
 # <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment>
 </pre>
 
 <note>
-It is also possible to change your boot variables from MacOS.  Depending
-upon the model, either 
-<uri link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or 
-<uri link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin">
-Apple System Disk</uri> should be used.  Please see the quik quirks page
-above for more information.
+It is also possible to change your boot variables from MacOS.  Depending upon
+the model, either <uri
+link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or
+<uri
+link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin">
+Apple System Disk</uri> should be used.  Please see the quik quirks page above
+for more information.
 </note>
 
 <p>
@@ -445,7 +451,7 @@
 </p>
 
 <pre caption = "Installing bootcreator">
-# <i>emerge --usepkg bootcreator</i>
+# <i>emerge bootcreator</i>
 </pre>
 
 <p>
@@ -459,8 +465,8 @@
 </pre>
 
 <p>
-Below is a complete <path>/etc/bootmenu</path> config file.  The kernel-name
-and initrd-name should be replaced by your kernel and initrd image names.
+Below is a complete <path>/etc/bootmenu</path> config file. vmlinux and
+initrd should be replaced by your kernel and initrd image names.
 </p>
 
 <pre caption = "bootcreator config file">
@@ -485,15 +491,15 @@
 
 [SECTION]
 Local HD -> Linux (Normal)
-ide:0 kernel-name video=radeonfb:1024x768@70 root=/dev/hda3
+ide:0 <keyval id="kernel-name"/> video=radeonfb:1024x768@70 root=/dev/hda3
 
 [SECTION]
 Local HD -> Genkernel (Normal)
-ide:0 kernel-name root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc initrd=initrd-name
+ide:0 kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc initrd=initramfs-genkernel-ppc<keyval id="kernel-gentoo"/>
 </pre>
 
 <p>
-Finally the <path>bootmenu</path> must be transfered into Forth and copied to
+Finally the <path>bootmenu</path> must be transferred into Forth and copied to
 your boot partition, so that the SmartFirmware can read it.  Therefore you have
 to call <c>bootcreator</c>:
 </p>



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

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

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.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-ppc-disk.xml	2 Nov 2006 20:49:38 -0000	1.37
+++ hb-install-ppc-disk.xml	7 May 2007 18:11:41 -0000	1.38
@@ -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.37 2006/11/02 20:49:38 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.38 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2006-11-02</date>
+<version>8.0</version>
+<date>2007-05-07</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>
@@ -436,15 +593,15 @@
 </tr>
 <tr>
   <ti>ext2</ti>
-  <ti><c>mkfs.ext2</c></ti>
+  <ti><c>mke2fs</c></ti>
 </tr>
 <tr>
   <ti>ext3</ti>
-  <ti><c>mkfs.ext3</c></ti>
+  <ti><c>mke2fs -j</c></ti>
 </tr>
 <tr>
   <ti>reiserfs</ti>
-  <ti><c>mkfs.reiserfs</c></ti>
+  <ti><c>mkreiserfs</c></ti>
 </tr>
 <tr>
   <ti>xfs</ti>
@@ -453,12 +610,12 @@
 </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">
-# <i>mkfs.ext3 /dev/hda4</i>
+# <i>mke2fs -j /dev/hda4</i>
 </pre>
 
 <p>
@@ -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,32 +633,6 @@
 
 </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>
@@ -519,17 +650,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.48                 xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml

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

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.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- hb-install-ppc-kernel.xml	13 Mar 2007 00:30:09 -0000	1.47
+++ hb-install-ppc-kernel.xml	7 May 2007 18:11: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-kernel.xml,v 1.47 2007/03/13 00:30:09 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.48 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.5</version>
-<date>2007-02-12</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,13 +26,14 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
 </section>
 <section>
-<title>Installing the Sources</title>
+<title>Installing the Kernel Sources</title>
 <subsection>
 <title>Choosing a Kernel</title>
 <body>
@@ -40,13 +41,13 @@
 <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">
@@ -56,20 +57,20 @@
 <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.
+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-2.6.15
+lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -&gt; linux-<keyval id="kernel-gentoo"/>
 </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 +92,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 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>
 
@@ -157,6 +158,7 @@
 <pre caption="Selecting necessary file systems">
 File systems ---&gt;
   Pseudo Filesystems ---&gt;
+<comment>(/proc may already be forced on by your configuration, if so, you'll see --- instead)</comment>
     [*] /proc file system support
     [*] Virtual memory file system support (former shm fs)
   Partition Types ---&gt;
@@ -171,49 +173,67 @@
 </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;
+  Miscellaneous filesystems ---&gt;
+    &lt;*&gt; Apple Macintosh file system support
+    &lt;*&gt; Apple Extended HFS file system 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>
 
 <pre caption="Selecting PPPoE necessary drivers">
 Device Drivers ---&gt;
-  Networking support ---&gt;
+  Network device support ---&gt;
     &lt;*&gt; PPP (point-to-point protocol) support
     &lt;*&gt;   PPP support for async serial ports
     &lt;*&gt;   PPP support for sync tty ports
 </pre>
 
 <p>
-The two compression options won't harm but are not definitely needed, neither
-does the <c>PPP over Ethernet</c> option, that might only be used by 
-<c>rp-pppoe</c> when configured to do kernel mode PPPoE.
+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>ppp</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.
-</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:
+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>
 
-<pre caption="Activating HFS support">
-File Systems ---&gt;
-  [*] HFS Support
+<pre caption="Selecting the network driver">
+Device Drivers ---&gt;
+  Network device support ---&gt;
+    Ethernet (10 or 100Mbit) ---&gt;
+      [*] Ethernet (10 or 100Mbit)
+      &lt;*&gt;   Generic Media Independent Interface device support
+      &lt;*&gt;   MACE (Power Mac ethernet) support
+      &lt;*&gt;   BMAC (G3 ethernet) support
+      &lt;*&gt; Sun GEM support
 </pre>
 
 <p>
-At this time, kernel preemption is still unstable on PPC and may cause 
+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.
+that you do not use this featurea.  Both <e>Voluntary Preemption</e> and 
+<e>No Forced Preemption</e> should be safe.
 </p>
 
 <pre caption="Ensure the Preemptible Kernel Option is Off">
 Kernel options ---&gt;
-  Preemption Model (No Forced Preemption (Server))
+<comment>(Select One)</comment>
+  Preemption Model 
+    (X) No Forced Preemption (Server)
+    (X) Voluntary Kernel Preemption (Desktop)
 </pre>
 
 <p>
@@ -251,7 +271,7 @@
 framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon).
 </p>
 
-<pre caption="Chosing a Framebuffer Driver">
+<pre caption="Choosing a Framebuffer Driver">
 Device Drivers ---&gt;
   Graphics support ---&gt;
     &lt;*&gt; Support for frame buffer devices
@@ -266,8 +286,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 +303,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,26 +312,27 @@
 
 <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 separate 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>
-Yaboot and BootX expect to use an uncompressed kernel unlike many other 
-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>.
+Yaboot and BootX expect to use an uncompressed kernel unlike many other
+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 which can be found in
+<path>/usr/src/linux/arch/powerpc/boot/images</path>.
 </p>
 
 <pre caption="Installing the kernel">
 # <i>cd /usr/src/linux</i>
-<comment>replace &lt;kernel-version&gt; with your kernel version</comment>
+<comment>Note, your kernel version might be different</comment>
 <comment>(Apple/IBM)</comment>
-# <i>cp vmlinux /boot/&lt;kernel-version&gt;</i> 
+# <i>cp vmlinux /boot/<keyval id="kernel-name"/></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>
@@ -329,9 +350,9 @@
 <body>
 
 <p>
-You should list the modules you want automatically loaded in 
-<path>/etc/modules.autoload.d/kernel-2.6</path>. 
-You can add extra options to the modules too if you want.
+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 if required.
 </p>
 
 <p>
@@ -345,9 +366,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,19 +391,15 @@
 <body>
 
 <p>
-If you are reading this section, you have chosen to use our <c>genkernel</c>
-script to configure your kernel for you.
-</p>
-
-<p>
-Now that your kernel source tree is installed, it's now time to compile your 
-kernel by using our <c>genkernel</c> script to automatically build a kernel for 
-you. <c>genkernel</c> works by configuring a kernel nearly identically to the 
-way our Installation CD kernel is configured. This means that when you use 
-<c>genkernel</c> to build your kernel, your system will generally detect all 
-your hardware at boot-time, just like our Installation CD does. Because 
-genkernel doesn't require any manual kernel configuration, it is an ideal 
-solution for those users who may not be comfortable compiling their own kernels.
+Now that your kernel source tree is installed, it's now time to compile your
+kernel by using our <c>genkernel</c> script to automatically build a kernel for
+you. <c>genkernel</c> works by configuring a kernel nearly identically to the
+way our Installation CD kernel is configured. This means that when you use
+<c>genkernel</c> to build your kernel, your system will generally detect all
+your hardware at boot-time, just like our Installation CD does. Because
+genkernel doesn't require any manual kernel configuration, it is an ideal
+solution for those users who may not be comfortable compiling their own
+kernels.
 </p>
 
 <p>
@@ -412,10 +428,10 @@
 
 <p>
 Before compiling your sources, the fstab needs a slight adjustment. The rest of
-the fstab will be completed during a later step, so don't worry about the 
+the fstab will be completed during a later step, so don't worry about the
 details now. If you did not create a separate boot partition (NOT bootstrap,
-that's different), remove the line referencing /boot from 
-<path>/etc/fstab</path>.  This will need to be done on most Apple computers.
+that's different), remove the line referencing <path>/boot</path> from
+<path>/etc/fstab</path>. This will need to be done on most Apple computers.
 </p>
 
 <pre caption="Removing /boot from /etc/fstab on machines without a boot partition">
@@ -437,7 +453,7 @@
 or ext3 as filesystem you might need to manually configure your kernel using
 <c>genkernel --menuconfig all</c> and add support for your 
 filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or
-LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as argument as 
+LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as
 well.
 </p>
 
@@ -453,7 +469,7 @@
 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
@@ -461,17 +477,8 @@
 </p>
 
 <pre caption="Checking the created kernel image name and initrd">
-# <i>ls /boot/kernel* /boot/initramfs*</i>
-</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>
+<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>
 </pre>
 
 <p>
@@ -480,6 +487,5 @@
 
 </body>
 </section>
-
 </sections>
 



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

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

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.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- hb-install-ppc-medium.xml	30 Aug 2006 22:52:28 -0000	1.54
+++ hb-install-ppc-medium.xml	7 May 2007 18:11:41 -0000	1.55
@@ -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.54 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.55 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -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>
@@ -155,12 +155,11 @@
 <body>
 
 <p>
-You can download the Universal Installation CD (and, if you want to, the 
-Packages CD as well) from one of our <uri 
-link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located 
-in the <path>releases/ppc/2006.1/ppc32/installcd</path> directory;
-the Package CDs are located in the 
-<path>releases/ppc/2006.1/ppc32/packagecd</path> directory.
+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.
 </p>
 
 <p>
@@ -470,8 +469,10 @@
 </p>
 
 <pre caption="Tweaking hard disk performance">
-<comment>Activate DMA:</comment>                                       # <i>hdparm -d 1 /dev/hda</i>
-<comment>Activate DMA + Safe Performance-enhancing Options:</comment>  # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
+<comment>Activate DMA:</comment>
+# <i>hdparm -d 1 /dev/hda</i>
+<comment>Activate DMA + Safe Performance-enhancing Options:</comment>
+# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
 </pre>
 
 </body>
@@ -551,7 +552,7 @@
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
 </pre>
 
 <p>



1.26                 xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml

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

Index: hb-install-ppc64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-install-ppc64-bootloader.xml	30 Aug 2006 22:52:28 -0000	1.25
+++ hb-install-ppc64-bootloader.xml	7 May 2007 18:11:41 -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/hb-install-ppc64-bootloader.xml,v 1.25 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml,v 1.26 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Making your Choice</title>
@@ -45,13 +45,12 @@
 </impo>
 
 <p>
-There are two ways to configure yaBoot for your system. You can use the
-new and improved <c>yabootconfig</c> included with
-<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If
-for some reason you do not want to run <c>yabootconfig</c> to
-automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo
-on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit 
-the sample file already installed on your system.
+There are two ways to configure yaBoot for your system. You can use the new and
+improved <c>yabootconfig</c> included with <path>yaboot-1.3.8-r1</path> and
+later to automatically set up yaboot. If for some reason you do not want to run
+<c>yabootconfig</c> to automatically set up <path>/etc/yaboot.conf</path> or you
+are installing Gentoo on a G5 (on which <c>yabootconfig</c> does not always
+work), you can just edit the sample file already installed on your system.
 </p>
 
 <impo>
@@ -102,19 +101,19 @@
 </pre>
 
 <p>
-Now run <c>yabootconfig</c>. The program will run and it will confirm
-the location of the bootstrap partition. Type <c>Y</c> if it is correct. If
-not, double check <path>/etc/fstab</path>. yabootconfig will then scan your
-system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for
-you. <c>mkofboot</c> is used to format the bootstrap partition, and install 
-the yaboot configuration file into it.
+Now run <c>yabootconfig</c>. The program will run and it will confirm the
+location of the bootstrap partition. Type <c>Y</c> if it is correct. If not,
+double check <path>/etc/fstab</path>. yabootconfig will then scan your system
+setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you.
+<c>mkofboot</c> is used to format the bootstrap partition, and install the
+yaboot configuration file into it.
 </p>
 
 <p>
-You might want to verify the contents of <path>/etc/yaboot.conf</path>. If 
-you make changes to <path>/etc/yaboot.conf</path> (like setting the 
-default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the 
-bootstrap partition.
+You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you
+make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot
+OS), make sure to rerun <c>ybin -v</c> to apply changes to the bootstrap
+partition.
 </p>
 
 <p>
@@ -176,9 +175,9 @@
 
 <comment>#################
 ## This section can be duplicated if you have more than one kernel or set of
-## boot options - replace 2.6.17-gentoo-r5 with your kernel-version
+## boot options - replace <keyval id="kernel-name"/> with your kernel-version
 #################</comment>
-image=/boot/kernel-2.6.17-gentoo-r5
+image=/boot/<keyval id="kernel-name"/>
   label=Linux
   root=/dev/hda3
   partition=3
@@ -191,25 +190,22 @@
 </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.
+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.
+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.
 </p>
 
 <p>
 For more information on yaboot, take a look at the <uri
-link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For
-now, continue the installation with <uri link="#reboot">Rebooting your 
-System</uri>.
+link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For now,
+continue the installation with <uri link="#reboot">Rebooting your System</uri>.
 </p>
 
 </body>
@@ -226,16 +222,22 @@
 
 <ul>
   <li>Install yaboot-static</li>
-  <li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX
-  with your disk and partition for the PReP partition; this was in our
-  example /dev/sda1)</li>
-  <li>Next construct your own yaboot.conf file and place into /etc.
-  (Take a look at the config above, look into the man page of
-  yaboot.conf or look at the below yaboot.conf example)</li>
-  <li>Assuming your boot device in OF is pointing to the harddrive you
-  prep boot partition is on then it'll just work, otherwise at IPL time,
-  go into the multiboot menu and set the boot device to the one with
-  your prep boot partition.</li>
+  <li>
+    Run <c>dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX</c> (fill in XX with
+    your disk and partition for the PReP partition; this was in our example
+    <path>/dev/sda1</path>)
+  </li>
+  <li>
+    Next construct your own <path>yaboot.conf</path> file and place into
+    <path>/etc</path>. (Take a look at the config above, look into the man page
+    of yaboot.conf or look at the below <path>yaboot.conf</path> example.)
+  </li>
+  <li>
+    Assuming your boot device in OF is pointing to the harddrive you prep boot
+    partition is on then it'll just work, otherwise at IPL time, go into the
+    multiboot menu and set the boot device to the one with your prep boot
+    partition
+  </li>
   <li>That's it!</li>
 </ul>
 
@@ -246,22 +248,23 @@
 default=linux
 timeout=50
 
-image=/boot/kernel-2.6.17-gentoo-r5
+image=/boot/<keyval id="kernel-name"/>
     label=linux
     append="console=ttyS0,9600"
     read-only
 </pre>
 
 <p>
-For POWER4, POWER5, and blade-based hardware where the PReP disk partition 
-and the disk partition that contains your kernel are on the same physical disk,
-you can use a simplified yaboot.conf.  The following should be sufficient:
+For POWER4, POWER5, and blade-based hardware where the PReP disk partition and
+the disk partition that contains your kernel are on the same physical disk, you
+can use a simplified <path>yaboot.conf</path>. The following should be
+sufficient:
 </p>
 
 <pre caption="yaboot.conf for PReP hardware">
 default = linux
 timeout = 100
-image=/boot/kernel-2.6.17-gentoo-r5
+image=/boot/<keyval id="kernel-name"/>
         label=linux
         read-only
         root = /dev/sda2



1.29                 xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml

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

Index: hb-install-ppc64-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- hb-install-ppc64-disk.xml	16 Feb 2007 13:45:39 -0000	1.28
+++ hb-install-ppc64-disk.xml	7 May 2007 18:11:41 -0000	1.29
@@ -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-ppc64-disk.xml,v 1.28 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml,v 1.29 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2007-02-16</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -104,11 +104,10 @@
 
 <note>
 There are some partitions named like this: <path>Apple_Driver43,
-Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit,
-Apple_Patches</path>. If you are not planning to use MacOS 9 you can
-delete them, because MacOS X and Linux don't need them.
-You might have to use parted in order to delete them, as mac-fdisk can't delete
-them yet.
+Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If
+you are not planning to use MacOS 9 you can delete them, because MacOS X and
+Linux don't need them.  You might have to use parted in order to delete them, as
+mac-fdisk can't delete them yet.
 </note>
 
 <p>
@@ -129,14 +128,14 @@
 The number of partitions is highly dependent on your environment. For instance,
 if you have lots of users, you will most likely want to have your
 <path>/home</path> separate as it increases security and makes backups easier.
-If you are installing Gentoo to perform as a mailserver, your 
-<path>/var</path> should be separate as all mails are stored inside 
-<path>/var</path>. A good choice of filesystem will then maximise your 
-performance. Gameservers will have a separate <path>/opt</path> as most gaming 
-servers are installed there. The reason is similar for <path>/home</path>: 
-security and backups. You will definitely want to keep <path>/usr</path> big:
-not only will it contain the majority of applications, the Portage tree alone
-takes around 500 Mbyte excluding the various sources that are stored in it.
+If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
+should be separate as all mails are stored inside <path>/var</path>. A good
+choice of filesystem will then maximise your performance. Gameservers will have
+a separate <path>/opt</path> as most gaming servers are installed there. The
+reason is similar for <path>/home</path>: security and backups. You will
+definitely want to keep <path>/usr</path> big: not only will it contain the
+majority of applications, the Portage tree alone takes around 500 Mbyte
+excluding the various sources that are stored in it.
 </p>
 
 <p>
@@ -164,17 +163,17 @@
 </ul>
 
 <p>
-However, multiple partitions have one big disadvantage: if not configured 
-properly, you might result in having a system with lots
-of free space on one partition and none on another. There is also a 15-partition
-limit for SCSI and SATA.
+However, multiple partitions have one big disadvantage: if not configured
+properly, you might result in having a system with lots of free space on one
+partition and none on another. There is also a 15-partition limit for SCSI and
+SATA.
 </p>
 
 </body>
 </subsection>
 </section>
 <section id="mac-fdisk">
-<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title>
+<title>Default: Using mac-fdisk (Apple G5) to Partition your Disk</title>
 <body>
 
 <p>
@@ -225,10 +224,10 @@
 
 <note>
 To make sure everything is ok, you should run mac-fdisk once more and check
-whether all the partitions are there.If you don't see any of the partitions you
+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. 
+pressing <c>i</c> in mac-fdisk. Note that this will recreate the partition map
+and thus remove all your partitions. 
 </note>
     
 <p>
@@ -244,14 +243,14 @@
 <body>
 
 <note>
-If you are planning to use a RAID disk array for your gentoo installation and 
+If you are planning to use a RAID disk array for your Gentoo installation and 
 you are using POWER5-based hardware, you should now run <c>iprconfig</c> to 
 format the disks to Advanced Function format and create the disk array. You
 should emerge <c>iprutils</c> after your install is complete.
 </note>
 
 <p>
-If you have an ipr based SCSI adapter, you should start the ipr utilities now.
+If you have an ipr-based SCSI adapter, you should start the ipr utilities now.
 </p>
 
 <pre caption="Starting ipr utilities">
@@ -647,8 +646,7 @@
 
 <p>
 <b>JFS</b> is IBM's high-performance journaling filesystem. It has recently 
-become production-ready and there hasn't been a sufficient track record to 
-comment positively nor negatively on its general stability at this point.
+become production-ready.
 </p>
 
 </body>
@@ -695,7 +693,7 @@
 </p>
 
 <pre caption="Applying a filesystem on a partition">
-# <i>mke2fs -j -O dir_index /dev/sda4</i>
+# <i>mke2fs -j /dev/sda4</i>
 </pre>
 
 <p>
@@ -740,7 +738,7 @@
 Now that your partitions are initialized and are housing a filesystem, it is
 time to mount those partitions. Use the <c>mount</c> command. Don't forget to
 create the necessary mount directories for every partition you created. As an
-example we create a mount-point and mount the root and boot partition:
+example we create a mount point and mount the root partition:
 </p>
 
 <pre caption="Mounting partitions">



1.27                 xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml

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

Index: hb-install-ppc64-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- hb-install-ppc64-kernel.xml	26 Feb 2007 08:54:53 -0000	1.26
+++ hb-install-ppc64-kernel.xml	7 May 2007 18:11:41 -0000	1.27
@@ -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-ppc64-kernel.xml,v 1.26 2007/02/26 08:54:53 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v 1.27 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.1</version>
-<date>2007-02-26</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,7 +26,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -56,13 +57,13 @@
 <p>
 When you take a look in <path>/usr/src</path> you should see a symlink called
 <path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>gentoo-sources-2.6.17-r5</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
+Your version may be different, so keep this in mind.
 </p>
 
 <pre caption="Viewing the kernel source symlink">
 # <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx   1 root   root      12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.17-gentoo-r5
+lrwxrwxrwx   1 root   root      12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
 </pre>
 
 <p>
@@ -106,8 +107,8 @@
 <pre caption="Invoking menuconfig">
 # <i>cd /usr/src/linux</i>
 <comment>Important: In case you are in 32-bit userland, you must edit the top
-level Makefile in /usr/src/linux and change the CROSS_COMPILE option to 
-CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run 
+level Makefile in /usr/src/linux and change the CROSS_COMPILE option to
+CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run
 make menuconfig or it may result in kernel compilation problems.</comment>
 # <i>make menuconfig</i>
 </pre>
@@ -177,8 +178,8 @@
 
 <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.
+does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
+when configured to do kernel mode PPPoE.
 </p>
 
 <p>



1.33                 xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml

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

Index: hb-install-ppc64-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- hb-install-ppc64-medium.xml	30 Aug 2006 22:52:28 -0000	1.32
+++ hb-install-ppc64-medium.xml	7 May 2007 18:11:41 -0000	1.33
@@ -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-ppc64-medium.xml,v 1.32 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v 1.33 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -87,8 +87,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2006.1/index.xml">Gentoo 2006.1 Handbooks</uri>. This is currently not
-supported for the PPC64 architecture though.
+link="2007.0/index.xml">Gentoo 2007.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -121,7 +120,7 @@
 
 <p>
 The Minimal Installation CD is called 
-<c>install-ppc64-minimal-2006.1.iso</c> and takes up only 124 MB of 
+<c>install-ppc64-minimal-2007.0.iso</c> and takes up only 124 MB of 
 diskspace. You can use this Installation CD to install Gentoo, but always with a
 working Internet connection only.
 </p>
@@ -152,7 +151,7 @@
 
 <p>
 The Universal Installation CD is called
-<c>install-ppc64-universal-2006.1.iso</c> and uses 460 MB. You can use
+<c>install-ppc64-universal-2007.0.iso</c> and uses 460 MB. You can use
 this Installation CD to install Gentoo, and you can even use it to install
 Gentoo without a working internet connection, just in case you want to bring
 Gentoo to another PC than the one you are currently installing Gentoo on :)
@@ -195,6 +194,51 @@
 
 </body>
 </subsection>
+<subsection>
+<title>Choosing a userland</title>
+<body>
+
+<p>
+On PPC64, the kernel is 64-bit and the <e>userland</e> can be 32-bit or 64-bit. The
+userland is basically the applications you are running, such as
+<c>bash</c> or <c>mozilla-firefox</c>. They can be compiled and run in either
+64-bit or 32-bit modes. The Gentoo/PPC64 team provides both 32-bit and 64-bit
+userlands, so which one should you use?
+</p>
+
+<p>
+You may have heard that 64-bit applications are better, but in fact, 32-bit
+applications take up slightly less memory and often run a little bit faster than
+64-bit applications.
+</p>
+
+<p>
+You really only need 64-bit applications when you need more memory than a 32-bit
+userland allows, or if you do a lot of 64-bit number crunching. If you run
+applications that require more than 4GB of memory or you run scientific
+applications, you should choose the 64-bit userland. Otherwise, choose the
+32-bit userland, as it is recommended by the Gentoo/PPC64 developers.
+</p>
+
+<p>
+Additionally, the 32-bit userland has been available in Portage longer than the
+64-bit userland has. This means that there are more applications tested in the
+32-bit userland that just work "out of the box." Many applications compiled for
+the 64-bit userland may be just as stable as the 32-bit version, but they
+haven't been tested yet. Though testing isn't difficult to do, it can be
+annoying and time consuming if you want to use many untested 64-bit
+applications. Also, some programs just won't run in the 64-bit userland until
+their code is fixed, such as OpenOffice.
+</p>
+
+<p>
+The Gentoo/PPC64 team provides stages and Package CDs for both 32-bit and 64-bit
+userlands, so no matter which one you choose, you'll be able to successfully
+install Gentoo and get a full system up and running with minimal fuss.
+</p>
+
+</body>
+</subsection>
 </section>
 <!-- STOP -->
 <section>
@@ -210,10 +254,10 @@
 </p>
 
 <p>
-You can download any of the Installation CDs (and, if you want to, a Packages
-CD as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The
-Installation CDs are located in the
-<path>releases/ppc/2006.1/ppc64/installcd</path> directory.
+You can download any of the Installation CDs (and, if you want to, a 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.
 </p>
 
 <p>
@@ -224,7 +268,7 @@
 <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>install-ppc64-minimal-2006.1.iso.DIGESTS</path>). You can check the MD5 
+<path>install-ppc64-minimal-2007.0.iso.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>
@@ -306,15 +350,15 @@
     This option takes one of the following vendor-specific tags:
     <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>, <c>nvidiafb</c>
     or <c>ofonly</c>. You can follow this tag with the resolution and
-    refreshrate you want to use. For instance <c>video=radeonfb:1280x1024@75</c>
-    . If you are uncertain what to choose, <c>ofonly</c> will most certainly
-    work.
+    refreshrate you want to use. For instance
+    <c>video=radeonfb:1280x1024@75</c>. If you are uncertain what to choose,
+    <c>ofonly</c> will most certainly work.
   </ti>
 </tr>
 <tr>
   <ti><c>nol3</c></ti>
   <ti>
-    Disables level 3 cache on some powerbooks (needed for at least the 17'')
+    Disables level 3 cache on some powerbooks (needed for at least the 17")
   </ti>
 </tr>
 <tr>
@@ -433,11 +477,11 @@
 
 <p>
 When the Installation CD boots, it tries to detect all your hardware devices and
-loads the appropriate kernel modules to support your hardware. In the
-vast majority of cases, it does a very good job. However, in some cases it may 
-not auto-load the kernel 
-modules you need. If the PCI auto-detection missed some of your system's 
-hardware, you will have to load the appropriate kernel modules manually. 
+loads the appropriate kernel modules to support your hardware. In the vast
+majority of cases, it does a very good job. However, in some cases it may not
+auto-load the kernel modules you need. If the PCI auto-detection missed some of
+your system's hardware, you will have to load the appropriate kernel modules
+manually. 
 </p>
 
 <p>
@@ -473,8 +517,10 @@
 </p>
 
 <pre caption="Tweaking hard disk performance">
-<comment>Activate DMA:</comment>                                       # <i>hdparm -d 1 /dev/hda</i>
-<comment>Activate DMA + Safe Performance-enhancing Options:</comment>  # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
+<comment>Activate DMA:</comment>
+# <i>hdparm -d 1 /dev/hda</i>
+<comment>Activate DMA + Safe Performance-enhancing Options:</comment>
+# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
 </pre>
 
 </body>
@@ -549,7 +595,7 @@
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
 </pre>
 
 <p>



1.20                 xml/htdocs/doc/en/handbook/hb-install-sparc-bootloader.xml

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

Index: hb-install-sparc-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-bootloader.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-install-sparc-bootloader.xml	28 Oct 2006 11:00:55 -0000	1.19
+++ hb-install-sparc-bootloader.xml	7 May 2007 18:11:41 -0000	1.20
@@ -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-sparc-bootloader.xml,v 1.19 2006/10/28 11:00:55 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-bootloader.xml,v 1.20 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>2.4</version>
-<date>2006-10-28</date>
+<version>3.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Making your Choice</title>
@@ -53,7 +53,7 @@
 <p>
 Below you'll find an example <path>silo.conf</path> file. It uses the
 partitioning scheme we use throughout this book and
-<path>kernel-2.4.31</path> as kernelimage.
+<path>kernel-<keyval id="kernel-version"/></path> as kernelimage.
 </p>
 
 <pre caption = "Example /etc/silo.conf">
@@ -61,7 +61,7 @@
 root = /dev/sda1      <comment># Root partition</comment>
 timeout = 150         <comment># Wait 15 seconds before booting the default section</comment>
 
-image = /boot/kernel-2.4.31
+image = /boot/kernel-<keyval id="kernel-version"/>
   label = linux
 </pre>
 
@@ -93,6 +93,11 @@
 /etc/silo.conf appears to be valid
 </pre>
 
+<note>
+You have to run <c>silo</c> (with parameters) again each time you update or
+reinstall the <c>sys-boot/silo</c> package.
+</note>
+
 <p>
 Now continue with <uri link="#reboot">Rebooting the System</uri>.
 </p>



1.29                 xml/htdocs/doc/en/handbook/hb-install-sparc-disk.xml

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

Index: hb-install-sparc-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-disk.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- hb-install-sparc-disk.xml	16 Feb 2007 13:45:39 -0000	1.28
+++ hb-install-sparc-disk.xml	7 May 2007 18:11:41 -0000	1.29
@@ -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-sparc-disk.xml,v 1.28 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-disk.xml,v 1.29 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>3.2</version>
-<date>2007-02-16</date>
+<version>4.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -112,9 +112,9 @@
     <ti>&lt;2 GByte</ti>
     <ti>/</ti>
     <ti>
-      Root partition. For sun4c, sun4d and sun4m systems, some PROMs require 
-      this partition to be less than 1 GBytes in size and the first
-      partition on the disk.
+      Root partition. For sparc64 systems with older OBP versions, this
+      <e>must</e> be less than 2 GBytes in size, and the first partition on the
+      disk.
     </ti>
 </tr>
 <tr>
@@ -553,9 +553,9 @@
 
 <pre caption="Applying a filesystem on a partition">
 # <i>mke2fs /dev/sda1</i>
-# <i>mke2fs -j -O dir_index /dev/sda4</i>
-# <i>mke2fs -j -O dir_index /dev/sda5</i>
-# <i>mke2fs -j -O dir_index /dev/sda6</i>
+# <i>mke2fs -j /dev/sda4</i>
+# <i>mke2fs -j /dev/sda5</i>
+# <i>mke2fs -j /dev/sda6</i>
 </pre>
 
 </body>



1.26                 xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml

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

Index: hb-install-sparc-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-install-sparc-kernel.xml	7 Mar 2007 01:00:20 -0000	1.25
+++ hb-install-sparc-kernel.xml	7 May 2007 18:11:41 -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/hb-install-sparc-kernel.xml,v 1.25 2007/03/07 01:00:20 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-kernel.xml,v 1.26 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.2</version>
-<date>2007-03-06</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -17,8 +17,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -26,7 +26,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -46,14 +47,12 @@
 </p>
 
 <p>
-For sparc-based systems we have <c>sparc-sources</c> (2.4 kernel sources
-optimized for SPARC users) and <c>gentoo-sources</c> (recommended 2.6 kernel
+For sparc-based systems we have <c>gentoo-sources</c> (recommended 2.6 kernel
 sources).
 </p>
 
 <p>
-In the next example we install the <c>gentoo-sources</c>. Of course substitute
-with your choice of sources, this is merely an example.
+In the next example we install <c>gentoo-sources</c>.
 </p>
 
 <pre caption="Installing a kernel source">
@@ -63,13 +62,13 @@
 <p>
 When you take a look in <path>/usr/src</path> you should see a symlink called
 <path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>linux-2.6.17-gentoo-r5</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>linux-<keyval id="kernel-version"/></c>. Your version
+may be different, so keep this in mind.
 </p>
 
 <pre caption="Viewing the kernel source symlink">
 # <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx    1 root     root       12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.17-gentoo-r5
+lrwxrwxrwx    1 root     root       12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
 </pre>
 
 <p>
@@ -139,31 +138,18 @@
 Now go to <c>File Systems</c> and select support for the filesystems you use.
 <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
 able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
-file system</c>. If you are running a 2.4 kernel, you should also select
-<c>/dev file system</c> + <c>Automatically mount at boot</c>:
+file system</c>:
 </p>
 
 <pre caption="Selecting necessary file systems">
-<comment>(With a 2.4.x kernel)</comment>
-File systems ---&gt;
-  [*] Virtual memory file system support (former shm fs)
-  [*] /proc file system support
-  [*] /dev file system support (EXPERIMENTAL)
-  [*]   Automatically mount at boot
-  [ ] /dev/pts file system for Unix98 PTYs
-
-<comment>(With a 2.6.x kernel)</comment>
 File systems ---&gt;
   Pseudo Filesystems ---&gt;
     [*] /proc file system support
     [*] Virtual memory file system support (former shm fs)
 
 <comment>(Select one or more of the following options as needed by your system)</comment>
-  &lt; &gt; Reiserfs support
   &lt;*&gt; Ext3 journalling file system support
-  &lt; &gt; JFS filesystem support
   &lt;*&gt; Second extended fs support
-  &lt; &gt; XFS filesystem support
 </pre>
 
 <p>
@@ -172,13 +158,6 @@
 </p>
 
 <pre caption="Selecting PPPoE necessary drivers">
-<comment>(With a 2.4.x kernel)</comment>
-Network device support ---&gt;
-  &lt;*&gt; PPP (point-to-point protocol) support
-  &lt;*&gt;   PPP support for async serial ports
-  &lt;*&gt;   PPP support for sync tty ports
-
-<comment>(With a 2.6.x kernel)</comment>
 Device Drivers ---&gt;
   Networking support ---&gt;
     &lt;*&gt; PPP (point-to-point protocol) support
@@ -188,13 +167,8 @@
 
 <p>
 The two compression options won't harm but are not definitely needed, neither
-does the <c>PPP over Ethernet</c> option, that might only be used by 
-<c>rp-pppoe</c> when configured to do kernel mode PPPoE.
-</p>
-
-<p>
-If you require it, don't forget to include support in the kernel for your
-ethernet card.
+does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
+when configured to do kernel mode PPPoE.
 </p>
 
 <p>
@@ -262,16 +236,12 @@
 </pre>
 
 <p>
-If the (uncompressed) size is bigger than 2.5 MB (for Sparc32) or 3.5 MB (for 
-Sparc64), reconfigure your kernel until it doesn't exceed these limits. One way
-of accomplishing this is by having most kernel drivers compiled as modules.
-Ignoring this can lead to a non-booting kernel.
+If the (uncompressed) size is bigger than 7.5 MB, reconfigure your kernel until
+it doesn't exceed these limits. One way of accomplishing this is by having most
+kernel drivers compiled as modules.  Ignoring this can lead to a non-booting
+kernel.
 </p>
 
-<note>
-If you use a 2.6.3 or higher kernel, sparc64 kernels can be up to 7.5 MB.
-</note>
-
 <p>
 Also, if your kernel is just a tad too big, you can try stripping it using the
 <c>strip</c> command:
@@ -293,16 +263,6 @@
 </p>
 
 <pre caption="Compiling the kernel">
-<comment>(For 2.4 kernel, sparc32)</comment>
-# <i>make dep &amp;&amp; make clean vmlinux modules modules_install</i>
-
-<comment>(For 2.4 kernel, sparc64)</comment>
-# <i>make dep &amp;&amp; make clean vmlinux image modules modules_install</i>
-
-<comment>(For 2.6 kernel, sparc32)</comment>
-# <i>make &amp;&amp; make modules_install</i>
-
-<comment>(For 2.6 kernel, sparc64)</comment>
 # <i>make &amp;&amp; make image modules_install</i>
 </pre>
 
@@ -313,16 +273,6 @@
 </p>
 
 <pre caption="Installing the kernel">
-<comment>(For 2.4 kernel, sparc32)</comment>
-# <i>cp vmlinux /boot/&lt;kernel-version&gt;</i>
-
-<comment>(For 2.4 kernel, sparc64)</comment>
-# <i>cp arch/sparc64/boot/image /boot/&lt;kernel-version&gt;</i>
-
-<comment>(For 2.6 kernel, sparc32)</comment>
-# <i>cp arch/sparc/boot/image /boot/&lt;kernel-version&gt;</i>
-
-<comment>(For 2.6 kernel, sparc64)</comment>
 # <i>cp arch/sparc64/boot/image /boot/&lt;kernel-version&gt;</i>
 </pre>
 
@@ -341,9 +291,9 @@
 <body>
 
 <p>
-You should list the modules you want automatically loaded in 
-<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). 
-You can add extra options to the modules too if you want.
+You should list the modules you want automatically loaded in
+<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to
+the modules too if you want.
 </p>
 
 <p>
@@ -358,16 +308,14 @@
 
 <p>
 For instance, to automatically load the <c>3c59x.o</c> module, edit the
-<path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module
-name in it.
+<path>kernel-2.6</path> file and enter the module name in it.
 </p>
 
-<pre caption="Editing /etc/modules.autoload.d/kernel-2.4">
-<comment>(Example for 2.4 kernels)</comment>
-# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i>
+<pre caption="Editing /etc/modules.autoload.d/kernel-2.6">
+# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i>
 </pre>
 
-<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
+<pre caption="/etc/modules.autoload.d/kernel-2.6">
 3c59x
 </pre>
 



1.43                 xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml

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

Index: hb-install-sparc-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- hb-install-sparc-medium.xml	30 Aug 2006 22:52:28 -0000	1.42
+++ hb-install-sparc-medium.xml	7 May 2007 18:11:41 -0000	1.43
@@ -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-sparc-medium.xml,v 1.42 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml,v 1.43 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -61,7 +61,6 @@
 </subsection>
 </section>
 <!-- Copy/Paste from hb-install-x86-medium.xml -->
-<!-- Warning: The part originally contains "x86" -->
 <!-- START -->
 <section>
 <title>The Gentoo Installation CDs</title>
@@ -87,7 +86,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2006.1/index.xml">Gentoo 2006.1 Handbooks</uri>.
+link="2007.0/index.xml">Gentoo 2007.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -108,14 +107,6 @@
 </ul>
 
 <p>
-We currently only provide Installation CDs for the sparc64 architecture. Users
-of sparc32 can use the experimental netboot images to install Gentoo from.
-More information about netbooting can be found in our <uri
-link="/doc/en/gentoo-sparc-netboot-howto.xml">Gentoo/SPARC Netboot
-HOWTO</uri>.
-</p>
-
-<p>
 To help you decide which Installation CD you need, we have written down the
 major advantages and disadvantages of each Installation CD.
 </p>
@@ -127,7 +118,7 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-sparc64-minimal-2006.1.iso</c> 
+The Minimal Installation CD is called <c>install-sparc64-minimal-2007.0.iso</c> 
 and takes up only 32 MB of diskspace. You can use this Installation CD to 
 install Gentoo, but always with a working Internet connection only.
 </p>
@@ -158,7 +149,7 @@
 
 <p>
 The Universal Installation CD is called
-<c>install-sparc64-universal-2006.1.iso</c> and uses 287 MB. You can use this
+<c>install-sparc64-universal-2007.0.iso</c> and uses 287 MB. You can use this
 Installation CD to install Gentoo, and you can even use it to install Gentoo
 without a working internet connection, just in case you want to bring Gentoo to
 another PC than the one you are currently installing Gentoo on :)
@@ -236,10 +227,10 @@
 </p>
 
 <p>
-You can download any of the Installation CDs (and, if you want to, a Packages 
-CD as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The
-Installation CDs are located in the 
-<path>releases/sparc/2006.1/sparc64/installcd</path> directory.
+You can download any of the Installation CDs (and, if you want to, a 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.
 </p>
 
 <p>
@@ -250,7 +241,7 @@
 <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>install-sparc64-minimal-2006.1.iso.DIGESTS</path>). You can check the MD5 
+<path>install-sparc64-minimal-2007.0.iso.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>
@@ -310,13 +301,16 @@
 </pre>
 
 <p>
-You will be greeted by the SILO boot manager (on the Installation CD). Type in
-<c>gentoo</c> and press enter to continue booting the 
-system:
+You will be greeted by the SILO boot manager (on the Installation CD). You can
+hit Enter for more help if you want. Type in <c>2617</c> (if you have an FC-AL
+machine; check the <uri
+link="http://www.gentoo.org/proj/en/base/sparc/sunhw.xml">Hardware Compatibility
+List</uri>) or <c>2620</c> (for everyone else) and press enter to continue
+booting the system:
 </p>
 
 <pre caption="Continue booting from the Installation CD">
-boot: <i>gentoo</i>
+boot: <i>2620</i>
 </pre>
 
 <p>
@@ -325,10 +319,8 @@
 </p>
 
 <p>
-You should have a root ("#") prompt on the current console and can also switch
-to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you
-started on by pressing Alt-F1.  You will also find a root prompt on the serial
-console (<path>ttyS0</path>).
+You should have a root ("#") prompt on the current console. You will also find a
+root prompt on the serial console (<path>ttyS0</path>).
 </p>
 
 <p>
@@ -431,7 +423,7 @@
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i>
 </pre>
 
 <p>



1.107                xml/htdocs/doc/en/handbook/hb-install-stage.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.107&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.107&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?r1=1.106&r2=1.107

Index: hb-install-stage.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -r1.106 -r1.107
--- hb-install-stage.xml	30 Mar 2007 12:01:19 -0000	1.106
+++ hb-install-stage.xml	7 May 2007 18:11:41 -0000	1.107
@@ -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/hb-install-stage.xml,v 1.106 2007/03/30 12:01:19 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.107 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 describe how you extract the stage3 archive and configure Portage.
 </abstract>
 
-<version>7.5</version>
-<date>2007-03-10</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Installing a Stage Tarball</title>
@@ -234,12 +234,12 @@
 <c>tar</c>. Make sure you use the same options (<c>xvjpf</c>). The <c>v</c>
 argument is optional and not supported in some <c>tar</c> versions.  In the
 next example, we extract the stage tarball
-<path>stage3-&lt;subarch&gt;-2006.1.tar.bz2</path>. Be sure to substitute
+<path>stage3-&lt;subarch&gt;-2007.0.tar.bz2</path>. Be sure to substitute
 the tarball filename with your stage.
 </p>
 
 <pre caption="Extracting the stage tarball">
-# <i>tar xvjpf /mnt/cdrom/stages/stage3-&lt;subarch&gt;-2006.1.tar.bz2</i>
+# <i>tar xvjpf /mnt/cdrom/stages/stage3-&lt;subarch&gt;-2007.0.tar.bz2</i>
 </pre>
 
 <p>



1.106                xml/htdocs/doc/en/handbook/hb-install-system.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml?rev=1.106&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml?rev=1.106&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml?r1=1.105&r2=1.106

Index: hb-install-system.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -r1.105 -r1.106
--- hb-install-system.xml	12 Feb 2007 21:55:42 -0000	1.105
+++ hb-install-system.xml	7 May 2007 18:11:41 -0000	1.106
@@ -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/hb-install-system.xml,v 1.105 2007/02/12 21:55:42 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.106 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -14,8 +14,8 @@
 to progress to that state.
 </abstract>
 
-<version>7.6</version>
-<date>2007-02-12</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Chrooting</title>
@@ -199,14 +199,7 @@
 Gentoo developers.
 </p>
 
-<p test="contains('Alpha x86', func:keyval('arch'))">
-Previously, such a profile was barely touched by the user. However, <keyval
-id="arch"/> users can choose between two profiles, one for a 2.4 kernel and one
-for a 2.6 kernel. This requirement has been imposed to improve the integration
-of the 2.6 kernels.
-</p>
-
-<p test="contains('AMD64 arm HPPA IA64 MIPS PPC PPC64 SPARC', func:keyval('arch'))">
+<p>
 Previously, such a profile was untouched by the users. However, there may be
 certain situations in which you may decide a profile change is necessary.
 </p>
@@ -217,7 +210,7 @@
 
 <pre caption="Verifying system profile">
 # <i>ls -FGg /etc/make.profile</i>
-lrwxrwxrwx  1 48 Apr  8 18:51 /etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2006.1/
+lrwxrwxrwx  1 48 Apr  8 18:51 /etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2007.0/
 </pre>
 
 <p>
@@ -227,86 +220,27 @@
 
 <p>
 There are also <c>desktop</c> and <c>server</c> subprofiles available for some
-architectures. Look inside the <path>2006.1/</path> profile to see if there is
+architectures. Look inside the <path>2007.0/</path> profile to see if there is
 one available for your architecture. You may wish to view the <c>desktop</c>
 profile's <path>make.defaults</path> to determine if it fits your needs.
 </p>
 
-<p test="func:keyval('arch')='AMD64'">
-If you want to have a pure 64-bit environment, with no 32-bit applications or
-libraries, you should use a non-multilib profile:
-</p>
-
-<pre test="func:keyval('arch')='AMD64'" caption="Switching to a non-multilib profile">
-# <i>ln -snf /usr/portage/profiles/default-linux/amd64/2006.1/no-multilib /etc/make.profile</i>
-</pre>
-
 <p>
-Some users may wish to install a system based on the older Linux 2.4 profile.
-If you have good reason to do this, then you should first check that an
-additional profile exists. On x86, we can do this with the following command:
+After viewing the available profiles for your architecture in
+<path>/usr/portage/profiles/</path>, you can use a different one if you wish:
 </p>
 
-<pre caption="Finding out if an additional profile exists">
-# <i>ls -d /usr/portage/profiles/default-linux/x86/no-nptl/2.4</i>
-/usr/portage/profiles/default-linux/x86/no-nptl/2.4
+<pre caption="Changing profiles">
+# <i>ln -snf /usr/portage/profiles/&lt;profile name&gt; /etc/make.profile</i>
 </pre>
 
-<p>
-The above example shows that the additional 2.4 profile exists (i.e. it didn't
-complain about missing file or directory). It is recommended that you stay with
-the default, but if you wish to switch, you can do so as follows:
-</p>
-
-<pre caption="Switching to a 2.4 profile">
-<comment>(Make sure you use the right architecture, the example below is for x86)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/x86/no-nptl/2.4 /etc/make.profile</i>
-<comment>(List the files in the 2.4 profile)</comment>
-# <i>ls -FGg /etc/make.profile/</i>
-total 12
--rw-r--r--  1 939 Dec 10 14:06 packages
--rw-r--r--  1 347 Dec  3  2004 parent
--rw-r--r--  1 573 Dec  3  2004 virtuals
-</pre>
-
-<p test="func:keyval('arch')='PPC'">
-For ppc, there are a number of new profiles provided with 2006.1:
-</p>
-
-<pre test="func:keyval('arch')='PPC'" caption="PPC Profiles">
-<comment>(Generic PPC profile, for all PPC machines, minimal)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc32/2006.1 /etc/make.profile</i>
-<comment>(G3 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc32/2006.1/G3 /etc/make.profile</i>
-<comment>(G3 Pegasos profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc32/2006.1/G3/Pegasos/ /etc/make.profile</i>
-<comment>(G4 (Altivec) profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc32/2006.1/G4 /etc/make.profile</i>
-<comment>(G4 (Altivec) Pegasos profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc32/2006.1/G4/Pegasos/ /etc/make.profile</i>
-</pre>
-
-<p test="func:keyval('arch')='PPC64'">
-For ppc64, there are a number of new profiles provided with 2006.1:
+<p test="func:keyval('arch')='AMD64'">
+If you want to have a pure 64-bit environment, with no 32-bit applications or
+libraries, you should use a non-multilib profile:
 </p>
 
-<pre test="func:keyval('arch')='PPC64'" caption="PPC64 Profiles">
-<comment>(Generic 64bit userland PPC64 profile, for all PPC64 machines)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/64bit-userland /etc/make.profile</i>
-<comment>(Generic 32bit userland PPC64 profile, for all PPC64 machines)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/32bit-userland /etc/make.profile</i>
-<comment>(Each type of userland has sub profiles as follows, with (userland) replaced with the chosen userland from above)</comment>
-<comment>(970 profile for JS20)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/(userland)/970 /etc/make.profile</i>
-<comment>(G5 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/(userland)/970/pmac /etc/make.profile</i>
-<comment>(POWER3 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/(userland)/power3 /etc/make.profile</i>
-<comment>(POWER4 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/(userland)/power4 /etc/make.profile</i>
-<comment>(POWER5 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/(userland)/power5 /etc/make.profile</i>
-<comment>(The multilib profile is not stable as of this release.)</comment>
+<pre test="func:keyval('arch')='AMD64'" caption="Switching to a non-multilib profile">
+# <i>ln -snf /usr/portage/profiles/default-linux/amd64/2007.0/no-multilib /etc/make.profile</i>
 </pre>
 
 </body>
@@ -382,7 +316,7 @@
 </body>
 </subsection>
 <subsection>
-<title>Optional: GLIBC Locales</title>
+<title>Optional: glibc Locales</title>
 <body>
 
 <p>
@@ -411,11 +345,6 @@
 have specified in the <path>/etc/locale.gen</path> file.
 </p>
 
-<note>
-<c>locale-gen</c> is available in <c>glibc-2.3.6-r4</c> and newer. If you have
-an older version of glibc, you should update it now.
-</note>
-
 <p>
 Now continue with <uri link="?part=1&amp;chap=7">Configuring the Kernel</uri>.
 </p>



1.46                 xml/htdocs/doc/en/handbook/hb-install-tools.xml

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

Index: hb-install-tools.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-tools.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- hb-install-tools.xml	10 Apr 2007 05:40:49 -0000	1.45
+++ hb-install-tools.xml	7 May 2007 18:11:41 -0000	1.46
@@ -4,37 +4,16 @@
 <!-- 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-tools.xml,v 1.45 2007/04/10 05:40:49 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-tools.xml,v 1.46 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
 <abstract>
-As mentioned before, Gentoo is about choices. In this chapter we help you
-choose and install some important tools.
+In this chapter we help you choose and install some important tools.
 </abstract>
 
-<version>7.3</version>
-<date>2007-04-09</date>
-
-<section>
-<title>Device Manager</title>
-<body>
-
-<p>
-If you are using a 2.4 kernel <e>and</e> are installing Gentoo from stage 3, 
-there are a few things you <e>need</e> to do. Since Gentoo now uses udev by 
-default and udev is not supported by 2.4 kernels, you will have to make use of 
-devfsd and remove udev.
-</p>
-
-<pre caption="Installing devfsd">
-<comment>(For those using 2.4.x kernels with a stage 3 install)</comment>
-# <i>emerge --unmerge udev</i>
-# <i>emerge devfsd</i>
-</pre>
-
-</body>
-</section>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>System Logger</title>
@@ -67,14 +46,6 @@
 rotation mechanism for the log files.
 </p>
 
-<!--
-  Even though syslog-ng does not rotate the logs, it does conform to the syslog
-  RFC (http://www.faqs.org/rfcs/rfc3164.html) and is far more powerful than most
-  other system loggers. That and some architectures really prefer syslog-ng
-  above others (metalog for instance doesn't work nicely with sparc all the
-  time).
--->
-
 <p>
 To install the system logger of your choice, <c>emerge</c> it and have it added
 to the default runlevel using <c>rc-update</c>. The following example installs
@@ -215,8 +186,8 @@
 <body>
 
 <p>
-If you don't require any additional networking-related tools (such as rp-pppoe
-or a dhcp client) continue with <uri link="?part=1&amp;chap=10">Configuring the
+If you don't require any additional networking-related tools (such as ppp or a
+dhcp client) continue with <uri link="?part=1&amp;chap=10">Configuring the
 Bootloader</uri>.
 </p>
 
@@ -238,14 +209,6 @@
 # <i>emerge dhcpcd</i>
 </pre>
 
-<note>
-You'll probably need to update <c>baselayout</c> at this point (<c>emerge -u
-baselayout</c>), as <c>dhcpcd-3.x</c> isn't compatible with the
-<c>baselayout</c> version found in the stage tarballs. Once you've updated
-<c>baselayout</c>, you'll need to redo your timezone info by editing
-<path>/etc/conf.d/clock</path>.
-</note>
-
 </body>
 </subsection>
 <subsection>
@@ -253,21 +216,14 @@
 <body>
 
 <p>
-If you need <c>rp-pppoe</c> to connect to the net, you need to install it.
+If you need <c>ppp</c> to connect to the net, you need to install it.
 </p>
 
-<pre caption="Installing rp-pppoe">
-# <i>USE="-X" emerge rp-pppoe</i>
+<pre caption="Installing ppp">
+# <i>emerge ppp</i>
 </pre>
 
 <p>
-The <c>USE="-X"</c> will prohibit xorg-x11 to be installed as a dependency
-(<c>rp-pppoe</c> has graphical tools; if you want those enabled, you can
-recompile <c>rp-pppoe</c> later on or have xorg-x11 installed now -- which takes a
-long time to compile).
-</p>
-
-<p>
 Now continue with <uri link="?part=1&amp;chap=10">Configuring the
 Bootloader</uri>.
 </p>



1.8                  xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.7&r2=1.8

Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-install-x86+amd64-bootloader.xml	13 Mar 2007 14:31:03 -0000	1.7
+++ hb-install-x86+amd64-bootloader.xml	7 May 2007 18:11:41 -0000	1.8
@@ -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-x86+amd64-bootloader.xml,v 1.7 2007/03/13 14:31:03 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.8 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
-<version>4.3</version>
-<date>2007-03-12</date>
+<version>5.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Making your Choice</title>
@@ -59,7 +59,7 @@
 set the <c>vga</c> statement.
 </p>
 
-<p test="func:keyval('arch')='AMD64'">
+<p test="contains('AMD64 IA64',func:keyval('arch'))">
 64-bit systems must use the the <c>vesafb</c> driver, and need the <c>vga</c>
 statement.
 </p>
@@ -160,7 +160,7 @@
 </table>
 
 </body>
-<body test="func:keyval('arch')='AMD64'">
+<body test="contains('AMD64 IA64',func:keyval('arch'))">
 
 <p>
 The result of those two statements could be something like <c>vga=0x318
@@ -168,11 +168,15 @@
 shortly.
 </p>
 
-<p>
+<p test="func:keyval('arch')='AMD64'">
 While LILO does work on AMD64, Gentoo only supports using GRUB. Now continue by
 its <uri link="#grub">installation</uri>.
 </p>
 
+<p test="func:keyval('arch')='IA64'">
+Now, you should install the <uri link="#elilo">elilo bootloader</uri>.
+</p>
+
 </body>
 <body test="func:keyval('arch')='x86'">
 
@@ -191,7 +195,7 @@
 </body>
 </subsection>
 </section>
-<section id="grub">
+<section id="grub" test="contains('AMD64 x86',func:keyval('arch'))">
 <title>Default: Using GRUB</title>
 <subsection>
 <title>Understanding GRUB's terminology</title>
@@ -658,6 +662,79 @@
 </body>
 </subsection>
 </section>
+<section id="elilo" test="func:keyval('arch')='IA64'">
+<title>Default: Installing elilo</title>
+<body>
+
+<p>
+On the IA64 platform, the boot loader is called elilo. You may need to emerge
+it on your machine first.
+</p>
+
+<pre caption="Installing elilo">
+# <i>emerge elilo</i>
+</pre>
+
+<p>
+You can find the configuration file at <path>/etc/elilo.conf</path> and a
+sample file in the typical docs dir
+<path>/usr/share/doc/elilo-&lt;ver&gt;/</path>. Here is another sample
+configuration:
+</p>
+
+<pre caption="/etc/elilo.conf example">
+boot=/dev/sda1
+delay=30
+timeout=50
+default=Gentoo
+append="console=ttyS0,9600"
+prompt
+
+image=/vmlinuz
+	label=Gentoo
+	root=/dev/sda2
+	read-only
+
+image=/vmlinuz.old
+	label=Gentoo.old
+	root=/dev/sda2
+	read-only
+</pre>
+
+<p>
+The <c>boot</c> line tells elilo the location of the boot partition (in this
+case, <path>/dev/sda1</path>). The <c>delay</c> line sets the number of
+10<sup>th</sup> of seconds before automatically booting the default when in
+non-interactive mode. The <c>timeout</c> line is just like the delay line but
+for interactive mode. The <c>default</c> line sets the default kernel entry
+(which is defined below). The <c>append</c> line adds extra options to the
+kernel command line. The <c>prompt</c> sets the default elilo behavior to
+interactive.
+</p>
+
+<p>
+The sections that start with <c>image</c> define different bootable images.
+Each image has a nice <c>label</c>, a <c>root</c> filesystem, and will only
+mount the root filesystem <c>read-only</c>.
+</p>
+
+<p>
+When configuration is done, just run <c>elilo --efiboot</c>. The
+<c>--efiboot</c> option adds a menu entry for Gentoo Linux to the EFI Boot
+Manager.
+</p>
+
+<pre caption="Applying the elilo configuration">
+# <i>elilo --efiboot</i>
+</pre>
+
+<p>
+Now continue with <uri link="#reboot">Rebooting the System</uri>.
+</p>
+
+</body>
+</section>
+
 <section id="reboot">
 <title>Rebooting the System</title>
 <subsection>
@@ -668,7 +745,14 @@
 that one magical command you have been waiting for: <c>reboot</c>.
 </p>
 
-<pre caption="Unmounting all partitions and rebooting">
+<pre caption="Unmounting all partitions and rebooting" test="func:keyval('arch')='IA64'">
+# <i>exit</i>
+cdimage ~# <i>cd</i>
+cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/sys /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
+cdimage ~# <i>reboot</i>
+</pre>
+
+<pre caption="Unmounting all partitions and rebooting" test="not(func:keyval('arch')='IA64')">
 # <i>exit</i>
 cdimage ~# <i>cd</i>
 cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i>
@@ -680,6 +764,11 @@
 booted again instead of your new Gentoo system.
 </p>
 
+<p test="func:keyval('arch')='IA64'">
+When you reboot you should see a new Gentoo Linux menu option in the EFI Boot
+Manager which will boot Gentoo.
+</p>
+
 <p>
 Once rebooted in your Gentoo installation, finish up with <uri
 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.



1.8                  xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?r1=1.7&r2=1.8

Index: hb-install-x86+amd64-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-install-x86+amd64-disk.xml	16 Feb 2007 13:45:39 -0000	1.7
+++ hb-install-x86+amd64-disk.xml	7 May 2007 18:11:41 -0000	1.8
@@ -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/hb-install-x86+amd64-disk.xml,v 1.7 2007/02/16 13:45:39 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v 1.8 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 This chapter describes how to partition a disk for future usage.
 </abstract>
 
-<version>4.2</version>
-<date>2007-02-16</date>
+<version>5.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -613,7 +613,7 @@
 
 <pre caption="Applying a filesystem on a partition">
 # <i>mke2fs /dev/hda1</i>
-# <i>mke2fs -j -O dir_index /dev/hda3</i>
+# <i>mke2fs -j /dev/hda3</i>
 </pre>
 
 <p>



1.10                 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.10&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.10&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?r1=1.9&r2=1.10

Index: hb-install-x86+amd64-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- hb-install-x86+amd64-kernel.xml	13 Mar 2007 00:30:09 -0000	1.9
+++ hb-install-x86+amd64-kernel.xml	7 May 2007 18:11:41 -0000	1.10
@@ -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/hb-install-x86+amd64-kernel.xml,v 1.9 2007/03/13 00:30:09 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml,v 1.10 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 explains how to configure your kernel.
 </abstract>
 
-<version>4.3</version>
-<date>2007-03-12</date>
+<version>5.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Timezone</title>
@@ -22,8 +22,8 @@
 
 <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
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</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>
@@ -31,7 +31,8 @@
 <pre caption="Setting the timezone information">
 # <i>ls /usr/share/zoneinfo</i>
 <comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
 </pre>
 
 </body>
@@ -56,9 +57,8 @@
 </p>
 
 <p test="func:keyval('arch')='AMD64'">
-For AMD64-based systems we have <c>gentoo-sources</c> (kernel v2.6 source
-patched with amd64 specific fixes for stability, performance and hardware
-support).
+For AMD64-based systems we have <c>gentoo-sources</c> (kernel source patched
+with amd64 specific fixes for stability, performance and hardware support).
 </p>
 
 <p>
@@ -207,21 +207,7 @@
 </body>
 <body test="func:keyval('arch')='x86'">
 
-<p>
-If you are using a 2.4 kernel, you need to select <c>/dev file
-system</c> as 2.4 kernels do not support <c>udev</c>.
-</p>
-
 <pre caption="Selecting necessary file systems">
-<comment>(With a 2.4.x kernel)</comment>
-File systems ---&gt;
-  [*] Virtual memory file system support (former shm fs)
-  [*] /proc file system support
-  [*] /dev file system support (EXPERIMENTAL)
-  [*]   automatically mount /dev at boot
-  [ ] /dev/pts file system for Unix98 PTYs
-
-<comment>(With a 2.6.x kernel)</comment>
 File systems ---&gt;
   Pseudo Filesystems ---&gt;
     [*] /proc file system support
@@ -235,21 +221,6 @@
   &lt;*&gt; XFS filesystem support
 </pre>
 
-<p>
-If your BIOS can't handle large hard drives and you jumpered the hard drive to
-report a limited size you have to enable the following option to gain access to
-your whole hard drive:
-</p>
-
-<pre caption="Selecting autogeometry resizing support">
-<comment>(2.4.x kernel only)</comment>
-ATA/IDE/MFM/RLL support ---&gt;
-  IDE, ATA and ATAPI Block devices ---&gt;
-    &lt;*&gt;   Include IDE/ATA-2 DISK support
-    [ ]     Use multi-mode by default
-    [*]     Auto-Geometry Resizing support
-</pre>
-
 </body>
 <body test="func:keyval('arch')='AMD64'">
 
@@ -295,13 +266,6 @@
 </pre>
 
 <pre caption="Selecting PPPoE necessary drivers" test="func:keyval('arch')='x86'">
-<comment>(With a 2.4.x kernel)</comment>
-Network device support ---&gt;
-  &lt;*&gt; PPP (point-to-point protocol) support
-  &lt;*&gt;   PPP support for async serial ports
-  &lt;*&gt;   PPP support for sync tty ports
-
-<comment>(With a 2.6.x kernel)</comment>
 Device Drivers ---&gt;
   Networking support ---&gt;
     &lt;*&gt; PPP (point-to-point protocol) support
@@ -311,8 +275,8 @@
 
 <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.
+does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
+when configured to do kernel mode PPPoE.
 </p>
 
 <p>
@@ -354,18 +318,11 @@
 <body test="func:keyval('arch')='x86'">
 
 <p>
-Laptop-users who want PCMCIA support should <e>not</e> use the PCMCIA drivers if
-they choose to use a 2.4 kernel. More recent drivers are available through the
-<c>pcmcia-cs</c> package which will be installed later on. 2.6-kernel users
-however should use the PCMCIA drivers from the kernel.
-</p>
-
-<p>
-Besides compiling in PCMCIA support in the 2.6 kernel, don't forget to enable
+If you want PCMCIA support for your laptop, don't forget to enable
 support for the PCMCIA card bridge present in your system:
 </p>
 
-<pre caption="Enabling PCMCIA support for 2.6 kernels">
+<pre caption="Enabling PCMCIA support">
 Bus options (PCI, PCMCIA, EISA, MCA, ISA)  ---&gt;
   PCCARD (PCMCIA/CardBus) support  ---&gt;
     &lt;*&gt; PCCard (PCMCIA/CardBus) support
@@ -397,15 +354,7 @@
 the configuration and start the compilation process:
 </p>
 
-<pre caption="Compiling the kernel" test="func:keyval('arch')='x86'">
-<comment>(For 2.4 kernel)</comment>
-# <i>make dep &amp;&amp; make bzImage modules modules_install</i>
-
-<comment>(For 2.6 kernel)</comment>
-# <i>make &amp;&amp; make modules_install</i>
-</pre>
-
-<pre caption="Compiling the kernel" test="func:keyval('arch')='AMD64'">
+<pre caption="Compiling the kernel">
 # <i>make &amp;&amp; make modules_install</i>
 </pre>
 
@@ -460,13 +409,11 @@
 <body test="func:keyval('arch')='x86'">
 
 <p>
-Next, if you are going to configure a 2.6 kernel, copy over the kernel 
-configuration used by the Installation CD to the location where genkernel 
-looks for the default kernel configuration:
+Next, copy over the kernel configuration used by the Installation CD to the
+location where genkernel looks for the default kernel configuration:
 </p>
 
 <pre caption="Copying over the Installation CD kernel config">
-<comment>(Only do this if you are going to configure a 2.6 kernel)</comment>
 # <i>zcat /proc/config.gz &gt; /usr/share/genkernel/x86/kernel-config-2.6</i>
 </pre>
 
@@ -513,11 +460,6 @@
 <title>Configuring the Modules</title>
 <body>
 
-<note test="func:keyval('arch')='x86'">
-If you chose a kernel 2.4, replace occurrences of <c>2.6</c> with <c>2.4</c> in
-this section.
-</note>
-
 <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



1.6                  xml/htdocs/doc/en/handbook/hb-install-x86+amd64-medium.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-medium.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-medium.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-medium.xml?r1=1.5&r2=1.6

Index: hb-install-x86+amd64-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-medium.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- hb-install-x86+amd64-medium.xml	28 Oct 2006 09:17:55 -0000	1.5
+++ hb-install-x86+amd64-medium.xml	7 May 2007 18:11:41 -0000	1.6
@@ -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/hb-install-x86+amd64-medium.xml,v 1.5 2006/10/28 09:17:55 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-medium.xml,v 1.6 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -14,8 +14,8 @@
 Installer LiveCD is possible as well.
 </abstract>
 
-<version>4.0</version>
-<date>2006-08-30</date>
+<version>5.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -116,7 +116,7 @@
 <impo>
 If you wish to install Gentoo without a working Internet connection, or would
 like to use one of the provided installers, please use the installation
-instructions described in the <uri link="2006.1/">Gentoo 2006.1
+instructions described in the <uri link="2007.0/">Gentoo 2007.0
 Handbooks</uri>.
 </impo>
 
@@ -460,14 +460,6 @@
 # <i>modprobe 8139too</i>
 </pre>
 
-<p>
-If you need PCMCIA support, you should start the <c>pcmcia</c> init script:
-</p>
-
-<pre caption="Starting the PCMCIA init script">
-# <i>/etc/init.d/pcmcia start</i>
-</pre>
-
 </body>
 </subsection>
 <subsection>



1.14                 xml/htdocs/doc/en/handbook/hb-net-advanced.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?r1=1.13&r2=1.14

Index: hb-net-advanced.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- hb-net-advanced.xml	28 Oct 2006 09:17:55 -0000	1.13
+++ hb-net-advanced.xml	7 May 2007 18:11:41 -0000	1.14
@@ -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/hb-net-advanced.xml,v 1.13 2006/10/28 09:17:55 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.14 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 before we learn about modular networking.
 </abstract>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Advanced Configuration</title>
@@ -28,7 +28,7 @@
 </p>
 
 <p>
-Here's a list of in-built instructions.
+Here's a list of built-in instructions.
 </p>
 
 <table>
@@ -237,11 +237,11 @@
 </p>
 
 <pre caption="variable name example">
-<comment># This does work, but the domain is invalid</comment>
+<comment>(This does work, but the domain is invalid)</comment>
 dns_domain_My____NET="My \"\\ NET"
 
-<comment># The above sets the dns domain to My "\ NET when a wireless card
-# connects to an AP whose ESSID is My "\ NET</comment>
+<comment>(The above sets the dns domain to My "\ NET when a wireless card
+connects to an AP whose ESSID is My "\ NET)</comment>
 </pre>
 
 </body>



1.11                 xml/htdocs/doc/en/handbook/hb-net-functions.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml?r1=1.10&r2=1.11

Index: hb-net-functions.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- hb-net-functions.xml	7 Mar 2007 01:00:20 -0000	1.10
+++ hb-net-functions.xml	7 May 2007 18:11:41 -0000	1.11
@@ -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/hb-net-functions.xml,v 1.10 2007/03/07 01:00:20 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml,v 1.11 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -12,8 +12,8 @@
 If you're feeling adventurous, you can add your own functions to networking.
 </abstract>
 
-<version>7.1</version>
-<date>2007-03-06</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Standard function hooks</title>



1.11                 xml/htdocs/doc/en/handbook/hb-net-management.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml?r1=1.10&r2=1.11

Index: hb-net-management.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- hb-net-management.xml	25 Apr 2007 14:57:33 -0000	1.10
+++ hb-net-management.xml	7 May 2007 18:11:41 -0000	1.11
@@ -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/hb-net-management.xml,v 1.10 2007/04/25 14:57:33 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml,v 1.11 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -12,8 +12,8 @@
 For laptop users or people who move their computer around different networks.
 </abstract>
 
-<version>7.2</version>
-<date>2007-04-25</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Network Management</title>



1.8                  xml/htdocs/doc/en/handbook/hb-net-start.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml?r1=1.7&r2=1.8

Index: hb-net-start.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-net-start.xml	28 Oct 2006 09:17:55 -0000	1.7
+++ hb-net-start.xml	7 May 2007 18:11:41 -0000	1.8
@@ -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/hb-net-start.xml,v 1.7 2006/10/28 09:17:55 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml,v 1.8 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 environments.
 </abstract>
 
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-05-07</date>
 
 <section>
 <title>Getting started</title>
@@ -28,7 +28,7 @@
 </note>
 
 <note>
-This document requires you are running <c>baselayout-1.11.11</c> or better.
+This document requires you to run <c>baselayout-1.11.11</c> or better.
 </note>
 
 <p>
@@ -59,7 +59,7 @@
 
 <comment># For static IP using netmask notation</comment>
 config_eth0=( "192.168.0.7 netmask 255.255.255.0" )
-routes_eth0=( "default gw 192.168.0.1" )
+routes_eth0=( "default via 192.168.0.1" )
 </pre>
 
 <note>
@@ -67,19 +67,19 @@
 </note>
 
 <note>
-CIDR stands for Classless InterDomain Routing. 
-Originally, IPv4 addresses were classified as A, B, or C.
-The early classification system did not envision the massive popularity of the
-Internet, and is in danger of running out of new unique addresses. CIDR is an
-addressing scheme that allows one IP address to designate many IP addresses.
-A CIDR IP address looks like a normal IP address except that it ends with a
-slash followed by a number; for example, 192.168.0.0/16.
-CIDR is described in <uri link="http://rfc.net/rfc1519.html">RFC 1519</uri>.
+CIDR stands for Classless InterDomain Routing. Originally, IPv4 addresses were
+classified as A, B, or C. The early classification system did not envision the
+massive popularity of the Internet, and is in danger of running out of new
+unique addresses. CIDR is an addressing scheme that allows one IP address to
+designate many IP addresses. A CIDR IP address looks like a normal IP address
+except that it ends with a slash followed by a number; for example,
+192.168.0.0/16. CIDR is described in <uri link="http://rfc.net/rfc1519.html">RFC
+1519</uri>.
 </note>
 
 <p>
 Now that we have configured our interface, we can start and stop it using the
-below commands
+following commands:
 </p>
 
 <pre caption="Starting and stopping network scripts">



1.15                 xml/htdocs/doc/en/handbook/hb-net-wireless.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?r1=1.14&r2=1.15

Index: hb-net-wireless.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- hb-net-wireless.xml	20 Mar 2007 10:14:04 -0000	1.14
+++ hb-net-wireless.xml	7 May 2007 18:11:41 -0000	1.15
@@ -4,16 +4,16 @@
 <!-- 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-net-wireless.xml,v 1.14 2007/03/20 10:14:04 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.15 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <sections>
 
 <abstract>
-Wireless isn't straight-forward. Hopefully we'll get you working!
+Wireless isn't straightforward. Hopefully we'll get you working!
 </abstract>
 
 <version>8.0</version>
-<date>2007-03-20</date>
+<date>2007-05-07</date>
 
 <section>
 <title>Introduction</title>
@@ -29,8 +29,8 @@
 <c>wpa_supplicant</c> is the best choice, but it does not support all drivers.
 For a list of supported drivers, <uri
 link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant
-site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's
-that you have configured for.
+site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSIDs
+that you have configured.
 </p>
 
 <p>
@@ -39,12 +39,11 @@
 </p>
 
 <warn>
-The <c>linux-wlan-ng</c> driver is not supported by baselayout at this
-time. This is because <c>linux-wlan-ng</c> have their own setup and
-configuration which is completely different to everyone else's. The
-<c>linux-wlan-ng</c> developers are rumoured to be changing their setup over to
-<c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c>
-with baselayout.
+The <c>linux-wlan-ng</c> driver is not supported by baselayout at this time.
+This is because <c>linux-wlan-ng</c> have its own setup and configuration which
+is completely different to everyone else's. The <c>linux-wlan-ng</c> developers
+are rumoured to be changing their setup over to <c>wireless-tools</c>, so when
+this happens you may use <c>linux-wlan-ng</c> with baselayout.
 </warn>
 
 </body>
@@ -55,7 +54,7 @@
 
 <p>
 <uri link="http://hostap.epitest.fi/wpa_supplicant">WPA Supplicant</uri> is a
-package that allows you to connect to WPA enabled access points. It's setup is
+package that allows you to connect to WPA enabled access points. Its setup is
 fairly fluid as it is still in beta - however it works fine for the most part.
 </p>
 



1.68                 xml/htdocs/doc/en/handbook/index.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/index.xml?rev=1.68&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/index.xml?rev=1.68&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/index.xml?r1=1.67&r2=1.68

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- index.xml	31 Mar 2007 05:42:58 -0000	1.67
+++ index.xml	7 May 2007 18:11:41 -0000	1.68
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.67 2007/03/31 05:42:58 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.68 2007/05/07 18:11:41 nightmorph Exp $ -->
 
 <guide link="/doc/en/handbook/index.xml">
 <title>Gentoo Handbook</title>
@@ -19,8 +19,8 @@
 
 <license/>
 
-<version>0.43</version>
-<date>2007-03-30</date>
+<version>0.44</version>
+<date>2007-05-07</date>
 
 <chapter>
 <title>The Gentoo Handbook Effort</title>
@@ -88,7 +88,8 @@
     <uri link="handbook-ppc64.xml">ppc64</uri>, 
     <uri link="handbook-alpha.xml">alpha</uri>, 
     <uri link="handbook-hppa.xml">hppa</uri>, 
-    <uri link="handbook-mips.xml">mips</uri>
+    <uri link="handbook-mips.xml">mips</uri>,
+    <uri link="handbook-arm.xml">arm</uri>
   </ti>
 </tr>
 <tr>
@@ -121,9 +122,9 @@
 </tr>
 <tr>
   <ti>HTML</ti>
-  <ti>2006.1 Specific Networkless Installation Instructions</ti>
+  <ti>2007.0 Specific Networkless Installation Instructions</ti>
   <ti>
-    <uri link="/doc/en/handbook/2006.1/index.xml">2006.1 Gentoo
+    <uri link="/doc/en/handbook/2007.0/index.xml">2007.0 Gentoo
     Handbooks</uri>
   </ti>
 </tr>
@@ -133,7 +134,7 @@
 We also have release-specific handbooks which include the installation
 instructions for <b>networkless installations</b> using the released CDs. If
 you are interested in performing a networkless installation, please consult the
-<uri link="/doc/en/handbook/2006.1/index.xml">Gentoo Linux 2006.1
+<uri link="/doc/en/handbook/2007.0/index.xml">Gentoo Linux 2007.0
 Handbook</uri> for your architecture.
 </p>
 
@@ -216,6 +217,18 @@
     <uri link="2006.0/handbook-x86.xml">x86</uri>
   </ti>
 </tr>
+<tr>
+  <ti>2006.1</ti>
+  <ti>
+    <uri link="2006.1/handbook-alpha.xml">alpha</uri>, 
+    <uri link="2006.1/handbook-amd64.xml">amd64</uri>, 
+    <uri link="2006.1/handbook-hppa.xml">hppa</uri>, 
+    <uri link="2006.1/handbook-ppc.xml">ppc</uri>, 
+    <uri link="2006.1/handbook-ppc64.xml">ppc64</uri>, 
+    <uri link="2006.1/handbook-sparc.xml">sparc</uri>, 
+    <uri link="2006.1/handbook-x86.xml">x86</uri>
+  </ti>
+</tr>
 </table>
 
 </body>



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