/[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.59 Revision 1.88
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.59 2005/04/21 13:27:19 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.88 2006/11/28 07:40:38 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<abstract>
12You need to edit some important configuration files. In this chapter
13you receive an overview of these files and an explanation on how to
14proceed.
15</abstract>
16
11<version>2.2</version> 17<version>7.6</version>
12<date>2005-04-20</date> 18<date>2006-11-27</date>
13 19
14<section> 20<section>
15<title>Filesystem Information</title> 21<title>Filesystem Information</title>
16<subsection> 22<subsection>
17<title>What is fstab?</title> 23<title>What is fstab?</title>
18<body> 24<body>
19 25
20<p> 26<p>
21Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 28<path>/etc/fstab</path>. This file contains the mount points of those partitions
23(where they are seen in the file system structure), how they should be mounted 29(where they are seen in the file system structure), how they should be mounted
24and with what special options (automatically or not, whether users can mount 30and with what special options (automatically or not, whether users can mount
25them or not, etc.) 31them or not, etc.)
26</p> 32</p>
27 33
41<li> 47<li>
42 The first field shows the <b>partition</b> described (the path to the device 48 The first field shows the <b>partition</b> described (the path to the device
43 file) 49 file)
44</li> 50</li>
45<li> 51<li>
46 The second field shows the <b>mountpoint</b> at which the partition should be 52 The second field shows the <b>mount point</b> at which the partition should be
47 mounted 53 mounted
48</li> 54</li>
49<li> 55<li>
50 The third field shows the <b>filesystem</b> used by the partition 56 The third field shows the <b>filesystem</b> used by the partition
51</li> 57</li>
52<li> 58<li>
53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 59 The fourth field shows the <b>mount options</b> used by <c>mount</c> when it
54 wants to mount the partition. As every filesystem has its own mountoptions, 60 wants to mount the partition. As every filesystem has its own mount options,
55 you are encouraged to read the mount man page (<c>man mount</c>) for a full 61 you are encouraged to read the mount man page (<c>man mount</c>) for a full
56 listing. Multiple mountoptions are comma-separated. 62 listing. Multiple mount options are comma-separated.
57</li> 63</li>
58<li> 64<li>
59 The fifth field is used by <c>dump</c> to determine if the partition needs to 65 The fifth field is used by <c>dump</c> to determine if the partition needs to
60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 66 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
61</li> 67</li>
65 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 71 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
66 (or <c>0</c> if a filesystem check isn't necessary). 72 (or <c>0</c> if a filesystem check isn't necessary).
67</li> 73</li>
68</ul> 74</ul>
69 75
70<p> 76<impo>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab 77The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72file</e>, so start <c>nano</c> (or your favorite editor) to create your 78fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>.
73<path>/etc/fstab</path>: 79</impo>
74</p>
75 80
76<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
77# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
78</pre> 83</pre>
79 84
85</body>
86<body test="func:keyval('/boot')">
87
80<p> 88<p>
81Let us take a look at how we write down the options for the <path>/boot</path> 89Let us take a look at how we write down the options for the <path>/boot</path>
82partition. This is just an example, so if your architecture doesn't require a 90partition. This is just an example, if you didn't or couldn't create a
83<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. 91<path>/boot</path>, don't copy it.
84</p>
85
86<p> 92</p>
93
94<p test="contains(func:keyval('/boot'), '/dev/hd')">
87In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
88<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 96usually the <path><keyval id="/boot"/></path> partition (or
97<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
89It needs to be checked during boot, so we would write down: 98filesystem. It needs to be checked during boot, so we would write down:
99</p>
100
101<p test="contains(func:keyval('/boot'), '/dev/sd')">
102In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
103usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
104filesystem. It needs to be checked during boot, so we would write down:
90</p> 105</p>
91 106
92<pre caption="An example /boot line for /etc/fstab"> 107<pre caption="An example /boot line for /etc/fstab">
93/dev/hda1 /boot ext2 defaults 1 2 108<keyval id="/boot"/> /boot ext2 defaults 1 2
94</pre> 109</pre>
95 110
96<p> 111<p>
97Some users don't want their <path>/boot</path> partition to be mounted 112Some users don't want their <path>/boot</path> partition to be mounted
98automatically to improve their system's security. Those people should 113automatically to improve their system's security. Those people should
99substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 114substitute <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. 115manually mount this partition every time you want to use it.
101</p> 116</p>
102 117
118</body>
119<body>
120
121<p test="not(func:keyval('arch')='SPARC')">
122Add the rules that match your partitioning scheme and append rules for
123<path>/proc</path>, <c>tmpfs</c>, for your CD-ROM drive(s), and of course, if
124you have other partitions or drives, for those too.
103<p> 125</p>
104Now, to improve performance, most users would want to add the <c>noatime</c>
105option as mountoption, which results in a faster system since access times
106aren't registered (you don't need those generally anyway):
107</p>
108 126
109<pre caption="An improved /boot line for /etc/fstab"> 127<p test="func:keyval('arch')='SPARC'">
110/dev/hda1 /boot ext2 defaults,noatime 1 2 128Add the rules that match your partitioning schema and append rules for
111</pre> 129<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
112 130drive(s), and of course, if you have other partitions or drives, for those too.
113<p> 131</p>
114If we continue with this, we would end up with the following three lines (for 132
115<path>/boot</path>, <path>/</path> and the swap partition):
116</p> 133<p>
117 134Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
118<pre caption="Three /etc/fstab lines">
119/dev/hda1 /boot ext2 defaults,noatime 1 2
120/dev/hda2 none swap sw 0 0
121/dev/hda3 / ext3 noatime 0 1
122</pre>
123
124<p> 135</p>
125To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
126(required) and for your CD-ROM drive (and of course, if you have other
127partitions or drives, for those too):
128</p>
129 136
130<pre caption="A full /etc/fstab example"> 137<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
131/dev/hda1 /boot ext2 defaults,noatime 1 2 138<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132/dev/hda2 none swap sw 0 0 139/dev/hda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 140/dev/hda3 / ext3 noatime 0 1
134 141
135none /proc proc defaults 0 0 142proc /proc proc defaults 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 143shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
137 144
145/dev/cdrom /mnt/cdrom auto noauto,user 0 0
146</pre>
147
148<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
149<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
150/dev/sda3 none swap sw 0 0
151/dev/sda4 / ext3 noatime 0 1
152
153proc /proc proc defaults 0 0
154shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
155
156/dev/cdrom /mnt/cdrom auto noauto,user 0 0
157</pre>
158
159<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'">
160<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
161/dev/sda2 none swap sw 0 0
162/dev/sda3 / ext3 noatime 0 1
163
164proc /proc proc defaults 0 0
165shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
166
167/dev/cdrom /mnt/cdrom auto noauto,user 0 0
168</pre>
169
170<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
171/dev/sda1 / ext3 noatime 0 1
172/dev/sda2 none swap sw 0 0
173/dev/sda4 /usr ext3 noatime 0 2
174/dev/sda5 /var ext3 noatime 0 2
175/dev/sda6 /home ext3 noatime 0 2
176
177openprom /proc/openprom openpromfs defaults 0 0
178proc /proc proc defaults 0 0
179shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
180
138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 181/dev/cdrom /mnt/cdrom auto noauto,user 0 0
182</pre>
183
184<note test="func:keyval('arch')='PPC'">
185There are important variations between PPC machine types. Please make sure you
186adapt the following example to your system.
187</note>
188
189<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'">
190/dev/hda4 / ext3 noatime 0 1
191/dev/hda3 none swap sw 0 0
192
193proc /proc proc defaults 0 0
194shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
195
196/dev/cdrom /mnt/cdrom auto noauto,user 0 0
197</pre>
198
199<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'">
200/dev/sda4 / ext3 noatime 0 1
201/dev/sda3 none swap sw 0 0
202
203proc /proc proc defaults 0 0
204shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
205
206/dev/cdrom /mnt/cdrom auto noauto,user 0 0
139</pre> 207</pre>
140 208
141<p> 209<p>
142<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 210<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
143removable media as they can be created with one of many filesystems) and 211removable media as they can be created with one of many filesystems) and
144<c>user</c> makes it possible for non-root users to mount the CD. 212<c>user</c> makes it possible for non-root users to mount the CD.
145</p> 213</p>
146 214
147<p> 215<p>
148Now use the above example to create your <path>/etc/fstab</path>. If you are a 216To improve performance, most users would want to add the <c>noatime</c>
149<b>SPARC</b>-user, you should add the following line to your 217mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 218aren't registered (you don't need those generally anyway).
151too:
152</p>
153
154<pre caption="Adding openprom filesystem to /etc/fstab">
155none /proc/openprom openpromfs defaults 0 0
156</pre> 219</p>
157 220
158<p> 221<p>
159Double-check your <path>/etc/fstab</path>, save and quit to continue. 222Double-check your <path>/etc/fstab</path>, save and quit to continue.
160</p> 223</p>
161 224
163</subsection> 226</subsection>
164</section> 227</section>
165<section> 228<section>
166<title>Networking Information</title> 229<title>Networking Information</title>
167<subsection> 230<subsection>
168<title>Hostname, Domainname etc.</title> 231<title>Host name, Domainname, etc</title>
169<body> 232<body>
170 233
171<p> 234<p>
172One of the choices the user has to make is name his/her PC. This seems to be 235One of the choices the user has to make is name his/her PC. This seems to be
173quite easy, but <e>lots</e> of users are having difficulties finding the 236quite easy, but <e>lots</e> of users are having difficulties finding the
174appropriate name for their Linux-pc. To speed things up, know that any name you 237appropriate name for their Linux-pc. To speed things up, know that any name you
175choose can be changed afterwards. For all we care, you can just call your system 238choose can be changed afterwards. For all we care, you can just call your system
176<c>tux</c> and domain <c>homenetwork</c>. 239<c>tux</c> and domain <c>homenetwork</c>.
177</p> 240</p>
178 241
179<p>
180We use these values in the next examples. First we set the hostname:
181</p>
182
183<pre caption="Setting the hostname"> 242<pre caption="Setting the host name">
184# <i>echo tux &gt; /etc/hostname</i> 243# <i>nano -w /etc/conf.d/hostname</i>
185</pre>
186 244
245<comment>(Set the HOSTNAME variable to your host name)</comment>
246HOSTNAME="<i>tux</i>"
247</pre>
248
187<p> 249<p>
188Second we set the domainname: 250Second we set the domainname in <path>/etc/conf.d/net</path>:
189</p> 251</p>
190 252
191<pre caption="Setting the domainname"> 253<pre caption="Setting the domainname">
192# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 254# <i>nano -w /etc/conf.d/net</i>
255
256<comment>(Set the dns_domain variable to your domain name)</comment>
257dns_domain_lo="<i>homenetwork</i>"
193</pre> 258</pre>
194 259
195<p> 260<p>
196If you have a NIS domain (if you don't know what that is, then you don't have 261If you have a NIS domain (if you don't know what that is, then you don't have
197one), you need to define that one too: 262one), you need to define that one too:
198</p> 263</p>
199 264
200<pre caption="Setting the NIS domainname"> 265<pre caption="Setting the NIS domainname">
201# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 266# <i>nano -w /etc/conf.d/net</i>
202</pre>
203 267
204<p> 268<comment>(Set the nis_domain variable to your NIS domain name)</comment>
205Now add the <c>domainname</c> script to the default runlevel: 269nis_domain_lo="<i>my-nisdomain</i>"
206</p> 270</pre>
207 271
208<pre caption="Adding domainname to the default runlevel"> 272<note>
209# <i>rc-update add domainname default</i> 273For more information on configuring DNS and NIS, please read the examples
210</pre> 274provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
275<c>resolvconf-gentoo</c> to help manage your DNS/NIS setup.
276</note>
211 277
212</body> 278</body>
213</subsection> 279</subsection>
214<subsection> 280<subsection>
215<title>Configuring your Network</title> 281<title>Configuring your Network</title>
216<body> 282<body>
217 283
218<p> 284<p>
219Before you get that "Hey, we've had that already"-feeling, you should remember 285Before you get that "Hey, we've had that already"-feeling, you should remember
220that the networking you set up in the beginning of the gentoo installation was 286that the networking you set up in the beginning of the Gentoo installation was
221just for the installation. Right now you are going to configure networking for 287just for the installation. Right now you are going to configure networking for
222your Gentoo system permanently. 288your Gentoo system permanently.
223</p> 289</p>
224 290
291<note>
292More detailed information about networking, including advanced topics like
293bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
294link="?part=4">Gentoo Network Configuration</uri> section.
295</note>
296
225<p> 297<p>
226All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 298All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
227a straightforward yet not intuitive syntax if you don't know how to set up 299a straightforward yet not intuitive syntax if you don't know how to set up
228networking manually. But don't fear, we'll explain everything :) 300networking manually. But don't fear, we'll explain everything. A fully
229</p> 301commented example that covers many different configurations is available in
230 302<path>/etc/conf.d/net.example</path>.
231<p> 303</p>
304
305<p>
306DHCP is used by default. For DHCP to work, you will need to install a DHCP
307client. This is described later in <uri
308link="?part=1&amp;chap=9#networking-tools">Installing Necessary System
309Tools</uri>. Do not forget to install a DHCP client.
310</p>
311
312<p>
313If you need to configure your network connection either because you need
314specific DHCP options or because you do not use DHCP at all, open
232First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 315<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233is used in this example): 316this example):
234</p> 317</p>
235 318
236<pre caption="Opening /etc/conf.d/net for editing"> 319<pre caption="Opening /etc/conf.d/net for editing">
237# <i>nano -w /etc/conf.d/net</i> 320# <i>nano -w /etc/conf.d/net</i>
238</pre> 321</pre>
239 322
240<!-- Old baselayout - current stable -->
241
242<p>
243The first variable you'll find is <c>iface_eth0</c>. It uses the following
244syntax:
245</p> 323<p>
246 324You will see the following file:
247<pre caption="iface_eth0 syntaxis">
248iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
249</pre>
250
251<p> 325</p>
252If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 326
253to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 327<pre caption="Default /etc/conf.d/net">
254If you need to set up your network manually and you're 328# This blank configuration will automatically use DHCP for any net.*
255not familiar with all the above terms, please read the section on <uri 329# scripts in /etc/init.d. To create a more complete configuration,
256link="?part=1&amp;chap=3#network_term">Understanding Network 330# please review /etc/conf.d/net.example and save your configuration
257Terminology</uri> if you haven't done so already. 331# in /etc/conf.d/net (this file :]!).
332</pre>
333
258</p> 334<p>
259 335To enter your own IP address, netmask and gateway, you need
336to set both <c>config_eth0</c> and <c>routes_eth0</c>:
260<p> 337</p>
261So let us give three examples; the first one uses DHCP, the second one a static 338
262IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 339<pre caption="Manually setting IP information for eth0">
263gateway 192.168.0.1 while the third one just activates the interface for 340config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
264rp-pppoe usage: 341routes_eth0=( "default gw 192.168.0.1" )
342</pre>
343
265</p> 344<p>
266 345To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
267<pre caption="Examples for /etc/conf.d/net"> 346<c>dhcp_eth0</c>:
268<comment>(For DHCP)</comment>
269iface_eth0="dhcp"
270<comment># Some network admins require that you use the</comment>
271<comment># hostname and domainname provided by the DHCP server.</comment>
272<comment># In that case, add the following to let dhcpcd use them.</comment>
273<comment># That will override your own hostname and domainname definitions.</comment>
274dhcpcd_eth0="-HD"
275<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
276<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
277dhcpcd_eth0="-N"
278
279<comment>(For static IP)</comment>
280iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
281gateway="eth0/192.168.0.1"
282
283<comment>(For rp-pppoe)</comment>
284iface_eth0="up"
285</pre>
286
287<p> 347</p>
288If you have several network interfaces, create extra <c>iface_eth</c> variables,
289like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
290shouldn't be reproduced as you can only set one gateway per computer.
291</p>
292 348
293<!-- New baselayout - current testing
294
295<p>
296The first variable you'll find is called <c>config_eth0</c>. As you can probably
297imagine, this variable configured the eth0 network interface. If the interface
298needs to automatically obtain an IP through DHCP, you should set it like so:
299</p>
300
301<pre caption="Automatically obtaining an IP for eth0"> 349<pre caption="Automatically obtaining an IP address for eth0">
302config_eth0=( "dhcp" ) 350config_eth0=( "dhcp" )
351dhcp_eth0="nodns nontp nonis"
303</pre> 352</pre>
304 353
305<p>
306However, if you have to enter your own IP address, netmask and gateway, you need
307to set both <c>config_eth0</c> and <c>routes_eth0</c>:
308</p> 354<p>
309 355Please read <path>/etc/conf.d/net.example</path> for a list of all available
310<pre caption="Manually setting IP information for eth0"> 356options.
311config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
312routes_eth0=( "default gw 192.168.0.1" )
313</pre> 357</p>
314 358
315<p> 359<p>
316If you have several network interfaces repeat the above steps for 360If you have several network interfaces repeat the above steps for
317<c>config_eth1</c>, <c>config_eth2</c>, etc. 361<c>config_eth1</c>, <c>config_eth2</c>, etc.
318</p> 362</p>
319
320-->
321 363
322<p> 364<p>
323Now save the configuration and exit to continue. 365Now save the configuration and exit to continue.
324</p> 366</p>
325 367
345use <c>ln</c> to do this: 387use <c>ln</c> to do this:
346</p> 388</p>
347 389
348<pre caption="Creating extra initscripts"> 390<pre caption="Creating extra initscripts">
349# <i>cd /etc/init.d</i> 391# <i>cd /etc/init.d</i>
350# <i>ln -s net.eth0 net.eth1</i> 392# <i>ln -s net.lo net.eth1</i>
351# <i>rc-update add net.eth1 default</i> 393# <i>rc-update add net.eth1 default</i>
352</pre> 394</pre>
353 395
354</body> 396</body>
355</subsection> 397</subsection>
357<title>Writing Down Network Information</title> 399<title>Writing Down Network Information</title>
358<body> 400<body>
359 401
360<p> 402<p>
361You now need to inform Linux about your network. This is defined in 403You now need to inform Linux about your network. This is defined in
362<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 404<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
363for hosts that aren't resolved by your nameserver. For instance, if your 405hosts that aren't resolved by your nameserver. You need to define your system.
364internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 406You may also want to define other systems on your network if you don't want to
365<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 407set up your own internal DNS system.
366open <path>/etc/hosts</path> and fill in the values:
367</p> 408</p>
368 409
369<pre caption="Opening /etc/hosts"> 410<pre caption="Opening /etc/hosts">
370# <i>nano -w /etc/hosts</i> 411# <i>nano -w /etc/hosts</i>
371</pre> 412</pre>
372 413
373<pre caption="Filling in the networking information"> 414<pre caption="Filling in the networking information">
374127.0.0.1 localhost 415<comment>(This defines the current system)</comment>
416127.0.0.1 tux.homenetwork tux localhost
417
418<comment>(Define extra systems on your network,
419they need to have a static IP to be defined this way.)</comment>
375192.168.0.5 jenny.homenetwork jenny 420192.168.0.5 jenny.homenetwork jenny
376192.168.0.6 benny.homenetwork benny 421192.168.0.6 benny.homenetwork benny
377192.168.0.7 tux.homenetwork tux
378</pre>
379
380<p>
381If your system is the only system (or the nameservers handle all name
382resolution) a single line is sufficient. For instance, if you want to call your
383system <c>tux</c>:
384</p>
385
386<pre caption="/etc/hosts for lonely or fully integrated PCs">
387127.0.0.1 localhost tux
388</pre> 422</pre>
389 423
390<p> 424<p>
391Save and exit the editor to continue. 425Save and exit the editor to continue.
392</p> 426</p>
393 427
394<p> 428<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
395If you don't have PCMCIA, you can now continue with <uri 429If you don't have PCMCIA, you can now continue with <uri
396link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 430link="#sysinfo">System Information</uri>. PCMCIA-users should read the
397following topic on PCMCIA. 431following topic on PCMCIA.
398</p> 432</p>
399 433
400</body> 434</body>
401</subsection> 435</subsection>
402<subsection> 436<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
403<title>Optional: Get PCMCIA Working</title> 437<title>Optional: Get PCMCIA Working</title>
404<body> 438<body>
405
406<note>
407pcmcia-cs is only available for x86, amd64 and ppc platforms.
408</note>
409 439
410<p> 440<p>
411PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 441PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
412includes users who will be working with a 2.6 kernel (even though they won't be 442includes users who will be working with a 2.6 kernel (even though they won't be
413using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary 443using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
428</pre> 458</pre>
429 459
430</body> 460</body>
431</subsection> 461</subsection>
432</section> 462</section>
433<section> 463
464<section id="sysinfo">
434<title>System Information</title> 465<title>System Information</title>
435<subsection> 466<subsection>
436<title>Root Password</title> 467<title>Root Password</title>
437<body> 468<body>
438 469
467<pre caption="Opening /etc/rc.conf"> 498<pre caption="Opening /etc/rc.conf">
468# <i>nano -w /etc/rc.conf</i> 499# <i>nano -w /etc/rc.conf</i>
469</pre> 500</pre>
470 501
471<p> 502<p>
503When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
504</p>
505
506<p>
472As you can see, this file is well commented to help you set up the necessary 507As you can see, this file is well commented to help you set up the necessary
473configuration variables. Take special care with the <c>KEYMAP</c> setting: if 508configuration variables. You can configure your system to use unicode and
474you select the wrong <c>KEYMAP</c> you will get weird results when typing on 509define your default editor and your display manager (like gdm or kdm).
475your keyboard. 510</p>
511
476</p> 512<p>
513Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
514Edit it to configure your keyboard.
515</p>
477 516
478<note> 517<pre caption="Opening /etc/conf.d/keymaps">
518# <i>nano -w /etc/conf.d/keymaps</i>
519</pre>
520
521<p>
522Take special care with the <c>KEYMAP</c> variable. If you select the wrong
523<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
524</p>
525
526<note test="func:keyval('arch')='SPARC'">
479Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 527Users of USB-based SPARC systems and SPARC clones might need to select an i386
480select an i386 keymap (such as "us") instead of "sunkeymap". 528keymap (such as "us") instead of "sunkeymap".
481</note> 529</note>
482 530
483<p> 531<note test="substring(func:keyval('arch'),1,3)='PPC'">
484<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 532PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
485ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 533keymaps on boot have to enable ADB keycode sendings in their kernel and have to
486to set a mac/ppc keymap in <path>rc.conf</path>. 534set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
535</note>
536
487</p> 537<p>
488 538When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
539exit.
489<p> 540</p>
541
542<p>
543Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
544according to your needs.
545</p>
546
547<pre caption="Opening /etc/conf.d/clock">
548# <i>nano -w /etc/conf.d/clock</i>
549</pre>
550
551<p>
552If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
553to the file. Otherwise you will notice some clock skew.
554</p>
555
556<p>
490When you're finished configuring <path>/etc/rc.conf</path>, save and exit. 557When you're finished configuring <path>/etc/conf.d/clock</path>, save and
491</p> 558exit.
492
493<p> 559</p>
494If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with 560
561<p test="not(func:keyval('arch')='PPC64')">
495<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>. 562Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
563Tools</uri>.
496</p> 564</p>
497 565
498</body> 566</body>
499</subsection>
500<subsection> 567</subsection>
568<subsection test="func:keyval('arch')='PPC64'">
501<title>Configuring the Console</title> 569<title>Configuring the Console</title>
502<body> 570<body>
503 571
504<note>
505The following section applies to the IBM POWER5 and JS20 hardware platforms.
506</note>
507
508<p>
509If you are running gentoo in an LPAR or on a JS20 blade, you must uncomment
510the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
511</p> 572<p>
573If you are using a virtual console, you must uncomment the appropriate line in
574<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
575</p>
512 576
513<pre caption="Enabling hvc support in /etc/inittab"> 577<pre caption="Enabling hvc or hvsi support in /etc/inittab">
514hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220 578hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
579hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
580</pre>
581
582<p>
583You should also take this time to verify that the appropriate console is
584listed in <path>/etc/securetty</path>.
515</pre> 585</p>
516 586
517<p> 587<p>
518You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary 588You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
519System Tools</uri>. 589System Tools</uri>.
520</p> 590</p>

Legend:
Removed from v.1.59  
changed lines
  Added in v.1.88

  ViewVC Help
Powered by ViewVC 1.1.20