/[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.7 Revision 1.18
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 -->
6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.18 2004/01/08 14:23:17 swift Exp $ -->
3 8
4<sections> 9<sections>
5<section> 10<section>
6<title>Timezone</title> 11<title>Timezone</title>
7<body> 12<body>
12symlink to <path>/etc/localtime</path> using <c>ln</c>: 17symlink to <path>/etc/localtime</path> using <c>ln</c>:
13</p> 18</p>
14 19
15<pre caption="Setting the timezone information"> 20<pre caption="Setting the timezone information">
16# <i>ls /usr/share/zoneinfo</i> 21# <i>ls /usr/share/zoneinfo</i>
17<comment>(Suppose you want to use GTM:)</comment> 22<comment>(Suppose you want to use GMT:)</comment>
18# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i> 23# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
19</pre> 24</pre>
20 25
21</body> 26</body>
22</section> 27</section>
39<subsection> 44<subsection>
40<title>Creating /etc/fstab</title> 45<title>Creating /etc/fstab</title>
41<body> 46<body>
42 47
43<p> 48<p>
44<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six 49<path>/etc/fstab</path> uses a special syntax. Every line consists of six
45fields, seperated by whitespace (space(s), tabs or a mixture). Each field has 50fields, separated by whitespace (space(s), tabs or a mixture). Each field has
46its own meaning: 51its own meaning:
47</p> 52</p>
48 53
49<ul> 54<ul>
50<li> 55<li>
60</li> 65</li>
61<li> 66<li>
62 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 67 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it
63 wants to mount the partition. As every filesystem has its own mountoptions, 68 wants to mount the partition. As every filesystem has its own mountoptions,
64 you are encouraged to read the mount manpage (<c>man mount</c>) for a full 69 you are encouraged to read the mount manpage (<c>man mount</c>) for a full
65 listing. Multiple mountoptions are comma-seperated. 70 listing. Multiple mountoptions are comma-separated.
66</li> 71</li>
67<li> 72<li>
68 The fifth field is used by <c>dump</c> to determine if the partition needs to 73 The fifth field is used by <c>dump</c> to determine if the partition needs to
69 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 74 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
70</li> 75</li>
71<li> 76<li>
72 The sixth field is used by <c>fsck</c> the order in which filesystems should 77 The sixth field is used by <c>fsck</c> to determine the order in which
73 be <b>check</b>ed if the system wasn't shut down properly. The root filesystem 78 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
74 should have <c>1</c> while the rest should have <c>2</c> (or <c>0</c> in case 79 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
75 a filesystem check isn't necessary). 80 (or <c>0</c> in case a filesystem check isn't necessary).
76</li> 81</li>
77</ul> 82</ul>
78 83
79<p> 84<p>
80So start <c>nano</c> (or your favorite editor) to create your 85So start <c>nano</c> (or your favorite editor) to create your
84<pre caption="Opening /etc/fstab"> 89<pre caption="Opening /etc/fstab">
85# <i>nano -w /etc/fstab</i> 90# <i>nano -w /etc/fstab</i>
86</pre> 91</pre>
87 92
88<p> 93<p>
89Lets take a look at how we write down the options for the <path>/boot</path> 94Let us take a look at how we write down the options for the <path>/boot</path>
90partition. This is just an example, so if your architecture doesn't require a 95partition. This is just an example, so if your architecture doesn't require a
91<path>/boot</path> partition, don't copy it verbatim. 96<path>/boot</path> partition, don't copy it verbatim.
92</p> 97</p>
93 98
94<p> 99<p>
208 213
209<pre caption="Setting the NIS domainname"> 214<pre caption="Setting the NIS domainname">
210# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 215# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
211</pre> 216</pre>
212 217
218<p>
219Now add the <c>domainname</c> script to the default runlevel:
220</p>
221
222<pre caption="Adding domainname to the default runlevel">
223# <i>rc-update add domainname default</i>
224</pre>
225
213</body> 226</body>
214</subsection> 227</subsection>
215<subsection> 228<subsection>
216<title>Configuring your Network</title> 229<title>Configuring your Network</title>
217<body> 230<body>
254link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 267link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
255Terminology</uri> if you haven't done so already. 268Terminology</uri> if you haven't done so already.
256</p> 269</p>
257 270
258<p> 271<p>
259So lets give two examples; the first one uses DHCP, the second one a static IP 272So let us give two examples; the first one uses DHCP, the second one a static IP
260(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 273(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway
261192.168.0.1: 274192.168.0.1:
262</p> 275</p>
263 276
264<pre caption="Examples for /etc/conf.d/net"> 277<pre caption="Examples for /etc/conf.d/net">
317<p> 330<p>
318You now need to inform Linux about your network. This is defined in 331You now need to inform Linux about your network. This is defined in
319<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 332<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses
320for hosts that aren't resolved by your nameserver. For instance, if your 333for hosts that aren't resolved by your nameserver. For instance, if your
321internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 334internal network consists of three PCs called <c>jenny</c> (192.168.0.5),
322<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 335<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would
323open <path>/etc/hosts</path> and fill in the values: 336open <path>/etc/hosts</path> and fill in the values:
324</p> 337</p>
325 338
326<pre caption="Opening /etc/hosts"> 339<pre caption="Opening /etc/hosts">
327# <i>nano -w /etc/hosts</i> 340# <i>nano -w /etc/hosts</i>
328</pre> 341</pre>
329 342
330<pre caption="Filling in the networking information"> 343<pre caption="Filling in the networking information">
331127.0.0.1 tux.homenetwork localhost 344127.0.0.1 localhost
332192.168.0.5 jenny 345192.168.0.5 jenny
333192.168.0.56 benny 346192.168.0.6 benny
347192.168.0.7 tux
334</pre> 348</pre>
335 349
336<p> 350<p>
337If your system is the only system (or the nameservers handle all name 351If your system is the only system (or the nameservers handle all name
338resolution) a single line is sufficient: 352resolution) a single line is sufficient:
361<p> 375<p>
362PCMCIA-users should first install the <c>pcmcia-cs</c> package: 376PCMCIA-users should first install the <c>pcmcia-cs</c> package:
363</p> 377</p>
364 378
365<pre caption="Installing pcmcia-cs"> 379<pre caption="Installing pcmcia-cs">
366# <i>emerge -k pcmcia-cs</i> 380# <i>emerge --usepkg pcmcia-cs</i>
367</pre> 381</pre>
368 382
369<p> 383<p>
370When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 384When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>
371runlevel: 385runlevel:
372</p> 386</p>
373 387
374<pre caption="Adding pcmcia to the default runlevel"> 388<pre caption="Adding pcmcia to the boot runlevel">
375# <i>rc-update add pcmcia boot</i> 389# <i>rc-update add pcmcia boot</i>
376</pre> 390</pre>
377 391
378</body> 392</body>
379</subsection> 393</subsection>
391# <i>nano -w /etc/rc.conf</i> 405# <i>nano -w /etc/rc.conf</i>
392</pre> 406</pre>
393 407
394<p> 408<p>
395As you can see, this file is well commented to help you set up the necessary 409As you can see, this file is well commented to help you set up the necessary
396configuration variables. When you're finished configuring 410configuration variables. Take special care with the <c>KEYMAP</c> setting: if
397<path>/etc/rc.conf</path>, save and exit to continue. 411you select the wrong <c>KEYMAP</c> you will get weird results when typing on
412your keyboard.
413</p>
414
415<note>
416Users of USB-based SPARC systems and SPARC clones might need to select an i386
417keymap (such as "us") instead of "sunkeymap".
418</note>
419
420<p>
421When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
422continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
398</p> 423</p>
399 424
400</body> 425</body>
401</section> 426</section>
402</sections> 427</sections>

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.18

  ViewVC Help
Powered by ViewVC 1.1.20