|
|
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.30 2004/03/21 10:21:35 swift Exp $ --> |
|
|
8 | |
| 4 | <sections> |
9 | <sections> |
| 5 | <section> |
|
|
| 6 | <title>Timezone</title> |
|
|
| 7 | <body> |
|
|
| 8 | |
|
|
| 9 | <p> |
|
|
| 10 | You now need to select your timezone so that your system knows where it is |
|
|
| 11 | located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a |
|
|
| 12 | symlink 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 |
| 45 | fields, seperated by whitespace (space(s), tabs or a mixture). Each field has |
32 | fields, separated by whitespace (space(s), tabs or a mixture). Each field has |
| 46 | its own meaning: |
33 | its 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> |
| 80 | So start <c>nano</c> (or your favorite editor) to create your |
67 | So 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> |
| 89 | Lets take a look at how we write down the options for the <path>/boot</path> |
76 | Let us take a look at how we write down the options for the <path>/boot</path> |
| 90 | partition. This is just an example, so if your architecture doesn't require a |
77 | partition. 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 PPC), don't copy it verbatim. |
| 92 | </p> |
79 | </p> |
| 93 | |
80 | |
| 94 | <p> |
81 | <p> |
| 95 | In our default x86 partitioning example <path>/boot</path> is the |
82 | In 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 |
| … | |
… | |
| 123 | /dev/hda3 / ext3 noatime 0 1 |
110 | /dev/hda3 / ext3 noatime 0 1 |
| 124 | </pre> |
111 | </pre> |
| 125 | |
112 | |
| 126 | <p> |
113 | <p> |
| 127 | To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> |
114 | To 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 |
| 129 | partitions or drives, for those too): |
116 | partitions 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 |
| … | |
… | |
| 151 | SPARC-user, you should add the following line to your <path>/etc/fstab</path> |
138 | SPARC-user, you should add the following line to your <path>/etc/fstab</path> |
| 152 | too: |
139 | too: |
| 153 | </p> |
140 | </p> |
| 154 | |
141 | |
| 155 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
142 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
| 156 | none /proc/openprom openpromfs defaults 0 0 |
143 | none /proc/openprom openpromfs defaults 0 0 |
|
|
144 | </pre> |
|
|
145 | |
|
|
146 | <p> |
|
|
147 | If 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"> |
|
|
151 | none /proc/bus/usb usbfs defaults 0 0 |
| 157 | </pre> |
152 | </pre> |
| 158 | |
153 | |
| 159 | <p> |
154 | <p> |
| 160 | Reread your <path>/etc/fstab</path>, save and quit to continue. |
155 | Reread 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 > /etc/nisdomainname</i> |
197 | # <i>echo nis.homenetwork > /etc/nisdomainname</i> |
| 203 | </pre> |
198 | </pre> |
| 204 | |
199 | |
|
|
200 | <p> |
|
|
201 | Now 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> |
| … | |
… | |
| 239 | iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>" |
242 | iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>" |
| 240 | </pre> |
243 | </pre> |
| 241 | |
244 | |
| 242 | <p> |
245 | <p> |
| 243 | If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> |
246 | If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> |
|
|
247 | to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. |
| 244 | to <c>dhcp</c>. However, if you need to setup your network manually and you're |
248 | If you need to setup your network manually and you're |
| 245 | not familiar with all the above terms, please read the section on <uri |
249 | not familiar with all the above terms, please read the section on <uri |
| 246 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
250 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
| 247 | Terminology</uri> if you haven't done so already. |
251 | Terminology</uri> if you haven't done so already. |
| 248 | </p> |
252 | </p> |
| 249 | |
253 | |
| 250 | <p> |
254 | <p> |
| 251 | So lets give two examples; the first one uses DHCP, the second one a static IP |
255 | So let us give three examples; the first one uses DHCP, the second one a static |
| 252 | (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway |
256 | IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and |
| 253 | 192.168.0.1: |
257 | gateway 192.168.0.1 while the third one just activates the interface for |
|
|
258 | rp-pppoe usage: |
| 254 | </p> |
259 | </p> |
| 255 | |
260 | |
| 256 | <pre caption="Examples for /etc/conf.d/net"> |
261 | <pre caption="Examples for /etc/conf.d/net"> |
| 257 | <comment>(For DHCP:)</comment> |
262 | <comment>(For DHCP)</comment> |
| 258 | iface_eth0="dhcp" |
263 | iface_eth0="dhcp" |
| 259 | |
264 | |
| 260 | <comment>(For static IP:)</comment> |
265 | <comment>(For static IP)</comment> |
| 261 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
266 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
| 262 | gateway="eth0/192.168.0.1" |
267 | gateway="eth0/192.168.0.1" |
|
|
268 | |
|
|
269 | <comment>(For rp-pppoe)</comment> |
|
|
270 | iface_eth0="up" |
| 263 | </pre> |
271 | </pre> |
| 264 | |
272 | |
| 265 | <p> |
273 | <p> |
| 266 | If you have several network interfaces, create extra <c>iface_eth</c> variables, |
274 | If you have several network interfaces, create extra <c>iface_eth</c> variables, |
| 267 | like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable |
275 | like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable |
| … | |
… | |
| 309 | <p> |
317 | <p> |
| 310 | You now need to inform Linux about your network. This is defined in |
318 | You 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 |
319 | <path>/etc/hosts</path> and helps in resolving hostnames to IP addresses |
| 312 | for hosts that aren't resolved by your nameserver. For instance, if your |
320 | for hosts that aren't resolved by your nameserver. For instance, if your |
| 313 | internal network consists of three PCs called <c>jenny</c> (192.168.0.5), |
321 | internal 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 |
322 | <c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would |
| 315 | open <path>/etc/hosts</path> and fill in the values: |
323 | open <path>/etc/hosts</path> and fill in the values: |
| 316 | </p> |
324 | </p> |
| 317 | |
325 | |
| 318 | <pre caption="Opening /etc/hosts"> |
326 | <pre caption="Opening /etc/hosts"> |
| 319 | # <i>nano -w /etc/hosts</i> |
327 | # <i>nano -w /etc/hosts</i> |
| 320 | </pre> |
328 | </pre> |
| 321 | |
329 | |
| 322 | <pre caption="Filling in the networking information"> |
330 | <pre caption="Filling in the networking information"> |
| 323 | 127.0.0.1 localhost tux |
331 | 127.0.0.1 localhost |
| 324 | 192.168.0.5 jenny |
332 | 192.168.0.5 jenny.homenetwork jenny |
| 325 | 192.168.0.56 benny |
333 | 192.168.0.6 benny.homenetwork benny |
|
|
334 | 192.168.0.7 tux.homenetwork tux |
| 326 | </pre> |
335 | </pre> |
| 327 | |
336 | |
| 328 | <p> |
337 | <p> |
| 329 | If your system is the only system (or the nameservers handle all name |
338 | If your system is the only system (or the nameservers handle all name |
| 330 | resolution) a single line is sufficient: |
339 | resolution) a single line is sufficient: |
| 331 | </p> |
340 | </p> |
| 332 | |
341 | |
| 333 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
342 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 334 | 127.0.0.1 localhost tux |
343 | 127.0.0.1 localhost |
| 335 | </pre> |
344 | </pre> |
| 336 | |
345 | |
| 337 | <p> |
346 | <p> |
| 338 | Save and exit the editor to continue. |
347 | Save and exit the editor to continue. |
| 339 | </p> |
348 | </p> |
| 340 | |
349 | |
| 341 | <p> |
350 | <p> |
| 342 | If you don't have PCMCIA, you can now continue with <uri |
351 | If you don't have PCMCIA, you can now continue with <uri |
| 343 | link="#doc_chap4">System Information</uri>. PCMCIA-users should read the |
352 | link="#doc_chap3">System Information</uri>. PCMCIA-users should read the |
| 344 | following topic on PCMCIA. |
353 | following topic on PCMCIA. |
| 345 | </p> |
354 | </p> |
| 346 | |
355 | |
| 347 | </body> |
356 | </body> |
| 348 | </subsection> |
357 | </subsection> |
| 349 | <subsection> |
358 | <subsection> |
| 350 | <title>Optional: Get PCMCIA Working</title> |
359 | <title>Optional: Get PCMCIA Working</title> |
| 351 | <body> |
360 | <body> |
| 352 | |
361 | |
| 353 | <p> |
362 | <p> |
| 354 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
363 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. The |
|
|
364 | <c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment: |
| 355 | </p> |
365 | </p> |
| 356 | |
366 | |
| 357 | <pre caption="Installing pcmcia-cs"> |
367 | <pre caption="Installing pcmcia-cs"> |
| 358 | # <i>emerge -k pcmcia-cs</i> |
368 | # <i>USE="-X" emerge pcmcia-cs</i> |
| 359 | </pre> |
369 | </pre> |
| 360 | |
370 | |
| 361 | <p> |
371 | <p> |
| 362 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> |
372 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 363 | runlevel: |
373 | runlevel: |
| 364 | </p> |
374 | </p> |
| 365 | |
375 | |
| 366 | <pre caption="Adding pcmcia to the default runlevel"> |
376 | <pre caption="Adding pcmcia to the default runlevel"> |
| 367 | # <i>rc-update add pcmcia boot</i> |
377 | # <i>rc-update add pcmcia default</i> |
| 368 | </pre> |
378 | </pre> |
| 369 | |
379 | |
| 370 | </body> |
380 | </body> |
| 371 | </subsection> |
381 | </subsection> |
| 372 | </section> |
382 | </section> |
| … | |
… | |
| 383 | # <i>nano -w /etc/rc.conf</i> |
393 | # <i>nano -w /etc/rc.conf</i> |
| 384 | </pre> |
394 | </pre> |
| 385 | |
395 | |
| 386 | <p> |
396 | <p> |
| 387 | As you can see, this file is well commented to help you set up the necessary |
397 | As you can see, this file is well commented to help you set up the necessary |
| 388 | configuration variables. When you're finished configuring |
398 | configuration variables. Take special care with the <c>KEYMAP</c> setting: if |
| 389 | <path>/etc/rc.conf</path>, save and exit to continue. |
399 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
|
|
400 | your keyboard. |
|
|
401 | </p> |
|
|
402 | |
|
|
403 | <note> |
|
|
404 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
|
|
405 | keymap (such as "us") instead of "sunkeymap". |
|
|
406 | </note> |
|
|
407 | |
|
|
408 | <p> |
|
|
409 | PPC uses x86 keymaps on most systems. Users who want to be able to use ADB |
|
|
410 | keymaps on boot have to enable ADB keycode sendings in their kernel and have to |
|
|
411 | set a mac/ppc keymap in <path>rc.conf</path>. |
|
|
412 | </p> |
|
|
413 | |
|
|
414 | <p> |
|
|
415 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
|
|
416 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
| 390 | </p> |
417 | </p> |
| 391 | |
418 | |
| 392 | </body> |
419 | </body> |
| 393 | </section> |
420 | </section> |
| 394 | </sections> |
421 | </sections> |
Parent Directory
| 
Revision Log
| 
Patch