/[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.4 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
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 $ -->
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 -s /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, don't copy it verbatim.
92</p> 79</p>
93 80
94<p> 81<p>
123/dev/hda3 / ext3 noatime 0 1 110/dev/hda3 / ext3 noatime 0 1
124</pre> 111</pre>
125 112
126<p> 113<p>
127To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> 114To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
128(required) and for your CD-ROM drive (and ofcourse, if you have other 115(required) and for your CD-ROM drive (and of course, if you have other
129partitions or drives, for those too): 116partitions or drives, for those too):
130</p> 117</p>
131 118
132<pre caption="A full /etc/fstab example"> 119<pre caption="A full /etc/fstab example">
133/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 noauto,noatime 1 2
151SPARC-user, you should add the following line to your <path>/etc/fstab</path> 138SPARC-user, you should add the following line to your <path>/etc/fstab</path>
152too: 139too:
153</p> 140</p>
154 141
155<pre caption="Adding openprom filesystem to /etc/fstab"> 142<pre caption="Adding openprom filesystem to /etc/fstab">
156none /proc/openprom openpromfs defaults 0 0 143none /proc/openprom openpromfs defaults 0 0
144</pre>
145
146<p>
147If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
148</p>
149
150<pre caption="Adding usbfs filesystem to /etc/fstab">
151none /proc/bus/usb usbfs defaults 0 0
157</pre> 152</pre>
158 153
159<p> 154<p>
160Reread your <path>/etc/fstab</path>, save and quit to continue. 155Reread your <path>/etc/fstab</path>, save and quit to continue.
161</p> 156</p>
200 195
201<pre caption="Setting the NIS domainname"> 196<pre caption="Setting the NIS domainname">
202# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 197# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
203</pre> 198</pre>
204 199
200<p>
201Now add the <c>domainname</c> script to the default runlevel:
202</p>
203
204<pre caption="Adding domainname to the default runlevel">
205# <i>rc-update add domainname default</i>
206</pre>
207
205</body> 208</body>
206</subsection> 209</subsection>
207<subsection> 210<subsection>
208<title>Configuring your Network</title> 211<title>Configuring your Network</title>
209<body> 212<body>
246link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 249link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
247Terminology</uri> if you haven't done so already. 250Terminology</uri> if you haven't done so already.
248</p> 251</p>
249 252
250<p> 253<p>
251So 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
252(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
253192.168.0.1: 256192.168.0.1:
254</p> 257</p>
255 258
256<pre caption="Examples for /etc/conf.d/net"> 259<pre caption="Examples for /etc/conf.d/net">
309<p> 312<p>
310You 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
311<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
312for 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
313internal 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),
314<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
315open <path>/etc/hosts</path> and fill in the values: 318open <path>/etc/hosts</path> and fill in the values:
316</p> 319</p>
317 320
318<pre caption="Opening /etc/hosts"> 321<pre caption="Opening /etc/hosts">
319# <i>nano -w /etc/hosts</i> 322# <i>nano -w /etc/hosts</i>
320</pre> 323</pre>
321 324
322<pre caption="Filling in the networking information"> 325<pre caption="Filling in the networking information">
323127.0.0.1 localhost tux 326127.0.0.1 localhost
324192.168.0.5 jenny 327192.168.0.5 jenny
325192.168.0.56 benny 328192.168.0.6 benny
329192.168.0.7 tux
326</pre> 330</pre>
327 331
328<p> 332<p>
329If 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
330resolution) a single line is sufficient: 334resolution) a single line is sufficient:
338Save and exit the editor to continue. 342Save and exit the editor to continue.
339</p> 343</p>
340 344
341<p> 345<p>
342If you don't have PCMCIA, you can now continue with <uri 346If you don't have PCMCIA, you can now continue with <uri
343link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 347link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
344following topic on PCMCIA. 348following topic on PCMCIA.
345</p> 349</p>
346 350
347</body> 351</body>
348</subsection> 352</subsection>
353<p> 357<p>
354PCMCIA-users should first install the <c>pcmcia-cs</c> package: 358PCMCIA-users should first install the <c>pcmcia-cs</c> package:
355</p> 359</p>
356 360
357<pre caption="Installing pcmcia-cs"> 361<pre caption="Installing pcmcia-cs">
358# <i>emerge -k pcmcia-cs</i> 362# <i>emerge --usepkg pcmcia-cs</i>
359</pre> 363</pre>
360 364
361<p> 365<p>
362When <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>
363runlevel: 367runlevel:
364</p> 368</p>
365 369
366<pre caption="Adding pcmcia to the default runlevel"> 370<pre caption="Adding pcmcia to the default runlevel">
367# <i>rc-update add pcmcia boot</i> 371# <i>rc-update add pcmcia default</i>
368</pre> 372</pre>
369 373
370</body> 374</body>
371</subsection> 375</subsection>
372</section> 376</section>
383# <i>nano -w /etc/rc.conf</i> 387# <i>nano -w /etc/rc.conf</i>
384</pre> 388</pre>
385 389
386<p> 390<p>
387As 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
388configuration variables. When you're finished configuring 392configuration variables. Take special care with the <c>KEYMAP</c> setting: if
389<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>.
390</p> 405</p>
391 406
392</body> 407</body>
393</section> 408</section>
394</sections> 409</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20