[gentoo-doc-cvs] cvs commit: hb-install-mips-stage.xml

[Shyam Mani]

fox2mike    06/02/27 00:55:35

  Modified:    xml/htdocs/doc/en/handbook handbook-mips.xml
                        handbook-ppc.xml hb-install-alpha-medium.xml
                        hb-install-amd64-medium.xml hb-install-config.xml
                        hb-install-hppa-kernel.xml
                        hb-install-hppa-medium.xml
                        hb-install-mips-bootloader.xml
                        hb-install-mips-disk.xml hb-install-mips-kernel.xml
                        hb-install-mips-medium.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-medium.xml hb-install-stage.xml
                        hb-install-system.xml hb-install-x86-medium.xml
                        index.xml
  Added:       xml/htdocs/doc/en/handbook hb-install-mips-stage.xml
  Log:
  Handbook for 2006.0, "Chuck Norris can divide by zero"

Revision  Changes    Path
1.108     +6 -6      xml/htdocs/doc/en/handbook/handbook-mips.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-mips.xml?rev=1.108&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-mips.xml?rev=1.108&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-mips.xml.diff?r1=1.107&r2=1.108&cvsroot=gentoo

Index: handbook-mips.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- handbook-mips.xml	19 Dec 2005 12:36:15 -0000	1.107
+++ handbook-mips.xml	27 Feb 2006 00:55:34 -0000	1.108
@@ -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.107 2005/12/19 12:36:15 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v 1.108 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <book link="handbook-mips.xml">
 <title>Gentoo Linux/MIPS Handbook</title>
@@ -90,7 +90,7 @@
   <mail link="kumba@g.o">Joshua Kinard</mail>
 </author>
 <author title="Editor">
-  <mail link="stuartl@××××××××××××××××××.org">Stuart Longland</mail>
+  <mail link="redhatter@g.o">Stuart Longland</mail>
 </author>
 <author title="Editor">
   <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
@@ -124,8 +124,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>4.3</version>
-<date>2005-12-19</date>
+<version>4.4</version>
+<date>2006-02-27</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -175,7 +175,7 @@
 Gentoo installs work through a stage3 archive. In this chapter we
 describe how you extract the stage3 archive and configure Portage.
 </abstract>
-  <include href="hb-install-stage.xml"/>
+  <include href="hb-install-mips-stage.xml"/>
 </chapter>
 
 <chapter>
@@ -221,7 +221,7 @@
 <abstract>
 On both Silicon Graphics machines, and on Cobalt servers, both require the use
 of a bootloader to load the kernel.  This section covers setting up
-arcboot (for SGI machines) and colo for Cobalt servers.
+arcboot/arcload (for SGI machines) and colo for Cobalt servers.
 </abstract>
   <include href="hb-install-mips-bootloader.xml"/>
 </chapter>



1.138     +6 -3      xml/htdocs/doc/en/handbook/handbook-ppc.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.138&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.138&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc.xml.diff?r1=1.137&r2=1.138&cvsroot=gentoo

Index: handbook-ppc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v
retrieving revision 1.137
retrieving revision 1.138
diff -u -r1.137 -r1.138
--- handbook-ppc.xml	19 Dec 2005 12:36:15 -0000	1.137
+++ handbook-ppc.xml	27 Feb 2006 00:55:34 -0000	1.138
@@ -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-ppc.xml,v 1.137 2005/12/19 12:36:15 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.138 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <book link="handbook-ppc.xml">
 <title>Gentoo Linux PPC Handbook</title>
@@ -101,6 +101,9 @@
 <author title="Editor">
   <mail link="neysx@g.o">Xavier Neys</mail>
 </author>
+<author title="Editor">
+  <mail link="josejx@g.o">Joseph Jezak</mail>
+</author>
 <author title="Reviewer">
     <mail link="g2boojum@g.o">Grant Goodyear</mail>
 </author>
@@ -124,8 +127,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>4.3</version>
-<date>2005-12-19</date>
+<version>4.4</version>
+<date>2006-02-27</date>
 
 <part>
 <title>Installing Gentoo</title>



1.40      +23 -14    xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml?rev=1.40&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml?rev=1.40&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml.diff?r1=1.39&r2=1.40&cvsroot=gentoo

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.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- hb-install-alpha-medium.xml	29 Nov 2005 14:48:46 -0000	1.39
+++ hb-install-alpha-medium.xml	27 Feb 2006 00:55:34 -0000	1.40
@@ -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.39 2005/11/29 14:48:46 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml,v 1.40 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.10</version>
-<date>2005-11-29</date>
+<version>2.11</version>
+<date>2006-02-27</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="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>. 
+link="2006.0/index.xml">Gentoo 2006.0 Handbooks</uri>. 
 </p>
 
 <p>
@@ -112,8 +112,8 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-alpha-minimal-2005.1.iso</c>
-and takes up only 54 MB of diskspace. You can use this Installation CD to 
+The Minimal Installation CD is called <c>install-alpha-minimal-2006.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,11 +142,11 @@
 <body>
 
 <p>
-The Universal Installation CD is called <c>install-alpha-universal-2005.1.iso</c>
-and consumes the entire surface of a 650 MB 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 you are currently installing Gentoo on :)
+The Universal Installation CD is called <c>install-alpha-universal-2006.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
+you are currently installing Gentoo on :)
 </p>
 
 <table>
@@ -171,6 +171,7 @@
 
 </body>
 </subsection>
+<!-- No package CDs for Alpha - 2006.0
 <subsection>
 <title>Other CDs</title>
 <body>
@@ -190,7 +191,7 @@
 </p>
 
 </body>
-</subsection>
+</subsection>-->
 <subsection>
 <title>The Stage3 Tarball</title>
 <body>
@@ -225,7 +226,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/alpha/2005.1/installcd</path>
+Installation CDs are located in the <path>releases/alpha/2006.0/installcd</path>
 directory.
 </p>
 
@@ -237,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-2005.1.iso.md5</path>). You can check the MD5 
+<path>install-alpha-minimal-2006.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>
@@ -336,6 +337,14 @@
 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>
 </pre>
 
+<note>
+The default Alpha profile uses nptl and requires a 2.6 kernel. If your system
+cannot support nptl (or you do not want to use nptl), you should use the 2.4
+kernel. Alternatively, if you prefer to compile your system without nptl, you
+will be given the chance to select a stage built without nptl in <uri
+link="?part=1&amp;chap=5">Installing a Stage Tarball</uri>.
+</note>
+
 <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



1.44      +12 -12    xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml?rev=1.44&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml?rev=1.44&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml.diff?r1=1.43&r2=1.44&cvsroot=gentoo

Index: hb-install-amd64-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- hb-install-amd64-medium.xml	6 Jan 2006 09:50:09 -0000	1.43
+++ hb-install-amd64-medium.xml	27 Feb 2006 00:55:34 -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-amd64-medium.xml,v 1.43 2006/01/06 09:50:09 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml,v 1.44 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.12</version>
-<date>2005-11-29</date>
+<version>2.13</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -81,7 +81,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>.
+link="2006.0/index.xml">Gentoo 2006.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -114,7 +114,7 @@
 
 <p>
 The Minimal Installation CD is called
-<c>install-amd64-minimal-2005.1-r1.iso</c> and takes up only 67 MB of
+<c>install-amd64-minimal-2006.0.iso</c> and takes up only 45 MB of
 diskspace. You can use this Installation CD to install Gentoo, but always with
 a working Internet connection only.
 </p>
@@ -145,7 +145,7 @@
 
 <p>
 The Universal Installation CD is called
-<c>install-amd64-universal-2005.1-r1.iso</c> and takes up 393 MB. You can use
+<c>install-amd64-universal-2006.0.iso</c> and takes up 401 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 :)
@@ -225,7 +225,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/amd64/2005.1-r1/installcd</path>
+Installation CDs are located in the <path>releases/amd64/2006.0/installcd</path>
 directory.
 </p>
 
@@ -237,7 +237,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-amd64-minimal-2005.1-r1.iso.md5</path>). You can check the MD5 
+<path>install-amd64-minimal-2006.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>
@@ -501,23 +501,23 @@
 
 <p>
 If you want to view the documentation on the CD you can immediately run
-<c>links2</c> to read it:
+<c>links</c> to read it:
 </p>
 
 <pre caption="Viewing the on-CD documentation">
-# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i>
+# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
 </pre>
 
 <p>
 However, it is preferred that you use the online Gentoo Handbook as it will be
-more recent than the one provided on the CD. You can view it using <c>links2</c>
+more recent than the one provided on the CD. You can view it using <c>links</c>
 as well, but only after having completed the <e>Configuring your Network</e>
 chapter (otherwise you won't be able to go on the Internet to view the
 document):
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml</i>
 </pre>
 
 <p>



1.75      +5 -4      xml/htdocs/doc/en/handbook/hb-install-config.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-config.xml?rev=1.75&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-config.xml?rev=1.75&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-config.xml.diff?r1=1.74&r2=1.75&cvsroot=gentoo

Index: hb-install-config.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- hb-install-config.xml	19 Nov 2005 09:31:05 -0000	1.74
+++ hb-install-config.xml	27 Feb 2006 00:55:34 -0000	1.75
@@ -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-config.xml,v 1.74 2005/11/19 09:31:05 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.75 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.15</version>
-<date>2005-11-19</date>
+<version>2.17</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Filesystem Information</title>
@@ -80,7 +80,8 @@
 <p>
 Let us take a look at how we write down the options for the <path>/boot</path>
 partition. This is just an example, so if your architecture doesn't require a
-<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
+<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it
+verbatim.
 </p>
 
 <p>



1.31      +5 -5      xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml?rev=1.31&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml?rev=1.31&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml.diff?r1=1.30&r2=1.31&cvsroot=gentoo

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.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- hb-install-hppa-kernel.xml	8 Jan 2006 14:05:29 -0000	1.30
+++ hb-install-hppa-kernel.xml	27 Feb 2006 00:55:34 -0000	1.31
@@ -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.30 2006/01/08 14:05:29 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v 1.31 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>1.23</version>
-<date>2006-01-06</date>
+<version>1.24</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Timezone</title>
@@ -63,13 +63,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.12.2-pa2</c>. Your version may be
+kernel source points to <c>hppa-sources-2.6.15.1-pa4</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.12.2-pa2
+lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.15.1-pa4
 </pre>
 
 <p>



1.39      +16 -16    xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml?rev=1.39&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml?rev=1.39&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml.diff?r1=1.38&r2=1.39&cvsroot=gentoo

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.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- hb-install-hppa-medium.xml	29 Nov 2005 14:48:46 -0000	1.38
+++ hb-install-hppa-medium.xml	27 Feb 2006 00:55:34 -0000	1.39
@@ -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.38 2005/11/29 14:48:46 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml,v 1.39 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>1.29</version>
-<date>2005-11-29</date>
+<version>1.30</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -79,7 +79,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>.
+link="2006.0/index.xml">Gentoo 2006.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -111,8 +111,8 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-hppa-minimal-2005.1.iso</c> 
-and takes up only 65 MB of diskspace. You can use this Installation CD to 
+The Minimal Installation CD is called <c>install-hppa-minimal-2006.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>
 
@@ -141,11 +141,11 @@
 <body>
 
 <p>
-The Universal Installation CD is called <c>install-hppa-universal-2005.1.iso</c>
-and consumes the entire surface of a 650 MB 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 you are currently installing Gentoo on :)
+The Universal Installation CD is called <c>install-hppa-universal-2006.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
+you are currently installing Gentoo on :)
 </p>
 
 <table>
@@ -222,7 +222,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/2005.1/installcd</path> 
+Installation CDs are located in the <path>releases/hppa/2006.0/installcd</path> 
 directory.
 </p>
 
@@ -518,23 +518,23 @@
 
 <p>
 If you want to view the documentation on the CD you can immediately run
-<c>links2</c> to read it:
+<c>links</c> to read it:
 </p>
 
 <pre caption="Viewing the on-CD documentation">
-# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i>
+# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
 </pre>
 
 <p>
 However, it is preferred that you use the online Gentoo Handbook as it will be
-more recent than the one provided on the CD. You can view it using <c>links2</c>
+more recent than the one provided on the CD. You can view it using <c>links</c>
 as well, but only after having completed the <e>Configuring your Network</e>
 chapter (otherwise you won't be able to go on the Internet to view the
 document):
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml</i>
 </pre>
 
 <p>



1.13      +379 -66   xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?rev=1.13&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?rev=1.13&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml.diff?r1=1.12&r2=1.13&cvsroot=gentoo

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.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- hb-install-mips-bootloader.xml	19 Jan 2006 21:48:10 -0000	1.12
+++ hb-install-mips-bootloader.xml	27 Feb 2006 00:55:34 -0000	1.13
@@ -4,15 +4,73 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.12 2006/01/19 21:48:10 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.13 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>1.8</version>
-<date>2006-01-19</date>
+<version>1.10</version>
+<date>2006-02-27</date>
 
 <section id="sgi">
-<title>Silicon Graphics Machines -- Setting Up Arcboot</title>
+<title>Silicon Graphics Machines -- Setting Up arcboot/arcload</title>
+<subsection>
+<title>Which one?</title>
+<body>
+
+<p>
+On SGI machines, you have two options for bootloaders.  <c>arcboot</c> and
+<c>arcload</c>.  The table below lists the pros and cons for each bootloader.
+</p>
+
+<table>
+<tr>
+  <th> </th>
+  <th>arcboot</th>
+</tr>
+<tr>
+  <th>+</th>
+  <ti>
+    It can load off EXT2 and EXT3 partitions, so no need to store them in the
+    volume header
+  </ti>
+</tr>
+<tr>
+  <th>-</th>
+  <ti>
+    It doesn't work on Octane/Octane2, Origin 200/2000 or
+    Indigo2 Impact (R10000)
+  </ti>
+</tr>
+</table>
+
+<table>
+<tr>
+  <th> </th>
+  <th>arcload</th>
+</tr>
+<tr>
+  <th>+</th>
+  <ti>
+    It boots ALL Linux-compatable SGI systems
+  </ti>
+</tr>
+<tr>
+  <th>-</th>
+  <ti>
+    Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels
+    and config file to be placed in the volume header
+  </ti>
+</tr>
+</table>
+
+<note>
+The SGI volume header filenames are limited to 8 characters, and there may be no
+more than 16 files contained in a single volume header.
+</note>
+
+</body>
+</subsection>
+
 <subsection>
 <title>Installing arcboot</title>
 <body>
@@ -45,13 +103,22 @@
 header and loads kernels for us, and <c>dvhtool</c> which helps us put
 <c>arcboot</c> into the volume header.
 </p>
+
 <p>
