/[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.49 Revision 1.78
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.49 2004/10/23 11:04:27 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.78 2006/05/27 13:02:15 neysx Exp $ -->
8 8
9<sections> 9<sections>
10
11<version>2.19</version>
12<date>2006-05-27</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>
62 (or <c>0</c> if 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 not a valid
68file</e>, so start <c>nano</c> (or your favorite editor) to create your 72fstab file</e>, so start <c>nano</c> (or your favorite editor) to create your
69<path>/etc/fstab</path>: 73<path>/etc/fstab</path>:
70</p> 74</p>
71 75
72<pre caption="Opening /etc/fstab"> 76<pre caption="Opening /etc/fstab">
73# <i>nano -w /etc/fstab</i> 77# <i>nano -w /etc/fstab</i>
74</pre> 78</pre>
75 79
76<p> 80<p>
77Let 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>
78partition. 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
79<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.
80</p> 85</p>
81 86
82<p> 87<p>
83In our default x86 partitioning example <path>/boot</path> is the 88In our default x86 partitioning example <path>/boot</path> is the
84<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 89<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
122(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
123partitions or drives, for those too): 128partitions or drives, for those too):
124</p> 129</p>
125 130
126<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example">
127/dev/hda1 /boot ext2 noauto,noatime 1 2 132/dev/hda1 /boot ext2 defaults,noatime 1 2
128/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
129/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
130 135
131none /proc proc defaults 0 0 136none /proc proc defaults 0 0
132none /dev/shm tmpfs nodev,nosuid,noexec 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
147too: 152too:
148</p> 153</p>
149 154
150<pre caption="Adding openprom filesystem to /etc/fstab"> 155<pre caption="Adding openprom filesystem to /etc/fstab">
151none /proc/openprom openpromfs defaults 0 0 156none /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> 157</pre>
161 158
162<p> 159<p>
163Double-check your <path>/etc/fstab</path>, save and quit to continue. 160Double-check your <path>/etc/fstab</path>, save and quit to continue.
164</p> 161</p>
183<p> 180<p>
184We 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:
185</p> 182</p>
186 183
187<pre caption="Setting the hostname"> 184<pre caption="Setting the hostname">
188# <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>"
189</pre> 189</pre>
190 190
191<p> 191<p>
192Second we set the domainname: 192Second we set the domainname:
193</p> 193</p>
194 194
195<pre caption="Setting the domainname"> 195<pre caption="Setting the domainname">
196# <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>"
197</pre> 200</pre>
198 201
199<p> 202<p>
200If 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
201one), you need to define that one too: 204one), you need to define that one too:
202</p> 205</p>
203 206
204<pre caption="Setting the NIS domainname"> 207<pre caption="Setting the NIS domainname">
205# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 208# <i>nano -w /etc/conf.d/domainname</i>
206</pre>
207 209
208<p> 210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
209Now add the <c>domainname</c> script to the default runlevel: 211NISDOMAIN="<i>my-nisdomain</i>"
210</p>
211
212<pre caption="Adding domainname to the default runlevel">
213# <i>rc-update add domainname default</i>
214</pre> 212</pre>
215 213
216</body> 214</body>
217</subsection> 215</subsection>
218<subsection> 216<subsection>
219<title>Configuring your Network</title> 217<title>Configuring your Network</title>
220<body> 218<body>
221 219
222<p> 220<p>
223Before 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
224that 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
225just 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
226your Gentoo system permanently. 224your Gentoo system permanently.
227</p> 225</p>
228 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
229<p> 233<p>
230All 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
231a straightforward yet not intuitive syntax if you don't know how to set up 235a straightforward yet not intuitive syntax if you don't know how to set up
232networking manually. But don't fear, we'll explain everything :) 236networking manually. But don't fear, we'll explain everything. A fully
233</p> 237commented example that covers many different configurations is available in
234 238<path>/etc/conf.d/net.example</path>.
235<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
236First 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
237is used in this example): 249this example):
238</p> 250</p>
239 251
240<pre caption="Opening /etc/conf.d/net for editing"> 252<pre caption="Opening /etc/conf.d/net for editing">
241# <i>nano -w /etc/conf.d/net</i> 253# <i>nano -w /etc/conf.d/net</i>
242</pre> 254</pre>
243 255
244<p> 256<p>
245The first variable you'll find is <c>iface_eth0</c>. It uses the following 257You will see the following file:
246syntax:
247</p>
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> 258</p>
254If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 259
255to <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">
256If you need to set up your network manually and you're 261# This blank configuration will automatically use DHCP for any net.*
257not familiar with all the above terms, please read the section on <uri 262# scripts in /etc/init.d. To create a more complete configuration,
258link="?part=1&amp;chap=3#network_term">Understanding Network 263# please review /etc/conf.d/net.example and save your configuration
259Terminology</uri> if you haven't done so already. 264# in /etc/conf.d/net (this file :]!).
265</pre>
266
260</p> 267<p>
261 268To enter your own IP address, netmask and gateway, you need
269to set both <c>config_eth0</c> and <c>routes_eth0</c>:
262<p> 270</p>
263So let us give three examples; the first one uses DHCP, the second one a static 271
264IP (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">
265gateway 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" )
266rp-pppoe usage: 274routes_eth0=( "default gw 192.168.0.1" )
275</pre>
276
267</p> 277<p>
268 278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
269<pre caption="Examples for /etc/conf.d/net"> 279<c>dhcp_eth0</c>:
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> 280</p>
290If you have several network interfaces, create extra <c>iface_eth</c> variables, 281
291like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282<pre caption="Automatically obtaining an IP address for eth0">
292shouldn'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.
293</p> 295</p>
294 296
295<p> 297<p>
296Now save the configuration and exit to continue. 298Now save the configuration and exit to continue.
297</p> 299</p>
330<title>Writing Down Network Information</title> 332<title>Writing Down Network Information</title>
331<body> 333<body>
332 334
333<p> 335<p>
334You now need to inform Linux about your network. This is defined in 336You now need to inform Linux about your network. This is defined in
335<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 337<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for
336for hosts that aren't resolved by your nameserver. For instance, if your 338hosts that aren't resolved by your nameserver. You need to define your system.
337internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 339You may also want to define other systems on your network if you don't want to
338<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 340set up your own internal DNS system.
339open <path>/etc/hosts</path> and fill in the values:
340</p> 341</p>
341 342
342<pre caption="Opening /etc/hosts"> 343<pre caption="Opening /etc/hosts">
343# <i>nano -w /etc/hosts</i> 344# <i>nano -w /etc/hosts</i>
344</pre> 345</pre>
345 346
346<pre caption="Filling in the networking information"> 347<pre caption="Filling in the networking information">
347127.0.0.1 localhost 348<comment>(This defines the current system)</comment>
349127.0.0.1 tux.homenetwork tux localhost
350
351<comment>(Define extra systems on your network,
352they need to have a static IP to be defined this way.)</comment>
348192.168.0.5 jenny.homenetwork jenny 353192.168.0.5 jenny.homenetwork jenny
349192.168.0.6 benny.homenetwork benny 354192.168.0.6 benny.homenetwork benny
350192.168.0.7 tux.homenetwork tux
351</pre>
352
353<p>
354If 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
356system <c>tux.homenetwork</c>:
357</p>
358
359<pre caption="/etc/hosts for lonely or fully integrated PCs">
360127.0.0.1 tux.homenetwork tux localhost
361</pre> 355</pre>
362 356
363<p> 357<p>
364Save and exit the editor to continue. 358Save and exit the editor to continue.
365</p> 359</p>
440<pre caption="Opening /etc/rc.conf"> 434<pre caption="Opening /etc/rc.conf">
441# <i>nano -w /etc/rc.conf</i> 435# <i>nano -w /etc/rc.conf</i>
442</pre> 436</pre>
443 437
444<p> 438<p>
439When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
440</p>
441
442<p>
445As you can see, this file is well commented to help you set up the necessary 443As you can see, this file is well commented to help you set up the necessary
446configuration variables. Take special care with the <c>KEYMAP</c> setting: if 444configuration variables. You can configure your system to use unicode and
447you select the wrong <c>KEYMAP</c> you will get weird results when typing on 445define your default editor and your display manager (like gdm or kdm).
448your keyboard. 446</p>
447
448<p>
449Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
450Edit it to configure your keyboard.
451</p>
452
453<pre caption="Opening /etc/conf.d/keymaps">
454# <i>nano -w /etc/conf.d/keymaps</i>
455</pre>
456
457<p>
458Take special care with the <c>KEYMAP</c> variable. If you select the wrong
459<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
449</p> 460</p>
450 461
451<note> 462<note>
452Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 463Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
453select an i386 keymap (such as "us") instead of "sunkeymap". 464select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
465keymaps on most systems. Users who want to be able to use ADB keymaps on boot
466have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
467keymap in <path>/etc/conf.d/keymaps</path>.
454</note> 468</note>
455 469
456<p> 470<p>
457<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 471When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
458ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 472exit.
459to set a mac/ppc keymap in <path>rc.conf</path>.
460</p>
461
462<p> 473</p>
474
475<p>
476Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
477according to your needs.
478</p>
479
480<pre caption="Opening /etc/conf.d/clock">
481# <i>nano -w /etc/conf.d/clock</i>
482</pre>
483
484<p>
485If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
486the file. Otherwise you will notice some clock skew. Furthermore, Windows
487assumes that your hardware clock uses local time, so if you want to dualboot,
488you should set this variable appropriately, otherwise your clock will go crazy.
489</p>
490
491<p>
463When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 492When you're finished configuring <path>/etc/conf.d/clock</path>, save and
493exit.
494</p>
495
496<p>
497If you are not installing Gentoo on IBM PPC64 hardware, continue with
498<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>.
499</p>
500
501</body>
502</subsection>
503<subsection>
504<title>Configuring the Console</title>
505<body>
506
507<note>
508The following section applies to the IBM PPC64 hardware platforms.
509</note>
510
511<p>
512If you are running Gentoo on IBM PPC64 hardware and using a virtual console
513you must uncomment the appropriate line in <path>/etc/inittab</path> for the
514virtual console to spawn a login prompt.
515</p>
516
517<pre caption="Enabling hvc or hvsi support in /etc/inittab">
518hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
519hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
520</pre>
521
522<p>
523You should also take this time to verify that the appropriate console is
524listed in <path>/etc/securetty</path>.
525</p>
526
527<p>
464continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 528You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
465Tools</uri>. 529System Tools</uri>.
466</p> 530</p>
467 531
468</body> 532</body>
469</subsection> 533</subsection>
470</section> 534</section>

Legend:
Removed from v.1.49  
changed lines
  Added in v.1.78

  ViewVC Help
Powered by ViewVC 1.1.20