| … | |
… | |
| 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/2.5 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 6 | |
6 | |
| 7 | <!-- $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 $ --> |
7 | <!-- $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 $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>2.5</version> |
11 | <version>2.6</version> |
| 12 | <date>2005-08-25</date> |
12 | <date>2005-10-09</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> |
| … | |
… | |
| 125 | A <e>stage1</e> is used when you want to bootstrap and build the entire system |
125 | A <e>stage1</e> is used when you want to bootstrap and build the entire system |
| 126 | from scratch. |
126 | from scratch. |
| 127 | </p> |
127 | </p> |
| 128 | |
128 | |
| 129 | <p> |
129 | <p> |
| 130 | Starting from a stage1 allows you to have total control over the |
130 | This approach builds core system packages that are vital to your system and is |
| 131 | optimization settings and optional build-time functionality that is |
131 | used by Gentoo developers to prepare the Gentoo release media. It is a great |
| 132 | initially enabled on your system. This makes <e>stage1</e> installs good for |
|
|
| 133 | power users who know what they are doing. It is also a great |
|
|
| 134 | installation method for those who would like to know more about the |
132 | installation method for those who would like to learn more about the inner |
| 135 | inner workings of Gentoo Linux. |
133 | workings of bootstrapping, toolchains and the like. |
|
|
134 | </p> |
|
|
135 | |
|
|
136 | <p> |
|
|
137 | However, if you do not plan to tweak the bootstrapping instructions in the |
|
|
138 | <path>bootstrap.sh</path> script written by the Gentoo developers, then a |
|
|
139 | stage1 approach has no benefits for you. |
| 136 | </p> |
140 | </p> |
| 137 | |
141 | |
| 138 | <table> |
142 | <table> |
| 139 | <tr> |
143 | <tr> |
| 140 | <th>Stage1</th> |
144 | <th>Stage1</th> |
| 141 | <th>Pros and Cons</th> |
145 | <th>Pros and Cons</th> |
| 142 | </tr> |
146 | </tr> |
| 143 | <tr> |
147 | <tr> |
| 144 | <th>+</th> |
148 | <th>+</th> |
| 145 | <ti> |
149 | <ti> |
| 146 | Allows you to have total control over the optimization settings and optional |
150 | Allows you to have total control over the installation routine, bootstrap |
| 147 | build-time functionality that is initially enabled on your system |
151 | sequence, etc. |
| 148 | </ti> |
152 | </ti> |
| 149 | </tr> |
|
|
| 150 | <tr> |
153 | </tr> |
| 151 | <th>+</th> |
|
|
| 152 | <ti>Suitable for powerusers that know what they are doing</ti> |
|
|
| 153 | </tr> |
154 | <tr> |
| 154 | <tr> |
|
|
| 155 | <th>+</th> |
155 | <th>+</th> |
| 156 | <ti>Allows you to learn more about the inner workings of Gentoo</ti> |
156 | <ti>Suitable for powerusers and developers who know what they are doing</ti> |
| 157 | </tr> |
157 | </tr> |
| 158 | <tr> |
158 | <tr> |
| 159 | <th>-</th> |
159 | <th>-</th> |
| 160 | <ti>Takes a long time to finish the installation</ti> |
160 | <ti> |
|
|
161 | Takes a long time to finish the installation (it is the lengthiest approach) |
|
|
162 | </ti> |
| 161 | </tr> |
163 | </tr> |
| 162 | <tr> |
164 | <tr> |
| 163 | <th>-</th> |
165 | <th>-</th> |
| 164 | <ti> |
166 | <ti> |
| 165 | If you don't intend to tweak the settings, it is a waste of time |
167 | If you don't intend to tweak the settings, it is a waste of time |
| … | |
… | |
| 183 | A <e>stage2</e> is used for building the entire system from a bootstrapped |
185 | A <e>stage2</e> is used for building the entire system from a bootstrapped |
| 184 | "semi-compiled" state. |
186 | "semi-compiled" state. |
| 185 | </p> |
187 | </p> |
| 186 | |
188 | |
| 187 | <p> |
189 | <p> |
| 188 | Stage2 installs allow you to skip the bootstrap process; doing this |
190 | When you perform a stage2 installation approach, you will build all system |
| 189 | is fine if you are happy with the optimization settings that we chose |
191 | packages (core packages, including toolchain) using your specific <c>USE</c>, |
| 190 | for your particular stage2 tarball. |
192 | <c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be |
|
|
193 | optimized to your preference. |
|
|
194 | </p> |
|
|
195 | |
|
|
196 | <p> |
|
|
197 | However, this installation takes some time and if you do not intend to change |
|
|
198 | the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good |
|
|
199 | default", using this approach only makes sense if your <c>USE</c> variable is |
|
|
200 | sufficiently different from the default <c>USE</c> we provide. |
| 191 | </p> |
201 | </p> |
| 192 | |
202 | |
| 193 | <table> |
203 | <table> |
| 194 | <tr> |
204 | <tr> |
| 195 | <th>Stage2</th> |
205 | <th>Stage2</th> |
| … | |
… | |
| 207 | <th>+</th> |
217 | <th>+</th> |
| 208 | <ti>You can still tweak your settings</ti> |
218 | <ti>You can still tweak your settings</ti> |
| 209 | </tr> |
219 | </tr> |
| 210 | <tr> |
220 | <tr> |
| 211 | <th>-</th> |
221 | <th>-</th> |
| 212 | <ti>You cannot tweak as much as with a stage1</ti> |
222 | <ti>It's still not the fastest way to install Gentoo</ti> |
| 213 | </tr> |
223 | </tr> |
| 214 | <tr> |
224 | <tr> |
| 215 | <th>-</th> |
225 | <th>-</th> |
| 216 | <ti>It's still not the fastest way to install Gentoo</ti> |
|
|
| 217 | </tr> |
|
|
| 218 | <tr> |
|
|
| 219 | <th>-</th> |
|
|
| 220 | <ti>You have to accept the optimizations we chose for the bootstrap</ti> |
|
|
| 221 | </tr> |
|
|
| 222 | <tr> |
|
|
| 223 | <th>-</th> |
|
|
| 224 | <ti> |
226 | <ti> |
| 225 | Requires a working Internet connection during the installation |
227 | Requires a working Internet connection during the installation |
| 226 | </ti> |
228 | </ti> |
| 227 | </tr> |
229 | </tr> |
| 228 | </table> |
230 | </table> |
| … | |
… | |
| 233 | <title>A Stage3 Approach</title> |
235 | <title>A Stage3 Approach</title> |
| 234 | <body> |
236 | <body> |
| 235 | |
237 | |
| 236 | <p> |
238 | <p> |
| 237 | A <e>stage3</e> installation contains a basic Gentoo Linux system that has been |
239 | A <e>stage3</e> installation contains a basic Gentoo Linux system that has been |
| 238 | built for you. You will only need to build a few packages of which we can't |
240 | built for you. You will only need to build a few packages (such as system |
| 239 | decide for you which one to choose. |
241 | logger, networking tools, ...) before you can boot into a base Gentoo |
|
|
242 | installation. |
| 240 | </p> |
243 | </p> |
| 241 | |
244 | |
| 242 | <p> |
245 | <p> |
| 243 | Choosing to go with a stage3 allows for the fastest install of Gentoo |
246 | Choosing to go with a stage3 allows for the fastest install of Gentoo |
| 244 | Linux, but also means that your base system will have the optimization |
247 | Linux, but also means that your base system will have the optimization |
| … | |
… | |
| 256 | <tr> |
259 | <tr> |
| 257 | <th>+</th> |
260 | <th>+</th> |
| 258 | <ti>Fastest way to get a Gentoo base system</ti> |
261 | <ti>Fastest way to get a Gentoo base system</ti> |
| 259 | </tr> |
262 | </tr> |
| 260 | <tr> |
263 | <tr> |
| 261 | <th>-</th> |
264 | <th>+</th> |
| 262 | <ti>You cannot tweak the base system - it's built already</ti> |
265 | <ti> |
|
|
266 | You can still tweak your system |
|
|
267 | </ti> |
| 263 | </tr> |
268 | </tr> |
| 264 | </table> |
269 | </table> |
| 265 | |
270 | |
| 266 | <p> |
271 | <p> |
| 267 | You might be interested to know that, if you decide to use different |
272 | You might be interested to know that, if you decide to use different |
| 268 | optimization settings after having installed Gentoo, you will be able to |
273 | optimization settings after having installed Gentoo, you will be able to |
| 269 | recompile your entire system with the new optimization settings. |
274 | recompile your entire system with the new optimization settings. The same goes |
|
|
275 | for any <c>USE</c> flag changes: Portage is intelligent enough to know what |
|
|
276 | packages need to be rebuild. |
| 270 | </p> |
277 | </p> |
| 271 | |
278 | |
| 272 | </body> |
279 | </body> |
| 273 | </subsection> |
280 | </subsection> |
| 274 | </section> |
281 | </section> |
|
|
282 | |
| 275 | <section> |
283 | <section> |
| 276 | <title>The Gentoo Installation CDs</title> |
284 | <title>The Gentoo Installation CDs</title> |
| 277 | <subsection> |
285 | <subsection> |
| 278 | <title>Introduction</title> |
286 | <title>Introduction</title> |
| 279 | <body> |
287 | <body> |
| … | |
… | |
| 404 | set) that allows you to easily and quickly install additional applications |
412 | set) that allows you to easily and quickly install additional applications |
| 405 | (such as OpenOffice.org, KDE, GNOME, ...) immediately after the networkless |
413 | (such as OpenOffice.org, KDE, GNOME, ...) immediately after the networkless |
| 406 | Gentoo installation. |
414 | Gentoo installation. |
| 407 | </p> |
415 | </p> |
| 408 | |
416 | |
|
|
417 | <p> |
|
|
418 | If you intend to use the Packages CD to quickly install additional software, |
|
|
419 | make sure that you use the same subarchitecture as the stage-3 tarball you use. |
|
|
420 | </p> |
|
|
421 | |
| 409 | </body> |
422 | </body> |
| 410 | </subsection> |
423 | </subsection> |
| 411 | </section> |
424 | </section> |
| 412 | <!-- STOP --> |
425 | <!-- STOP --> |
| 413 | <section> |
426 | <section> |
Parent Directory
| 
Revision Log
| 
Patch