/[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.4 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 -->
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 $ -->
3 8
4<sections> 9<sections>
5<section>
6<title>Timezone</title>
7<body>
8 10
9<p> 11<version>2.19</version>
10You now need to select your timezone so that your system knows where it is 12<date>2006-05-27</date>
11located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
12symlink to <path>/etc/localtime</path> using <c>ln</c>:
13</p>
14 13
15<pre caption="Setting the timezone information">
16# <i>ls /usr/share/zoneinfo</i>
17<comment>(Suppose you want to use GTM:)</comment>
18# <i>ln -s /usr/share/zoneinfo/GMT /etc/localtime</i>
19</pre>
20
21</body>
22</section>
23<section> 14<section>
24<title>Filesystem Information</title> 15<title>Filesystem Information</title>
25<subsection> 16<subsection>
26<title>What is fstab?</title> 17<title>What is fstab?</title>
27<body> 18<body>
28 19
29<p> 20<p>
30Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
31<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
32(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
33(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
34etc.). 25them or not, etc.)
35</p> 26</p>
36 27
37</body> 28</body>
38</subsection> 29</subsection>
39<subsection> 30<subsection>
40<title>Creating /etc/fstab</title> 31<title>Creating /etc/fstab</title>
41<body> 32<body>
42 33
43<p> 34<p>
44<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
45fields, 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
46its own meaning: 37its own meaning:
47</p> 38</p>
48 39
49<ul> 40<ul>
50<li> 41<li>
59 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
60</li> 51</li>
61<li> 52<li>
62 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
63 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,
64 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
65 listing. Multiple mountoptions are comma-seperated. 56 listing. Multiple mountoptions are comma-separated.
66</li> 57</li>
67<li> 58<li>
68 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
69 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).
70</li> 61</li>
71<li> 62<li>
72 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
73 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.
74 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>
75 a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
76</li> 67</li>
77</ul> 68</ul>
78 69
79<p> 70<p>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
80So 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
81<path>/etc/fstab</path>: 73<path>/etc/fstab</path>:
82</p> 74</p>
83 75
84<pre caption="Opening /etc/fstab"> 76<pre caption="Opening /etc/fstab">
85# <i>nano -w /etc/fstab</i> 77# <i>nano -w /etc/fstab</i>
86</pre> 78</pre>
87 79
88<p> 80<p>
89Lets 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>
90partition. 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
91<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.
92</p> 85</p>
93 86
94<p> 87<p>
95In our default x86 partitioning example <path>/boot</path> is the 88In our default x86 partitioning example <path>/boot</path> is the
96<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.
97be 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:
98would write down:
99</p> 91</p>
100 92
101<pre caption="An example /boot line for /etc/fstab"> 93<pre caption="An example /boot line for /etc/fstab">
102/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.
103</pre> 102</p>
104 103
105<p> 104<p>
106Now, 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>
107option as mountoption, which results in a faster system since access times 106option as mountoption, which results in a faster system since access times
108aren't registered (you don't need those generally anyway): 107aren't registered (you don't need those generally anyway):
109</p> 108</p>
110 109
111<pre caption="An improved /boot line for /etc/fstab"> 110<pre caption="An improved /boot line for /etc/fstab">
112/dev/hda1 /boot ext2 noauto,noatime 1 2 111/dev/hda1 /boot ext2 defaults,noatime 1 2
113</pre> 112</pre>
114 113
115<p> 114<p>
116If 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
117<path>/boot</path>, <path>/</path> and the swap partition): 116<path>/boot</path>, <path>/</path> and the swap partition):
118</p> 117</p>
119 118
120<pre caption="Three /etc/fstab lines"> 119<pre caption="Three /etc/fstab lines">
121/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 defaults,noatime 1 2
122/dev/hda2 none swap sw 0 0 121/dev/hda2 none swap sw 0 0
123/dev/hda3 / ext3 noatime 0 1 122/dev/hda3 / ext3 noatime 0 1
124</pre> 123</pre>
125 124
126<p> 125<p>
127To 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>
128(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
129partitions or drives, for those too): 128partitions or drives, for those too):
130</p> 129</p>
131 130
132<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example">
133/dev/hda1 /boot ext2 noauto,noatime 1 2 132/dev/hda1 /boot ext2 defaults,noatime 1 2
134/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
135/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
136 135
137none /proc proc defaults 0 0 136none /proc proc defaults 0 0
138none /dev/shm tmpfs defaults 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
139 138
140/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
141</pre> 140</pre>
142 141
143<p> 142<p>
146<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.
147</p> 146</p>
148 147
149<p> 148<p>
150Now 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
151SPARC-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>
152too: 152too:
153</p> 153</p>
154 154
155<pre caption="Adding openprom filesystem to /etc/fstab"> 155<pre caption="Adding openprom filesystem to /etc/fstab">
156none /proc/openprom openpromfs defaults 0 0 156none /proc/openprom openpromfs defaults 0 0
157</pre> 157</pre>
158 158
159<p> 159<p>
160Reread your <path>/etc/fstab</path>, save and quit to continue. 160Double-check your <path>/etc/fstab</path>, save and quit to continue.
161</p> 161</p>
162 162
163</body> 163</body>
164</subsection> 164</subsection>
165</section> 165</section>
168<subsection> 168<subsection>
169<title>Hostname, Domainname etc.</title> 169<title>Hostname, Domainname etc.</title>
170<body> 170<body>
171 171
172<p> 172<p>
173One 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
174easy, 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
175name 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
176be 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
177<c>tux</c> and domain <c>homenetwork</c>. 177<c>tux</c> and domain <c>homenetwork</c>.
178</p> 178</p>
179 179
180<p> 180<p>
181We 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:
182</p> 182</p>
183 183
184<pre caption="Setting the hostname"> 184<pre caption="Setting the hostname">
185# <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>"
186</pre> 189</pre>
187 190
188<p> 191<p>
189Second we set the domainname: 192Second we set the domainname:
190</p> 193</p>
191 194
192<pre caption="Setting the domainname"> 195<pre caption="Setting the domainname">
193# <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>"
194</pre> 200</pre>
195 201
196<p> 202<p>
197If 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
198one), you need to define that one too: 204one), you need to define that one too:
199</p> 205</p>
200 206
201<pre caption="Setting the NIS domainname"> 207<pre caption="Setting the NIS domainname">
202# <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>"
203</pre> 212</pre>
204 213
205</body> 214</body>
206</subsection> 215</subsection>
207<subsection> 216<subsection>
208<title>Configuring your Network</title> 217<title>Configuring your Network</title>
209<body> 218<body>
210 219
211<p> 220<p>
212Before 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
213that 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
214just 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
215your Gentoo system permanently. 224your Gentoo system permanently.
216</p> 225</p>
217 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
218<p> 233<p>
219All 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
220a 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
221networking manually. But don't fear, we'll explain everything :) 236networking manually. But don't fear, we'll explain everything. A fully
222</p> 237commented example that covers many different configurations is available in
223 238<path>/etc/conf.d/net.example</path>.
224<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
225First 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
226is used in this example): 249this example):
227</p> 250</p>
228 251
229<pre caption="Opening /etc/conf.d/net for editing"> 252<pre caption="Opening /etc/conf.d/net for editing">
230# <i>nano -w /etc/conf.d/net</i> 253# <i>nano -w /etc/conf.d/net</i>
231</pre> 254</pre>
232 255
233<p> 256<p>
234The first variable you'll find is <c>iface_eth0</c>. It uses the following 257You will see the following file:
235syntax:
236</p>
237
238<pre caption="iface_eth0 syntaxis">
239iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
240</pre>
241
242<p> 258</p>
243If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 259
244to <c>dhcp</c>. However, if you need to setup your network manually and you're 260<pre caption="Default /etc/conf.d/net">
245not familiar with all the above terms, please read the section on <uri 261# This blank configuration will automatically use DHCP for any net.*
246link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 262# scripts in /etc/init.d. To create a more complete configuration,
247Terminology</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
248</p> 267<p>
249 268To enter your own IP address, netmask and gateway, you need
269to set both <c>config_eth0</c> and <c>routes_eth0</c>:
250<p> 270</p>
251So lets give two examples; the first one uses DHCP, the second one a static IP 271
252(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">
253192.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
254</p> 277<p>
255 278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
256<pre caption="Examples for /etc/conf.d/net"> 279<c>dhcp_eth0</c>:
257<comment>(For DHCP:)</comment>
258iface_eth0="dhcp"
259
260<comment>(For static IP:)</comment>
261iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
262gateway="eth0/192.168.0.1"
263</pre>
264
265<p> 280</p>
266If you have several network interfaces, create extra <c>iface_eth</c> variables, 281
267like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282<pre caption="Automatically obtaining an IP address for eth0">
268shouldn'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.
269</p> 295</p>
270 296
271<p> 297<p>
272Now save the configuration and exit to continue. 298Now save the configuration and exit to continue.
273</p> 299</p>
277<subsection> 303<subsection>
278<title>Automatically Start Networking at Boot</title> 304<title>Automatically Start Networking at Boot</title>
279<body> 305<body>
280 306
281<p> 307<p>
282To 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
283default 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
284the PCMCIA interfaces are started by the PCMCIA init script. 310the PCMCIA interfaces are started by the PCMCIA init script.
285</p> 311</p>
286 312
287<pre caption="Adding net.eth0 to the default runlevel"> 313<pre caption="Adding net.eth0 to the default runlevel">
306<title>Writing Down Network Information</title> 332<title>Writing Down Network Information</title>
307<body> 333<body>
308 334
309<p> 335<p>
310You 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
311<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
312for 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.
313internal 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
314<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 340set up your own internal DNS system.
315open <path>/etc/hosts</path> and fill in the values:
316</p> 341</p>
317 342
318<pre caption="Opening /etc/hosts"> 343<pre caption="Opening /etc/hosts">
319# <i>nano -w /etc/hosts</i> 344# <i>nano -w /etc/hosts</i>
320</pre> 345</pre>
321 346
322<pre caption="Filling in the networking information"> 347<pre caption="Filling in the networking information">
323127.0.0.1 localhost tux 348<comment>(This defines the current system)</comment>
324192.168.0.5 jenny 349127.0.0.1 tux.homenetwork tux localhost
325192.168.0.56 benny
326</pre>
327 350
328<p> 351<comment>(Define extra systems on your network,
329If 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>
330resolution) a single line is sufficient: 353192.168.0.5 jenny.homenetwork jenny
331</p> 354192.168.0.6 benny.homenetwork benny
332
333<pre caption="/etc/hosts for lonely or fully integrated PCs">
334127.0.0.1 localhost tux
335</pre> 355</pre>
336 356
337<p> 357<p>
338Save and exit the editor to continue. 358Save and exit the editor to continue.
339</p> 359</p>
340 360
341<p> 361<p>
342If you don't have PCMCIA, you can now continue with <uri 362If you don't have PCMCIA, you can now continue with <uri
343link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 363link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
344following topic on PCMCIA. 364following topic on PCMCIA.
345</p> 365</p>
346 366
347</body> 367</body>
348</subsection> 368</subsection>
349<subsection> 369<subsection>
350<title>Optional: Get PCMCIA Working</title> 370<title>Optional: Get PCMCIA Working</title>
351<body> 371<body>
352 372
373<note>
374pcmcia-cs is only available for x86, amd64 and ppc platforms.
375</note>
376
353<p> 377<p>
354PCMCIA-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:
355</p> 382</p>
356 383
357<pre caption="Installing pcmcia-cs"> 384<pre caption="Installing pcmcia-cs">
358# <i>emerge -k pcmcia-cs</i> 385# <i>USE="-X" emerge pcmcia-cs</i>
359</pre> 386</pre>
360 387
361<p> 388<p>
362When <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>
363runlevel: 390runlevel:
364</p> 391</p>
365 392
366<pre caption="Adding pcmcia to the default runlevel"> 393<pre caption="Adding pcmcia to the default runlevel">
367# <i>rc-update add pcmcia boot</i> 394# <i>rc-update add pcmcia default</i>
368</pre> 395</pre>
369 396
370</body> 397</body>
371</subsection> 398</subsection>
372</section> 399</section>
373<section> 400<section>
374<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>
375<body> 427<body>
376 428
377<p> 429<p>
378Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 430Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
379Open 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 :)
382<pre caption="Opening /etc/rc.conf"> 434<pre caption="Opening /etc/rc.conf">
383# <i>nano -w /etc/rc.conf</i> 435# <i>nano -w /etc/rc.conf</i>
384</pre> 436</pre>
385 437
386<p> 438<p>
439When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
440</p>
441
442<p>
387As 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
388configuration variables. When you're finished configuring 444configuration variables. You can configure your system to use unicode and
389<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
390</p> 448<p>
449Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
450Edit it to configure your keyboard.
451</p>
391 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>
392</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>
393</section> 534</section>
394</sections> 535</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20