/[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.60 Revision 1.100
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.60 2005/04/29 15:30:23 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.100 2009/02/11 08:40:54 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.2</version> 17<version>9.3</version>
12<date>2005-04-20</date> 18<date>2009-02-11</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 no valid fstab 77The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72file</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 <b>PPC</b>), don't copy it verbatim. 91<path>/boot</path>, don't copy it.
84</p>
85
86<p> 92</p>
93
94<p>
87In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
88<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 96usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
89It needs to be checked during boot, so we would write down: 97filesystem. It needs to be checked during boot, so we would write down:
90</p> 98</p>
91 99
92<pre caption="An example /boot line for /etc/fstab"> 100<pre caption="An example /boot line for /etc/fstab">
93/dev/hda1 /boot ext2 defaults 1 2 101<keyval id="/boot"/> /boot ext2 defaults 1 2
94</pre> 102</pre>
95 103
96<p> 104<p>
97Some 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
98automatically to improve their system's security. Those people should 106automatically to improve their system's security. Those people should
99substitute <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
100manually mount this partition every time you want to use it. 108manually mount this partition every time you want to use it.
101</p> 109</p>
102 110
103<p> 111</body>
104Now, to improve performance, most users would want to add the <c>noatime</c> 112<body>
105option as mountoption, which results in a faster system since access times 113
106aren't registered (you don't need those generally anyway):
107</p> 114<p>
108 115Add the rules that match your partitioning scheme and append rules for
109<pre caption="An improved /boot line for /etc/fstab"> 116your CD-ROM drive(s), and of course, if you have other partitions or drives,
110/dev/hda1 /boot ext2 defaults,noatime 1 2 117for those too.
111</pre>
112
113<p> 118</p>
114If we continue with this, we would end up with the following three lines (for 119
115<path>/boot</path>, <path>/</path> and the swap partition):
116</p> 120<p>
121Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
122</p>
117 123
118<pre caption="Three /etc/fstab lines"> 124<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
119/dev/hda1 /boot ext2 defaults,noatime 1 2 125<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
120/dev/hda2 none swap sw 0 0 126/dev/sda3 none swap sw 0 0
121/dev/hda3 / ext3 noatime 0 1 127/dev/sda4 / ext3 noatime 0 1
122</pre>
123 128
124<p> 129/dev/cdrom /mnt/cdrom auto noauto,user 0 0
125To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
126(required) and for your CD-ROM drive (and of course, if you have other
127partitions or drives, for those too):
128</p> 130</pre>
129 131
130<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'">
131/dev/hda1 /boot ext2 defaults,noatime 1 2 133<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132/dev/hda2 none swap sw 0 0 134/dev/sda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 135/dev/sda3 / ext3 noatime 0 1
134 136
135none /proc proc defaults 0 0 137/dev/cdrom /mnt/cdrom auto noauto,user 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 138</pre>
137 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
138/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
139</pre> 159</pre>
140 160
141<p> 161<p>
142<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
143removable 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
144<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.
145</p> 165</p>
146 166
147<p> 167<p>
148Now 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>
149<b>SPARC</b>-user, you should add the following line to your 169mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 170aren't registered (you don't need those generally anyway).
151too:
152</p>
153
154<pre caption="Adding openprom filesystem to /etc/fstab">
155none /proc/openprom openpromfs defaults 0 0
156</pre> 171</p>
157 172
158<p> 173<p>
159Double-check your <path>/etc/fstab</path>, save and quit to continue. 174Double-check your <path>/etc/fstab</path>, save and quit to continue.
160</p> 175</p>
161 176
163</subsection> 178</subsection>
164</section> 179</section>
165<section> 180<section>
166<title>Networking Information</title> 181<title>Networking Information</title>
167<subsection> 182<subsection>
168<title>Hostname, Domainname etc.</title> 183<title>Host name, Domainname, etc</title>
169<body> 184<body>
170 185
171<p> 186<p>
172One 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
173quite 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
174appropriate 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
175choose 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
176<c>tux</c> and domain <c>homenetwork</c>. 191<c>tux</c> and domain <c>homenetwork</c>.
177</p> 192</p>
178 193
179<p>
180We use these values in the next examples. First we set the hostname:
181</p>
182
183<pre caption="Setting the hostname"> 194<pre caption="Setting the host name">
184# <i>echo tux &gt; /etc/hostname</i> 195# <i>nano -w /etc/conf.d/hostname</i>
185</pre>
186 196
197<comment>(Set the HOSTNAME variable to your host name)</comment>
198HOSTNAME="<i>tux</i>"
199</pre>
200
187<p> 201<p>
188Second 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.
189</p> 206</p>
190 207
191<pre caption="Setting the domainname"> 208<pre caption="Setting the domainname">
192# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 209# <i>nano -w /etc/conf.d/net</i>
210
211<comment>(Set the dns_domain variable to your domain name)</comment>
212dns_domain_lo="<i>homenetwork</i>"
193</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>
194 220
195<p> 221<p>
196If 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
197one), you need to define that one too: 223one), you need to define that one too:
198</p> 224</p>
199 225
200<pre caption="Setting the NIS domainname"> 226<pre caption="Setting the NIS domainname">
201# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 227# <i>nano -w /etc/conf.d/net</i>
202</pre>
203 228
204<p> 229<comment>(Set the nis_domain variable to your NIS domain name)</comment>
205Now add the <c>domainname</c> script to the default runlevel: 230nis_domain_lo="<i>my-nisdomain</i>"
206</p> 231</pre>
207 232
208<pre caption="Adding domainname to the default runlevel"> 233<note>
209# <i>rc-update add domainname default</i> 234For more information on configuring DNS and NIS, please read the examples
210</pre> 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>
211 238
212</body> 239</body>
213</subsection> 240</subsection>
214<subsection> 241<subsection>
215<title>Configuring your Network</title> 242<title>Configuring your Network</title>
216<body> 243<body>
217 244
218<p> 245<p>
219Before you get that "Hey, we've had that already"-feeling, you should remember 246Before you get that "Hey, we've had that already"-feeling, you should remember
220that the networking you set up in the beginning of the gentoo installation was 247that the networking you set up in the beginning of the Gentoo installation was
221just for the installation. Right now you are going to configure networking for 248just for the installation. Right now you are going to configure networking for
222your Gentoo system permanently. 249your Gentoo system permanently.
223</p> 250</p>
224 251
252<note>
253More detailed information about networking, including advanced topics like
254bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
255link="?part=4">Gentoo Network Configuration</uri> section.
256</note>
257
225<p> 258<p>
226All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 259All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
227a straightforward yet not intuitive syntax if you don't know how to set up 260a straightforward yet not intuitive syntax if you don't know how to set up
228networking manually. But don't fear, we'll explain everything :) 261networking manually. But don't fear, we'll explain everything. A fully
229</p> 262commented example that covers many different configurations is available in
230 263<path>/etc/conf.d/net.example</path>.
231<p> 264</p>
265
266<p>
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.
271</p>
272
273<p>
274If you need to configure your network connection either because you need
275specific DHCP options or because you do not use DHCP at all, open
232First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 276<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233is used in this example): 277this example):
234</p> 278</p>
235 279
236<pre caption="Opening /etc/conf.d/net for editing"> 280<pre caption="Opening /etc/conf.d/net for editing">
237# <i>nano -w /etc/conf.d/net</i> 281# <i>nano -w /etc/conf.d/net</i>
238</pre> 282</pre>
239 283
240<!-- Old baselayout - current stable -->
241
242<p>
243The first variable you'll find is <c>iface_eth0</c>. It uses the following
244syntax:
245</p> 284<p>
246 285You will see the following file:
247<pre caption="iface_eth0 syntaxis">
248iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
249</pre>
250
251<p> 286</p>
252If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 287
253to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 288<pre caption="Default /etc/conf.d/net">
254If you need to set up your network manually and you're 289# This blank configuration will automatically use DHCP for any net.*
255not familiar with all the above terms, please read the section on <uri 290# scripts in /etc/init.d. To create a more complete configuration,
256link="?part=1&amp;chap=3#network_term">Understanding Network 291# please review /etc/conf.d/net.example and save your configuration
257Terminology</uri> if you haven't done so already. 292# in /etc/conf.d/net (this file :]!).
293</pre>
294
258</p> 295<p>
259 296To enter your own IP address, netmask and gateway, you need
297to set both <c>config_eth0</c> and <c>routes_eth0</c>:
260<p> 298</p>
261So let us give three examples; the first one uses DHCP, the second one a static 299
262IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 300<pre caption="Manually setting IP information for eth0">
263gateway 192.168.0.1 while the third one just activates the interface for 301config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
264rp-pppoe usage: 302routes_eth0=( "default via 192.168.0.1" )
303</pre>
304
265</p> 305<p>
266 306To use DHCP, define <c>config_eth0</c>:
267<pre caption="Examples for /etc/conf.d/net">
268<comment>(For DHCP)</comment>
269iface_eth0="dhcp"
270<comment># Some network admins require that you use the</comment>
271<comment># hostname and domainname provided by the DHCP server.</comment>
272<comment># In that case, add the following to let dhcpcd use them.</comment>
273<comment># That will override your own hostname and domainname definitions.</comment>
274dhcpcd_eth0="-HD"
275<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
276<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
277dhcpcd_eth0="-N"
278
279<comment>(For static IP)</comment>
280iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
281gateway="eth0/192.168.0.1"
282
283<comment>(For rp-pppoe)</comment>
284iface_eth0="up"
285</pre>
286
287<p> 307</p>
288If you have several network interfaces, create extra <c>iface_eth</c> variables,
289like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
290shouldn't be reproduced as you can only set one gateway per computer.
291</p>
292 308
293<!-- New baselayout - current testing
294
295<p>
296The first variable you'll find is called <c>config_eth0</c>. As you can probably
297imagine, this variable configured the eth0 network interface. If the interface
298needs to automatically obtain an IP through DHCP, you should set it like so:
299</p>
300
301<pre caption="Automatically obtaining an IP for eth0"> 309<pre caption="Automatically obtaining an IP address for eth0">
302config_eth0=( "dhcp" ) 310config_eth0=( "dhcp" )
303</pre> 311</pre>
304 312
305<p> 313<p>
306However, if you have to enter your own IP address, netmask and gateway, you need 314Please read <path>/etc/conf.d/net.example</path> for a list of all available
307to set both <c>config_eth0</c> and <c>routes_eth0</c>: 315options. Be sure to also read your DHCP client manpage if you need to set
308</p> 316specific DHCP options.
309
310<pre caption="Manually setting IP information for eth0">
311config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
312routes_eth0=( "default gw 192.168.0.1" )
313</pre> 317</p>
314 318
315<p> 319<p>
316If you have several network interfaces repeat the above steps for 320If you have several network interfaces repeat the above steps for
317<c>config_eth1</c>, <c>config_eth2</c>, etc. 321<c>config_eth1</c>, <c>config_eth2</c>, etc.
318</p> 322</p>
319 323
320-->
321
322<p> 324<p>
323Now save the configuration and exit to continue. 325Now save the configuration and exit to continue.
324</p> 326</p>
325 327
326</body> 328</body>
329<title>Automatically Start Networking at Boot</title> 331<title>Automatically Start Networking at Boot</title>
330<body> 332<body>
331 333
332<p> 334<p>
333To 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
334default runlevel. If you have PCMCIA interfaces you should skip this action as 336default runlevel.
335the PCMCIA interfaces are started by the PCMCIA init script.
336</p> 337</p>
337 338
338<pre caption="Adding net.eth0 to the default runlevel"> 339<pre caption="Adding net.eth0 to the default runlevel">
339# <i>rc-update add net.eth0 default</i> 340# <i>rc-update add net.eth0 default</i>
340</pre> 341</pre>
345use <c>ln</c> to do this: 346use <c>ln</c> to do this:
346</p> 347</p>
347 348
348<pre caption="Creating extra initscripts"> 349<pre caption="Creating extra initscripts">
349# <i>cd /etc/init.d</i> 350# <i>cd /etc/init.d</i>
350# <i>ln -s net.eth0 net.eth1</i> 351# <i>ln -s net.lo net.eth1</i>
351# <i>rc-update add net.eth1 default</i> 352# <i>rc-update add net.eth1 default</i>
352</pre> 353</pre>
353 354
354</body> 355</body>
355</subsection> 356</subsection>
357<title>Writing Down Network Information</title> 358<title>Writing Down Network Information</title>
358<body> 359<body>
359 360
360<p> 361<p>
361You 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
362<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 363<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
363for hosts that aren't resolved by your nameserver. For instance, if your 364hosts that aren't resolved by your nameserver. You need to define your system.
364internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 365You may also want to define other systems on your network if you don't want to
365<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 366set up your own internal DNS system.
366open <path>/etc/hosts</path> and fill in the values:
367</p> 367</p>
368 368
369<pre caption="Opening /etc/hosts"> 369<pre caption="Opening /etc/hosts">
370# <i>nano -w /etc/hosts</i> 370# <i>nano -w /etc/hosts</i>
371</pre> 371</pre>
372 372
373<pre caption="Filling in the networking information"> 373<pre caption="Filling in the networking information">
374127.0.0.1 localhost 374<comment>(This defines the current system)</comment>
375127.0.0.1 tux.homenetwork tux localhost
376
377<comment>(Define extra systems on your network,
378they need to have a static IP to be defined this way.)</comment>
375192.168.0.5 jenny.homenetwork jenny 379192.168.0.5 jenny.homenetwork jenny
376192.168.0.6 benny.homenetwork benny 380192.168.0.6 benny.homenetwork benny
377192.168.0.7 tux.homenetwork tux
378</pre>
379
380<p>
381If your system is the only system (or the nameservers handle all name
382resolution) a single line is sufficient. For instance, if you want to call your
383system <c>tux</c>:
384</p>
385
386<pre caption="/etc/hosts for lonely or fully integrated PCs">
387127.0.0.1 localhost tux
388</pre> 381</pre>
389 382
390<p> 383<p>
391Save and exit the editor to continue. 384Save and exit the editor to continue.
392</p> 385</p>
393 386
394<p> 387<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
395If you don't have PCMCIA, you can now continue with <uri 388If you don't have PCMCIA, you can now continue with <uri
396link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 389link="#sysinfo">System Information</uri>. PCMCIA-users should read the
397following topic on PCMCIA. 390following topic on PCMCIA.
398</p> 391</p>
399 392
400</body> 393</body>
401</subsection> 394</subsection>
402<subsection> 395<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
403<title>Optional: Get PCMCIA Working</title> 396<title>Optional: Get PCMCIA Working</title>
404<body> 397<body>
405 398
406<note>
407pcmcia-cs is only available for x86, amd64 and ppc platforms.
408</note>
409
410<p> 399<p>
411PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 400PCMCIA users should first install the <c>pcmciautils</c> package.
412includes users who will be working with a 2.6 kernel (even though they won't be
413using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
414to avoid installing xorg-x11 at this moment:
415</p> 401</p>
416 402
417<pre caption="Installing pcmcia-cs"> 403<pre caption="Installing pcmciautils">
418# <i>USE="-X" emerge pcmcia-cs</i> 404# <i>emerge pcmciautils</i>
419</pre>
420
421<p>
422When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
423runlevel:
424</p>
425
426<pre caption="Adding pcmcia to the default runlevel">
427# <i>rc-update add pcmcia default</i>
428</pre> 405</pre>
429 406
430</body> 407</body>
431</subsection> 408</subsection>
432</section> 409</section>
433<section> 410
411<section id="sysinfo">
434<title>System Information</title> 412<title>System Information</title>
435<subsection> 413<subsection>
436<title>Root Password</title> 414<title>Root Password</title>
437<body> 415<body>
438 416
442 420
443<pre caption="Setting the root password"> 421<pre caption="Setting the root password">
444# <i>passwd</i> 422# <i>passwd</i>
445</pre> 423</pre>
446 424
447<p>
448If you want root to be able to log on through the serial console, add
449<c>tts/0</c> to <path>/etc/securetty</path>:
450</p>
451
452<pre caption="Adding tts/0 to /etc/securetty">
453# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
454</pre>
455
456</body> 425</body>
457</subsection> 426</subsection>
458<subsection> 427<subsection>
459<title>System Information</title> 428<title>System Information</title>
460<body> 429<body>
467<pre caption="Opening /etc/rc.conf"> 436<pre caption="Opening /etc/rc.conf">
468# <i>nano -w /etc/rc.conf</i> 437# <i>nano -w /etc/rc.conf</i>
469</pre> 438</pre>
470 439
471<p> 440<p>
441When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
442</p>
443
444<p>
472As you can see, this file is well commented to help you set up the necessary 445As you can see, this file is well commented to help you set up the necessary
473configuration variables. Take special care with the <c>KEYMAP</c> setting: if 446configuration variables. You can configure your system to use unicode and
474you select the wrong <c>KEYMAP</c> you will get weird results when typing on 447define your default editor and your display manager (like gdm or kdm).
475your keyboard. 448</p>
449
476</p> 450<p>
451Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
452Edit it to configure your keyboard.
453</p>
477 454
478<note> 455<pre caption="Opening /etc/conf.d/keymaps">
479Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 456# <i>nano -w /etc/conf.d/keymaps</i>
480select an i386 keymap (such as "us") instead of "sunkeymap". 457</pre>
458
459<p>
460Take special care with the <c>KEYMAP</c> variable. If you select the wrong
461<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
462</p>
463
464<note test="substring(func:keyval('arch'),1,3)='PPC'">
465PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
466keymaps on boot have to enable ADB keycode sendings in their kernel and have to
467set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
481</note> 468</note>
482 469
483<p> 470<p>
484<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 471When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
485ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 472exit.
486to set a mac/ppc keymap in <path>rc.conf</path>.
487</p>
488
489<p> 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>
486to the file. Otherwise you will notice some clock skew.
487</p>
488
489<p>
490You should define the timezone that you previously copied to
491<path>/etc/localtime</path> so that further upgrades of the
492<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
493automatically. For instance, if you used the GMT timezone, you would add
494<c>TIMEZONE="GMT"</c>
495</p>
496
497<p>
490When you're finished configuring <path>/etc/rc.conf</path>, save and exit. 498When you're finished configuring <path>/etc/conf.d/clock</path>, save and
491</p> 499exit.
492
493<p> 500</p>
494If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with 501
502<p test="not(func:keyval('arch')='PPC64')">
495<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>. 503Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
504Tools</uri>.
496</p> 505</p>
497 506
498</body> 507</body>
499</subsection>
500<subsection> 508</subsection>
509<subsection test="func:keyval('arch')='PPC64'">
501<title>Configuring the Console</title> 510<title>Configuring the Console</title>
502<body> 511<body>
503 512
504<note>
505The following section applies to the IBM POWER5 and JS20 hardware platforms.
506</note>
507
508<p>
509If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
510the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
511</p> 513<p>
514If you are using a virtual console, you must uncomment the appropriate line in
515<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
516</p>
512 517
513<pre caption="Enabling hvc support in /etc/inittab"> 518<pre caption="Enabling hvc or hvsi support in /etc/inittab">
514hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220 519hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
520hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
521</pre>
522
523<p>
524You should also take this time to verify that the appropriate console is
525listed in <path>/etc/securetty</path>.
515</pre> 526</p>
516 527
517<p> 528<p>
518You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary 529You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
519System Tools</uri>. 530System Tools</uri>.
520</p> 531</p>

Legend:
Removed from v.1.60  
changed lines
  Added in v.1.100

  ViewVC Help
Powered by ViewVC 1.1.20