/[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.13 Revision 1.20
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.13 2003/12/07 12:15:17 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.20 2004/01/19 18:48:52 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, don't copy it verbatim.
94</p> 79</p>
95 80
96<p> 81<p>
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 249link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
265Terminology</uri> if you haven't done so already. 250Terminology</uri> if you haven't done so already.
266</p> 251</p>
267 252
268<p> 253<p>
269So lets give two examples; the first one uses DHCP, the second one a static IP 254So let us give two examples; the first one uses DHCP, the second one a static IP
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 255(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway
271192.168.0.1: 256192.168.0.1:
272</p> 257</p>
273 258
274<pre caption="Examples for /etc/conf.d/net"> 259<pre caption="Examples for /etc/conf.d/net">
327<p> 312<p>
328You now need to inform Linux about your network. This is defined in 313You now need to inform Linux about your network. This is defined in
329<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 314<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses
330for hosts that aren't resolved by your nameserver. For instance, if your 315for hosts that aren't resolved by your nameserver. For instance, if your
331internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 316internal network consists of three PCs called <c>jenny</c> (192.168.0.5),
332<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 317<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would
333open <path>/etc/hosts</path> and fill in the values: 318open <path>/etc/hosts</path> and fill in the values:
334</p> 319</p>
335 320
336<pre caption="Opening /etc/hosts"> 321<pre caption="Opening /etc/hosts">
337# <i>nano -w /etc/hosts</i> 322# <i>nano -w /etc/hosts</i>
338</pre> 323</pre>
339 324
340<pre caption="Filling in the networking information"> 325<pre caption="Filling in the networking information">
341127.0.0.1 tux.homenetwork localhost 326127.0.0.1 localhost
342192.168.0.5 jenny 327192.168.0.5 jenny
343192.168.0.56 benny 328192.168.0.6 benny
329192.168.0.7 tux
344</pre> 330</pre>
345 331
346<p> 332<p>
347If your system is the only system (or the nameservers handle all name 333If your system is the only system (or the nameservers handle all name
348resolution) a single line is sufficient: 334resolution) a single line is sufficient:
356Save and exit the editor to continue. 342Save and exit the editor to continue.
357</p> 343</p>
358 344
359<p> 345<p>
360If you don't have PCMCIA, you can now continue with <uri 346If you don't have PCMCIA, you can now continue with <uri
361link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 347link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
362following topic on PCMCIA. 348following topic on PCMCIA.
363</p> 349</p>
364 350
365</body> 351</body>
366</subsection> 352</subsection>
375<pre caption="Installing pcmcia-cs"> 361<pre caption="Installing pcmcia-cs">
376# <i>emerge --usepkg pcmcia-cs</i> 362# <i>emerge --usepkg pcmcia-cs</i>
377</pre> 363</pre>
378 364
379<p> 365<p>
380When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 366When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
381runlevel: 367runlevel:
382</p> 368</p>
383 369
384<pre caption="Adding pcmcia to the boot runlevel"> 370<pre caption="Adding pcmcia to the default runlevel">
385# <i>rc-update add pcmcia boot</i> 371# <i>rc-update add pcmcia default</i>
386</pre> 372</pre>
387 373
388</body> 374</body>
389</subsection> 375</subsection>
390</section> 376</section>
401# <i>nano -w /etc/rc.conf</i> 387# <i>nano -w /etc/rc.conf</i>
402</pre> 388</pre>
403 389
404<p> 390<p>
405As you can see, this file is well commented to help you set up the necessary 391As you can see, this file is well commented to help you set up the necessary
406configuration variables. When you're finished configuring 392configuration variables. Take special care with the <c>KEYMAP</c> setting: if
407<path>/etc/rc.conf</path>, save and exit to continue. 393you select the wrong <c>KEYMAP</c> you will get weird results when typing on
394your keyboard.
395</p>
396
397<note>
398Users of USB-based SPARC systems and SPARC clones might need to select an i386
399keymap (such as "us") instead of "sunkeymap".
400</note>
401
402<p>
403When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
404continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
408</p> 405</p>
409 406
410</body> 407</body>
411</section> 408</section>
412</sections> 409</sections>

Legend:
Removed from v.1.13  
changed lines
  Added in v.1.20

  ViewVC Help
Powered by ViewVC 1.1.20