swift 05/10/09 16:33:54
Modified: xml/htdocs/doc/en/handbook 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-x86-medium.xml
Log:
#105809 - Stage* description updates
Revision Changes Path
1.36 +46 -33 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.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-alpha-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-alpha-medium.xml.diff?r1=1.35&r2=1.36&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.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- hb-install-alpha-medium.xml 25 Aug 2005 19:53:25 -0000 1.35
+++ hb-install-alpha-medium.xml 9 Oct 2005 16:33:54 -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-alpha-medium.xml,v
1.35 2005/08/25 19:53:25 neysx Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>2.7</version>
-<date>2005-08-25</date>
+<version>2.8</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -102,12 +102,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -118,21 +122,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -160,9 +162,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -184,18 +194,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -210,8 +212,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -233,20 +236,25 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
</section>
+
<section>
<title>The Gentoo Installation CDs</title>
<subsection>
@@ -382,6 +390,11 @@
installation.
</p>
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage-3 tarball you use.
+</p>
+
</body>
</subsection>
</section>
1.37 +46 -33 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.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-amd64-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-amd64-medium.xml.diff?r1=1.36&r2=1.37&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.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- hb-install-amd64-medium.xml 9 Aug 2005 09:43:58 -0000 1.36
+++ hb-install-amd64-medium.xml 9 Oct 2005 16:33:54 -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/2.5 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml,v
1.36 2005/08/09 09:43:58 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-amd64-medium.xml,v
1.37 2005/10/09 16:33:54 swift Exp $ -->
<sections>
-<version>2.7</version>
-<date>2005-08-09</date>
+<version>2.8</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -104,12 +104,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -120,21 +124,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -162,9 +164,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -186,18 +196,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -212,8 +214,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -235,20 +238,25 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
</section>
+
<section>
<title>The Gentoo Installation CDs</title>
<subsection>
@@ -385,6 +393,11 @@
Gentoo installation.
</p>
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage-3 tarball you use.
+</p>
+
</body>
</subsection>
</section>
1.33 +54 -29 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.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-hppa-medium.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-hppa-medium.xml.diff?r1=1.32&r2=1.33&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.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- hb-install-hppa-medium.xml 10 Aug 2005 11:13:37 -0000 1.32
+++ hb-install-hppa-medium.xml 9 Oct 2005 16:33:54 -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-hppa-medium.xml,v
1.32 2005/08/10 11:13:37 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-medium.xml,v
1.33 2005/10/09 16:33:54 swift Exp $ -->
<sections>
-<version>1.26</version>
-<date>2005-08-10</date>
+<version>1.27</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -102,12 +102,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -118,26 +122,30 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
+ <ti>Suitable for powerusers and developers who know what they are doing</ti>
</tr>
<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <th>-</th>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
- <ti>Takes a long time to finish the installation</ti>
+ <ti>
+ If you don't intend to tweak the settings, it is a waste of time
+ </ti>
</tr>
<tr>
<th>-</th>
<ti>
- If you don't intend to tweak the settings, it is a waste of time
+ Requires a working Internet connection during the installation
</ti>
</tr>
</table>
@@ -154,9 +162,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -178,15 +194,13 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
+ <ti>
+ Requires a working Internet connection during the installation
+ </ti>
</tr>
</table>
@@ -198,8 +212,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -221,20 +236,25 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
</section>
+
<section>
<title>The Gentoo Installation CDs</title>
<subsection>
@@ -368,6 +388,11 @@
installation.
</p>
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage-3 tarball you use.
+</p>
+
</body>
</subsection>
</section>
1.15 +43 -37 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.15&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.15&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.14&r2=1.15&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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- hb-install-mips-medium.xml 11 Jul 2005 07:25:59 -0000 1.14
+++ hb-install-mips-medium.xml 9 Oct 2005 16:33:54 -0000 1.15
@@ -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.14 2005/07/11 07:25:59 fox2mike Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>1.9</version>
-<date>2005-07-11</date>
+<version>1.10</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -69,9 +69,9 @@
<ul>
<li>
- A stage1 file contains nothing more than a compiler (C only, no C++),
- Portage (Gentoo's software management system) and a couple of
- packages on which the compiler or Portage depends.
+ 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
@@ -102,12 +102,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -118,21 +122,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -160,9 +162,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -184,18 +194,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -210,8 +212,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -233,20 +236,23 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
-
<subsection>
<title>A note about Processor Architectures</title>
<body>
1.48 +46 -33 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.48&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.48&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.47&r2=1.48&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.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- hb-install-ppc-medium.xml 25 Aug 2005 19:53:25 -0000 1.47
+++ hb-install-ppc-medium.xml 9 Oct 2005 16:33:54 -0000 1.48
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.47
2005/08/25 19:53:25 neysx Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>2.5</version>
-<date>2005-08-25</date>
+<version>2.6</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -127,12 +127,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -143,21 +147,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -185,9 +187,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -209,18 +219,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -235,8 +237,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -258,20 +261,25 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
</section>
+
<section>
<title>The Gentoo Installation CDs</title>
<subsection>
@@ -406,6 +414,11 @@
Gentoo installation.
</p>
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage-3 tarball you use.
+</p>
+
</body>
</subsection>
</section>
1.24 +41 -33 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.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-medium.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-medium.xml.diff?r1=1.23&r2=1.24&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.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-ppc64-medium.xml 15 Sep 2005 09:51:47 -0000 1.23
+++ hb-install-ppc64-medium.xml 9 Oct 2005 16:33:54 -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/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v
1.23 2005/09/15 09:51:47 rane Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>2.6</version>
-<date>2005-09-15</date>
+<version>2.7</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -110,12 +110,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -126,21 +130,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -168,9 +170,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -192,18 +202,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -218,8 +220,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -241,20 +244,25 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
</section>
+
<section>
<title>The Gentoo Installation CDs</title>
<subsection>
1.35 +46 -33 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.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-sparc-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-sparc-medium.xml.diff?r1=1.34&r2=1.35&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.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- hb-install-sparc-medium.xml 5 Sep 2005 15:22:02 -0000 1.34
+++ hb-install-sparc-medium.xml 9 Oct 2005 16:33:54 -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-sparc-medium.xml,v
1.34 2005/09/05 15:22:02 neysx Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>2.4</version>
-<date>2005-09-05</date>
+<version>2.5</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -109,12 +109,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -125,21 +129,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -167,9 +169,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -191,18 +201,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -217,8 +219,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -240,20 +243,25 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
</subsection>
</section>
+
<section>
<title>The Gentoo Installation CDs</title>
<subsection>
@@ -397,6 +405,11 @@
installation.
</p>
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage-3 tarball you use.
+</p>
+
</body>
</subsection>
</section>
1.40 +45 -33 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.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-x86-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-x86-medium.xml.diff?r1=1.39&r2=1.40&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.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- hb-install-x86-medium.xml 25 Aug 2005 19:53:25 -0000 1.39
+++ hb-install-x86-medium.xml 9 Oct 2005 16:33:54 -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-x86-medium.xml,v 1.39
2005/08/25 19:53:25 neysx Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>2.4</version>
-<date>2005-08-25</date>
+<version>2.5</version>
+<date>2005-10-09</date>
<section>
<title>Hardware Requirements</title>
@@ -99,12 +99,16 @@
</p>
<p>
-Starting from a stage1 allows you to have total control over the
-optimization settings and optional build-time functionality that is
-initially enabled on your system. This makes <e>stage1</e> installs good for
-power users who know what they are doing. It is also a great
-installation method for those who would like to know more about the
-inner workings of Gentoo Linux.
+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>
@@ -115,21 +119,19 @@
<tr>
<th>+</th>
<ti>
- Allows you to have total control over the optimization settings and
optional
- build-time functionality that is initially enabled on your system
+ Allows you to have total control over the installation routine, bootstrap
+ sequence, etc.
</ti>
</tr>
<tr>
<th>+</th>
- <ti>Suitable for powerusers that know what they are doing</ti>
-</tr>
-<tr>
- <th>+</th>
- <ti>Allows you to learn more about the inner workings of Gentoo</ti>
+ <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</ti>
+ <ti>
+ Takes a long time to finish the installation (it is the lengthiest
approach)
+ </ti>
</tr>
<tr>
<th>-</th>
@@ -157,9 +159,17 @@
</p>
<p>
-Stage2 installs allow you to skip the bootstrap process; doing this
-is fine if you are happy with the optimization settings that we chose
-for your particular stage2 tarball.
+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>
@@ -181,18 +191,10 @@
</tr>
<tr>
<th>-</th>
- <ti>You cannot tweak as much as with a stage1</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>It's still not the fastest way to install Gentoo</ti>
</tr>
<tr>
<th>-</th>
- <ti>You have to accept the optimizations we chose for the bootstrap</ti>
-</tr>
-<tr>
- <th>-</th>
<ti>
Requires a working Internet connection during the installation
</ti>
@@ -207,8 +209,9 @@
<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 of which we can't
-decide for you which one to choose.
+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>
@@ -230,15 +233,19 @@
<ti>Fastest way to get a Gentoo base system</ti>
</tr>
<tr>
- <th>-</th>
- <ti>You cannot tweak the base system - it's built already</ti>
+ <th>+</th>
+ <ti>
+ You can still tweak your system
+ </ti>
</tr>
</table>
<p>
You might be interested to know that, if you decide to use different
optimization settings after having installed Gentoo, you will be able to
-recompile your entire system with the new optimization settings.
+recompile your entire system with the new optimization settings. The same goes
+for any <c>USE</c> flag changes: Portage is intelligent enough to know what
+packages need to be rebuild.
</p>
</body>
@@ -379,6 +386,11 @@
installation.
</p>
+<p>
+If you intend to use the Packages CD to quickly install additional software,
+make sure that you use the same subarchitecture as the stage-3 tarball you use.
+</p>
+
</body>
</subsection>
</section>
--
[email protected] mailing list