-The magic binary we want, hides in <path>/usr/lib/arcboot</path> -- on IP22
-systems (Indy, Indigo 2, Challenge S), it'll be called
-<path>arcboot.ip22</path>.  Other systems should be similar.  We
-first copy this file into the volume header.
+The <c>arcboot</c> binary lurks in <path>/usr/lib/arcboot</path>.  The name of
+the binary depends on the machine it's compiled for.
 </p>
 
+<ul>
+  <li>
+    <c>arcboot.ip22</c>: The binary for Indy, Indigo2 (R4k) and Challenge S
+    systems
+  </li>
+  <li>
+    <c>arcboot.ip32</c>: The binary for O2 systems
+  </li>
+</ul>
+
 <pre caption="Installing arcboot into the volume header">
 # <i>dvhtool --unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i>
 </pre>
@@ -70,20 +137,12 @@
 </pre>
 
 <note>
-You'll notice that in my case, I've got two old kernels sitting around there,
-<path>linux</path> and <path>newlinux</path>.  This is a hangover from before we
-started using <c>arcboot</c>.  Their presence doesn't matter -- just so long as
-<c>arcboot</c> is present, everything is fine.
+You'll notice that in the example above, there are two old kernels sitting
+around, <path>linux</path> and <path>newlinux</path>.  This is a hangover from
+before we started using <c>arcboot</c>.  Their presence doesn't matter -- just
+so long as <c>arcboot</c> is present, everything is fine.
 </note>
 
-</body>
-</subsection>
-
-<subsection>
-<title>Configuring arcboot</title>
-
-<body>
-
 <p>
 If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that
 <c>arcboot</c> employs a similar syntax in its configuration file.  Bear in mind
@@ -92,9 +151,14 @@
 is to make sure <path>/boot</path> is an EXT2/3 partition and that there's a
 file called <path>arcboot.conf</path> inside the <path>/boot/etc</path>
 directory.  An example config can be found in
-<path>/etc/arcboot.conf.sample</path>
+<path>/etc/arcboot.conf.sample</path>.
 </p>
 
+<note>
+Adjust the paths accordingly if you
+don't have a separate <path>/boot</path> partition.
+</note>
+
 <pre caption="Putting arcboot.conf in its place">
 <comment>(Create the /boot/etc directory)</comment>
 # <i>mkdir /boot/etc</i>
@@ -111,9 +175,10 @@
 
 <p>
 You can then edit <path>/etc/arcboot.conf</path> to your own preference.
-Personally, I prefer to set up two kernel images: <path>new</path>, a freshly built
-image that may or may not work; and <path>working</path>, a proven trustworthy 
-kernel image.  My <path>arcboot.conf</path> looks a bit like this.
+One possible layout, is to set up two kernel images: <path>new</path>, a
+freshly built image that may or may not work; and <path>working</path>, a
+proven trustworthy kernel image.  The <path>arcboot.conf</path> for that
+setup looks a bit like this.
 </p>
 
 <pre caption="Example arcboot.conf">
@@ -121,11 +186,12 @@
 <comment>#</comment>
 <comment># copyright 2002 Guido Guenther &lt;agx@×××××××.org&gt;</comment>
 <comment>#</comment>
+<comment># known working version</comment>
 label=working
         image=/vmlinux
         append="root=/dev/sda3"
 
-<comment># backup version</comment>
+<comment># fresh "untested" version</comment>
 label=new
         image=/vmlinux-new
         append="root=/dev/sda3"
@@ -140,6 +206,129 @@
 
 </body>
 </subsection>
+
+<subsection>
+<title>Installing arcload</title>
+<body>
+
+<p>
+<c>arcload</c> was written for machines that require 64-bit kernels, and
+therefore can't use <c>arcboot</c> (which can't easily be compiled as a 64-bit
+binary).  It also works around peculiarities that arise when loading kernels
+directly from the volume header.  So, now you know what this is about, we
+can proceed with the installation:
+</p>
+
+<pre caption="Merging arcload and dvhtool">
+# <i>emerge arcload dvhtool</i>
+</pre>
+
+<p>
+Once this has finished, you should find the <c>arcload</c> binary in
+<path>/usr/lib/arcload</path>.  Now, two files exist:
+</p>
+
+<ul>
+  <li>
+    <c>sashARCS</c>: The 32-bit binary for Indy, Indigo2 (R4k), Challenge S
+    and O2 systems
+  </li>
+  <li>
+    <c>sash64</c>: The 64-bit binary for Octane/Octane2, Origin 200/2000 and
+    Indigo2 Impact systems
+  </li>
+</ul>
+
+<p>
+Use <c>dvhtool</c> to install the appropriate binary for your system into the
+volume header:
+</p>
+
+<pre caption="Placing arcload in the volume header">
+<comment>(Indy/Indigo2/Challenge S/O2 users)</comment>
+# <i>dvhtool --unix-to-vh /usr/lib/arcload/sashARCS sashARCS</i>
+
+<comment>(Indigo2 Impact/Octane/Octane2/Origin 200/Origin 2000 users)</comment>
+# <i>dvhtool --unix-to-vh /usr/lib/arcload/sash64 sash64</i>
+</pre>
+
+<note>
+You don't have to use the name <c>sashARCS</c> or <c>sash64</c>, unless you are
+installing to the volume header of a bootable CD.  For normal boot from
+hard-disk, you may name them something else if you wish.
+</note>
+
+<p>
+Now just use <c>dvhtool</c> to verify they are in the volume header.
+</p>
+
+<pre caption="Checking arcload is present in the volume header">
+# <i>dvhtool --print-volume-directory</i>
+----- directory entries -----
+Entry #0, name "sash64", start 4, bytes 55859
+#
+</pre>
+
+<p>
+Now, the <c>arc.cf</c> file has a C-like syntax.  For the full detail on how
+one configures it, see the <uri
+link="http://www.linux-mips.org/wiki/Arcload">arcload page on the
+Linux/MIPS wiki</uri>.  In short, you define a number of options, which you
+enable and disable at boot time using the <c>OSLoadFilename</c> variable.
+</p>
+
+<pre caption="An example arc.cf">
+<comment># ARCLoad Configuration</comment>
+
+<comment># Some default settings...</comment>
+append  "root=/dev/sda3";
+append  "ro";
+append  "console=ttyS0,9600";
+
+<comment># Our main definition.  ip28 may be changed if you wish.</comment>
+ip28 {
+        <comment># Definition for a "working" kernel</comment>
+        <comment># Select this by setting OSLoadFilename="ip28(working)"</comment>
+        working {
+                description     "SGI Indigo2 Impact R10000\n\r";
+                image system    "/working";
+        }
+
+        <comment># Definition for a "new" kernel</comment>
+        <comment># Select this by setting OSLoadFilename="ip28(new)"</comment>
+        new {
+                description     "SGI Indigo2 Impact R10000 - Testing Kernel\n\r";
+                image system    "/new";
+        }
+
+        <comment># For debugging a kernel</comment>
+        <comment># Select this by setting OSLoadFilename="ip28(working,debug)"</comment>
+        <comment># or OSLoadFilename="ip28(new,debug)"</comment>
+        debug {
+                description     "Debug console";
+                append          "init=/bin/bash";
+        }
+}
+</pre>
+
+<p>
+This is then placed in the volume header with <c>sash64</c> (or
+<c>sashARCS</c>) as shown below.  Kernels also get placed in the volume header.
+</p>
+
+<pre caption="Placing arc.cf and kernel in the volume header">
+# <i>dvhtool --unix-to-vh arc.cf arc.cf</i>
+# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i>
+</pre>
+
+<p>
+With this done, now all that's left is to set some options in the PROM.  See the
+section on <uri link="#reboot">Rebooting the System</uri>.
+</p>
+
+</body>
+</subsection>
+
 </section>
 
 <section id="cobalt">
@@ -156,9 +345,9 @@
 
 <ul>
   <li>
