|
|
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.37 2004/07/26 09:04:42 dertobi123 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 -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 |
| 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 <b>PPC</b>), 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. |
| 97 | be mounted automatically (<c>noauto</c>) but does need to be checked. So we |
84 | It needs to be checked during boot, so we would write down: |
| 98 | would write down: |
|
|
| 99 | </p> |
85 | </p> |
| 100 | |
86 | |
| 101 | <pre caption="An example /boot line for /etc/fstab"> |
87 | <pre caption="An example /boot line for /etc/fstab"> |
| 102 | /dev/hda1 /boot ext2 noauto 1 2 |
88 | /dev/hda1 /boot ext2 defaults 1 2 |
|
|
89 | </pre> |
|
|
90 | |
|
|
91 | <p> |
|
|
92 | Some users don't want their <path>/boot</path> partition to be mounted |
|
|
93 | automatically. Those people should substitute <c>defaults</c> with |
|
|
94 | <c>noauto</c>. This does mean that you need to manually mount this partition |
|
|
95 | every time you want to use it. |
| 103 | </pre> |
96 | </p> |
| 104 | |
97 | |
| 105 | <p> |
98 | <p> |
| 106 | Now, to improve performance, most users would want to add the <c>noatime</c> |
99 | Now, to improve performance, most users would want to add the <c>noatime</c> |
| 107 | option as mountoption, which results in a faster system since access times |
100 | option as mountoption, which results in a faster system since access times |
| 108 | aren't registered (you don't need those generally anyway): |
101 | aren't registered (you don't need those generally anyway): |
| … | |
… | |
| 146 | <c>user</c> makes it possible for non-root users to mount the CD. |
139 | <c>user</c> makes it possible for non-root users to mount the CD. |
| 147 | </p> |
140 | </p> |
| 148 | |
141 | |
| 149 | <p> |
142 | <p> |
| 150 | Now use the above example to create your <path>/etc/fstab</path>. If you are a |
143 | Now use the above example to create your <path>/etc/fstab</path>. If you are a |
| 151 | SPARC-user, you should add the following line to your <path>/etc/fstab</path> |
144 | <b>SPARC</b>-user, you should add the following line to your |
|
|
145 | <path>/etc/fstab</path> |
| 152 | too: |
146 | too: |
| 153 | </p> |
147 | </p> |
| 154 | |
148 | |
| 155 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
149 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
| 156 | none /proc/openprom openpromfs defaults 0 0 |
150 | none /proc/openprom openpromfs defaults 0 0 |
| … | |
… | |
| 163 | <pre caption="Adding usbfs filesystem to /etc/fstab"> |
157 | <pre caption="Adding usbfs filesystem to /etc/fstab"> |
| 164 | none /proc/bus/usb usbfs defaults 0 0 |
158 | none /proc/bus/usb usbfs defaults 0 0 |
| 165 | </pre> |
159 | </pre> |
| 166 | |
160 | |
| 167 | <p> |
161 | <p> |
| 168 | Reread your <path>/etc/fstab</path>, save and quit to continue. |
162 | Double-check your <path>/etc/fstab</path>, save and quit to continue. |
| 169 | </p> |
163 | </p> |
| 170 | |
164 | |
| 171 | </body> |
165 | </body> |
| 172 | </subsection> |
166 | </subsection> |
| 173 | </section> |
167 | </section> |
| … | |
… | |
| 176 | <subsection> |
170 | <subsection> |
| 177 | <title>Hostname, Domainname etc.</title> |
171 | <title>Hostname, Domainname etc.</title> |
| 178 | <body> |
172 | <body> |
| 179 | |
173 | |
| 180 | <p> |
174 | <p> |
| 181 | One of the choices the user has to make is name his PC. This seems to be quite |
175 | One of the choices the user has to make is name his/her PC. This seems to be |
| 182 | easy, but <e>lots</e> of users are having difficulties finding the appropriate |
176 | quite easy, but <e>lots</e> of users are having difficulties finding the |
| 183 | name for their Linux-pc. To speed things up, know that any name you choose can |
177 | appropriate name for their Linux-pc. To speed things up, know that any name you |
| 184 | be changed afterwards. For all we care, you can just call your system |
178 | choose can be changed afterwards. For all we care, you can just call your system |
| 185 | <c>tux</c> and domain <c>homenetwork</c>. |
179 | <c>tux</c> and domain <c>homenetwork</c>. |
| 186 | </p> |
180 | </p> |
| 187 | |
181 | |
| 188 | <p> |
182 | <p> |
| 189 | We use these values in the next examples. First we set the hostname: |
183 | We use these values in the next examples. First we set the hostname: |
| … | |
… | |
| 206 | one), you need to define that one too: |
200 | one), you need to define that one too: |
| 207 | </p> |
201 | </p> |
| 208 | |
202 | |
| 209 | <pre caption="Setting the NIS domainname"> |
203 | <pre caption="Setting the NIS domainname"> |
| 210 | # <i>echo nis.homenetwork > /etc/nisdomainname</i> |
204 | # <i>echo nis.homenetwork > /etc/nisdomainname</i> |
|
|
205 | </pre> |
|
|
206 | |
|
|
207 | <p> |
|
|
208 | Now add the <c>domainname</c> script to the default runlevel: |
|
|
209 | </p> |
|
|
210 | |
|
|
211 | <pre caption="Adding domainname to the default runlevel"> |
|
|
212 | # <i>rc-update add domainname default</i> |
| 211 | </pre> |
213 | </pre> |
| 212 | |
214 | |
| 213 | </body> |
215 | </body> |
| 214 | </subsection> |
216 | </subsection> |
| 215 | <subsection> |
217 | <subsection> |
| … | |
… | |
| 247 | iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>" |
249 | iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>" |
| 248 | </pre> |
250 | </pre> |
| 249 | |
251 | |
| 250 | <p> |
252 | <p> |
| 251 | If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> |
253 | 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>. |
| 252 | to <c>dhcp</c>. However, if you need to setup your network manually and you're |
255 | If you need to setup your network manually and you're |
| 253 | not familiar with all the above terms, please read the section on <uri |
256 | not familiar with all the above terms, please read the section on <uri |
| 254 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
257 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
| 255 | Terminology</uri> if you haven't done so already. |
258 | Terminology</uri> if you haven't done so already. |
| 256 | </p> |
259 | </p> |
| 257 | |
260 | |
| 258 | <p> |
261 | <p> |
| 259 | So lets give two examples; the first one uses DHCP, the second one a static IP |
262 | So 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 |
263 | IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and |
| 261 | 192.168.0.1: |
264 | gateway 192.168.0.1 while the third one just activates the interface for |
|
|
265 | rp-pppoe usage: |
| 262 | </p> |
266 | </p> |
| 263 | |
267 | |
| 264 | <pre caption="Examples for /etc/conf.d/net"> |
268 | <pre caption="Examples for /etc/conf.d/net"> |
| 265 | <comment>(For DHCP:)</comment> |
269 | <comment>(For DHCP)</comment> |
| 266 | iface_eth0="dhcp" |
270 | iface_eth0="dhcp" |
|
|
271 | <comment>Some network admins require that you use the</comment> |
|
|
272 | <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>That will override your own hostname and domainname definitions.</comment> |
|
|
275 | dhcpcd_eth0="-HD" |
|
|
276 | <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 | dhcpcd_eth0="-N" |
| 267 | |
279 | |
| 268 | <comment>(For static IP:)</comment> |
280 | <comment>(For static IP)</comment> |
| 269 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
281 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
| 270 | gateway="eth0/192.168.0.1" |
282 | gateway="eth0/192.168.0.1" |
|
|
283 | |
|
|
284 | <comment>(For rp-pppoe)</comment> |
|
|
285 | iface_eth0="up" |
| 271 | </pre> |
286 | </pre> |
| 272 | |
287 | |
| 273 | <p> |
288 | <p> |
| 274 | If you have several network interfaces, create extra <c>iface_eth</c> variables, |
289 | If you have several network interfaces, create extra <c>iface_eth</c> variables, |
| 275 | like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable |
290 | like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable |
| … | |
… | |
| 317 | <p> |
332 | <p> |
| 318 | You now need to inform Linux about your network. This is defined in |
333 | You 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 |
334 | <path>/etc/hosts</path> and helps in resolving hostnames to IP addresses |
| 320 | for hosts that aren't resolved by your nameserver. For instance, if your |
335 | for hosts that aren't resolved by your nameserver. For instance, if your |
| 321 | internal network consists of three PCs called <c>jenny</c> (192.168.0.5), |
336 | internal 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 |
337 | <c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would |
| 323 | open <path>/etc/hosts</path> and fill in the values: |
338 | open <path>/etc/hosts</path> and fill in the values: |
| 324 | </p> |
339 | </p> |
| 325 | |
340 | |
| 326 | <pre caption="Opening /etc/hosts"> |
341 | <pre caption="Opening /etc/hosts"> |
| 327 | # <i>nano -w /etc/hosts</i> |
342 | # <i>nano -w /etc/hosts</i> |
| 328 | </pre> |
343 | </pre> |
| 329 | |
344 | |
| 330 | <pre caption="Filling in the networking information"> |
345 | <pre caption="Filling in the networking information"> |
| 331 | 127.0.0.1 tux.homenetwork localhost |
346 | 127.0.0.1 localhost |
| 332 | 192.168.0.5 jenny |
347 | 192.168.0.5 jenny.homenetwork jenny |
| 333 | 192.168.0.56 benny |
348 | 192.168.0.6 benny.homenetwork benny |
|
|
349 | 192.168.0.7 tux.homenetwork tux |
| 334 | </pre> |
350 | </pre> |
| 335 | |
351 | |
| 336 | <p> |
352 | <p> |
| 337 | If your system is the only system (or the nameservers handle all name |
353 | If your system is the only system (or the nameservers handle all name |
| 338 | resolution) a single line is sufficient: |
354 | resolution) a single line is sufficient: |
| 339 | </p> |
355 | </p> |
| 340 | |
356 | |
| 341 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
357 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 342 | 127.0.0.1 localhost tux |
358 | 127.0.0.1 localhost |
| 343 | </pre> |
359 | </pre> |
| 344 | |
360 | |
| 345 | <p> |
361 | <p> |
| 346 | Save and exit the editor to continue. |
362 | Save and exit the editor to continue. |
| 347 | </p> |
363 | </p> |
| 348 | |
364 | |
| 349 | <p> |
365 | <p> |
| 350 | If you don't have PCMCIA, you can now continue with <uri |
366 | If you don't have PCMCIA, you can now continue with <uri |
| 351 | link="#doc_chap4">System Information</uri>. PCMCIA-users should read the |
367 | link="#doc_chap3">System Information</uri>. PCMCIA-users should read the |
| 352 | following topic on PCMCIA. |
368 | following topic on PCMCIA. |
| 353 | </p> |
369 | </p> |
| 354 | |
370 | |
| 355 | </body> |
371 | </body> |
| 356 | </subsection> |
372 | </subsection> |
| 357 | <subsection> |
373 | <subsection> |
| 358 | <title>Optional: Get PCMCIA Working</title> |
374 | <title>Optional: Get PCMCIA Working</title> |
| 359 | <body> |
375 | <body> |
| 360 | |
376 | |
|
|
377 | <note> |
|
|
378 | pcmcia-cs is only available for x86, amd64 and ppc platforms. |
|
|
379 | </note> |
|
|
380 | |
| 361 | <p> |
381 | <p> |
| 362 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
382 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. The |
|
|
383 | <c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment: |
| 363 | </p> |
384 | </p> |
| 364 | |
385 | |
| 365 | <pre caption="Installing pcmcia-cs"> |
386 | <pre caption="Installing pcmcia-cs"> |
| 366 | # <i>emerge -k pcmcia-cs</i> |
387 | # <i>USE="-X" emerge pcmcia-cs</i> |
| 367 | </pre> |
388 | </pre> |
| 368 | |
389 | |
| 369 | <p> |
390 | <p> |
| 370 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> |
391 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 371 | runlevel: |
392 | runlevel: |
| 372 | </p> |
393 | </p> |
| 373 | |
394 | |
| 374 | <pre caption="Adding pcmcia to the default runlevel"> |
395 | <pre caption="Adding pcmcia to the default runlevel"> |
| 375 | # <i>rc-update add pcmcia boot</i> |
396 | # <i>rc-update add pcmcia default</i> |
| 376 | </pre> |
397 | </pre> |
| 377 | |
398 | |
| 378 | </body> |
399 | </body> |
| 379 | </subsection> |
400 | </subsection> |
| 380 | </section> |
401 | </section> |
| … | |
… | |
| 391 | # <i>nano -w /etc/rc.conf</i> |
412 | # <i>nano -w /etc/rc.conf</i> |
| 392 | </pre> |
413 | </pre> |
| 393 | |
414 | |
| 394 | <p> |
415 | <p> |
| 395 | As you can see, this file is well commented to help you set up the necessary |
416 | As you can see, this file is well commented to help you set up the necessary |
| 396 | configuration variables. When you're finished configuring |
417 | configuration variables. Take special care with the <c>KEYMAP</c> setting: if |
| 397 | <path>/etc/rc.conf</path>, save and exit to continue. |
418 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
|
|
419 | your keyboard. |
|
|
420 | </p> |
|
|
421 | |
|
|
422 | <note> |
|
|
423 | Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to |
|
|
424 | select an i386 keymap (such as "us") instead of "sunkeymap". |
|
|
425 | </note> |
|
|
426 | |
|
|
427 | <p> |
|
|
428 | <b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use |
|
|
429 | ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have |
|
|
430 | to set a mac/ppc keymap in <path>rc.conf</path>. |
|
|
431 | </p> |
|
|
432 | |
|
|
433 | <p> |
|
|
434 | 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>. |
| 398 | </p> |
436 | </p> |
| 399 | |
437 | |
| 400 | </body> |
438 | </body> |
| 401 | </section> |
439 | </section> |
| 402 | </sections> |
440 | </sections> |
Parent Directory
| 
Revision Log
| 
Patch