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

Legend:
Removed from v.1.45  
changed lines
  Added in v.1.103

  ViewVC Help
Powered by ViewVC 1.1.20