-    There's a 675kB 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 totally out
-    of the question.
+    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
+    totally out of the question.
   </li>
   <li>
     64-bit kernels are not supported by the stock firmware (although these are
@@ -254,41 +443,40 @@
 
 <p>
 It is also possible to ask a question, such as which kernel &amp; configuration
-you'd like to boot, with a default timeout.  This is the configuration I use on
-my Cobalt server:
+you'd like to boot, with a default timeout.  This configuration does exactly
+this, asks the user which kernel they wish to use, and executes the chosen
+image.  <path>vmlinux.gz.new</path> and <path>vmlinux.gz.working</path> may be
+actual kernel images, or just symlinks pointing to the kernel images on that
+disk.  The <c>50</c> argument to <c>select</c> specifies that it should proceed
+with the first option ("Working") after 50/10 seconds.
 </p>
 
-<impo>
-Please note that you need to be using CoLo v1.12 or v1.13 to use the <c>menu</c>
-command. The following example won't work with v1.11.
-</impo>
-
-<impo>
-The <c>menu</c> command was replaced by the <c>select</c> command in CoLo v1.14.
-If you've installed a later version by hand, have a look at
-<path>menu.colo</path> in the <path>examples</path> subdirectory of the CoLo
-distribution.
-</impo>
-
 <pre caption="Menu-based configuration">
 <comment>#:CoLo:#</comment>
 
 lcd "Mounting hda1"
 mount hda1
-menu "Which Kernel?" 50 Working working New new
-lcd "Loading Linux" {menu-option}
-load /kernel.gz.{menu-option}
+select "Which Kernel?" 50 Working New
+
+goto {menu-option}
+var image-name vmlinux.gz.working
+goto 3f
+@var image-name vmlinux.gz.working
+goto 2f
+@var image-name vmlinux.gz.new
+
+@lcd "Loading Linux" {image-name}
+load /{image-name}
 lcd "Booting..."
 execute root=/dev/hda5 ro console=ttyS0,115200
 boot
 </pre>
 
 <p>
-The above script asks the user which kernel he/she would like to boot (either
-New or Working), then loads <path>vmlinux.gz.new</path> or
-<path>vmlinux.gz.working</path> depending on the selection.  If a selection is
-not made within 5 seconds (50/10ths of a second) it boots the first option.
+See the documentation in <path>/usr/share/doc/colo-VERSION</path> for more
+details.
 </p>
+
 </body>
 
 </subsection>
@@ -307,7 +495,7 @@
 </p>
 
 <note>
-Those who do have the luxury of a supported framebuffer may skip this section if
+Those who do have the luxury of a supported video chipset may skip this section if
 they wish.
 </note>
 
@@ -395,10 +583,10 @@
 
 <note>
 <e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI
-PROM so that it boots <c>arcboot</c> off disk and loads Linux.  This is not
-applicable to the setup of Cobalt servers.  In fact, all your work is done --
-there is no configuration needed for the first boot up, you can skip to the next
-section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo
+PROM so that it boots <c>arcboot</c>/<c>arcload</c> off disk and loads Linux.
+This is not applicable to the setup of Cobalt servers.  In fact, all your work
+is done -- there is no configuration needed for the first boot up, you can skip
+to the next section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo
 Installation</uri>
 </note>
 
@@ -408,14 +596,29 @@
 <section>
 <title>Tweaking the SGI PROM</title>
 <subsection>
+<title>Setting generic PROM settings</title>
 <body>
 
 <p>
+Now that you've installed the bootloader, you're ready to reboot the machine.
+</p>
+
+<pre caption="Rebooting">
+<comment>(Exit the chroot environment)</comment>
+# <i>exit</i>
+
+<comment>(Unmount the drives)</comment>
+# <i>umount /gentoo/boot</i>
+# <i>umount /gentoo</i>
+
+<comment>(Reboot)</comment>
+# <i>reboot</i>
+</pre>
+
+<p>
 When you are rebooted, go to the <e>System Maintenance Menu</e> and select 
-<e>Enter Command Monitor</e> (<c>5</c>). If you want to test your new Gentoo 
-installation, you can just run <c>boot -f &lt;kernel name&gt;</c>. To have your 
-system permanently boot into the Gentoo installation, you need to set some 
-variables in the SGI PROM: 
+<e>Enter Command Monitor</e> (<c>5</c>) like you did when you netbooted the
+machine.
 </p>
 
 <pre caption="Configuring the PROM to Boot Gentoo">
@@ -428,6 +631,46 @@
 Option? <i>5</i>
 Command Monitor.  Type "exit" to return to the menu.
 
+<comment>(Set some options which are common for both arcload and arcboot)</comment>
+
+<comment>(Provide the location of the Volume Header)</comment>
+&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
+
+<comment>(Automatically boot Gentoo)</comment>
+&gt;&gt; <i>setenv AutoLoad Yes</i>
+
+<comment>(Set the timezone)</comment>
+&gt;&gt; <i>setenv TimeZone EST5EDT</i>
+
+<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
+&gt;&gt; <i>setenv console d1</i>
+
+<comment>(Setting the serial console baud rate.  This is optional, 9600 is the           )
+(default setting, although one may use rates up to 38400 if that is desired.   )</comment>
+&gt;&gt; <i>setenv dbaud 9600</i>
+</pre>
+
+<p>
+Now, the next settings depend on how you are booting the system.
+</p>
+
+</body>
+</subsection>
+
+<subsection>
+<title>Settings for direct volume-header booting</title>
+<body>
+
+<p>
+This is covered here for completeness.  It's recommended that users look into
+installing <c>arcboot</c> or <c>arcload</c> instead.
+</p>
+
+<note>
+This only works on the Indy, Indigo2 (R4k) and Challenge S.
+</note>
+
+<pre caption="PROM settings for booting off the volume header">
 <comment>(&lt;root device&gt; = Gentoo's root partition, e.g. /dev/sda3)</comment>
 &gt;&gt; <i>setenv OSLoadPartition &lt;root device&gt;</i>
 
@@ -437,21 +680,91 @@
 
 <comment>(Declare the kernel parameters you want to pass)</comment>
 &gt;&gt; <i>setenv OSLoadOptions &lt;kernel parameters&gt;</i>
+</pre>
 
-<comment>(Provide the location of the Volume Header)</comment>
-&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
+<p>
+If you wish to try a kernel without messing with kernel parameters, you may do
+so using the <c>boot -f</c> PROM command:
+</p>
 
-<comment>(Automatically boot Gentoo)</comment>
-&gt;&gt; <i>setenv AutoLoad Yes</i>
+<pre caption="Booting without changing environment variables">
+<comment>(Booting a kernel, "new", with additional options)</comment>
+# <i>boot -f new root=/dev/sda3 ro</i>
+</pre>
 
-<comment>(Set the timezone)</comment>
-&gt;&gt; <i>setenv TimeZone EST5EDT</i>
+</body>
+</subsection>
 
-<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
-&gt;&gt; <i>setenv console d1</i>
+<subsection>
+<title>Settings for arcload</title>
+<body>
+
+<p>
+<c>arcload</c> uses the <c>OSLoadFilename</c> option to specify which options to
+set from <path>arc.cf</path>.  The configuration file is essentially a script,
+with the top-level blocks defining boot images for different systems, and inside
+that, optional settings.  Thus, setting <c>OSLoadFilename=mysys(serial)</c>
+pulls in the settings for the <c>mysys</c> block, then sets further options
+overridden in <c>serial</c>.
+</p>
+
+<p>
+In the example file above, we have one system block defined, <c>ip28</c> with
+<c>working</c>, <c>new</c> and <c>debug</c> options available.  We define our
+PROM variables as so:
+</p>
+
+<pre caption="PROM settings for using arcload">
+<comment>(Select arcload as the bootloader:- sash64 or sashARCS)</comment>
+&gt;&gt; setenv OSLoader sash64
+
+<comment>(Use the "working" kernel image, defined in "ip28" section of arc.cf)</comment>
+&gt;&gt; setenv OSLoadFilename ip28(working)
+</pre>
+
+</body>
+</subsection>
+
+<subsection>
+<title>Settings for arcboot</title>
+<body>
+
+<p>
+<c>arcboot</c> loads its configuration file and kernels from your
+<path>/boot</path> partition, which needs to be formatted either EXT2 or EXT3.
+Thus <c>OSLoadPartition</c> needs to point to that partition.  <c>OSLoader</c>
+should point to the <c>arcboot</c> binary in the volume header, and
+<c>OSLoadFilename</c> is the image name being used.
+</p>
+
+<pre caption="PROM settings for using arcboot">
+<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 -- sda1)</comment>
+&gt;&gt; <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i>
+
+<comment>(Use arcboot as the bootloader)</comment>
+&gt;&gt; <i>setenv OSLoader arcload</i>
+
+<comment>(Which boot image in arcboot.conf to load)</comment>
+&gt;&gt; <i>setenv OSLoadFilename working</i>
 </pre>
 
 <p>
+When testing kernels via <c>arcboot</c> you can specify an alternate image like
+so (where <c>new</c> is the alternate image):
+</p>
+
+<pre caption="Specifying an alternate image">
+# <i>boot new</i>
+</pre>
+
+</body>
+</subsection>
+
+<subsection>
+<title>All Done</title>
+<body>
+
+<p>
 Now you're ready to enjoy Gentoo! Boot in your Gentoo installation and finish 
 up with <uri link="?part=1&amp;chap=11">Finalizing your Gentoo 
 Installation</uri>.



1.18      +12 -3     xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml?rev=1.18&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml?rev=1.18&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml.diff?r1=1.17&r2=1.18&cvsroot=gentoo

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.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- hb-install-mips-disk.xml	14 Dec 2005 00:22:34 -0000	1.17
+++ hb-install-mips-disk.xml	27 Feb 2006 00:55:34 -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-disk.xml,v 1.17 2005/12/14 00:22:34 vanquirius Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v 1.18 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>1.11</version>
-<date>2005-10-02</date>
+<version>1.13</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -223,6 +223,15 @@
 with each 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



1.20      +216 -74   xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml?rev=1.20&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml?rev=1.20&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml.diff?r1=1.19&r2=1.20&cvsroot=gentoo

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.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-install-mips-kernel.xml	8 Jan 2006 14:05:29 -0000	1.19
+++ hb-install-mips-kernel.xml	27 Feb 2006 00:55:34 -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-mips-kernel.xml,v 1.19 2006/01/08 14:05:29 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-kernel.xml,v 1.20 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>1.15</version>
-<date>2006-01-06</date>
+<version>1.16</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Timezone</title>
@@ -44,34 +44,75 @@
 </p>
 
 <p>
-MIPS-based systems can choose from <c>mips-sources</c> (the default kernel
-source for the MIPS architecture) and <c>mips-prepatch-sources</c> (prerelease
-kernel tree).
+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.
 </p>
 
-<p>
-Choose your kernel source and install it using <c>emerge</c>.  Of course
-substitute with your choice of sources, this is merely an example.  The
-<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other
-dependencies at this point. <c>USE="symlink"</c> is not necessary for a new
-install, but ensures proper creation of the <path>/usr/src/linux</path>
-symlink.
-</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>
 
 <note>
-Special patches are needed to make a kernel work on Cobalt servers.  The
-<c>cobalt</c> USE flag must be defined in order to grab the necessary patches
-and apply them.
+The <c>USE="-doc"</c> disables the generation of kernel API documentation, which
+would otherwise pull in numerous dependancies not required for this step.
 </note>
 
-<pre caption="Installing a kernel source">
-<comment>(For SGI machines)</comment>
-# <i>USE="-doc symlink" emerge mips-sources</i>
-
-<comment>(For Cobalt machines)</comment>
-# <i>mkdir -p /etc/portage</i>
+<pre caption="Setting USE flags and merging kernel sources...">
+<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>
-# <i>USE="-doc symlink" emerge mips-sources</i>
+
+<comment>(Unpack &amp; install the kernel sources)</comment>
+# <i>USE="-doc" 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 gcc-mips64</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="Changing Profiles and installing gcc-mips64...">
+<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 gcc-mips64</i>
 </pre>
 
 <p>
@@ -83,7 +124,18 @@
 
 <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.4.24
+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>
 </pre>
 
 <p>
@@ -101,53 +153,107 @@
 
 <p>
 Previously, we went through the manual configuration of how to set up the kernel
-sources.  Instead, we have uploaded a number of sample configurations which you
-can base your configuration upon.  Simply click on the closest option that
-matches your system and kernel version.  You may also find other configuration
-samples at the URLs mentioned below.
+sources.  This has become impractical with the number of systems we now support.
+This section details various sources for sample kernel configurations.
+</p>
+
+</body>
+</subsection>
+<subsection>
+<title>Using sample configurations in the kernel source</title>
+<body>
+
+<p>
+Many of the systems supported have sample .configs hiding in amongst the kernel
+source.  Not all systems have configs distributed in this way.  Those that do,
+can be configured using the commands mentioned in the table below.
 </p>
 
 <table>
-  <tr>
-    <th>System</th>
-    <th>Kernel Version</th>
-  </tr>
-  <tr>
-    <ti>SGI IP22 (Indy, Indigo 2, Challenge S)</ti>
-    <ti>
-      <uri link="http://www.longlandclan.hopto.org/~stuartl/mips-linux/sgi/ip22/config/2.4.29-mipscvs-20050130.gz">2.4.29</uri>
-    </ti>
-  </tr>
-  <tr>
-    <ti>Cobalt Qube/Raq 2800</ti>
-    <ti>
-      <uri link="http://dev.gentoo.org/~kumba/mips/cobalt/kernel/cobalt-2605.config">2.6.5</uri>
-      <uri link="http://dev.gentoo.org/~kumba/mips/cobalt/kernel/cobalt-2606.config">2.6.6</uri>
-      <uri link="http://dev.gentoo.org/~kumba/mips/cobalt/kernel/cobalt-config-2609">2.6.9</uri>
-    </ti>
-  </tr>
+<tr>
+  <th>System</th>
+  <th>Configure command</th>
+</tr>
+<tr>
+  <ti>Cobalt Servers</ti>
+  <ti><c>make cobalt_defconfig</c></ti>
+</tr>
+<tr>
+  <ti>Indy, Indigo2 (R4k), Challenge S</ti>
+  <ti><c>make ip22_defconfig</c></ti>
+</tr>
+<tr>
+  <ti>Origin 200/2000</ti>
+  <ti><c>make ip27_defconfig</c></ti>
+</tr>
+<tr>
+  <ti>Indigo2 Impact (R10k)</ti>
+  <ti>
+    <c>make ip28_defconfig</c> (requires <c>mips-sources-2.6.14.5</c> or
+    later)
+  </ti>
+</tr>
+<tr>
+  <ti>O2</ti>
+  <ti><c>make ip32_defconfig</c></ti>
+</tr>
 </table>
 
-<ul>
-  <li>
-    IP22 (Indy, Indigo2, Challenge S) Configurations:
-    <uri link="http://www.longlandclan.hopto.org/~stuartl/mips-linux/sgi/ip22/config">
-      http://www.longlandclan.hopto.org/~stuartl/mips-linux/sgi/ip22/config
-    </uri>
-  </li>
-  <li>
-    Cobalt Server Configurations:
-    <uri link="http://dev.gentoo.org/~kumba/mips">
-      http://dev.gentoo.org/~kumba/mips
-    </uri>
-  </li>
-</ul>
+</body>
+</subsection>
 
-<note>
-More kernel configuration examples can be found on the Gentoo/MIPS Hardware
-Support Database, which is located at
+<subsection>
+<title>Using the running kernel config from the installation media</title>
+<body>
+
+<p>
+All of the Gentoo installation images provide a kernel config option as part of
+the image itself, accessible as <path>/proc/config.gz</path>.  This may be used
+in many cases.  It is best though if your kernel source matches closely, the
+kernel that is currently running.  To extract it, simply run it through
+<c>zcat</c> as shown below.
+</p>
+
+<pre caption="Extracting .config from /proc/config.gz">
+# <i>zcat /proc/config.gz > .config</i>
+</pre>
+
+<impo>
+This kernel config is set up for a netboot image.  That
+is, it will expect to find a root filesystem image somewhere nearby, either as a
+directory for initramfs, or a loopback device for initrd.  When you run <c>make
+menuconfig</c> below, don't forget to go into General Setup and disable the
+options for initramfs.
+</impo>
+
+</body>
+</subsection>
+
+<subsection>
+<title>The Hardware Compatability Database</title>
+<body>
+
+<p>
+As an aid to users in finding working settings, a hardware compatability
+database was set up.  This database lists the support for various MIPS devices,
+and allows users to contribute kernel configurations that are known to work.
+The address for this site is
 <uri>http://stuartl.longlandclan.hopto.org/gentoo/mips</uri>.
-</note>
+</p>
+
+<p>
+If you find this service useful, you're welcome to contribute your notes and
+.config files so that others may benefit from your experience.  It should be
+noted however that there is no guarantee that any of the configuration files
+downloaded from this site will work.
+</p>
+
+</body>
+</subsection>
+
+<subsection>
+<title>Customising the configuration for your needs.</title>
+<body>
 
 <p>
 Once you have found a configuration, download it into your kernel source
@@ -164,6 +270,15 @@
 # <i>make menuconfig</i>
 </pre>
 
+<impo>
+In the Kernel Hacking section, there is an option named "Are You Using A Cross
+Compiler?".  This tells the kernel Makefiles to prepend "<c>mips-linux-</c>" (or
+<c>mipsel-linux</c> ... etc) to <c>gcc</c> and <c>as</c> commands when compiling
+the kernel.  This should be turned off, even if cross-compiling.  Instead, if
+you do need to call a cross-compiler, specify the prefix using the
+<c>CROSS_COMPILE</c> variable as shown in the next section.
+</impo>
+
 </body>
 </subsection>
 <subsection id="compiling">
@@ -175,12 +290,40 @@
 the configuration and start the compilation process:
 </p>
 
+<note>
+On 64-bit machines, you need to specify
+<c>CROSS_COMPILE=mips64-unknown-linux-gnu-</c> (or <c>mips64el-...</c> if on
+a little-endian system) to use the 64-bit compiler.
+</note>
+
 <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.4 kernel only)</comment>
+# <i>make dep</i>
+
+<comment>(2.4 and 2.6 kernels -- compiling natively)</comment>
+# <i>make vmlinux modules modules_install</i>
 
-<comment>(For 2.6 kernel)</comment>
-# <i>make &amp;&amp; make 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>
+# <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>
+# <i>make vmlinux modules CROSS_COMPILE=mips64-unknown-linux-gnu-</i>
+# <i>make modules_install INSTALL_MOD_PATH=/somewhere</i>
+</pre>
+
+<impo>
+When compiling a 64-bit kernel for the Indy, Indigo2 (R4k), Challenge S and O2,
+use the <c>vmlinux.32</c> target instead of <c>vmlinux</c>.  Otherwise, your
+machine will not be able to boot.  This is to work around the PROM not
+understanding the ELF64 format.
+</impo>
+
+<pre caption="Using the vmlinux.32 target">
+# <i>make vmlinux.32</i>
+<comment>(This will create vmlinux.32 -- which is your final kernel)</comment>
 </pre>
 
 <p>
@@ -190,15 +333,14 @@
 
 <note>
 On Cobalt servers, the bootloader will expect to see a compressed kernel image.
-Remember to <c>gzip -9</c> the file once it is in <path>/boot</path>. In the
-following example, replace <path>&lt;kernel-version&gt;</path> with your kernel
-version.
+Remember to <c>gzip -9</c> the file once it is in <path>/boot</path>.
 </note>
 
 <pre caption="Installing the kernel">
-# <i>cp vmlinux /boot/&lt;kernel-version&lt;</i>
+# <i>cp vmlinux /boot/kernel-2.6.13.4</i>
+
 <comment>(Cobalt Servers -- Compressing the kernel image)</comment>
-# <i>gzip -9v /boot/&lt;kernel-version&lt;</i>
+# <i>gzip -9v /boot/kernel-2.6.13.4</i>
 </pre>
 
 <!--



1.17      +153 -257  xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml?rev=1.17&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml?rev=1.17&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml.diff?r1=1.16&r2=1.17&cvsroot=gentoo

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.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- hb-install-mips-medium.xml	11 Nov 2005 17:27:15 -0000	1.16
+++ hb-install-mips-medium.xml	27 Feb 2006 00:55:34 -0000	1.17
@@ -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.16 2005/11/11 17:27:15 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-medium.xml,v 1.17 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>1.11</version>
-<date>2005-11-11</date>
+<version>1.13</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -30,6 +30,14 @@
 
 <table>
 <tr>
+  <th>CPU <e>(Big Endian port)</e></th>
+  <ti>MIPS3, MIPS4, MIPS5 or MIPS64-class CPU</ti>
+</tr>
+<tr>
+  <th>CPU <e>(Little Endian port)</e></th>
+  <ti>MIPS4, MIPS5 or MIPS64-class CPU</ti>
+</tr>
+<tr>
   <th>Memory</th>
   <ti>64 MB</ti>
 </tr>
@@ -107,6 +115,7 @@
       <uri link="http://www.linux-mips.org/wiki/index.php/R5000">RM5000</uri>,
       <uri link="http://www.linux-mips.org/wiki/index.php/RM7000">RM7000</uri>
       <uri link="http://www.linux-mips.org/wiki/index.php/R8000">R8000</uri>,
+      R9000,
       <uri link="http://www.linux-mips.org/wiki/index.php/R10000">R10000</uri>,
       <uri link="http://www.linux-mips.org/wiki/index.php/R10000">R12000</uri>,
       <uri link="http://www.linux-mips.org/wiki/index.php/R10000">R14000</uri>,
@@ -120,8 +129,36 @@
       None As Yet
     </ti>
   </tr>
