/[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.10 - (hide annotations) (download) (as text)
Sun May 9 10:36:50 2004 UTC (10 years, 7 months ago) by swift
Branch: MAIN
Changes since 1.9: +27 -1 lines
File MIME type: application/xml
#50520 - Make it more prominent that stage1 and stage2 cannot be used for networkless installations and that stage3 does

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

  ViewVC Help
Powered by ViewVC 1.1.20