/[gentoo]/xml/htdocs/doc/en/handbook/index.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/index.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.79 - (hide annotations) (download) (as text)
Fri Sep 30 15:05:59 2011 UTC (3 years ago) by cam
Branch: MAIN
Changes since 1.78: +2 -2 lines
File MIME type: application/xml
typo fixed (Chema Alonso)

1 swift 1.1 <?xml version='1.0' encoding="UTF-8"?>
2     <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3    
4 cam 1.79 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.78 2011/09/23 18:47:05 swift Exp $ -->
5 swift 1.2
6 swift 1.77 <guide>
7 swift 1.1 <title>Gentoo Handbook</title>
8    
9     <author title="Author">
10 neysx 1.72 <mail link="swift"/>
11 swift 1.1 </author>
12    
13     <abstract>
14     The Gentoo Handbook is an effort to centralise documentation into a coherent
15 swift 1.45 handbook. This handbook contains the installation instructions for
16     internet-based installation approaches and parts about working with Gentoo and
17     Portage.
18 swift 1.1 </abstract>
19    
20 swift 1.14 <license/>
21    
22 swift 1.78 <version>2</version>
23     <date>2011-09-23</date>
24 swift 1.1
25     <chapter>
26     <title>The Gentoo Handbook Effort</title>
27     <section>
28 swift 1.23 <title>Available languages</title>
29     <body>
30    
31     <p>
32     The Gentoo Handbook is available in the following languages:
33     </p>
34    
35     <p>
36 neysx 1.71 <!--<uri link="/doc/pt_br/handbook/">Brazilian Portuguese</uri> |-->
37     <!--<uri link="/doc/cs/handbook/">Czech</uri> |-->
38 neysx 1.58 <!--<uri link="/doc/da/handbook/">Danish</uri> |-->
39 neysx 1.46 <uri link="/doc/de/handbook/">German</uri> |
40     <uri link="/doc/en/handbook/">English</uri> |
41     <uri link="/doc/fr/handbook/">French</uri> |
42 neysx 1.51 <!--<uri link="/doc/id/handbook/">Indonesian</uri> |-->
43 neysx 1.46 <uri link="/doc/it/handbook/">Italian</uri> |
44 neysx 1.75 <uri link="/doc/ja/handbook/">Japanese</uri> |
45 neysx 1.53 <uri link="/doc/pl/handbook/">Polish</uri> |
46 neysx 1.71 <!--<uri link="/doc/ro/handbook/">Romanian</uri> |-->
47     <!--<uri link="/doc/ru/handbook/">Russian</uri> |-->
48 neysx 1.72 <uri link="/doc/zh_cn/handbook/">Simplified Chinese</uri> |
49 yoswink 1.74 <uri link="/doc/es/handbook/">Spanish</uri>
50 swift 1.23 </p>
51    
52     </body>
53     </section>
54     <section>
55 swift 1.1 <title>Introduction</title>
56     <body>
57    
58     <p>
59     Welcome to the Gentoo Handbook page. This page will give you some explanation
60 neysx 1.76 about the Gentoo Handbook and should answer most of your questions regarding
61     the handbook. We will talk about the ideas behind the handbook, its current
62     status, the future plans, how bug reports are handled, etc.
63 swift 1.1 </p>
64    
65     </body>
66     </section>
67 swift 1.78 <section>
68     <title>Architectures</title>
69     <body>
70    
71     <p>
72     Gentoo Linux is available for many architectures. But what exactly is an
73     architecture?
74     </p>
75    
76     <p>
77     An <b>architecture</b> is a family of CPUs (processors) who support the same
78     instructions. The two most prominent architectures in the desktop world are the
79     <e>x86</e> architecture and the <e>x86_64</e> architecture (for which Gentoo
80     uses the <e>amd64</e> notation). But many other architectures exist, such as
81     <e>sparc</e>, <e>ppc</e> (the PowerPC family), <e>mips</e>, <e>arm</e>, ...
82     </p>
83    
84     <p>
85     A distribution as versatile as Gentoo supports many architectures. For that
86     reason, you'll find that our Gentoo Handbooks are offered for many of the
87     supported architectures. However, that might lead to some confusion as not all
88     users are aware of the differences. Some are only aware of the
89     CPU type or name that their system is a part of (like i686 or Intel Core
90     i7). Below you will find a quick summary of the supported architectures and the
91     abbreviation used in Gentoo. However, most people that do not know the
92     architecture of their system are mostly interested in <e>x86</e> or
93     <e>amd64</e>.
94     </p>
95    
96     <note>
97     The table below gives a high-level overview of the supported architectures. The
98     example set of CPUs or systems is nothing more than an example. If you are
99     still not certain which architecture to pick, please read the first section of
100     the Gentoo Handbook's second chapter (<e>Choosing the Right Installation
101     Medium</e>) as this will elaborate on the supported platforms.
102     </note>
103    
104     <table>
105     <tr>
106     <th>Architecture</th>
107     <th>Description</th>
108     <th>Sample set of CPUs or systems</th>
109     </tr>
110     <tr>
111     <ti>x86</ti>
112     <ti>
113     A 32-bit architecture used by CPUs that are often said to be "Intel
114     compatible". It was, until recently, the most popular architecture for
115     desktop PCs. Gentoo offers builds for i486 (supports all families) and
116     i686 (supports Pentium and higher or compatible).
117     </ti>
118     <ti>i486, i686, Intel Core, AMD Athlon, Intel Atom</ti>
119     </tr>
120     <tr>
121     <ti>x86_64<br />(amd64)</ti>
122     <ti>
123     A 64-bit architecture that is compatible with the x86 architecture. It was
124     first used by AMD (under the AMD64 name) and Intel (under the EM64T name)
125     and is now the most prominent architecture for medium and high-end desktop
126     PCs. It is also commonly found in the server segment.
127     </ti>
128     <ti>
129     AMD Athlon 64, AMD Opteron, AMD Sempron processors, AMD Phenom,
130     Intel Pentium 4, Pentium Core i3, i5, i7
131     </ti>
132     </tr>
133     <tr>
134     <ti>ia64</ti>
135     <ti>
136     A 64-bit architecture designed by Intel and used in their Intel Itanium
137     processor series. This architecture is <e>not</e> compatible with x86 or
138     x86_64 (aka amd64) and is mostly found in medium and high-end server series.
139     </ti>
140     <ti>
141     Intel Itanium
142     </ti>
143     </tr>
144     <tr>
145     <ti>sparc</ti>
146     <ti>
147     The SPARC architecture is best known by its most common producers, Sun (now
148     Oracle) and Fujitsu. It is used in server systems although a few
149     workstations exist as well. In Gentoo, only SPARC64 compatible CPUs are
150     supported.
151     </ti>
152     <ti>
153     E3000, Blade 1000, Ultra 2
154     </ti>
155     </tr>
156     <tr>
157     <ti>ppc</ti>
158     <ti>
159     A 32-bit architecture used by many Apple, IBM and Motorola processors. They
160     are most commonly found in embedded systems.
161     </ti>
162     <ti>
163     Apple OldWorld, Apple NewWorld, generi Pegasos, Efika, older IBM iSeries and
164     pSeries
165     </ti>
166     </tr>
167     <tr>
168     <ti>ppc64</ti>
169     <ti>
170     The 64-bit variant of the PPC architecture, popular in both embedded as well
171     as high-end performance servers.
172     </ti>
173     <ti>
174     IBM RS/6000s, IBM pSeries, IBM iSeries
175     </ti>
176     </tr>
177     <tr>
178     <ti>alpha</ti>
179     <ti>
180     The Alpha architecture is a 64-bit architecture developed by Digital
181     Equipment Corporation (DEC). It is still in use by some mid-range and
182     high-end servers, but the architecture is slowly being faded out.
183     </ti>
184     <ti>
185     ES40, AlphaPC, UP1000, Noname
186     </ti>
187     </tr>
188     <tr>
189     <ti>PA-RISC<br />(hppa)</ti>
190     <ti>
191     Referred to as HPPA, the PA-RISC architecture is an instruction set
192     developed by Hewlett-Packard and was used in their mid- and high-end server
193     series until about 2008 (after which HP started using Intel Itanium)
194     </ti>
195     <ti>
196     HP 9000, PA-8600
197     </ti>
198     </tr>
199     <tr>
200     <ti>mips</ti>
201     <ti>
202     Developed by MIPS Technologies, the MIPS architecture entails multiple
203     subfamilies (called revisions) such as MIPS I, MIPS III, MIPS32, MIPS64 and
204 cam 1.79 more. MIPS is most common in embedded systems.
205 swift 1.78 </ti>
206     <ti>
207     MIPS32 1074K, R16000
208     </ti>
209     </tr>
210     <tr>
211     <ti>arm</ti>
212     <ti>
213     This 32-bit architecture is a very popular architecture for embedded and
214     small systems. Subarchitectures range from ARMv1 to ARMv7 (Cortex) and are
215     often found in smartphones, tablets, handheld consoles, end-user GPS
216     navigation systems, etc.
217     </ti>
218     <ti>
219     StrongARM, Cortex-M
220     </ti>
221     </tr>
222     </table>
223    
224     </body>
225     </section>
226 swift 1.1 </chapter>
227     <chapter>
228     <title>View the Handbook</title>
229     <section>
230     <body>
231    
232 swift 1.78 <p>
233     Assuming that you know (or at least have an idea) which architecture your system
234     is using, you can now select your choice of handbook.
235     </p>
236    
237 swift 1.1 <table>
238     <tr>
239     <th>Format</th>
240     <th>Description</th>
241 swift 1.21 <th>Links</th>
242 swift 1.1 </tr>
243     <tr>
244 swift 1.21 <ti>HTML</ti>
245 swift 1.38 <ti>Latest version, one page per chapter, perfect for online viewing</ti>
246 swift 1.21 <ti>
247 swift 1.44 <uri link="handbook-x86.xml">x86</uri>,
248     <uri link="handbook-sparc.xml">sparc</uri>,
249     <uri link="handbook-amd64.xml">amd64</uri>,
250     <uri link="handbook-ppc.xml">ppc</uri>,
251 neysx 1.47 <uri link="handbook-ppc64.xml">ppc64</uri>,
252 swift 1.44 <uri link="handbook-alpha.xml">alpha</uri>,
253     <uri link="handbook-hppa.xml">hppa</uri>,
254 nightmorph 1.68 <uri link="handbook-mips.xml">mips</uri>,
255 nightmorph 1.69 <uri link="handbook-ia64.xml">ia64</uri>,
256 nightmorph 1.68 <uri link="handbook-arm.xml">arm</uri>
257 swift 1.21 </ti>
258 swift 1.15 </tr>
259     <tr>
260 swift 1.21 <ti>HTML</ti>
261 swift 1.44 <ti>Latest version, all in one page</ti>
262 swift 1.21 <ti>
263 swift 1.44 <uri link="handbook-x86.xml?full=1">x86</uri>,
264     <uri link="handbook-sparc.xml?full=1">sparc</uri>,
265     <uri link="handbook-amd64.xml?full=1">amd64</uri>,
266     <uri link="handbook-ppc.xml?full=1">ppc</uri>,
267     <uri link="handbook-ppc64.xml?full=1">ppc64</uri>,
268     <uri link="handbook-alpha.xml?full=1">alpha</uri>,
269     <uri link="handbook-hppa.xml?full=1">hppa</uri>,
270 nightmorph 1.69 <uri link="handbook-mips.xml?full=1">mips</uri>,
271 nightmorph 1.70 <uri link="handbook-ia64.xml?full=1">ia64</uri>,
272     <uri link="handbook-arm.xml?full=1">arm</uri>
273 swift 1.21 </ti>
274 swift 1.15 </tr>
275     <tr>
276 swift 1.21 <ti>HTML</ti>
277 swift 1.38 <ti>Latest version, all in one page, printable version</ti>
278 swift 1.21 <ti>
279 swift 1.44 <uri link="handbook-x86.xml?style=printable&amp;full=1">x86</uri>,
280     <uri link="handbook-sparc.xml?style=printable&amp;full=1">sparc</uri>,
281     <uri link="handbook-amd64.xml?style=printable&amp;full=1">amd64</uri>,
282 swift 1.21 <uri link="handbook-ppc.xml?style=printable&amp;full=1">ppc</uri>,
283 swift 1.44 <uri link="handbook-ppc64.xml?style=printable&amp;full=1">ppc64</uri>,
284     <uri link="handbook-alpha.xml?style=printable&amp;full=1">alpha</uri>,
285     <uri link="handbook-hppa.xml?style=printable&amp;full=1">hppa</uri>,
286 nightmorph 1.69 <uri link="handbook-mips.xml?style=printable&amp;full=1">mips</uri>,
287     <uri link="handbook-ia64.xml?style=printable&amp;full=1">ia64</uri>,
288     <uri link="handbook-arm.xml?style=printable&amp;full=1">arm</uri>
289 swift 1.21 </ti>
290 swift 1.1 </tr>
291 swift 1.44 </table>
292    
293     </body>
294     </section>
295     <section>
296     <title>Historical Releases</title>
297     <body>
298    
299     <p>
300     For historical reasons we also keep the handbook versions for older releases
301     (since 2004.2). Printable versions of individual pages can be reached through
302     the "Print" link on the top right corner. To have an all-in-one-page version,
303     add <path>?full=1</path> to the URL.
304     </p>
305    
306     <warn>
307     These handbooks are <e>not</e> maintained.
308     </warn>
309    
310     <table>
311 swift 1.38 <tr>
312 swift 1.44 <th>Release</th>
313     <th>Architectures</th>
314 swift 1.38 </tr>
315     <tr>
316 swift 1.44 <ti>2004.2</ti>
317 swift 1.38 <ti>
318 swift 1.44 <uri link="2004.2/handbook-alpha.xml">alpha</uri>,
319     <uri link="2004.2/handbook-amd64.xml">amd64</uri>,
320     <uri link="2004.2/handbook-hppa.xml">hppa</uri>,
321     <uri link="2004.2/handbook-mips.xml">mips</uri>,
322     <uri link="2004.2/handbook-ppc.xml">ppc</uri>,
323     <uri link="2004.2/handbook-sparc.xml">sparc</uri>,
324     <uri link="2004.2/handbook-x86.xml">x86</uri>
325 swift 1.38 </ti>
326     </tr>
327 swift 1.49 <tr>
328     <ti>2004.3</ti>
329     <ti>
330     <uri link="2004.3/handbook-amd64.xml">amd64</uri>,
331     <uri link="2004.3/handbook-hppa.xml">hppa</uri>,
332     <uri link="2004.3/handbook-ppc.xml">ppc</uri>,
333     <uri link="2004.3/handbook-sparc.xml">sparc</uri>,
334     <uri link="2004.3/handbook-x86.xml">x86</uri>
335     </ti>
336     </tr>
337 swift 1.54 <tr>
338     <ti>2005.0</ti>
339     <ti>
340     <uri link="2005.0/handbook-alpha.xml">alpha</uri>,
341     <uri link="2005.0/handbook-amd64.xml">amd64</uri>,
342     <uri link="2005.0/handbook-hppa.xml">hppa</uri>,
343     <uri link="2005.0/handbook-ppc.xml">ppc</uri>,
344     <uri link="2005.0/handbook-sparc.xml">sparc</uri>,
345     <uri link="2005.0/handbook-x86.xml">x86</uri>
346     </ti>
347     </tr>
348 neysx 1.60 <tr>
349     <ti>2005.1</ti>
350     <ti>
351     <uri link="2005.1/handbook-alpha.xml">alpha</uri>,
352     <uri link="2005.1/handbook-amd64.xml">amd64</uri>,
353     <uri link="2005.1/handbook-hppa.xml">hppa</uri>,
354     <uri link="2005.1/handbook-ppc.xml">ppc</uri>,
355     <uri link="2005.1/handbook-ppc64.xml">ppc64</uri>,
356     <uri link="2005.1/handbook-sparc.xml">sparc</uri>,
357     <uri link="2005.1/handbook-x86.xml">x86</uri>
358     </ti>
359     </tr>
360 nightmorph 1.62 <tr>
361     <ti>2006.0</ti>
362     <ti>
363     <uri link="2006.0/handbook-alpha.xml">alpha</uri>,
364     <uri link="2006.0/handbook-amd64.xml">amd64</uri>,
365     <uri link="2006.0/handbook-hppa.xml">hppa</uri>,
366     <uri link="2006.0/handbook-ppc.xml">ppc</uri>,
367     <uri link="2006.0/handbook-ppc64.xml">ppc64</uri>,
368     <uri link="2006.0/handbook-sparc.xml">sparc</uri>,
369     <uri link="2006.0/handbook-x86.xml">x86</uri>
370     </ti>
371     </tr>
372 nightmorph 1.68 <tr>
373     <ti>2006.1</ti>
374     <ti>
375     <uri link="2006.1/handbook-alpha.xml">alpha</uri>,
376     <uri link="2006.1/handbook-amd64.xml">amd64</uri>,
377     <uri link="2006.1/handbook-hppa.xml">hppa</uri>,
378     <uri link="2006.1/handbook-ppc.xml">ppc</uri>,
379     <uri link="2006.1/handbook-ppc64.xml">ppc64</uri>,
380     <uri link="2006.1/handbook-sparc.xml">sparc</uri>,
381     <uri link="2006.1/handbook-x86.xml">x86</uri>
382     </ti>
383     </tr>
384 nightmorph 1.73 <tr>
385     <ti>2007.0</ti>
386     <ti>
387     <uri link="2007.0/handbook-amd64.xml">amd64</uri>,
388     <uri link="2007.0/handbook-hppa.xml">hppa</uri>,
389     <uri link="2007.0/handbook-ppc.xml">ppc</uri>,
390     <uri link="2007.0/handbook-ppc64.xml">ppc64</uri>,
391     <uri link="2007.0/handbook-sparc.xml">sparc</uri>,
392     <uri link="2007.0/handbook-x86.xml">x86</uri>
393     </ti>
394     </tr>
395 neysx 1.76 <tr>
396     <ti>2008.0</ti>
397     <ti>
398     <uri link="2008.0/handbook-amd64.xml">amd64</uri>,
399     <uri link="2008.0/handbook-hppa.xml">hppa</uri>,
400     <uri link="2008.0/handbook-ppc.xml">ppc</uri>,
401     <uri link="2008.0/handbook-ppc64.xml">ppc64</uri>,
402     <uri link="2008.0/handbook-sparc.xml">sparc</uri>,
403     <uri link="2008.0/handbook-x86.xml">x86</uri>
404     </ti>
405     </tr>
406 swift 1.1 </table>
407    
408     </body>
409     </section>
410     </chapter>
411    
412     <chapter>
413     <title>Information about the handbook</title>
414     <section>
415     <title>Goal</title>
416     <body>
417    
418     <p>
419     The goal of the Gentoo Handbook is to create a coherent document that describes
420     every possible aspect of Gentoo Linux. It combines already existing guides in
421 swift 1.78 one consistent book, targeting a specific architecture, so that the entire
422     document can be used as a single resource for installing and administering
423     Gentoo Linux.
424 swift 1.3 </p>
425    
426     <p>
427 swift 1.78 Many parts of the different Gentoo Handbooks (different by architecture) are
428     copied across all handbooks (actually, it is written once and duplicated
429     automatically) to make sure that the general information and quality of the
430     documentation remains consistent.
431 swift 1.1 </p>
432    
433     </body>
434     </section>
435     <section>
436     <title>Reporting bugs and enhancement requests</title>
437     <body>
438    
439     <p>
440     If you find a bug in the handbook, please visit our <uri
441     link="http://bugs.gentoo.org">Gentoo Linux Bugzilla</uri> and create a bug for
442 nightmorph 1.67 <e>Documentation</e>, Component <e>Installation Handbook</e>.
443 swift 1.5 </p>
444    
445     </body>
446     </section>
447     </chapter>
448 swift 1.16 <chapter id="faq">
449 swift 1.5 <title>Frequently Asked Questions</title>
450     <section>
451     <title>Can't you magically have the handbook dynamically created for each choice?</title>
452     <body>
453    
454     <p>
455 swift 1.78 Everything is possible, but we have opted to only do this on a per-architecture
456     level. Other choices, like partitioning, kernel selection, tool installation and
457     more are easy enough to explain in a single document.
458 swift 1.5 </p>
459    
460 swift 1.78 <!--
461 swift 1.5 <p>
462     <b>Maintaining</b> the guide would be a lot more difficult. Not only will we
463 swift 1.9 have to map bug reports to certain decisions (far from all bug reports would
464     tell us what choices they made before) but it would be more difficult to write
465     the guide fluently: we would have to pay more attention to the line in the
466     handbook, the consistencies, etc.
467 swift 1.5 </p>
468    
469     <p>
470 neysx 1.64 Although we currently only have an online version, <b>other formats</b> could
471     be developed, such as PDF versions. If we created PDFs for every architecture
472     and option, we would have to provide numerous PDFs of which only a few sections
473     differ. Talk about a waste of resources :).
474 swift 1.5 </p>
475    
476     <p>
477 swift 1.9 The choices that the user makes are made <b>in different places</b>. This would
478 swift 1.78 make it more difficult for the user to just print out the handbook - - we would
479 swift 1.27 first have to inform the user of all possible options before they can begin,
480     probably scaring them away.
481 swift 1.5 </p>
482    
483     <p>
484     The part on "Installing Gentoo" <b>is not the only part</b> of the Gentoo
485     Handbook. It is the first, but all following parts are independent of the
486     choices the user made. Dynamically creating the handbook just for the
487     installation instructions would be overkill.
488     </p>
489    
490     <p>
491     By not separating the instructions for each possible option, the user can view
492     the results of the other choices easily. This provides a <b>better view on the
493 swift 1.55 installation instructions</b> for the user.
494 swift 1.5 </p>
495 swift 1.78 -->
496 swift 1.5
497     </body>
498     </section>
499     <section>
500 swift 1.50 <title>I can't find stage1 information in the Gentoo Handbook</title>
501     <body>
502    
503     <p>
504 swift 1.55 Instructions on using a stage1 or stage2 tarball are now available in the <uri
505     link="/doc/en/faq.xml#stage12">Gentoo FAQ</uri>. A stage3 installation is the
506     only supported installation as of now.
507 swift 1.50 </p>
508    
509     </body>
510     </section>
511     <section>
512 swift 1.5 <title>I disagree with ...</title>
513     <body>
514    
515     <p>
516     Please <uri link="http://bugs.gentoo.org">report</uri> your idea; disagreeing
517     without providing us with constructive feedback doesn't help the situation.
518     Documentation is made for the community, so community feedback is well
519     appreciated.
520     </p>
521    
522     <p>
523     However, you must know that most decisions made while developing documentation
524     are based on a consensus-model. It is <e>impossible</e> to write/structure
525     documentation in such a way that everybody is happy with it. You must be able to
526     accept a "No" with the reason that we believe the current implementation
527     benefits most people.
528 swift 1.1 </p>
529    
530     </body>
531     </section>
532     </chapter>
533     </guide>

  ViewVC Help
Powered by ViewVC 1.1.20