+  <tr>
+    <ti>MIPS32</ti>
+    <ti>32-bit</ti>
+    <ti>
+      AMD Alchemy series, 4kc, 4km, many others...
+    </ti>
+  </tr>
+  <tr>
+    <ti>MIPS64</ti>
+    <ti>64-bit</ti>
+    <ti>
+      Broadcom SiByte SB1, 5kc ... etc...
+    </ti>
+  </tr>
 </table>
 
+<note>
+The <c>MIPS5</c> ISA level was designed by Silicon Graphics back in 1994, but
+never actually got used in a real life CPU.  It lives on as part of the
+<c>MIPS64</c> ISA.
+</note>
+
+<note>
+The <c>MIPS32</c> and <c>MIPS64</c> ISAs are a common source of confusion.  The
+<c>MIPS64</c> ISA level is actually a superset of the <c>MIPS5</c> ISA, so it
+includes all instructions from <c>MIPS5</c> and earlier ISAs.  <c>MIPS32</c> is
+the 32-bit subset of <c>MIPS64</c>, it exists because most applications only
+require 32-bit processing.
+</note>
+
 <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
@@ -222,8 +259,8 @@
 <p>
 In this section, we'll cover what you need in order to successfully network boot
 a Silicon Graphics workstation or Cobalt Server appliance.  This is just a brief
-guide, it is not intended to be thorough, for more information, I recommend
-reading the <uri link="/doc/en/diskless-howto.xml">Diskless
+guide, it is not intended to be thorough, for more information, it is
+recommended that you read the <uri link="/doc/en/diskless-howto.xml">Diskless
 HOWTO</uri>.
 </p>
 
@@ -268,12 +305,9 @@
 SGI machines use a MiniDIN 8 connector for the serial ports.  Apparently Apple
 modem cables work just fine as serial cables, but with Apple machines being
 equipped with USB &amp; internal modems, these are getting harder to
-find.  A number of sites describe how to make these cables (Google is your
-friend).  The following site describes making such a cable.  It's in German,
-but has a reasonably good wiring diagram.
-<uri link="http://www.arbeitsplatzvernichtung-durch-outsourcing.de/marty44/sgihard.html">
-  http://www.arbeitsplatzvernichtung-durch-outsourcing.de/marty44/sgihard.html
-</uri>
+find.  One wiring diagram is available from the <uri
+link="http://www.linux-mips.org/wiki/Serial_Cable">Linux/MIPS Wiki</uri>, and
+most electronics stores should stock the plugs required.
 </note>
 
 <note>
@@ -302,7 +336,7 @@
 
 <p>
 Okay, so you've got your bits and pieces together, now to set everything up.  As
-I mentioned earlier -- this is not a complete guide, this is a bare-bones config
+mentioned earlier -- this is not a complete guide, this is a bare-bones config
 that will just get things rolling.  You can either use this when starting a
 setup from scratch, or use the suggestions to amend your existing setup to
 support netbooting.
@@ -315,6 +349,12 @@
 separate machine to the DHCP server if desired.
 </p>
 
+<warn>
+The Gentoo/MIPS Team cannot help you with setting up other operating
+systems as netboot servers.  If you choose a different OS, it is assumed you
+know what you're doing.
+</warn>
+
 <p>
 First Step -- configuring DHCP.  In order for the ISC DHCP daemon to respond
 to BOOTP requests (as required by the SGI &amp; Cobalt BOOTROM) you need to
@@ -361,10 +401,9 @@
 </p>
 
 <p>
-Next Step -- Setting up TFTP server.  For the purposes of this guide, I'll
-restrict this to the tftp-hpa TFTP daemon.  I use this myself on SGI machines,
-Cobalt servers and PXE clients alike without any hassle.  Installation and
-configuration is fairly straightforward:
+Next Step -- Setting up TFTP server.  It is recommended that you use
+<c>tftp-hpa</c> as it is the only TFTP daemon known to work correctly.  Proceed
+by installing it as shown below.
 </p>
 
 <pre caption="Installing tftp-hpa">
@@ -372,15 +411,9 @@
 </pre>
 
 <p>
-Now, I personally like to move my <path>/tftpboot</path> directory into
-<path>/home</path> where I have more space.  This is totally optional, and can
-be configured through the <path>/etc/conf.d/in.tftpd</path> file.  For the
-purposes of this guide, I'll assume you've left it in the default place.
-</p>
-
-<p>
-Now that everything is configured, we're ready to move onto the fun bit --
-tayloring our config to suit the machine we wish to netboot.
+This will create <path>/tftproot</path> for you to store the netboot images.
+You may move this elsewhere if you wish.  For the purposes of this guide, it is
+assumed that you have left it in the default location.
 </p>
 
 </body>
@@ -458,16 +491,12 @@
 <body>
 
 <p>
-Once you have downloaded the file, simply place it in your
-<path>/tftpboot</path> directory.  Then edit your
-<path>/etc/dhcp/dhcpd.conf</path> and add the entry for your SGI client.
+Once you have downloaded the file, place the decompressed image file in your
+<path>/tftproot</path> directory.  (Use <c>bzip2 -d</c> to decompress)
+Then edit your <path>/etc/dhcp/dhcpd.conf</path> and add the entry for your
+SGI client.
 </p>
 
-<note>
-You may need to create the <path>/tftpboot</path> directory if it isn't
-there already.
-</note>
-
 <pre caption="dhcpd.conf snippet for SGI Workstation">
 subnet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx {
   <comment># ... usual stuff here ...</comment>
@@ -625,25 +654,18 @@
 
 <ul>
   <li>
-    dhcpd is giving the SGI Machine an IP Address.  You should see some
+    <c>dhcpd</c> is giving the SGI Machine an IP Address.  You should see some
     messages about a BOOTP request in the system logs.  <c>tcpdump</c> is also
     useful here.
   </li>
   <li>
     Permissions are set properly in your tftp folder (typically 
-    <path>/tftpboot</path> -- should be world readable)
+    <path>/tftproot</path> -- should be world readable)
   </li>
   <li>
     Check system logs to see what the tftp server is reporting (errors
     perhaps)
   </li>
-<!--
-  I really think this tip can go...
-  
-  <li>
-    Pray to a Tux plushie (this may or may not work, and is not an officially
-    supported troubleshooting technique)
-  </li>-->
 </ul>
 
 <p>
@@ -664,6 +686,82 @@
 </section>
 
 <section>
+<title>Alternative Method: Gentoo/MIPS SGI LiveCD</title>
+<subsection>
+<title>Overview</title>
+<body>
+
+<p>
+On Silicon Graphics machines, it is possible to boot from a CD in order to
+install operating systems.  (This is how one installs IRIX for instance)
+Recently, images for such bootable CDs to install Gentoo have been made
+possible.  These CDs are designed to work in the same way.
+</p>
+
+<p>
+At the moment the Gentoo/MIPS Live CD will only work on the SGI Indy,
+Indigo 2 and O2 workstations equipped with R4000 and R5000-series CPUs, however
+other platforms may be possible in future.
+</p>
+
+<p>
+You can find the Live CD images for download on your favourite Gentoo Mirror
+under the <path>experimental/mips/livecd</path> directory.
+</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.
+</warn>
+
+</body>
+
+</subsection>
+
+<subsection>
+<title>Burning a Live CD</title>
+<body>
+
+<p>
+An important thing to note, the SGI PROM does not understand the ISO9660 format,
+nor does it know anything about the El Torito boot standard.  These CD images
+are constructed as a SGI disklabel with the boot image in the volume header like
+a hard drive.  Therefore, care must be taken when burning the CD image.
+</p>
+
+<p>
+Below is an example command that assumes 24x burning speed on an IDE burner.  If
+you have a SCSI burner for instance, you may want to adjust the <c>dev</c>
+statement as appropriate.  Likewise with the <c>speed</c> option - if you
+strike troubles, you might want to try dropping the speed.
+</p>
+
+<pre caption="Burning using cdrecord">
+# <i>bzip2 -d mips-livecd-prototype-rc2-20041027.img.bz2</i>
+# <i>cdrecord -vv -pad speed=24 dev=ATAPI:0,0,0 -tao mips-livecd-prototype-rc2-20041027.img</i>
+</pre>
+
+<note>
+It may be possible to burn these CDs under Windows, assuming your burning
+program just blindly burns the image as is.  However, no one has succeeded in
+making a working CD this way to date.
+</note>
+
+<note>
+If you don't know what to put as your <c>dev</c> argument, run <c>cdrecord
+-scanbus</c> as root - this will tell you where your burner is located.
+</note>
+
+</body>
+</subsection>
+</section>
+
+<section>
 <title>Netbooting on Cobalt Servers</title>
 <subsection>
 <body>
@@ -681,17 +779,7 @@
 buttons whilst powering the unit on.  The machine will then attempt to obtain an
 IP number via BOOTP, mount the <path>/nfsroot</path> directory from the server via
 NFS, then try to download and boot the file <path>vmlinux_raq-2800.gz</path>
-which it assumes to be a standard ELF binary.
-</p>
-
-<p>
-Unfortunately, the Cobalt BOOTROM does not give us any say in this procedure,
-so the file HAS to reside in <path>/nfsroot</path> directory, and must be less
-than 675kB in size.  In this guide, we'll set up 
-<uri link="http://www.colonel-panic.org/cobalt-mips/">CoLo</uri> to allow us to
-boot larger kernels than this limit.  CoLo also supports embedded ramdisks,
-therefore ridding the need of a full root filesystem sitting in
-<path>/nfsroot</path>.
+(depending on the model) which it assumes to be a standard ELF binary.
 </p>
 
 </body>
@@ -703,52 +791,18 @@
 
 <p>
 Inside
-<uri link="http://dev.gentoo.org/~kumba/mips/cobalt/netboot/">
-http://dev.gentoo.org/~kumba/mips/cobalt/netboot/</uri>
+<uri link="http://dev.gentoo.org/~redhatter/mips/cobalt/netboots/">
+http://dev.gentoo.org/~redhatter/mips/cobalt/netboots/</uri>
 you'll find the necessary boot images for getting a Cobalt up
 and running.  The files you need will have the name
-<path>cobalt-netboot-YYYYMMDD.img.gz</path> -- select the most recent one and
-place it in your <path>/nfsroot</path> directory.  For convenience, rename the
-file to <path>gentoo-cobalt.img.gz</path> -- I'll assume that you have done
-this.
-</p>
-
-<p>
-Once that is done, head over to
-<uri link="http://www.colonel-panic.org/cobalt-mips/">
-http://www.colonel-panic.org/cobalt-mips/</uri> and
-download the latest release of the CoLo bootloader.  Untar this somewhere
-convenient.  Inside the <path>colo-1.XX/binaries</path> directory created,
-you should find under a file named <path>colo-chain.elf</path>.  Gzip this
-file up and place it in <path>/nfsroot</path> calling it
-<path>vmlinux_raq-2800.gz</path>. Also, in some cases, you will need to create a
-symbolic link called <path>boot</path> that points back to
-<path>/nfsroot</path>. You can do this in one hit using these commands:
+<path>nfsroot-KERNEL-COLO-DATE-cobalt.tar</path> -- select the most recent one and
+unpack it to <path>/</path> as shown below:
 </p>
 
-<note>
-Please note, the RaQ1 and Qube 2700 look for <path>vmlinux.gz</path> rather than
-<path>vmlinux_raq-2800.gz</path>.
-</note>
-
-<pre caption="Putting CoLo in the nfsroot">
-# <i>tar -xzvf colo-1.XX.tar.gz</i>
-# <i>cd colo-1.XX/binaries</i>
-
-<comment>(For Qube 2800, RaQ2, etc)</comment>
-# <i>gzip -9vc colo-chain.elf &gt; /nfsroot/vmlinux_raq-2800.gz</i>
-
-<comment>(For RaQ1, Qube 2700)</comment>
-# <i>gzip -9vc colo-chain.elf &gt; /nfsroot/vmlinux.gz</i>
-# <i>cd /nfsroot</i>
-# <i>ln . boot</i>
+<pre caption="Unpacking the nfsroot image">
+# <i>tar -C / -xvf nfsroot-2.6.13.4-1.19-20051122.tar</i>
 </pre>
 
-<note>
-If the latest CoLo release fails to boot, you may wish to try an earlier
-release. Version 1.16 and earlier are known to work.
-</note>
-
 </body>
 </subsection>
 
@@ -812,6 +866,7 @@
   host <i>qube</i> {
     <comment># Path to the nfsroot directory.</comment>
     <comment># This is mainly for when using the TFTP boot option on CoLo</comment>
+    <comment># You shouldn't need to change this.</comment>
     option root-path "/nfsroot";
 
     <comment># Cobalt server's ethernet MAC address</comment>
@@ -823,9 +878,9 @@
     <comment># IP address of cobalt server</comment>
     fixed-address <i>192.168.10.2</i>;
 
-    <comment># Image to download</comment>
-    <comment># Again, this has more to do with CoLo</comment>
-    filename "<i>gentoo-cobalt.img.gz</i>";
+    <comment># Location of the default.colo file relative to /nfsroot</comment>
+    <comment># You shouldn't need to change this.</comment>
+    filename "default.colo";
   }
 }
 </pre>
@@ -872,91 +927,11 @@
 <p>
 If all is well, the back panel should display "Net Booting", you should
 see some network activity, closely followed by CoLo kicking in.  On the rear
-panel, scroll down the menu until you see "Boot Shell" then press ENTER.  On the
-serial console, you should be dropped to a prompt as shown below.
-</p>
-
-<note>
-It has been reported that simply selecting the NFS boot option does all of this
-for you under modern versions of CoLo. If selecting this option does not work,
-then read on.
-</note>
-
-<pre caption="CoLo booting to a prompt">
-[ "CoLo" v1.13 ]
-stage2: 87fb0000-88000000
-pci: unit type &lt;Qube2&gt;
-tulip: {00:10:e0:00:86:3d}
-ide: resetting
-boot: running boot menu
-&gt;
-</pre>
-
-<p>
-First step, tell the machine to fetch an address via DHCP.  Type <c>dhcp</c> at
-the prompt.
-</p>
-
-<pre caption="Fetching an address via DHCP">
-&gt; <i>dhcp</i>
-net: interface up
-dhcp: DISCOVER
-dhcp: OFFER 10.0.0.1 &lt;-- 192.168.10.254
-dhcp: REQUEST
-arp: sent request for 192.168.10.254
-udp: no matching socket 192.168.5.1:67 --&gt; 10.0.0.1:68
-arp: resolved 192.168.10.254
-udp: no matching socket 192.168.5.1:67 --&gt; 10.0.0.1:68
-dhcp: DISCOVER
-dhcp: OFFER 10.0.0.1 &lt;-- 192.168.10.254
-dhcp: REQUEST
-udp: no matching socket 192.168.5.1:67 --&gt; 10.0.0.1:68
-dhcp: ACK
-net: interface down
-net: interface up
-  address     10.0.0.1
-  netmask     255.255.255.0
-  gateway     10.0.0.254
-  name server 192.168.5.1
-</pre>
-
-<p>
-NOTE: If you have a Windows network you may see messages along the lines of
-<c>udp: no matching socket</c>.  These are in response to network broadcasts on
-ports that CoLo doesn't recognise.  As annoying as they are, they are perfectly
-harmless.
-</p>
-
-<pre caption="'no matching socket' error messages">
-udp: no matching socket 10.0.0.254:138 --&gt; 10.0.0.255:138
-udp: no matching socket 10.0.0.254:138 --&gt; 10.0.0.255:138
-udp: no matching socket 10.0.0.253:1062 --&gt; 10.0.0.255:137
-udp: no matching socket 10.0.0.253:1062 --&gt; 10.0.0.255:137
-</pre>
-
-<p>
-Okay, the next step is to tell the Cobalt server to download its kernel.
-</p>
-
-<pre caption="Downloading the kernel">
-&gt; <i>nfs 10.0.0.254 /nfsroot gentoo.img.gz</i>
-arp: sent request for 10.0.0.254
-arp: resolved 10.0.0.254
-udp: no matching socket 10.0.0.253:1062 --&gt; 10.0.0.255:137
-nfs: mounted "/nfsroot"
-nfs: lookup "gentoo.img.gz"
-nfs: mode &lt;0100644&gt;
-4651KB loaded (1240KB/sec)
-0048ada0 4763040t
-</pre>
-
-<p>
-And that's it... it has now downloaded its kernel, we now can tell it to start
-booting.
+panel, scroll down the menu until you see "Network (NFS)" then press ENTER.
+You should notice the machine starts booting on the serial console.
 </p>
 
 <pre caption="Booting the kernel">
