| … | |
… | |
| 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.20 2004/01/19 18:48:52 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.39 2004/08/01 11:20:51 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> |
| … | |
… | |
| 73 | </pre> |
73 | </pre> |
| 74 | |
74 | |
| 75 | <p> |
75 | <p> |
| 76 | Let us 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> |
| 77 | 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 |
| 78 | <path>/boot</path> partition, don't copy it verbatim. |
78 | <path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. |
| 79 | </p> |
79 | </p> |
| 80 | |
80 | |
| 81 | <p> |
81 | <p> |
| 82 | In our default x86 partitioning example <path>/boot</path> is the |
82 | In our default x86 partitioning example <path>/boot</path> is the |
| 83 | <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. |
| 84 | 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: |
| 85 | would write down: |
|
|
| 86 | </p> |
85 | </p> |
| 87 | |
86 | |
| 88 | <pre caption="An example /boot line for /etc/fstab"> |
87 | <pre caption="An example /boot line for /etc/fstab"> |
| 89 | /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. |
| 90 | </pre> |
96 | </p> |
| 91 | |
97 | |
| 92 | <p> |
98 | <p> |
| 93 | 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> |
| 94 | 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 |
| 95 | aren't registered (you don't need those generally anyway): |
101 | aren't registered (you don't need those generally anyway): |
| … | |
… | |
| 133 | <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. |
| 134 | </p> |
140 | </p> |
| 135 | |
141 | |
| 136 | <p> |
142 | <p> |
| 137 | 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 |
| 138 | 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> |
| 139 | too: |
146 | too: |
| 140 | </p> |
147 | </p> |
| 141 | |
148 | |
| 142 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
149 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
| 143 | none /proc/openprom openpromfs defaults 0 0 |
150 | none /proc/openprom openpromfs defaults 0 0 |
| … | |
… | |
| 150 | <pre caption="Adding usbfs filesystem to /etc/fstab"> |
157 | <pre caption="Adding usbfs filesystem to /etc/fstab"> |
| 151 | none /proc/bus/usb usbfs defaults 0 0 |
158 | none /proc/bus/usb usbfs defaults 0 0 |
| 152 | </pre> |
159 | </pre> |
| 153 | |
160 | |
| 154 | <p> |
161 | <p> |
| 155 | Reread your <path>/etc/fstab</path>, save and quit to continue. |
162 | Double-check your <path>/etc/fstab</path>, save and quit to continue. |
| 156 | </p> |
163 | </p> |
| 157 | |
164 | |
| 158 | </body> |
165 | </body> |
| 159 | </subsection> |
166 | </subsection> |
| 160 | </section> |
167 | </section> |
| … | |
… | |
| 163 | <subsection> |
170 | <subsection> |
| 164 | <title>Hostname, Domainname etc.</title> |
171 | <title>Hostname, Domainname etc.</title> |
| 165 | <body> |
172 | <body> |
| 166 | |
173 | |
| 167 | <p> |
174 | <p> |
| 168 | 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 |
| 169 | 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 |
| 170 | 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 |
| 171 | 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 |
| 172 | <c>tux</c> and domain <c>homenetwork</c>. |
179 | <c>tux</c> and domain <c>homenetwork</c>. |
| 173 | </p> |
180 | </p> |
| 174 | |
181 | |
| 175 | <p> |
182 | <p> |
| 176 | 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: |
| … | |
… | |
| 242 | 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>" |
| 243 | </pre> |
250 | </pre> |
| 244 | |
251 | |
| 245 | <p> |
252 | <p> |
| 246 | 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>. |
| 247 | 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 |
| 248 | 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 |
| 249 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
257 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
| 250 | Terminology</uri> if you haven't done so already. |
258 | Terminology</uri> if you haven't done so already. |
| 251 | </p> |
259 | </p> |
| 252 | |
260 | |
| 253 | <p> |
261 | <p> |
| 254 | So let us 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 |
| 255 | (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 |
| 256 | 192.168.0.1: |
264 | gateway 192.168.0.1 while the third one just activates the interface for |
|
|
265 | rp-pppoe usage: |
| 257 | </p> |
266 | </p> |
| 258 | |
267 | |
| 259 | <pre caption="Examples for /etc/conf.d/net"> |
268 | <pre caption="Examples for /etc/conf.d/net"> |
| 260 | <comment>(For DHCP:)</comment> |
269 | <comment>(For DHCP)</comment> |
| 261 | 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" |
| 262 | |
279 | |
| 263 | <comment>(For static IP:)</comment> |
280 | <comment>(For static IP)</comment> |
| 264 | 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" |
| 265 | gateway="eth0/192.168.0.1" |
282 | gateway="eth0/192.168.0.1" |
|
|
283 | |
|
|
284 | <comment>(For rp-pppoe)</comment> |
|
|
285 | iface_eth0="up" |
| 266 | </pre> |
286 | </pre> |
| 267 | |
287 | |
| 268 | <p> |
288 | <p> |
| 269 | 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, |
| 270 | 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 |
| … | |
… | |
| 322 | # <i>nano -w /etc/hosts</i> |
342 | # <i>nano -w /etc/hosts</i> |
| 323 | </pre> |
343 | </pre> |
| 324 | |
344 | |
| 325 | <pre caption="Filling in the networking information"> |
345 | <pre caption="Filling in the networking information"> |
| 326 | 127.0.0.1 localhost |
346 | 127.0.0.1 localhost |
| 327 | 192.168.0.5 jenny |
347 | 192.168.0.5 jenny.homenetwork jenny |
| 328 | 192.168.0.6 benny |
348 | 192.168.0.6 benny.homenetwork benny |
| 329 | 192.168.0.7 tux |
349 | 192.168.0.7 tux.homenetwork tux |
| 330 | </pre> |
350 | </pre> |
| 331 | |
351 | |
| 332 | <p> |
352 | <p> |
| 333 | 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 |
| 334 | resolution) a single line is sufficient: |
354 | resolution) a single line is sufficient. For instance, if you want to call your |
|
|
355 | system <c>tux.homenetwork</c>: |
| 335 | </p> |
356 | </p> |
| 336 | |
357 | |
| 337 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
358 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 338 | 127.0.0.1 localhost tux |
359 | 127.0.0.1 tux.homenetwork tux localhost |
| 339 | </pre> |
360 | </pre> |
| 340 | |
361 | |
| 341 | <p> |
362 | <p> |
| 342 | Save and exit the editor to continue. |
363 | Save and exit the editor to continue. |
| 343 | </p> |
364 | </p> |
| … | |
… | |
| 352 | </subsection> |
373 | </subsection> |
| 353 | <subsection> |
374 | <subsection> |
| 354 | <title>Optional: Get PCMCIA Working</title> |
375 | <title>Optional: Get PCMCIA Working</title> |
| 355 | <body> |
376 | <body> |
| 356 | |
377 | |
|
|
378 | <note> |
|
|
379 | pcmcia-cs is only available for x86, amd64 and ppc platforms. |
|
|
380 | </note> |
|
|
381 | |
| 357 | <p> |
382 | <p> |
| 358 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
383 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. The |
|
|
384 | <c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment: |
| 359 | </p> |
385 | </p> |
| 360 | |
386 | |
| 361 | <pre caption="Installing pcmcia-cs"> |
387 | <pre caption="Installing pcmcia-cs"> |
| 362 | # <i>emerge --usepkg pcmcia-cs</i> |
388 | # <i>USE="-X" emerge pcmcia-cs</i> |
| 363 | </pre> |
389 | </pre> |
| 364 | |
390 | |
| 365 | <p> |
391 | <p> |
| 366 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
392 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 367 | runlevel: |
393 | runlevel: |
| … | |
… | |
| 393 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
419 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
| 394 | your keyboard. |
420 | your keyboard. |
| 395 | </p> |
421 | </p> |
| 396 | |
422 | |
| 397 | <note> |
423 | <note> |
| 398 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
424 | Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to |
| 399 | keymap (such as "us") instead of "sunkeymap". |
425 | select an i386 keymap (such as "us") instead of "sunkeymap". |
| 400 | </note> |
426 | </note> |
|
|
427 | |
|
|
428 | <p> |
|
|
429 | <b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use |
|
|
430 | ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have |
|
|
431 | to set a mac/ppc keymap in <path>rc.conf</path>. |
|
|
432 | </p> |
| 401 | |
433 | |
| 402 | <p> |
434 | <p> |
| 403 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
435 | 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>. |
436 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
| 405 | </p> |
437 | </p> |
Parent Directory
| 
Revision Log
| 
Patch