/[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.3 Revision 1.20
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4<!-- The content of this document is licensed under the CC-BY-SA license -->
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.20 2004/01/19 18:48:52 swift Exp $ -->
8
1<sections> 9<sections>
2<section>
3<title>Timezone</title>
4<body>
5
6<p>
7You now need to select your timezone so that your system knows where it is
8located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
9symlink to <path>/etc/localtime</path> using <c>ln</c>:
10</p>
11
12<pre caption="Setting the timezone information">
13# <i>ls /usr/share/zoneinfo</i>
14<comment>(Suppose you want to use GTM:)</comment>
15# <i>ln -s /usr/share/zoneinfo/GMT /etc/localtime</i>
16</pre>
17
18</body>
19</section>
20<section> 10<section>
21<title>Filesystem Information</title> 11<title>Filesystem Information</title>
22<subsection> 12<subsection>
23<title>What is fstab?</title> 13<title>What is fstab?</title>
24<body> 14<body>
36<subsection> 26<subsection>
37<title>Creating /etc/fstab</title> 27<title>Creating /etc/fstab</title>
38<body> 28<body>
39 29
40<p> 30<p>
41<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
42fields, 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
43its own meaning: 33its own meaning:
44</p> 34</p>
45 35
46<ul> 36<ul>
47<li> 37<li>
57</li> 47</li>
58<li> 48<li>
59 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
60 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,
61 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
62 listing. Multiple mountoptions are comma-seperated. 52 listing. Multiple mountoptions are comma-separated.
63</li> 53</li>
64<li> 54<li>
65 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
66 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).
67</li> 57</li>
68<li> 58<li>
69 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
70 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.
71 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>
72 a filesystem check isn't necessary). 62 (or <c>0</c> in case a filesystem check isn't necessary).
73</li> 63</li>
74</ul> 64</ul>
75 65
76<p> 66<p>
77So start <c>nano</c> (or your favorite editor) to create your 67So start <c>nano</c> (or your favorite editor) to create your
81<pre caption="Opening /etc/fstab"> 71<pre caption="Opening /etc/fstab">
82# <i>nano -w /etc/fstab</i> 72# <i>nano -w /etc/fstab</i>
83</pre> 73</pre>
84 74
85<p> 75<p>
86Lets 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>
87partition. 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
88<path>/boot</path> partition, don't copy it verbatim. 78<path>/boot</path> partition, don't copy it verbatim.
89</p> 79</p>
90 80
91<p> 81<p>
120/dev/hda3 / ext3 noatime 0 1 110/dev/hda3 / ext3 noatime 0 1
121</pre> 111</pre>
122 112
123<p> 113<p>
124To 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>
125(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
126partitions or drives, for those too): 116partitions or drives, for those too):
127</p> 117</p>
128 118
129<pre caption="A full /etc/fstab example"> 119<pre caption="A full /etc/fstab example">
130/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 noauto,noatime 1 2
148SPARC-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>
149too: 139too:
150</p> 140</p>
151 141
152<pre caption="Adding openprom filesystem to /etc/fstab"> 142<pre caption="Adding openprom filesystem to /etc/fstab">
153none /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
154</pre> 152</pre>
155 153
156<p> 154<p>
157Reread your <path>/etc/fstab</path>, save and quit to continue. 155Reread your <path>/etc/fstab</path>, save and quit to continue.
158</p> 156</p>
197 195
198<pre caption="Setting the NIS domainname"> 196<pre caption="Setting the NIS domainname">
199# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 197# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
200</pre> 198</pre>
201 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
202</body> 208</body>
203</subsection> 209</subsection>
204<subsection> 210<subsection>
205<title>Configuring your Network</title> 211<title>Configuring your Network</title>
206<body> 212<body>
243link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 249link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
244Terminology</uri> if you haven't done so already. 250Terminology</uri> if you haven't done so already.
245</p> 251</p>
246 252
247<p> 253<p>
248So 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
249(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
250192.168.0.1: 256192.168.0.1:
251</p> 257</p>
252 258
253<pre caption="Examples for /etc/conf.d/net"> 259<pre caption="Examples for /etc/conf.d/net">
306<p> 312<p>
307You 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
308<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
309for 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
310internal 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),
311<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
312open <path>/etc/hosts</path> and fill in the values: 318open <path>/etc/hosts</path> and fill in the values:
313</p> 319</p>
314 320
315<pre caption="Opening /etc/hosts"> 321<pre caption="Opening /etc/hosts">
316# <i>nano -w /etc/hosts</i> 322# <i>nano -w /etc/hosts</i>
317</pre> 323</pre>
318 324
319<pre caption="Filling in the networking information"> 325<pre caption="Filling in the networking information">
320127.0.0.1 localhost tux 326127.0.0.1 localhost
321192.168.0.5 jenny 327192.168.0.5 jenny
322192.168.0.56 benny 328192.168.0.6 benny
329192.168.0.7 tux
323</pre> 330</pre>
324 331
325<p> 332<p>
326If 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
327resolution) a single line is sufficient: 334resolution) a single line is sufficient:
335Save and exit the editor to continue. 342Save and exit the editor to continue.
336</p> 343</p>
337 344
338<p> 345<p>
339If you don't have PCMCIA, you can now continue with <uri 346If you don't have PCMCIA, you can now continue with <uri
340link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 347link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
341following topic on PCMCIA. 348following topic on PCMCIA.
342</p> 349</p>
343 350
344</body> 351</body>
345</subsection> 352</subsection>
350<p> 357<p>
351PCMCIA-users should first install the <c>pcmcia-cs</c> package: 358PCMCIA-users should first install the <c>pcmcia-cs</c> package:
352</p> 359</p>
353 360
354<pre caption="Installing pcmcia-cs"> 361<pre caption="Installing pcmcia-cs">
355# <i>emerge -k pcmcia-cs</i> 362# <i>emerge --usepkg pcmcia-cs</i>
356</pre> 363</pre>
357 364
358<p> 365<p>
359When <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>
360runlevel: 367runlevel:
361</p> 368</p>
362 369
363<pre caption="Adding pcmcia to the default runlevel"> 370<pre caption="Adding pcmcia to the default runlevel">
364# <i>rc-update add pcmcia boot</i> 371# <i>rc-update add pcmcia default</i>
365</pre> 372</pre>
366 373
367</body> 374</body>
368</subsection> 375</subsection>
369</section> 376</section>
380# <i>nano -w /etc/rc.conf</i> 387# <i>nano -w /etc/rc.conf</i>
381</pre> 388</pre>
382 389
383<p> 390<p>
384As 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
385configuration variables. When you're finished configuring 392configuration variables. Take special care with the <c>KEYMAP</c> setting: if
386<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>.
387</p> 405</p>
388 406
389</body> 407</body>
390</section> 408</section>
391</sections> 409</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20