/[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.24 Revision 1.78
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.24 2004/02/23 16:34:12 vapier 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 $ -->
8 8
9<sections> 9<sections>
10
11<version>2.19</version>
12<date>2006-05-27</date>
13
10<section> 14<section>
11<title>Filesystem Information</title> 15<title>Filesystem Information</title>
12<subsection> 16<subsection>
13<title>What is fstab?</title> 17<title>What is fstab?</title>
14<body> 18<body>
15 19
16<p> 20<p>
17Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
18<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
19(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
20(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
21etc.). 25them or not, etc.)
22</p> 26</p>
23 27
24</body> 28</body>
25</subsection> 29</subsection>
26<subsection> 30<subsection>
46 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
47</li> 51</li>
48<li> 52<li>
49 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
50 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,
51 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
52 listing. Multiple mountoptions are comma-separated. 56 listing. Multiple mountoptions are comma-separated.
53</li> 57</li>
54<li> 58<li>
55 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
56 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).
57</li> 61</li>
58<li> 62<li>
59 The sixth field is used by <c>fsck</c> to determine the order in which 63 The sixth field is used by <c>fsck</c> to determine the order in which
60 filesystems should be <b>check</b>ed if the system wasn't shut down properly. 64 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
61 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 65 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
62 (or <c>0</c> in case a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
63</li> 67</li>
64</ul> 68</ul>
65 69
66<p> 70<p>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
67So 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
68<path>/etc/fstab</path>: 73<path>/etc/fstab</path>:
69</p> 74</p>
70 75
71<pre caption="Opening /etc/fstab"> 76<pre caption="Opening /etc/fstab">
72# <i>nano -w /etc/fstab</i> 77# <i>nano -w /etc/fstab</i>
73</pre> 78</pre>
74 79
75<p> 80<p>
76Let us 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>
77partition. 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
78<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.
79</p> 85</p>
80 86
81<p> 87<p>
82In our default x86 partitioning example <path>/boot</path> is the 88In our default x86 partitioning example <path>/boot</path> is the
83<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.
84be 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:
85would write down:
86</p> 91</p>
87 92
88<pre caption="An example /boot line for /etc/fstab"> 93<pre caption="An example /boot line for /etc/fstab">
89/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.
90</pre> 102</p>
91 103
92<p> 104<p>
93Now, 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>
94option as a mountoption, which results in a faster system since access times 106option as mountoption, which results in a faster system since access times
95aren't registered (you don't need those generally anyway): 107aren't registered (you don't need those generally anyway):
96</p> 108</p>
97 109
98<pre caption="An improved /boot line for /etc/fstab"> 110<pre caption="An improved /boot line for /etc/fstab">
99/dev/hda1 /boot ext2 noauto,noatime 1 2 111/dev/hda1 /boot ext2 defaults,noatime 1 2
100</pre> 112</pre>
101 113
102<p> 114<p>
103If 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
104<path>/boot</path>, <path>/</path> and the swap partition): 116<path>/boot</path>, <path>/</path> and the swap partition):
105</p> 117</p>
106 118
107<pre caption="Three /etc/fstab lines"> 119<pre caption="Three /etc/fstab lines">
108/dev/hda1 /boot ext2 noauto,noatime 1 2 120/dev/hda1 /boot ext2 defaults,noatime 1 2
109/dev/hda2 none swap sw 0 0 121/dev/hda2 none swap sw 0 0
110/dev/hda3 / ext3 noatime 0 1 122/dev/hda3 / ext3 noatime 0 1
111</pre> 123</pre>
112 124
113<p> 125<p>
115(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
116partitions or drives, for those too): 128partitions or drives, for those too):
117</p> 129</p>
118 130
119<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example">
120/dev/hda1 /boot ext2 noauto,noatime 1 2 132/dev/hda1 /boot ext2 defaults,noatime 1 2
121/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
122/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
123 135
124none /proc proc defaults 0 0 136none /proc proc defaults 0 0
125none /dev/shm tmpfs defaults 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
126 138
127/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
128</pre> 140</pre>
129 141
130<p> 142<p>
133<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.
134</p> 146</p>
135 147
136<p> 148<p>
137Now 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
138SPARC-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>
139too: 152too:
140</p> 153</p>
141 154
142<pre caption="Adding openprom filesystem to /etc/fstab"> 155<pre caption="Adding openprom filesystem to /etc/fstab">
143none /proc/openprom openpromfs defaults 0 0 156none /proc/openprom openpromfs defaults 0 0
144</pre> 157</pre>
145 158
146<p> 159<p>
147If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
148</p>
149
150<pre caption="Adding usbfs filesystem to /etc/fstab">
151none /proc/bus/usb usbfs defaults 0 0
152</pre>
153
154<p>
155Reread your <path>/etc/fstab</path>, save and quit to continue. 160Double-check your <path>/etc/fstab</path>, save and quit to continue.
156</p> 161</p>
157 162
158</body> 163</body>
159</subsection> 164</subsection>
160</section> 165</section>
163<subsection> 168<subsection>
164<title>Hostname, Domainname etc.</title> 169<title>Hostname, Domainname etc.</title>
165<body> 170<body>
166 171
167<p> 172<p>
168One 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
169easy, 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
170name 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
171be 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
172<c>tux</c> and domain <c>homenetwork</c>. 177<c>tux</c> and domain <c>homenetwork</c>.
173</p> 178</p>
174 179
175<p> 180<p>
176We 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:
177</p> 182</p>
178 183
179<pre caption="Setting the hostname"> 184<pre caption="Setting the hostname">
180# <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>"
181</pre> 189</pre>
182 190
183<p> 191<p>
184Second we set the domainname: 192Second we set the domainname:
185</p> 193</p>
186 194
187<pre caption="Setting the domainname"> 195<pre caption="Setting the domainname">
188# <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>"
189</pre> 200</pre>
190 201
191<p> 202<p>
192If 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
193one), you need to define that one too: 204one), you need to define that one too:
194</p> 205</p>
195 206
196<pre caption="Setting the NIS domainname"> 207<pre caption="Setting the NIS domainname">
197# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 208# <i>nano -w /etc/conf.d/domainname</i>
198</pre>
199 209
200<p> 210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
201Now add the <c>domainname</c> script to the default runlevel: 211NISDOMAIN="<i>my-nisdomain</i>"
202</p>
203
204<pre caption="Adding domainname to the default runlevel">
205# <i>rc-update add domainname default</i>
206</pre> 212</pre>
207 213
208</body> 214</body>
209</subsection> 215</subsection>
210<subsection> 216<subsection>
211<title>Configuring your Network</title> 217<title>Configuring your Network</title>
212<body> 218<body>
213 219
214<p> 220<p>
215Before 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
216that 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
217just 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
218your Gentoo system permanently. 224your Gentoo system permanently.
219</p> 225</p>
220 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
221<p> 233<p>
222All 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
223a 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
224networking manually. But don't fear, we'll explain everything :) 236networking manually. But don't fear, we'll explain everything. A fully
225</p> 237commented example that covers many different configurations is available in
226 238<path>/etc/conf.d/net.example</path>.
227<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
228First 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
229is used in this example): 249this example):
230</p> 250</p>
231 251
232<pre caption="Opening /etc/conf.d/net for editing"> 252<pre caption="Opening /etc/conf.d/net for editing">
233# <i>nano -w /etc/conf.d/net</i> 253# <i>nano -w /etc/conf.d/net</i>
234</pre> 254</pre>
235 255
236<p> 256<p>
237The first variable you'll find is <c>iface_eth0</c>. It uses the following 257You will see the following file:
238syntax:
239</p>
240
241<pre caption="iface_eth0 syntaxis">
242iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
243</pre>
244
245<p> 258</p>
246If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 259
247to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 260<pre caption="Default /etc/conf.d/net">
248If you need to setup your network manually and you're 261# This blank configuration will automatically use DHCP for any net.*
249not familiar with all the above terms, please read the section on <uri 262# scripts in /etc/init.d. To create a more complete configuration,
250link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 263# please review /etc/conf.d/net.example and save your configuration
251Terminology</uri> if you haven't done so already. 264# in /etc/conf.d/net (this file :]!).
265</pre>
266
252</p> 267<p>
253 268To enter your own IP address, netmask and gateway, you need
269to set both <c>config_eth0</c> and <c>routes_eth0</c>:
254<p> 270</p>
255So let us give three examples; the first one uses DHCP, the second one a static 271
256IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 272<pre caption="Manually setting IP information for eth0">
257gateway 192.168.0.1 while the third one just activates the interface for 273config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
258rp-pppoe usage: 274routes_eth0=( "default gw 192.168.0.1" )
275</pre>
276
259</p> 277<p>
260 278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
261<pre caption="Examples for /etc/conf.d/net"> 279<c>dhcp_eth0</c>:
262<comment>(For DHCP:)</comment>
263iface_eth0="dhcp"
264
265<comment>(For static IP:)</comment>
266iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
267gateway="eth0/192.168.0.1"
268
269<comment>(For rp-pppoe:)</comment>
270iface_eth0="up"
271</pre>
272
273<p> 280</p>
274If you have several network interfaces, create extra <c>iface_eth</c> variables, 281
275like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282<pre caption="Automatically obtaining an IP address for eth0">
276shouldn'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.
277</p> 295</p>
278 296
279<p> 297<p>
280Now save the configuration and exit to continue. 298Now save the configuration and exit to continue.
281</p> 299</p>
285<subsection> 303<subsection>
286<title>Automatically Start Networking at Boot</title> 304<title>Automatically Start Networking at Boot</title>
287<body> 305<body>
288 306
289<p> 307<p>
290To 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
291default 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
292the PCMCIA interfaces are started by the PCMCIA init script. 310the PCMCIA interfaces are started by the PCMCIA init script.
293</p> 311</p>
294 312
295<pre caption="Adding net.eth0 to the default runlevel"> 313<pre caption="Adding net.eth0 to the default runlevel">
314<title>Writing Down Network Information</title> 332<title>Writing Down Network Information</title>
315<body> 333<body>
316 334
317<p> 335<p>
318You 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
319<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
320for 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.
321internal 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
322<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 340set up your own internal DNS system.
323open <path>/etc/hosts</path> and fill in the values:
324</p> 341</p>
325 342
326<pre caption="Opening /etc/hosts"> 343<pre caption="Opening /etc/hosts">
327# <i>nano -w /etc/hosts</i> 344# <i>nano -w /etc/hosts</i>
328</pre> 345</pre>
329 346
330<pre caption="Filling in the networking information"> 347<pre caption="Filling in the networking information">
331127.0.0.1 localhost 348<comment>(This defines the current system)</comment>
349127.0.0.1 tux.homenetwork tux localhost
350
351<comment>(Define extra systems on your network,
352they need to have a static IP to be defined this way.)</comment>
332192.168.0.5 jenny.homenetwork jenny 353192.168.0.5 jenny.homenetwork jenny
333192.168.0.6 benny.homenetwork benny 354192.168.0.6 benny.homenetwork benny
334192.168.0.7 tux.homenetwork tux
335</pre>
336
337<p>
338If your system is the only system (or the nameservers handle all name
339resolution) a single line is sufficient:
340</p>
341
342<pre caption="/etc/hosts for lonely or fully integrated PCs">
343127.0.0.1 localhost tux
344</pre> 355</pre>
345 356
346<p> 357<p>
347Save and exit the editor to continue. 358Save and exit the editor to continue.
348</p> 359</p>
357</subsection> 368</subsection>
358<subsection> 369<subsection>
359<title>Optional: Get PCMCIA Working</title> 370<title>Optional: Get PCMCIA Working</title>
360<body> 371<body>
361 372
373<note>
374pcmcia-cs is only available for x86, amd64 and ppc platforms.
375</note>
376
362<p> 377<p>
363PCMCIA-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:
364</p> 382</p>
365 383
366<pre caption="Installing pcmcia-cs"> 384<pre caption="Installing pcmcia-cs">
367# <i>emerge --usepkg pcmcia-cs</i> 385# <i>USE="-X" emerge pcmcia-cs</i>
368</pre> 386</pre>
369 387
370<p> 388<p>
371When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> 389When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
372runlevel: 390runlevel:
379</body> 397</body>
380</subsection> 398</subsection>
381</section> 399</section>
382<section> 400<section>
383<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>
384<body> 427<body>
385 428
386<p> 429<p>
387Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 430Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
388Open 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 :)
391<pre caption="Opening /etc/rc.conf"> 434<pre caption="Opening /etc/rc.conf">
392# <i>nano -w /etc/rc.conf</i> 435# <i>nano -w /etc/rc.conf</i>
393</pre> 436</pre>
394 437
395<p> 438<p>
439When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
440</p>
441
442<p>
396As 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
397configuration variables. Take special care with the <c>KEYMAP</c> setting: if 444configuration variables. You can configure your system to use unicode and
398you select the wrong <c>KEYMAP</c> you will get weird results when typing on 445define your default editor and your display manager (like gdm or kdm).
399your keyboard. 446</p>
447
448<p>
449Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
450Edit it to configure your keyboard.
451</p>
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.
400</p> 460</p>
401 461
402<note> 462<note>
403Users of USB-based SPARC systems and SPARC clones might need to select an i386 463Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
404keymap (such as "us") instead of "sunkeymap". 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>.
405</note> 468</note>
406 469
407<p> 470<p>
408When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 471When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
409continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 472exit.
473</p>
474
410</p> 475<p>
476Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
477according to your needs.
478</p>
411 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>
412</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>
413</section> 534</section>
414</sections> 535</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20