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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.33 - (hide annotations) (download) (as text)
Mon Nov 15 12:47:47 2004 UTC (9 years, 8 months ago) by swift
Branch: MAIN
Changes since 1.32: +24 -37 lines
File MIME type: application/xml
Moving 2004.3 documentation

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 swift 1.33 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml,v 1.23 2004/11/09 13:05:40 swift Exp $ -->
8 swift 1.1
9     <sections>
10 swift 1.32
11     <version>1.31</version>
12     <date>November 4, 2004</date>
13    
14 swift 1.1 <section>
15     <title>Hardware Requirements</title>
16     <subsection>
17     <title>Introduction</title>
18     <body>
19    
20     <p>
21     Before we start, we first list what hardware requirements you need to
22     successfully install Gentoo on your box. This of course depends on your
23     architecture.
24     </p>
25    
26     </body>
27     </subsection>
28     <subsection>
29     <title>The PPC Architecture</title>
30     <body>
31    
32     <p>
33     Check the following requirements before you
34     continue with the Gentoo installation:
35     </p>
36    
37     <ul>
38     <li>
39 dertobi123 1.17 You need at least 2 GB of free disk space
40 swift 1.1 </li>
41     <li>
42 dertobi123 1.17 If you do not use prebuilt packages, you need at least 300 MB of memory (RAM +
43 sejo 1.24 swap), if you do use prebuilt packages you need at least 64 MB of memory to boot the system.
44 swift 1.1 </li>
45     <li>
46 dertobi123 1.17 For the <e>PowerPC architecture</e>, you can install Gentoo/PPC on NewWorld machines
47 swift 1.1 having a Power or PowerPC microprocessor, including but not limited to G3, G4
48 dertobi123 1.17 or G5 powered Apple computers such as the iMac, the eMac, the iBook, the PowerBook,
49 pylon 1.21 Xserve, PowerMac, and bPlan's Pegasos II. We also provide limited
50 dertobi123 1.17 support for OldWorld systems, IBM (RS/6000, iSeries, pSeries, ...) and Amiga
51 swift 1.7 systems. Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo
52 dertobi123 1.17 PPC FAQ</uri> before you begin.
53 swift 1.1 </li>
54     </ul>
55    
56     </body>
57     </subsection>
58     </section>
59     <section>
60     <title>Make your Choice</title>
61     <subsection>
62     <title>Introduction</title>
63     <body>
64    
65     <p>
66     Still interested in trying out Gentoo? Well, then it is now time to
67     choose the installation medium you want to use. Yes, you have the
68     choice, no, they are not all equal, and yes, the result is always the same: a
69     Gentoo base system.
70     </p>
71    
72     <p>
73     The installation media we will describe are:
74     </p>
75    
76     <ul>
77     <li>Gentoo's Minimal LiveCD</li>
78     <li>Gentoo's Universal LiveCD</li>
79     </ul>
80    
81     <p>
82     Every single media has its advantages and disadvantages. We will list
83     the pros and cons of every medium so you have all the information to
84     make a justified decision. But before we continue, let's explain our
85     three-stage installation.
86     </p>
87    
88     </body>
89     </subsection>
90     <subsection>
91     <title>The Three Stages</title>
92     <body>
93    
94     <p>
95     Gentoo Linux can be installed using one of three <e>stage</e> tarball files.
96     The one you choose depends on how much of the system you want to compile
97     yourself. The <e>stage1</e> tarball is used when you want to bootstrap and
98     build the entire system from scratch. The <e>stage2</e> tarball is used for
99     building the entire system from a bootstrapped &quot;semi-compiled&quot; state.
100     The <e>stage3</e> tarball already contains a basic Gentoo Linux system that has
101     been built for you. As we will explain later, you can also install
102     Gentoo without compiling anything (except your kernel and some optional
103     packages). If you want this, you have to use a <e>stage3</e> tarball.
104     </p>
105    
106     <p>
107     Now what stage do you have to choose?
108     </p>
109    
110     <p>
111     Starting from a <e>stage1</e> allows you to have total control over the
112     optimization settings and optional build-time functionality that is
113     initially enabled on your system. This makes <e>stage1</e> installs good for
114     power users who know what they are doing. It is also a great
115     installation method for those who would like to know more about the
116     inner workings of Gentoo Linux.
117     </p>
118    
119 swift 1.10 <p>
120     A <e>stage1</e> installation can only be performed when you have a working
121     Internet connection.
122     </p>
123    
124 swift 1.1 <table>
125     <tr>
126     <th>Stage1</th>
127     <th>Pros and Cons</th>
128     </tr>
129     <tr>
130     <th>+</th>
131     <ti>
132     Allows you to have total control over the optimization settings and optional
133     build-time functionality that is initially enabled on your system
134     </ti>
135     </tr>
136     <tr>
137     <th>+</th>
138     <ti>Suitable for powerusers that know what they are doing</ti>
139     </tr>
140     <tr>
141     <th>+</th>
142     <ti>Allows you to learn more about the inner workings of Gentoo</ti>
143     </tr>
144     <tr>
145     <th>-</th>
146     <ti>Takes a long time to finish the installation</ti>
147     </tr>
148     <tr>
149     <th>-</th>
150     <ti>
151     If you don't intend to tweak the settings, it is probably a waste of time
152     </ti>
153     </tr>
154 swift 1.10 <tr>
155     <th>-</th>
156     <ti>
157     Not suitable for networkless installations
158     </ti>
159     </tr>
160 swift 1.1 </table>
161    
162     <p>
163     <e>Stage2</e> installs allow you to skip the bootstrap process and doing this
164     is fine if you are happy with the optimization settings that we chose
165     for your particular <e>stage2</e> tarball.
166     </p>
167    
168 swift 1.10 <p>
169     A <e>stage2</e> installation can only be performed when you have a working
170     Internet connection.
171     </p>
172    
173 swift 1.1 <table>
174     <tr>
175     <th>Stage2</th>
176     <th>Pros and Cons</th>
177     </tr>
178     <tr>
179     <th>+</th>
180     <ti>You don't need to bootstrap</ti>
181     </tr>
182     <tr>
183     <th>+</th>
184     <ti>Faster than starting with stage1</ti>
185     </tr>
186     <tr>
187     <th>+</th>
188     <ti>You can still tweak your settings</ti>
189     </tr>
190     <tr>
191     <th>-</th>
192     <ti>You cannot tweak as much as with a stage1</ti>
193     </tr>
194     <tr>
195     <th>-</th>
196     <ti>It's not the fastest way to install Gentoo</ti>
197     </tr>
198     <tr>
199     <th>-</th>
200     <ti>You have to accept the optimizations we chose for the bootstrap</ti>
201     </tr>
202 swift 1.10 <tr>
203     <th>-</th>
204     <ti>
205     Not suitable for networkless installations
206     </ti>
207     </tr>
208 swift 1.1 </table>
209    
210     <p>
211     Choosing to go with a <e>stage3</e> allows for the fastest install of Gentoo
212     Linux, but also means that your base system will have the optimization
213     settings that we chose for you (which to be honest, are good settings
214     and were carefully chosen to enhance performance while maintaining
215     stability). <e>stage3</e> is also required if you want to install Gentoo using
216 swift 1.9 prebuilt packages or without a network connection.
217 swift 1.1 </p>
218    
219     <table>
220     <tr>
221     <th>Stage3</th>
222     <th>Pros and Cons</th>
223     </tr>
224     <tr>
225     <th>+</th>
226     <ti>Fastest way to get a Gentoo base system</ti>
227     </tr>
228     <tr>
229 swift 1.10 <th>+</th>
230     <ti>Suitable for networkless installations</ti>
231     </tr>
232     <tr>
233 swift 1.1 <th>-</th>
234     <ti>You cannot tweak the base system - it's built already</ti>
235     </tr>
236     <tr>
237     <th>-</th>
238     <ti>You cannot brag about having used stage1 or stage2</ti>
239     </tr>
240     </table>
241    
242     <p>
243     Write down (or remember) what stage you want to use. You need this later when
244     you decide what LiveCD (or other installation medium) you want to use. You might
245     be interested to know that, if you decide to use different optimization settings
246     after having installed Gentoo, you will be able to recompile your entire system
247     with the new optimization settings.
248     </p>
249    
250     <p>
251     Now take a look at the available installation media.
252     </p>
253    
254     </body>
255     </subsection>
256     <subsection>
257     <title>Gentoo LiveCDs</title>
258     <body>
259    
260     <p>
261     The <e>Gentoo LiveCDs</e> are bootable CDs which contain a
262     self-sustained Gentoo environment. They allow you to boot Linux from the CD.
263     During the boot process your hardware is detected and the appropriate drivers
264     are loaded. They are maintained by Gentoo developers.
265     </p>
266    
267     <p>
268 swift 1.28 All LiveCDs allow you to boot, set up networking, initialize your
269 swift 1.1 partitions and start installing Gentoo from the Internet. However, some
270     LiveCDs also contain all necessary source code so you are able to install
271     Gentoo without a working network configuration.
272     </p>
273    
274     <p>
275     Now what do these LiveCDs contain?
276     </p>
277    
278     </body>
279     </subsection>
280     <subsection>
281     <title>Gentoo's Minimal LiveCD</title>
282     <body>
283    
284     <p>
285     This is a small, no-nonsense, bootable CD which sole purpose is to boot the
286     system, prepare the networking and continue with the Gentoo installation. It
287     does not contain any stages (or, in some cases, a single stage1 file),
288     source code or precompiled packages. For example the ppc variant of this
289 dertobi123 1.17 LiveCD can be found in the <path>livecd</path> subdirectory and is called
290 swift 1.33 <c>install-ppc-minimal-2004.3.iso</c>.
291 swift 1.1 </p>
292    
293     <table>
294     <tr>
295     <th>Minimal LiveCD</th>
296     <th>Pros and Cons</th>
297     </tr>
298     <tr>
299     <th>+</th>
300     <ti>Smallest download</ti>
301     </tr>
302     <tr>
303     <th>+</th>
304     <ti>Suitable for a complete architecture</ti>
305     </tr>
306     <tr>
307     <th>+</th>
308     <ti>
309     You can do a stage1, stage2 or stage3 by getting the stage tarball off the
310     net
311     </ti>
312     </tr>
313     <tr>
314     <th>-</th>
315     <ti>
316 swift 1.27 Contains no stages, no Portage snapshot, no GRP packages and therefore not
317 swift 1.1 suitable for networkless installation
318     </ti>
319     </tr>
320     </table>
321    
322     </body>
323     </subsection>
324     <subsection>
325     <title>Gentoo's Universal LiveCD</title>
326     <body>
327    
328     <p>
329     Gentoo's Universal LiveCD is a bootable CD suitable to install Gentoo without
330     networking. It contains a stage1 and several stage3 tarballs (optimized for the
331     individual subarchitectures). For example the ppc variant of this CD is called
332 swift 1.33 <c>install-ppc-universal-2004.3.iso</c> and can be found in the
333 dertobi123 1.17 <path>livecd</path> subdirectory.
334 swift 1.1 </p>
335    
336     <p>
337 swift 1.7 If you take a closer look on our mirrors, you will see
338     that we provide <e>Gentoo Package CDs</e>. This CD (which isn't
339 swift 1.1 bootable) only contains precompiled packages and can be used to install software
340     after a succesfull Gentoo Installation. To install Gentoo, you only
341     need the Universal LiveCD, but if you want OpenOffice.org, Mozilla, KDE, GNOME
342     etc. without having to compile every single one of them, you need the Packages
343     CD too. For example the G4 (a subarchitecture of ppc) Packages CD is
344 swift 1.33 called <c>packages-g4-2004.3.iso</c> and can be found in the appropriate
345 swift 1.1 subdirectory (<path>g4/</path>).
346     </p>
347    
348 swift 1.11 <p>
349     You only need the Packages CD if you want to perform a stage3 with GRP
350     installation.
351     </p>
352    
353 swift 1.1 <table>
354     <tr>
355     <th>Universal LiveCD with Packages CD</th>
356     <th>Pros and Cons</th>
357     </tr>
358     <tr>
359     <th>+</th>
360     <ti>Packages CD is optimized to your architecture and subarchitecture</ti>
361     </tr>
362     <tr>
363     <th>+</th>
364     <ti>
365     Packages CD provides precompiled packages for fast Gentoo installations
366     </ti>
367     </tr>
368     <tr>
369     <th>+</th>
370     <ti>
371     Contains everything you need. You can even install without a network
372     connection.
373     </ti>
374     </tr>
375     <tr>
376     <th>-</th>
377     <ti>Huge download</ti>
378     </tr>
379     </table>
380    
381     </body>
382     </subsection>
383     </section>
384     <section>
385     <title>Download, Burn and Boot a Gentoo LiveCD</title>
386     <subsection>
387     <title>Downloading and Burning the LiveCDs</title>
388     <body>
389    
390     <p>
391     You have chosen to use a Gentoo LiveCD (if not, then you are reading the
392     wrong section). We'll first start by downloading and burning the chosen
393     LiveCD. We previously discussed the several available LiveCDs, but where can you
394     find them?
395     </p>
396    
397     <p>
398     Visit one of our <uri
399     link="/main/en/mirrors.xml">mirrors</uri> and go to
400 swift 1.33 <path>releases/ppc/2004.3/livecd</path>, which is
401 swift 1.1 the path where the LiveCD(s) of your choice are located. Inside that
402     directory you'll find so-called ISO-files. Those are full CD images
403     which you can write on a CD-R.
404     </p>
405    
406     <p>
407     In case you wonder if your downloaded file is corrupted or not, you can
408     check its MD5 checksum and compare it with the MD5 checksum we provide (such as
409 swift 1.33 <path>install-ppc-minimal-2004.3.iso.md5</path>). You can check the MD5 checksum
410 swift 1.1 with the <c>md5sum</c> tool under Linux/Unix or <uri
411 neysx 1.16 link="http://www.etree.org/md5com.html">md5sum</uri> for Windows.
412 swift 1.1 </p>
413    
414     <p>
415 dertobi123 1.17 As long as Mac OS X does not support <c>md5sum</c> you have to use the md5
416     capability of <c>openssl</c>. Therefore type in Terminal.app:
417 swift 1.12 </p>
418    
419 dertobi123 1.18 <pre caption="md5sum with the help of openssl">
420 dertobi123 1.17 $ <i>openssl md5 /path/to/iso</i>
421     <comment>This could take some time depending of the size of the ISO and your CPU</comment>
422 swift 1.12 </pre>
423    
424     <p>
425 dertobi123 1.17 Now compare this output with the appropriate file found on the server where you
426     downloaded the ISO (the file will end with .md5). If it is the same, the ISO
427     image downloaded correctly. Be sure you have not mounted it (e.g. with Disk
428     Copy) yet!
429 swift 1.12 </p>
430    
431 dertobi123 1.17 <p>
432     More information are available in our <uri
433 swift 1.33 link="/doc/en/gentoo-ppc-faq.xml">PPC FAQ</uri>.
434 dertobi123 1.17 </p>
435 swift 1.12
436     <p>
437 swift 1.1 To burn the downloaded ISO(s), you have to select raw-burning. How you
438 swift 1.33 do this is highly program-dependent. We will discuss <c>cdrecord</c>,
439     <c>k3b</c> and the MacOS burning possibilities here; more information can be
440     found in our <uri link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri> and the
441     <uri link="/doc/en/gentoo-ppc-faq.xml">PPC FAQ</uri>.
442 swift 1.1 </p>
443    
444     <ul>
445     <li>
446     With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace
447     <path>/dev/hdc</path> with your CD-RW drive's device path) followed
448     by the path to the ISO file :)
449     </li>
450     <li>
451 dertobi123 1.17 With k3b, select <c>Tools</c> &gt; <c>CD</c> &gt; <c>Burn Image</c>. Then
452 bennyc 1.6 you can locate your ISO file within the 'Image to Burn' area. Finally click
453 swift 1.3 <c>Start</c>.
454     </li>
455 swift 1.29 <li>
456     With Mac OS X Panther, launch <c>Disk Utility</c> from
457     <path>Applications/Utilities</path>, select <c>Open</c> from the
458     <c>Images</c> menu, select the mounted disk image in the main window and
459     select <c>Burn</c> in the <c>Images</c> menu.
460     </li>
461     <li>
462     With Mac OS X Jaguar, launch <c>Disk Copy</c> from
463     <path>Applications/Utilities</path>, select <c>Burn Image</c> from the
464     <c>File</c> menu, select the ISO and click the <c>Burn</c> button.
465     </li>
466 swift 1.1 </ul>
467    
468     </body>
469     </subsection>
470 swift 1.7 </section>
471     <section>
472     <title>Booting the PPC LiveCD(s)</title>
473 swift 1.1 <subsection>
474 swift 1.7 <title>Default: Apple/IBM</title>
475 swift 1.1 <body>
476    
477     <p>
478 dertobi123 1.17 On NewWorld machines place the LiveCD in the CD-ROM and reboot the system. When
479     the system-start-bell sounds, simply hold down the 'C' until the CD loads.
480     </p>
481    
482     <p>
483     If you have an OldWorld Mac the bootable portion of the livecd can't be used.
484     Instead you need to download <uri
485     link="http://penguinppc.org/projects/bootx/">BootX</uri> and have a working
486     MacOS installed on your system. You need to copy the <c>BootX Extension</c> from
487     the unpacked archive-file into the <c>Extensions Folder</c> and make a new
488     directory called <c>Linux Kernels</c> in the System Folder. In the next step you
489 swift 1.33 need to copy the files <c>G3G4kernel</c> and <c>initrd.img.gz</c> from the
490     LiveCD <path>boot</path> folder into the <c>Linux Kernels</c> directory. Then
491     reboot the system and wait for BootX to load. After BootX loaded you still have
492     to set up a few items. In the options dialog you need to check <c>Use Specified
493     RAM Disk</c> and select the <c>initrd.img.gz</c> which you put in the <c>Linux
494     Kernels</c> directory. The ramdisk size should be set to at least <c>32000</c>.
495     Furthermore the kernel argument needs to be set to <c>rw init=/linuxrc
496     cdroot</c>. Eventually you are able to boot the LiveCD when you select Linux on
497     Startup.
498 dertobi123 1.17 </p>
499    
500     <p>
501     After the LiveCD loaded, you will be greeted by a friendly welcome message and a
502     <e>boot:</e> prompt at the bottom of the screen.
503 swift 1.1 </p>
504    
505     <p>
506     At this prompt you are able to select a kernel for the subarchitecture you use.
507 dertobi123 1.17 We provide <c>G3</c>, <c>G4</c> and <c>G5</c>. All kernels are built with
508     support for multiple CPUs, but they will boot on single processor machines as
509     well.
510 swift 1.1 </p>
511    
512     <p>
513     You are also able to tweak some kernel options at this prompt. The following
514     table lists the available boot options you can add:
515     </p>
516    
517     <table>
518     <tr>
519     <th>Boot Option</th>
520     <th>Description</th>
521     </tr>
522     <tr>
523     <ti><c>video</c></ti>
524     <ti>
525     This option takes one of the following vendor-specific tags:
526     <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or
527     <c>ofonly</c>. You can follow this tag with the resolution and refreshrate
528     you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are
529     uncertain what to choose, <c>ofonly</c> will most certainly work.
530     </ti>
531     </tr>
532     <tr>
533 pylon 1.2 <ti><c>nol3</c></ti>
534 swift 1.1 <ti>
535 dertobi123 1.17 Disables level 3 cache on some PowerBooks (needed for at least the 17&quot;)
536 swift 1.1 </ti>
537     </tr>
538     <tr>
539     <ti><c>debug</c></ti>
540     <ti>
541     Enables verbose booting, spawns an initrd shell that can be used to debug
542     the LiveCD
543     </ti>
544     </tr>
545 swift 1.7 <tr>
546     <ti><c>sleep=X</c></ti>
547     <ti>
548     Wait X seconds before continuing; this can be needed by some very old SCSI
549     CD-ROMs which don't speed up the CD quick enough
550     </ti>
551     </tr>
552     <tr>
553     <ti><c>bootfrom=X</c></ti>
554     <ti>
555     Boot from a different device
556     </ti>
557     </tr>
558 swift 1.1 </table>
559    
560     <p>
561     At this prompt, hit enter, and a complete Gentoo Linux environment will be
562 swift 1.7 loaded from the CD. Continue with <uri link="#booted">And When You're
563     Booted...</uri>.
564 swift 1.1 </p>
565    
566 swift 1.7 </body>
567     </subsection>
568     <subsection>
569     <title>Alternative: Pegasos</title>
570     <body>
571    
572 swift 1.1 <p>
573 swift 1.7 On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type
574 swift 1.33 <c>boot cd /boot/pegasos</c>. If you need any special boot options you can append them to the
575     command-line. For instance <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.
576 swift 1.1 </p>
577    
578 swift 1.7 </body>
579     </subsection>
580     <subsection id="booted">
581     <title>And When You're Booted...</title>
582     <body>
583 swift 1.1
584     <p>
585 swift 1.7 You will be greeted by a root ("#") prompt on the current console. You can also
586     switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get
587     back to the one you started on by pressing Alt-fn-F1.
588 swift 1.1 </p>
589    
590     <p>
591     If you are installing Gentoo on a system with a non-US keyboard, use
592     <c>loadkeys</c> to load the keymap for your keyboard. To list the available
593 dertobi123 1.17 keymaps, execute <c>ls /usr/share/keymaps/i386</c>. Do not use the keymaps in
594     <path>ppc</path> or <path>mac</path> as they are for ADB-based OldWorld
595     machines.
596 swift 1.1 </p>
597    
598     <pre caption="Listing available keymaps">
599     <comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided
600     on the LiveCD are ADB keymaps and unusable with the LiveCD kernel)</comment>
601     # <i>ls /usr/share/keymaps/i386</i>
602     </pre>
603    
604     <p>
605     Now load the keymap of your choice:
606     </p>
607    
608     <pre caption="Loading a keymap">
609 swift 1.7 # <i>loadkeys be-latin1</i>
610 swift 1.1 </pre>
611    
612     <p>
613     Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>.
614     </p>
615    
616     </body>
617     </subsection>
618     <subsection id="hardware">
619     <title>Extra Hardware Configuration</title>
620     <body>
621    
622     <p>
623 dertobi123 1.17 When the LiveCD boots, it tries to detect all your hardware devices and
624 swift 1.1 loads the appropriate kernel modules to support your hardware. In the
625 dertobi123 1.17 vast majority of cases, it does a very good job. However, in some cases, it may
626     not auto-load the kernel modules you need. If the PCI auto-detection missed some
627     of your system's hardware, you will have to load the appropriate kernel modules
628     manually.
629 swift 1.1 </p>
630    
631     <p>
632 swift 1.33 In the next example we try to load the <c>airport</c> module (support for
633 swift 1.1 certain kinds of network interfaces):
634     </p>
635    
636     <pre caption="Loading kernel modules">
637 swift 1.33 # <i>modprobe airport</i>
638 swift 1.1 </pre>
639    
640     </body>
641     </subsection>
642     <subsection>
643     <title>Optional: Tweaking Hard Disk Performance</title>
644     <body>
645    
646     <p>
647     If you are an advanced user, you might want to tweak the IDE hard disk
648     performance using <c>hdparm</c>. With the <c>-tT</c> options you can
649     test the performance of your disk (execute it several times to get a
650     more precise impression):
651     </p>
652    
653     <pre caption="Testing disk performance">
654     # <i>hdparm -tT /dev/hda</i>
655     </pre>
656    
657     <p>
658     To tweak, you can use any of the following examples (or experiment
659     yourself) which use <path>/dev/hda</path> as disk (substitute with your
660     disk):
661     </p>
662    
663     <pre caption="Tweaking hard disk performance">
664     <comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i>
665     <comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
666     </pre>
667    
668     </body>
669     </subsection>
670 swift 1.20 <subsection id="useraccounts">
671 swift 1.1 <title>Optional: User Accounts</title>
672     <body>
673    
674     <p>
675     If you plan on giving other people access to your installation
676     environment or you want to chat using <c>irssi</c> without root privileges (for
677     security reasons), you need to create the necessary user accounts and change
678     the root password.
679     </p>
680    
681     <p>
682     To change the root password, use the <c>passwd</c> utility:
683     </p>
684    
685     <pre caption="Changing the root password">
686     # <i>passwd</i>
687     New password: <comment>(Enter your new password)</comment>
688     Re-enter password: <comment>(Re-enter your password)</comment>
689     </pre>
690    
691     <p>
692 swift 1.5 To create a user account, we first enter their credentials, followed by
693 swift 1.1 its password. We use <c>useradd</c> and <c>passwd</c> for these tasks.
694     In the next example, we create a user called &quot;john&quot;.
695     </p>
696    
697     <pre caption="Creating a user account">
698 swift 1.30 # <i>useradd -m -G users john</i>
699 swift 1.1 # <i>passwd john</i>
700     New password: <comment>(Enter john's password)</comment>
701     Re-enter password: <comment>(Re-enter john's password)</comment>
702     </pre>
703    
704     <p>
705     You can change your user id from root to the newly created user by using
706     <c>su</c>:
707     </p>
708    
709     <pre caption="Changing user id">
710 swift 1.26 # <i>su - john</i>
711 swift 1.1 </pre>
712    
713     </body>
714     </subsection>
715     <subsection>
716 swift 1.20 <title>Optional: Viewing Documentation while Installing</title>
717     <body>
718    
719     <p>
720     If you want to view the Gentoo Handbook (either from-CD or online) during the
721     installation, make sure you have created a user account (see <uri
722 neysx 1.31 link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to
723 swift 1.20 go to a new terminal and log in.
724     </p>
725    
726     <p>
727     If you want to view the documentation on the CD you can immediately run
728     <c>links2</c> to read it:
729     </p>
730    
731     <pre caption="Viewing the on-CD documentation">
732     # <i>links2 /mnt/cdrom/docs/html/index.html</i>
733     </pre>
734    
735     <p>
736     However, it is preferred that you use the online Gentoo Handbook as it will be
737     more recent than the one provided on the CD. You can view it using <c>links2</c>
738     as well, but only after having completed the <e>Configuring your Network</e>
739     chapter (otherwise you won't be able to go on the Internet to view the
740     document):
741     </p>
742    
743     <pre caption="Viewing the Online Documentation">
744     # <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i>
745     </pre>
746    
747     <p>
748     You can go back to your original terminal by pressing <c>Alt-F1</c>.
749     </p>
750    
751     </body>
752     </subsection>
753     <subsection>
754 swift 1.1 <title>Optional: Starting the SSH Daemon</title>
755     <body>
756    
757     <p>
758     If you want to allow other users to access your computer during the
759     Gentoo installation (perhaps because those users are going to help you
760     install Gentoo, or even do it for you), you need to create a user
761     account for them and perhaps even provide them with your root password
762     (<e>only</e> do that <e>if</e> you <b>fully trust</b> that user).
763     </p>
764    
765     <p>
766     To fire up the SSH daemon, execute the following command:
767     </p>
768    
769     <pre caption="Starting the SSH daemon">
770     # <i>/etc/init.d/sshd start</i>
771     </pre>
772    
773     <p>
774 swift 1.28 To be able to use sshd, you first need to set up your networking. Continue with
775 swift 1.1 the chapter on <uri link="?part=1&amp;chap=3">Configuring your Network</uri>.
776     </p>
777    
778     </body>
779     </subsection>
780     </section>
781     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20