/[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.32
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
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.32 2004/03/29 19:11:27 swift Exp $ -->
8
4<sections> 9<sections>
5<section>
6<title>Timezone</title>
7<body>
8
9<p>
10You now need to select your timezone so that your system knows where it is
11located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
12symlink to <path>/etc/localtime</path> using <c>ln</c>:
13</p>
14
15<pre caption="Setting the timezone information">
16# <i>ls /usr/share/zoneinfo</i>
17<comment>(Suppose you want to use GTM:)</comment>
18# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
19</pre>
20
21</body>
22</section>
23<section> 10<section>
24<title>Filesystem Information</title> 11<title>Filesystem Information</title>
25<subsection> 12<subsection>
26<title>What is fstab?</title> 13<title>What is fstab?</title>
27<body> 14<body>
39<subsection> 26<subsection>
40<title>Creating /etc/fstab</title> 27<title>Creating /etc/fstab</title>
41<body> 28<body>
42 29
43<p> 30<p>
44<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
45fields, seperated by whitespace (space(s), tabs or a mixture). Each field has 32fields, separated by whitespace (space(s), tabs or a mixture). Each field has
46its own meaning: 33its own meaning:
47</p> 34</p>
48 35
49<ul> 36<ul>
50<li> 37<li>
60</li> 47</li>
61<li> 48<li>
62 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 49 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, 50 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 51 you are encouraged to read the mount manpage (<c>man mount</c>) for a full
65 listing. Multiple mountoptions are comma-seperated. 52 listing. Multiple mountoptions are comma-separated.
66</li> 53</li>
67<li> 54<li>
68 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
69 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).
70</li> 57</li>
71<li> 58<li>
72 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
73 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.
74 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>
75 a filesystem check isn't necessary). 62 (or <c>0</c> in case a filesystem check isn't necessary).
76</li> 63</li>
77</ul> 64</ul>
78 65
79<p> 66<p>
80So start <c>nano</c> (or your favorite editor) to create your 67So start <c>nano</c> (or your favorite editor) to create your
84<pre caption="Opening /etc/fstab"> 71<pre caption="Opening /etc/fstab">
85# <i>nano -w /etc/fstab</i> 72# <i>nano -w /etc/fstab</i>
86</pre> 73</pre>
87 74
88<p> 75<p>
89Lets 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>
90partition. 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
91<path>/boot</path> partition, don't copy it verbatim. 78<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
92</p> 79</p>
93 80
94<p> 81<p>
95In our default x86 partitioning example <path>/boot</path> is the 82In our default x86 partitioning example <path>/boot</path> is the
96<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
146<c>user</c> makes it possible for non-root users to mount the CD. 133<c>user</c> makes it possible for non-root users to mount the CD.
147</p> 134</p>
148 135
149<p> 136<p>
150Now use the above example to create your <path>/etc/fstab</path>. If you are a 137Now use the above example to create your <path>/etc/fstab</path>. If you are a
151SPARC-user, you should add the following line to your <path>/etc/fstab</path> 138<b>SPARC</b>-user, you should add the following line to your
139<path>/etc/fstab</path>
152too: 140too:
153</p> 141</p>
154 142
155<pre caption="Adding openprom filesystem to /etc/fstab"> 143<pre caption="Adding openprom filesystem to /etc/fstab">
156none /proc/openprom openpromfs defaults 0 0 144none /proc/openprom openpromfs defaults 0 0
208 196
209<pre caption="Setting the NIS domainname"> 197<pre caption="Setting the NIS domainname">
210# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 198# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
211</pre> 199</pre>
212 200
201<p>
202Now add the <c>domainname</c> script to the default runlevel:
203</p>
204
205<pre caption="Adding domainname to the default runlevel">
206# <i>rc-update add domainname default</i>
207</pre>
208
213</body> 209</body>
214</subsection> 210</subsection>
215<subsection> 211<subsection>
216<title>Configuring your Network</title> 212<title>Configuring your Network</title>
217<body> 213<body>
247iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>" 243iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
248</pre> 244</pre>
249 245
250<p> 246<p>
251If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 247If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
248to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.
252to <c>dhcp</c>. However, if you need to setup your network manually and you're 249If you need to setup your network manually and you're
253not familiar with all the above terms, please read the section on <uri 250not familiar with all the above terms, please read the section on <uri
254link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 251link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
255Terminology</uri> if you haven't done so already. 252Terminology</uri> if you haven't done so already.
256</p> 253</p>
257 254
258<p> 255<p>
259So lets give two examples; the first one uses DHCP, the second one a static IP 256So let us give three examples; the first one uses DHCP, the second one a static
260(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 257IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and
261192.168.0.1: 258gateway 192.168.0.1 while the third one just activates the interface for
259rp-pppoe usage:
262</p> 260</p>
263 261
264<pre caption="Examples for /etc/conf.d/net"> 262<pre caption="Examples for /etc/conf.d/net">
265<comment>(For DHCP:)</comment> 263<comment>(For DHCP)</comment>
266iface_eth0="dhcp" 264iface_eth0="dhcp"
267 265
268<comment>(For static IP:)</comment> 266<comment>(For static IP)</comment>
269iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" 267iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
270gateway="eth0/192.168.0.1" 268gateway="eth0/192.168.0.1"
269
270<comment>(For rp-pppoe)</comment>
271iface_eth0="up"
271</pre> 272</pre>
272 273
273<p> 274<p>
274If you have several network interfaces, create extra <c>iface_eth</c> variables, 275If you have several network interfaces, create extra <c>iface_eth</c> variables,
275like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 276like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
317<p> 318<p>
318You now need to inform Linux about your network. This is defined in 319You 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 320<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 321for 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), 322internal 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 323<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: 324open <path>/etc/hosts</path> and fill in the values:
324</p> 325</p>
325 326
326<pre caption="Opening /etc/hosts"> 327<pre caption="Opening /etc/hosts">
327# <i>nano -w /etc/hosts</i> 328# <i>nano -w /etc/hosts</i>
328</pre> 329</pre>
329 330
330<pre caption="Filling in the networking information"> 331<pre caption="Filling in the networking information">
331127.0.0.1 tux.homenetwork localhost 332127.0.0.1 localhost
332192.168.0.5 jenny 333192.168.0.5 jenny.homenetwork jenny
333192.168.0.56 benny 334192.168.0.6 benny.homenetwork benny
335192.168.0.7 tux.homenetwork tux
334</pre> 336</pre>
335 337
336<p> 338<p>
337If your system is the only system (or the nameservers handle all name 339If your system is the only system (or the nameservers handle all name
338resolution) a single line is sufficient: 340resolution) a single line is sufficient:
339</p> 341</p>
340 342
341<pre caption="/etc/hosts for lonely or fully integrated PCs"> 343<pre caption="/etc/hosts for lonely or fully integrated PCs">
342127.0.0.1 localhost tux 344127.0.0.1 localhost
343</pre> 345</pre>
344 346
345<p> 347<p>
346Save and exit the editor to continue. 348Save and exit the editor to continue.
347</p> 349</p>
348 350
349<p> 351<p>
350If you don't have PCMCIA, you can now continue with <uri 352If you don't have PCMCIA, you can now continue with <uri
351link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 353link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
352following topic on PCMCIA. 354following topic on PCMCIA.
353</p> 355</p>
354 356
355</body> 357</body>
356</subsection> 358</subsection>
357<subsection> 359<subsection>
358<title>Optional: Get PCMCIA Working</title> 360<title>Optional: Get PCMCIA Working</title>
359<body> 361<body>
360 362
363<note>
364pcmcia-cs is only available for x86, amd64 and ppc platforms.
365</note>
366
361<p> 367<p>
362PCMCIA-users should first install the <c>pcmcia-cs</c> package: 368PCMCIA-users should first install the <c>pcmcia-cs</c> package. The
369<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:
363</p> 370</p>
364 371
365<pre caption="Installing pcmcia-cs"> 372<pre caption="Installing pcmcia-cs">
366# <i>emerge -k pcmcia-cs</i> 373# <i>USE="-X" emerge pcmcia-cs</i>
367</pre> 374</pre>
368 375
369<p> 376<p>
370When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 377When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
371runlevel: 378runlevel:
372</p> 379</p>
373 380
374<pre caption="Adding pcmcia to the default runlevel"> 381<pre caption="Adding pcmcia to the default runlevel">
375# <i>rc-update add pcmcia boot</i> 382# <i>rc-update add pcmcia default</i>
376</pre> 383</pre>
377 384
378</body> 385</body>
379</subsection> 386</subsection>
380</section> 387</section>
391# <i>nano -w /etc/rc.conf</i> 398# <i>nano -w /etc/rc.conf</i>
392</pre> 399</pre>
393 400
394<p> 401<p>
395As you can see, this file is well commented to help you set up the necessary 402As you can see, this file is well commented to help you set up the necessary
396configuration variables. When you're finished configuring 403configuration variables. Take special care with the <c>KEYMAP</c> setting: if
397<path>/etc/rc.conf</path>, save and exit to continue. 404you select the wrong <c>KEYMAP</c> you will get weird results when typing on
405your keyboard.
406</p>
407
408<note>
409Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
410select an i386 keymap (such as "us") instead of "sunkeymap".
411</note>
412
413<p>
414<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
415ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
416to set a mac/ppc keymap in <path>rc.conf</path>.
417</p>
418
419<p>
420When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
421continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
398</p> 422</p>
399 423
400</body> 424</body>
401</section> 425</section>
402</sections> 426</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20