| … | |
… | |
| 2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3 | |
3 | |
| 4 | <!-- 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 --> |
| 5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 6 | |
6 | |
| 7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.36 2004/07/09 11:24:20 neysx Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.46 2004/09/11 13:34:53 swift Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | <section> |
10 | <section> |
| 11 | <title>Filesystem Information</title> |
11 | <title>Filesystem Information</title> |
| 12 | <subsection> |
12 | <subsection> |
| … | |
… | |
| 15 | |
15 | |
| 16 | <p> |
16 | <p> |
| 17 | Under Linux, all partitions used by the system must be listed in |
17 | Under Linux, all partitions used by the system must be listed in |
| 18 | <path>/etc/fstab</path>. This file contains the mountpoints of those partitions |
18 | <path>/etc/fstab</path>. This file contains the mountpoints of those partitions |
| 19 | (where they are seen in the file system structure), how they should be mounted |
19 | (where they are seen in the file system structure), how they should be mounted |
| 20 | (special options) and when (automatically or not, can users mount those or not, |
20 | and with what special options (automatically or not, whether users can mount |
| 21 | etc.). |
21 | them or not, etc.) |
| 22 | </p> |
22 | </p> |
| 23 | |
23 | |
| 24 | </body> |
24 | </body> |
| 25 | </subsection> |
25 | </subsection> |
| 26 | <subsection> |
26 | <subsection> |
| … | |
… | |
| 57 | </li> |
57 | </li> |
| 58 | <li> |
58 | <li> |
| 59 | The sixth field is used by <c>fsck</c> to determine the order in which |
59 | The sixth field is used by <c>fsck</c> to determine the order in which |
| 60 | filesystems should be <b>check</b>ed if the system wasn't shut down properly. |
60 | filesystems should be <b>check</b>ed if the system wasn't shut down properly. |
| 61 | The root filesystem should have <c>1</c> while the rest should have <c>2</c> |
61 | The root filesystem should have <c>1</c> while the rest should have <c>2</c> |
| 62 | (or <c>0</c> in case a filesystem check isn't necessary). |
62 | (or <c>0</c> if a filesystem check isn't necessary). |
| 63 | </li> |
63 | </li> |
| 64 | </ul> |
64 | </ul> |
| 65 | |
65 | |
| 66 | <p> |
66 | <p> |
|
|
67 | The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab |
| 67 | So start <c>nano</c> (or your favorite editor) to create your |
68 | file</e>, so start <c>nano</c> (or your favorite editor) to create your |
| 68 | <path>/etc/fstab</path>: |
69 | <path>/etc/fstab</path>: |
| 69 | </p> |
70 | </p> |
| 70 | |
71 | |
| 71 | <pre caption="Opening /etc/fstab"> |
72 | <pre caption="Opening /etc/fstab"> |
| 72 | # <i>nano -w /etc/fstab</i> |
73 | # <i>nano -w /etc/fstab</i> |
| … | |
… | |
| 88 | /dev/hda1 /boot ext2 defaults 1 2 |
89 | /dev/hda1 /boot ext2 defaults 1 2 |
| 89 | </pre> |
90 | </pre> |
| 90 | |
91 | |
| 91 | <p> |
92 | <p> |
| 92 | Some users don't want their <path>/boot</path> partition to be mounted |
93 | Some users don't want their <path>/boot</path> partition to be mounted |
| 93 | automatically. Those people should substitute <c>defaults</c> with |
94 | automatically to improve their system's security. Those people should |
| 94 | <c>noauto</c>. This does mean that you need to manually mount this partition |
95 | substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to |
| 95 | every time you want to use it. |
96 | manually mount this partition every time you want to use it. |
| 96 | </p> |
97 | </p> |
| 97 | |
98 | |
| 98 | <p> |
99 | <p> |
| 99 | Now, to improve performance, most users would want to add the <c>noatime</c> |
100 | Now, to improve performance, most users would want to add the <c>noatime</c> |
| 100 | option as mountoption, which results in a faster system since access times |
101 | option as mountoption, which results in a faster system since access times |
| 101 | aren't registered (you don't need those generally anyway): |
102 | aren't registered (you don't need those generally anyway): |
| 102 | </p> |
103 | </p> |
| 103 | |
104 | |
| 104 | <pre caption="An improved /boot line for /etc/fstab"> |
105 | <pre caption="An improved /boot line for /etc/fstab"> |
| 105 | /dev/hda1 /boot ext2 noauto,noatime 1 2 |
106 | /dev/hda1 /boot ext2 defaults,noatime 1 2 |
| 106 | </pre> |
107 | </pre> |
| 107 | |
108 | |
| 108 | <p> |
109 | <p> |
| 109 | If we continue with this, we would end up with the following three lines (for |
110 | If we continue with this, we would end up with the following three lines (for |
| 110 | <path>/boot</path>, <path>/</path> and the swap partition): |
111 | <path>/boot</path>, <path>/</path> and the swap partition): |
| 111 | </p> |
112 | </p> |
| 112 | |
113 | |
| 113 | <pre caption="Three /etc/fstab lines"> |
114 | <pre caption="Three /etc/fstab lines"> |
| 114 | /dev/hda1 /boot ext2 noauto,noatime 1 2 |
115 | /dev/hda1 /boot ext2 defaults,noatime 1 2 |
| 115 | /dev/hda2 none swap sw 0 0 |
116 | /dev/hda2 none swap sw 0 0 |
| 116 | /dev/hda3 / ext3 noatime 0 1 |
117 | /dev/hda3 / ext3 noatime 0 1 |
| 117 | </pre> |
118 | </pre> |
| 118 | |
119 | |
| 119 | <p> |
120 | <p> |
| … | |
… | |
| 252 | <p> |
253 | <p> |
| 253 | If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> |
254 | If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> |
| 254 | to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. |
255 | to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. |
| 255 | If you need to setup your network manually and you're |
256 | If you need to setup your network manually and you're |
| 256 | not familiar with all the above terms, please read the section on <uri |
257 | not familiar with all the above terms, please read the section on <uri |
| 257 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
258 | link="?part=1&chap=3#network_term">Understanding Network |
| 258 | Terminology</uri> if you haven't done so already. |
259 | Terminology</uri> if you haven't done so already. |
| 259 | </p> |
260 | </p> |
| 260 | |
261 | |
| 261 | <p> |
262 | <p> |
| 262 | So let us give three examples; the first one uses DHCP, the second one a static |
263 | So let us give three examples; the first one uses DHCP, the second one a static |
| … | |
… | |
| 266 | </p> |
267 | </p> |
| 267 | |
268 | |
| 268 | <pre caption="Examples for /etc/conf.d/net"> |
269 | <pre caption="Examples for /etc/conf.d/net"> |
| 269 | <comment>(For DHCP)</comment> |
270 | <comment>(For DHCP)</comment> |
| 270 | iface_eth0="dhcp" |
271 | iface_eth0="dhcp" |
| 271 | <comment>Some network admins require that you use the</comment> |
272 | <comment># Some network admins require that you use the</comment> |
| 272 | <comment>hostname and domainname provided by the DHCP server.</comment> |
273 | <comment># hostname and domainname provided by the DHCP server.</comment> |
| 273 | <comment>In that case, add the following to let dhcpcd use them.</comment> |
274 | <comment># In that case, add the following to let dhcpcd use them.</comment> |
| 274 | <comment>That will override your own hostname and domainname definitions.</comment> |
275 | <comment># That will override your own hostname and domainname definitions.</comment> |
| 275 | dhcpcd_eth0="-HD" |
276 | dhcpcd_eth0="-HD" |
| 276 | <comment>If you intend on using NTP to keep your machine clock synchronized, use</comment> |
277 | <comment># If you intend on using NTP to keep your machine clock synchronized, use</comment> |
| 277 | <comment>the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment> |
278 | <comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment> |
| 278 | dhcpcd_eth0="-N" |
279 | dhcpcd_eth0="-N" |
| 279 | |
280 | |
| 280 | <comment>(For static IP)</comment> |
281 | <comment>(For static IP)</comment> |
| 281 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
282 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
| 282 | gateway="eth0/192.168.0.1" |
283 | gateway="eth0/192.168.0.1" |
| … | |
… | |
| 300 | <subsection> |
301 | <subsection> |
| 301 | <title>Automatically Start Networking at Boot</title> |
302 | <title>Automatically Start Networking at Boot</title> |
| 302 | <body> |
303 | <body> |
| 303 | |
304 | |
| 304 | <p> |
305 | <p> |
| 305 | To have your network interfaces activated at boot, you need to add those to the |
306 | To have your network interfaces activated at boot, you need to add them to the |
| 306 | default runlevel. If you have PCMCIA interfaces you should skip this action as |
307 | default runlevel. If you have PCMCIA interfaces you should skip this action as |
| 307 | the PCMCIA interfaces are started by the PCMCIA init script. |
308 | the PCMCIA interfaces are started by the PCMCIA init script. |
| 308 | </p> |
309 | </p> |
| 309 | |
310 | |
| 310 | <pre caption="Adding net.eth0 to the default runlevel"> |
311 | <pre caption="Adding net.eth0 to the default runlevel"> |
| … | |
… | |
| 349 | 192.168.0.7 tux.homenetwork tux |
350 | 192.168.0.7 tux.homenetwork tux |
| 350 | </pre> |
351 | </pre> |
| 351 | |
352 | |
| 352 | <p> |
353 | <p> |
| 353 | If your system is the only system (or the nameservers handle all name |
354 | If your system is the only system (or the nameservers handle all name |
| 354 | resolution) a single line is sufficient: |
355 | resolution) a single line is sufficient. For instance, if you want to call your |
|
|
356 | system <c>tux.homenetwork</c>: |
| 355 | </p> |
357 | </p> |
| 356 | |
358 | |
| 357 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
359 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 358 | 127.0.0.1 localhost |
360 | 127.0.0.1 tux.homenetwork tux localhost |
| 359 | </pre> |
361 | </pre> |
| 360 | |
362 | |
| 361 | <p> |
363 | <p> |
| 362 | Save and exit the editor to continue. |
364 | Save and exit the editor to continue. |
| 363 | </p> |
365 | </p> |
| … | |
… | |
| 377 | <note> |
379 | <note> |
| 378 | pcmcia-cs is only available for x86, amd64 and ppc platforms. |
380 | pcmcia-cs is only available for x86, amd64 and ppc platforms. |
| 379 | </note> |
381 | </note> |
| 380 | |
382 | |
| 381 | <p> |
383 | <p> |
| 382 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. The |
384 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also |
| 383 | <c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment: |
385 | includes users who will be working with a 2.6 kernel (even though they won't be |
|
|
386 | using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary |
|
|
387 | to avoid installing xorg-x11 at this moment: |
| 384 | </p> |
388 | </p> |
| 385 | |
389 | |
| 386 | <pre caption="Installing pcmcia-cs"> |
390 | <pre caption="Installing pcmcia-cs"> |
| 387 | # <i>USE="-X" emerge pcmcia-cs</i> |
391 | # <i>USE="-X" emerge pcmcia-cs</i> |
| 388 | </pre> |
392 | </pre> |
| … | |
… | |
| 398 | |
402 | |
| 399 | </body> |
403 | </body> |
| 400 | </subsection> |
404 | </subsection> |
| 401 | </section> |
405 | </section> |
| 402 | <section> |
406 | <section> |
|
|
407 | <title>System Information</title> |
|
|
408 | <subsection> |
|
|
409 | <title>Root Password</title> |
|
|
410 | <body> |
|
|
411 | |
|
|
412 | <p> |
|
|
413 | First we set the root password by typing: |
|
|
414 | </p> |
|
|
415 | |
|
|
416 | <pre caption="Setting the root password"> |
|
|
417 | # <i>passwd</i> |
|
|
418 | </pre> |
|
|
419 | |
|
|
420 | <p> |
|
|
421 | If you want root to be able to log on through the serial console, add |
|
|
422 | <c>tts/0</c> to <path>/etc/securetty</path>: |
|
|
423 | </p> |
|
|
424 | |
|
|
425 | <pre caption="Adding tts/0 to /etc/securetty"> |
|
|
426 | # <i>echo "tts/0" >> /etc/securetty</i> |
|
|
427 | </pre> |
|
|
428 | |
|
|
429 | </body> |
|
|
430 | </subsection> |
|
|
431 | <subsection> |
| 403 | <title>System Information</title> |
432 | <title>System Information</title> |
| 404 | <body> |
433 | <body> |
| 405 | |
434 | |
| 406 | <p> |
435 | <p> |
| 407 | Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. |
436 | Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. |
| … | |
… | |
| 430 | to set a mac/ppc keymap in <path>rc.conf</path>. |
459 | to set a mac/ppc keymap in <path>rc.conf</path>. |
| 431 | </p> |
460 | </p> |
| 432 | |
461 | |
| 433 | <p> |
462 | <p> |
| 434 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
463 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
| 435 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
464 | continue with <uri link="?part=1&chap=9">Installing Necessary System |
|
|
465 | Tools</uri>. |
| 436 | </p> |
466 | </p> |
| 437 | |
467 | |
| 438 | </body> |
468 | </body> |
|
|
469 | </subsection> |
| 439 | </section> |
470 | </section> |
| 440 | </sections> |
471 | </sections> |
Parent Directory
| 
Revision Log
| 
Patch