/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.11 - (hide annotations) (download) (as text)
Fri Jul 9 08:43:40 2004 UTC (10 years ago) by neysx
Branch: MAIN
Changes since 1.10: +2 -2 lines
File MIME type: application/xml
#56333:use md5sum.exe to check MD5 on a W machine

1 swift 1.1 <?xml version='1.0' encoding='UTF-8'?>
2     <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3    
4     <!-- The content of this document is licensed under the CC-BY-SA license -->
5     <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6    
7 neysx 1.11 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-medium.xml,v 1.10 2004/07/03 19:01:52 swift Exp $ -->
8 swift 1.1
9     <sections>
10     <section>
11     <title>Hardware Requirements</title>
12     <subsection>
13     <title>Introduction</title>
14     <body>
15    
16     <p>
17     Before we start, we first list what hardware requirements you need to
18     successfully install Gentoo on your box. This of course depends on your
19     architecture.
20     </p>
21    
22     </body>
23     </subsection>
24     <subsection>
25     <title>The Alpha Architecture</title>
26     <body>
27    
28     <p>
29     Check the following requirements before you
30     continue with the Gentoo installation:
31     </p>
32    
33     <ul>
34     <li>
35     You need at least 1 Gb of free disk space
36     </li>
37     <li>
38     For the <e>Alpha architecture</e>, you should check with the <uri
39     link="http://www.alphalinux.org/faq/FAQ-5.html">Alpha/Linux FAQ</uri>
40     </li>
41     </ul>
42    
43     </body>
44     </subsection>
45     </section>
46     <section>
47     <title>Make your Choice</title>
48     <subsection>
49     <title>Introduction</title>
50     <body>
51    
52     <p>
53     Still interested in trying out Gentoo? Well, then it is now time to
54     choose the installation medium you want to use. Yes, you have the
55     choice, no, they are not all equal, and yes, the result is always the same: a
56     Gentoo base system.
57     </p>
58    
59     <p>
60     The installation media we will describe are:
61     </p>
62    
63     <ul>
64     <li>The Gentoo Alpha LiveCD</li>
65     </ul>
66    
67     <p>
68     Before we continue, let's explain our three-stage installation.
69     </p>
70    
71     </body>
72     </subsection>
73     <subsection>
74     <title>The Three Stages</title>
75     <body>
76    
77     <p>
78     Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
79     The one you choose depends on how much of the system you want to compile
80     yourself. The <e>stage1</e> tarball is used when you want to bootstrap and
81     build the entire system from scratch. The <e>stage2</e> tarball is used for
82     building the entire system from a bootstrapped &quot;semi-compiled&quot; state.
83     The <e>stage3</e> tarball already contains a basic Gentoo Linux system that has
84     been built for you.
85     </p>
86    
87     <p>
88     Now what stage do you have to choose?
89     </p>
90    
91     <p>
92     Starting from a <e>stage1</e> allows you to have total control over the
93     optimization settings and optional build-time functionality that is
94     initially enabled on your system. This makes <e>stage1</e> installs good for
95     power users who know what they are doing. It is also a great
96     installation method for those who would like to know more about the
97     inner workings of Gentoo Linux.
98     </p>
99    
100 swift 1.7 <p>
101     A <e>stage1</e> installation can only be performed when you have a working
102     Internet connection.
103     </p>
104    
105 swift 1.1 <table>
106     <tr>
107     <th>Stage1</th>
108     <th>Pros and Cons</th>
109     </tr>
110     <tr>
111     <th>+</th>
112     <ti>
113     Allows you to have total control over the optimization settings and optional
114     build-time functionality that is initially enabled on your system
115     </ti>
116     </tr>
117     <tr>
118     <th>+</th>
119     <ti>Suitable for powerusers that know what they are doing</ti>
120     </tr>
121     <tr>
122     <th>+</th>
123     <ti>Allows you to learn more about the inner workings of Gentoo</ti>
124     </tr>
125     <tr>
126     <th>-</th>
127     <ti>Takes a long time to finish the installation</ti>
128     </tr>
129     <tr>
130     <th>-</th>
131     <ti>
132     If you don't intend to tweak the settings, it is probably a waste of time
133     </ti>
134     </tr>
135 swift 1.7 <tr>
136     <th>-</th>
137     <ti>
138     Not suitable for networkless installations
139     </ti>
140     </tr>
141 swift 1.1 </table>
142    
143     <p>
144     <e>Stage2</e> installs allow you to skip the bootstrap process and doing this
145     is fine if you are happy with the optimization settings that we chose
146     for your particular <e>stage2</e> tarball.
147     </p>
148    
149 swift 1.7 <p>
150     A <e>stage2</e> installation can only be performed when you have a working
151     Internet connection.
152     </p>
153    
154 swift 1.1 <table>
155     <tr>
156     <th>Stage2</th>
157     <th>Pros and Cons</th>
158     </tr>
159     <tr>
160     <th>+</th>
161     <ti>You don't need to bootstrap</ti>
162     </tr>
163     <tr>
164     <th>+</th>
165     <ti>Faster than starting with stage1</ti>
166     </tr>
167     <tr>
168     <th>+</th>
169     <ti>You can still tweak your settings</ti>
170     </tr>
171     <tr>
172     <th>-</th>
173     <ti>You cannot tweak as much as with a stage1</ti>
174     </tr>
175     <tr>
176     <th>-</th>
177     <ti>It's not the fastest way to install Gentoo</ti>
178     </tr>
179     <tr>
180     <th>-</th>
181     <ti>You have to accept the optimizations we chose for the bootstrap</ti>
182     </tr>
183 swift 1.7 <tr>
184     <th>-</th>
185     <ti>
186     Not suitable for networkless installations
187     </ti>
188     </tr>
189 swift 1.1 </table>
190    
191     <p>
192     Choosing to go with a <e>stage3</e> allows for the fastest install of Gentoo
193     Linux, but also means that your base system will have the optimization
194     settings that we chose for you (which to be honest, are good settings
195     and were carefully chosen to enhance performance while maintaining
196     stability). <e>stage3</e> is also required if you want to install Gentoo using
197 swift 1.6 prebuilt packages or without a network connection.
198 swift 1.1 </p>
199    
200     <table>
201     <tr>
202     <th>Stage3</th>
203     <th>Pros and Cons</th>
204     </tr>
205     <tr>
206     <th>+</th>
207     <ti>Fastest way to get a Gentoo base system</ti>
208     </tr>
209     <tr>
210 swift 1.7 <th>+</th>
211     <ti>Suitable for networkless installations</ti>
212     </tr>
213     <tr>
214 swift 1.1 <th>-</th>
215     <ti>You cannot tweak the base system - it's built already</ti>
216     </tr>
217     <tr>
218     <th>-</th>
219     <ti>You cannot brag about having used stage1 or stage2</ti>
220     </tr>
221     </table>
222    
223     <p>
224     Write down (or remember) what stage you want to use. You need this later when
225     you decide what LiveCD (or other installation medium) you want to use. You might
226     be interested to know that, if you decide to use different optimization settings
227     after having installed Gentoo, you will be able to recompile your entire system
228     with the new optimization settings.
229     </p>
230    
231     <p>
232     Now take a look at the available installation media.
233     </p>
234    
235     </body>
236     </subsection>
237     <subsection>
238     <title>The Gentoo Alpha LiveCD</title>
239     <body>
240    
241     <p>
242     The <e>Gentoo Alpha LiveCD</e> is a bootable CD which contain a
243     self-sustained Gentoo environment. It allows you to boot Linux from the CD.
244     During the boot process your hardware is detected and the appropriate drivers
245     are loaded. It is maintained by Gentoo developers.
246     </p>
247    
248     <p>
249     The <e>Gentoo Alpha LiveCD</e> is a small, no-nonsense, bootable CD which sole
250     purpose is to boot the system, prepare the networking and continue with the
251     Gentoo installation. It does not contain any stages (or, in some cases, a
252     single stage1 file), source code or precompiled packages. For example the
253     alpha variant of this LiveCD can be found in the
254     <path>releases/1.4_rc1/alpha</path> subdirectory and is called
255     <c>gentoo-alpha-1.4rc1-test3.iso.bz2</c>.
256     </p>
257    
258     </body>
259     </subsection>
260     </section>
261     <section>
262     <title>Download, Burn and Boot the Gentoo LiveCD</title>
263     <subsection>
264     <title>Downloading and Burning the LiveCDs</title>
265     <body>
266    
267     <p>
268     You have chosen to use a Gentoo LiveCD (if not, then you are reading the
269     wrong document). We'll first start by downloading and burning the chosen
270     LiveCD.
271     </p>
272    
273     <p>
274     Visit one of our <uri
275     link="/main/en/mirrors.xml">mirrors</uri> and go to
276     <path>releases/1.4rc1/alpha</path> which is where the LiveCD(s) of your choice
277     are located. Inside that directory you'll find so-called ISO-files. Those are
278     full CD images which you can write on a CD-R.
279     </p>
280    
281     <p>
282     In case you wonder if your downloaded file is corrupted or not, you can
283     check its MD5 checksum and compare it with the MD5 checksum we provide (such as
284     <path>gentoo-alpha-1.4rc1-test3.iso.bz2.md5sum</path>). You can check the MD5
285     checksum with the <c>md5sum</c> tool under Linux/Unix or <uri
286 neysx 1.11 link="http://www.etree.org/md5com.html">md5sum</uri> for Windows.
287 swift 1.1 </p>
288    
289     <p>
290     Once downloaded, decompress the ISO file (as it is stored in a compressed format
291     using the Burrows-Wheeler text compression algorithm) using <c>bunzip2</c> (on
292     Unix/Linux systems):
293     </p>
294    
295     <pre caption="Decompressing the iso.bz2 file">
296     # <i>bunzip2 gentoo-alpha-1.4rc1-test3.iso.bz2</i>
297     </pre>
298    
299 swift 1.10 <!--
300 swift 1.1 <p>
301 swift 1.8 Another way to check the validity of the downloaded file is to use GnuPG to
302     verify the cryptographic signature that we provide (the file ending with
303     <path>.asc</path>). Download the signature file and obtain the public key:
304     </p>
305    
306     <pre caption="Obtaining the public key">
307 swift 1.10 $ <i>gpg - -keyserver pgp.mit.edu - -recv-keys 19462D47</i>
308 swift 1.8 </pre>
309    
310     <p>
311     Now verify the signature:
312     </p>
313    
314     <pre caption="Verify the cryptographic signature">
315 swift 1.10 $ <i>gpg - -verify &lt;signature file&gt; &lt;downloaded iso&gt;</i>
316 swift 1.8 <comment>(If everything goes well, you should see something like this:)</comment>
317     gpg: Signature made Mon Apr 19 18:54:40 2004 EDT using DSA key ID 19462D47
318     gpg: Good signature from "John Davis (Gentoo Linux Developer) &lt;zhen@gentoo.org&gt;"
319     gpg: aka "Gentoo Linux Release Engineering &lt;releng@gentoo.org&gt;"
320     </pre>
321 swift 1.10 -->
322 swift 1.8
323     <p>
324 swift 1.1 To burn the downloaded ISO(s), you have to select raw-burning. How you
325 swift 1.9 do this is highly program-dependent. We will discuss <c>cdrecord</c> and
326     <c>K3B</c> here; more information can be found in our <uri
327     link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>.
328 swift 1.1 </p>
329    
330     <ul>
331     <li>
332     With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace
333     <path>/dev/hdc</path> with your CD-RW drive's device path) followed
334     by the path to the ISO file :)
335     </li>
336 swift 1.2 <li>
337 bennyc 1.5 With K3B, select <c>Tools</c> &gt; <c>CD</c> &gt; <c>Burn Image</c>. Then
338     you can locate your ISO file within the 'Image to Burn' area. Finally click
339 swift 1.2 <c>Start</c>.
340     </li>
341 swift 1.1 </ul>
342    
343     </body>
344     </subsection>
345     <subsection>
346     <title>Booting the Alpha LiveCD(s)</title>
347     <body>
348    
349     <p>
350     When your Alpha is powered on, the first thing that gets started is the
351     firmware. It is loosely synonymous with the BIOS software on PC systems. There
352     are two types of firmware on Alpha systems: SRM (<e>Systems Reference
353     Manual</e>) and ARC (<e>Advanced Risc Console</e>).
354     </p>
355    
356     <p>
357     SRM is based on the Alpha Console Subsystem specification, which provides an
358     operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. ARM
359     is based on the Advanced RISC Computing (ARC) specification, which provides
360     an operating environment for Windows NT.
361     </p>
362    
363     <p>
364     If your Alpha system supports both SRC and ARCs (ARC, AlphaBIOS, ARCSBIOS) you
365     should follow <uri link="http://www.alphalinux.org/faq/x31.html">these
366     instructions</uri> for switching to SRM. If your system already uses SRM, you
367     are all set. If your system can only use ARCs (Ruffian, nautilus, xl, etc.) you
368     will need to choose <c>MILO</c> later on when we are talking about bootloaders.
369     </p>
370    
371     <p>
372     Now to boot an Alpha LiveCD, put the CD-ROM in the tray and reboot the system.
373     You can use SRM to boot the LiveCD. If you cannot do that, you will have to use
374     <c>MILO</c>. If you don't have <c>MILO</c> installed already, use one of the
375     precompiled <c>MILO</c> images available on <uri
376     link="http://dev.gentoo.org/~taviso/milo/">taviso's homepage</uri>.
377     </p>
378    
379     <pre caption="Booting a CD-ROM using SRM">
380     <comment>(List available hardware drives)</comment>
381     &gt;&gt;&gt; <i>show device</i>
382     dkb0.0.1.4.0 DKB0 TOSHIBA CDROM
383     <comment>(...)</comment>
384     <comment>(Substitute dkb0 with your CD-ROM drive device)</comment>
385     &gt;&gt;&gt; <i>boot dkb0 -flags 0</i>
386     </pre>
387    
388     <pre caption="Booting a CD-ROM using MILO">
389     <comment>(Substitute hdb with your CD-ROM drive device)</comment>
390     MILO&gt; <i>boot hdb:boot/vmlinuz initrd=initrd.img root=/dev/ram0 init=/linuxrc</i>
391     </pre>
392    
393     <p>
394     You should have a root ("#") prompt on the current console and can also switch
395     to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you
396     started on by pressing Alt-F1.
397     </p>
398    
399     <p>
400     Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>.
401     </p>
402    
403     </body>
404     </subsection>
405     <subsection id="hardware">
406     <title>Extra Hardware Configuration</title>
407     <body>
408    
409     <p>
410     When the Live CD boots, it tries to detect all your hardware devices and
411     loads the appropriate kernel modules to support your hardware. In the
412     vast majority of cases, it does a very good job. However, in some cases (the
413     SPARC LiveCDs don't even do autodetection), it may not auto-load the kernel
414     modules you need. If the PCI auto-detection missed some of your system's
415     hardware, you will have to load the appropriate kernel modules manually.
416     </p>
417    
418     <p>
419     In the next example we try to load the <c>8139too</c> module (support for
420     certain kinds of network interfaces):
421     </p>
422    
423     <pre caption="Loading kernel modules">
424     # <i>modprobe 8139too</i>
425     </pre>
426    
427     </body>
428     </subsection>
429     <subsection>
430     <title>Optional: Tweaking Hard Disk Performance</title>
431     <body>
432    
433     <p>
434     If you are an advanced user, you might want to tweak the IDE hard disk
435     performance using <c>hdparm</c>. With the <c>-tT</c> options you can
436     test the performance of your disk (execute it several times to get a
437     more precise impression):
438     </p>
439    
440     <pre caption="Testing disk performance">
441     # <i>hdparm -tT /dev/hda</i>
442     </pre>
443    
444     <p>
445     To tweak, you can use any of the following examples (or experiment
446     yourself) which use <path>/dev/hda</path> as disk (substitute with your
447     disk):
448     </p>
449    
450     <pre caption="Tweaking hard disk performance">
451     <comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i>
452     <comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
453     </pre>
454    
455     </body>
456     </subsection>
457     <subsection>
458     <title>Optional: User Accounts</title>
459     <body>
460    
461     <p>
462     If you plan on giving other people access to your installation
463     environment or you want to chat using <c>irssi</c> without root privileges (for
464     security reasons), you need to create the necessary user accounts and change
465     the root password.
466     </p>
467    
468     <p>
469     To change the root password, use the <c>passwd</c> utility:
470     </p>
471    
472     <pre caption="Changing the root password">
473     # <i>passwd</i>
474     New password: <comment>(Enter your new password)</comment>
475     Re-enter password: <comment>(Re-enter your password)</comment>
476     </pre>
477    
478     <p>
479 swift 1.4 To create a user account, we first enter their credentials, followed by
480 swift 1.1 its password. We use <c>useradd</c> and <c>passwd</c> for these tasks.
481     In the next example, we create a user called &quot;john&quot;.
482     </p>
483    
484     <pre caption="Creating a user account">
485     # <i>useradd john</i>
486     # <i>passwd john</i>
487     New password: <comment>(Enter john's password)</comment>
488     Re-enter password: <comment>(Re-enter john's password)</comment>
489     </pre>
490    
491     <p>
492     You can change your user id from root to the newly created user by using
493     <c>su</c>:
494     </p>
495    
496     <pre caption="Changing user id">
497     # <i>su john -</i>
498     </pre>
499    
500     </body>
501     </subsection>
502     <subsection>
503     <title>Optional: Starting the SSH Daemon</title>
504     <body>
505    
506     <p>
507     If you want to allow other users to access your computer during the
508     Gentoo installation (perhaps because those users are going to help you
509     install Gentoo, or even do it for you), you need to create a user
510     account for them and perhaps even provide them with your root password
511     (<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
512     </p>
513    
514     <p>
515     To fire up the SSH daemon, execute the following command:
516     </p>
517    
518     <pre caption="Starting the SSH daemon">
519     # <i>/etc/init.d/sshd start</i>
520     </pre>
521    
522     <p>
523     To be able to use sshd, you first need to setup your networking. Continue with
524     the chapter on <uri link="?part=1&amp;chap=3">Configuring your Network</uri>.
525     </p>
526    
527     </body>
528     </subsection>
529     </section>
530     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20