| … | |
… | |
| 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.29 2004/03/12 11:56:15 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 PPC), 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. It shouldn't |
| … | |
… | |
| 242 | 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>" |
| 243 | </pre> |
243 | </pre> |
| 244 | |
244 | |
| 245 | <p> |
245 | <p> |
| 246 | 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>. |
| 247 | 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 |
| 248 | 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 |
| 249 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
250 | link="?part=1&chap=3#doc_chap4_sect3">Understanding Network |
| 250 | Terminology</uri> if you haven't done so already. |
251 | Terminology</uri> if you haven't done so already. |
| 251 | </p> |
252 | </p> |
| 252 | |
253 | |
| 253 | <p> |
254 | <p> |
| 254 | So let us 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 |
| 255 | (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 |
| 256 | 192.168.0.1: |
257 | gateway 192.168.0.1 while the third one just activates the interface for |
|
|
258 | rp-pppoe usage: |
| 257 | </p> |
259 | </p> |
| 258 | |
260 | |
| 259 | <pre caption="Examples for /etc/conf.d/net"> |
261 | <pre caption="Examples for /etc/conf.d/net"> |
| 260 | <comment>(For DHCP:)</comment> |
262 | <comment>(For DHCP)</comment> |
| 261 | iface_eth0="dhcp" |
263 | iface_eth0="dhcp" |
| 262 | |
264 | |
| 263 | <comment>(For static IP:)</comment> |
265 | <comment>(For static IP)</comment> |
| 264 | 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" |
| 265 | gateway="eth0/192.168.0.1" |
267 | gateway="eth0/192.168.0.1" |
|
|
268 | |
|
|
269 | <comment>(For rp-pppoe)</comment> |
|
|
270 | iface_eth0="up" |
| 266 | </pre> |
271 | </pre> |
| 267 | |
272 | |
| 268 | <p> |
273 | <p> |
| 269 | 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, |
| 270 | 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 |
| … | |
… | |
| 322 | # <i>nano -w /etc/hosts</i> |
327 | # <i>nano -w /etc/hosts</i> |
| 323 | </pre> |
328 | </pre> |
| 324 | |
329 | |
| 325 | <pre caption="Filling in the networking information"> |
330 | <pre caption="Filling in the networking information"> |
| 326 | 127.0.0.1 localhost |
331 | 127.0.0.1 localhost |
| 327 | 192.168.0.5 jenny |
332 | 192.168.0.5 jenny.homenetwork jenny |
| 328 | 192.168.0.6 benny |
333 | 192.168.0.6 benny.homenetwork benny |
| 329 | 192.168.0.7 tux |
334 | 192.168.0.7 tux.homenetwork tux |
| 330 | </pre> |
335 | </pre> |
| 331 | |
336 | |
| 332 | <p> |
337 | <p> |
| 333 | 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 |
| 334 | resolution) a single line is sufficient: |
339 | resolution) a single line is sufficient: |
| 335 | </p> |
340 | </p> |
| 336 | |
341 | |
| 337 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
342 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 338 | 127.0.0.1 localhost tux |
343 | 127.0.0.1 localhost |
| 339 | </pre> |
344 | </pre> |
| 340 | |
345 | |
| 341 | <p> |
346 | <p> |
| 342 | Save and exit the editor to continue. |
347 | Save and exit the editor to continue. |
| 343 | </p> |
348 | </p> |
| … | |
… | |
| 357 | <p> |
362 | <p> |
| 358 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
363 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
| 359 | </p> |
364 | </p> |
| 360 | |
365 | |
| 361 | <pre caption="Installing pcmcia-cs"> |
366 | <pre caption="Installing pcmcia-cs"> |
| 362 | # <i>emerge --usepkg pcmcia-cs</i> |
367 | # <i>emerge pcmcia-cs</i> |
| 363 | </pre> |
368 | </pre> |
| 364 | |
369 | |
| 365 | <p> |
370 | <p> |
| 366 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
371 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 367 | runlevel: |
372 | runlevel: |
| … | |
… | |
| 398 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
403 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
| 399 | keymap (such as "us") instead of "sunkeymap". |
404 | keymap (such as "us") instead of "sunkeymap". |
| 400 | </note> |
405 | </note> |
| 401 | |
406 | |
| 402 | <p> |
407 | <p> |
|
|
408 | PPC uses x86 keymaps on most systems. Users who want to be able to use ADB |
|
|
409 | keymaps on boot have to enable ADB keycode sendings in their kernel and have to |
|
|
410 | set a mac/ppc keymap in <path>rc.conf</path>. |
|
|
411 | </p> |
|
|
412 | |
|
|
413 | <p> |
| 403 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
414 | 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>. |
415 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
| 405 | </p> |
416 | </p> |
| 406 | |
417 | |
| 407 | </body> |
418 | </body> |
Parent Directory
| 
Revision Log
| 
Patch