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

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.69

  ViewVC Help
Powered by ViewVC 1.1.20