/[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.7 Revision 1.109
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.109 2012/02/22 21:27:45 swift 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>16</version>
16# <i>ls /usr/share/zoneinfo</i> 18<date>2012-02-22</date>
17<comment>(Suppose you want to use GTM:)</comment>
18# <i>ln -sf /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
131proc /proc proc defaults 0 0
132shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
133</pre>
134
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'">
136<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
122/dev/hda2 none swap sw 0 0 137/dev/sda2 none swap sw 0 0
123/dev/hda3 / ext3 noatime 0 1 138/dev/sda3 / ext3 noatime 0 1
124</pre>
125 139
126<p> 140/dev/cdrom /mnt/cdrom auto noauto,user 0 0
127To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> 141
128(required) and for your CD-ROM drive (and of course, if you have other 142proc /proc proc defaults 0 0
129partitions or drives, for those too): 143shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
130</p> 144</pre>
131 145
132<pre caption="A full /etc/fstab example"> 146<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
133/dev/hda1 /boot ext2 noauto,noatime 1 2 147/dev/sda1 / ext3 noatime 0 1
134/dev/hda2 none swap sw 0 0 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
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'">
135/dev/hda3 / ext3 noatime 0 1 164/dev/sda4 / ext3 noatime 0 1
165/dev/sda3 none swap sw 0 0
136 166
167/dev/cdrom /mnt/cdrom auto noauto,user 0 0
168
137none /proc proc defaults 0 0 169proc /proc proc defaults 0 0
138none /dev/shm tmpfs defaults 0 0 170shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
139
140/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
141</pre> 171</pre>
142 172
143<p> 173<p>
144<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
145removable 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
146<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.
147</p> 177</p>
148 178
149<p> 179<p>
150Now 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>
151SPARC-user, you should add the following line to your <path>/etc/fstab</path> 181mount option, which results in a faster system since access times
152too: 182aren'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> 183</p>
160If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>: 184
161</p> 185<p>
162
163<pre caption="Adding usbfs filesystem to /etc/fstab">
164none /proc/bus/usb usbfs defaults 0 0
165</pre>
166
167<p>
168Reread your <path>/etc/fstab</path>, save and quit to continue. 186Double-check your <path>/etc/fstab</path>, save and quit to continue.
169</p> 187</p>
170 188
171</body> 189</body>
172</subsection> 190</subsection>
173</section> 191</section>
174<section> 192<section>
175<title>Networking Information</title> 193<title>Networking Information</title>
176<subsection> 194<subsection>
177<title>Hostname, Domainname etc.</title> 195<title>Host name, Domainname, etc</title>
178<body> 196<body>
179 197
180<p> 198<p>
181One of the choices the user has to make is name his PC. This seems to be quite 199One of the choices the user has to make is name his/her PC. This seems to be
182easy, but <e>lots</e> of users are having difficulties finding the appropriate 200quite easy, but <e>lots</e> of users are having difficulties finding the
183name for their Linux-pc. To speed things up, know that any name you choose can 201appropriate name for their Linux-pc. To speed things up, know that any name you
184be 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
185<c>tux</c> and domain <c>homenetwork</c>. 203<c>tux</c> and domain <c>homenetwork</c>.
186</p> 204</p>
187 205
188<p>
189We use these values in the next examples. First we set the hostname:
190</p>
191
192<pre caption="Setting the hostname"> 206<pre caption="Setting the host name">
193# <i>echo tux &gt; /etc/hostname</i> 207# <i>nano -w /etc/conf.d/hostname</i>
194</pre>
195 208
209<comment>(Set the hostname variable to your host name)</comment>
210hostname="<i>tux</i>"
211</pre>
212
196<p> 213<p>
197Second 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.
198</p> 218</p>
199 219
200<pre caption="Setting the domainname"> 220<pre caption="Setting the domainname">
201# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 221# <i>nano -w /etc/conf.d/net</i>
222
223<comment>(Set the dns_domain variable to your domain name)</comment>
224dns_domain_lo="<i>homenetwork</i>"
202</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>
203 232
204<p> 233<p>
205If 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
206one), you need to define that one too: 235one), you need to define that one too:
207</p> 236</p>
208 237
209<pre caption="Setting the NIS domainname"> 238<pre caption="Setting the NIS domainname">
210# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 239# <i>nano -w /etc/conf.d/net</i>
240
241<comment>(Set the nis_domain variable to your NIS domain name)</comment>
242nis_domain_lo="<i>my-nisdomain</i>"
211</pre> 243</pre>
244
245<note>
246For more information on configuring DNS and NIS, please read the examples
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>
212 251
213</body> 252</body>
214</subsection> 253</subsection>
215<subsection> 254<subsection>
216<title>Configuring your Network</title> 255<title>Configuring your Network</title>
217<body> 256<body>
218 257
219<p> 258<p>
220Before you get that "Hey, we've had that already"-feeling, you should remember 259Before you get that "Hey, we've had that already"-feeling, you should remember
221that the networking you set up in the beginning of the gentoo installation was 260that the networking you set up in the beginning of the Gentoo installation was
222just for the installation. Right now you are going to configure networking for 261just for the installation. Right now you are going to configure networking for
223your Gentoo system permanently. 262your Gentoo system permanently.
224</p> 263</p>
225 264
265<note>
266More detailed information about networking, including advanced topics like
267bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
268link="?part=4">Gentoo Network Configuration</uri> section.
269</note>
270
226<p> 271<p>
227All 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
228a straightforward yet not intuitive syntax if you don't know how to setup 273a straightforward yet not intuitive syntax if you don't know how to set up
229networking manually. But don't fear, we'll explain everything :) 274networking manually. But don't fear, we'll explain everything. A fully
230</p> 275commented example that covers many different configurations is available in
231 276<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
232<p> 277</p>
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.
284</p>
285
286<p>
287If you need to configure your network connection either because you need
288specific DHCP options or because you do not use DHCP at all, open
233First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> 289<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
234is used in this example): 290this example):
235</p> 291</p>
236 292
237<pre caption="Opening /etc/conf.d/net for editing"> 293<pre caption="Opening /etc/conf.d/net for editing">
238# <i>nano -w /etc/conf.d/net</i> 294# <i>nano -w /etc/conf.d/net</i>
239</pre> 295</pre>
240 296
241<p> 297<p>
242The first variable you'll find is <c>iface_eth0</c>. It uses the following 298You will see the following file:
243syntax:
244</p>
245
246<pre caption="iface_eth0 syntaxis">
247iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
248</pre>
249
250<p> 299</p>
251If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 300
252to <c>dhcp</c>. However, if you need to setup your network manually and you're 301<pre caption="Default /etc/conf.d/net">
253not familiar with all the above terms, please read the section on <uri 302# This blank configuration will automatically use DHCP for any net.*
254link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 303# scripts in /etc/init.d. To create a more complete configuration,
255Terminology</uri> if you haven't done so already. 304# please review /usr/share/doc/openrc-*/net.example.bz2 and save
305# your configuration in /etc/conf.d/net (this file :]!).
306</pre>
307
256</p> 308<p>
257 309To enter your own IP address, netmask and gateway, you need
310to set both <c>config_eth0</c> and <c>routes_eth0</c>:
258<p> 311</p>
259So lets give two examples; the first one uses DHCP, the second one a static IP 312
260(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 313<pre caption="Manually setting IP information for eth0">
261192.168.0.1: 314config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255"
315routes_eth0="default via 192.168.0.1"
316</pre>
317
262</p> 318<p>
263 319To use DHCP, define <c>config_eth0</c>:
264<pre caption="Examples for /etc/conf.d/net">
265<comment>(For DHCP:)</comment>
266iface_eth0="dhcp"
267
268<comment>(For static IP:)</comment>
269iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
270gateway="eth0/192.168.0.1"
271</pre>
272
273<p> 320</p>
274If you have several network interfaces, create extra <c>iface_eth</c> variables, 321
275like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 322<pre caption="Automatically obtaining an IP address for eth0">
276shouldn't be reproduced as you can only set one gateway per computer. 323config_eth0="dhcp"
324</pre>
325
326<p>
327Please read <path>/usr/share/doc/openrc-*/net.example.bz2</path> for a
328list of all available options. Be sure to also read your DHCP client manpage if
329you need to set specific DHCP options.
330</p>
331
332<p>
333If you have several network interfaces repeat the above steps for
334<c>config_eth1</c>, <c>config_eth2</c>, etc.
277</p> 335</p>
278 336
279<p> 337<p>
280Now save the configuration and exit to continue. 338Now save the configuration and exit to continue.
281</p> 339</p>
285<subsection> 343<subsection>
286<title>Automatically Start Networking at Boot</title> 344<title>Automatically Start Networking at Boot</title>
287<body> 345<body>
288 346
289<p> 347<p>
290To have your network interfaces activated at boot, you need to add those to the 348To have your network interfaces activated at boot, you need to add them to the
291default runlevel. If you have PCMCIA interfaces you should skip this action as 349default runlevel.
292the PCMCIA interfaces are started by the PCMCIA init script.
293</p> 350</p>
294 351
295<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>
296# <i>rc-update add net.eth0 default</i> 355# <i>rc-update add net.eth0 default</i>
297</pre> 356</pre>
298 357
299<p> 358<p>
300If you have several network interfaces, you need to create the appropriate 359If you have several network interfaces, you need to create the appropriate
301<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
302use <c>ln</c> to do this: 361<path>net.eth0</path>.
303</p>
304
305<pre caption="Creating extra initscripts">
306# <i>cd /etc/init.d</i>
307# <i>ln -s net.eth0 net.eth1</i>
308# <i>rc-update add net.eth1 default</i>
309</pre> 362</p>
310 363
311</body> 364</body>
312</subsection> 365</subsection>
313<subsection> 366<subsection>
314<title>Writing Down Network Information</title> 367<title>Writing Down Network Information</title>
315<body> 368<body>
316 369
317<p> 370<p>
318You 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
319<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
320for 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.
321internal 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
322<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 375set up your own internal DNS system.
323open <path>/etc/hosts</path> and fill in the values:
324</p> 376</p>
325 377
326<pre caption="Opening /etc/hosts"> 378<pre caption="Opening /etc/hosts">
327# <i>nano -w /etc/hosts</i> 379# <i>nano -w /etc/hosts</i>
328</pre> 380</pre>
329 381
330<pre caption="Filling in the networking information"> 382<pre caption="Filling in the networking information">
383<comment>(This defines the current system)</comment>
331127.0.0.1 tux.homenetwork localhost 384127.0.0.1 tux.homenetwork tux localhost
332192.168.0.5 jenny
333192.168.0.56 benny
334</pre>
335 385
336<p> 386<comment>(Define extra systems on your network,
337If your system is the only system (or the nameservers handle all name 387they need to have a static IP to be defined this way.)</comment>
338resolution) a single line is sufficient: 388192.168.0.5 jenny.homenetwork jenny
339</p> 389192.168.0.6 benny.homenetwork benny
340
341<pre caption="/etc/hosts for lonely or fully integrated PCs">
342127.0.0.1 localhost tux
343</pre> 390</pre>
344 391
345<p> 392<p>
346Save and exit the editor to continue. 393Save and exit the editor to continue.
347</p> 394</p>
348 395
349<p> 396<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
350If you don't have PCMCIA, you can now continue with <uri 397If you don't have PCMCIA, you can now continue with <uri
351link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 398link="#sysinfo">System Information</uri>. PCMCIA-users should read the
352following topic on PCMCIA. 399following topic on PCMCIA.
353</p> 400</p>
354 401
355</body> 402</body>
356</subsection> 403</subsection>
357<subsection> 404<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
358<title>Optional: Get PCMCIA Working</title> 405<title>Optional: Get PCMCIA Working</title>
359<body> 406<body>
360 407
361<p> 408<p>
362PCMCIA-users should first install the <c>pcmcia-cs</c> package: 409PCMCIA users should first install the <c>pcmciautils</c> package.
363</p> 410</p>
364 411
365<pre caption="Installing pcmcia-cs"> 412<pre caption="Installing pcmciautils">
366# <i>emerge -k pcmcia-cs</i> 413# <i>emerge pcmciautils</i>
367</pre>
368
369<p>
370When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>
371runlevel:
372</p>
373
374<pre caption="Adding pcmcia to the default runlevel">
375# <i>rc-update add pcmcia boot</i>
376</pre> 414</pre>
377 415
378</body> 416</body>
379</subsection> 417</subsection>
380</section> 418</section>
419
420<section id="sysinfo">
421<title>System Information</title>
381<section> 422<subsection>
423<title>Root Password</title>
424<body>
425
426<p>
427First we set the root password by typing:
428</p>
429
430<pre caption="Setting the root password">
431# <i>passwd</i>
432</pre>
433
434</body>
435</subsection>
436<subsection>
382<title>System Information</title> 437<title>System Information</title>
383<body> 438<body>
384 439
385<p> 440<p>
386Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 441Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
390<pre caption="Opening /etc/rc.conf"> 445<pre caption="Opening /etc/rc.conf">
391# <i>nano -w /etc/rc.conf</i> 446# <i>nano -w /etc/rc.conf</i>
392</pre> 447</pre>
393 448
394<p> 449<p>
450When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
451</p>
452
453<p>
395As you can see, this file is well commented to help you set up the necessary 454As you can see, this file is well commented to help you set up the necessary
396configuration variables. When you're finished configuring 455configuration variables. You can configure your system to use unicode and
397<path>/etc/rc.conf</path>, save and exit to continue. 456define your default editor and your display manager (like gdm or kdm).
457</p>
458
398</p> 459<p>
460Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
461Edit it to configure your keyboard.
462</p>
399 463
464<pre caption="Opening /etc/conf.d/keymaps">
465# <i>nano -w /etc/conf.d/keymaps</i>
466</pre>
467
468<p>
469Take special care with the <c>keymap</c> variable. If you select the wrong
470<c>keymap</c>, you will get weird results when typing on your keyboard.
471</p>
472
473<note test="substring(func:keyval('arch'),1,3)='PPC'">
474PPC uses x86 keymaps on most systems.
475</note>
476
477<p>
478When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
479exit.
480</p>
481
482<p>
483Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
484according to your needs.
485</p>
486
487<pre caption="Opening /etc/conf.d/hwclock">
488# <i>nano -w /etc/conf.d/hwclock</i>
489</pre>
490
491<p>
492If your hardware clock is not using UTC, you need to add <c>clock="local"</c>
493to the file. Otherwise you will notice some clock skew.
494</p>
495
496<p>
497When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and
498exit.
499</p>
500
501<p>
502You should define the timezone that you previously copied to
503<path>/etc/localtime</path> in the <path>/etc/timezone</path> file so that
504further upgrades of the <c>sys-libs/timezone-data</c> package can update
505<path>/etc/localtime</path> automatically. For instance, if you used the
506Europe/Brussels timezone, you would write <c>Europe/Brussels</c> in the
507<path>/etc/timezone</path> file.
508</p>
509
510<p test="not(func:keyval('arch')='PPC64')">
511Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
512Tools</uri>.
513</p>
514
515</body>
516</subsection>
517<subsection test="func:keyval('arch')='PPC64'">
518<title>Configuring the Console</title>
400</body> 519<body>
520
521<p>
522If you are using a virtual console, you must uncomment the appropriate line in
523<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
524</p>
525
526<pre caption="Enabling hvc or hvsi support in /etc/inittab">
527hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
528hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
529</pre>
530
531<p>
532You should also take this time to verify that the appropriate console is
533listed in <path>/etc/securetty</path>.
534</p>
535
536<p>
537You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
538System Tools</uri>.
539</p>
540
541</body>
542</subsection>
401</section> 543</section>
402</sections> 544</sections>

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.109

  ViewVC Help
Powered by ViewVC 1.1.20