From: "swift" <swift@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: handbook-alpha.xml
Date: Fri, 11 Nov 2005 17:27:15 +0000 [thread overview]
Message-ID: <200511111727.jABHRHvA024457@robin.gentoo.org> (raw)
swift 05/11/11 17:27:15
Modified: xml/htdocs/doc/en/handbook handbook-alpha.xml
handbook-amd64.xml handbook-hppa.xml
handbook-mips.xml handbook-ppc.xml
handbook-ppc64.xml handbook-sparc.xml
handbook-x86.xml hb-install-alpha-medium.xml
hb-install-amd64-medium.xml
hb-install-hppa-medium.xml
hb-install-mips-medium.xml
hb-install-ppc-medium.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
Log:
#105809 - Moving bootstrapping/system to FAQ, outside handbook
Revision Changes Path
1.118 +5 -5 xml/htdocs/doc/en/handbook/handbook-alpha.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-alpha.xml?rev=1.118&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-alpha.xml?rev=1.118&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-alpha.xml.diff?r1=1.117&r2=1.118&cvsroot=gentoo
Index: handbook-alpha.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -r1.117 -r1.118
--- handbook-alpha.xml 13 Oct 2005 15:08:00 -0000 1.117
+++ handbook-alpha.xml 11 Nov 2005 17:27:15 -0000 1.118
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v 1.117 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v 1.118 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-alpha.xml">
<title>Gentoo Linux Alpha Handbook</title>
@@ -121,8 +121,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -170,8 +170,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we
-describe how you extract a stage-file and configure Portage.
+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"/>
</chapter>
1.126 +5 -5 xml/htdocs/doc/en/handbook/handbook-amd64.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.126&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.126&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-amd64.xml.diff?r1=1.125&r2=1.126&cvsroot=gentoo
Index: handbook-amd64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -r1.125 -r1.126
--- handbook-amd64.xml 13 Oct 2005 15:08:00 -0000 1.125
+++ handbook-amd64.xml 11 Nov 2005 17:27:15 -0000 1.126
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.125 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.126 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-amd64.xml">
<title>Gentoo Linux AMD64 Handbook</title>
@@ -121,8 +121,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -170,8 +170,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we
-describe how you extract a stage-file and configure Portage.
+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"/>
</chapter>
1.115 +5 -5 xml/htdocs/doc/en/handbook/handbook-hppa.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-hppa.xml?rev=1.115&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-hppa.xml?rev=1.115&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-hppa.xml.diff?r1=1.114&r2=1.115&cvsroot=gentoo
Index: handbook-hppa.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -r1.114 -r1.115
--- handbook-hppa.xml 13 Oct 2005 15:08:00 -0000 1.114
+++ handbook-hppa.xml 11 Nov 2005 17:27:15 -0000 1.115
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v 1.114 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v 1.115 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-hppa.xml">
<title>Gentoo Linux HPPA Handbook</title>
@@ -121,8 +121,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -170,8 +170,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we
-describe how you extract a stage-file and configure Portage.
+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"/>
</chapter>
1.105 +5 -5 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.105&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.105&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.104&r2=1.105&cvsroot=gentoo
Index: handbook-mips.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -r1.104 -r1.105
--- handbook-mips.xml 13 Oct 2005 15:08:00 -0000 1.104
+++ handbook-mips.xml 11 Nov 2005 17:27:15 -0000 1.105
@@ -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.104 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v 1.105 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-mips.xml">
<title>Gentoo Linux/MIPS Handbook</title>
@@ -124,8 +124,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -172,8 +172,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we
-describe how you extract a stage-file and configure Portage.
+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"/>
</chapter>
1.135 +5 -5 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.135&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.135&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.134&r2=1.135&cvsroot=gentoo
Index: handbook-ppc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v
retrieving revision 1.134
retrieving revision 1.135
diff -u -r1.134 -r1.135
--- handbook-ppc.xml 13 Oct 2005 15:08:00 -0000 1.134
+++ handbook-ppc.xml 11 Nov 2005 17:27:15 -0000 1.135
@@ -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.134 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.135 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-ppc.xml">
<title>Gentoo Linux PPC Handbook</title>
@@ -124,8 +124,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -173,8 +173,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we describe
-how you extract a stage-file and configure Portage.
+Gentoo installs work through a stage3 archive. In this chapter we describe
+how you extract a stage3 archive and configure Portage.
</abstract>
<include href="hb-install-stage.xml"/>
</chapter>
1.57 +5 -5 xml/htdocs/doc/en/handbook/handbook-ppc64.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?rev=1.57&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?rev=1.57&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc64.xml.diff?r1=1.56&r2=1.57&cvsroot=gentoo
Index: handbook-ppc64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- handbook-ppc64.xml 13 Oct 2005 15:08:00 -0000 1.56
+++ handbook-ppc64.xml 11 Nov 2005 17:27:15 -0000 1.57
@@ -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-ppc64.xml,v 1.56 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v 1.57 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-ppc64.xml">
<title>Gentoo Linux PPC64 Handbook</title>
@@ -121,8 +121,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -170,8 +170,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we describe
-how you extract a stage-file and configure Portage.
+Gentoo installs work through a stage3 archive. In this chapter we describe
+how you extract a stage3 archive and configure Portage.
</abstract>
<include href="hb-install-stage.xml"/>
</chapter>
1.118 +5 -5 xml/htdocs/doc/en/handbook/handbook-sparc.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-sparc.xml?rev=1.118&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-sparc.xml?rev=1.118&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-sparc.xml.diff?r1=1.117&r2=1.118&cvsroot=gentoo
Index: handbook-sparc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -r1.117 -r1.118
--- handbook-sparc.xml 13 Oct 2005 15:08:00 -0000 1.117
+++ handbook-sparc.xml 11 Nov 2005 17:27:15 -0000 1.118
@@ -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-sparc.xml,v 1.117 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v 1.118 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-sparc.xml">
<title>Gentoo Linux SPARC Handbook</title>
@@ -121,8 +121,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -170,8 +170,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we
-describe how you extract a stage-file and configure Portage.
+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"/>
</chapter>
1.145 +5 -5 xml/htdocs/doc/en/handbook/handbook-x86.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.145&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.145&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-x86.xml.diff?r1=1.144&r2=1.145&cvsroot=gentoo
Index: handbook-x86.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -r1.144 -r1.145
--- handbook-x86.xml 13 Oct 2005 15:08:00 -0000 1.144
+++ handbook-x86.xml 11 Nov 2005 17:27:15 -0000 1.145
@@ -1,7 +1,7 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book SYSTEM "/dtd/book.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.144 2005/10/13 15:08:00 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.145 2005/11/11 17:27:15 swift Exp $ -->
<book link="handbook-x86.xml">
<title>Gentoo Linux x86 Handbook</title>
@@ -121,8 +121,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4.1</version>
-<date>2005-10-13</date>
+<version>4.2</version>
+<date>2005-11-11</date>
<part>
<title>Installing Gentoo</title>
@@ -170,8 +170,8 @@
<chapter>
<title>Installing the Gentoo Installation Files</title>
<abstract>
-Gentoo installs work through so-called stage-files. In this chapter we
-describe how you extract a stage-file and configure Portage.
+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"/>
</chapter>
1.37 +26 -215 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.37&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.37&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.36&r2=1.37&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.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- hb-install-alpha-medium.xml 9 Oct 2005 16:33:54 -0000 1.36
+++ hb-install-alpha-medium.xml 11 Nov 2005 17:27:15 -0000 1.37
@@ -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-alpha-medium.xml,v 1.36 2005/10/09 16:33:54 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml,v 1.37 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.8</version>
-<date>2005-10-09</date>
+<version>2.9</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -53,208 +53,9 @@
</body>
</subsection>
</section>
-<!-- Copy/paste from the hb-install-x86-medium.xml file. -->
-<!-- START -->
-<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
1.39 +24 -215 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.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-amd64-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-amd64-medium.xml.diff?r1=1.38&r2=1.39&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.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- hb-install-amd64-medium.xml 31 Oct 2005 13:31:33 -0000 1.38
+++ hb-install-amd64-medium.xml 11 Nov 2005 17:27:15 -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-amd64-medium.xml,v 1.38 2005/10/31 13:31:33 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml,v 1.39 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.9</version>
-<date>2005-10-31</date>
+<version>2.10</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -58,206 +58,6 @@
<!-- Copy/paste from hb-install-x86-medium.xml -->
<!-- START -->
<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
-</p>
-
-<table>
1.35 +24 -215 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.35&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.35&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.34&r2=1.35&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.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- hb-install-hppa-medium.xml 25 Oct 2005 17:27:35 -0000 1.34
+++ hb-install-hppa-medium.xml 11 Nov 2005 17:27:15 -0000 1.35
@@ -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-hppa-medium.xml,v 1.34 2005/10/25 17:27:35 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml,v 1.35 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>1.27</version>
-<date>2005-10-09</date>
+<version>1.28</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -56,206 +56,6 @@
<!-- Copy/paste from hb-install-x86-medium.xml -->
<!-- START -->
<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
-</p>
-
-<table>
1.16 +21 -204 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.16&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.16&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.15&r2=1.16&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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- hb-install-mips-medium.xml 9 Oct 2005 16:33:54 -0000 1.15
+++ hb-install-mips-medium.xml 11 Nov 2005 17:27:15 -0000 1.16
@@ -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.15 2005/10/09 16:33:54 swift Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>1.10</version>
-<date>2005-10-09</date>
+<version>1.11</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -51,208 +51,9 @@
</body>
</subsection>
</section>
-<!-- Only the stuff about the stages is replicated from the
- hb-install-x86-medium.xml file since MIPS uses netbooting
- -->
-<!-- START -->
-<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
1.49 +24 -215 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.49&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.49&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.48&r2=1.49&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.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- hb-install-ppc-medium.xml 9 Oct 2005 16:33:54 -0000 1.48
+++ hb-install-ppc-medium.xml 11 Nov 2005 17:27:15 -0000 1.49
@@ -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.48 2005/10/09 16:33:54 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.49 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.6</version>
-<date>2005-10-09</date>
+<version>2.7</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -81,206 +81,6 @@
<!-- Copy/paste from hb-install-x86-medium.xml (with s/x86/ppc/) -->
<!-- START -->
<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
-</p>
-
-<table>
1.25 +21 -211 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.25&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.25&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.24&r2=1.25&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.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- hb-install-ppc64-medium.xml 9 Oct 2005 16:33:54 -0000 1.24
+++ hb-install-ppc64-medium.xml 11 Nov 2005 17:27:15 -0000 1.25
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v 1.24 2005/10/09 16:33:54 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v 1.25 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.7</version>
-<date>2005-10-09</date>
+<version>2.8</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -64,206 +64,6 @@
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ -->
<!-- START -->
<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
-</p>
-
-<table>
1.36 +24 -215 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.36&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.36&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.35&r2=1.36&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.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- hb-install-sparc-medium.xml 9 Oct 2005 16:33:54 -0000 1.35
+++ hb-install-sparc-medium.xml 11 Nov 2005 17:27:15 -0000 1.36
@@ -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-sparc-medium.xml,v 1.35 2005/10/09 16:33:54 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-medium.xml,v 1.36 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.5</version>
-<date>2005-10-09</date>
+<version>2.6</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -63,206 +63,6 @@
<!-- Warning: The part originally contains "x86" -->
<!-- START -->
<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
-</p>
-
-<table>
1.90 +17 -106 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.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-stage.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-stage.xml.diff?r1=1.89&r2=1.90&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.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- hb-install-stage.xml 13 Aug 2005 21:21:30 -0000 1.89
+++ hb-install-stage.xml 11 Nov 2005 17:27:15 -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/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.89 2005/08/13 21:21:30 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.90 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.5</version>
-<date>2005-08-13</date>
+<version>2.6</version>
+<date>2005-11-11</date>
<section>
<title>Installing a Stage Tarball</title>
@@ -49,8 +49,8 @@
<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
+The next step you need to perform is to install the <e>stage3</e> tarball
+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
@@ -124,14 +124,19 @@
</pre>
<p>
+Make sure you download a stage3 tarball - installations using a stage1 or stage2
+tarball are not supported anymore.
+</p>
+
+<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 x86 stage tarball:
</p>
<pre caption="Example checking integrity of a stage tarball">
-# <i>md5sum -c stage1-x86-2005.1.tar.bz2.md5</i>
-stage1-x86-2005.1.tar.bz2: OK
+# <i>md5sum -c stage3-x86-2005.1.tar.bz2.md5</i>
+stage3-x86-2005.1.tar.bz2: OK
</pre>
</body>
@@ -146,7 +151,7 @@
</p>
<pre caption="Unpacking the stage">
-# <i>tar -xvjpf stage?-*.tar.bz2</i>
+# <i>tar -xvjpf stage3-*.tar.bz2</i>
</pre>
<p>
@@ -340,105 +345,11 @@
<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. The possibilities are:
-</p>
-
-<table>
-<tr>
- <th>Architecture</th>
- <th>Subarchitecture</th>
- <th>CHOST Setting</th>
-</tr>
-<tr>
- <ti>x86</ti>
- <ti>i386</ti>
- <ti>i386-pc-linux-gnu</ti>
-</tr>
-<tr>
- <ti>x86</ti>
- <ti>i486</ti>
- <ti>i486-pc-linux-gnu</ti>
-</tr>
-<tr>
- <ti>x86</ti>
- <ti>i586</ti>
- <ti>i586-pc-linux-gnu</ti>
-</tr>
-<tr>
- <ti>x86</ti>
- <ti>i686 and above (incl. athlon)</ti>
- <ti>i686-pc-linux-gnu</ti>
-</tr>
-<tr>
- <ti>alpha</ti>
- <ti></ti>
- <ti>alpha-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>ppc</ti>
- <ti></ti>
- <ti>powerpc-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>ppc64</ti>
- <ti></ti>
- <ti>powerpc64-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>sparc</ti>
- <ti></ti>
- <ti>sparc-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>sparc64</ti>
- <ti></ti>
- <ti>sparc-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>hppa</ti>
- <ti>(generic)</ti>
- <ti>hppa-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>hppa</ti>
- <ti>pa7000</ti>
- <ti>hppa1.1-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>hppa</ti>
- <ti>pa8000 and above</ti>
- <ti>hppa2.0-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>mips</ti>
- <ti></ti>
- <ti>mips-unknown-linux-gnu</ti>
-</tr>
-<tr>
- <ti>amd64</ti>
- <ti></ti>
- <ti>x86_64-pc-linux-gnu</ti>
-</tr>
-</table>
-
-<p>
-Please, make sure that you use the <e>correct</e> CHOST setting. For instance,
-the CHOST setting for sparc64 still is <c>sparc-unknown-linux-gnu</c> and
-<e>not</e> <c>sparc64-unknown-linux-gnu</c>!
-</p>
-
<p>
-Users interested in bootstrapping their entire system with NPTL support on an
-x86 system need to set their CHOST to <c>i586-pc-linux-gnu</c> or higher.
+The <c>CHOST</c> variable declares the target build host for your system. This
+variable should already be set to the correct value. <brite>Do not edit
+it</brite> as that might break your system. If the <c>CHOST</c> variable does
+not look correct to you, you might be using the wrong stage3 tarball.
</p>
</body>
1.85 +9 -203 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.85&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.85&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.84&r2=1.85&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.84
retrieving revision 1.85
diff -u -r1.84 -r1.85
--- hb-install-system.xml 16 Aug 2005 22:14:44 -0000 1.84
+++ hb-install-system.xml 11 Nov 2005 17:27:15 -0000 1.85
@@ -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.84 2005/08/16 22:14:44 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.85 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.11</version>
-<date>2005-08-17</date>
+<version>2.12</version>
+<date>2005-11-11</date>
<section>
<title>Chrooting</title>
@@ -124,6 +124,10 @@
</body>
</subsection>
+</section>
+
+<section>
+<title>Configuring Portage</title>
<subsection>
<title>Updating the Portage tree</title>
<body>
@@ -341,8 +345,7 @@
after compiling <c>glibc</c> a full set of all available locales will be
created. As of now you can activate the <c>userlocales</c> USE flag and specify
only the locales you will need in <path>/etc/locales.build</path>. Only do this
-if you know what locales to choose. This will not work for the bootstrapping,
-but when you recompile glibc afterwards it will.
+if you know what locales to choose.
</p>
<pre caption="Activate the userlocales USE flag especially for glibc">
@@ -370,208 +373,11 @@
de_DE@euro/ISO-8859-15
</pre>
-</body>
-</subsection>
-</section>
-<section>
-<title>Differences between Stage1, Stage2 and Stage3</title>
-<body>
-
-<p>
-Now take a seat and think of your previous steps. We asked you to
-select a <e>stage1</e>, <e>stage2</e> or <e>stage3</e> and warned you
-that your choice is important for further installation steps. Well, this
-is the first place where your choice defines the subsequent steps.
-</p>
-
-<ul>
-<li>
- If you chose <e>stage1</e>, then you have to follow <e>both</e> steps in
- this chapter (starting with <uri link="#doc_chap3">Progressing from Stage1
- to Stage2</uri>)
-</li>
-<li>
- If you chose <e>stage2</e> you only can skip the first step
- and immediately start with the second one (<uri link="#doc_chap4">Progressing
- from Stage2 to Stage3</uri>)
-</li>
-<li>
- If you chose <e>stage3</e> then you can skip both
- steps and continue with <uri link="?part=1&chap=7">Configuring the
- Kernel</uri>
-</li>
-</ul>
-
-</body>
-</section>
-<section>
-<title>Progressing from Stage1 to Stage2</title>
-<subsection>
-<title>Introduction to Bootstrapping</title>
-<body>
-
-<p>
-So, you want to compile everything from scratch? Okay then :-)
-</p>
-
-<p>
-In this step, we will <e>bootstrap</e> your Gentoo system. This takes a
-long time, but the result is a system that has been optimized from the
-ground up for your specific machine and needs.
-</p>
-
-<p>
-<e>Bootstrapping</e> means building the GNU C Library, GNU Compiler
-Collection and several other key system programs.
-</p>
-
-<p>
-Before starting the bootstrap, you might want to download all necessary
-sourcecode first. If you do not want to do this, continue
-with <uri link="#bootstrap">Bootstrapping the System</uri>.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>Optional: Downloading the Sources First</title>
-<body>
-
-<p>
-If you haven't copied over all source code before, then the bootstrap
-script will download all necessary files. If you want to
-download the source code first and later bootstrap the system (for instance
-because you don't want to have your internet connection open during the
-compilation) use the <e>-f</e> option of the bootstrap script, which will
-fetch (hence the letter <e>f</e>) all source code for you.
-</p>
-
-<pre caption = "Downloading the necessary sources">
-# <i>cd /usr/portage</i>
-# <i>scripts/bootstrap.sh -f</i>
-</pre>
-
-</body>
-</subsection>
-<subsection id="bootstrap">
-<title>Bootstrapping the System</title>
-<body>
-
-<p>
-Okay then, take your keyboard and punch in the next commands to start
-the bootstrap. Then go amuse yourself with something else because this step
-takes quite some time to finish.
-</p>
-
-<pre caption = "Bootstrapping the system">
-# <i>cd /usr/portage</i>
-# <i>scripts/bootstrap.sh</i>
-</pre>
-
-<p>
-Now continue with the next step, <uri link="#doc_chap4">Progressing from Stage2
-to Stage3</uri>.
-</p>
-
-</body>
-</subsection>
-</section>
-<section>
-<title>Progressing from Stage2 to Stage3</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-If you are reading this section, then you have a bootstrapped system
-(either because you bootstrapped it previously, or you are using a
-<e>stage2</e>). Then it is now time to build all system packages.
-</p>
-
-<p>
-<e>All</e> system packages? No, not really. In this step, you will build
-the system packages of which there are no alternatives to use.
-Some system packages have several alternatives (such as system loggers)
-and as Gentoo is all about choices, we don't want to force one upon you.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>Optional: Viewing what will be done</title>
-<body>
-
-<p>
-If you want to know what packages will be installed, execute <c>emerge
---pretend --emptytree system</c>. This will list all packages that will be
-built. As this list is pretty big, you should also use a pager like
-<c>less</c> or <c>more</c> to go up and down the list.
-</p>
-
-<pre caption = "View what 'emerge system' will do">
-# <i>emerge --pretend --emptytree system | less</i>
-</pre>
-
-<p>
-Note that, if you haven't touched the default CFLAGS/CXXFLAGS setting, using
-<c>emerge --pretend --newuse system</c> is sufficient: it will rebuild the
-applications that are affected by a change in USE flags (compared to the USE
-flag we used while building the stage2). If you didn't touch
-the USE flag either, why are you running a stage2 installation then?
-</p>
-
1.41 +24 -214 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.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-x86-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-x86-medium.xml.diff?r1=1.40&r2=1.41&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.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- hb-install-x86-medium.xml 9 Oct 2005 16:33:54 -0000 1.40
+++ hb-install-x86-medium.xml 11 Nov 2005 17:27:15 -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-x86-medium.xml,v 1.40 2005/10/09 16:33:54 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86-medium.xml,v 1.41 2005/11/11 17:27:15 swift Exp $ -->
<sections>
-<version>2.5</version>
-<date>2005-10-09</date>
+<version>2.6</version>
+<date>2005-11-11</date>
<section>
<title>Hardware Requirements</title>
@@ -53,205 +53,6 @@
<!-- This part can be propagated to the other architectures as well. -->
<!-- START -->
<section>
-<title>The Gentoo Installation Approaches</title>
-<subsection>
-<title>Introduction</title>
-<body>
-
-<p>
-Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
-A stage file is a tarball (compressed archive) that contains a minimal
-environment.
-</p>
-
-<ul>
- <li>
- A stage1 file contains nothing more than a compiler, Portage (Gentoo's
- software management system) and a couple of packages on which the compiler
- or Portage depends.
- </li>
- <li>
- A stage2 file contains a so-called bootstrapped system, a minimal
- environment from which one can start building all other necessary
- applications that make a Gentoo environment complete.
- </li>
- <li>
- A stage3 file contains a prebuilt minimal system which is almost fully
- deployable. It only lacks a few applications where you, the Gentoo user,
- needs to choose which one you want to install.
- </li>
-</ul>
-
-<p>
-To help you decide what stage file you want to use, we have written down the
-major advantages and disadvantages of each stage file.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage1 Approach</title>
-<body>
-
-<p>
-A <e>stage1</e> is used when you want to bootstrap and build the entire system
-from scratch.
-</p>
-
-<p>
-This approach builds core system packages that are vital to your system and is
-used by Gentoo developers to prepare the Gentoo release media. It is a great
-installation method for those who would like to learn more about the inner
-workings of bootstrapping, toolchains and the like.
-</p>
-
-<p>
-However, if you do not plan to tweak the bootstrapping instructions in the
-<path>bootstrap.sh</path> script written by the Gentoo developers, then a
-stage1 approach has no benefits for you.
-</p>
-
-<table>
-<tr>
- <th>Stage1</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- Allows you to have total control over the installation routine, bootstrap
- sequence, etc.
- </ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Suitable for powerusers and developers who know what they are doing</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Takes a long time to finish the installation (it is the lengthiest approach)
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- If you don't intend to tweak the settings, it is a waste of time
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage2 Approach</title>
-<body>
-
-<p>
-A <e>stage2</e> is used for building the entire system from a bootstrapped
-"semi-compiled" state.
-</p>
-
-<p>
-When you perform a stage2 installation approach, you will build all system
-packages (core packages, including toolchain) using your specific <c>USE</c>,
-<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be
-optimized to your preference.
-</p>
-
-<p>
-However, this installation takes some time and if you do not intend to change
-the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good
-default", using this approach only makes sense if your <c>USE</c> variable is
-sufficiently different from the default <c>USE</c> we provide.
-</p>
-
-<table>
-<tr>
- <th>Stage2</th>
- <th>Pros and Cons</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>You don't need to bootstrap</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Faster than starting with stage1</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>You can still tweak your settings</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>It's still not the fastest way to install Gentoo</ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Requires a working Internet connection during the installation
- </ti>
-</tr>
-</table>
-
-</body>
-</subsection>
-<subsection>
-<title>A Stage3 Approach</title>
-<body>
-
-<p>
-A <e>stage3</e> installation contains a basic Gentoo Linux system that has been
-built for you. You will only need to build a few packages (such as system
-logger, networking tools, ...) before you can boot into a base Gentoo
-installation.
-</p>
-
-<p>
-Choosing to go with a stage3 allows for the fastest install of Gentoo
-Linux, but also means that your base system will have the optimization
-settings that we chose for you (which to be honest, are good settings
-and were carefully chosen to enhance performance while maintaining
-stability). Stage3 is also required if you want to install Gentoo using
-prebuilt packages or without a network connection.
-</p>
-
-<table>
1.55 +7 -14 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.55&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.55&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.54&r2=1.55&cvsroot=gentoo
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- index.xml 8 Aug 2005 13:48:40 -0000 1.54
+++ index.xml 11 Nov 2005 17:27:15 -0000 1.55
@@ -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.54 2005/08/08 13:48:40 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.55 2005/11/11 17:27:15 swift Exp $ -->
<guide link="index.xml">
<title>Gentoo Handbook</title>
@@ -19,8 +19,8 @@
<license/>
-<version>0.29</version>
-<date>2005-08-08</date>
+<version>0.30</version>
+<date>2005-11-11</date>
<chapter>
<title>The Gentoo Handbook Effort</title>
@@ -290,9 +290,7 @@
<p>
By not separating the instructions for each possible option, the user can view
the results of the other choices easily. This provides a <b>better view on the
-installation instructions</b> for the user: even though they chose - for
-instance - stage3, they are easily informed about what stage2 or stage1 does.
-Not hiding these instructions is a good thing.
+installation instructions</b> for the user.
</p>
</body>
@@ -302,14 +300,9 @@
<body>
<p>
-You are reading the wrong Gentoo Handbook.
-</p>
-
-<p>
-The release-specific Gentoo Handbooks (such as the 2005.0 one) are meant for
-networkless installations only. Running a stage1 or stage2 installation requires
-source code that isn't available on the universal installation CD, so you would
-need a working Internet connection to do a stage1 or stage2 installation.
+Instructions on using a stage1 or stage2 tarball are now available in the <uri
+link="/doc/en/faq.xml#stage12">Gentoo FAQ</uri>. A stage3 installation is the
+only supported installation as of now.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-11-11 17:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 17:27 swift [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-30 23:32 [gentoo-doc-cvs] cvs commit: handbook-alpha.xml Josh Saddler
2007-03-19 6:54 Josh Saddler
2006-08-02 22:09 Lukasz Damentko
2006-02-27 18:01 Shyam Mani
2006-02-27 1:04 Shyam Mani
2006-02-27 0:11 Shyam Mani
2006-02-22 5:32 Shyam Mani
2006-02-10 17:45 Shyam Mani
2006-02-05 9:51 Shyam Mani
2006-02-01 18:38 Shyam Mani
2005-12-19 12:36 Jan Kundrat
2005-12-19 12:28 Jan Kundrat
2005-10-13 15:08 Xavier Neys
2005-10-13 15:08 Xavier Neys
2005-10-09 23:28 Lukasz Damentko
2005-10-09 23:24 Lukasz Damentko
2005-08-08 14:00 swift
2005-08-08 13:27 swift
2005-08-08 13:24 swift
2005-08-08 13:16 swift
2005-07-28 14:33 Sven Vermeulen
2005-07-28 14:33 Sven Vermeulen
2005-07-28 14:33 Sven Vermeulen
2005-07-28 14:33 Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511111727.jABHRHvA024457@robin.gentoo.org \
--to=swift@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox