| … | |
… | |
| 2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3 | |
3 | |
| 4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 6 | |
6 | |
| 7 | <!-- $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 $ --> |
7 | <!-- $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 $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>2.7</version> |
11 | <version>2.8</version> |
| 12 | <date>2005-10-09</date> |
12 | <date>2005-11-11</date> |
| 13 | |
13 | |
| 14 | <section> |
14 | <section> |
| 15 | <title>Hardware Requirements</title> |
15 | <title>Hardware Requirements</title> |
| 16 | <subsection> |
16 | <subsection> |
| 17 | <title>Introduction</title> |
17 | <title>Introduction</title> |
| … | |
… | |
| 61 | </body> |
61 | </body> |
| 62 | </subsection> |
62 | </subsection> |
| 63 | </section> |
63 | </section> |
| 64 | <!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
64 | <!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
| 65 | <!-- START --> |
65 | <!-- START --> |
| 66 | <section> |
|
|
| 67 | <title>The Gentoo Installation Approaches</title> |
|
|
| 68 | <subsection> |
|
|
| 69 | <title>Introduction</title> |
|
|
| 70 | <body> |
|
|
| 71 | |
|
|
| 72 | <p> |
|
|
| 73 | Gentoo Linux can be installed using one of three <e>stage</e> tarball files. |
|
|
| 74 | A stage file is a tarball (compressed archive) that contains a minimal |
|
|
| 75 | environment. |
|
|
| 76 | </p> |
|
|
| 77 | |
|
|
| 78 | <ul> |
|
|
| 79 | <li> |
|
|
| 80 | A stage1 file contains nothing more than a compiler, Portage (Gentoo's |
|
|
| 81 | software management system) and a couple of packages on which the compiler |
|
|
| 82 | or Portage depends. |
|
|
| 83 | </li> |
|
|
| 84 | <li> |
|
|
| 85 | A stage2 file contains a so-called bootstrapped system, a minimal |
|
|
| 86 | environment from which one can start building all other necessary |
|
|
| 87 | applications that make a Gentoo environment complete. |
|
|
| 88 | </li> |
|
|
| 89 | <li> |
|
|
| 90 | A stage3 file contains a prebuilt minimal system which is almost fully |
|
|
| 91 | deployable. It only lacks a few applications where you, the Gentoo user, |
|
|
| 92 | needs to choose which one you want to install. |
|
|
| 93 | </li> |
|
|
| 94 | </ul> |
|
|
| 95 | |
|
|
| 96 | <p> |
|
|
| 97 | To help you decide what stage file you want to use, we have written down the |
|
|
| 98 | major advantages and disadvantages of each stage file. |
|
|
| 99 | </p> |
|
|
| 100 | |
|
|
| 101 | </body> |
|
|
| 102 | </subsection> |
|
|
| 103 | <subsection> |
|
|
| 104 | <title>A Stage1 Approach</title> |
|
|
| 105 | <body> |
|
|
| 106 | |
|
|
| 107 | <p> |
|
|
| 108 | A <e>stage1</e> is used when you want to bootstrap and build the entire system |
|
|
| 109 | from scratch. |
|
|
| 110 | </p> |
|
|
| 111 | |
|
|
| 112 | <p> |
|
|
| 113 | This approach builds core system packages that are vital to your system and is |
|
|
| 114 | used by Gentoo developers to prepare the Gentoo release media. It is a great |
|
|
| 115 | installation method for those who would like to learn more about the inner |
|
|
| 116 | workings of bootstrapping, toolchains and the like. |
|
|
| 117 | </p> |
|
|
| 118 | |
|
|
| 119 | <p> |
|
|
| 120 | However, if you do not plan to tweak the bootstrapping instructions in the |
|
|
| 121 | <path>bootstrap.sh</path> script written by the Gentoo developers, then a |
|
|
| 122 | stage1 approach has no benefits for you. |
|
|
| 123 | </p> |
|
|
| 124 | |
|
|
| 125 | <table> |
|
|
| 126 | <tr> |
|
|
| 127 | <th>Stage1</th> |
|
|
| 128 | <th>Pros and Cons</th> |
|
|
| 129 | </tr> |
|
|
| 130 | <tr> |
|
|
| 131 | <th>+</th> |
|
|
| 132 | <ti> |
|
|
| 133 | Allows you to have total control over the installation routine, bootstrap |
|
|
| 134 | sequence, etc. |
|
|
| 135 | </ti> |
|
|
| 136 | </tr> |
|
|
| 137 | <tr> |
|
|
| 138 | <th>+</th> |
|
|
| 139 | <ti>Suitable for powerusers and developers who know what they are doing</ti> |
|
|
| 140 | </tr> |
|
|
| 141 | <tr> |
|
|
| 142 | <th>-</th> |
|
|
| 143 | <ti> |
|
|
| 144 | Takes a long time to finish the installation (it is the lengthiest approach) |
|
|
| 145 | </ti> |
|
|
| 146 | </tr> |
|
|
| 147 | <tr> |
|
|
| 148 | <th>-</th> |
|
|
| 149 | <ti> |
|
|
| 150 | If you don't intend to tweak the settings, it is a waste of time |
|
|
| 151 | </ti> |
|
|
| 152 | </tr> |
|
|
| 153 | <tr> |
|
|
| 154 | <th>-</th> |
|
|
| 155 | <ti> |
|
|
| 156 | Requires a working Internet connection during the installation |
|
|
| 157 | </ti> |
|
|
| 158 | </tr> |
|
|
| 159 | </table> |
|
|
| 160 | |
|
|
| 161 | </body> |
|
|
| 162 | </subsection> |
|
|
| 163 | <subsection> |
|
|
| 164 | <title>A Stage2 Approach</title> |
|
|
| 165 | <body> |
|
|
| 166 | |
|
|
| 167 | <p> |
|
|
| 168 | A <e>stage2</e> is used for building the entire system from a bootstrapped |
|
|
| 169 | "semi-compiled" state. |
|
|
| 170 | </p> |
|
|
| 171 | |
|
|
| 172 | <p> |
|
|
| 173 | When you perform a stage2 installation approach, you will build all system |
|
|
| 174 | packages (core packages, including toolchain) using your specific <c>USE</c>, |
|
|
| 175 | <c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be |
|
|
| 176 | optimized to your preference. |
|
|
| 177 | </p> |
|
|
| 178 | |
|
|
| 179 | <p> |
|
|
| 180 | However, this installation takes some time and if you do not intend to change |
|
|
| 181 | the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good |
|
|
| 182 | default", using this approach only makes sense if your <c>USE</c> variable is |
|
|
| 183 | sufficiently different from the default <c>USE</c> we provide. |
|
|
| 184 | </p> |
|
|
| 185 | |
|
|
| 186 | <table> |
|
|
| 187 | <tr> |
|
|
| 188 | <th>Stage2</th> |
|
|
| 189 | <th>Pros and Cons</th> |
|
|
| 190 | </tr> |
|
|
| 191 | <tr> |
|
|
| 192 | <th>+</th> |
|
|
| 193 | <ti>You don't need to bootstrap</ti> |
|
|
| 194 | </tr> |
|
|
| 195 | <tr> |
|
|
| 196 | <th>+</th> |
|
|
| 197 | <ti>Faster than starting with stage1</ti> |
|
|
| 198 | </tr> |
|
|
| 199 | <tr> |
|
|
| 200 | <th>+</th> |
|
|
| 201 | <ti>You can still tweak your settings</ti> |
|
|
| 202 | </tr> |
|
|
| 203 | <tr> |
|
|
| 204 | <th>-</th> |
|
|
| 205 | <ti>It's still not the fastest way to install Gentoo</ti> |
|
|
| 206 | </tr> |
|
|
| 207 | <tr> |
|
|
| 208 | <th>-</th> |
|
|
| 209 | <ti> |
|
|
| 210 | Requires a working Internet connection during the installation |
|
|
| 211 | </ti> |
|
|
| 212 | </tr> |
|
|
| 213 | </table> |
|
|
| 214 | |
|
|
| 215 | </body> |
|
|
| 216 | </subsection> |
|
|
| 217 | <subsection> |
|
|
| 218 | <title>A Stage3 Approach</title> |
|
|
| 219 | <body> |
|
|
| 220 | |
|
|
| 221 | <p> |
|
|
| 222 | A <e>stage3</e> installation contains a basic Gentoo Linux system that has been |
|
|
| 223 | built for you. You will only need to build a few packages (such as system |
|
|
| 224 | logger, networking tools, ...) before you can boot into a base Gentoo |
|
|
| 225 | installation. |
|
|
| 226 | </p> |
|
|
| 227 | |
|
|
| 228 | <p> |
|
|
| 229 | Choosing to go with a stage3 allows for the fastest install of Gentoo |
|
|
| 230 | Linux, but also means that your base system will have the optimization |
|
|
| 231 | settings that we chose for you (which to be honest, are good settings |
|
|
| 232 | and were carefully chosen to enhance performance while maintaining |
|
|
| 233 | stability). Stage3 is also required if you want to install Gentoo using |
|
|
| 234 | prebuilt packages or without a network connection. |
|
|
| 235 | </p> |
|
|
| 236 | |
|
|
| 237 | <table> |
|
|
| 238 | <tr> |
|
|
| 239 | <th>Stage3</th> |
|
|
| 240 | <th>Pros and Cons</th> |
|
|
| 241 | </tr> |
|
|
| 242 | <tr> |
|
|
| 243 | <th>+</th> |
|
|
| 244 | <ti>Fastest way to get a Gentoo base system</ti> |
|
|
| 245 | </tr> |
|
|
| 246 | <tr> |
|
|
| 247 | <th>+</th> |
|
|
| 248 | <ti> |
|
|
| 249 | You can still tweak your system |
|
|
| 250 | </ti> |
|
|
| 251 | </tr> |
|
|
| 252 | </table> |
|
|
| 253 | |
|
|
| 254 | <p> |
|
|
| 255 | You might be interested to know that, if you decide to use different |
|
|
| 256 | optimization settings after having installed Gentoo, you will be able to |
|
|
| 257 | recompile your entire system with the new optimization settings. The same goes |
|
|
| 258 | for any <c>USE</c> flag changes: Portage is intelligent enough to know what |
|
|
| 259 | packages need to be rebuild. |
|
|
| 260 | </p> |
|
|
| 261 | |
|
|
| 262 | </body> |
|
|
| 263 | </subsection> |
|
|
| 264 | </section> |
|
|
| 265 | |
|
|
| 266 | <section> |
66 | <section> |
| 267 | <title>The Gentoo Installation CDs</title> |
67 | <title>The Gentoo Installation CDs</title> |
| 268 | <subsection> |
68 | <subsection> |
| 269 | <title>Introduction</title> |
69 | <title>Introduction</title> |
| 270 | <body> |
70 | <body> |
| … | |
… | |
| 319 | <tr> |
119 | <tr> |
| 320 | <th>+</th> |
120 | <th>+</th> |
| 321 | <ti>Smallest download</ti> |
121 | <ti>Smallest download</ti> |
| 322 | </tr> |
122 | </tr> |
| 323 | <tr> |
123 | <tr> |
| 324 | <th>+</th> |
|
|
| 325 | <ti> |
|
|
| 326 | You can do a stage1, stage2 or stage3 by getting the stage tarball off the |
|
|
| 327 | net |
|
|
| 328 | </ti> |
|
|
| 329 | </tr> |
|
|
| 330 | <tr> |
|
|
| 331 | <th>-</th> |
124 | <th>-</th> |
| 332 | <ti> |
125 | <ti> |
| 333 | Contains no stages, no Portage snapshot, no prebuilt packages and is |
126 | Contains no stage3 tarball, no Portage snapshot, no prebuilt packages and is |
| 334 | therefore not suitable for networkless installation |
127 | therefore not suitable for networkless installation |
| 335 | </ti> |
128 | </ti> |
| 336 | </tr> |
129 | </tr> |
| 337 | </table> |
130 | </table> |
|
|
131 | |
|
|
132 | </body> |
|
|
133 | </subsection> |
|
|
134 | <subsection> |
|
|
135 | <title>The Stage3 Tarball</title> |
|
|
136 | <body> |
|
|
137 | |
|
|
138 | <p> |
|
|
139 | A stage3 tarball is an archive containing a minimal Gentoo environment, suitable |
|
|
140 | to continue the Gentoo installation using the instructions in this manual. |
|
|
141 | Previously, the Gentoo Handbook described the installation using one of three |
|
|
142 | stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the |
|
|
143 | official installation method uses the stage3 tarball. If you are interested in |
|
|
144 | performing a Gentoo installation using a stage1 or stage2 tarball, please read |
|
|
145 | the Gentoo FAQ on <uri link="/doc/en/faq.xml#stage12">How do I Install Gentoo |
|
|
146 | Using a Stage1 or Stage2 Tarball?</uri> |
|
|
147 | </p> |
| 338 | |
148 | |
| 339 | </body> |
149 | </body> |
| 340 | </subsection> |
150 | </subsection> |
| 341 | </section> |
151 | </section> |
| 342 | <!-- STOP --> |
152 | <!-- STOP --> |