/[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.71 Revision 1.111
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.71 2005/08/13 21:03:21 jkt Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.111 2012/04/06 12:09:19 swift 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.12</version> 17<version>18</version>
12<date>2005-08-13</date> 18<date>2012-04-06</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> 130
126(required) and for your CD-ROM drive (and of course, if you have other 131proc /proc proc defaults 0 0
127partitions or drives, for those too): 132shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
128</p> 133</pre>
129 134
130<pre caption="A full /etc/fstab example"> 135<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 136<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132/dev/hda2 none swap sw 0 0 137/dev/sda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 138/dev/sda3 / ext3 noatime 0 1
134 139
140/dev/cdrom /mnt/cdrom auto noauto,user 0 0
141
135none /proc proc defaults 0 0 142proc /proc proc defaults 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 143shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
144</pre>
137 145
146<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
147/dev/sda1 / ext3 noatime 0 1
148/dev/sda2 none swap sw 0 0
149/dev/sda4 /usr ext3 noatime 0 2
150/dev/sda5 /var ext3 noatime 0 2
151/dev/sda6 /home ext3 noatime 0 2
152
153<comment># You must add the rules for openprom</comment>
154openprom /proc/openprom openpromfs defaults 0 0
155
138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 156/dev/cdrom /mnt/cdrom auto noauto,user 0 0
157
158proc /proc proc defaults 0 0
159shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
160</pre>
161
162<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or
163func:keyval('arch')='PPC64'">
164/dev/sda4 / ext3 noatime 0 1
165/dev/sda3 none swap sw 0 0
166
167/dev/cdrom /mnt/cdrom auto noauto,user 0 0
168
169proc /proc proc defaults 0 0
170shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
139</pre> 171</pre>
140 172
141<p> 173<p>
142<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 174<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 175removable 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. 176<c>user</c> makes it possible for non-root users to mount the CD.
145</p> 177</p>
146 178
147<p> 179<p>
148Now use the above example to create your <path>/etc/fstab</path>. If you are a 180To 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 181mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 182aren'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> 183</p>
157 184
158<p> 185<p>
159Double-check your <path>/etc/fstab</path>, save and quit to continue. 186Double-check your <path>/etc/fstab</path>, save and quit to continue.
160</p> 187</p>
161 188
163</subsection> 190</subsection>
164</section> 191</section>
165<section> 192<section>
166<title>Networking Information</title> 193<title>Networking Information</title>
167<subsection> 194<subsection>
168<title>Hostname, Domainname etc.</title> 195<title>Host name, Domainname, etc</title>
169<body> 196<body>
170 197
171<p> 198<p>
172One of the choices the user has to make is name his/her PC. This seems to be 199One 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 200quite 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 201appropriate 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 202choose can be changed afterwards. For all we care, you can just call your system
176<c>tux</c> and domain <c>homenetwork</c>. 203<c>tux</c> and domain <c>homenetwork</c>.
177</p> 204</p>
178 205
179<p>
180We use these values in the next examples. First we set the hostname:
181</p>
182
183<pre caption="Setting the hostname"> 206<pre caption="Setting the host name">
184# <i>nano -w /etc/conf.d/hostname</i> 207# <i>nano -w /etc/conf.d/hostname</i>
185 208
186<comment>(Set the HOSTNAME variable to your hostname)</comment> 209<comment>(Set the hostname variable to your host name)</comment>
187HOSTNAME="<i>tux</i>" 210hostname="<i>tux</i>"
188</pre> 211</pre>
189 212
190<p> 213<p>
191Second we set the domainname: 214Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
215You only need a domain if your ISP or network administrator says so, or if you
216have a DNS server but not a DHCP server. You don't need to worry about DNS or
217domainnames if your networking is setup for DHCP.
192</p> 218</p>
193 219
194<pre caption="Setting the domainname"> 220<pre caption="Setting the domainname">
195# <i>nano -w /etc/conf.d/domainname</i> 221# <i>nano -w /etc/conf.d/net</i>
196 222
197<comment>(Set the DNSDOMAIN variable to your domain name)</comment> 223<comment>(Set the dns_domain variable to your domain name)</comment>
198DNSDOMAIN="<i>homenetwork</i>" 224dns_domain_lo="<i>homenetwork</i>"
199</pre> 225</pre>
226
227<note>
228If you choose not to set a domainname, you can get rid of the "This is
229hostname.(none)" messages at your login screen by editing
230<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
231</note>
200 232
201<p> 233<p>
202If you have a NIS domain (if you don't know what that is, then you don't have 234If you have a NIS domain (if you don't know what that is, then you don't have
203one), you need to define that one too: 235one), you need to define that one too:
204</p> 236</p>
205 237
206<pre caption="Setting the NIS domainname"> 238<pre caption="Setting the NIS domainname">
207# <i>nano -w /etc/conf.d/domainname</i> 239# <i>nano -w /etc/conf.d/net</i>
208 240
209<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment> 241<comment>(Set the nis_domain variable to your NIS domain name)</comment>
210NISDOMAIN="<i>my-nisdomain</i>" 242nis_domain_lo="<i>my-nisdomain</i>"
211</pre>
212
213<p>
214Now add the <c>domainname</c> script to the default runlevel:
215</p> 243</pre>
216 244
217<pre caption="Adding domainname to the default runlevel"> 245<note>
218# <i>rc-update add domainname default</i> 246For more information on configuring DNS and NIS, please read the examples
219</pre> 247provided in <path>/usr/share/doc/openrc-*/net.example.bz2</path> which
248can be read using <c>bzless</c>. Also, you may want to emerge <c>openresolv</c>
249to help manage your DNS/NIS setup.
250</note>
220 251
221</body> 252</body>
222</subsection> 253</subsection>
223<subsection> 254<subsection>
224<title>Configuring your Network</title> 255<title>Configuring your Network</title>
231your Gentoo system permanently. 262your Gentoo system permanently.
232</p> 263</p>
233 264
234<note> 265<note>
235More detailed information about networking, including advanced topics like 266More detailed information about networking, including advanced topics like
236bonding, bridging, 802.11q VLANs or wireless networking is covered in the <uri 267bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
237link="?part=4">Gentoo Network Configuration</uri> section. 268link="?part=4">Gentoo Network Configuration</uri> section.
238</note> 269</note>
239 270
240<p> 271<p>
241All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 272All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
242a straightforward yet not intuitive syntax if you don't know how to set up 273a straightforward yet not intuitive syntax if you don't know how to set up
243networking manually. But don't fear, we'll explain everything. A fully 274networking manually. But don't fear, we'll explain everything. A fully
244commented example that covers many different configurations is available in 275commented example that covers many different configurations is available in
245<path>/etc/conf.d/net.example</path>. 276<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
246</p>
247
248<p> 277</p>
249DHCP is used by default and does not require any further configuration. 278
279<p>
280DHCP is used by default. For DHCP to work, you will need to install a DHCP
281client. This is described later in <uri
282link="?part=1&amp;chap=9#networking-tools">Installing Necessary System
283Tools</uri>. Do not forget to install a DHCP client.
250</p> 284</p>
251 285
252<p> 286<p>
253If you need to configure your network connection either because you need 287If you need to configure your network connection either because you need
254specific DHCP options or because you do not use DHCP at all, open 288specific DHCP options or because you do not use DHCP at all, open
265</p> 299</p>
266 300
267<pre caption="Default /etc/conf.d/net"> 301<pre caption="Default /etc/conf.d/net">
268# This blank configuration will automatically use DHCP for any net.* 302# This blank configuration will automatically use DHCP for any net.*
269# scripts in /etc/init.d. To create a more complete configuration, 303# scripts in /etc/init.d. To create a more complete configuration,
270# please review /etc/conf.d/net.example and save your configuration 304# please review /usr/share/doc/openrc-*/net.example.bz2 and save
271# in /etc/conf.d/net (this file :]!). 305# your configuration in /etc/conf.d/net (this file :]!).
272</pre> 306</pre>
273 307
274<p> 308<p>
275To enter your own IP address, netmask and gateway, you need 309To enter your own IP address, netmask and gateway, you need
276to set both <c>config_eth0</c> and <c>routes_eth0</c>: 310to set both <c>config_eth0</c> and <c>routes_eth0</c>:
277</p> 311</p>
278 312
279<pre caption="Manually setting IP information for eth0"> 313<pre caption="Manually setting IP information for eth0">
280config_eth0=( "192.168.0.2 netmask 255.255.255.0" ) 314config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255"
281routes_eth0=( "default gw 192.168.0.1" ) 315routes_eth0="default via 192.168.0.1"
282</pre> 316</pre>
283 317
284<p> 318<p>
285To use DHCP and add specific DHCP options, define <c>config_eth0</c> and 319To use DHCP, define <c>config_eth0</c>:
286<c>dhcp_eth0</c>:
287</p> 320</p>
288 321
289<pre caption="Automatically obtaining an IP address for eth0"> 322<pre caption="Automatically obtaining an IP address for eth0">
290config_eth0=( "dhcp" ) 323config_eth0="dhcp"
291dhcp_eth0="nodns nontp nonis"
292</pre> 324</pre>
293 325
294<p> 326<p>
295Please read <path>/etc/conf.d/net.example</path> for a list of all available 327Please read <path>/usr/share/doc/openrc-*/net.example.bz2</path> for a
296options. 328list of all available options. Be sure to also read your DHCP client manpage if
329you need to set specific DHCP options.
297</p> 330</p>
298 331
299<p> 332<p>
300If you have several network interfaces repeat the above steps for 333If you have several network interfaces repeat the above steps for
301<c>config_eth1</c>, <c>config_eth2</c>, etc. 334<c>config_eth1</c>, <c>config_eth2</c>, etc.
311<title>Automatically Start Networking at Boot</title> 344<title>Automatically Start Networking at Boot</title>
312<body> 345<body>
313 346
314<p> 347<p>
315To have your network interfaces activated at boot, you need to add them to the 348To have your network interfaces activated at boot, you need to add them to the
316default runlevel. If you have PCMCIA interfaces you should skip this action as 349default runlevel.
317the PCMCIA interfaces are started by the PCMCIA init script.
318</p> 350</p>
319 351
320<pre caption="Adding net.eth0 to the default runlevel"> 352<pre caption="Adding net.eth0 to the default runlevel">
353# <i>cd /etc/init.d</i>
354# <i>ln -s net.lo net.eth0</i>
321# <i>rc-update add net.eth0 default</i> 355# <i>rc-update add net.eth0 default</i>
322</pre> 356</pre>
323 357
324<p> 358<p>
325If you have several network interfaces, you need to create the appropriate 359If you have several network interfaces, you need to create the appropriate
326<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can 360<path>net.eth1</path>, <path>net.eth2</path> etc. just like you did with
327use <c>ln</c> to do this: 361<path>net.eth0</path>.
328</p>
329
330<pre caption="Creating extra initscripts">
331# <i>cd /etc/init.d</i>
332# <i>ln -s net.eth0 net.eth1</i>
333# <i>rc-update add net.eth1 default</i>
334</pre> 362</p>
335 363
336</body> 364</body>
337</subsection> 365</subsection>
338<subsection> 366<subsection>
339<title>Writing Down Network Information</title> 367<title>Writing Down Network Information</title>
340<body> 368<body>
341 369
342<p> 370<p>
343You now need to inform Linux about your network. This is defined in 371You now need to inform Linux about your network. This is defined in
344<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 372<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
345for hosts that aren't resolved by your nameserver. For instance, if your 373hosts that aren't resolved by your nameserver. You need to define your system.
346internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 374You may also want to define other systems on your network if you don't want to
347<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 375set up your own internal DNS system.
348open <path>/etc/hosts</path> and fill in the values:
349</p> 376</p>
350 377
351<pre caption="Opening /etc/hosts"> 378<pre caption="Opening /etc/hosts">
352# <i>nano -w /etc/hosts</i> 379# <i>nano -w /etc/hosts</i>
353</pre> 380</pre>
354 381
355<pre caption="Filling in the networking information"> 382<pre caption="Filling in the networking information">
356127.0.0.1 localhost 383<comment>(This defines the current system)</comment>
384127.0.0.1 tux.homenetwork tux localhost
385
386<comment>(Define extra systems on your network,
387they need to have a static IP to be defined this way.)</comment>
357192.168.0.5 jenny.homenetwork jenny 388192.168.0.5 jenny.homenetwork jenny
358192.168.0.6 benny.homenetwork benny 389192.168.0.6 benny.homenetwork benny
359192.168.0.7 tux.homenetwork tux
360</pre>
361
362<p>
363If your system is the only system (or the nameservers handle all name
364resolution) a single line is sufficient. For instance, if you want to call your
365system <c>tux</c>:
366</p>
367
368<pre caption="/etc/hosts for lonely or fully integrated PCs">
369127.0.0.1 localhost tux
370</pre> 390</pre>
371 391
372<p> 392<p>
373Save and exit the editor to continue. 393Save and exit the editor to continue.
374</p> 394</p>
375 395
376<p> 396<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
377If you don't have PCMCIA, you can now continue with <uri 397If you don't have PCMCIA, you can now continue with <uri
378link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 398link="#sysinfo">System Information</uri>. PCMCIA-users should read the
379following topic on PCMCIA. 399following topic on PCMCIA.
380</p> 400</p>
381 401
382</body> 402</body>
383</subsection> 403</subsection>
384<subsection> 404<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
385<title>Optional: Get PCMCIA Working</title> 405<title>Optional: Get PCMCIA Working</title>
386<body> 406<body>
387 407
388<note>
389pcmcia-cs is only available for x86, amd64 and ppc platforms.
390</note>
391
392<p> 408<p>
393PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 409PCMCIA users should first install the <c>pcmciautils</c> package.
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:
397</p> 410</p>
398 411
399<pre caption="Installing pcmcia-cs"> 412<pre caption="Installing pcmciautils">
400# <i>USE="-X" emerge pcmcia-cs</i> 413# <i>emerge pcmciautils</i>
401</pre>
402
403<p>
404When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
405runlevel:
406</p>
407
408<pre caption="Adding pcmcia to the default runlevel">
409# <i>rc-update add pcmcia default</i>
410</pre> 414</pre>
411 415
412</body> 416</body>
413</subsection> 417</subsection>
414</section> 418</section>
415<section> 419
420<section id="sysinfo">
416<title>System Information</title> 421<title>System Information</title>
417<subsection> 422<subsection>
418<title>Root Password</title> 423<title>Root Password</title>
419<body> 424<body>
420 425
424 429
425<pre caption="Setting the root password"> 430<pre caption="Setting the root password">
426# <i>passwd</i> 431# <i>passwd</i>
427</pre> 432</pre>
428 433
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> 434</body>
439</subsection> 435</subsection>
440<subsection> 436<subsection>
441<title>System Information</title> 437<title>System Information</title>
442<body> 438<body>
443 439
444<p> 440<p>
445Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 441Gentoo uses <path>/etc/rc.conf</path> to configure the services, startup,
446Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) 442and shutdown of your system. Open up <path>/etc/rc.conf</path> and enjoy all
443the comments in the file.
447</p> 444</p>
448 445
449<pre caption="Opening /etc/rc.conf"> 446<pre caption="Configuring services">
450# <i>nano -w /etc/rc.conf</i> 447# <i>nano -w /etc/rc.conf</i>
451</pre> 448</pre>
452 449
453<p> 450<p>
454When you're finished configuring <path>/etc/rc.conf</path>, save and exit. 451When you're finished configuring these two files, save them and exit.
455</p>
456
457<p>
458As you can see, this file is well commented to help you set up the necessary
459configuration variables. You can configure your system to use unicode and
460define your default editor and your display manager (like gdm or kdm).
461</p> 452</p>
462 453
463<p> 454<p>
464Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration. 455Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
465Edit it to configure your keyboard. 456Edit it to configure your keyboard.
468<pre caption="Opening /etc/conf.d/keymaps"> 459<pre caption="Opening /etc/conf.d/keymaps">
469# <i>nano -w /etc/conf.d/keymaps</i> 460# <i>nano -w /etc/conf.d/keymaps</i>
470</pre> 461</pre>
471 462
472<p> 463<p>
473Take special care with the <c>KEYMAP</c> variable. If you select the wrong 464Take 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. 465<c>keymap</c>, you will get weird results when typing on your keyboard.
475</p> 466</p>
476 467
477<note> 468<note test="substring(func:keyval('arch'),1,3)='PPC'">
478Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 469PPC uses x86 keymaps on most systems.
479select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
480keymaps on most systems. Users who want to be able to use ADB keymaps on boot
481have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
482keymap in <path>/etc/conf.d/keymaps</path>.
483</note> 470</note>
484 471
485<p> 472<p>
486When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and 473When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
487exit. 474exit.
488</p> 475</p>
489 476
490<p> 477<p>
491Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it 478Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
492according to your needs. 479according to your needs.
493</p> 480</p>
494 481
495<pre caption="Opening /etc/conf.d/clock"> 482<pre caption="Opening /etc/conf.d/hwclock">
496# <i>nano -w /etc/conf.d/clock</i> 483# <i>nano -w /etc/conf.d/hwclock</i>
497</pre> 484</pre>
498 485
499<p> 486<p>
500If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to 487If your hardware clock is not using UTC, you need to add <c>clock="local"</c>
501the file. Otherwise you will notice some clock skew. 488to the file. Otherwise you will notice some clock skew.
502</p>
503
504<p> 489</p>
490
491<p>
505When you're finished configuring <path>/etc/conf.d/clock</path>, save and 492When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and
506exit. 493exit.
507</p> 494</p>
508 495
509<p> 496<p>
510If you are not installing Gentoo on IBM PPC64 hardware, continue with 497You should define the timezone that you previously copied to
498<path>/etc/localtime</path> in the <path>/etc/timezone</path> file so that
499further upgrades of the <c>sys-libs/timezone-data</c> package can update
500<path>/etc/localtime</path> automatically. For instance, if you used the
501Europe/Brussels timezone, you would write <c>Europe/Brussels</c> in the
502<path>/etc/timezone</path> file.
503</p>
504
505<p test="not(func:keyval('arch')='PPC64')">
511<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>. 506Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
507Tools</uri>.
512</p> 508</p>
513 509
514</body> 510</body>
515</subsection>
516<subsection> 511</subsection>
512<subsection test="func:keyval('arch')='PPC64'">
517<title>Configuring the Console</title> 513<title>Configuring the Console</title>
518<body> 514<body>
519 515
520<note>
521The following section applies to the IBM PPC64 hardware platforms.
522</note>
523
524<p> 516<p>
525If you are running Gentoo on IBM PPC64 hardware and using a virtual console 517If you are using a virtual console, you must uncomment the appropriate line in
526you must uncomment the appropriate line in <path>/etc/inittab</path> for the 518<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
527virtual console to spawn a login prompt.
528</p> 519</p>
529 520
530<pre caption="Enabling hvc or hvsi support in /etc/inittab"> 521<pre caption="Enabling hvc or hvsi support in /etc/inittab">
531hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 522hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
532hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 523hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

Legend:
Removed from v.1.71  
changed lines
  Added in v.1.111

  ViewVC Help
Powered by ViewVC 1.1.20