/[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.78 Revision 1.101
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/2.5 --> 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.78 2006/05/27 13:02:15 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.101 2009/08/05 15:25:23 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<abstract>
12You need to edit some important configuration files. In this chapter
13you receive an overview of these files and an explanation on how to
14proceed.
15</abstract>
16
11<version>2.19</version> 17<version>9.4</version>
12<date>2006-05-27</date> 18<date>2009-08-05</date>
13 19
14<section> 20<section>
15<title>Filesystem Information</title> 21<title>Filesystem Information</title>
16<subsection> 22<subsection>
17<title>What is fstab?</title> 23<title>What is fstab?</title>
18<body> 24<body>
19 25
20<p> 26<p>
21Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 28<path>/etc/fstab</path>. This file contains the mount points of those partitions
23(where they are seen in the file system structure), how they should be mounted 29(where they are seen in the file system structure), how they should be mounted
24and with what special options (automatically or not, whether users can mount 30and with what special options (automatically or not, whether users can mount
25them or not, etc.) 31them or not, etc.)
26</p> 32</p>
27 33
41<li> 47<li>
42 The first field shows the <b>partition</b> described (the path to the device 48 The first field shows the <b>partition</b> described (the path to the device
43 file) 49 file)
44</li> 50</li>
45<li> 51<li>
46 The second field shows the <b>mountpoint</b> at which the partition should be 52 The second field shows the <b>mount point</b> at which the partition should be
47 mounted 53 mounted
48</li> 54</li>
49<li> 55<li>
50 The third field shows the <b>filesystem</b> used by the partition 56 The third field shows the <b>filesystem</b> used by the partition
51</li> 57</li>
52<li> 58<li>
53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 59 The fourth field shows the <b>mount options</b> used by <c>mount</c> when it
54 wants to mount the partition. As every filesystem has its own mountoptions, 60 wants to mount the partition. As every filesystem has its own mount options,
55 you are encouraged to read the mount man page (<c>man mount</c>) for a full 61 you are encouraged to read the mount man page (<c>man mount</c>) for a full
56 listing. Multiple mountoptions are comma-separated. 62 listing. Multiple mount options are comma-separated.
57</li> 63</li>
58<li> 64<li>
59 The fifth field is used by <c>dump</c> to determine if the partition needs to 65 The fifth field is used by <c>dump</c> to determine if the partition needs to
60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 66 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
61</li> 67</li>
65 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 71 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
66 (or <c>0</c> if a filesystem check isn't necessary). 72 (or <c>0</c> if a filesystem check isn't necessary).
67</li> 73</li>
68</ul> 74</ul>
69 75
70<p> 76<impo>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid 77The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72fstab file</e>, so start <c>nano</c> (or your favorite editor) to create your 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
73<path>/etc/fstab</path>: 79</impo>
74</p>
75 80
76<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
77# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
78</pre> 83</pre>
79 84
85</body>
86<body test="func:keyval('/boot')">
87
80<p> 88<p>
81Let us take a look at how we write down the options for the <path>/boot</path> 89Let us take a look at how we write down the options for the <path>/boot</path>
82partition. This is just an example, so if your architecture doesn't require a 90partition. This is just an example, if you didn't or couldn't create a
83<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it 91<path>/boot</path>, don't copy it.
84verbatim.
85</p>
86
87<p> 92</p>
93
94<p>
88In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
89<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 96usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
90It needs to be checked during boot, so we would write down: 97filesystem. It needs to be checked during boot, so we would write down:
91</p> 98</p>
92 99
93<pre caption="An example /boot line for /etc/fstab"> 100<pre caption="An example /boot line for /etc/fstab">
94/dev/hda1 /boot ext2 defaults 1 2 101<keyval id="/boot"/> /boot ext2 defaults 1 2
95</pre> 102</pre>
96 103
97<p> 104<p>
98Some users don't want their <path>/boot</path> partition to be mounted 105Some users don't want their <path>/boot</path> partition to be mounted
99automatically to improve their system's security. Those people should 106automatically to improve their system's security. Those people should
100substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 107substitute <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. 108manually mount this partition every time you want to use it.
102</p> 109</p>
103 110
104<p> 111</body>
105Now, to improve performance, most users would want to add the <c>noatime</c> 112<body>
106option as mountoption, which results in a faster system since access times 113
107aren't registered (you don't need those generally anyway):
108</p> 114<p>
109 115Add the rules that match your partitioning scheme and append rules for
110<pre caption="An improved /boot line for /etc/fstab"> 116your CD-ROM drive(s), and of course, if you have other partitions or drives,
111/dev/hda1 /boot ext2 defaults,noatime 1 2 117for those too.
112</pre>
113
114<p> 118</p>
115If we continue with this, we would end up with the following three lines (for 119
116<path>/boot</path>, <path>/</path> and the swap partition):
117</p> 120<p>
121Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
122</p>
118 123
119<pre caption="Three /etc/fstab lines"> 124<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
120/dev/hda1 /boot ext2 defaults,noatime 1 2 125<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
121/dev/hda2 none swap sw 0 0 126/dev/sda3 none swap sw 0 0
122/dev/hda3 / ext3 noatime 0 1 127/dev/sda4 / ext3 noatime 0 1
123</pre>
124 128
125<p> 129/dev/cdrom /mnt/cdrom auto noauto,user 0 0
126To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
127(required) and for your CD-ROM drive (and of course, if you have other
128partitions or drives, for those too):
129</p> 130</pre>
130 131
131<pre caption="A full /etc/fstab example"> 132<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'">
132/dev/hda1 /boot ext2 defaults,noatime 1 2 133<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
133/dev/hda2 none swap sw 0 0 134/dev/sda2 none swap sw 0 0
134/dev/hda3 / ext3 noatime 0 1 135/dev/sda3 / ext3 noatime 0 1
135 136
136none /proc proc defaults 0 0 137/dev/cdrom /mnt/cdrom auto noauto,user 0 0
137none /dev/shm tmpfs nodev,nosuid,noexec 0 0 138</pre>
138 139
140<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
141/dev/sda1 / ext3 noatime 0 1
142/dev/sda2 none swap sw 0 0
143/dev/sda4 /usr ext3 noatime 0 2
144/dev/sda5 /var ext3 noatime 0 2
145/dev/sda6 /home ext3 noatime 0 2
146
147<comment># You must add the rules for openprom</comment>
148openprom /proc/openprom openpromfs defaults 0 0
149
139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 150/dev/cdrom /mnt/cdrom auto noauto,user 0 0
151</pre>
152
153<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or
154func:keyval('arch')='PPC64'">
155/dev/sda4 / ext3 noatime 0 1
156/dev/sda3 none swap sw 0 0
157
158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
140</pre> 159</pre>
141 160
142<p> 161<p>
143<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 162<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
144removable media as they can be created with one of many filesystems) and 163removable media as they can be created with one of many filesystems) and
145<c>user</c> makes it possible for non-root users to mount the CD. 164<c>user</c> makes it possible for non-root users to mount the CD.
146</p> 165</p>
147 166
148<p> 167<p>
149Now use the above example to create your <path>/etc/fstab</path>. If you are a 168To improve performance, most users would want to add the <c>noatime</c>
150<b>SPARC</b>-user, you should add the following line to your 169mount option, which results in a faster system since access times
151<path>/etc/fstab</path> 170aren't registered (you don't need those generally anyway).
152too:
153</p>
154
155<pre caption="Adding openprom filesystem to /etc/fstab">
156none /proc/openprom openpromfs defaults 0 0
157</pre> 171</p>
158 172
159<p> 173<p>
160Double-check your <path>/etc/fstab</path>, save and quit to continue. 174Double-check your <path>/etc/fstab</path>, save and quit to continue.
161</p> 175</p>
162 176
164</subsection> 178</subsection>
165</section> 179</section>
166<section> 180<section>
167<title>Networking Information</title> 181<title>Networking Information</title>
168<subsection> 182<subsection>
169<title>Hostname, Domainname etc.</title> 183<title>Host name, Domainname, etc</title>
170<body> 184<body>
171 185
172<p> 186<p>
173One of the choices the user has to make is name his/her PC. This seems to be 187One of the choices the user has to make is name his/her PC. This seems to be
174quite easy, but <e>lots</e> of users are having difficulties finding the 188quite easy, but <e>lots</e> of users are having difficulties finding the
175appropriate name for their Linux-pc. To speed things up, know that any name you 189appropriate name for their Linux-pc. To speed things up, know that any name you
176choose can be changed afterwards. For all we care, you can just call your system 190choose can be changed afterwards. For all we care, you can just call your system
177<c>tux</c> and domain <c>homenetwork</c>. 191<c>tux</c> and domain <c>homenetwork</c>.
178</p> 192</p>
179 193
180<p>
181We use these values in the next examples. First we set the hostname:
182</p>
183
184<pre caption="Setting the hostname"> 194<pre caption="Setting the host name">
185# <i>nano -w /etc/conf.d/hostname</i> 195# <i>nano -w /etc/conf.d/hostname</i>
186 196
187<comment>(Set the HOSTNAME variable to your hostname)</comment> 197<comment>(Set the HOSTNAME variable to your host name)</comment>
188HOSTNAME="<i>tux</i>" 198HOSTNAME="<i>tux</i>"
189</pre> 199</pre>
190 200
191<p> 201<p>
192Second we set the domainname: 202Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
203You only need a domain if your ISP or network administrator says so, or if you
204have a DNS server but not a DHCP server. You don't need to worry about DNS or
205domainnames if your networking is setup for DHCP.
193</p> 206</p>
194 207
195<pre caption="Setting the domainname"> 208<pre caption="Setting the domainname">
196# <i>nano -w /etc/conf.d/domainname</i> 209# <i>nano -w /etc/conf.d/net</i>
197 210
198<comment>(Set the DNSDOMAIN variable to your domain name)</comment> 211<comment>(Set the dns_domain variable to your domain name)</comment>
199DNSDOMAIN="<i>homenetwork</i>" 212dns_domain_lo="<i>homenetwork</i>"
200</pre> 213</pre>
214
215<note>
216If you choose not to set a domainname, you can get rid of the "This is
217hostname.(none)" messages at your login screen by editing
218<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
219</note>
201 220
202<p> 221<p>
203If you have a NIS domain (if you don't know what that is, then you don't have 222If you have a NIS domain (if you don't know what that is, then you don't have
204one), you need to define that one too: 223one), you need to define that one too:
205</p> 224</p>
206 225
207<pre caption="Setting the NIS domainname"> 226<pre caption="Setting the NIS domainname">
208# <i>nano -w /etc/conf.d/domainname</i> 227# <i>nano -w /etc/conf.d/net</i>
209 228
210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment> 229<comment>(Set the nis_domain variable to your NIS domain name)</comment>
211NISDOMAIN="<i>my-nisdomain</i>" 230nis_domain_lo="<i>my-nisdomain</i>"
212</pre> 231</pre>
232
233<note>
234For more information on configuring DNS and NIS, please read the examples
235provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
236<c>openresolv</c> to help manage your DNS/NIS setup.
237</note>
213 238
214</body> 239</body>
215</subsection> 240</subsection>
216<subsection> 241<subsection>
217<title>Configuring your Network</title> 242<title>Configuring your Network</title>
237commented example that covers many different configurations is available in 262commented example that covers many different configurations is available in
238<path>/etc/conf.d/net.example</path>. 263<path>/etc/conf.d/net.example</path>.
239</p> 264</p>
240 265
241<p> 266<p>
242DHCP is used by default and does not require any further configuration. 267DHCP is used by default. For DHCP to work, you will need to install a DHCP
268client. This is described later in <uri
269link="?part=1&amp;chap=9#networking-tools">Installing Necessary System
270Tools</uri>. Do not forget to install a DHCP client.
243</p> 271</p>
244 272
245<p> 273<p>
246If you need to configure your network connection either because you need 274If you need to configure your network connection either because you need
247specific DHCP options or because you do not use DHCP at all, open 275specific DHCP options or because you do not use DHCP at all, open
269to set both <c>config_eth0</c> and <c>routes_eth0</c>: 297to set both <c>config_eth0</c> and <c>routes_eth0</c>:
270</p> 298</p>
271 299
272<pre caption="Manually setting IP information for eth0"> 300<pre caption="Manually setting IP information for eth0">
273config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" ) 301config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
274routes_eth0=( "default gw 192.168.0.1" ) 302routes_eth0=( "default via 192.168.0.1" )
275</pre> 303</pre>
276 304
277<p> 305<p>
278To use DHCP and add specific DHCP options, define <c>config_eth0</c> and 306To use DHCP, define <c>config_eth0</c>:
279<c>dhcp_eth0</c>:
280</p> 307</p>
281 308
282<pre caption="Automatically obtaining an IP address for eth0"> 309<pre caption="Automatically obtaining an IP address for eth0">
283config_eth0=( "dhcp" ) 310config_eth0=( "dhcp" )
284dhcp_eth0="nodns nontp nonis"
285</pre> 311</pre>
286 312
287<p> 313<p>
288Please read <path>/etc/conf.d/net.example</path> for a list of all available 314Please read <path>/etc/conf.d/net.example</path> for a list of all available
289options. 315options. Be sure to also read your DHCP client manpage if you need to set
316specific DHCP options.
290</p> 317</p>
291 318
292<p> 319<p>
293If you have several network interfaces repeat the above steps for 320If you have several network interfaces repeat the above steps for
294<c>config_eth1</c>, <c>config_eth2</c>, etc. 321<c>config_eth1</c>, <c>config_eth2</c>, etc.
304<title>Automatically Start Networking at Boot</title> 331<title>Automatically Start Networking at Boot</title>
305<body> 332<body>
306 333
307<p> 334<p>
308To have your network interfaces activated at boot, you need to add them to the 335To have your network interfaces activated at boot, you need to add them to the
309default runlevel. If you have PCMCIA interfaces you should skip this action as 336default runlevel.
310the PCMCIA interfaces are started by the PCMCIA init script.
311</p> 337</p>
312 338
313<pre caption="Adding net.eth0 to the default runlevel"> 339<pre caption="Adding net.eth0 to the default runlevel">
314# <i>rc-update add net.eth0 default</i> 340# <i>rc-update add net.eth0 default</i>
315</pre> 341</pre>
320use <c>ln</c> to do this: 346use <c>ln</c> to do this:
321</p> 347</p>
322 348
323<pre caption="Creating extra initscripts"> 349<pre caption="Creating extra initscripts">
324# <i>cd /etc/init.d</i> 350# <i>cd /etc/init.d</i>
325# <i>ln -s net.eth0 net.eth1</i> 351# <i>ln -s net.lo net.eth1</i>
326# <i>rc-update add net.eth1 default</i> 352# <i>rc-update add net.eth1 default</i>
327</pre> 353</pre>
328 354
329</body> 355</body>
330</subsection> 356</subsection>
332<title>Writing Down Network Information</title> 358<title>Writing Down Network Information</title>
333<body> 359<body>
334 360
335<p> 361<p>
336You now need to inform Linux about your network. This is defined in 362You now need to inform Linux about your network. This is defined in
337<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for 363<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
338hosts that aren't resolved by your nameserver. You need to define your system. 364hosts that aren't resolved by your nameserver. You need to define your system.
339You may also want to define other systems on your network if you don't want to 365You may also want to define other systems on your network if you don't want to
340set up your own internal DNS system. 366set up your own internal DNS system.
341</p> 367</p>
342 368
356 382
357<p> 383<p>
358Save and exit the editor to continue. 384Save and exit the editor to continue.
359</p> 385</p>
360 386
361<p> 387<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
362If you don't have PCMCIA, you can now continue with <uri 388If you don't have PCMCIA, you can now continue with <uri
363link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 389link="#sysinfo">System Information</uri>. PCMCIA-users should read the
364following topic on PCMCIA. 390following topic on PCMCIA.
365</p> 391</p>
366 392
367</body> 393</body>
368</subsection> 394</subsection>
369<subsection> 395<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
370<title>Optional: Get PCMCIA Working</title> 396<title>Optional: Get PCMCIA Working</title>
371<body> 397<body>
372 398
373<note>
374pcmcia-cs is only available for x86, amd64 and ppc platforms.
375</note>
376
377<p> 399<p>
378PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 400PCMCIA users should first install the <c>pcmciautils</c> package.
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:
382</p> 401</p>
383 402
384<pre caption="Installing pcmcia-cs"> 403<pre caption="Installing pcmciautils">
385# <i>USE="-X" emerge pcmcia-cs</i> 404# <i>emerge pcmciautils</i>
386</pre>
387
388<p>
389When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
390runlevel:
391</p>
392
393<pre caption="Adding pcmcia to the default runlevel">
394# <i>rc-update add pcmcia default</i>
395</pre> 405</pre>
396 406
397</body> 407</body>
398</subsection> 408</subsection>
399</section> 409</section>
400<section> 410
411<section id="sysinfo">
401<title>System Information</title> 412<title>System Information</title>
402<subsection> 413<subsection>
403<title>Root Password</title> 414<title>Root Password</title>
404<body> 415<body>
405 416
407First we set the root password by typing: 418First we set the root password by typing:
408</p> 419</p>
409 420
410<pre caption="Setting the root password"> 421<pre caption="Setting the root password">
411# <i>passwd</i> 422# <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> 423</pre>
422 424
423</body> 425</body>
424</subsection> 426</subsection>
425<subsection> 427<subsection>
457<p> 459<p>
458Take special care with the <c>KEYMAP</c> variable. If you select the wrong 460Take 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. 461<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
460</p> 462</p>
461 463
462<note> 464<note test="substring(func:keyval('arch'),1,3)='PPC'">
463Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 465PPC uses x86 keymaps on most systems.
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> 466</note>
469 467
470<p> 468<p>
471When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and 469When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
472exit. 470exit.
480<pre caption="Opening /etc/conf.d/clock"> 478<pre caption="Opening /etc/conf.d/clock">
481# <i>nano -w /etc/conf.d/clock</i> 479# <i>nano -w /etc/conf.d/clock</i>
482</pre> 480</pre>
483 481
484<p> 482<p>
485If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to 483If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
486the file. Otherwise you will notice some clock skew. Furthermore, Windows 484to the file. Otherwise you will notice some clock skew.
487assumes that your hardware clock uses local time, so if you want to dualboot, 485</p>
488you should set this variable appropriately, otherwise your clock will go crazy. 486
487<p>
488You should define the timezone that you previously copied to
489<path>/etc/localtime</path> so that further upgrades of the
490<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
491automatically. For instance, if you used the GMT timezone, you would add
492<c>TIMEZONE="GMT"</c>
489</p> 493</p>
490 494
491<p> 495<p>
492When you're finished configuring <path>/etc/conf.d/clock</path>, save and 496When you're finished configuring <path>/etc/conf.d/clock</path>, save and
493exit. 497exit.
494</p> 498</p>
495 499
500<p test="not(func:keyval('arch')='PPC64')">
501Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
502Tools</uri>.
496<p> 503</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 504
501</body> 505</body>
502</subsection>
503<subsection> 506</subsection>
507<subsection test="func:keyval('arch')='PPC64'">
504<title>Configuring the Console</title> 508<title>Configuring the Console</title>
505<body> 509<body>
506 510
507<note>
508The following section applies to the IBM PPC64 hardware platforms.
509</note>
510
511<p> 511<p>
512If you are running Gentoo on IBM PPC64 hardware and using a virtual console 512If you are using a virtual console, you must uncomment the appropriate line in
513you must uncomment the appropriate line in <path>/etc/inittab</path> for the 513<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
514virtual console to spawn a login prompt.
515</p> 514</p>
516 515
517<pre caption="Enabling hvc or hvsi support in /etc/inittab"> 516<pre caption="Enabling hvc or hvsi support in /etc/inittab">
518hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 517hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
519hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 518hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

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

  ViewVC Help
Powered by ViewVC 1.1.20