/[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.13 Revision 1.78
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/2.5 -->
3 6
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.13 2003/12/07 12:15:17 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 $ -->
5 8
6<sections> 9<sections>
7<section>
8<title>Timezone</title>
9<body>
10 10
11<p> 11<version>2.19</version>
12You now need to select your timezone so that your system knows where it is 12<date>2006-05-27</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>
42<title>Creating /etc/fstab</title> 31<title>Creating /etc/fstab</title>
43<body> 32<body>
44 33
45<p> 34<p>
46<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six 35<path>/etc/fstab</path> uses a special syntax. Every line consists of six
47fields, separated by whitespace (space(s), tabs or a mixture). Each field has 36fields, separated by whitespace (space(s), tabs or a mixture). Each field has
48its own meaning: 37its own meaning:
49</p> 38</p>
50 39
51<ul> 40<ul>
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> the order in which filesystems should 63 The sixth field is used by <c>fsck</c> to determine the order in which
75 be <b>check</b>ed if the system wasn't shut down properly. The root filesystem 64 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
76 should have <c>1</c> while the rest should have <c>2</c> (or <c>0</c> in case 65 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
77 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 not a valid
82So 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
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>
91Lets 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 Apple <b>PPC</b> machines), don't copy it
84verbatim.
94</p> 85</p>
95 86
96<p> 87<p>
97In our default x86 partitioning example <path>/boot</path> is the 88In 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 89<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 90It needs to be checked during boot, so we would write down:
100would write down:
101</p> 91</p>
102 92
103<pre caption="An example /boot line for /etc/fstab"> 93<pre caption="An example /boot line for /etc/fstab">
104/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.
105</pre> 102</p>
106 103
107<p> 104<p>
108Now, 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>
109option as mountoption, which results in a faster system since access times 106option as mountoption, which results in a faster system since access times
110aren't registered (you don't need those generally anyway): 107aren't registered (you don't need those generally anyway):
111</p> 108</p>
112 109
113<pre caption="An improved /boot line for /etc/fstab"> 110<pre caption="An improved /boot line for /etc/fstab">
114/dev/hda1 /boot ext2 noauto,noatime 1 2 111/dev/hda1 /boot ext2 defaults,noatime 1 2
115</pre> 112</pre>
116 113
117<p> 114<p>
118If 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
119<path>/boot</path>, <path>/</path> and the swap partition): 116<path>/boot</path>, <path>/</path> and the swap partition):
120</p> 117</p>
121 118
122<pre caption="Three /etc/fstab lines"> 119<pre caption="Three /etc/fstab lines">
123/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 defaults,noatime 1 2
124/dev/hda2 none swap sw 0 0 121/dev/hda2 none swap sw 0 0
125/dev/hda3 / ext3 noatime 0 1 122/dev/hda3 / ext3 noatime 0 1
126</pre> 123</pre>
127 124
128<p> 125<p>
130(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
131partitions or drives, for those too): 128partitions or drives, for those too):
132</p> 129</p>
133 130
134<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example">
135/dev/hda1 /boot ext2 noauto,noatime 1 2 132/dev/hda1 /boot ext2 defaults,noatime 1 2
136/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
137/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
138 135
139none /proc proc defaults 0 0 136none /proc proc defaults 0 0
140none /dev/shm tmpfs defaults 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
141 138
142/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
143</pre> 140</pre>
144 141
145<p> 142<p>
148<c>user</c> makes it possible for non-root users to mount the CD. 145<c>user</c> makes it possible for non-root users to mount the CD.
149</p> 146</p>
150 147
151<p> 148<p>
152Now use the above example to create your <path>/etc/fstab</path>. If you are a 149Now 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> 150<b>SPARC</b>-user, you should add the following line to your
151<path>/etc/fstab</path>
154too: 152too:
155</p> 153</p>
156 154
157<pre caption="Adding openprom filesystem to /etc/fstab"> 155<pre caption="Adding openprom filesystem to /etc/fstab">
158none /proc/openprom openpromfs defaults 0 0 156none /proc/openprom openpromfs defaults 0 0
159</pre> 157</pre>
160 158
161<p> 159<p>
162If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
163</p>
164
165<pre caption="Adding usbfs filesystem to /etc/fstab">
166none /proc/bus/usb usbfs defaults 0 0
167</pre>
168
169<p>
170Reread your <path>/etc/fstab</path>, save and quit to continue. 160Double-check your <path>/etc/fstab</path>, save and quit to continue.
171</p> 161</p>
172 162
173</body> 163</body>
174</subsection> 164</subsection>
175</section> 165</section>
178<subsection> 168<subsection>
179<title>Hostname, Domainname etc.</title> 169<title>Hostname, Domainname etc.</title>
180<body> 170<body>
181 171
182<p> 172<p>
183One of the choices the user has to make is name his PC. This seems to be quite 173One 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 174quite 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 175appropriate 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 176choose can be changed afterwards. For all we care, you can just call your system
187<c>tux</c> and domain <c>homenetwork</c>. 177<c>tux</c> and domain <c>homenetwork</c>.
188</p> 178</p>
189 179
190<p> 180<p>
191We 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:
192</p> 182</p>
193 183
194<pre caption="Setting the hostname"> 184<pre caption="Setting the hostname">
195# <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>"
196</pre> 189</pre>
197 190
198<p> 191<p>
199Second we set the domainname: 192Second we set the domainname:
200</p> 193</p>
201 194
202<pre caption="Setting the domainname"> 195<pre caption="Setting the domainname">
203# <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>"
204</pre> 200</pre>
205 201
206<p> 202<p>
207If 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
208one), you need to define that one too: 204one), you need to define that one too:
209</p> 205</p>
210 206
211<pre caption="Setting the NIS domainname"> 207<pre caption="Setting the NIS domainname">
212# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 208# <i>nano -w /etc/conf.d/domainname</i>
213</pre>
214 209
215<p> 210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
216Now add the <c>domainname</c> script to the default runlevel: 211NISDOMAIN="<i>my-nisdomain</i>"
217</p>
218
219<pre caption="Adding domainname to the default runlevel">
220# <i>rc-update add domainname default</i>
221</pre> 212</pre>
222 213
223</body> 214</body>
224</subsection> 215</subsection>
225<subsection> 216<subsection>
226<title>Configuring your Network</title> 217<title>Configuring your Network</title>
227<body> 218<body>
228 219
229<p> 220<p>
230Before 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
231that 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
232just 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
233your Gentoo system permanently. 224your Gentoo system permanently.
234</p> 225</p>
235 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
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. A fully
240</p> 237commented example that covers many different configurations is available in
241 238<path>/etc/conf.d/net.example</path>.
242<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
243First 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
244is used in this example): 249this example):
245</p> 250</p>
246 251
247<pre caption="Opening /etc/conf.d/net for editing"> 252<pre caption="Opening /etc/conf.d/net for editing">
248# <i>nano -w /etc/conf.d/net</i> 253# <i>nano -w /etc/conf.d/net</i>
249</pre> 254</pre>
250 255
251<p> 256<p>
252The first variable you'll find is <c>iface_eth0</c>. It uses the following 257You will see the following file:
253syntax:
254</p>
255
256<pre caption="iface_eth0 syntaxis">
257iface_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>
259
260<p> 258</p>
261If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 259
262to <c>dhcp</c>. However, if you need to setup your network manually and you're 260<pre caption="Default /etc/conf.d/net">
263not familiar with all the above terms, please read the section on <uri 261# This blank configuration will automatically use DHCP for any net.*
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 262# scripts in /etc/init.d. To create a more complete configuration,
265Terminology</uri> if you haven't done so already. 263# please review /etc/conf.d/net.example and save your configuration
264# in /etc/conf.d/net (this file :]!).
265</pre>
266
266</p> 267<p>
267 268To enter your own IP address, netmask and gateway, you need
269to set both <c>config_eth0</c> and <c>routes_eth0</c>:
268<p> 270</p>
269So lets give two examples; the first one uses DHCP, the second one a static IP 271
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 272<pre caption="Manually setting IP information for eth0">
271192.168.0.1: 273config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
274routes_eth0=( "default gw 192.168.0.1" )
275</pre>
276
272</p> 277<p>
273 278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
274<pre caption="Examples for /etc/conf.d/net"> 279<c>dhcp_eth0</c>:
275<comment>(For DHCP:)</comment>
276iface_eth0="dhcp"
277
278<comment>(For static IP:)</comment>
279iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
280gateway="eth0/192.168.0.1"
281</pre>
282
283<p> 280</p>
284If you have several network interfaces, create extra <c>iface_eth</c> variables, 281
285like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282<pre caption="Automatically obtaining an IP address for eth0">
286shouldn'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.
287</p> 295</p>
288 296
289<p> 297<p>
290Now save the configuration and exit to continue. 298Now save the configuration and exit to continue.
291</p> 299</p>
295<subsection> 303<subsection>
296<title>Automatically Start Networking at Boot</title> 304<title>Automatically Start Networking at Boot</title>
297<body> 305<body>
298 306
299<p> 307<p>
300To 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
301default 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
302the PCMCIA interfaces are started by the PCMCIA init script. 310the PCMCIA interfaces are started by the PCMCIA init script.
303</p> 311</p>
304 312
305<pre caption="Adding net.eth0 to the default runlevel"> 313<pre caption="Adding net.eth0 to the default runlevel">
324<title>Writing Down Network Information</title> 332<title>Writing Down Network Information</title>
325<body> 333<body>
326 334
327<p> 335<p>
328You 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
329<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
330for 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.
331internal 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
332<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 340set up your own internal DNS system.
333open <path>/etc/hosts</path> and fill in the values:
334</p> 341</p>
335 342
336<pre caption="Opening /etc/hosts"> 343<pre caption="Opening /etc/hosts">
337# <i>nano -w /etc/hosts</i> 344# <i>nano -w /etc/hosts</i>
338</pre> 345</pre>
339 346
340<pre caption="Filling in the networking information"> 347<pre caption="Filling in the networking information">
348<comment>(This defines the current system)</comment>
341127.0.0.1 tux.homenetwork localhost 349127.0.0.1 tux.homenetwork tux localhost
342192.168.0.5 jenny
343192.168.0.56 benny
344</pre>
345 350
346<p> 351<comment>(Define extra systems on your network,
347If your system is the only system (or the nameservers handle all name 352they need to have a static IP to be defined this way.)</comment>
348resolution) a single line is sufficient: 353192.168.0.5 jenny.homenetwork jenny
349</p> 354192.168.0.6 benny.homenetwork benny
350
351<pre caption="/etc/hosts for lonely or fully integrated PCs">
352127.0.0.1 localhost tux
353</pre> 355</pre>
354 356
355<p> 357<p>
356Save and exit the editor to continue. 358Save and exit the editor to continue.
357</p> 359</p>
358 360
359<p> 361<p>
360If you don't have PCMCIA, you can now continue with <uri 362If you don't have PCMCIA, you can now continue with <uri
361link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 363link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
362following topic on PCMCIA. 364following topic on PCMCIA.
363</p> 365</p>
364 366
365</body> 367</body>
366</subsection> 368</subsection>
367<subsection> 369<subsection>
368<title>Optional: Get PCMCIA Working</title> 370<title>Optional: Get PCMCIA Working</title>
369<body> 371<body>
370 372
373<note>
374pcmcia-cs is only available for x86, amd64 and ppc platforms.
375</note>
376
371<p> 377<p>
372PCMCIA-users should first install the <c>pcmcia-cs</c> package: 378PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
379includes users who will be working with a 2.6 kernel (even though they won't be
380using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
381to avoid installing xorg-x11 at this moment:
373</p> 382</p>
374 383
375<pre caption="Installing pcmcia-cs"> 384<pre caption="Installing pcmcia-cs">
376# <i>emerge --usepkg pcmcia-cs</i> 385# <i>USE="-X" emerge pcmcia-cs</i>
377</pre> 386</pre>
378 387
379<p> 388<p>
380When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 389When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
381runlevel: 390runlevel:
382</p> 391</p>
383 392
384<pre caption="Adding pcmcia to the boot runlevel"> 393<pre caption="Adding pcmcia to the default runlevel">
385# <i>rc-update add pcmcia boot</i> 394# <i>rc-update add pcmcia default</i>
386</pre> 395</pre>
387 396
388</body> 397</body>
389</subsection> 398</subsection>
390</section> 399</section>
391<section> 400<section>
392<title>System Information</title> 401<title>System Information</title>
402<subsection>
403<title>Root Password</title>
404<body>
405
406<p>
407First we set the root password by typing:
408</p>
409
410<pre caption="Setting the root password">
411# <i>passwd</i>
412</pre>
413
414<p>
415If you want root to be able to log on through the serial console, add
416<c>tts/0</c> to <path>/etc/securetty</path>:
417</p>
418
419<pre caption="Adding tts/0 to /etc/securetty">
420# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
421</pre>
422
423</body>
424</subsection>
425<subsection>
426<title>System Information</title>
393<body> 427<body>
394 428
395<p> 429<p>
396Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 430Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
397Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) 431Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
400<pre caption="Opening /etc/rc.conf"> 434<pre caption="Opening /etc/rc.conf">
401# <i>nano -w /etc/rc.conf</i> 435# <i>nano -w /etc/rc.conf</i>
402</pre> 436</pre>
403 437
404<p> 438<p>
439When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
440</p>
441
442<p>
405As 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
406configuration variables. When you're finished configuring 444configuration variables. You can configure your system to use unicode and
407<path>/etc/rc.conf</path>, save and exit to continue. 445define your default editor and your display manager (like gdm or kdm).
446</p>
447
408</p> 448<p>
449Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
450Edit it to configure your keyboard.
451</p>
409 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.
460</p>
461
462<note>
463Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
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>.
468</note>
469
470<p>
471When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
472exit.
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>
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>
410</body> 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>
528You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
529System Tools</uri>.
530</p>
531
532</body>
533</subsection>
411</section> 534</section>
412</sections> 535</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20