/[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.34 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.34 2004/06/03 20:58:34 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
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
17<version>9.3</version>
18<date>2009-02-11</date>
19
10<section> 20<section>
11<title>Filesystem Information</title> 21<title>Filesystem Information</title>
12<subsection> 22<subsection>
13<title>What is fstab?</title> 23<title>What is fstab?</title>
14<body> 24<body>
15 25
16<p> 26<p>
17Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
18<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
19(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
20(special options) and when (automatically or not, can users mount those or not, 30and with what special options (automatically or not, whether users can mount
21etc.). 31them or not, etc.)
22</p> 32</p>
23 33
24</body> 34</body>
25</subsection> 35</subsection>
26<subsection> 36<subsection>
37<li> 47<li>
38 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
39 file) 49 file)
40</li> 50</li>
41<li> 51<li>
42 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
43 mounted 53 mounted
44</li> 54</li>
45<li> 55<li>
46 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
47</li> 57</li>
48<li> 58<li>
49 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
50 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,
51 you are encouraged to read the mount manpage (<c>man mount</c>) for a full 61 you are encouraged to read the mount man page (<c>man mount</c>) for a full
52 listing. Multiple mountoptions are comma-separated. 62 listing. Multiple mount options are comma-separated.
53</li> 63</li>
54<li> 64<li>
55 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
56 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).
57</li> 67</li>
58<li> 68<li>
59 The sixth field is used by <c>fsck</c> to determine the order in which 69 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. 70 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> 71 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). 72 (or <c>0</c> if a filesystem check isn't necessary).
63</li> 73</li>
64</ul> 74</ul>
65 75
66<p> 76<impo>
67So start <c>nano</c> (or your favorite editor) to create your 77The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
68<path>/etc/fstab</path>: 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
69</p> 79</impo>
70 80
71<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
72# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
73</pre> 83</pre>
74 84
85</body>
86<body test="func:keyval('/boot')">
87
75<p> 88<p>
76Let 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>
77partition. 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
78<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. 91<path>/boot</path>, don't copy it.
79</p>
80
81<p> 92</p>
93
94<p>
82In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
83<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't 96usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
84be mounted automatically (<c>noauto</c>) but does need to be checked. So we 97filesystem. It needs to be checked during boot, so we would write down:
85would write down:
86</p> 98</p>
87 99
88<pre caption="An example /boot line for /etc/fstab"> 100<pre caption="An example /boot line for /etc/fstab">
89/dev/hda1 /boot ext2 noauto 1 2 101<keyval id="/boot"/> /boot ext2 defaults 1 2
90</pre> 102</pre>
91 103
92<p>
93Now, 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
95aren't registered (you don't need those generally anyway):
96</p> 104<p>
97 105Some users don't want their <path>/boot</path> partition to be mounted
98<pre caption="An improved /boot line for /etc/fstab"> 106automatically to improve their system's security. Those people should
99/dev/hda1 /boot ext2 noauto,noatime 1 2 107substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
100</pre> 108manually mount this partition every time you want to use it.
101
102<p> 109</p>
103If we continue with this, we would end up with the following three lines (for 110
104<path>/boot</path>, <path>/</path> and the swap partition): 111</body>
112<body>
113
105</p> 114<p>
115Add the rules that match your partitioning scheme and append rules for
116your CD-ROM drive(s), and of course, if you have other partitions or drives,
117for those too.
118</p>
106 119
107<pre caption="Three /etc/fstab lines"> 120<p>
108/dev/hda1 /boot ext2 noauto,noatime 1 2 121Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
122</p>
123
124<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
125<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
126/dev/sda3 none swap sw 0 0
127/dev/sda4 / ext3 noatime 0 1
128
129/dev/cdrom /mnt/cdrom auto noauto,user 0 0
130</pre>
131
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'">
133<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
109/dev/hda2 none swap sw 0 0 134/dev/sda2 none swap sw 0 0
110/dev/hda3 / ext3 noatime 0 1 135/dev/sda3 / ext3 noatime 0 1
111</pre>
112 136
113<p> 137/dev/cdrom /mnt/cdrom auto noauto,user 0 0
114To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
115(required) and for your CD-ROM drive (and of course, if you have other
116partitions or drives, for those too):
117</p> 138</pre>
118 139
119<pre caption="A full /etc/fstab example"> 140<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
120/dev/hda1 /boot ext2 noauto,noatime 1 2 141/dev/sda1 / ext3 noatime 0 1
121/dev/hda2 none swap sw 0 0 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
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'">
122/dev/hda3 / ext3 noatime 0 1 155/dev/sda4 / ext3 noatime 0 1
156/dev/sda3 none swap sw 0 0
123 157
124none /proc proc defaults 0 0
125none /dev/shm tmpfs defaults 0 0
126
127/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
128</pre> 159</pre>
129 160
130<p> 161<p>
131<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
132removable 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
133<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.
134</p> 165</p>
135 166
136<p> 167<p>
137Now 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>
138<b>SPARC</b>-user, you should add the following line to your 169mount option, which results in a faster system since access times
139<path>/etc/fstab</path> 170aren't registered (you don't need those generally anyway).
140too:
141</p>
142
143<pre caption="Adding openprom filesystem to /etc/fstab">
144none /proc/openprom openpromfs defaults 0 0
145</pre>
146
147<p> 171</p>
148If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
149</p>
150
151<pre caption="Adding usbfs filesystem to /etc/fstab">
152none /proc/bus/usb usbfs defaults 0 0
153</pre>
154 172
155<p> 173<p>
156Double-check your <path>/etc/fstab</path>, save and quit to continue. 174Double-check your <path>/etc/fstab</path>, save and quit to continue.
157</p> 175</p>
158 176
160</subsection> 178</subsection>
161</section> 179</section>
162<section> 180<section>
163<title>Networking Information</title> 181<title>Networking Information</title>
164<subsection> 182<subsection>
165<title>Hostname, Domainname etc.</title> 183<title>Host name, Domainname, etc</title>
166<body> 184<body>
167 185
168<p> 186<p>
169One 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
170quite 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
171appropriate 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
172choose 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
173<c>tux</c> and domain <c>homenetwork</c>. 191<c>tux</c> and domain <c>homenetwork</c>.
174</p> 192</p>
175 193
176<p>
177We use these values in the next examples. First we set the hostname:
178</p>
179
180<pre caption="Setting the hostname"> 194<pre caption="Setting the host name">
181# <i>echo tux &gt; /etc/hostname</i> 195# <i>nano -w /etc/conf.d/hostname</i>
182</pre>
183 196
197<comment>(Set the HOSTNAME variable to your host name)</comment>
198HOSTNAME="<i>tux</i>"
199</pre>
200
184<p> 201<p>
185Second 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.
186</p> 206</p>
187 207
188<pre caption="Setting the domainname"> 208<pre caption="Setting the domainname">
189# <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>"
190</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>
191 220
192<p> 221<p>
193If 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
194one), you need to define that one too: 223one), you need to define that one too:
195</p> 224</p>
196 225
197<pre caption="Setting the NIS domainname"> 226<pre caption="Setting the NIS domainname">
198# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 227# <i>nano -w /etc/conf.d/net</i>
199</pre>
200 228
201<p> 229<comment>(Set the nis_domain variable to your NIS domain name)</comment>
202Now add the <c>domainname</c> script to the default runlevel: 230nis_domain_lo="<i>my-nisdomain</i>"
203</p> 231</pre>
204 232
205<pre caption="Adding domainname to the default runlevel"> 233<note>
206# <i>rc-update add domainname default</i> 234For more information on configuring DNS and NIS, please read the examples
207</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>
208 238
209</body> 239</body>
210</subsection> 240</subsection>
211<subsection> 241<subsection>
212<title>Configuring your Network</title> 242<title>Configuring your Network</title>
213<body> 243<body>
214 244
215<p> 245<p>
216Before 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
217that 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
218just 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
219your Gentoo system permanently. 249your Gentoo system permanently.
220</p> 250</p>
221 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
222<p> 258<p>
223All 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
224a straightforward yet not intuitive syntax if you don't know how to setup 260a straightforward yet not intuitive syntax if you don't know how to set up
225networking manually. But don't fear, we'll explain everything :) 261networking manually. But don't fear, we'll explain everything. A fully
226</p> 262commented example that covers many different configurations is available in
227 263<path>/etc/conf.d/net.example</path>.
228<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
229First 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
230is used in this example): 277this example):
231</p> 278</p>
232 279
233<pre caption="Opening /etc/conf.d/net for editing"> 280<pre caption="Opening /etc/conf.d/net for editing">
234# <i>nano -w /etc/conf.d/net</i> 281# <i>nano -w /etc/conf.d/net</i>
235</pre> 282</pre>
236 283
237<p> 284<p>
238The first variable you'll find is <c>iface_eth0</c>. It uses the following 285You will see the following file:
239syntax:
240</p>
241
242<pre caption="iface_eth0 syntaxis">
243iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
244</pre>
245
246<p> 286</p>
247If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 287
248to <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">
249If you need to setup your network manually and you're 289# This blank configuration will automatically use DHCP for any net.*
250not familiar with all the above terms, please read the section on <uri 290# scripts in /etc/init.d. To create a more complete configuration,
251link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 291# please review /etc/conf.d/net.example and save your configuration
252Terminology</uri> if you haven't done so already. 292# in /etc/conf.d/net (this file :]!).
293</pre>
294
253</p> 295<p>
254 296To enter your own IP address, netmask and gateway, you need
297to set both <c>config_eth0</c> and <c>routes_eth0</c>:
255<p> 298</p>
256So let us give three examples; the first one uses DHCP, the second one a static 299
257IP (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">
258gateway 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" )
259rp-pppoe usage: 302routes_eth0=( "default via 192.168.0.1" )
303</pre>
304
260</p> 305<p>
261 306To use DHCP, define <c>config_eth0</c>:
262<pre caption="Examples for /etc/conf.d/net">
263<comment>(For DHCP)</comment>
264iface_eth0="dhcp"
265
266<comment>(For static IP)</comment>
267iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
268gateway="eth0/192.168.0.1"
269
270<comment>(For rp-pppoe)</comment>
271iface_eth0="up"
272</pre>
273
274<p> 307</p>
275If you have several network interfaces, create extra <c>iface_eth</c> variables, 308
276like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 309<pre caption="Automatically obtaining an IP address for eth0">
277shouldn't be reproduced as you can only set one gateway per computer. 310config_eth0=( "dhcp" )
311</pre>
312
313<p>
314Please read <path>/etc/conf.d/net.example</path> for a list of all available
315options. Be sure to also read your DHCP client manpage if you need to set
316specific DHCP options.
317</p>
318
319<p>
320If you have several network interfaces repeat the above steps for
321<c>config_eth1</c>, <c>config_eth2</c>, etc.
278</p> 322</p>
279 323
280<p> 324<p>
281Now save the configuration and exit to continue. 325Now save the configuration and exit to continue.
282</p> 326</p>
286<subsection> 330<subsection>
287<title>Automatically Start Networking at Boot</title> 331<title>Automatically Start Networking at Boot</title>
288<body> 332<body>
289 333
290<p> 334<p>
291To have your network interfaces activated at boot, you need to add those to the 335To have your network interfaces activated at boot, you need to add them to the
292default runlevel. If you have PCMCIA interfaces you should skip this action as 336default runlevel.
293the PCMCIA interfaces are started by the PCMCIA init script.
294</p> 337</p>
295 338
296<pre caption="Adding net.eth0 to the default runlevel"> 339<pre caption="Adding net.eth0 to the default runlevel">
297# <i>rc-update add net.eth0 default</i> 340# <i>rc-update add net.eth0 default</i>
298</pre> 341</pre>
303use <c>ln</c> to do this: 346use <c>ln</c> to do this:
304</p> 347</p>
305 348
306<pre caption="Creating extra initscripts"> 349<pre caption="Creating extra initscripts">
307# <i>cd /etc/init.d</i> 350# <i>cd /etc/init.d</i>
308# <i>ln -s net.eth0 net.eth1</i> 351# <i>ln -s net.lo net.eth1</i>
309# <i>rc-update add net.eth1 default</i> 352# <i>rc-update add net.eth1 default</i>
310</pre> 353</pre>
311 354
312</body> 355</body>
313</subsection> 356</subsection>
315<title>Writing Down Network Information</title> 358<title>Writing Down Network Information</title>
316<body> 359<body>
317 360
318<p> 361<p>
319You 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
320<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
321for 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.
322internal 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
323<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.
324open <path>/etc/hosts</path> and fill in the values:
325</p> 367</p>
326 368
327<pre caption="Opening /etc/hosts"> 369<pre caption="Opening /etc/hosts">
328# <i>nano -w /etc/hosts</i> 370# <i>nano -w /etc/hosts</i>
329</pre> 371</pre>
330 372
331<pre caption="Filling in the networking information"> 373<pre caption="Filling in the networking information">
332127.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>
333192.168.0.5 jenny.homenetwork jenny 379192.168.0.5 jenny.homenetwork jenny
334192.168.0.6 benny.homenetwork benny 380192.168.0.6 benny.homenetwork benny
335192.168.0.7 tux.homenetwork tux
336</pre>
337
338<p>
339If your system is the only system (or the nameservers handle all name
340resolution) a single line is sufficient:
341</p>
342
343<pre caption="/etc/hosts for lonely or fully integrated PCs">
344127.0.0.1 localhost
345</pre> 381</pre>
346 382
347<p> 383<p>
348Save and exit the editor to continue. 384Save and exit the editor to continue.
349</p> 385</p>
350 386
351<p> 387<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
352If you don't have PCMCIA, you can now continue with <uri 388If you don't have PCMCIA, you can now continue with <uri
353link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 389link="#sysinfo">System Information</uri>. PCMCIA-users should read the
354following topic on PCMCIA. 390following topic on PCMCIA.
355</p> 391</p>
356 392
357</body> 393</body>
358</subsection> 394</subsection>
359<subsection> 395<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
360<title>Optional: Get PCMCIA Working</title> 396<title>Optional: Get PCMCIA Working</title>
361<body> 397<body>
362 398
363<note>
364pcmcia-cs is only available for x86, amd64 and ppc platforms.
365</note>
366
367<p> 399<p>
368PCMCIA-users should first install the <c>pcmcia-cs</c> package. The 400PCMCIA users should first install the <c>pcmciautils</c> package.
369<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:
370</p> 401</p>
371 402
372<pre caption="Installing pcmcia-cs"> 403<pre caption="Installing pcmciautils">
373# <i>USE="-X" emerge pcmcia-cs</i> 404# <i>emerge pcmciautils</i>
374</pre>
375
376<p>
377When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
378runlevel:
379</p>
380
381<pre caption="Adding pcmcia to the default runlevel">
382# <i>rc-update add pcmcia default</i>
383</pre> 405</pre>
384 406
385</body> 407</body>
386</subsection> 408</subsection>
387</section> 409</section>
410
411<section id="sysinfo">
412<title>System Information</title>
388<section> 413<subsection>
414<title>Root Password</title>
415<body>
416
417<p>
418First we set the root password by typing:
419</p>
420
421<pre caption="Setting the root password">
422# <i>passwd</i>
423</pre>
424
425</body>
426</subsection>
427<subsection>
389<title>System Information</title> 428<title>System Information</title>
390<body> 429<body>
391 430
392<p> 431<p>
393Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 432Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
397<pre caption="Opening /etc/rc.conf"> 436<pre caption="Opening /etc/rc.conf">
398# <i>nano -w /etc/rc.conf</i> 437# <i>nano -w /etc/rc.conf</i>
399</pre> 438</pre>
400 439
401<p> 440<p>
441When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
442</p>
443
444<p>
402As 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
403configuration variables. Take special care with the <c>KEYMAP</c> setting: if 446configuration variables. You can configure your system to use unicode and
404you 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).
405your keyboard. 448</p>
449
406</p> 450<p>
451Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
452Edit it to configure your keyboard.
453</p>
407 454
408<note> 455<pre caption="Opening /etc/conf.d/keymaps">
409Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 456# <i>nano -w /etc/conf.d/keymaps</i>
410select 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>.
411</note> 468</note>
412 469
413<p> 470<p>
414<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
415ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 472exit.
416to set a mac/ppc keymap in <path>rc.conf</path>.
417</p>
418
419<p> 473</p>
420When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 474
421continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
422</p> 475<p>
476Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
477according to your needs.
478</p>
423 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>
498When you're finished configuring <path>/etc/conf.d/clock</path>, save and
499exit.
500</p>
501
502<p test="not(func:keyval('arch')='PPC64')">
503Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
504Tools</uri>.
505</p>
506
507</body>
508</subsection>
509<subsection test="func:keyval('arch')='PPC64'">
510<title>Configuring the Console</title>
424</body> 511<body>
512
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>
517
518<pre caption="Enabling hvc or hvsi support in /etc/inittab">
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>.
526</p>
527
528<p>
529You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
530System Tools</uri>.
531</p>
532
533</body>
534</subsection>
425</section> 535</section>
426</sections> 536</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20