/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-config.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-config.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.44 Revision 1.62
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.44 2004/08/29 11:38:12 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.62 2005/06/09 07:16:39 swift Exp $ -->
8 8
9<sections> 9<sections>
10
11<version>2.4</version>
12<date>2005-06-09</date>
13
10<section> 14<section>
11<title>Filesystem Information</title> 15<title>Filesystem Information</title>
12<subsection> 16<subsection>
13<title>What is fstab?</title> 17<title>What is fstab?</title>
14<body> 18<body>
15 19
16<p> 20<p>
17Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
18<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions
19(where they are seen in the file system structure), how they should be mounted 23(where they are seen in the file system structure), how they should be mounted
20(special options) and when (automatically or not, can users mount those or not, 24and with what special options (automatically or not, whether users can mount
21etc.). 25them or not, etc.)
22</p> 26</p>
23 27
24</body> 28</body>
25</subsection> 29</subsection>
26<subsection> 30<subsection>
46 The third field shows the <b>filesystem</b> used by the partition 50 The third field shows the <b>filesystem</b> used by the partition
47</li> 51</li>
48<li> 52<li>
49 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it
50 wants to mount the partition. As every filesystem has its own mountoptions, 54 wants to mount the partition. As every filesystem has its own mountoptions,
51 you are encouraged to read the mount manpage (<c>man mount</c>) for a full 55 you are encouraged to read the mount man page (<c>man mount</c>) for a full
52 listing. Multiple mountoptions are comma-separated. 56 listing. Multiple mountoptions are comma-separated.
53</li> 57</li>
54<li> 58<li>
55 The fifth field is used by <c>dump</c> to determine if the partition needs to 59 The fifth field is used by <c>dump</c> to determine if the partition needs to
56 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
57</li> 61</li>
58<li> 62<li>
59 The sixth field is used by <c>fsck</c> to determine the order in which 63 The sixth field is used by <c>fsck</c> to determine the order in which
60 filesystems should be <b>check</b>ed if the system wasn't shut down properly. 64 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
61 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 65 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
62 (or <c>0</c> in case a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
63</li> 67</li>
64</ul> 68</ul>
65 69
66<p> 70<p>
67The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab 71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
122(required) and for your CD-ROM drive (and of course, if you have other 126(required) and for your CD-ROM drive (and of course, if you have other
123partitions or drives, for those too): 127partitions or drives, for those too):
124</p> 128</p>
125 129
126<pre caption="A full /etc/fstab example"> 130<pre caption="A full /etc/fstab example">
127/dev/hda1 /boot ext2 noauto,noatime 1 2 131/dev/hda1 /boot ext2 defaults,noatime 1 2
128/dev/hda2 none swap sw 0 0 132/dev/hda2 none swap sw 0 0
129/dev/hda3 / ext3 noatime 0 1 133/dev/hda3 / ext3 noatime 0 1
130 134
131none /proc proc defaults 0 0 135none /proc proc defaults 0 0
132none /dev/shm tmpfs defaults 0 0 136none /dev/shm tmpfs nodev,nosuid,noexec 0 0
133 137
134/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
135</pre> 139</pre>
136 140
137<p> 141<p>
147too: 151too:
148</p> 152</p>
149 153
150<pre caption="Adding openprom filesystem to /etc/fstab"> 154<pre caption="Adding openprom filesystem to /etc/fstab">
151none /proc/openprom openpromfs defaults 0 0 155none /proc/openprom openpromfs defaults 0 0
152</pre>
153
154<p>
155If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
156</p>
157
158<pre caption="Adding usbfs filesystem to /etc/fstab">
159none /proc/bus/usb usbfs defaults 0 0
160</pre> 156</pre>
161 157
162<p> 158<p>
163Double-check your <path>/etc/fstab</path>, save and quit to continue. 159Double-check your <path>/etc/fstab</path>, save and quit to continue.
164</p> 160</p>
226your Gentoo system permanently. 222your Gentoo system permanently.
227</p> 223</p>
228 224
229<p> 225<p>
230All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 226All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
231a straightforward yet not intuitive syntax if you don't know how to setup 227a straightforward yet not intuitive syntax if you don't know how to set up
232networking manually. But don't fear, we'll explain everything :) 228networking manually. But don't fear, we'll explain everything :)
233</p> 229</p>
234 230
235<p> 231<p>
236First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 232First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>
240<pre caption="Opening /etc/conf.d/net for editing"> 236<pre caption="Opening /etc/conf.d/net for editing">
241# <i>nano -w /etc/conf.d/net</i> 237# <i>nano -w /etc/conf.d/net</i>
242</pre> 238</pre>
243 239
244<p> 240<p>
245The first variable you'll find is <c>iface_eth0</c>. It uses the following 241The first variable you'll find is called <c>config_eth0</c>. As you can probably
246syntax: 242imagine, this variable configured the eth0 network interface. If the interface
247</p> 243needs to automatically obtain an IP through DHCP, you should set it like so:
248
249<pre caption="iface_eth0 syntaxis">
250iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
251</pre>
252
253<p> 244</p>
254If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 245
255to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 246<pre caption="Automatically obtaining an IP for eth0">
256If you need to setup your network manually and you're 247config_eth0=( "dhcp" )
257not familiar with all the above terms, please read the section on <uri 248</pre>
258link="?part=1&amp;chap=3#network_term">Understanding Network 249
259Terminology</uri> if you haven't done so already.
260</p> 250<p>
261 251However, if you have to enter your own IP address, netmask and gateway, you need
252to set both <c>config_eth0</c> and <c>routes_eth0</c>:
262<p> 253</p>
263So let us give three examples; the first one uses DHCP, the second one a static 254
264IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 255<pre caption="Manually setting IP information for eth0">
265gateway 192.168.0.1 while the third one just activates the interface for 256config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
266rp-pppoe usage: 257routes_eth0=( "default gw 192.168.0.1" )
258</pre>
259
267</p> 260<p>
268 261If you have several network interfaces repeat the above steps for
269<pre caption="Examples for /etc/conf.d/net"> 262<c>config_eth1</c>, <c>config_eth2</c>, etc.
270<comment>(For DHCP)</comment>
271iface_eth0="dhcp"
272<comment># Some network admins require that you use the</comment>
273<comment># hostname and domainname provided by the DHCP server.</comment>
274<comment># In that case, add the following to let dhcpcd use them.</comment>
275<comment># That will override your own hostname and domainname definitions.</comment>
276dhcpcd_eth0="-HD"
277<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
278<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
279dhcpcd_eth0="-N"
280
281<comment>(For static IP)</comment>
282iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
283gateway="eth0/192.168.0.1"
284
285<comment>(For rp-pppoe)</comment>
286iface_eth0="up"
287</pre>
288
289<p>
290If you have several network interfaces, create extra <c>iface_eth</c> variables,
291like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
292shouldn't be reproduced as you can only set one gateway per computer.
293</p> 263</p>
294 264
295<p> 265<p>
296Now save the configuration and exit to continue. 266Now save the configuration and exit to continue.
297</p> 267</p>
301<subsection> 271<subsection>
302<title>Automatically Start Networking at Boot</title> 272<title>Automatically Start Networking at Boot</title>
303<body> 273<body>
304 274
305<p> 275<p>
306To have your network interfaces activated at boot, you need to add those to the 276To have your network interfaces activated at boot, you need to add them to the
307default runlevel. If you have PCMCIA interfaces you should skip this action as 277default runlevel. If you have PCMCIA interfaces you should skip this action as
308the PCMCIA interfaces are started by the PCMCIA init script. 278the PCMCIA interfaces are started by the PCMCIA init script.
309</p> 279</p>
310 280
311<pre caption="Adding net.eth0 to the default runlevel"> 281<pre caption="Adding net.eth0 to the default runlevel">
351</pre> 321</pre>
352 322
353<p> 323<p>
354If your system is the only system (or the nameservers handle all name 324If your system is the only system (or the nameservers handle all name
355resolution) a single line is sufficient. For instance, if you want to call your 325resolution) a single line is sufficient. For instance, if you want to call your
356system <c>tux.homenetwork</c>: 326system <c>tux</c>:
357</p> 327</p>
358 328
359<pre caption="/etc/hosts for lonely or fully integrated PCs"> 329<pre caption="/etc/hosts for lonely or fully integrated PCs">
360127.0.0.1 tux.homenetwork tux localhost 330127.0.0.1 localhost tux
361</pre> 331</pre>
362 332
363<p> 333<p>
364Save and exit the editor to continue. 334Save and exit the editor to continue.
365</p> 335</p>
379<note> 349<note>
380pcmcia-cs is only available for x86, amd64 and ppc platforms. 350pcmcia-cs is only available for x86, amd64 and ppc platforms.
381</note> 351</note>
382 352
383<p> 353<p>
384PCMCIA-users should first install the <c>pcmcia-cs</c> package. The 354PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
355includes users who will be working with a 2.6 kernel (even though they won't be
356using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
385<c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment: 357to avoid installing xorg-x11 at this moment:
386</p> 358</p>
387 359
388<pre caption="Installing pcmcia-cs"> 360<pre caption="Installing pcmcia-cs">
389# <i>USE="-X" emerge pcmcia-cs</i> 361# <i>USE="-X" emerge pcmcia-cs</i>
390</pre> 362</pre>
456ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 428ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
457to set a mac/ppc keymap in <path>rc.conf</path>. 429to set a mac/ppc keymap in <path>rc.conf</path>.
458</p> 430</p>
459 431
460<p> 432<p>
433If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
434the file. Otherwise you will notice some clock skew.
435</p>
436
437<p>
461When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 438When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
439</p>
440
441<p>
442If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with
443<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>.
444</p>
445
446</body>
447</subsection>
448<subsection>
449<title>Configuring the Console</title>
450<body>
451
452<note>
453The following section applies to the IBM POWER5 and JS20 hardware platforms.
454</note>
455
456<p>
457If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
458the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
459</p>
460
461<pre caption="Enabling hvc support in /etc/inittab">
462hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220
463</pre>
464
465<p>
462continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 466You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
463Tools</uri>. 467System Tools</uri>.
464</p> 468</p>
465 469
466</body> 470</body>
467</subsection> 471</subsection>
468</section> 472</section>

Legend:
Removed from v.1.44  
changed lines
  Added in v.1.62

  ViewVC Help
Powered by ViewVC 1.1.20