/[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.17 Revision 1.56
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
1<!-- 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 -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3 6
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.17 2004/01/06 10:08:38 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.56 2005/03/28 11:30:52 swift Exp $ -->
5 8
6<sections> 9<sections>
7<section>
8<title>Timezone</title>
9<body>
10 10
11<p> 11<version>2.00</version>
12You now need to select your timezone so that your system knows where it is 12<date>2005-03-28</date>
13located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
14symlink to <path>/etc/localtime</path> using <c>ln</c>:
15</p>
16 13
17<pre caption="Setting the timezone information">
18# <i>ls /usr/share/zoneinfo</i>
19<comment>(Suppose you want to use GMT:)</comment>
20# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
21</pre>
22
23</body>
24</section>
25<section> 14<section>
26<title>Filesystem Information</title> 15<title>Filesystem Information</title>
27<subsection> 16<subsection>
28<title>What is fstab?</title> 17<title>What is fstab?</title>
29<body> 18<body>
30 19
31<p> 20<p>
32Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
33<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
34(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
35(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
36etc.). 25them or not, etc.)
37</p> 26</p>
38 27
39</body> 28</body>
40</subsection> 29</subsection>
41<subsection> 30<subsection>
61 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
62</li> 51</li>
63<li> 52<li>
64 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
65 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,
66 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
67 listing. Multiple mountoptions are comma-separated. 56 listing. Multiple mountoptions are comma-separated.
68</li> 57</li>
69<li> 58<li>
70 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
71 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).
72</li> 61</li>
73<li> 62<li>
74 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
75 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.
76 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>
77 (or <c>0</c> in case a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
78</li> 67</li>
79</ul> 68</ul>
80 69
81<p> 70<p>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
82So 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
83<path>/etc/fstab</path>: 73<path>/etc/fstab</path>:
84</p> 74</p>
85 75
86<pre caption="Opening /etc/fstab"> 76<pre caption="Opening /etc/fstab">
87# <i>nano -w /etc/fstab</i> 77# <i>nano -w /etc/fstab</i>
88</pre> 78</pre>
89 79
90<p> 80<p>
91Let 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>
92partition. 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
93<path>/boot</path> partition, don't copy it verbatim. 83<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
94</p> 84</p>
95 85
96<p> 86<p>
97In our default x86 partitioning example <path>/boot</path> is the 87In our default x86 partitioning example <path>/boot</path> is the
98<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't 88<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
99be mounted automatically (<c>noauto</c>) but does need to be checked. So we 89It needs to be checked during boot, so we would write down:
100would write down:
101</p> 90</p>
102 91
103<pre caption="An example /boot line for /etc/fstab"> 92<pre caption="An example /boot line for /etc/fstab">
104/dev/hda1 /boot ext2 noauto 1 2 93/dev/hda1 /boot ext2 defaults 1 2
94</pre>
95
96<p>
97Some users don't want their <path>/boot</path> partition to be mounted
98automatically to improve their system's security. Those people should
99substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
100manually mount this partition every time you want to use it.
105</pre> 101</p>
106 102
107<p> 103<p>
108Now, to improve performance, most users would want to add the <c>noatime</c> 104Now, to improve performance, most users would want to add the <c>noatime</c>
109option as mountoption, which results in a faster system since access times 105option as mountoption, which results in a faster system since access times
110aren't registered (you don't need those generally anyway): 106aren't registered (you don't need those generally anyway):
111</p> 107</p>
112 108
113<pre caption="An improved /boot line for /etc/fstab"> 109<pre caption="An improved /boot line for /etc/fstab">
114/dev/hda1 /boot ext2 noauto,noatime 1 2 110/dev/hda1 /boot ext2 defaults,noatime 1 2
115</pre> 111</pre>
116 112
117<p> 113<p>
118If we continue with this, we would end up with the following three lines (for 114If we continue with this, we would end up with the following three lines (for
119<path>/boot</path>, <path>/</path> and the swap partition): 115<path>/boot</path>, <path>/</path> and the swap partition):
120</p> 116</p>
121 117
122<pre caption="Three /etc/fstab lines"> 118<pre caption="Three /etc/fstab lines">
123/dev/hda1 /boot ext2 noauto,noatime 1 2 119/dev/hda1 /boot ext2 defaults,noatime 1 2
124/dev/hda2 none swap sw 0 0 120/dev/hda2 none swap sw 0 0
125/dev/hda3 / ext3 noatime 0 1 121/dev/hda3 / ext3 noatime 0 1
126</pre> 122</pre>
127 123
128<p> 124<p>
130(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
131partitions or drives, for those too): 127partitions or drives, for those too):
132</p> 128</p>
133 129
134<pre caption="A full /etc/fstab example"> 130<pre caption="A full /etc/fstab example">
135/dev/hda1 /boot ext2 noauto,noatime 1 2 131/dev/hda1 /boot ext2 defaults,noatime 1 2
136/dev/hda2 none swap sw 0 0 132/dev/hda2 none swap sw 0 0
137/dev/hda3 / ext3 noatime 0 1 133/dev/hda3 / ext3 noatime 0 1
138 134
139none /proc proc defaults 0 0 135none /proc proc defaults 0 0
140none /dev/shm tmpfs defaults 0 0 136none /dev/shm tmpfs nodev,nosuid,noexec 0 0
141 137
142/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
143</pre> 139</pre>
144 140
145<p> 141<p>
148<c>user</c> makes it possible for non-root users to mount the CD. 144<c>user</c> makes it possible for non-root users to mount the CD.
149</p> 145</p>
150 146
151<p> 147<p>
152Now use the above example to create your <path>/etc/fstab</path>. If you are a 148Now use the above example to create your <path>/etc/fstab</path>. If you are a
153SPARC-user, you should add the following line to your <path>/etc/fstab</path> 149<b>SPARC</b>-user, you should add the following line to your
150<path>/etc/fstab</path>
154too: 151too:
155</p> 152</p>
156 153
157<pre caption="Adding openprom filesystem to /etc/fstab"> 154<pre caption="Adding openprom filesystem to /etc/fstab">
158none /proc/openprom openpromfs defaults 0 0 155none /proc/openprom openpromfs defaults 0 0
165<pre caption="Adding usbfs filesystem to /etc/fstab"> 162<pre caption="Adding usbfs filesystem to /etc/fstab">
166none /proc/bus/usb usbfs defaults 0 0 163none /proc/bus/usb usbfs defaults 0 0
167</pre> 164</pre>
168 165
169<p> 166<p>
170Reread your <path>/etc/fstab</path>, save and quit to continue. 167Double-check your <path>/etc/fstab</path>, save and quit to continue.
171</p> 168</p>
172 169
173</body> 170</body>
174</subsection> 171</subsection>
175</section> 172</section>
178<subsection> 175<subsection>
179<title>Hostname, Domainname etc.</title> 176<title>Hostname, Domainname etc.</title>
180<body> 177<body>
181 178
182<p> 179<p>
183One of the choices the user has to make is name his PC. This seems to be quite 180One of the choices the user has to make is name his/her PC. This seems to be
184easy, but <e>lots</e> of users are having difficulties finding the appropriate 181quite easy, but <e>lots</e> of users are having difficulties finding the
185name for their Linux-pc. To speed things up, know that any name you choose can 182appropriate name for their Linux-pc. To speed things up, know that any name you
186be changed afterwards. For all we care, you can just call your system 183choose can be changed afterwards. For all we care, you can just call your system
187<c>tux</c> and domain <c>homenetwork</c>. 184<c>tux</c> and domain <c>homenetwork</c>.
188</p> 185</p>
189 186
190<p> 187<p>
191We use these values in the next examples. First we set the hostname: 188We use these values in the next examples. First we set the hostname:
233your Gentoo system permanently. 230your Gentoo system permanently.
234</p> 231</p>
235 232
236<p> 233<p>
237All 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
238a 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
239networking manually. But don't fear, we'll explain everything :) 236networking manually. But don't fear, we'll explain everything :)
240</p> 237</p>
241 238
242<p> 239<p>
243First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 240First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>
257iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>" 254iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
258</pre> 255</pre>
259 256
260<p> 257<p>
261If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 258If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
259to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.
262to <c>dhcp</c>. However, if you need to setup your network manually and you're 260If you need to set up your network manually and you're
263not familiar with all the above terms, please read the section on <uri 261not familiar with all the above terms, please read the section on <uri
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 262link="?part=1&amp;chap=3#network_term">Understanding Network
265Terminology</uri> if you haven't done so already. 263Terminology</uri> if you haven't done so already.
266</p> 264</p>
267 265
268<p> 266<p>
269So let us give two examples; the first one uses DHCP, the second one a static IP 267So let us give three examples; the first one uses DHCP, the second one a static
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 268IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and
271192.168.0.1: 269gateway 192.168.0.1 while the third one just activates the interface for
270rp-pppoe usage:
272</p> 271</p>
273 272
274<pre caption="Examples for /etc/conf.d/net"> 273<pre caption="Examples for /etc/conf.d/net">
275<comment>(For DHCP:)</comment> 274<comment>(For DHCP)</comment>
276iface_eth0="dhcp" 275iface_eth0="dhcp"
276<comment># Some network admins require that you use the</comment>
277<comment># hostname and domainname provided by the DHCP server.</comment>
278<comment># In that case, add the following to let dhcpcd use them.</comment>
279<comment># That will override your own hostname and domainname definitions.</comment>
280dhcpcd_eth0="-HD"
281<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
282<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
283dhcpcd_eth0="-N"
277 284
278<comment>(For static IP:)</comment> 285<comment>(For static IP)</comment>
279iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" 286iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
280gateway="eth0/192.168.0.1" 287gateway="eth0/192.168.0.1"
288
289<comment>(For rp-pppoe)</comment>
290iface_eth0="up"
281</pre> 291</pre>
282 292
283<p> 293<p>
284If you have several network interfaces, create extra <c>iface_eth</c> variables, 294If you have several network interfaces, create extra <c>iface_eth</c> variables,
285like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 295like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
295<subsection> 305<subsection>
296<title>Automatically Start Networking at Boot</title> 306<title>Automatically Start Networking at Boot</title>
297<body> 307<body>
298 308
299<p> 309<p>
300To have your network interfaces activated at boot, you need to add those to the 310To have your network interfaces activated at boot, you need to add them to the
301default runlevel. If you have PCMCIA interfaces you should skip this action as 311default runlevel. If you have PCMCIA interfaces you should skip this action as
302the PCMCIA interfaces are started by the PCMCIA init script. 312the PCMCIA interfaces are started by the PCMCIA init script.
303</p> 313</p>
304 314
305<pre caption="Adding net.eth0 to the default runlevel"> 315<pre caption="Adding net.eth0 to the default runlevel">
337# <i>nano -w /etc/hosts</i> 347# <i>nano -w /etc/hosts</i>
338</pre> 348</pre>
339 349
340<pre caption="Filling in the networking information"> 350<pre caption="Filling in the networking information">
341127.0.0.1 localhost 351127.0.0.1 localhost
342192.168.0.5 jenny 352192.168.0.5 jenny.homenetwork jenny
343192.168.0.6 benny 353192.168.0.6 benny.homenetwork benny
344192.168.0.7 tux 354192.168.0.7 tux.homenetwork tux
345</pre> 355</pre>
346 356
347<p> 357<p>
348If your system is the only system (or the nameservers handle all name 358If your system is the only system (or the nameservers handle all name
349resolution) a single line is sufficient: 359resolution) a single line is sufficient. For instance, if you want to call your
360system <c>tux</c>:
350</p> 361</p>
351 362
352<pre caption="/etc/hosts for lonely or fully integrated PCs"> 363<pre caption="/etc/hosts for lonely or fully integrated PCs">
353127.0.0.1 localhost tux 364127.0.0.1 localhost tux
354</pre> 365</pre>
355 366
356<p> 367<p>
357Save and exit the editor to continue. 368Save and exit the editor to continue.
358</p> 369</p>
359 370
360<p> 371<p>
361If you don't have PCMCIA, you can now continue with <uri 372If you don't have PCMCIA, you can now continue with <uri
362link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 373link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
363following topic on PCMCIA. 374following topic on PCMCIA.
364</p> 375</p>
365 376
366</body> 377</body>
367</subsection> 378</subsection>
368<subsection> 379<subsection>
369<title>Optional: Get PCMCIA Working</title> 380<title>Optional: Get PCMCIA Working</title>
370<body> 381<body>
371 382
383<note>
384pcmcia-cs is only available for x86, amd64 and ppc platforms.
385</note>
386
372<p> 387<p>
373PCMCIA-users should first install the <c>pcmcia-cs</c> package: 388PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
389includes users who will be working with a 2.6 kernel (even though they won't be
390using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
391to avoid installing xorg-x11 at this moment:
374</p> 392</p>
375 393
376<pre caption="Installing pcmcia-cs"> 394<pre caption="Installing pcmcia-cs">
377# <i>emerge --usepkg pcmcia-cs</i> 395# <i>USE="-X" emerge pcmcia-cs</i>
378</pre> 396</pre>
379 397
380<p> 398<p>
381When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 399When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
382runlevel: 400runlevel:
383</p> 401</p>
384 402
385<pre caption="Adding pcmcia to the boot runlevel"> 403<pre caption="Adding pcmcia to the default runlevel">
386# <i>rc-update add pcmcia boot</i> 404# <i>rc-update add pcmcia default</i>
387</pre> 405</pre>
388 406
389</body> 407</body>
390</subsection> 408</subsection>
391</section> 409</section>
392<section> 410<section>
411<title>System Information</title>
412<subsection>
413<title>Root Password</title>
414<body>
415
416<p>
417First we set the root password by typing:
418</p>
419
420<pre caption="Setting the root password">
421# <i>passwd</i>
422</pre>
423
424<p>
425If you want root to be able to log on through the serial console, add
426<c>tts/0</c> to <path>/etc/securetty</path>:
427</p>
428
429<pre caption="Adding tts/0 to /etc/securetty">
430# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
431</pre>
432
433</body>
434</subsection>
435<subsection>
393<title>System Information</title> 436<title>System Information</title>
394<body> 437<body>
395 438
396<p> 439<p>
397Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 440Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
408you select the wrong <c>KEYMAP</c> you will get weird results when typing on 451you select the wrong <c>KEYMAP</c> you will get weird results when typing on
409your keyboard. 452your keyboard.
410</p> 453</p>
411 454
412<note> 455<note>
413Users of USB-based SPARC systems and SPARC clones might need to select an i386 456Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
414keymap (such as "us") instead of "sunkeymap". 457select an i386 keymap (such as "us") instead of "sunkeymap".
415</note> 458</note>
416 459
417<p> 460<p>
461<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
462ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
463to set a mac/ppc keymap in <path>rc.conf</path>.
464</p>
465
466<p>
418When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 467When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
419continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 468continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
469Tools</uri>.
420</p> 470</p>
421 471
422</body> 472</body>
473</subsection>
423</section> 474</section>
424</sections> 475</sections>

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.56

  ViewVC Help
Powered by ViewVC 1.1.20