/[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.78
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.78 2006/05/27 13:02:15 neysx Exp $ -->
8
1<sections> 9<sections>
2<section>
3<title>Timezone</title>
4<body>
5 10
6<p> 11<version>2.19</version>
7You now need to select your timezone so that your system knows where it is 12<date>2006-05-27</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 not a valid
77So 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
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 Apple <b>PPC</b> machines), don't copy it
84verbatim.
89</p> 85</p>
90 86
91<p> 87<p>
92In our default x86 partitioning example <path>/boot</path> is the 88In 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 89<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 90It needs to be checked during boot, so we would write down:
95would write down:
96</p> 91</p>
97 92
98<pre caption="An example /boot line for /etc/fstab"> 93<pre caption="An example /boot line for /etc/fstab">
99/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.
100</pre> 102</p>
101 103
102<p> 104<p>
103Now, 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>
104option as mountoption, which results in a faster system since access times 106option as mountoption, which results in a faster system since access times
105aren't registered (you don't need those generally anyway): 107aren't registered (you don't need those generally anyway):
106</p> 108</p>
107 109
108<pre caption="An improved /boot line for /etc/fstab"> 110<pre caption="An improved /boot line for /etc/fstab">
109/dev/hda1 /boot ext2 noauto,noatime 1 2 111/dev/hda1 /boot ext2 defaults,noatime 1 2
110</pre> 112</pre>
111 113
112<p> 114<p>
113If 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
114<path>/boot</path>, <path>/</path> and the swap partition): 116<path>/boot</path>, <path>/</path> and the swap partition):
115</p> 117</p>
116 118
117<pre caption="Three /etc/fstab lines"> 119<pre caption="Three /etc/fstab lines">
118/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 defaults,noatime 1 2
119/dev/hda2 none swap sw 0 0 121/dev/hda2 none swap sw 0 0
120/dev/hda3 / ext3 noatime 0 1 122/dev/hda3 / ext3 noatime 0 1
121</pre> 123</pre>
122 124
123<p> 125<p>
124To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> 126To 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 127(required) and for your CD-ROM drive (and of course, if you have other
126partitions or drives, for those too): 128partitions or drives, for those too):
127</p> 129</p>
128 130
129<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example">
130/dev/hda1 /boot ext2 noauto,noatime 1 2 132/dev/hda1 /boot ext2 defaults,noatime 1 2
131/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
132/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
133 135
134none /proc proc defaults 0 0 136none /proc proc defaults 0 0
135none /dev/shm tmpfs defaults 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
136 138
137/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
138</pre> 140</pre>
139 141
140<p> 142<p>
143<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.
144</p> 146</p>
145 147
146<p> 148<p>
147Now 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
148SPARC-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>
149too: 152too:
150</p> 153</p>
151 154
152<pre caption="Adding openprom filesystem to /etc/fstab"> 155<pre caption="Adding openprom filesystem to /etc/fstab">
153none /proc/openprom openpromfs defaults 0 0 156none /proc/openprom openpromfs defaults 0 0
154</pre> 157</pre>
155 158
156<p> 159<p>
157Reread your <path>/etc/fstab</path>, save and quit to continue. 160Double-check your <path>/etc/fstab</path>, save and quit to continue.
158</p> 161</p>
159 162
160</body> 163</body>
161</subsection> 164</subsection>
162</section> 165</section>
165<subsection> 168<subsection>
166<title>Hostname, Domainname etc.</title> 169<title>Hostname, Domainname etc.</title>
167<body> 170<body>
168 171
169<p> 172<p>
170One 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
171easy, 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
172name 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
173be 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
174<c>tux</c> and domain <c>homenetwork</c>. 177<c>tux</c> and domain <c>homenetwork</c>.
175</p> 178</p>
176 179
177<p> 180<p>
178We 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:
179</p> 182</p>
180 183
181<pre caption="Setting the hostname"> 184<pre caption="Setting the hostname">
182# <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>"
183</pre> 189</pre>
184 190
185<p> 191<p>
186Second we set the domainname: 192Second we set the domainname:
187</p> 193</p>
188 194
189<pre caption="Setting the domainname"> 195<pre caption="Setting the domainname">
190# <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>"
191</pre> 200</pre>
192 201
193<p> 202<p>
194If 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
195one), you need to define that one too: 204one), you need to define that one too:
196</p> 205</p>
197 206
198<pre caption="Setting the NIS domainname"> 207<pre caption="Setting the NIS domainname">
199# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 208# <i>nano -w /etc/conf.d/domainname</i>
209
210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
211NISDOMAIN="<i>my-nisdomain</i>"
200</pre> 212</pre>
201 213
202</body> 214</body>
203</subsection> 215</subsection>
204<subsection> 216<subsection>
205<title>Configuring your Network</title> 217<title>Configuring your Network</title>
206<body> 218<body>
207 219
208<p> 220<p>
209Before 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
210that 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
211just 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
212your Gentoo system permanently. 224your Gentoo system permanently.
213</p> 225</p>
214 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
215<p> 233<p>
216All 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
217a 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
218networking manually. But don't fear, we'll explain everything :) 236networking manually. But don't fear, we'll explain everything. A fully
219</p> 237commented example that covers many different configurations is available in
220 238<path>/etc/conf.d/net.example</path>.
221<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
222First 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
223is used in this example): 249this example):
224</p> 250</p>
225 251
226<pre caption="Opening /etc/conf.d/net for editing"> 252<pre caption="Opening /etc/conf.d/net for editing">
227# <i>nano -w /etc/conf.d/net</i> 253# <i>nano -w /etc/conf.d/net</i>
228</pre> 254</pre>
229 255
230<p> 256<p>
231The first variable you'll find is <c>iface_eth0</c>. It uses the following 257You 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> 258</p>
240If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 259
241to <c>dhcp</c>. However, if you need to setup your network manually and you're 260<pre caption="Default /etc/conf.d/net">
242not familiar with all the above terms, please read the section on <uri 261# This blank configuration will automatically use DHCP for any net.*
243link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 262# scripts in /etc/init.d. To create a more complete configuration,
244Terminology</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
245</p> 267<p>
246 268To enter your own IP address, netmask and gateway, you need
269to set both <c>config_eth0</c> and <c>routes_eth0</c>:
247<p> 270</p>
248So lets give two examples; the first one uses DHCP, the second one a static IP 271
249(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">
250192.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
251</p> 277<p>
252 278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
253<pre caption="Examples for /etc/conf.d/net"> 279<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> 280</p>
263If you have several network interfaces, create extra <c>iface_eth</c> variables, 281
264like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282<pre caption="Automatically obtaining an IP address for eth0">
265shouldn'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.
266</p> 295</p>
267 296
268<p> 297<p>
269Now save the configuration and exit to continue. 298Now save the configuration and exit to continue.
270</p> 299</p>
274<subsection> 303<subsection>
275<title>Automatically Start Networking at Boot</title> 304<title>Automatically Start Networking at Boot</title>
276<body> 305<body>
277 306
278<p> 307<p>
279To 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
280default 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
281the PCMCIA interfaces are started by the PCMCIA init script. 310the PCMCIA interfaces are started by the PCMCIA init script.
282</p> 311</p>
283 312
284<pre caption="Adding net.eth0 to the default runlevel"> 313<pre caption="Adding net.eth0 to the default runlevel">
303<title>Writing Down Network Information</title> 332<title>Writing Down Network Information</title>
304<body> 333<body>
305 334
306<p> 335<p>
307You 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
308<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
309for 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.
310internal 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
311<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 340set up your own internal DNS system.
312open <path>/etc/hosts</path> and fill in the values:
313</p> 341</p>
314 342
315<pre caption="Opening /etc/hosts"> 343<pre caption="Opening /etc/hosts">
316# <i>nano -w /etc/hosts</i> 344# <i>nano -w /etc/hosts</i>
317</pre> 345</pre>
318 346
319<pre caption="Filling in the networking information"> 347<pre caption="Filling in the networking information">
320127.0.0.1 localhost tux 348<comment>(This defines the current system)</comment>
321192.168.0.5 jenny 349127.0.0.1 tux.homenetwork tux localhost
322192.168.0.56 benny
323</pre>
324 350
325<p> 351<comment>(Define extra systems on your network,
326If 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>
327resolution) a single line is sufficient: 353192.168.0.5 jenny.homenetwork jenny
328</p> 354192.168.0.6 benny.homenetwork benny
329
330<pre caption="/etc/hosts for lonely or fully integrated PCs">
331127.0.0.1 localhost tux
332</pre> 355</pre>
333 356
334<p> 357<p>
335Save and exit the editor to continue. 358Save and exit the editor to continue.
336</p> 359</p>
337 360
338<p> 361<p>
339If you don't have PCMCIA, you can now continue with <uri 362If you don't have PCMCIA, you can now continue with <uri
340link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 363link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
341following topic on PCMCIA. 364following topic on PCMCIA.
342</p> 365</p>
343 366
344</body> 367</body>
345</subsection> 368</subsection>
346<subsection> 369<subsection>
347<title>Optional: Get PCMCIA Working</title> 370<title>Optional: Get PCMCIA Working</title>
348<body> 371<body>
349 372
373<note>
374pcmcia-cs is only available for x86, amd64 and ppc platforms.
375</note>
376
350<p> 377<p>
351PCMCIA-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:
352</p> 382</p>
353 383
354<pre caption="Installing pcmcia-cs"> 384<pre caption="Installing pcmcia-cs">
355# <i>emerge -k pcmcia-cs</i> 385# <i>USE="-X" emerge pcmcia-cs</i>
356</pre> 386</pre>
357 387
358<p> 388<p>
359When <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>
360runlevel: 390runlevel:
361</p> 391</p>
362 392
363<pre caption="Adding pcmcia to the default runlevel"> 393<pre caption="Adding pcmcia to the default runlevel">
364# <i>rc-update add pcmcia boot</i> 394# <i>rc-update add pcmcia default</i>
365</pre> 395</pre>
366 396
367</body> 397</body>
368</subsection> 398</subsection>
369</section> 399</section>
370<section> 400<section>
371<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>
372<body> 427<body>
373 428
374<p> 429<p>
375Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 430Gentoo 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 :) 431Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
379<pre caption="Opening /etc/rc.conf"> 434<pre caption="Opening /etc/rc.conf">
380# <i>nano -w /etc/rc.conf</i> 435# <i>nano -w /etc/rc.conf</i>
381</pre> 436</pre>
382 437
383<p> 438<p>
439When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
440</p>
441
442<p>
384As 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
385configuration variables. When you're finished configuring 444configuration variables. You can configure your system to use unicode and
386<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
387</p> 448<p>
449Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
450Edit it to configure your keyboard.
451</p>
388 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>
389</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>
390</section> 534</section>
391</sections> 535</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20