| … | |
… | |
| 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.23 2004/02/08 09:54:39 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.34 2004/06/03 20:58:34 neysx 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. It shouldn't |
| … | |
… | |
| 133 | <c>user</c> makes it possible for non-root users to mount the CD. |
133 | <c>user</c> makes it possible for non-root users to mount the CD. |
| 134 | </p> |
134 | </p> |
| 135 | |
135 | |
| 136 | <p> |
136 | <p> |
| 137 | Now use the above example to create your <path>/etc/fstab</path>. If you are a |
137 | 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> |
138 | <b>SPARC</b>-user, you should add the following line to your |
|
|
139 | <path>/etc/fstab</path> |
| 139 | too: |
140 | too: |
| 140 | </p> |
141 | </p> |
| 141 | |
142 | |
| 142 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
143 | <pre caption="Adding openprom filesystem to /etc/fstab"> |
| 143 | none /proc/openprom openpromfs defaults 0 0 |
144 | none /proc/openprom openpromfs defaults 0 0 |
| … | |
… | |
| 150 | <pre caption="Adding usbfs filesystem to /etc/fstab"> |
151 | <pre caption="Adding usbfs filesystem to /etc/fstab"> |
| 151 | none /proc/bus/usb usbfs defaults 0 0 |
152 | none /proc/bus/usb usbfs defaults 0 0 |
| 152 | </pre> |
153 | </pre> |
| 153 | |
154 | |
| 154 | <p> |
155 | <p> |
| 155 | Reread your <path>/etc/fstab</path>, save and quit to continue. |
156 | Double-check your <path>/etc/fstab</path>, save and quit to continue. |
| 156 | </p> |
157 | </p> |
| 157 | |
158 | |
| 158 | </body> |
159 | </body> |
| 159 | </subsection> |
160 | </subsection> |
| 160 | </section> |
161 | </section> |
| … | |
… | |
| 163 | <subsection> |
164 | <subsection> |
| 164 | <title>Hostname, Domainname etc.</title> |
165 | <title>Hostname, Domainname etc.</title> |
| 165 | <body> |
166 | <body> |
| 166 | |
167 | |
| 167 | <p> |
168 | <p> |
| 168 | One of the choices the user has to make is name his PC. This seems to be quite |
169 | 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 |
170 | 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 |
171 | 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 |
172 | choose can be changed afterwards. For all we care, you can just call your system |
| 172 | <c>tux</c> and domain <c>homenetwork</c>. |
173 | <c>tux</c> and domain <c>homenetwork</c>. |
| 173 | </p> |
174 | </p> |
| 174 | |
175 | |
| 175 | <p> |
176 | <p> |
| 176 | We use these values in the next examples. First we set the hostname: |
177 | We use these values in the next examples. First we set the hostname: |
| … | |
… | |
| 257 | gateway 192.168.0.1 while the third one just activates the interface for |
258 | gateway 192.168.0.1 while the third one just activates the interface for |
| 258 | rp-pppoe usage: |
259 | rp-pppoe usage: |
| 259 | </p> |
260 | </p> |
| 260 | |
261 | |
| 261 | <pre caption="Examples for /etc/conf.d/net"> |
262 | <pre caption="Examples for /etc/conf.d/net"> |
| 262 | <comment>(For DHCP:)</comment> |
263 | <comment>(For DHCP)</comment> |
| 263 | iface_eth0="dhcp" |
264 | iface_eth0="dhcp" |
| 264 | |
265 | |
| 265 | <comment>(For static IP:)</comment> |
266 | <comment>(For static IP)</comment> |
| 266 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
267 | iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" |
| 267 | gateway="eth0/192.168.0.1" |
268 | gateway="eth0/192.168.0.1" |
| 268 | |
269 | |
| 269 | <comment>(For rp-pppoe:)</comment> |
270 | <comment>(For rp-pppoe)</comment> |
| 270 | iface_eth0="up" |
271 | iface_eth0="up" |
| 271 | </pre> |
272 | </pre> |
| 272 | |
273 | |
| 273 | <p> |
274 | <p> |
| 274 | If you have several network interfaces, create extra <c>iface_eth</c> variables, |
275 | If you have several network interfaces, create extra <c>iface_eth</c> variables, |
| … | |
… | |
| 338 | If your system is the only system (or the nameservers handle all name |
339 | If your system is the only system (or the nameservers handle all name |
| 339 | resolution) a single line is sufficient: |
340 | resolution) a single line is sufficient: |
| 340 | </p> |
341 | </p> |
| 341 | |
342 | |
| 342 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
343 | <pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 343 | 127.0.0.1 localhost tux |
344 | 127.0.0.1 localhost |
| 344 | </pre> |
345 | </pre> |
| 345 | |
346 | |
| 346 | <p> |
347 | <p> |
| 347 | Save and exit the editor to continue. |
348 | Save and exit the editor to continue. |
| 348 | </p> |
349 | </p> |
| … | |
… | |
| 357 | </subsection> |
358 | </subsection> |
| 358 | <subsection> |
359 | <subsection> |
| 359 | <title>Optional: Get PCMCIA Working</title> |
360 | <title>Optional: Get PCMCIA Working</title> |
| 360 | <body> |
361 | <body> |
| 361 | |
362 | |
|
|
363 | <note> |
|
|
364 | pcmcia-cs is only available for x86, amd64 and ppc platforms. |
|
|
365 | </note> |
|
|
366 | |
| 362 | <p> |
367 | <p> |
| 363 | PCMCIA-users should first install the <c>pcmcia-cs</c> package: |
368 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. The |
|
|
369 | <c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment: |
| 364 | </p> |
370 | </p> |
| 365 | |
371 | |
| 366 | <pre caption="Installing pcmcia-cs"> |
372 | <pre caption="Installing pcmcia-cs"> |
| 367 | # <i>emerge --usepkg pcmcia-cs</i> |
373 | # <i>USE="-X" emerge pcmcia-cs</i> |
| 368 | </pre> |
374 | </pre> |
| 369 | |
375 | |
| 370 | <p> |
376 | <p> |
| 371 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
377 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 372 | runlevel: |
378 | runlevel: |
| … | |
… | |
| 398 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
404 | you select the wrong <c>KEYMAP</c> you will get weird results when typing on |
| 399 | your keyboard. |
405 | your keyboard. |
| 400 | </p> |
406 | </p> |
| 401 | |
407 | |
| 402 | <note> |
408 | <note> |
| 403 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
409 | Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to |
| 404 | keymap (such as "us") instead of "sunkeymap". |
410 | select an i386 keymap (such as "us") instead of "sunkeymap". |
| 405 | </note> |
411 | </note> |
|
|
412 | |
|
|
413 | <p> |
|
|
414 | <b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use |
|
|
415 | ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have |
|
|
416 | to set a mac/ppc keymap in <path>rc.conf</path>. |
|
|
417 | </p> |
| 406 | |
418 | |
| 407 | <p> |
419 | <p> |
| 408 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
420 | When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then |
| 409 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
421 | continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>. |
| 410 | </p> |
422 | </p> |
Parent Directory
| 
Revision Log
| 
Patch