/[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.33 Revision 1.76
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
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/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.33 2004/04/15 07:06:36 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.76 2006/03/28 10:35:59 neysx Exp $ -->
8 8
9<sections> 9<sections>
10
11<version>2.18</version>
12<date>2006-03-28</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>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
67So start <c>nano</c> (or your favorite editor) to create your 72file</e>, so start <c>nano</c> (or your favorite editor) to create your
68<path>/etc/fstab</path>: 73<path>/etc/fstab</path>:
69</p> 74</p>
70 75
71<pre caption="Opening /etc/fstab"> 76<pre caption="Opening /etc/fstab">
72# <i>nano -w /etc/fstab</i> 77# <i>nano -w /etc/fstab</i>
73</pre> 78</pre>
74 79
75<p> 80<p>
76Let us take a look at how we write down the options for the <path>/boot</path> 81Let us take a look at how we write down the options for the <path>/boot</path>
77partition. This is just an example, so if your architecture doesn't require a 82partition. This is just an example, so if your architecture doesn't require a
78<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. 83<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it
84verbatim.
79</p> 85</p>
80 86
81<p> 87<p>
82In our default x86 partitioning example <path>/boot</path> is the 88In 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 89<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
84be mounted automatically (<c>noauto</c>) but does need to be checked. So we 90It needs to be checked during boot, so we would write down:
85would write down:
86</p> 91</p>
87 92
88<pre caption="An example /boot line for /etc/fstab"> 93<pre caption="An example /boot line for /etc/fstab">
89/dev/hda1 /boot ext2 noauto 1 2 94/dev/hda1 /boot ext2 defaults 1 2
95</pre>
96
97<p>
98Some users don't want their <path>/boot</path> partition to be mounted
99automatically to improve their system's security. Those people should
100substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
101manually mount this partition every time you want to use it.
90</pre> 102</p>
91 103
92<p> 104<p>
93Now, to improve performance, most users would want to add the <c>noatime</c> 105Now, to improve performance, most users would want to add the <c>noatime</c>
94option as mountoption, which results in a faster system since access times 106option as mountoption, which results in a faster system since access times
95aren't registered (you don't need those generally anyway): 107aren't registered (you don't need those generally anyway):
96</p> 108</p>
97 109
98<pre caption="An improved /boot line for /etc/fstab"> 110<pre caption="An improved /boot line for /etc/fstab">
99/dev/hda1 /boot ext2 noauto,noatime 1 2 111/dev/hda1 /boot ext2 defaults,noatime 1 2
100</pre> 112</pre>
101 113
102<p> 114<p>
103If we continue with this, we would end up with the following three lines (for 115If we continue with this, we would end up with the following three lines (for
104<path>/boot</path>, <path>/</path> and the swap partition): 116<path>/boot</path>, <path>/</path> and the swap partition):
105</p> 117</p>
106 118
107<pre caption="Three /etc/fstab lines"> 119<pre caption="Three /etc/fstab lines">
108/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 defaults,noatime 1 2
109/dev/hda2 none swap sw 0 0 121/dev/hda2 none swap sw 0 0
110/dev/hda3 / ext3 noatime 0 1 122/dev/hda3 / ext3 noatime 0 1
111</pre> 123</pre>
112 124
113<p> 125<p>
115(required) and for your CD-ROM drive (and of course, if you have other 127(required) and for your CD-ROM drive (and of course, if you have other
116partitions or drives, for those too): 128partitions or drives, for those too):
117</p> 129</p>
118 130
119<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example">
120/dev/hda1 /boot ext2 noauto,noatime 1 2 132/dev/hda1 /boot ext2 defaults,noatime 1 2
121/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
122/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
123 135
124none /proc proc defaults 0 0 136none /proc proc defaults 0 0
125none /dev/shm tmpfs defaults 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
126 138
127/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
128</pre> 140</pre>
129 141
130<p> 142<p>
143<pre caption="Adding openprom filesystem to /etc/fstab"> 155<pre caption="Adding openprom filesystem to /etc/fstab">
144none /proc/openprom openpromfs defaults 0 0 156none /proc/openprom openpromfs defaults 0 0
145</pre> 157</pre>
146 158
147<p> 159<p>
148If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
149</p>
150
151<pre caption="Adding usbfs filesystem to /etc/fstab">
152none /proc/bus/usb usbfs defaults 0 0
153</pre>
154
155<p>
156Reread your <path>/etc/fstab</path>, save and quit to continue. 160Double-check your <path>/etc/fstab</path>, save and quit to continue.
157</p> 161</p>
158 162
159</body> 163</body>
160</subsection> 164</subsection>
161</section> 165</section>
176<p> 180<p>
177We use these values in the next examples. First we set the hostname: 181We use these values in the next examples. First we set the hostname:
178</p> 182</p>
179 183
180<pre caption="Setting the hostname"> 184<pre caption="Setting the hostname">
181# <i>echo tux &gt; /etc/hostname</i> 185# <i>nano -w /etc/conf.d/hostname</i>
186
187<comment>(Set the HOSTNAME variable to your hostname)</comment>
188HOSTNAME="<i>tux</i>"
182</pre> 189</pre>
183 190
184<p> 191<p>
185Second we set the domainname: 192Second we set the domainname:
186</p> 193</p>
187 194
188<pre caption="Setting the domainname"> 195<pre caption="Setting the domainname">
189# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 196# <i>nano -w /etc/conf.d/domainname</i>
197
198<comment>(Set the DNSDOMAIN variable to your domain name)</comment>
199DNSDOMAIN="<i>homenetwork</i>"
190</pre> 200</pre>
191 201
192<p> 202<p>
193If you have a NIS domain (if you don't know what that is, then you don't have 203If you have a NIS domain (if you don't know what that is, then you don't have
194one), you need to define that one too: 204one), you need to define that one too:
195</p> 205</p>
196 206
197<pre caption="Setting the NIS domainname"> 207<pre caption="Setting the NIS domainname">
198# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 208# <i>nano -w /etc/conf.d/domainname</i>
199</pre>
200 209
201<p> 210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
202Now add the <c>domainname</c> script to the default runlevel: 211NISDOMAIN="<i>my-nisdomain</i>"
203</p>
204
205<pre caption="Adding domainname to the default runlevel">
206# <i>rc-update add domainname default</i>
207</pre> 212</pre>
208 213
209</body> 214</body>
210</subsection> 215</subsection>
211<subsection> 216<subsection>
212<title>Configuring your Network</title> 217<title>Configuring your Network</title>
213<body> 218<body>
214 219
215<p> 220<p>
216Before you get that "Hey, we've had that already"-feeling, you should remember 221Before you get that "Hey, we've had that already"-feeling, you should remember
217that the networking you set up in the beginning of the gentoo installation was 222that the networking you set up in the beginning of the Gentoo installation was
218just for the installation. Right now you are going to configure networking for 223just for the installation. Right now you are going to configure networking for
219your Gentoo system permanently. 224your Gentoo system permanently.
220</p> 225</p>
221 226
227<note>
228More detailed information about networking, including advanced topics like
229bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
230link="?part=4">Gentoo Network Configuration</uri> section.
231</note>
232
222<p> 233<p>
223All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 234All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
224a straightforward yet not intuitive syntax if you don't know how to setup 235a straightforward yet not intuitive syntax if you don't know how to set up
225networking manually. But don't fear, we'll explain everything :) 236networking manually. But don't fear, we'll explain everything. A fully
226</p> 237commented example that covers many different configurations is available in
227 238<path>/etc/conf.d/net.example</path>.
228<p> 239</p>
240
241<p>
242DHCP is used by default and does not require any further configuration.
243</p>
244
245<p>
246If you need to configure your network connection either because you need
247specific DHCP options or because you do not use DHCP at all, open
229First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 248<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
230is used in this example): 249this example):
231</p> 250</p>
232 251
233<pre caption="Opening /etc/conf.d/net for editing"> 252<pre caption="Opening /etc/conf.d/net for editing">
234# <i>nano -w /etc/conf.d/net</i> 253# <i>nano -w /etc/conf.d/net</i>
235</pre> 254</pre>
236 255
237<p> 256<p>
238The first variable you'll find is <c>iface_eth0</c>. It uses the following 257You will see the following file:
239syntax:
240</p>
241
242<pre caption="iface_eth0 syntaxis">
243iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
244</pre>
245
246<p> 258</p>
247If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 259
248to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 260<pre caption="Default /etc/conf.d/net">
249If you need to setup your network manually and you're 261# This blank configuration will automatically use DHCP for any net.*
250not familiar with all the above terms, please read the section on <uri 262# scripts in /etc/init.d. To create a more complete configuration,
251link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 263# please review /etc/conf.d/net.example and save your configuration
252Terminology</uri> if you haven't done so already. 264# in /etc/conf.d/net (this file :]!).
265</pre>
266
253</p> 267<p>
254 268To enter your own IP address, netmask and gateway, you need
269to set both <c>config_eth0</c> and <c>routes_eth0</c>:
255<p> 270</p>
256So let us give three examples; the first one uses DHCP, the second one a static 271
257IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 272<pre caption="Manually setting IP information for eth0">
258gateway 192.168.0.1 while the third one just activates the interface for 273config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
259rp-pppoe usage: 274routes_eth0=( "default gw 192.168.0.1" )
275</pre>
276
260</p> 277<p>
261 278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
262<pre caption="Examples for /etc/conf.d/net"> 279<c>dhcp_eth0</c>:
263<comment>(For DHCP)</comment>
264iface_eth0="dhcp"
265
266<comment>(For static IP)</comment>
267iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
268gateway="eth0/192.168.0.1"
269
270<comment>(For rp-pppoe)</comment>
271iface_eth0="up"
272</pre>
273
274<p> 280</p>
275If you have several network interfaces, create extra <c>iface_eth</c> variables, 281
276like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282<pre caption="Automatically obtaining an IP address for eth0">
277shouldn't be reproduced as you can only set one gateway per computer. 283config_eth0=( "dhcp" )
284dhcp_eth0="nodns nontp nonis"
285</pre>
286
287<p>
288Please read <path>/etc/conf.d/net.example</path> for a list of all available
289options.
290</p>
291
292<p>
293If you have several network interfaces repeat the above steps for
294<c>config_eth1</c>, <c>config_eth2</c>, etc.
278</p> 295</p>
279 296
280<p> 297<p>
281Now save the configuration and exit to continue. 298Now save the configuration and exit to continue.
282</p> 299</p>
286<subsection> 303<subsection>
287<title>Automatically Start Networking at Boot</title> 304<title>Automatically Start Networking at Boot</title>
288<body> 305<body>
289 306
290<p> 307<p>
291To have your network interfaces activated at boot, you need to add those to the 308To have your network interfaces activated at boot, you need to add them to the
292default runlevel. If you have PCMCIA interfaces you should skip this action as 309default runlevel. If you have PCMCIA interfaces you should skip this action as
293the PCMCIA interfaces are started by the PCMCIA init script. 310the PCMCIA interfaces are started by the PCMCIA init script.
294</p> 311</p>
295 312
296<pre caption="Adding net.eth0 to the default runlevel"> 313<pre caption="Adding net.eth0 to the default runlevel">
335192.168.0.7 tux.homenetwork tux 352192.168.0.7 tux.homenetwork tux
336</pre> 353</pre>
337 354
338<p> 355<p>
339If your system is the only system (or the nameservers handle all name 356If your system is the only system (or the nameservers handle all name
340resolution) a single line is sufficient: 357resolution) a single line is sufficient. For instance, if you want to call your
358system <c>tux</c>:
341</p> 359</p>
342 360
343<pre caption="/etc/hosts for lonely or fully integrated PCs"> 361<pre caption="/etc/hosts for lonely or fully integrated PCs">
344127.0.0.1 localhost 362127.0.0.1 localhost tux
345</pre> 363</pre>
346 364
347<p> 365<p>
348Save and exit the editor to continue. 366Save and exit the editor to continue.
349</p> 367</p>
363<note> 381<note>
364pcmcia-cs is only available for x86, amd64 and ppc platforms. 382pcmcia-cs is only available for x86, amd64 and ppc platforms.
365</note> 383</note>
366 384
367<p> 385<p>
368PCMCIA-users should first install the <c>pcmcia-cs</c> package. The 386PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
369<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment: 387includes users who will be working with a 2.6 kernel (even though they won't be
388using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
389to avoid installing xorg-x11 at this moment:
370</p> 390</p>
371 391
372<pre caption="Installing pcmcia-cs"> 392<pre caption="Installing pcmcia-cs">
373# <i>USE="-X" emerge pcmcia-cs</i> 393# <i>USE="-X" emerge pcmcia-cs</i>
374</pre> 394</pre>
385</body> 405</body>
386</subsection> 406</subsection>
387</section> 407</section>
388<section> 408<section>
389<title>System Information</title> 409<title>System Information</title>
410<subsection>
411<title>Root Password</title>
412<body>
413
414<p>
415First we set the root password by typing:
416</p>
417
418<pre caption="Setting the root password">
419# <i>passwd</i>
420</pre>
421
422<p>
423If you want root to be able to log on through the serial console, add
424<c>tts/0</c> to <path>/etc/securetty</path>:
425</p>
426
427<pre caption="Adding tts/0 to /etc/securetty">
428# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
429</pre>
430
431</body>
432</subsection>
433<subsection>
434<title>System Information</title>
390<body> 435<body>
391 436
392<p> 437<p>
393Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 438Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
394Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) 439Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
397<pre caption="Opening /etc/rc.conf"> 442<pre caption="Opening /etc/rc.conf">
398# <i>nano -w /etc/rc.conf</i> 443# <i>nano -w /etc/rc.conf</i>
399</pre> 444</pre>
400 445
401<p> 446<p>
447When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
448</p>
449
450<p>
402As you can see, this file is well commented to help you set up the necessary 451As you can see, this file is well commented to help you set up the necessary
403configuration variables. Take special care with the <c>KEYMAP</c> setting: if 452configuration variables. You can configure your system to use unicode and
404you select the wrong <c>KEYMAP</c> you will get weird results when typing on 453define your default editor and your display manager (like gdm or kdm).
405your keyboard. 454</p>
455
456<p>
457Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
458Edit it to configure your keyboard.
459</p>
460
461<pre caption="Opening /etc/conf.d/keymaps">
462# <i>nano -w /etc/conf.d/keymaps</i>
463</pre>
464
465<p>
466Take special care with the <c>KEYMAP</c> variable. If you select the wrong
467<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
406</p> 468</p>
407 469
408<note> 470<note>
409Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 471Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
410select an i386 keymap (such as "us") instead of "sunkeymap". 472select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
473keymaps on most systems. Users who want to be able to use ADB keymaps on boot
474have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
475keymap in <path>/etc/conf.d/keymaps</path>.
411</note> 476</note>
412 477
413<p> 478<p>
414<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 479When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
415ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 480exit.
416to set a mac/ppc keymap in <path>rc.conf</path>.
417</p>
418
419<p> 481</p>
420When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 482
421continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
422</p> 483<p>
484Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
485according to your needs.
486</p>
423 487
488<pre caption="Opening /etc/conf.d/clock">
489# <i>nano -w /etc/conf.d/clock</i>
490</pre>
491
492<p>
493If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
494the file. Otherwise you will notice some clock skew. Furthermore, Windows
495assumes that your hardware clock uses local time, so if you want to dualboot,
496you should set this variable appropriately, otherwise your clock will go crazy.
497</p>
498
499<p>
500When you're finished configuring <path>/etc/conf.d/clock</path>, save and
501exit.
502</p>
503
504<p>
505If you are not installing Gentoo on IBM PPC64 hardware, continue with
506<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>.
507</p>
508
509</body>
510</subsection>
511<subsection>
512<title>Configuring the Console</title>
424</body> 513<body>
514
515<note>
516The following section applies to the IBM PPC64 hardware platforms.
517</note>
518
519<p>
520If you are running Gentoo on IBM PPC64 hardware and using a virtual console
521you must uncomment the appropriate line in <path>/etc/inittab</path> for the
522virtual console to spawn a login prompt.
523</p>
524
525<pre caption="Enabling hvc or hvsi support in /etc/inittab">
526hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
527hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
528</pre>
529
530<p>
531You should also take this time to verify that the appropriate console is
532listed in <path>/etc/securetty</path>.
533</p>
534
535<p>
536You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
537System Tools</uri>.
538</p>
539
540</body>
541</subsection>
425</section> 542</section>
426</sections> 543</sections>

Legend:
Removed from v.1.33  
changed lines
  Added in v.1.76

  ViewVC Help
Powered by ViewVC 1.1.20