-&gt; <i>execute</i>
 elf: 80080000 &lt;-- 00001000 6586368t + 192624t
 elf: entry 80328040
 net: interface down
@@ -1040,84 +1015,5 @@
 </body>
 </subsection>
 </section>
-<!--
-
-  Commented Out Until Further Notice
 
-<section>
-<title>Gentoo/MIPS LiveCD</title>
-<subsection>
-<title>Overview</title>
-<body>
-
-<p>
-On Silicon Graphics machines, it is possible to boot from a CD in order to
-install operating systems.  (This is how one installs IRIX for instance)
-Recently, images for such bootable CDs to install Gentoo have been made
-possible.  These CDs are designed to work in the same way.
-</p>
-
-<p>
-At the moment the Gentoo/MIPS Live CD will only work on the SGI Indy,
-Indigo 2 and O2 workstations equipped with R4000 and R5000-series CPUs, however
-other platforms may be possible in future.
-</p>
-
-<p>
-You can find the Live CD images for download on your favourite Gentoo Mirror
-under the <path>experimental/mips/livecd</path> directory.
-</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.
-</warn>
-
-</body>
-
-</subsection>
-
-<subsection>
-<title>Burning a Live CD</title>
-<body>
-
-<p>
-An important thing to note, the SGI PROM does not understand the ISO9660 format,
-nor does it know anything about the El Torito boot standard.  These CD images
-are constructed as a SGI disklabel with the boot image in the volume header like
-a hard drive.  Therefore, care must be taken when burning the CD image.
-</p>
-
-<p>
-Below is an example command that assumes 24x burning speed on an IDE burner.  If
-you have a SCSI burner for instance, you may want to adjust the <c>dev</c>
-statement as appropriate.  Likewise with the <c>speed</c> option - if you
-strike troubles, you might want to try dropping the speed.
-</p>
-
-<pre caption="Burning using cdrecord">
-# <i>bzip2 -d mips-livecd-prototype-rc2-20041027.img.bz2</i>
-# <i>cdrecord -vv -pad speed=24 dev=ATAPI:0,0,0 -tao mips-livecd-prototype-rc2-20041027.img</i>
-</pre>
-
-<note>
-It may be possible to burn these CDs under Windows, assuming your burning
-program just blindly burns the image as is.  However, no one has succeeded in
-making a working CD this way to date.
-</note>
-
-<note>
-If you don't know what to put as your <c>dev</c> argument, run <c>cdrecord
--scanbus</c> as root - this will tell you where your burner is located.
-</note>
-
-</body>
-</subsection>
-</section>
--->
 </sections>



1.33      +47 -36    xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml?rev=1.33&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml?rev=1.33&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml.diff?r1=1.32&r2=1.33&cvsroot=gentoo

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.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- hb-install-ppc-bootloader.xml	19 Jan 2006 21:48:10 -0000	1.32
+++ hb-install-ppc-bootloader.xml	27 Feb 2006 00:55:34 -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/1.0 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.32 2006/01/19 21:48:10 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.33 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.8</version>
-<date>2006-01-19</date>
+<version>2.9</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Choosing a Bootloader</title>
@@ -43,16 +43,21 @@
 <impo>
 yaboot can only be used on NewWorld Apple or IBM machines!
 </impo>
-
+  
 <p>
-In order to find the boot devices, yaboot needs access to the <path>/dev</path>
-filesystem.  To do this, you will need to "bind-map" the <path>/dev</path> 
-filesystem from the Installation CD to <path>/dev</path> inside of the chroot.
+In order to find the boot devices, yaboot needs access to the device nodes
+created by udev on startup and the sysfs filesystem.  These two filesystems
+are found at <path>/dev</path> and <path>sys</path> respectively.  To do this,
+you will need to "bind mount" these filesystems from the Installation CD's root
+to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot.
+If you have already bind mounted these filesystems, there is no need to do it
+again.
 </p>
-
-<pre caption="Bind-mounting the /dev filesystem">
+  
+<pre caption="Bind-mounting the device and sysfs filesystems">
 # <i>exit </i> # this will exit the chroot
 # <i>mount -o bind /dev /mnt/gentoo/dev</i>
+# <i>mount -o bind /sys /mnt/gentoo/sys</i>
 # <i>chroot /mnt/gentoo /bin/bash</i>
 # <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
 </pre>
@@ -73,10 +78,10 @@
 <pre caption="Adding genkernel boot arguments to yaboot.conf">
 <comment>###########################################################
 ## This section can be duplicated if you have more than one
-## kernel or set of boot options - replace kernel-2.6.12
+## kernel or set of boot options - replace kernel-2.6.15
 ## with the exact filename of your kernel.
 ###########################################################</comment>
-image=/boot/kernel-2.6.12
+image=/boot/kernel-2.6.15
   label=Linux
   root=/dev/ram0    <comment># If using genkernel this is /dev/ram0</comment>
   partition=3
@@ -104,27 +109,28 @@
 <c>yabootconfig</c> will auto-detect the partitions on your machine and will
 set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X.
 </p>
-
+  
 <p>
 To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
-and <path>/etc/fstab</path> must be configured with your Linux partitions. Both
-of these steps should have been completed already.  First, make sure that you 
-have the latest version of <c>yaboot</c> installed.
+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.
 </p>
-
-<pre caption = "Installing yaboot with GRP">
-# <i>emerge --usepkg --update yaboot</i>
+  
+<pre caption = "Installing yaboot">
+# <i>emerge yaboot</i>
 </pre>
-
+  
 <p>
-Now, exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>.  It will
-ask you to confirm the location of the Apple_Bootstrap partition.  Type <c>Y</c>
-if it is correct. If not, check <path>/etc/fstab</path> and ensure that the 
-device paths are correct.  Once the bootstrap partition has been selected, 
-<c>yabootconfig</c> will scan your system setup, create 
-<path>/etc/yaboot.conf</path> and run <c>mkofboot</c>. <c>mkofboot</c>
-formats the Apple_Bootstrap partition, and installs the yaboot configuration 
-file onto it.  After this is complete, enter the chroot again.
+Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First,
+the program will confirm the location of the bootstrap partition.  If you are
+using the suggested disk partitioning scheme, your bootstrap partition should
+be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your
+<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup, 
+create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. 
+<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install 
+the yaboot configuration file into it.  After this enter the chroot again.
 </p>
 
 <pre caption="Re-enter the chroot">
@@ -150,11 +156,11 @@
 <body>
 
 <p>
-First, make sure you have the latest version of <c>yaboot</c> installed.
+First, make sure you have <c>yaboot</c> installed.
 </p>
 
 <pre caption = "Installing yaboot">
-# <i>emerge --usepkg --update yaboot</i>
+# <i>emerge yaboot</i>
 </pre>
 
 <p>
@@ -313,6 +319,12 @@
 BootX home page</uri> for more information.
 </p>
 
+<impo>
+Make sure that you have support for HFS and HFS+ filesystems in your kernel,
+otherwise you will not be able to upgrade or change the kernel on your MacOS 
+partition.
+</impo>
+
 <p>
 Now reboot again and boot into Linux, then continue with <uri
 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
@@ -346,12 +358,12 @@
 
 <pre caption="Configuring quik.conf">
 # Example of quik.conf
-init-message = "Gentoo 2005.1\n"
+init-message = "Gentoo 2006.0\n"
 partition = 2		<comment># This is the boot partition</comment>
 root = /dev/hda4
 timeout = 30
 default = gentoo
-image = /vmlinux-2.6.12
+image = /vmlinux-2.6.15
 	label = gentoo
 </pre>
 
@@ -379,7 +391,7 @@
 # <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.12 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/vmlinux-2.6.15 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>
 
@@ -464,12 +476,12 @@
 ide:0 boot2.img ramdebug edebugflags="logkprintf"
 
 [SECTION]
-Local HD -> Linux 2.6.12 (Normal)
-ide:0 linux-2.6.12 video=radeonfb:1024x768@70 root=/dev/hda3
+Local HD -> Linux 2.6.15 (Normal)
+ide:0 linux-2.6.15 video=radeonfb:1024x768@70 root=/dev/hda3
 
 [SECTION]
 Local HD -> Genkernel (Normal)
-ide:0 kernelz-2.6.12 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc
+ide:0 kernelz-2.6.15 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc
 </pre>
 
 <p>
@@ -492,7 +504,6 @@
 <uri link="#reboot">Rebooting the System</uri>.
 </p>
 
-
 </body>
 </section>
 <section id="reboot">



1.34      +16 -18    xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml?rev=1.34&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml?rev=1.34&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml.diff?r1=1.33&r2=1.34&cvsroot=gentoo

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.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- hb-install-ppc-disk.xml	5 Sep 2005 23:17:21 -0000	1.33
+++ hb-install-ppc-disk.xml	27 Feb 2006 00:55:34 -0000	1.34
@@ -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.33 2005/09/05 23:17:21 vanquirius Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.34 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.4</version>
-<date>2005-08-25</date>
+<version>2.5</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -26,10 +26,10 @@
 </p>
 
 <p>
-To begin, we'll introduce <e>block devices</e>. The most famous block device is
-probably the one that represents the first IDE drive in a Linux system, namely
-<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your first
-hard drive would be <path>/dev/sda</path>.
+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>.
 </p>
 
 <p>
@@ -108,7 +108,7 @@
   <ti>(Not applicable)</ti>
   <ti><path>/dev/hda2</path> (If using quik)</ti>
   <ti><path>/dev/hda1</path></ti>
-  <ti>(Not needed)</ti>
+  <ti>(Not applicable)</ti>
   <ti>ext2</ti>
   <ti>32MB</ti>
   <ti>Boot partition</ti>
@@ -138,18 +138,17 @@
 Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not 
 planning to use MacOS 9 you can delete them, because MacOS X and Linux don't 
 need them.  To delete them, either use parted or erase the whole disk by 
-initialing the partition map.
+initializing the partition map.
 </note>
-
+  
 <warn>
-<c>parted</c> is able to resize partitions.  On the Installation CD there 
-are patches included to resize HFS+ filesystem.  Unfortunately it is risky to
-resize HFS+ journaled filesystems, be sure to switch off journaling in Mac OS X
-first and make sure to run a disk checking tool after the resize. Everything 
-you do with resizing in parted you do it at your own risk!  Be sure to have a 
-backup of your data!
+<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.  Remeber 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>
 If you are interested in knowing how big a partition should be, or even how many
 partitions you need, read on. Otherwise continue now with 
@@ -523,7 +522,6 @@
 also holds 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



1.39      +21 -16    xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.39&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.39&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml.diff?r1=1.38&r2=1.39&cvsroot=gentoo

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.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- hb-install-ppc-kernel.xml	8 Jan 2006 14:05:29 -0000	1.38
+++ hb-install-ppc-kernel.xml	27 Feb 2006 00:55:34 -0000	1.39
@@ -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.38 2006/01/08 14:05:29 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.39 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.15</version>
-<date>2006-01-06</date>
+<version>2.16</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Timezone</title>
@@ -59,24 +59,16 @@
 # <i>USE="-doc symlink" emerge gentoo-sources</i>
 </pre>
 
-<!-- Removed, as we're trying to avoid specific kernel versions to improve HB
-maintainability
-<note>
-The suggested sources at the time of the 2005.1 release are
-<c>gentoo-sources-2.6.12-r4</c> and <c>vanilla-sources-2.6.12.2</c>.
-</note> 
--->
-
 <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.12-r4</c>. Your version
+installed kernel source points to <c>gentoo-sources-2.6.15</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.12-gentoo-r4
+lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -&gt; linux-2.6.15-gentoo
 </pre>
 
 <p>
@@ -303,13 +295,26 @@
 
 <p>
 When the kernel has finished compiling, copy the kernel image to
-<path>/boot</path> (be sure that it is mounted properly on the Pegasos).
+<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.
+</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>.
 </p>
 
 <pre caption="Installing the kernel">
+# <i>cd /usr/src/linux</i>
 <comment>replace &lt;kernel-version&gt; with your kernel version</comment>
-(Apple/IBM)  # <i>cp vmlinux /boot/&lt;kernel-version&gt;</i>
-(Pegasos)    # <i>cp arch/ppc/boot/images/zImage.chrp /boot/&lt;kernel-version&gt;</i>
+<comment>(Apple/IBM)</comment>
+# <i>cp vmlinux /boot/&lt;kernel-version&gt;</i> 
+<comment>(Pegasos)</comment>
+# <i>cp arch/ppc/boot/images/zImage.chrp /boot/&lt;kernel-version&gt;</i> 
 </pre>
 
 <p>



1.52      +61 -50    xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml?rev=1.52&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml?rev=1.52&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml.diff?r1=1.51&r2=1.52&cvsroot=gentoo

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.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- hb-install-ppc-medium.xml	29 Nov 2005 14:48:46 -0000	1.51
+++ hb-install-ppc-medium.xml	27 Feb 2006 00:55:34 -0000	1.52
@@ -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.51 2005/11/29 14:48:46 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.52 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.8</version>
-<date>2005-11-29</date>
+<version>2.9</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -71,8 +71,9 @@
 </table>
 
 <p>
-Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo 
-PPC FAQ</uri> before you begin.
+Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri>
+for help with some common installation related issues or if you're unsure as to
+just what's in that PowerPC machine you've got sitting on your desk right now.
 </p>
 
 </body>
