/[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.4 Revision 1.99
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
1<!-- 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 -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.99 2008/05/02 08:04:23 nightmorph Exp $ -->
3 8
4<sections> 9<sections>
5<section>
6<title>Timezone</title>
7<body>
8 10
9<p> 11<abstract>
10You now need to select your timezone so that your system knows where it is 12You need to edit some important configuration files. In this chapter
11located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a 13you receive an overview of these files and an explanation on how to
12symlink to <path>/etc/localtime</path> using <c>ln</c>: 14proceed.
13</p> 15</abstract>
14 16
15<pre caption="Setting the timezone information"> 17<version>9.2</version>
16# <i>ls /usr/share/zoneinfo</i> 18<date>2008-05-02</date>
17<comment>(Suppose you want to use GTM:)</comment>
18# <i>ln -s /usr/share/zoneinfo/GMT /etc/localtime</i>
19</pre>
20 19
21</body>
22</section>
23<section> 20<section>
24<title>Filesystem Information</title> 21<title>Filesystem Information</title>
25<subsection> 22<subsection>
26<title>What is fstab?</title> 23<title>What is fstab?</title>
27<body> 24<body>
28 25
29<p> 26<p>
30Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
31<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
32(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
33(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
34etc.). 31them or not, etc.)
35</p> 32</p>
36 33
37</body> 34</body>
38</subsection> 35</subsection>
39<subsection> 36<subsection>
40<title>Creating /etc/fstab</title> 37<title>Creating /etc/fstab</title>
41<body> 38<body>
42 39
43<p> 40<p>
44<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six 41<path>/etc/fstab</path> uses a special syntax. Every line consists of six
45fields, seperated by whitespace (space(s), tabs or a mixture). Each field has 42fields, separated by whitespace (space(s), tabs or a mixture). Each field has
46its own meaning: 43its own meaning:
47</p> 44</p>
48 45
49<ul> 46<ul>
50<li> 47<li>
51 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
52 file) 49 file)
53</li> 50</li>
54<li> 51<li>
55 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
56 mounted 53 mounted
57</li> 54</li>
58<li> 55<li>
59 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
60</li> 57</li>
61<li> 58<li>
62 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
63 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,
64 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
65 listing. Multiple mountoptions are comma-seperated. 62 listing. Multiple mount options are comma-separated.
66</li> 63</li>
67<li> 64<li>
68 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
69 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).
70</li> 67</li>
71<li> 68<li>
72 The sixth field is used by <c>fsck</c> the order in which filesystems should 69 The sixth field is used by <c>fsck</c> to determine the order in which
73 be <b>check</b>ed if the system wasn't shut down properly. The root filesystem 70 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
74 should have <c>1</c> while the rest should have <c>2</c> (or <c>0</c> in case 71 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
75 a filesystem check isn't necessary). 72 (or <c>0</c> if a filesystem check isn't necessary).
76</li> 73</li>
77</ul> 74</ul>
78 75
79<p> 76<impo>
80So 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
81<path>/etc/fstab</path>: 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
82</p> 79</impo>
83 80
84<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
85# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
86</pre> 83</pre>
87 84
85</body>
86<body test="func:keyval('/boot')">
87
88<p> 88<p>
89Lets 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>
90partition. 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
91<path>/boot</path> partition, don't copy it verbatim. 91<path>/boot</path>, don't copy it.
92</p>
93
94<p> 92</p>
93
94<p>
95In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
96<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
97be 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:
98would write down:
99</p> 98</p>
100 99
101<pre caption="An example /boot line for /etc/fstab"> 100<pre caption="An example /boot line for /etc/fstab">
102/dev/hda1 /boot ext2 noauto 1 2 101<keyval id="/boot"/> /boot ext2 defaults 1 2
103</pre> 102</pre>
104 103
105<p>
106Now, to improve performance, most users would want to add the <c>noatime</c>
107option as mountoption, which results in a faster system since access times
108aren't registered (you don't need those generally anyway):
109</p> 104<p>
110 105Some users don't want their <path>/boot</path> partition to be mounted
111<pre caption="An improved /boot line for /etc/fstab"> 106automatically to improve their system's security. Those people should
112/dev/hda1 /boot ext2 noauto,noatime 1 2 107substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
113</pre> 108manually mount this partition every time you want to use it.
114
115<p> 109</p>
116If we continue with this, we would end up with the following three lines (for 110
117<path>/boot</path>, <path>/</path> and the swap partition): 111</body>
112<body>
113
118</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>
119 119
120<pre caption="Three /etc/fstab lines"> 120<p>
121/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
122/dev/hda2 none swap sw 0 0 134/dev/sda2 none swap sw 0 0
123/dev/hda3 / ext3 noatime 0 1 135/dev/sda3 / ext3 noatime 0 1
124</pre>
125 136
126<p> 137/dev/cdrom /mnt/cdrom auto noauto,user 0 0
127To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
128(required) and for your CD-ROM drive (and ofcourse, if you have other
129partitions or drives, for those too):
130</p> 138</pre>
131 139
132<pre caption="A full /etc/fstab example"> 140<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
133/dev/hda1 /boot ext2 noauto,noatime 1 2 141/dev/sda1 / ext3 noatime 0 1
134/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'">
135/dev/hda3 / ext3 noatime 0 1 155/dev/sda4 / ext3 noatime 0 1
156/dev/sda3 none swap sw 0 0
136 157
137none /proc proc defaults 0 0
138none /dev/shm tmpfs defaults 0 0
139
140/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
141</pre> 159</pre>
142 160
143<p> 161<p>
144<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
145removable 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
146<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.
147</p> 165</p>
148 166
149<p> 167<p>
150Now 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>
151SPARC-user, you should add the following line to your <path>/etc/fstab</path> 169mount option, which results in a faster system since access times
152too: 170aren't registered (you don't need those generally anyway).
153</p>
154
155<pre caption="Adding openprom filesystem to /etc/fstab">
156none /proc/openprom openpromfs defaults 0 0
157</pre>
158
159<p> 171</p>
172
173<p>
160Reread your <path>/etc/fstab</path>, save and quit to continue. 174Double-check your <path>/etc/fstab</path>, save and quit to continue.
161</p> 175</p>
162 176
163</body> 177</body>
164</subsection> 178</subsection>
165</section> 179</section>
166<section> 180<section>
167<title>Networking Information</title> 181<title>Networking Information</title>
168<subsection> 182<subsection>
169<title>Hostname, Domainname etc.</title> 183<title>Host name, Domainname, etc</title>
170<body> 184<body>
171 185
172<p> 186<p>
173One of the choices the user has to make is name his PC. This seems to be quite 187One of the choices the user has to make is name his/her PC. This seems to be
174easy, but <e>lots</e> of users are having difficulties finding the appropriate 188quite easy, but <e>lots</e> of users are having difficulties finding the
175name for their Linux-pc. To speed things up, know that any name you choose can 189appropriate name for their Linux-pc. To speed things up, know that any name you
176be changed afterwards. For all we care, you can just call your system 190choose can be changed afterwards. For all we care, you can just call your system
177<c>tux</c> and domain <c>homenetwork</c>. 191<c>tux</c> and domain <c>homenetwork</c>.
178</p> 192</p>
179 193
180<p>
181We use these values in the next examples. First we set the hostname:
182</p>
183
184<pre caption="Setting the hostname"> 194<pre caption="Setting the host name">
185# <i>echo tux &gt; /etc/hostname</i> 195# <i>nano -w /etc/conf.d/hostname</i>
186</pre>
187 196
197<comment>(Set the HOSTNAME variable to your host name)</comment>
198HOSTNAME="<i>tux</i>"
199</pre>
200
188<p> 201<p>
189Second 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.
190</p> 206</p>
191 207
192<pre caption="Setting the domainname"> 208<pre caption="Setting the domainname">
193# <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>"
194</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>
195 220
196<p> 221<p>
197If 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
198one), you need to define that one too: 223one), you need to define that one too:
199</p> 224</p>
200 225
201<pre caption="Setting the NIS domainname"> 226<pre caption="Setting the NIS domainname">
202# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 227# <i>nano -w /etc/conf.d/net</i>
228
229<comment>(Set the nis_domain variable to your NIS domain name)</comment>
230nis_domain_lo="<i>my-nisdomain</i>"
203</pre> 231</pre>
232
233<note>
234For more information on configuring DNS and NIS, please read the examples
235provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
236<c>openresolv</c> to help manage your DNS/NIS setup.
237</note>
204 238
205</body> 239</body>
206</subsection> 240</subsection>
207<subsection> 241<subsection>
208<title>Configuring your Network</title> 242<title>Configuring your Network</title>
209<body> 243<body>
210 244
211<p> 245<p>
212Before 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
213that 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
214just 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
215your Gentoo system permanently. 249your Gentoo system permanently.
216</p> 250</p>
217 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
218<p> 258<p>
219All 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
220a 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
221networking manually. But don't fear, we'll explain everything :) 261networking manually. But don't fear, we'll explain everything. A fully
222</p> 262commented example that covers many different configurations is available in
223 263<path>/etc/conf.d/net.example</path>.
224<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
225First 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
226is used in this example): 277this example):
227</p> 278</p>
228 279
229<pre caption="Opening /etc/conf.d/net for editing"> 280<pre caption="Opening /etc/conf.d/net for editing">
230# <i>nano -w /etc/conf.d/net</i> 281# <i>nano -w /etc/conf.d/net</i>
231</pre> 282</pre>
232 283
233<p> 284<p>
234The first variable you'll find is <c>iface_eth0</c>. It uses the following 285You will see the following file:
235syntax:
236</p>
237
238<pre caption="iface_eth0 syntaxis">
239iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
240</pre>
241
242<p> 286</p>
243If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 287
244to <c>dhcp</c>. However, if you need to setup your network manually and you're 288<pre caption="Default /etc/conf.d/net">
245not familiar with all the above terms, please read the section on <uri 289# This blank configuration will automatically use DHCP for any net.*
246link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 290# scripts in /etc/init.d. To create a more complete configuration,
247Terminology</uri> if you haven't done so already. 291# please review /etc/conf.d/net.example and save your configuration
292# in /etc/conf.d/net (this file :]!).
293</pre>
294
248</p> 295<p>
249 296To enter your own IP address, netmask and gateway, you need
297to set both <c>config_eth0</c> and <c>routes_eth0</c>:
250<p> 298</p>
251So lets give two examples; the first one uses DHCP, the second one a static IP 299
252(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 300<pre caption="Manually setting IP information for eth0">
253192.168.0.1: 301config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
302routes_eth0=( "default via 192.168.0.1" )
303</pre>
304
254</p> 305<p>
255 306To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
256<pre caption="Examples for /etc/conf.d/net"> 307<c>dhcp_eth0</c>:
257<comment>(For DHCP:)</comment>
258iface_eth0="dhcp"
259
260<comment>(For static IP:)</comment>
261iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
262gateway="eth0/192.168.0.1"
263</pre>
264
265<p> 308</p>
266If you have several network interfaces, create extra <c>iface_eth</c> variables, 309
267like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 310<pre caption="Automatically obtaining an IP address for eth0">
268shouldn't be reproduced as you can only set one gateway per computer. 311config_eth0=( "dhcp" )
312dhcp_eth0="nodns nontp nonis"
313</pre>
314
315<p>
316Please read <path>/etc/conf.d/net.example</path> for a list of all available
317options.
318</p>
319
320<p>
321If you have several network interfaces repeat the above steps for
322<c>config_eth1</c>, <c>config_eth2</c>, etc.
269</p> 323</p>
270 324
271<p> 325<p>
272Now save the configuration and exit to continue. 326Now save the configuration and exit to continue.
273</p> 327</p>
277<subsection> 331<subsection>
278<title>Automatically Start Networking at Boot</title> 332<title>Automatically Start Networking at Boot</title>
279<body> 333<body>
280 334
281<p> 335<p>
282To have your network interfaces activated at boot, you need to add those to the 336To have your network interfaces activated at boot, you need to add them to the
283default runlevel. If you have PCMCIA interfaces you should skip this action as 337default runlevel.
284the PCMCIA interfaces are started by the PCMCIA init script.
285</p> 338</p>
286 339
287<pre caption="Adding net.eth0 to the default runlevel"> 340<pre caption="Adding net.eth0 to the default runlevel">
288# <i>rc-update add net.eth0 default</i> 341# <i>rc-update add net.eth0 default</i>
289</pre> 342</pre>
294use <c>ln</c> to do this: 347use <c>ln</c> to do this:
295</p> 348</p>
296 349
297<pre caption="Creating extra initscripts"> 350<pre caption="Creating extra initscripts">
298# <i>cd /etc/init.d</i> 351# <i>cd /etc/init.d</i>
299# <i>ln -s net.eth0 net.eth1</i> 352# <i>ln -s net.lo net.eth1</i>
300# <i>rc-update add net.eth1 default</i> 353# <i>rc-update add net.eth1 default</i>
301</pre> 354</pre>
302 355
303</body> 356</body>
304</subsection> 357</subsection>
306<title>Writing Down Network Information</title> 359<title>Writing Down Network Information</title>
307<body> 360<body>
308 361
309<p> 362<p>
310You now need to inform Linux about your network. This is defined in 363You now need to inform Linux about your network. This is defined in
311<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 364<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
312for hosts that aren't resolved by your nameserver. For instance, if your 365hosts that aren't resolved by your nameserver. You need to define your system.
313internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 366You may also want to define other systems on your network if you don't want to
314<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 367set up your own internal DNS system.
315open <path>/etc/hosts</path> and fill in the values:
316</p> 368</p>
317 369
318<pre caption="Opening /etc/hosts"> 370<pre caption="Opening /etc/hosts">
319# <i>nano -w /etc/hosts</i> 371# <i>nano -w /etc/hosts</i>
320</pre> 372</pre>
321 373
322<pre caption="Filling in the networking information"> 374<pre caption="Filling in the networking information">
323127.0.0.1 localhost tux 375<comment>(This defines the current system)</comment>
324192.168.0.5 jenny 376127.0.0.1 tux.homenetwork tux localhost
325192.168.0.56 benny
326</pre>
327 377
328<p> 378<comment>(Define extra systems on your network,
329If your system is the only system (or the nameservers handle all name 379they need to have a static IP to be defined this way.)</comment>
330resolution) a single line is sufficient: 380192.168.0.5 jenny.homenetwork jenny
331</p> 381192.168.0.6 benny.homenetwork benny
332
333<pre caption="/etc/hosts for lonely or fully integrated PCs">
334127.0.0.1 localhost tux
335</pre> 382</pre>
336 383
337<p> 384<p>
338Save and exit the editor to continue. 385Save and exit the editor to continue.
339</p> 386</p>
340 387
341<p> 388<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
342If you don't have PCMCIA, you can now continue with <uri 389If you don't have PCMCIA, you can now continue with <uri
343link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 390link="#sysinfo">System Information</uri>. PCMCIA-users should read the
344following topic on PCMCIA. 391following topic on PCMCIA.
345</p> 392</p>
346 393
347</body> 394</body>
348</subsection> 395</subsection>
349<subsection> 396<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
350<title>Optional: Get PCMCIA Working</title> 397<title>Optional: Get PCMCIA Working</title>
351<body> 398<body>
352 399
353<p> 400<p>
354PCMCIA-users should first install the <c>pcmcia-cs</c> package: 401PCMCIA users should first install the <c>pcmciautils</c> package.
355</p> 402</p>
356 403
357<pre caption="Installing pcmcia-cs"> 404<pre caption="Installing pcmciautils">
358# <i>emerge -k pcmcia-cs</i> 405# <i>emerge pcmciautils</i>
359</pre>
360
361<p>
362When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>
363runlevel:
364</p>
365
366<pre caption="Adding pcmcia to the default runlevel">
367# <i>rc-update add pcmcia boot</i>
368</pre> 406</pre>
369 407
370</body> 408</body>
371</subsection> 409</subsection>
372</section> 410</section>
411
412<section id="sysinfo">
413<title>System Information</title>
373<section> 414<subsection>
415<title>Root Password</title>
416<body>
417
418<p>
419First we set the root password by typing:
420</p>
421
422<pre caption="Setting the root password">
423# <i>passwd</i>
424</pre>
425
426</body>
427</subsection>
428<subsection>
374<title>System Information</title> 429<title>System Information</title>
375<body> 430<body>
376 431
377<p> 432<p>
378Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 433Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
382<pre caption="Opening /etc/rc.conf"> 437<pre caption="Opening /etc/rc.conf">
383# <i>nano -w /etc/rc.conf</i> 438# <i>nano -w /etc/rc.conf</i>
384</pre> 439</pre>
385 440
386<p> 441<p>
442When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
443</p>
444
445<p>
387As you can see, this file is well commented to help you set up the necessary 446As you can see, this file is well commented to help you set up the necessary
388configuration variables. When you're finished configuring 447configuration variables. You can configure your system to use unicode and
389<path>/etc/rc.conf</path>, save and exit to continue. 448define your default editor and your display manager (like gdm or kdm).
449</p>
450
390</p> 451<p>
452Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
453Edit it to configure your keyboard.
454</p>
391 455
456<pre caption="Opening /etc/conf.d/keymaps">
457# <i>nano -w /etc/conf.d/keymaps</i>
458</pre>
459
460<p>
461Take special care with the <c>KEYMAP</c> variable. If you select the wrong
462<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
463</p>
464
465<note test="substring(func:keyval('arch'),1,3)='PPC'">
466PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
467keymaps on boot have to enable ADB keycode sendings in their kernel and have to
468set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
469</note>
470
471<p>
472When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
473exit.
474</p>
475
476<p>
477Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
478according to your needs.
479</p>
480
481<pre caption="Opening /etc/conf.d/clock">
482# <i>nano -w /etc/conf.d/clock</i>
483</pre>
484
485<p>
486If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
487to the file. Otherwise you will notice some clock skew.
488</p>
489
490<p>
491You should define the timezone that you previously copied to
492<path>/etc/localtime</path> so that further upgrades of the
493<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
494automatically. For instance, if you used the GMT timezone, you would add
495<c>TIMEZONE="GMT"</c>
496</p>
497
498<p>
499When you're finished configuring <path>/etc/conf.d/clock</path>, save and
500exit.
501</p>
502
503<p test="not(func:keyval('arch')='PPC64')">
504Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
505Tools</uri>.
506</p>
507
508</body>
509</subsection>
510<subsection test="func:keyval('arch')='PPC64'">
511<title>Configuring the Console</title>
392</body> 512<body>
513
514<p>
515If you are using a virtual console, you must uncomment the appropriate line in
516<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
517</p>
518
519<pre caption="Enabling hvc or hvsi support in /etc/inittab">
520hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
521hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
522</pre>
523
524<p>
525You should also take this time to verify that the appropriate console is
526listed in <path>/etc/securetty</path>.
527</p>
528
529<p>
530You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
531System Tools</uri>.
532</p>
533
534</body>
535</subsection>
393</section> 536</section>
394</sections> 537</sections>

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.99

  ViewVC Help
Powered by ViewVC 1.1.20