/[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.3 Revision 1.72
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.72 2005/08/15 09:00:27 swift Exp $ -->
8
1<sections> 9<sections>
2<section>
3<title>Timezone</title>
4<body>
5 10
6<p> 11<version>2.13</version>
7You now need to select your timezone so that your system knows where it is 12<date>2005-08-15</date>
8located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
9symlink to <path>/etc/localtime</path> using <c>ln</c>:
10</p>
11 13
12<pre caption="Setting the timezone information">
13# <i>ls /usr/share/zoneinfo</i>
14<comment>(Suppose you want to use GTM:)</comment>
15# <i>ln -s /usr/share/zoneinfo/GMT /etc/localtime</i>
16</pre>
17
18</body>
19</section>
20<section> 14<section>
21<title>Filesystem Information</title> 15<title>Filesystem Information</title>
22<subsection> 16<subsection>
23<title>What is fstab?</title> 17<title>What is fstab?</title>
24<body> 18<body>
25 19
26<p> 20<p>
27Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
28<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
29(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
30(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
31etc.). 25them or not, etc.)
32</p> 26</p>
33 27
34</body> 28</body>
35</subsection> 29</subsection>
36<subsection> 30<subsection>
37<title>Creating /etc/fstab</title> 31<title>Creating /etc/fstab</title>
38<body> 32<body>
39 33
40<p> 34<p>
41<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
42fields, seperated by whitespace (space(s), tabs or a mixture). Each field has 36fields, separated by whitespace (space(s), tabs or a mixture). Each field has
43its own meaning: 37its own meaning:
44</p> 38</p>
45 39
46<ul> 40<ul>
47<li> 41<li>
56 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
57</li> 51</li>
58<li> 52<li>
59 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
60 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,
61 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
62 listing. Multiple mountoptions are comma-seperated. 56 listing. Multiple mountoptions are comma-separated.
63</li> 57</li>
64<li> 58<li>
65 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
66 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).
67</li> 61</li>
68<li> 62<li>
69 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
70 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.
71 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>
72 a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
73</li> 67</li>
74</ul> 68</ul>
75 69
76<p> 70<p>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
77So 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
78<path>/etc/fstab</path>: 73<path>/etc/fstab</path>:
79</p> 74</p>
80 75
81<pre caption="Opening /etc/fstab"> 76<pre caption="Opening /etc/fstab">
82# <i>nano -w /etc/fstab</i> 77# <i>nano -w /etc/fstab</i>
83</pre> 78</pre>
84 79
85<p> 80<p>
86Lets 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>
87partition. 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
88<path>/boot</path> partition, don't copy it verbatim. 83<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
89</p> 84</p>
90 85
91<p> 86<p>
92In our default x86 partitioning example <path>/boot</path> is the 87In our default x86 partitioning example <path>/boot</path> is the
93<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.
94be 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:
95would write down:
96</p> 90</p>
97 91
98<pre caption="An example /boot line for /etc/fstab"> 92<pre caption="An example /boot line for /etc/fstab">
99/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.
100</pre> 101</p>
101 102
102<p> 103<p>
103Now, 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>
104option as mountoption, which results in a faster system since access times 105option as mountoption, which results in a faster system since access times
105aren't registered (you don't need those generally anyway): 106aren't registered (you don't need those generally anyway):
106</p> 107</p>
107 108
108<pre caption="An improved /boot line for /etc/fstab"> 109<pre caption="An improved /boot line for /etc/fstab">
109/dev/hda1 /boot ext2 noauto,noatime 1 2 110/dev/hda1 /boot ext2 defaults,noatime 1 2
110</pre> 111</pre>
111 112
112<p> 113<p>
113If 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
114<path>/boot</path>, <path>/</path> and the swap partition): 115<path>/boot</path>, <path>/</path> and the swap partition):
115</p> 116</p>
116 117
117<pre caption="Three /etc/fstab lines"> 118<pre caption="Three /etc/fstab lines">
118/dev/hda1 /boot ext2 noauto,noatime 1 2 119/dev/hda1 /boot ext2 defaults,noatime 1 2
119/dev/hda2 none swap sw 0 0 120/dev/hda2 none swap sw 0 0
120/dev/hda3 / ext3 noatime 0 1 121/dev/hda3 / ext3 noatime 0 1
121</pre> 122</pre>
122 123
123<p> 124<p>
124To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> 125To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
125(required) and for your CD-ROM drive (and ofcourse, if you have other 126(required) and for your CD-ROM drive (and of course, if you have other
126partitions or drives, for those too): 127partitions or drives, for those too):
127</p> 128</p>
128 129
129<pre caption="A full /etc/fstab example"> 130<pre caption="A full /etc/fstab example">
130/dev/hda1 /boot ext2 noauto,noatime 1 2 131/dev/hda1 /boot ext2 defaults,noatime 1 2
131/dev/hda2 none swap sw 0 0 132/dev/hda2 none swap sw 0 0
132/dev/hda3 / ext3 noatime 0 1 133/dev/hda3 / ext3 noatime 0 1
133 134
134none /proc proc defaults 0 0 135none /proc proc defaults 0 0
135none /dev/shm tmpfs defaults 0 0 136none /dev/shm tmpfs nodev,nosuid,noexec 0 0
136 137
137/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
138</pre> 139</pre>
139 140
140<p> 141<p>
143<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.
144</p> 145</p>
145 146
146<p> 147<p>
147Now 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
148SPARC-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>
149too: 151too:
150</p> 152</p>
151 153
152<pre caption="Adding openprom filesystem to /etc/fstab"> 154<pre caption="Adding openprom filesystem to /etc/fstab">
153none /proc/openprom openpromfs defaults 0 0 155none /proc/openprom openpromfs defaults 0 0
154</pre> 156</pre>
155 157
156<p> 158<p>
157Reread your <path>/etc/fstab</path>, save and quit to continue. 159Double-check your <path>/etc/fstab</path>, save and quit to continue.
158</p> 160</p>
159 161
160</body> 162</body>
161</subsection> 163</subsection>
162</section> 164</section>
165<subsection> 167<subsection>
166<title>Hostname, Domainname etc.</title> 168<title>Hostname, Domainname etc.</title>
167<body> 169<body>
168 170
169<p> 171<p>
170One of the choices the user has to make is name his PC. This seems to be quite 172One of the choices the user has to make is name his/her PC. This seems to be
171easy, but <e>lots</e> of users are having difficulties finding the appropriate 173quite easy, but <e>lots</e> of users are having difficulties finding the
172name for their Linux-pc. To speed things up, know that any name you choose can 174appropriate name for their Linux-pc. To speed things up, know that any name you
173be changed afterwards. For all we care, you can just call your system 175choose can be changed afterwards. For all we care, you can just call your system
174<c>tux</c> and domain <c>homenetwork</c>. 176<c>tux</c> and domain <c>homenetwork</c>.
175</p> 177</p>
176 178
177<p> 179<p>
178We use these values in the next examples. First we set the hostname: 180We use these values in the next examples. First we set the hostname:
179</p> 181</p>
180 182
181<pre caption="Setting the hostname"> 183<pre caption="Setting the hostname">
182# <i>echo tux &gt; /etc/hostname</i> 184# <i>nano -w /etc/conf.d/hostname</i>
185
186<comment>(Set the HOSTNAME variable to your hostname)</comment>
187HOSTNAME="<i>tux</i>"
183</pre> 188</pre>
184 189
185<p> 190<p>
186Second we set the domainname: 191Second we set the domainname:
187</p> 192</p>
188 193
189<pre caption="Setting the domainname"> 194<pre caption="Setting the domainname">
190# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 195# <i>nano -w /etc/conf.d/domainname</i>
196
197<comment>(Set the DNSDOMAIN variable to your domain name)</comment>
198DNSDOMAIN="<i>homenetwork</i>"
191</pre> 199</pre>
192 200
193<p> 201<p>
194If you have a NIS domain (if you don't know what that is, then you don't have 202If you have a NIS domain (if you don't know what that is, then you don't have
195one), you need to define that one too: 203one), you need to define that one too:
196</p> 204</p>
197 205
198<pre caption="Setting the NIS domainname"> 206<pre caption="Setting the NIS domainname">
199# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 207# <i>nano -w /etc/conf.d/domainname</i>
208
209<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
210NISDOMAIN="<i>my-nisdomain</i>"
211</pre>
212
213<p>
214Now add the <c>domainname</c> script to the default runlevel:
215</p>
216
217<pre caption="Adding domainname to the default runlevel">
218# <i>rc-update add domainname default</i>
200</pre> 219</pre>
201 220
202</body> 221</body>
203</subsection> 222</subsection>
204<subsection> 223<subsection>
205<title>Configuring your Network</title> 224<title>Configuring your Network</title>
206<body> 225<body>
207 226
208<p> 227<p>
209Before you get that "Hey, we've had that already"-feeling, you should remember 228Before you get that "Hey, we've had that already"-feeling, you should remember
210that the networking you set up in the beginning of the gentoo installation was 229that the networking you set up in the beginning of the Gentoo installation was
211just for the installation. Right now you are going to configure networking for 230just for the installation. Right now you are going to configure networking for
212your Gentoo system permanently. 231your Gentoo system permanently.
213</p> 232</p>
214 233
234<note>
235More detailed information about networking, including advanced topics like
236bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
237link="?part=4">Gentoo Network Configuration</uri> section.
238</note>
239
215<p> 240<p>
216All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 241All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
217a straightforward yet not intuitive syntax if you don't know how to setup 242a straightforward yet not intuitive syntax if you don't know how to set up
218networking manually. But don't fear, we'll explain everything :) 243networking manually. But don't fear, we'll explain everything. A fully
219</p> 244commented example that covers many different configurations is available in
220 245<path>/etc/conf.d/net.example</path>.
221<p> 246</p>
247
248<p>
249DHCP is used by default and does not require any further configuration.
250</p>
251
252<p>
253If you need to configure your network connection either because you need
254specific DHCP options or because you do not use DHCP at all, open
222First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 255<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
223is used in this example): 256this example):
224</p> 257</p>
225 258
226<pre caption="Opening /etc/conf.d/net for editing"> 259<pre caption="Opening /etc/conf.d/net for editing">
227# <i>nano -w /etc/conf.d/net</i> 260# <i>nano -w /etc/conf.d/net</i>
228</pre> 261</pre>
229 262
230<p> 263<p>
231The first variable you'll find is <c>iface_eth0</c>. It uses the following 264You will see the following file:
232syntax:
233</p>
234
235<pre caption="iface_eth0 syntaxis">
236iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
237</pre>
238
239<p> 265</p>
240If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 266
241to <c>dhcp</c>. However, if you need to setup your network manually and you're 267<pre caption="Default /etc/conf.d/net">
242not familiar with all the above terms, please read the section on <uri 268# This blank configuration will automatically use DHCP for any net.*
243link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 269# scripts in /etc/init.d. To create a more complete configuration,
244Terminology</uri> if you haven't done so already. 270# please review /etc/conf.d/net.example and save your configuration
271# in /etc/conf.d/net (this file :]!).
272</pre>
273
245</p> 274<p>
246 275To enter your own IP address, netmask and gateway, you need
276to set both <c>config_eth0</c> and <c>routes_eth0</c>:
247<p> 277</p>
248So lets give two examples; the first one uses DHCP, the second one a static IP 278
249(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 279<pre caption="Manually setting IP information for eth0">
250192.168.0.1: 280config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
281routes_eth0=( "default gw 192.168.0.1" )
282</pre>
283
251</p> 284<p>
252 285To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
253<pre caption="Examples for /etc/conf.d/net"> 286<c>dhcp_eth0</c>:
254<comment>(For DHCP:)</comment>
255iface_eth0="dhcp"
256
257<comment>(For static IP:)</comment>
258iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
259gateway="eth0/192.168.0.1"
260</pre>
261
262<p> 287</p>
263If you have several network interfaces, create extra <c>iface_eth</c> variables, 288
264like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 289<pre caption="Automatically obtaining an IP address for eth0">
265shouldn't be reproduced as you can only set one gateway per computer. 290config_eth0=( "dhcp" )
291dhcp_eth0="nodns nontp nonis"
292</pre>
293
294<p>
295Please read <path>/etc/conf.d/net.example</path> for a list of all available
296options.
297</p>
298
299<p>
300If you have several network interfaces repeat the above steps for
301<c>config_eth1</c>, <c>config_eth2</c>, etc.
266</p> 302</p>
267 303
268<p> 304<p>
269Now save the configuration and exit to continue. 305Now save the configuration and exit to continue.
270</p> 306</p>
274<subsection> 310<subsection>
275<title>Automatically Start Networking at Boot</title> 311<title>Automatically Start Networking at Boot</title>
276<body> 312<body>
277 313
278<p> 314<p>
279To have your network interfaces activated at boot, you need to add those to the 315To have your network interfaces activated at boot, you need to add them to the
280default runlevel. If you have PCMCIA interfaces you should skip this action as 316default runlevel. If you have PCMCIA interfaces you should skip this action as
281the PCMCIA interfaces are started by the PCMCIA init script. 317the PCMCIA interfaces are started by the PCMCIA init script.
282</p> 318</p>
283 319
284<pre caption="Adding net.eth0 to the default runlevel"> 320<pre caption="Adding net.eth0 to the default runlevel">
306<p> 342<p>
307You now need to inform Linux about your network. This is defined in 343You now need to inform Linux about your network. This is defined in
308<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 344<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses
309for hosts that aren't resolved by your nameserver. For instance, if your 345for hosts that aren't resolved by your nameserver. For instance, if your
310internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 346internal network consists of three PCs called <c>jenny</c> (192.168.0.5),
311<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 347<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would
312open <path>/etc/hosts</path> and fill in the values: 348open <path>/etc/hosts</path> and fill in the values:
313</p> 349</p>
314 350
315<pre caption="Opening /etc/hosts"> 351<pre caption="Opening /etc/hosts">
316# <i>nano -w /etc/hosts</i> 352# <i>nano -w /etc/hosts</i>
317</pre> 353</pre>
318 354
319<pre caption="Filling in the networking information"> 355<pre caption="Filling in the networking information">
320127.0.0.1 localhost tux 356127.0.0.1 localhost
321192.168.0.5 jenny 357192.168.0.5 jenny.homenetwork jenny
322192.168.0.56 benny 358192.168.0.6 benny.homenetwork benny
359192.168.0.7 tux.homenetwork tux
323</pre> 360</pre>
324 361
325<p> 362<p>
326If your system is the only system (or the nameservers handle all name 363If your system is the only system (or the nameservers handle all name
327resolution) a single line is sufficient: 364resolution) a single line is sufficient. For instance, if you want to call your
365system <c>tux</c>:
328</p> 366</p>
329 367
330<pre caption="/etc/hosts for lonely or fully integrated PCs"> 368<pre caption="/etc/hosts for lonely or fully integrated PCs">
331127.0.0.1 localhost tux 369127.0.0.1 localhost tux
332</pre> 370</pre>
333 371
334<p> 372<p>
335Save and exit the editor to continue. 373Save and exit the editor to continue.
336</p> 374</p>
337 375
338<p> 376<p>
339If you don't have PCMCIA, you can now continue with <uri 377If you don't have PCMCIA, you can now continue with <uri
340link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 378link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
341following topic on PCMCIA. 379following topic on PCMCIA.
342</p> 380</p>
343 381
344</body> 382</body>
345</subsection> 383</subsection>
346<subsection> 384<subsection>
347<title>Optional: Get PCMCIA Working</title> 385<title>Optional: Get PCMCIA Working</title>
348<body> 386<body>
349 387
388<note>
389pcmcia-cs is only available for x86, amd64 and ppc platforms.
390</note>
391
350<p> 392<p>
351PCMCIA-users should first install the <c>pcmcia-cs</c> package: 393PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
394includes users who will be working with a 2.6 kernel (even though they won't be
395using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
396to avoid installing xorg-x11 at this moment:
352</p> 397</p>
353 398
354<pre caption="Installing pcmcia-cs"> 399<pre caption="Installing pcmcia-cs">
355# <i>emerge -k pcmcia-cs</i> 400# <i>USE="-X" emerge pcmcia-cs</i>
356</pre> 401</pre>
357 402
358<p> 403<p>
359When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 404When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
360runlevel: 405runlevel:
361</p> 406</p>
362 407
363<pre caption="Adding pcmcia to the default runlevel"> 408<pre caption="Adding pcmcia to the default runlevel">
364# <i>rc-update add pcmcia boot</i> 409# <i>rc-update add pcmcia default</i>
365</pre> 410</pre>
366 411
367</body> 412</body>
368</subsection> 413</subsection>
369</section> 414</section>
370<section> 415<section>
371<title>System Information</title> 416<title>System Information</title>
417<subsection>
418<title>Root Password</title>
419<body>
420
421<p>
422First we set the root password by typing:
423</p>
424
425<pre caption="Setting the root password">
426# <i>passwd</i>
427</pre>
428
429<p>
430If you want root to be able to log on through the serial console, add
431<c>tts/0</c> to <path>/etc/securetty</path>:
432</p>
433
434<pre caption="Adding tts/0 to /etc/securetty">
435# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
436</pre>
437
438</body>
439</subsection>
440<subsection>
441<title>System Information</title>
372<body> 442<body>
373 443
374<p> 444<p>
375Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 445Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
376Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) 446Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
379<pre caption="Opening /etc/rc.conf"> 449<pre caption="Opening /etc/rc.conf">
380# <i>nano -w /etc/rc.conf</i> 450# <i>nano -w /etc/rc.conf</i>
381</pre> 451</pre>
382 452
383<p> 453<p>
454When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
455</p>
456
457<p>
384As you can see, this file is well commented to help you set up the necessary 458As you can see, this file is well commented to help you set up the necessary
385configuration variables. When you're finished configuring 459configuration variables. You can configure your system to use unicode and
386<path>/etc/rc.conf</path>, save and exit to continue. 460define your default editor and your display manager (like gdm or kdm).
461</p>
462
387</p> 463<p>
464Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
465Edit it to configure your keyboard.
466</p>
388 467
468<pre caption="Opening /etc/conf.d/keymaps">
469# <i>nano -w /etc/conf.d/keymaps</i>
470</pre>
471
472<p>
473Take special care with the <c>KEYMAP</c> variable. If you select the wrong
474<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
475</p>
476
477<note>
478Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
479select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
480keymaps on most systems. Users who want to be able to use ADB keymaps on boot
481have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
482keymap in <path>/etc/conf.d/keymaps</path>.
483</note>
484
485<p>
486When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
487exit.
488</p>
489
490<p>
491Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
492according to your needs.
493</p>
494
495<pre caption="Opening /etc/conf.d/clock">
496# <i>nano -w /etc/conf.d/clock</i>
497</pre>
498
499<p>
500If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
501the file. Otherwise you will notice some clock skew.
502</p>
503
504<p>
505When you're finished configuring <path>/etc/conf.d/clock</path>, save and
506exit.
507</p>
508
509<p>
510If you are not installing Gentoo on IBM PPC64 hardware, continue with
511<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>.
512</p>
513
514</body>
515</subsection>
516<subsection>
517<title>Configuring the Console</title>
389</body> 518<body>
519
520<note>
521The following section applies to the IBM PPC64 hardware platforms.
522</note>
523
524<p>
525If you are running Gentoo on IBM PPC64 hardware and using a virtual console
526you must uncomment the appropriate line in <path>/etc/inittab</path> for the
527virtual console to spawn a login prompt.
528</p>
529
530<pre caption="Enabling hvc or hvsi support in /etc/inittab">
531hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
532hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
533</pre>
534
535<p>
536You should also take this time to verify that the appropriate console is
537listed in <path>/etc/securetty</path>.
538</p>
539
540<p>
541You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
542System Tools</uri>.
543</p>
544
545</body>
546</subsection>
390</section> 547</section>
391</sections> 548</sections>

Legend:
Removed from v.1.3  
changed lines
  Added in v.1.72

  ViewVC Help
Powered by ViewVC 1.1.20