@@ -104,7 +105,7 @@
 <p>
 If you wish to install Gentoo without a working Internet connection, please use
 the installation instructions described in the <uri
-link="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>.
+link="2006.0/index.xml">Gentoo 2006.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -136,7 +137,7 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-ppc-minimal-2005.1.iso</c> and 
+The Minimal Installation CD is called <c>install-ppc-minimal-2006.0.iso</c> and 
 takes up only 52 MB of diskspace. You can use this Installation CD to install 
 Gentoo, but always with a working Internet connection only.
 </p>
@@ -166,11 +167,11 @@
 <body>
 
 <p>
-The Universal Installation CD is called <c>install-ppc-universal-2005.1.iso</c> 
-and consumes the entire surface of a 650 MB 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 you are currently installing Gentoo on :)
+The Universal Installation CD is called <c>install-ppc-universal-2006.0.iso</c> 
+and consumes about 578 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
+you are currently installing Gentoo on :)
 </p>
 
 <table>
@@ -247,7 +248,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/ppc/2005.1/installcd</path> 
+Installation CDs are located in the <path>releases/ppc/2006.0/ppc32/installcd</path> 
 directory.
 </p>
 
@@ -259,7 +260,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-ppc-minimal-2005.1.iso.md5</path>). You can check the MD5 checksum
+<path>install-ppc-minimal-2006.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. If
 <c>md5sum</c> is not available on Mac OS X, see the 
@@ -322,15 +323,13 @@
 </p>
 
 <p>
-At this prompt you are able to select a kernel for the subarchitecture you use.
-We provide <c>G3</c>, <c>G4</c> and <c>G5</c>. All kernels are built with
-support for multiple CPUs, but they will boot on single processor machines as
-well.
+We provide one generic kernel, <e>ppc32</e>. This kernel is built with support
+for multiple CPUs, but it will boot on single processor machines as well.
 </p>
 
 <p>
-You are also able to tweak some kernel options at this prompt. The following
-table lists some of the available boot options you can add:
+You can tweak some kernel options at this prompt. The following table lists 
+some of the available boot options you can add:
 </p>
 
 <table>
@@ -342,10 +341,13 @@
   <ti><c>video</c></ti>
   <ti>
     This option takes one of the following vendor-specific tags:
-    <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</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.
+    <c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, 
+    <c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution 
+    refresh rate and color depth you want to use. For instance,
+    <c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer
+    at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of
+    32 bits. If you are uncertain what to choose, and the default doesn't work,
+    <c>video=ofonly</c> will most certainly work.
   </ti>
 </tr>
 <tr>
@@ -385,11 +387,11 @@
 On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type
 <c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose
 between several preconfigured video configs. If you need any special boot
-options you can append them to the command-line. For instance <c>boot cd
-/boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.  The complete list of
-kernel appends (in case something goes wrong and you need it) is preconfigured
-in the kernel with <c>console=ttyS0,115200 console=tty0 init=/linuxrc
-looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>.
+options you can append them to the command-line just like with Yaboot above. 
+For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.
+The default kernel options (in case something goes wrong and you need it) are 
+preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc 
+looptype=squashfs loop=/image.squashfs udev nodevfs cdroot root=/dev/ram0</c>.
 </p>
 
 </body>
@@ -402,8 +404,7 @@
 <p>
 If you have an OldWorld Mac the bootable portion of the livecd can't be used.
 The most simple solution is to use MacOS to bootstrap into a Linux environment
-with a tool called BootX.  Boot floppies are being prepared for Macs without
-MacOS, but they are not available at this time.
+with a tool called BootX.  
 </p>
 
 <p>
@@ -412,33 +413,34 @@
 archive into <c>Extensions Folder</c> and the BootX App Control Panel into
 <c>Control Panels</c>, both of which are located in your MacOS System Folder.
 Next, create a folder called "Linux Kernels" in your System folder and copy the
-<c>G3G4</c> kernel from the CD to this folder.  Finally, copy <c>G3G4.igz</c> 
+<c>ppc32</c> kernel from the CD to this folder.  Finally, copy <c>ppc32.igz</c> 
 from the Installation CD <path>boot</path> folder into the MacOS 
 <c>System Folder</c>.
 </p>
 
 <p>
 To prepare BootX, start the BootX App Control Panel.  First select the Options
-dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from
+dialog and check <c>Use Specified RAM Disk</c> and select <c>ppc32.igz</c> from
 your System Folder.  Continue back to the initial screen and ensure that the
 ramdisk size is at least <c>32000</c>.  Finally, set the kernel arguments as
 shown below:
 </p>
 
 <pre caption="BootX kernel arguments">
-cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev
+cdroot root=/dev/ram0 init=linuxrc loop=image.squashfs looptype=squashfs console=tty0 nodevfs udev
 </pre>
 
 <note>
-The kernel parameters in the yaboot section above are also applicable here.
+The kernel parameters in the yaboot section above are also applicable here. You
+can append any of those options to the kernel arguments above.
 </note>
 
 <p>
 Check once more to make sure the settings are correct and then save the 
 configuration.  This saves typing just in case it doesn't boot or something is
-missing.  Press the Linux button at the top of the window to boot into the 
-Installation CD and continue with <uri link="#booted">And When 
-You're Booted...</uri>
+missing.  Press the Linux button at the top of the window.  If everything goes
+correctly, it should boot into the Installation CD. Continue with 
+<uri link="#booted">And When You're Booted...</uri>
 </p>
 
 </body>
@@ -451,8 +453,8 @@
 <p>
 You will be greeted by a root ("#") prompt on the current console. You 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. Probably you have to hit
-Alt-fn-Fx on Apple machines.
+back to the one you started on by pressing Alt-F1.  Due to the keyboard layout,
+you may need to press Alt-fn-Fx on Apple machines.
 </p>
 
 <p>
@@ -496,16 +498,25 @@
 of your system's hardware, you will have to load the appropriate kernel modules
 manually. 
 </p>
-
+  
 <p>
-In the next example we try to load the <c>airport</c> module. This module
-supports only the old Airport cards (b-net). AirportExtreme is currently not
-supported under Linux:
+In the next example we try to load the <c>airport</c> module.  This module
+supports only the old Airport cards (802.11b).  Airport Extreme (802.11g) is not
+supported on the InstallCD due to restrictions on firmware distribution.
 </p>
-
-<pre caption="Loading kernel modules">
+  
+<pre caption="Loading the airport module">
 # <i>modprobe airport</i>
 </pre>
+  
+<p>
+On older iMacs, sometimes the network card is not detected properly.  These use
+the BMAC driver:
+</p>
+
+<pre caption="Loading the bmac module">
+# <i>modprobe bmac</i>
+</pre>
 
 </body>
 </subsection>
@@ -595,23 +606,23 @@
 
 <p>
 If you want to view the documentation on the CD you can immediately run
-<c>links2</c> to read it:
+<c>links</c> to read it:
 </p>
 
 <pre caption="Viewing the on-CD documentation">
-# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i>
+# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
 </pre>
 
 <p>
 However, it is preferred that you use the online Gentoo Handbook as it will be
-more recent than the one provided on the CD. You can view it using <c>links2</c>
+more recent than the one provided on the CD. You can view it using <c>links</c>
 as well, but only after having completed the <e>Configuring your Network</e>
 chapter (otherwise you won't be able to go on the Internet to view the
 document):
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i>
 </pre>
 
 <p>



1.23      +14 -5     xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml?rev=1.23&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml?rev=1.23&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml.diff?r1=1.22&r2=1.23&cvsroot=gentoo

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.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- hb-install-ppc64-bootloader.xml	20 Jan 2006 10:52:15 -0000	1.22
+++ hb-install-ppc64-bootloader.xml	27 Feb 2006 00:55:34 -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-ppc64-bootloader.xml,v 1.22 2006/01/20 10:52:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-bootloader.xml,v 1.23 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.7</version>
-<date>2006-01-20</date>
+<version>2.8</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Making your Choice</title>
@@ -39,8 +39,9 @@
 <body>
 
 <impo>
-You have to use yaboot-static instead of yaboot, because yaboot won't
-compile on PPC64.
+If you are using a 64-bit userland, you must use the <c>yaboot-static</c>
+package because yaboot cannot be compiled as a 64-bit application. The 32-bit
+userlands should use the regular yaboot package.
 </impo>
 
 <p>
@@ -93,7 +94,11 @@
 </p>
 
 <pre caption = "Installing yaboot-static">
+<comment>(For 64-bit users)</comment>
 # <i>emerge --update yaboot-static</i>
+
+<comment>(For 32-bit users)</comment>
+# <i>emerge yaboot</i>
 </pre>
 
 <p>
@@ -128,7 +133,11 @@
 </p>
 
 <pre caption = "Installing yaboot">
+<comment>(For 64-bit users)</comment>
 # <i>emerge --update yaboot-static</i>
+
+<comment>(For 32-bit users)</comment>
+# <i>emerge yaboot</i>
 </pre>
 
 <p>



1.24      +17 -8     xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml?rev=1.24&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml?rev=1.24&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml.diff?r1=1.23&r2=1.24&cvsroot=gentoo

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.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-ppc64-disk.xml	20 Jan 2006 10:52:15 -0000	1.23
+++ hb-install-ppc64-disk.xml	27 Feb 2006 00:55:34 -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-ppc64-disk.xml,v 1.23 2006/01/20 10:52:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-disk.xml,v 1.24 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.6</version>
-<date>2006-01-20</date>
+<version>2.7</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -245,11 +245,20 @@
 
 <note>
 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>iprutils</c> to 
-format the disks to Advanced Function format and create the disk array.
+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.
+</p>
+
+<pre caption="Starting ipr utilities">
+# <i>/etc/init.d/iprinit start</i>
+</pre>
+
+<p>
 The following parts explain how to create the example partition layout
 described previously, namely:
 </p>
@@ -562,9 +571,9 @@
 <body>
 
 <note>
-Several filesystems are available. Ext2 and ext3 are found stable on the
-PPC64 architecture, reiserfs and xfs are in experimental stage. jfs is
-unsupported.
+Several filesystems are available. ext2, ext3 and ReiserFS support is built in
+the Installation CD kernels. JFS and XFS support is available through kernel
+modules.
 </note>
 
 <p>



1.23      +7 -8      xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml?rev=1.23&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml?rev=1.23&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml.diff?r1=1.22&r2=1.23&cvsroot=gentoo

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.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- hb-install-ppc64-kernel.xml	8 Jan 2006 14:05:29 -0000	1.22
+++ hb-install-ppc64-kernel.xml	27 Feb 2006 00:55:34 -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-ppc64-kernel.xml,v 1.22 2006/01/08 14:05:29 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-kernel.xml,v 1.23 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.10</version>
-<date>2006-01-06</date>
+<version>2.11</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Timezone</title>
@@ -107,13 +107,12 @@
 uses (it might provide you with a nice hint on what to enable).
 </p>
 
-<p>
-Now go to your kernel source directory and execute <c>make
-menuconfig</c>. This will fire up an ncurses-based configuration menu.
-</p>
-
 <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 
+make menuconfig or it may result in kernel compilation problems.</comment>
 # <i>make menuconfig</i>
 </pre>
 



1.29      +14 -15    xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml?rev=1.29&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml?rev=1.29&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml.diff?r1=1.28&r2=1.29&cvsroot=gentoo

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.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- hb-install-ppc64-medium.xml	29 Nov 2005 14:48:47 -0000	1.28
+++ hb-install-ppc64-medium.xml	27 Feb 2006 00:55:34 -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-medium.xml,v 1.28 2005/11/29 14:48:47 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v 1.29 2006/02/27 00:55:34 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.10</version>
-<date>2005-11-29</date>
+<version>2.11</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -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="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>. This is currently not
+link="2006.0/index.xml">Gentoo 2006.0 Handbooks</uri>. This is currently not
 supported for the PPC64 architecture though.
 </p>
 
@@ -121,7 +121,7 @@
 
 <p>
 The Minimal Installation CD is called 
-<c>install-ppc64-minimal-2005.1-r1.iso</c> and takes up only 143 MB of 
+<c>install-ppc64-minimal-2006.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,11 +152,10 @@
 
 <p>
 The Universal Installation CD is called
-<c>install-ppc64-universal-2005.1-r1.iso</c> and uses
-486 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 :)
+<c>install-ppc64-universal-2006.0-32ul.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 :)
 </p>
 
 <table>
@@ -214,7 +213,7 @@
 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/ppc64/2005.1-r1/installcd</path> directory.
+<path>releases/ppc/2006.0/ppc64/installcd</path> directory.
 </p>
 
 <p>
@@ -225,7 +224,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-2005.1-r1.iso.md5</path>). You can check the MD5 
+<path>install-ppc64-minimal-2006.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>
@@ -517,11 +516,11 @@
 
 <p>
 If you want to view the documentation on the CD you can immediately run
-<c>links2</c> to read it:
+<c>links</c> to read it:
 </p>
 
 <pre caption="Viewing the on-CD documentation">
-# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i>
+# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
 </pre>
 
 <p>
@@ -530,7 +529,7 @@
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i>
 </pre>
 
 <p>



1.41      +16 -15    xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml?rev=1.41&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml?rev=1.41&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml.diff?r1=1.40&r2=1.41&cvsroot=gentoo

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.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- hb-install-sparc-medium.xml	29 Nov 2005 14:48:47 -0000	1.40
+++ hb-install-sparc-medium.xml	27 Feb 2006 00:55:35 -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-sparc-medium.xml,v 1.40 2005/11/29 14:48:47 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml,v 1.41 2006/02/27 00:55:35 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.8</version>
-<date>2005-11-29</date>
+<version>2.9</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -32,7 +32,8 @@
 <tr>
   <th>Sparc System</th>
   <ti>
-    Please check the <uri 
+    Please check the <uri link="/proj/en/base/sparc/sunhw.xml">Gentoo
+    Linux/SPARC64 Compatibility list</uri> or the <uri
     link="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri>
   </ti>
 </tr>
@@ -86,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="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>.
+link="2006.0/index.xml">Gentoo 2006.0 Handbooks</uri>.
 </p>
 
 <p>
@@ -126,7 +127,7 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-sparc64-minimal-2005.1-r1.iso</c> 
+The Minimal Installation CD is called <c>install-sparc64-minimal-2006.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>
@@ -157,7 +158,7 @@
 
 <p>
 The Universal Installation CD is called
-<c>install-sparc-universal-2005.1-r1.iso</c> and use 525 MB. You can use this
+<c>install-sparc64-universal-2006.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 :)
@@ -238,7 +239,7 @@
 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/2005.1-r1/sparc64/installcd</path> directory.
+<path>releases/sparc/2006.0/sparc64/installcd</path> directory.
 </p>
 
 <p>
