|
|
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 | |
| 4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.8 2003/11/15 13:53:33 swift Exp $ --> |
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 $ --> |
| 5 | |
8 | |
| 6 | <sections> |
9 | <sections> |
| 7 | <section> |
|
|
| 8 | <title>Timezone</title> |
|
|
| 9 | <body> |
|
|
| 10 | |
|
|
| 11 | <p> |
|
|
| 12 | You now need to select your timezone so that your system knows where it is |
|
|
| 13 | located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a |
|
|
| 14 | symlink to <path>/etc/localtime</path> using <c>ln</c>: |
|
|
| 15 | </p> |
|
|
| 16 | |
|
|
| 17 | <pre caption="Setting the timezone information"> |
|
|
| 18 | # <i>ls /usr/share/zoneinfo</i> |
|
|
| 19 | <comment>(Suppose you want to use GTM:)</comment> |
|
|
| 20 | # <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i> |
|
|
| 21 | </pre> |
|
|
| 22 | |
|
|
| 23 | </body> |
|
|
| 24 | </section> |
|
|
| 25 | <section> |
10 | <section> |
| 26 | <title>Filesystem Information</title> |
11 | <title>Filesystem Information</title> |
| 27 | <subsection> |
12 | <subsection> |
| 28 | <title>What is fstab?</title> |
13 | <title>What is fstab?</title> |
| 29 | <body> |
14 | <body> |
| … | |
… | |
| 41 | <subsection> |
26 | <subsection> |
| 42 | <title>Creating /etc/fstab</title> |
27 | <title>Creating /etc/fstab</title> |
| 43 | <body> |
28 | <body> |
| 44 | |
29 | |
| 45 | <p> |
30 | <p> |
| 46 | <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 |
| 47 | 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 |
| 48 | its own meaning: |
33 | its own meaning: |
| 49 | </p> |
34 | </p> |
| 50 | |
35 | |
| 51 | <ul> |
36 | <ul> |
| 52 | <li> |
37 | <li> |
| … | |
… | |
| 62 | </li> |
47 | </li> |
| 63 | <li> |
48 | <li> |
| 64 | 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 |
| 65 | 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, |
| 66 | 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 |
| 67 | listing. Multiple mountoptions are comma-seperated. |
52 | listing. Multiple mountoptions are comma-separated. |
| 68 | </li> |
53 | </li> |
| 69 | <li> |
54 | <li> |
| 70 | 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 |
| 71 | 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). |
| 72 | </li> |
57 | </li> |
| 73 | <li> |
58 | <li> |
| 74 | 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 |
| 75 | 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. |
| 76 | 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> |
| 77 | a filesystem check isn't necessary). |
62 | (or <c>0</c> in case a filesystem check isn't necessary). |
| 78 | </li> |
63 | </li> |
| 79 | </ul> |
64 | </ul> |
| 80 | |
65 | |
| 81 | <p> |
66 | <p> |
| 82 | 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 |
| … | |
… | |
| 86 | <pre caption="Opening /etc/fstab"> |
71 | <pre caption="Opening /etc/fstab"> |
| 87 | # <i>nano -w /etc/fstab</i> |
72 | # <i>nano -w /etc/fstab</i> |
| 88 | </pre> |
73 | </pre> |
| 89 | |
74 | |
| 90 | <p> |
75 | <p> |
| 91 | 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> |
| 92 | 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 |
| 93 | <path>/boot</path> partition, don't copy it verbatim. |
78 | <path>/boot</path> partition, don't copy it verbatim. |
| 94 | </p> |
79 | </p> |
| 95 | |
80 | |
| 96 | <p> |
81 | <p> |
| … | |
… | |
| 210 | |
195 | |
| 211 | <pre caption="Setting the NIS domainname"> |
196 | <pre caption="Setting the NIS domainname"> |
| 212 | # <i>echo nis.homenetwork > /etc/nisdomainname</i> |
197 | # <i>echo nis.homenetwork > /etc/nisdomainname</i> |
| 213 | </pre> |
198 | </pre> |
| 214 | |
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 | |
| 215 | </body> |
208 | </body> |
| 216 | </subsection> |
209 | </subsection> |
| 217 | <subsection> |
210 | <subsection> |
| 218 | <title>Configuring your Network</title> |
211 | <title>Configuring your Network</title> |
| 219 | <body> |
212 | <body> |
| … | |
… | |
| 256 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
249 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
| 257 | Terminology</uri> if you haven't done so already. |
250 | Terminology</uri> if you haven't done so already. |
| 258 | </p> |
251 | </p> |
| 259 | |
252 | |
| 260 | <p> |
253 | <p> |
| 261 | So lets give two examples; the first one uses DHCP, the second one a static IP |
254 | So let us give two examples; the first one uses DHCP, the second one a static IP |
| 262 | (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 |
| 263 | 192.168.0.1: |
256 | 192.168.0.1: |
| 264 | </p> |
257 | </p> |
| 265 | |
258 | |
| 266 | <pre caption="Examples for /etc/conf.d/net"> |
259 | <pre caption="Examples for /etc/conf.d/net"> |
| … | |
… | |
| 319 | <p> |
312 | <p> |
| 320 | You now need to inform Linux about your network. This is defined in |
313 | You now need to inform Linux about your network. This is defined in |
| 321 | <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 |
| 322 | for hosts that aren't resolved by your nameserver. For instance, if your |
315 | for hosts that aren't resolved by your nameserver. For instance, if your |
| 323 | internal network consists of three PCs called <c>jenny</c> (192.168.0.5), |
316 | internal network consists of three PCs called <c>jenny</c> (192.168.0.5), |
| 324 | <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 |
| 325 | open <path>/etc/hosts</path> and fill in the values: |
318 | open <path>/etc/hosts</path> and fill in the values: |
| 326 | </p> |
319 | </p> |
| 327 | |
320 | |
| 328 | <pre caption="Opening /etc/hosts"> |
321 | <pre caption="Opening /etc/hosts"> |
| 329 | # <i>nano -w /etc/hosts</i> |
322 | # <i>nano -w /etc/hosts</i> |
| 330 | </pre> |
323 | </pre> |
| 331 | |
324 | |
| 332 | <pre caption="Filling in the networking information"> |
325 | <pre caption="Filling in the networking information"> |
| 333 | 127.0.0.1 tux.homenetwork localhost |
326 | 127.0.0.1 localhost |
| 334 | 192.168.0.5 jenny |
327 | 192.168.0.5 jenny |
| 335 | 192.168.0.56 benny |
328 | 192.168.0.6 benny |
|
|
329 | 192.168.0.7 tux |
| 336 | </pre> |
330 | </pre> |
| 337 | |
331 | |
| 338 | <p> |
332 | <p> |
| 339 | If your system is the only system (or the nameservers handle all name |
333 | If your system is the only system (or the nameservers handle all name |
| 340 | resolution) a single line is sufficient: |
334 | resolution) a single line is sufficient: |
| … | |
… | |
| 348 | Save and exit the editor to continue. |
342 | Save and exit the editor to continue. |
| 349 | </p> |
343 | </p> |
| 350 | |
344 | |
| 351 | <p> |
345 | <p> |
| 352 | If you don't have PCMCIA, you can now continue with <uri |
346 | If you don't have PCMCIA, you can now continue with <uri |
| 353 | link="#doc_chap4">System Information</uri>. PCMCIA-users should read the |
347 | link="#doc_chap3">System Information</uri>. PCMCIA-users should read the |
| 354 | following topic on PCMCIA. |
348 | following topic on PCMCIA. |
| 355 | </p> |
349 | </p> |
| 356 | |
350 | |
| 357 | </body> |
351 | </body> |
| 358 | </subsection> |
352 | </subsection> |
| … | |
… | |
| 363 | <p> |
357 | <p> |
| 364 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
358 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
| 365 | </p> |
359 | </p> |
| 366 | |
360 | |
| 367 | <pre caption="Installing pcmcia-cs"> |
361 | <pre caption="Installing pcmcia-cs"> |
| 368 | # <i>emerge -k pcmcia-cs</i> |
362 | # <i>emerge --usepkg pcmcia-cs</i> |
| 369 | </pre> |
363 | </pre> |
| 370 | |
364 | |
| 371 | <p> |
365 | <p> |
| 372 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> |
366 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 373 | runlevel: |
367 | runlevel: |
| 374 | </p> |
368 | </p> |
| 375 | |
369 | |
| 376 | <pre caption="Adding pcmcia to the default runlevel"> |
370 | <pre caption="Adding pcmcia to the default runlevel"> |
| 377 | # <i>rc-update add pcmcia boot</i> |
371 | # <i>rc-update add pcmcia default</i> |
| 378 | </pre> |
372 | </pre> |
| 379 | |
373 | |
| 380 | </body> |
374 | </body> |
| 381 | </subsection> |
375 | </subsection> |
| 382 | </section> |
376 | </section> |
| … | |
… | |
| 393 | # <i>nano -w /etc/rc.conf</i> |
387 | # <i>nano -w /etc/rc.conf</i> |
| 394 | </pre> |
388 | </pre> |
| 395 | |
389 | |
| 396 | <p> |
390 | <p> |
| 397 | As you can see, this file is well commented to help you set up the necessary |
391 | As you can see, this file is well commented to help you set up the necessary |
| 398 | configuration variables. When you're finished configuring |
392 | configuration variables. Take special care with the <c>KEYMAP</c> setting: if |
| 399 | <path>/etc/rc.conf</path>, save and exit to continue. |
393 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
|
|
394 | your keyboard. |
|
|
395 | </p> |
|
|
396 | |
|
|
397 | <note> |
|
|
398 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
|
|
399 | keymap (such as "us") instead of "sunkeymap". |
|
|
400 | </note> |
|
|
401 | |
|
|
402 | <p> |
|
|
403 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
|
|
404 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
| 400 | </p> |
405 | </p> |
| 401 | |
406 | |
| 402 | </body> |
407 | </body> |
| 403 | </section> |
408 | </section> |
| 404 | </sections> |
409 | </sections> |
Parent Directory
| 
Revision Log
| 
Patch