/[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.57 Revision 1.109
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.57 2005/04/07 16:12:35 swift Exp $ --> 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 $ -->
8 8
9<sections> 9<sections>
10 10
11<abstract>
12You need to edit some important configuration files. In this chapter
13you receive an overview of these files and an explanation on how to
14proceed.
15</abstract>
16
11<version>2.1</version> 17<version>16</version>
12<date>2005-04-07</date> 18<date>2012-02-22</date>
13 19
14<section> 20<section>
15<title>Filesystem Information</title> 21<title>Filesystem Information</title>
16<subsection> 22<subsection>
17<title>What is fstab?</title> 23<title>What is fstab?</title>
18<body> 24<body>
19 25
20<p> 26<p>
21Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 28<path>/etc/fstab</path>. This file contains the mount points of those partitions
23(where they are seen in the file system structure), how they should be mounted 29(where they are seen in the file system structure), how they should be mounted
24and with what special options (automatically or not, whether users can mount 30and with what special options (automatically or not, whether users can mount
25them or not, etc.) 31them or not, etc.)
26</p> 32</p>
27 33
41<li> 47<li>
42 The first field shows the <b>partition</b> described (the path to the device 48 The first field shows the <b>partition</b> described (the path to the device
43 file) 49 file)
44</li> 50</li>
45<li> 51<li>
46 The second field shows the <b>mountpoint</b> at which the partition should be 52 The second field shows the <b>mount point</b> at which the partition should be
47 mounted 53 mounted
48</li> 54</li>
49<li> 55<li>
50 The third field shows the <b>filesystem</b> used by the partition 56 The third field shows the <b>filesystem</b> used by the partition
51</li> 57</li>
52<li> 58<li>
53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 59 The fourth field shows the <b>mount options</b> used by <c>mount</c> when it
54 wants to mount the partition. As every filesystem has its own mountoptions, 60 wants to mount the partition. As every filesystem has its own mount options,
55 you are encouraged to read the mount man page (<c>man mount</c>) for a full 61 you are encouraged to read the mount man page (<c>man mount</c>) for a full
56 listing. Multiple mountoptions are comma-separated. 62 listing. Multiple mount options are comma-separated.
57</li> 63</li>
58<li> 64<li>
59 The fifth field is used by <c>dump</c> to determine if the partition needs to 65 The fifth field is used by <c>dump</c> to determine if the partition needs to
60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 66 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
61</li> 67</li>
65 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 71 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
66 (or <c>0</c> if a filesystem check isn't necessary). 72 (or <c>0</c> if a filesystem check isn't necessary).
67</li> 73</li>
68</ul> 74</ul>
69 75
70<p> 76<impo>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab 77The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72file</e>, so start <c>nano</c> (or your favorite editor) to create your 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
73<path>/etc/fstab</path>: 79</impo>
74</p>
75 80
76<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
77# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
78</pre> 83</pre>
79 84
85</body>
86<body test="func:keyval('/boot')">
87
80<p> 88<p>
81Let us take a look at how we write down the options for the <path>/boot</path> 89Let us take a look at how we write down the options for the <path>/boot</path>
82partition. This is just an example, so if your architecture doesn't require a 90partition. This is just an example, if you didn't or couldn't create a
83<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. 91<path>/boot</path>, don't copy it.
84</p>
85
86<p> 92</p>
93
94<p>
87In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
88<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 96usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
89It needs to be checked during boot, so we would write down: 97filesystem. It needs to be checked during boot, so we would write down:
90</p> 98</p>
91 99
92<pre caption="An example /boot line for /etc/fstab"> 100<pre caption="An example /boot line for /etc/fstab">
93/dev/hda1 /boot ext2 defaults 1 2 101<keyval id="/boot"/> /boot ext2 defaults 1 2
94</pre> 102</pre>
95 103
96<p> 104<p>
97Some users don't want their <path>/boot</path> partition to be mounted 105Some users don't want their <path>/boot</path> partition to be mounted
98automatically to improve their system's security. Those people should 106automatically to improve their system's security. Those people should
99substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 107substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
100manually mount this partition every time you want to use it. 108manually mount this partition every time you want to use it.
101</p> 109</p>
102 110
103<p> 111</body>
104Now, to improve performance, most users would want to add the <c>noatime</c> 112<body>
105option as mountoption, which results in a faster system since access times 113
106aren't registered (you don't need those generally anyway):
107</p> 114<p>
108 115Add the rules that match your partitioning scheme and append rules for
109<pre caption="An improved /boot line for /etc/fstab"> 116your CD-ROM drive(s), and of course, if you have other partitions or drives,
110/dev/hda1 /boot ext2 defaults,noatime 1 2 117for those too.
111</pre>
112
113<p> 118</p>
114If we continue with this, we would end up with the following three lines (for 119
115<path>/boot</path>, <path>/</path> and the swap partition):
116</p> 120<p>
121Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
122</p>
117 123
118<pre caption="Three /etc/fstab lines"> 124<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
119/dev/hda1 /boot ext2 defaults,noatime 1 2 125<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
120/dev/hda2 none swap sw 0 0 126/dev/sda3 none swap sw 0 0
121/dev/hda3 / ext3 noatime 0 1 127/dev/sda4 / ext3 noatime 0 1
122</pre>
123 128
124<p> 129/dev/cdrom /mnt/cdrom auto noauto,user 0 0
125To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> 130
126(required) and for your CD-ROM drive (and of course, if you have other 131proc /proc proc defaults 0 0
127partitions or drives, for those too): 132shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
128</p> 133</pre>
129 134
130<pre caption="A full /etc/fstab example"> 135<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'">
131/dev/hda1 /boot ext2 defaults,noatime 1 2 136<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132/dev/hda2 none swap sw 0 0 137/dev/sda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 138/dev/sda3 / ext3 noatime 0 1
134 139
140/dev/cdrom /mnt/cdrom auto noauto,user 0 0
141
135none /proc proc defaults 0 0 142proc /proc proc defaults 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 143shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
144</pre>
137 145
146<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
147/dev/sda1 / ext3 noatime 0 1
148/dev/sda2 none swap sw 0 0
149/dev/sda4 /usr ext3 noatime 0 2
150/dev/sda5 /var ext3 noatime 0 2
151/dev/sda6 /home ext3 noatime 0 2
152
153<comment># You must add the rules for openprom</comment>
154openprom /proc/openprom openpromfs defaults 0 0
155
138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 156/dev/cdrom /mnt/cdrom auto noauto,user 0 0
157
158proc /proc proc defaults 0 0
159shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
160</pre>
161
162<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or
163func:keyval('arch')='PPC64'">
164/dev/sda4 / ext3 noatime 0 1
165/dev/sda3 none swap sw 0 0
166
167/dev/cdrom /mnt/cdrom auto noauto,user 0 0
168
169proc /proc proc defaults 0 0
170shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
139</pre> 171</pre>
140 172
141<p> 173<p>
142<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 174<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
143removable media as they can be created with one of many filesystems) and 175removable media as they can be created with one of many filesystems) and
144<c>user</c> makes it possible for non-root users to mount the CD. 176<c>user</c> makes it possible for non-root users to mount the CD.
145</p> 177</p>
146 178
147<p> 179<p>
148Now use the above example to create your <path>/etc/fstab</path>. If you are a 180To improve performance, most users would want to add the <c>noatime</c>
149<b>SPARC</b>-user, you should add the following line to your 181mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 182aren't registered (you don't need those generally anyway).
151too:
152</p>
153
154<pre caption="Adding openprom filesystem to /etc/fstab">
155none /proc/openprom openpromfs defaults 0 0
156</pre> 183</p>
157 184
158<p> 185<p>
159Double-check your <path>/etc/fstab</path>, save and quit to continue. 186Double-check your <path>/etc/fstab</path>, save and quit to continue.
160</p> 187</p>
161 188
163</subsection> 190</subsection>
164</section> 191</section>
165<section> 192<section>
166<title>Networking Information</title> 193<title>Networking Information</title>
167<subsection> 194<subsection>
168<title>Hostname, Domainname etc.</title> 195<title>Host name, Domainname, etc</title>
169<body> 196<body>
170 197
171<p> 198<p>
172One of the choices the user has to make is name his/her PC. This seems to be 199One of the choices the user has to make is name his/her PC. This seems to be
173quite easy, but <e>lots</e> of users are having difficulties finding the 200quite easy, but <e>lots</e> of users are having difficulties finding the
174appropriate name for their Linux-pc. To speed things up, know that any name you 201appropriate name for their Linux-pc. To speed things up, know that any name you
175choose can be changed afterwards. For all we care, you can just call your system 202choose can be changed afterwards. For all we care, you can just call your system
176<c>tux</c> and domain <c>homenetwork</c>. 203<c>tux</c> and domain <c>homenetwork</c>.
177</p> 204</p>
178 205
179<p>
180We use these values in the next examples. First we set the hostname:
181</p>
182
183<pre caption="Setting the hostname"> 206<pre caption="Setting the host name">
184# <i>echo tux &gt; /etc/hostname</i> 207# <i>nano -w /etc/conf.d/hostname</i>
185</pre>
186 208
209<comment>(Set the hostname variable to your host name)</comment>
210hostname="<i>tux</i>"
211</pre>
212
187<p> 213<p>
188Second 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.
189</p> 218</p>
190 219
191<pre caption="Setting the domainname"> 220<pre caption="Setting the domainname">
192# <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>"
193</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>
194 232
195<p> 233<p>
196If 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
197one), you need to define that one too: 235one), you need to define that one too:
198</p> 236</p>
199 237
200<pre caption="Setting the NIS domainname"> 238<pre caption="Setting the NIS domainname">
201# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 239# <i>nano -w /etc/conf.d/net</i>
202</pre>
203 240
204<p> 241<comment>(Set the nis_domain variable to your NIS domain name)</comment>
205Now add the <c>domainname</c> script to the default runlevel: 242nis_domain_lo="<i>my-nisdomain</i>"
206</p> 243</pre>
207 244
208<pre caption="Adding domainname to the default runlevel"> 245<note>
209# <i>rc-update add domainname default</i> 246For more information on configuring DNS and NIS, please read the examples
210</pre> 247provided in <path>/usr/share/doc/openrc-*/net.example.bz2</path> which
248can be read using <c>bzless</c>. Also, you may want to emerge <c>openresolv</c>
249to help manage your DNS/NIS setup.
250</note>
211 251
212</body> 252</body>
213</subsection> 253</subsection>
214<subsection> 254<subsection>
215<title>Configuring your Network</title> 255<title>Configuring your Network</title>
216<body> 256<body>
217 257
218<p> 258<p>
219Before 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
220that 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
221just 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
222your Gentoo system permanently. 262your Gentoo system permanently.
223</p> 263</p>
224 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
225<p> 271<p>
226All 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
227a straightforward yet not intuitive syntax if you don't know how to set up 273a straightforward yet not intuitive syntax if you don't know how to set up
228networking manually. But don't fear, we'll explain everything :) 274networking manually. But don't fear, we'll explain everything. A fully
229</p> 275commented example that covers many different configurations is available in
230 276<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
231<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
232First 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
233is used in this example): 290this example):
234</p> 291</p>
235 292
236<pre caption="Opening /etc/conf.d/net for editing"> 293<pre caption="Opening /etc/conf.d/net for editing">
237# <i>nano -w /etc/conf.d/net</i> 294# <i>nano -w /etc/conf.d/net</i>
238</pre> 295</pre>
239 296
240<p> 297<p>
241The first variable you'll find is <c>iface_eth0</c>. It uses the following 298You will see the following file:
242syntax:
243</p>
244
245<pre caption="iface_eth0 syntaxis">
246iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
247</pre>
248
249<p> 299</p>
250If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 300
251to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 301<pre caption="Default /etc/conf.d/net">
252If you need to set up your network manually and you're 302# This blank configuration will automatically use DHCP for any net.*
253not familiar with all the above terms, please read the section on <uri 303# scripts in /etc/init.d. To create a more complete configuration,
254link="?part=1&amp;chap=3#network_term">Understanding Network 304# please review /usr/share/doc/openrc-*/net.example.bz2 and save
255Terminology</uri> if you haven't done so already. 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 let us give three examples; the first one uses DHCP, the second one a static 312
260IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 313<pre caption="Manually setting IP information for eth0">
261gateway 192.168.0.1 while the third one just activates the interface for 314config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255"
262rp-pppoe usage: 315routes_eth0="default via 192.168.0.1"
316</pre>
317
263</p> 318<p>
264 319To use DHCP, define <c>config_eth0</c>:
265<pre caption="Examples for /etc/conf.d/net">
266<comment>(For DHCP)</comment>
267iface_eth0="dhcp"
268<comment># Some network admins require that you use the</comment>
269<comment># hostname and domainname provided by the DHCP server.</comment>
270<comment># In that case, add the following to let dhcpcd use them.</comment>
271<comment># That will override your own hostname and domainname definitions.</comment>
272dhcpcd_eth0="-HD"
273<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
274<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
275dhcpcd_eth0="-N"
276
277<comment>(For static IP)</comment>
278iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
279gateway="eth0/192.168.0.1"
280
281<comment>(For rp-pppoe)</comment>
282iface_eth0="up"
283</pre>
284
285<p> 320</p>
286If you have several network interfaces, create extra <c>iface_eth</c> variables, 321
287like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 322<pre caption="Automatically obtaining an IP address for eth0">
288shouldn'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.
289</p> 335</p>
290 336
291<p> 337<p>
292Now save the configuration and exit to continue. 338Now save the configuration and exit to continue.
293</p> 339</p>
298<title>Automatically Start Networking at Boot</title> 344<title>Automatically Start Networking at Boot</title>
299<body> 345<body>
300 346
301<p> 347<p>
302To have your network interfaces activated at boot, you need to add them to the 348To have your network interfaces activated at boot, you need to add them to the
303default runlevel. If you have PCMCIA interfaces you should skip this action as 349default runlevel.
304the PCMCIA interfaces are started by the PCMCIA init script.
305</p> 350</p>
306 351
307<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>
308# <i>rc-update add net.eth0 default</i> 355# <i>rc-update add net.eth0 default</i>
309</pre> 356</pre>
310 357
311<p> 358<p>
312If you have several network interfaces, you need to create the appropriate 359If you have several network interfaces, you need to create the appropriate
313<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
314use <c>ln</c> to do this: 361<path>net.eth0</path>.
315</p>
316
317<pre caption="Creating extra initscripts">
318# <i>cd /etc/init.d</i>
319# <i>ln -s net.eth0 net.eth1</i>
320# <i>rc-update add net.eth1 default</i>
321</pre> 362</p>
322 363
323</body> 364</body>
324</subsection> 365</subsection>
325<subsection> 366<subsection>
326<title>Writing Down Network Information</title> 367<title>Writing Down Network Information</title>
327<body> 368<body>
328 369
329<p> 370<p>
330You 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
331<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
332for 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.
333internal 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
334<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 375set up your own internal DNS system.
335open <path>/etc/hosts</path> and fill in the values:
336</p> 376</p>
337 377
338<pre caption="Opening /etc/hosts"> 378<pre caption="Opening /etc/hosts">
339# <i>nano -w /etc/hosts</i> 379# <i>nano -w /etc/hosts</i>
340</pre> 380</pre>
341 381
342<pre caption="Filling in the networking information"> 382<pre caption="Filling in the networking information">
343127.0.0.1 localhost 383<comment>(This defines the current system)</comment>
384127.0.0.1 tux.homenetwork tux localhost
385
386<comment>(Define extra systems on your network,
387they need to have a static IP to be defined this way.)</comment>
344192.168.0.5 jenny.homenetwork jenny 388192.168.0.5 jenny.homenetwork jenny
345192.168.0.6 benny.homenetwork benny 389192.168.0.6 benny.homenetwork benny
346192.168.0.7 tux.homenetwork tux
347</pre>
348
349<p>
350If your system is the only system (or the nameservers handle all name
351resolution) a single line is sufficient. For instance, if you want to call your
352system <c>tux</c>:
353</p>
354
355<pre caption="/etc/hosts for lonely or fully integrated PCs">
356127.0.0.1 localhost tux
357</pre> 390</pre>
358 391
359<p> 392<p>
360Save and exit the editor to continue. 393Save and exit the editor to continue.
361</p> 394</p>
362 395
363<p> 396<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
364If you don't have PCMCIA, you can now continue with <uri 397If you don't have PCMCIA, you can now continue with <uri
365link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 398link="#sysinfo">System Information</uri>. PCMCIA-users should read the
366following topic on PCMCIA. 399following topic on PCMCIA.
367</p> 400</p>
368 401
369</body> 402</body>
370</subsection> 403</subsection>
371<subsection> 404<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
372<title>Optional: Get PCMCIA Working</title> 405<title>Optional: Get PCMCIA Working</title>
373<body> 406<body>
374 407
375<note>
376pcmcia-cs is only available for x86, amd64 and ppc platforms.
377</note>
378
379<p> 408<p>
380PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 409PCMCIA users should first install the <c>pcmciautils</c> package.
381includes users who will be working with a 2.6 kernel (even though they won't be
382using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
383to avoid installing xorg-x11 at this moment:
384</p> 410</p>
385 411
386<pre caption="Installing pcmcia-cs"> 412<pre caption="Installing pcmciautils">
387# <i>USE="-X" emerge pcmcia-cs</i> 413# <i>emerge pcmciautils</i>
388</pre>
389
390<p>
391When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
392runlevel:
393</p>
394
395<pre caption="Adding pcmcia to the default runlevel">
396# <i>rc-update add pcmcia default</i>
397</pre> 414</pre>
398 415
399</body> 416</body>
400</subsection> 417</subsection>
401</section> 418</section>
402<section> 419
420<section id="sysinfo">
403<title>System Information</title> 421<title>System Information</title>
404<subsection> 422<subsection>
405<title>Root Password</title> 423<title>Root Password</title>
406<body> 424<body>
407 425
411 429
412<pre caption="Setting the root password"> 430<pre caption="Setting the root password">
413# <i>passwd</i> 431# <i>passwd</i>
414</pre> 432</pre>
415 433
416<p>
417If you want root to be able to log on through the serial console, add
418<c>tts/0</c> to <path>/etc/securetty</path>:
419</p>
420
421<pre caption="Adding tts/0 to /etc/securetty">
422# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
423</pre>
424
425</body> 434</body>
426</subsection> 435</subsection>
427<subsection> 436<subsection>
428<title>System Information</title> 437<title>System Information</title>
429<body> 438<body>
436<pre caption="Opening /etc/rc.conf"> 445<pre caption="Opening /etc/rc.conf">
437# <i>nano -w /etc/rc.conf</i> 446# <i>nano -w /etc/rc.conf</i>
438</pre> 447</pre>
439 448
440<p> 449<p>
450When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
451</p>
452
453<p>
441As 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
442configuration variables. Take special care with the <c>KEYMAP</c> setting: if 455configuration variables. You can configure your system to use unicode and
443you select the wrong <c>KEYMAP</c> you will get weird results when typing on 456define your default editor and your display manager (like gdm or kdm).
444your keyboard. 457</p>
458
445</p> 459<p>
460Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
461Edit it to configure your keyboard.
462</p>
446 463
447<note> 464<pre caption="Opening /etc/conf.d/keymaps">
448Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 465# <i>nano -w /etc/conf.d/keymaps</i>
449select an i386 keymap (such as "us") instead of "sunkeymap". 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.
450</note> 475</note>
451 476
452<p> 477<p>
453<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 478When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
454ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 479exit.
455to set a mac/ppc keymap in <path>rc.conf</path>.
456</p>
457
458<p> 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>
459When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 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')">
460continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 511Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
461Tools</uri>. 512Tools</uri>.
513</p>
514
515</body>
516</subsection>
517<subsection test="func:keyval('arch')='PPC64'">
518<title>Configuring the Console</title>
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>.
462</p> 539</p>
463 540
464</body> 541</body>
465</subsection> 542</subsection>
466</section> 543</section>

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

  ViewVC Help
Powered by ViewVC 1.1.20