@@ -249,7 +250,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-2005.1-r1.iso.md5</path>). You can check the MD5 
+<path>install-sparc64-minimal-2006.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,12 +311,12 @@
 
 <p>
 You will be greeted by the SILO boot manager (on the Installation CD). Type in
-<c>gentoo-2.4</c> and press enter to continue booting the 
+<c>gentoo</c> and press enter to continue booting the 
 system:
 </p>
 
 <pre caption="Continue booting from the Installation CD">
-boot: <i>gentoo-2.4</i>
+boot: <i>gentoo</i>
 </pre>
 
 <p>
@@ -414,23 +415,23 @@
 
 <p>
 If you want to view the documentation on the CD you can immediately run
-<c>links2</c> to read it:
+<c>links</c> to read it:
 </p>
 
 <pre caption="Viewing the on-CD documentation">
-# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i>
+# <i>links /mnt/cdrom/docs/handbook/html/index.html</i>
 </pre>
 
 <p>
 However, it is preferred that you use the online Gentoo Handbook as it will be
-more recent than the one provided on the CD. You can view it using <c>links2</c>
+more recent than the one provided on the CD. You can view it using <c>links</c>
 as well, but only after having completed the <e>Configuring your Network</e>
 chapter (otherwise you won't be able to go on the Internet to view the
 document):
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml</i>
 </pre>
 
 <p>



1.94      +21 -22    xml/htdocs/doc/en/handbook/hb-install-stage.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.94&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.94&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-stage.xml.diff?r1=1.93&r2=1.94&cvsroot=gentoo

Index: hb-install-stage.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- hb-install-stage.xml	15 Feb 2006 13:05:58 -0000	1.93
+++ hb-install-stage.xml	27 Feb 2006 00:55:35 -0000	1.94
@@ -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-stage.xml,v 1.93 2006/02/15 13:05:58 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.94 2006/02/27 00:55:35 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.7</version>
-<date>2005-11-24</date>
+<version>2.8</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Installing a Stage Tarball</title>
@@ -86,13 +86,13 @@
 
 <p>
 Depending on your installation medium, you have a couple of tools available to
-download a stage. If you have <c>links2</c> available, then you can immediately
+download a stage. If you have <c>links</c> available, then you can immediately
 surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and 
 choose a mirror close to you.
 </p>
 
 <p>
-If you don't have <c>links2</c> available you should have <c>lynx</c> at your 
+If you don't have <c>links</c> available you should have <c>lynx</c> at your 
 disposal. If you need to go through a proxy, export the <c>http_proxy</c> and
 <c>ftp_proxy</c> variables:
 </p>
@@ -103,24 +103,23 @@
 </pre>
 
 <p>
-We will now assume that you have <c>links2</c> at your disposal.
+We will now assume that you have <c>links</c> at your disposal.
 </p>
 
 <p>
 Pick the <path>releases/</path> directory, followed by your architecture (for
-instance <path>x86/</path>) and the Gentoo version (<path>2005.1/</path> or
-<path>2005.1-r1/</path> if available) to finish up with the
-<path>stages/</path> directory. There you should see all available stage files
-for your architecture (they might be stored within subdirectories named to the
-individual subarchitectures). Select one and press <c>D</c> to download. When
-you're finished, press <c>Q</c> to quit the browser.
+instance <path>x86/</path>) and the Gentoo version (<path>2006.0/</path>) to
+finish up with the <path>stages/</path> directory. There you should see all
+available stage files for your architecture (they might be stored within
+subdirectories named to the individual subarchitectures). Select one and press
+<c>D</c> to download. When you're finished, press <c>Q</c> to quit the browser.
 </p>
 
-<pre caption="Surfing to the mirror listing with links2">
-# <i>links2 http://www.gentoo.org/main/en/mirrors.xml</i>
+<pre caption="Surfing to the mirror listing with links">
+# <i>links http://www.gentoo.org/main/en/mirrors.xml</i>
 
-<comment>(If you need proxy support with links2:)</comment>
-# <i>links2 -http-proxy proxy.server.com:8080 http://www.gentoo.org/main/en/mirrors.xml</i>
+<comment>(If you need proxy support with links:)</comment>
+# <i>links -http-proxy proxy.server.com:8080 http://www.gentoo.org/main/en/mirrors.xml</i>
 </pre>
 
 <p>
@@ -135,8 +134,8 @@
 </p>
 
 <pre caption="Example checking integrity of a stage tarball">
-# <i>md5sum -c stage3-x86-2005.1-r1.tar.bz2.md5</i>
-stage3-x86-2005.1-r1.tar.bz2: OK
+# <i>md5sum -c stage3-x86-2006.0.tar.bz2.DIGESTS</i>
+stage3-x86-2006.0.tar.bz2: OK
 </pre>
 
 </body>
@@ -215,12 +214,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;-2005.1-r1.tar.bz2</path>. Be sure to substitute
+<path>stage3-&lt;subarch&gt;-2006.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;-2005.1-r1.tar.bz2</i>
+# <i>tar xvjpf /mnt/cdrom/stages/stage3-&lt;subarch&gt;-2006.0.tar.bz2</i>
 </pre>
 
 <p>
@@ -258,14 +257,14 @@
 </pre>
 
 <p>
-Fire up <c>links2</c> (or <c>lynx</c>) and go to our <uri
+Fire up <c>links</c> (or <c>lynx</c>) and go to our <uri
 link="/main/en/mirrors.xml">Gentoo mirror list</uri>. Pick a mirror close to
 you and open the <path>snapshots/</path> directory. There, download the latest
 Portage snapshot by selecting it and pressing <c>D</c>.
 </p>
 
 <pre caption="Browsing the Gentoo mirrorlist">
-# <i>links2 http://www.gentoo.org/main/en/mirrors.xml</i>
+# <i>links http://www.gentoo.org/main/en/mirrors.xml</i>
 </pre>
 
 <p>



1.90      +20 -20    xml/htdocs/doc/en/handbook/hb-install-system.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-system.xml?rev=1.90&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-system.xml?rev=1.90&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-system.xml.diff?r1=1.89&r2=1.90&cvsroot=gentoo

Index: hb-install-system.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- hb-install-system.xml	22 Feb 2006 10:17:44 -0000	1.89
+++ hb-install-system.xml	27 Feb 2006 00:55:35 -0000	1.90
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.89 2006/02/22 10:17:44 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.90 2006/02/27 00:55:35 fox2mike Exp $ -->
 
 <sections>
 
-<version>2.16</version>
-<date>2006-02-22</date>
+<version>2.17</version>
+<date>2006-02-27</date>
 
 <section>
 <title>Chrooting</title>
@@ -113,7 +113,7 @@
 <pre caption = "Chrooting into the new environment">
 # <i>chroot /mnt/gentoo /bin/bash</i>
 # <i>env-update</i>
->>> Regenerating /etc/ld.so.cache...
+ * Caching service dependencies...
 # <i>source /etc/profile</i>
 # <i>export PS1="(chroot) $PS1"</i>
 </pre>
@@ -189,7 +189,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/2005.1/
+lrwxrwxrwx  1 48 Apr  8 18:51 /etc/make.profile -> ../usr/portage/profiles/default-linux/x86/2006.0/
 </pre>
 
 <p>
@@ -227,42 +227,42 @@
 </pre>
 
 <p>
