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

Diff of /xml/htdocs/doc/en/handbook/hb-install-config.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.16 Revision 1.30
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
1<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3 6
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.16 2004/01/04 17:33:58 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.30 2004/03/21 10:21:35 swift Exp $ -->
5 8
6<sections> 9<sections>
7<section>
8<title>Timezone</title>
9<body>
10
11<p>
12You now need to select your timezone so that your system knows where it is
13located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
14symlink to <path>/etc/localtime</path> using <c>ln</c>:
15</p>
16
17<pre caption="Setting the timezone information">
18# <i>ls /usr/share/zoneinfo</i>
19<comment>(Suppose you want to use GMT:)</comment>
20# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
21</pre>
22
23</body>
24</section>
25<section> 10<section>
26<title>Filesystem Information</title> 11<title>Filesystem Information</title>
27<subsection> 12<subsection>
28<title>What is fstab?</title> 13<title>What is fstab?</title>
29<body> 14<body>
41<subsection> 26<subsection>
42<title>Creating /etc/fstab</title> 27<title>Creating /etc/fstab</title>
43<body> 28<body>
44 29
45<p> 30<p>
46<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six 31<path>/etc/fstab</path> uses a special syntax. Every line consists of six
47fields, separated by whitespace (space(s), tabs or a mixture). Each field has 32fields, separated by whitespace (space(s), tabs or a mixture). Each field has
48its own meaning: 33its own meaning:
49</p> 34</p>
50 35
51<ul> 36<ul>
69<li> 54<li>
70 The fifth field is used by <c>dump</c> to determine if the partition needs to 55 The fifth field is used by <c>dump</c> to determine if the partition needs to
71 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 56 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
72</li> 57</li>
73<li> 58<li>
74 The sixth field is used by <c>fsck</c> the order in which filesystems should 59 The sixth field is used by <c>fsck</c> to determine the order in which
75 be <b>check</b>ed if the system wasn't shut down properly. The root filesystem 60 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
76 should have <c>1</c> while the rest should have <c>2</c> (or <c>0</c> in case 61 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
77 a filesystem check isn't necessary). 62 (or <c>0</c> in case a filesystem check isn't necessary).
78</li> 63</li>
79</ul> 64</ul>
80 65
81<p> 66<p>
82So start <c>nano</c> (or your favorite editor) to create your 67So start <c>nano</c> (or your favorite editor) to create your
86<pre caption="Opening /etc/fstab"> 71<pre caption="Opening /etc/fstab">
87# <i>nano -w /etc/fstab</i> 72# <i>nano -w /etc/fstab</i>
88</pre> 73</pre>
89 74
90<p> 75<p>
91Lets take a look at how we write down the options for the <path>/boot</path> 76Let us take a look at how we write down the options for the <path>/boot</path>
92partition. This is just an example, so if your architecture doesn't require a 77partition. This is just an example, so if your architecture doesn't require a
93<path>/boot</path> partition, don't copy it verbatim. 78<path>/boot</path> partition (such as PPC), don't copy it verbatim.
94</p> 79</p>
95 80
96<p> 81<p>
97In our default x86 partitioning example <path>/boot</path> is the 82In our default x86 partitioning example <path>/boot</path> is the
98<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't 83<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't
257iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>" 242iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
258</pre> 243</pre>
259 244
260<p> 245<p>
261If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 246If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
247to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.
262to <c>dhcp</c>. However, if you need to setup your network manually and you're 248If you need to setup your network manually and you're
263not familiar with all the above terms, please read the section on <uri 249not familiar with all the above terms, please read the section on <uri
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 250link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
265Terminology</uri> if you haven't done so already. 251Terminology</uri> if you haven't done so already.
266</p> 252</p>
267 253
268<p> 254<p>
269So lets give two examples; the first one uses DHCP, the second one a static IP 255So let us give three examples; the first one uses DHCP, the second one a static
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 256IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and
271192.168.0.1: 257gateway 192.168.0.1 while the third one just activates the interface for
258rp-pppoe usage:
272</p> 259</p>
273 260
274<pre caption="Examples for /etc/conf.d/net"> 261<pre caption="Examples for /etc/conf.d/net">
275<comment>(For DHCP:)</comment> 262<comment>(For DHCP)</comment>
276iface_eth0="dhcp" 263iface_eth0="dhcp"
277 264
278<comment>(For static IP:)</comment> 265<comment>(For static IP)</comment>
279iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" 266iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
280gateway="eth0/192.168.0.1" 267gateway="eth0/192.168.0.1"
268
269<comment>(For rp-pppoe)</comment>
270iface_eth0="up"
281</pre> 271</pre>
282 272
283<p> 273<p>
284If you have several network interfaces, create extra <c>iface_eth</c> variables, 274If you have several network interfaces, create extra <c>iface_eth</c> variables,
285like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 275like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
337# <i>nano -w /etc/hosts</i> 327# <i>nano -w /etc/hosts</i>
338</pre> 328</pre>
339 329
340<pre caption="Filling in the networking information"> 330<pre caption="Filling in the networking information">
341127.0.0.1 localhost 331127.0.0.1 localhost
342192.168.0.5 jenny 332192.168.0.5 jenny.homenetwork jenny
343192.168.0.6 benny 333192.168.0.6 benny.homenetwork benny
344192.168.0.7 tux 334192.168.0.7 tux.homenetwork tux
345</pre> 335</pre>
346 336
347<p> 337<p>
348If your system is the only system (or the nameservers handle all name 338If your system is the only system (or the nameservers handle all name
349resolution) a single line is sufficient: 339resolution) a single line is sufficient:
350</p> 340</p>
351 341
352<pre caption="/etc/hosts for lonely or fully integrated PCs"> 342<pre caption="/etc/hosts for lonely or fully integrated PCs">
353127.0.0.1 localhost tux 343127.0.0.1 localhost
354</pre> 344</pre>
355 345
356<p> 346<p>
357Save and exit the editor to continue. 347Save and exit the editor to continue.
358</p> 348</p>
359 349
360<p> 350<p>
361If you don't have PCMCIA, you can now continue with <uri 351If you don't have PCMCIA, you can now continue with <uri
362link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 352link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
363following topic on PCMCIA. 353following topic on PCMCIA.
364</p> 354</p>
365 355
366</body> 356</body>
367</subsection> 357</subsection>
368<subsection> 358<subsection>
369<title>Optional: Get PCMCIA Working</title> 359<title>Optional: Get PCMCIA Working</title>
370<body> 360<body>
371 361
372<p> 362<p>
373PCMCIA-users should first install the <c>pcmcia-cs</c> package: 363PCMCIA-users should first install the <c>pcmcia-cs</c> package. The
364<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:
374</p> 365</p>
375 366
376<pre caption="Installing pcmcia-cs"> 367<pre caption="Installing pcmcia-cs">
377# <i>emerge --usepkg pcmcia-cs</i> 368# <i>USE="-X" emerge pcmcia-cs</i>
378</pre> 369</pre>
379 370
380<p> 371<p>
381When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 372When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
382runlevel: 373runlevel:
383</p> 374</p>
384 375
385<pre caption="Adding pcmcia to the boot runlevel"> 376<pre caption="Adding pcmcia to the default runlevel">
386# <i>rc-update add pcmcia boot</i> 377# <i>rc-update add pcmcia default</i>
387</pre> 378</pre>
388 379
389</body> 380</body>
390</subsection> 381</subsection>
391</section> 382</section>
413Users of USB-based SPARC systems and SPARC clones might need to select an i386 404Users of USB-based SPARC systems and SPARC clones might need to select an i386
414keymap (such as "us") instead of "sunkeymap". 405keymap (such as "us") instead of "sunkeymap".
415</note> 406</note>
416 407
417<p> 408<p>
409PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
410keymaps on boot have to enable ADB keycode sendings in their kernel and have to
411set a mac/ppc keymap in <path>rc.conf</path>.
412</p>
413
414<p>
418When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 415When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
419continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 416continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
420</p> 417</p>
421 418
422</body> 419</body>

Legend:
Removed from v.1.16  
changed lines
  Added in v.1.30

  ViewVC Help
Powered by ViewVC 1.1.20