-For ppc, there are a number of new profiles provided with 2005.1.
+For ppc, there are a number of new profiles provided with 2006.0
 </p>
 
 <pre caption="PPC Profiles">
 <comment>(Generic PPC profile, for all PPC machines)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc32 /etc/make.profile</i>
 <comment>(G3 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc/G3 /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc32/G3 /etc/make.profile</i>
 <comment>(G3 Pegasos profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc/G3/Pegasos/ /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc32/G3/Pegasos/ /etc/make.profile</i>
 <comment>(G4 (Altivec) profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc/G4 /etc/make.profile</i>
-<comment>(G4 Pegasos profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc/G4/Pegasos/ /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc32/G4 /etc/make.profile</i>
+<comment>(G4 (Altivec) Pegasos profile)</comment>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc32/G4/Pegasos/ /etc/make.profile</i>
 </pre>
 
 <p>
-For ppc64, there are a number of new profiles provided with 2005.1.
+For ppc64, there are a number of new profiles provided with 2006.0.
 </p>
 
 <pre caption="PPC64 Profiles">
 <comment>(Generic 64bit userland PPC64 profile, for all PPC64 machines)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/64bit-userland /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/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/2005.1/ppc64/32bit-userland /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/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/2005.1/ppc64/(userland)/970 /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/(userland)/970 /etc/make.profile</i>
 <comment>(G5 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/970/pmac /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/(userland)/970/pmac /etc/make.profile</i>
 <comment>(POWER3 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/power3 /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/(userland)/power3 /etc/make.profile</i>
 <comment>(POWER4 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/power4 /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/(userland)/power4 /etc/make.profile</i>
 <comment>(POWER5 profile)</comment>
-# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/power5 /etc/make.profile</i>
+# <i>ln -snf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/(userland)/power5 /etc/make.profile</i>
 <comment>(The multilib profile is not stable as of this release.)</comment>
 </pre>
 



1.45      +30 -21    xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml?rev=1.45&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml?rev=1.45&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml.diff?r1=1.44&r2=1.45&cvsroot=gentoo

Index: hb-install-x86-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- hb-install-x86-medium.xml	29 Nov 2005 14:48:47 -0000	1.44
+++ hb-install-x86-medium.xml	27 Feb 2006 00:55:35 -0000	1.45
@@ -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-medium.xml,v 1.44 2005/11/29 14:48:47 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml,v 1.45 2006/02/27 00:55:35 fox2mike Exp $ -->
 
 <sections>
 
@@ -73,11 +73,12 @@
 latest version of the available packages.
 </p>
 
-<p>
-If you wish to install Gentoo without a working Internet connection, please use
-the installation instructions described in the <uri
-link="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>.
-</p>
+<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.0/index.xml">Gentoo 2006.0
+Handbooks</uri>.
+</impo>
 
 <p>
 The two Installation CDs that we currently provide are:
@@ -90,9 +91,10 @@
     continue with the Gentoo installation.
   </li>
   <li>
-    The Gentoo <e>Universal</e> Installation CD, a bootable CD with the same
-    abilities as the Minimal Installation CD. Additionally, it contains 
-    several stage3 tarballs (optimized for the individual subarchitectures). 
+    The Gentoo <e>Installer LiveCD</e> contains everything you need to install
+    Gentoo. It provides a graphical environment, a graphical as well as console
+    based installer which automatically carries out the installation for you,
+    and of course, the installation instructions for your architecture.
   </li>
 </ul>
 
@@ -108,8 +110,8 @@
 <body>
 
 <p>
-The Minimal Installation CD is called <c>install-x86-minimal-2005.1-r1.iso</c> 
-and takes up only 58 MB of diskspace. You can use this Installation CD to 
+The Minimal Installation CD is called <c>install-x86-minimal-2006.0.iso</c> 
+and takes up only 49 MB of diskspace. You can use this Installation CD to 
 install Gentoo, but always with a working Internet connection only.
 </p>
 
@@ -134,12 +136,12 @@
 </body>
 </subsection>
 <subsection>
-<title>Gentoo's Universal Installation CD</title>
+<title>Gentoo's Installer LiveCD</title>
 <body>
 
 <p>
-The Universal Installation CD is called
-<c>install-x86-universal-2005.1-r1.iso</c> and takes up 398 MB. You can use
+The Installer LiveCD is called
+<c>livecd-i686-installer-2006.0.iso</c> and takes up 697 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 :)
@@ -165,6 +167,7 @@
 
 </body>
 </subsection>
+<!-- PackageCDs on x86 are outdated
 <subsection>
 <title>Other CDs</title>
 <body>
@@ -184,7 +187,7 @@
 </p>
 
 </body>
-</subsection>
+</subsection>-->
 <subsection>
 <title>The Stage3 Tarball</title>
 <body>
@@ -200,6 +203,12 @@
 Using a Stage1 or Stage2 Tarball?</uri>
 </p>
 
+<p>
+Stage3 tarballs can be downloaded from <path>releases/x86/2006.0/stages/</path>
+on any of the <uri link="/main/en/mirrors.xml">Official Gentoo Mirrors</uri>
+and are not provided on the LiveCD.
+</p>
+
 </body>
 </subsection>
 </section>
@@ -219,7 +228,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/x86/2005.1-r1/installcd</path> 
+Installation CDs are located in the <path>releases/x86/2006.0/installcd</path> 
 directory.
 </p>
 
@@ -231,7 +240,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-x86-minimal-2005.1-r1.iso.md5</path>). You can check the MD5
+<path>install-x86-minimal-2006.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>
@@ -507,23 +516,23 @@
 
 <p>
 If you want to view the documentation on the CD you can immediately run
-<c>links2</c> to read it:
+<c>links</c> to read it:
 </p>
 
 <pre caption="Viewing the on-CD documentation">
-# <i>links2 /mnt/cdrom/docs/html/index.html</i>
+# <i>links /mnt/cdrom/docs/html/index.html</i>
 </pre>
 
 <p>
 However, it is preferred that you use the online Gentoo Handbook as it will be
-more recent than the one provided on the CD. You can view it using <c>links2</c>
+more recent than the one provided on the CD. You can view it using <c>links</c>
 as well, but only after having completed the <e>Configuring your Network</e>
 chapter (otherwise you won't be able to go on the Internet to view the
 document):
 </p>
 
 <pre caption="Viewing the Online Documentation">
-# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-x86.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/handbook-x86.xml</i>
 </pre>
 
 <p>



1.59      +6 -6      xml/htdocs/doc/en/handbook/index.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/index.xml?rev=1.59&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/index.xml?rev=1.59&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/index.xml.diff?r1=1.58&r2=1.59&cvsroot=gentoo

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- index.xml	12 Jan 2006 13:30:17 -0000	1.58
+++ index.xml	27 Feb 2006 00:55:35 -0000	1.59
@@ -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.58 2006/01/12 13:30:17 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.59 2006/02/27 00:55:35 fox2mike Exp $ -->
 
 <guide link="index.xml">
 <title>Gentoo Handbook</title>
@@ -19,8 +19,8 @@
 
 <license/>
 
-<version>0.33</version>
-<date>2006-01-12</date>
+<version>0.34</version>
+<date>2006-02-27</date>
 
 <chapter>
 <title>The Gentoo Handbook Effort</title>
@@ -121,8 +121,8 @@
 </tr>
 <tr>
   <ti>HTML</ti>
-  <ti>2005.1 Specific Networkless Installation Instructions</ti>
-  <ti><uri link="2005.1/index.xml">2005.1 Gentoo Handbooks</uri></ti>
+  <ti>2006.0 Specific Networkless Installation Instructions</ti>
+  <ti><uri link="2006.0/index.xml">2006.0 Gentoo Handbooks</uri></ti>
 </tr>
 </table>
 
@@ -130,7 +130,7 @@
 We also have release-specific handbooks which include the installation
 instructions for networkless installations using the released CDs. If you are
 interested in performing a networkless installation, please consult the <uri
-link="2005.1/index.xml">Gentoo Linux 2005.1 Handbook</uri> for your
+link="2006.0/index.xml">Gentoo Linux 2006.0 Handbook</uri> for your
 architecture.
 </p>
 



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

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-install-mips-stage.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-stage.xml,v 1.1 2006/02/27 00:55:34 fox2mike Exp $ -->

<sections>

<version>1.0</version>
<date>2006-02-27</date>

<section>
<title>Installing a Stage Tarball</title>
<subsection>
<title>Setting the Date/Time Right</title>
<body>

<p>
Before you continue you need to check your date/time and update it. A
misconfigured clock may lead to strange results in the future!
</p>

<p>
To verify the current date/time, run <c>date</c>:
</p>

<pre caption="Verifying the date/time">
# <i>date</i>
Fri Mar 29 16:21:18 CEST 2005
</pre>

<p>
If the date/time displayed is wrong, update it using the <c>date
MMDDhhmmYYYY</c> syntax (<b>M</b>onth, <b>D</b>ay, <b>h</b>our, <b>m</b>inute
and <b>Y</b>ear). For instance, to set the date to March 29th, 16:21 in the
year 2005:
</p>

<pre caption="Setting the date/time">
# <i>date 032916212005</i>
</pre>

</body>
</subsection>
<subsection>
<title>Making your Choice</title>
<body>

<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>-->

</body>
</subsection>
</section>
<section>
<title>Using a Stage from the Internet</title>
<subsection>
<title>Downloading the Stage Tarball</title>
<body>

<p>
Go to the Gentoo mountpoint at which you mounted your filesystems
(most likely <path>/gentoo</path>):
</p>

<pre caption="Going to the Gentoo mountpoint">
# <i>cd /gentoo</i>
</pre>

<p>
The table below specifies exactly which stages you need for your system.
Stages may be downloaded
off the <uri link="/main/en/mirrors.xml">official Gentoo mirrors</uri> under the
<c>releases/mips/current</c> directory.
</p>

<table>
<tr>
  <th>Endianness</th>
  <th>CPU</th>
  <th>Location</th>
</tr>
<tr>
  <ti>
    Big Endian<br />
    <e>(SGI Users)</e>
  </ti>
  <ti>
    R4000<br />
    R4400<br />
    R4600
  </ti>
  <ti><c>mips3/stage#-mips3-RELEASE.tar.bz2</c></ti>
</tr>
<tr>
  <ti>
    Big Endian<br />
    <e>(SGI Users)</e>
  </ti>
  <ti>
    R5000<br />
    RM5200<br />
    RM7000<br />
    R10000<br />
    R12000<br />
    R14000
  </ti>
  <ti><c>mips4/stage#-mips4-RELEASE.tar.bz2</c></ti>
</tr>
<tr>
  <ti>
    Little Endian<br />
    <e>(Cobalt Users)</e>
  </ti>
  <ti>
    RM5230<br />
    RM5231
  </ti>
  <ti><c>cobalt/stage#-mipsel4-RELEASE.tar.bz2</c></ti>
</tr>
</table>

<p>
If you need to go through a proxy, export the <c>http_proxy</c> and
<c>ftp_proxy</c> variables:
</p>

<pre caption="Setting proxy information for wget">
# <i>export http_proxy="http://proxy.server.com:port"</i>
# <i>export ftp_proxy="http://proxy.server.com:port"</i>
</pre>

<p>
The Gentoo/MIPS netboot images provide <c>wget</c> as a means of downloading
files.  Due to space constraints, it is not possible to provide more capable
browsers on SGI netboot images. LiveCD users may use <c>elinks</c>.
</p>

<pre caption="Fetching the tarball via wget">
# <i>wget -c http://distfiles.gentoo.org/releases/mips/mips4/stage3-mips4-2006.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:
</p>

<pre caption="Example checking integrity of a stage tarball">
# <i>md5sum -c stage3-mips4-2006.0.tar.bz2.md5</i>
stage3-mips4-2006.0.tar.bz2: OK
</pre>

</body>
</subsection>
<subsection>
<title>Unpacking the Stage Tarball</title>
<body>

<p>
Now unpack your downloaded stage onto your system. We use GNU's <c>tar</c> to
proceed as it is the easiest method:
</p>

<pre caption="Unpacking the stage">
# <i>tar -xjpf stage?-*.tar.bz2</i>
</pre>

<p>
Make sure that you use the same options (<c>-xjpf</c>). The <c>x</c> stands for
<e>Extract</e>, the <c>j</c> for <e>Decompress with bzip2</e>, the <c>p</c> for
<e>Preserve permissions</e> and the <c>f</c> to denote that we want to extract
a file, not standard input.
</p>

<p>
Now that the stage is installed, continue with <uri
link="#installing_portage">Installing Portage</uri>.
</p>

</body>
</subsection>
</section>
<!--
<section>
<title>Alternative: Using a Stage from the Installation CD</title>
<subsection>
<title>Extracting the Stage Tarball</title>
<body>

<p>
The stages on the CD reside in the <path>/mnt/cdrom/stages</path> directory. To
see a listing of available stages, use <c>ls</c>:
</p>

<pre caption="List all available stages">
# <i>ls /mnt/cdrom/stages</i>
</pre>

<p>
If the system replies with an error, you may need to mount the CD-ROM first:
</p>

<pre caption="Mounting the CD-ROM">
# <i>ls /mnt/cdrom/stages</i>
ls: /mnt/cdrom/stages: No such file or directory
# <i>mount /dev/cdroms/cdrom0 /mnt/cdrom</i>
# <i>ls /mnt/cdrom/stages</i>
</pre>

<p>
Now go into your Gentoo mountpoint (usually <path>/mnt/gentoo</path>):
</p>

<pre caption="Changing directory to /mnt/gentoo">
# <i>cd /mnt/gentoo</i>
</pre>

<p>
We will now extract the stage tarball of your choice. We will do this with the
GNU <c>tar</c> tool. Make sure you use the same options (<c>-xvjpf</c>)! Again,
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.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.0.tar.bz2</i>
</pre>

<p>
Now that the stage is installed, continue with <uri
link="#installing_portage">Installing Portage</uri>.
</p>

</body>
</subsection>
</section>-->
<section id="installing_portage">
<title>Installing Portage</title>
<subsection>
<title>Unpacking a Portage Snapshot</title>
<body>

<p>
You now have to install a Portage snapshot, a collection of files that inform
Portage what software titles you can install, which profiles are available, etc.
</p>

</body>
</subsection>
<subsection id="installing_from_Internet">
<title>Download and Install a Portage Snapshot</title>
<body>

<p>
Go to the mountpoint where you mounted your filesystem (most likely
<path>/gentoo</path>):
</p>

<pre caption="Going to the Gentoo mountpoint">
# <i>cd /gentoo</i>
</pre>

<p>
Download a portage snapshot from a <uri
link="/main/en/mirrors.xml">local mirror</uri>.
You'll find them in the <path>snapshots/</path> directory.  Transfer it to the
target system in the same manner that you did for the stage tarball.
</p>

<pre caption="Extracting the Portage snapshot">
# <i>tar -xjf portage-*.tar.bz2 -C /gentoo/usr</i>
</pre>

</body>
</subsection>
</section>

<section id="compile_options">
<title>Configuring the Compile Options</title>
<subsection>
<title>Introduction</title>
<body>

<p>
To optimize Gentoo, you can set a couple of variables which impact Portage 
behaviour. All those variables can be set as environment variables (using
<c>export</c>) but that isn't permanent. To keep your settings, Portage provides
you with <path>/etc/make.conf</path>, a configuration file for Portage. It is
this file we will edit now. 
</p>

<note>
A commented listing of all possible variables can be found in
<path>/gentoo/etc/make.conf.example</path>. For a successful Gentoo 
installation you'll only need to set the variables which are mentioned beneath.
</note>

<p>
Fire up a text editor so we can alter the optimization variables we will discuss
hereafter.  Two editors are provided, <c>vi</c> (part of Busybox) and
<c>nano</c>.  We will assume you're using <c>nano</c>.
</p>

<pre caption="Opening /etc/make.conf">
# <i>nano -w /gentoo/etc/make.conf</i>
</pre>

<p>
As you probably noticed, the <path>make.conf.example</path> file is
structured in a generic way: commented lines start with "#", other lines define
variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path>
file uses the same syntax. Several of those variables are discussed next. 
</p>

</body>
</subsection>
<!--<subsection>
<title>CHOST</title>
<body>

<warn>
Although it might be tempting for non-stage1 users, they should <e>not</e>
change the <c>CHOST</c> setting in <path>make.conf</path>. Doing so might render
their system unusable. Again: only change this variable if you use a
<e>stage1</e> installation.
</warn>

<p>
The <c>CHOST</c> variable defines what architecture <c>gcc</c> has to
compile programs for, as well as the <c>libc</c> (<c>glibc</c> or <c>µClibc</c>) used
for linking.
</p>

<table>
<tr>
  <th>Endianness</th>
  <th>Userland/ABI</th>
  <th>CHOST Setting</th>
</tr>
<tr>
  <ti>Big Endian <e>(SGI Users)</e></ti>
  <ti><c>glibc</c> <c>o32</c></ti>
  <ti>mips-unknown-linux-gnu</ti>
</tr>
<tr>
  <ti>Big Endian <e>(SGI Users)</e></ti>
  <ti><c>µClibc</c> <c>o32</c></ti>
  <ti>mips-unknown-linux-uclibc (1)</ti>
</tr>
<tr>
  <ti>Big Endian <e>(SGI Users)</e></ti>
  <ti><c>glibc</c> <c>n32</c> &amp; <c>n64</c></ti>
  <ti>mips64-unknown-linux-gnu (2)</ti>
</tr>
<tr>
  <ti>Little Endian <e>(Cobalt Users)</e></ti>
  <ti><c>glibc</c> <c>o32</c></ti>
  <ti>mipsel-unknown-linux-gnu</ti>
</tr>
<tr>
  <ti>Little Endian <e>(Cobalt Users)</e></ti>
  <ti><c>µClibc</c> <c>o32</c></ti>
  <ti>mipsel-unknown-linux-uclibc (1)</ti>
</tr>
<tr>
  <ti>Little Endian <e>(Cobalt Users)</e></ti>
  <ti><c>glibc</c> <c>n32</c> &amp; <c>n64</c></ti>
  <ti>mips64el-unknown-linux-gnu (2)</ti>
</tr>
</table>

<warn>
(1) µClibc stages are the realm of the
<uri link="/proj/en/base/embedded/">Gentoo Embedded</uri>
team, and are therefore not officially supported by the
Gentoo/MIPS team.  This <c>CHOST</c> setting is only mentioned here for
completeness.
</warn>

<warn>
(2) Currently we do not provide <c>n64</c> stages, and only provide <c>n32</c>
stages on the Big Endian MIPS4 architecture.  These are highly experimental
stages and are known to be totally broken in places.  Users are thus 
<e>highly</e> recommended to avoid these like the plague.
The only reason one would need the <c>mips64(el)</c> <c>CHOST</c>, is to use a
64-bit (<c>n32</c> or <c>n64</c>) userland.  This <c>CHOST</c> setting is only
mentioned here for completeness.
</warn>

</body>
</subsection>-->
<subsection>
<title>CFLAGS and CXXFLAGS</title>
<body>

<p>
The <c>CFLAGS</c> and <c>CXXFLAGS</c> variables define the optimization flags 
for the <c>gcc</c> C and C++ compiler respectively. Although we define those
generally here, you will only have maximum performance if you optimize these
flags for each program separately. The reason for this is because every program
is different.
</p>

<p>
In <path>make.conf</path> you should define the optimization flags you think
will make your system the most responsive <e>generally</e>. Don't place
experimental settings in this variable; too much optimization can make 
programs behave bad (crash, or even worse, malfunction).
</p>

<p>
We will not explain all possible optimization options. If you want to know
them all, read the <uri link="http://gcc.gnu.org/onlinedocs/">GNU
Online Manual(s)</uri> or the <c>gcc</c> info page (<c>info gcc</c> -- only
works on a working Linux system). The <path>make.conf.example</path> file 
itself also contains lots of examples and information; don't forget to read it 
too. 
</p>

<p>
A first setting is the <c>-march=</c> flag, which specifies the name of the
target architecture. Possible options are described in the
<path>make.conf.example</path> file (as comments).  Examples include ISA levels
(<c>mips1</c> ... <c>mips4</c>) and CPU models (<c>r4400</c>, <c>r4600</c> ...
etc).  For pure ISA level architectures, one can simply specify <c>-mips3</c>
rather than <c>-march=mips3</c>.
</p>

<pre caption="The GCC -march and -mips# settings">
<comment>(For an R4600 system...)</comment>
-march=r4600

<comment>(Any MIPS4-class CPU...)</comment>
-march=mips4

<comment>(Or just specify the ISA level directly...)</comment>
-mips4
</pre>

<p>
A second one is the <c>-O</c> flag (that is a capital O, not a zero),
which specifies the <c>gcc</c> optimization
class flag. Possible classes are <c>s</c> (for size-optimized),
<c>0</c> (zero - for no optimizations), <c>1</c>, <c>2</c> or <c>3</c> for more
speed-optimization flags (every class has the same flags as the one before, plus
some extras). For instance, for a class-2 optimization:
</p>

<pre caption="The GCC O setting">
-O2
</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
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).
</p>

<p>
Another popular optimization flag is <c>-pipe</c> (use pipes rather than
temporary files for communication between the various stages of compilation).
</p>

<p>
Mind you that using <c>-fomit-frame-pointer</c> (which doesn't keep the frame 
pointer in a register for functions that don't need one) might have serious
repercussions on the debugging of applications!
</p>

<p>
When you define the <c>CFLAGS</c> and <c>CXXFLAGS</c>, you should combine
several optimization flags, like in the following example:
</p>

<pre caption="Defining the CFLAGS and CXXFLAGS variable">
CFLAGS="-mabi=32 -mips4 -pipe -O2"
CXXFLAGS="${CFLAGS}"                  <comment># Use the same settings for both variables</comment>
</pre>

</body>
</subsection>
<subsection>
<title>MAKEOPTS</title>
<body>

<p>
With <c>MAKEOPTS</c> you define how many parallel compilations should occur when
you install a package. A good choice is the number of CPUs in your system plus 
one, but this guideline isn't always perfect.
</p>

<pre caption="MAKEOPTS for a regular, 1-CPU system">
MAKEOPTS="-j2"
</pre>

</body>
</subsection>
<subsection>
<title>Ready, Set, Go!</title>
<body>

<p>
Update your <path>/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>

</body>
</subsection>
</section>
</sections>



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