/[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.122
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.122 2013/07/24 20:40:40 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>28</version>
12<date>2005-04-07</date> 18<date>2013-07-24</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 0 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 0 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 / ext4 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>
126(required) and for your CD-ROM drive (and of course, if you have other
127partitions or drives, for those too):
128</p> 130</pre>
129 131
130<pre caption="A full /etc/fstab example"> 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'">
131/dev/hda1 /boot ext2 defaults,noatime 1 2 133<keyval id="/boot"/> /boot ext2 defaults,noatime 0 2
132/dev/hda2 none swap sw 0 0 134/dev/sda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 135/dev/sda3 / ext4 noatime 0 1
134 136
135none /proc proc defaults 0 0 137/dev/cdrom /mnt/cdrom auto noauto,user 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 138</pre>
137 139
140<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
141/dev/sda1 / ext4 noatime 0 1
142/dev/sda2 none swap sw 0 0
143/dev/sda4 /usr ext4 noatime 0 2
144/dev/sda5 /var ext4 noatime 0 2
145/dev/sda6 /home ext4 noatime 0 2
146
147<comment># You must add the rules for openprom</comment>
148openprom /proc/openprom openpromfs defaults 0 0
149
138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 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'">
155/dev/sda4 / ext4 noatime 0 1
156/dev/sda3 none swap sw 0 0
157
158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
139</pre> 159</pre>
140 160
141<p> 161<p>
142<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
143removable 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
144<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.
145</p> 165</p>
146 166
147<p> 167<p>
148Now 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>
149<b>SPARC</b>-user, you should add the following line to your 169mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 170aren'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> 171</p>
157 172
158<p> 173<p>
159Double-check your <path>/etc/fstab</path>, save and quit to continue. 174Double-check your <path>/etc/fstab</path>, save and quit to continue.
160</p> 175</p>
161 176
163</subsection> 178</subsection>
164</section> 179</section>
165<section> 180<section>
166<title>Networking Information</title> 181<title>Networking Information</title>
167<subsection> 182<subsection>
168<title>Hostname, Domainname etc.</title> 183<title>Host name, Domainname, etc</title>
169<body> 184<body>
170 185
171<p> 186<p>
172One of the choices the user has to make is name his/her PC. This seems to be 187One of the choices the user has to make is name his/her PC. This seems to be
173quite easy, but <e>lots</e> of users are having difficulties finding the 188quite easy, but <e>lots</e> of users are having difficulties finding the
174appropriate name for their Linux-pc. To speed things up, know that any name you 189appropriate name for their Linux-pc. To speed things up, know that any name you
175choose can be changed afterwards. For all we care, you can just call your system 190choose can be changed afterwards. For all we care, you can just call your system
176<c>tux</c> and domain <c>homenetwork</c>. 191<c>tux</c> and domain <c>homenetwork</c>.
177</p> 192</p>
178 193
179<p>
180We use these values in the next examples. First we set the hostname:
181</p>
182
183<pre caption="Setting the hostname"> 194<pre caption="Setting the host name">
184# <i>echo tux &gt; /etc/hostname</i> 195# <i>nano -w /etc/conf.d/hostname</i>
185</pre>
186 196
197<comment>(Set the hostname variable to your host name)</comment>
198hostname="<i>tux</i>"
199</pre>
200
187<p> 201<p>
188Second 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.
189</p> 206</p>
190 207
191<pre caption="Setting the domainname"> 208<pre caption="Setting the domainname">
192# <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>"
193</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>
194 220
195<p> 221<p>
196If 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
197one), you need to define that one too: 223one), you need to define that one too:
198</p> 224</p>
199 225
200<pre caption="Setting the NIS domainname"> 226<pre caption="Setting the NIS domainname">
201# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 227# <i>nano -w /etc/conf.d/net</i>
202</pre>
203 228
204<p> 229<comment>(Set the nis_domain variable to your NIS domain name)</comment>
205Now add the <c>domainname</c> script to the default runlevel: 230nis_domain_lo="<i>my-nisdomain</i>"
206</p> 231</pre>
207 232
208<pre caption="Adding domainname to the default runlevel"> 233<note>
209# <i>rc-update add domainname default</i> 234For more information on configuring DNS and NIS, please read the examples
210</pre> 235provided in <path>/usr/share/doc/openrc-*/net.example.bz2</path> which
236can be read using <c>bzless</c>. Also, you may want to emerge <c>openresolv</c>
237to help manage your DNS/NIS setup.
238</note>
211 239
212</body> 240</body>
213</subsection> 241</subsection>
214<subsection> 242<subsection>
215<title>Configuring your Network</title> 243<title>Configuring your Network</title>
216<body> 244<body>
217 245
218<p> 246<p>
219Before you get that "Hey, we've had that already"-feeling, you should remember 247Before 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 248that 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 249just for the installation. Right now you are going to configure networking for
222your Gentoo system permanently. 250your Gentoo system permanently.
223</p> 251</p>
224 252
253<note>
254More detailed information about networking, including advanced topics like
255bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
256link="?part=4">Gentoo Network Configuration</uri> section.
257</note>
258
225<p> 259<p>
226All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 260All 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 261a straightforward yet not intuitive syntax if you don't know how to set up
228networking manually. But don't fear, we'll explain everything :) 262networking manually. But don't fear, we'll explain everything. A fully
229</p> 263commented example that covers many different configurations is available in
230 264<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
231<p> 265</p>
266
267<p>
268DHCP is used by default. For DHCP to work, you will need to install a DHCP
269client. This is described later in <uri
270link="?part=1&amp;chap=9#networking-tools">Installing Necessary System
271Tools</uri>. Do not forget to install a DHCP client.
272</p>
273
274<p>
275If you need to configure your network connection either because you need
276specific 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> 277<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233is used in this example): 278this example):
234</p> 279</p>
235 280
236<pre caption="Opening /etc/conf.d/net for editing"> 281<pre caption="Opening /etc/conf.d/net for editing">
237# <i>nano -w /etc/conf.d/net</i> 282# <i>nano -w /etc/conf.d/net</i>
238</pre> 283</pre>
239 284
240<p> 285<p>
241The first variable you'll find is <c>iface_eth0</c>. It uses the following 286You 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> 287</p>
250If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 288
251to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 289<pre caption="Default /etc/conf.d/net">
252If you need to set up your network manually and you're 290# This blank configuration will automatically use DHCP for any net.*
253not familiar with all the above terms, please read the section on <uri 291# scripts in /etc/init.d. To create a more complete configuration,
254link="?part=1&amp;chap=3#network_term">Understanding Network 292# please review /usr/share/doc/openrc-*/net.example.bz2 and save
255Terminology</uri> if you haven't done so already. 293# your configuration in /etc/conf.d/net (this file :]!).
294</pre>
295
256</p> 296<p>
257 297To enter your own IP address, netmask and gateway, you need
298to set both <c>config_eth0</c> and <c>routes_eth0</c>:
258<p> 299</p>
259So let us give three examples; the first one uses DHCP, the second one a static 300
260IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 301<note>
261gateway 192.168.0.1 while the third one just activates the interface for 302This assumes that your network interface will be called eth0. This is, however,
262rp-pppoe usage: 303very system dependent. It is recommended to assume that the interface is named
304the same as the interface name when booted from the installation media <e>if</e>
305the installation media is sufficiently recent. More information can be found in
306<uri link="?part=4&amp;chap=2#doc_chap4">Network Interface Naming</uri>.
307</note>
308
309<pre caption="Manually setting IP information for eth0">
310config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255"
311routes_eth0="default via 192.168.0.1"
312</pre>
313
263</p> 314<p>
264 315To 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> 316</p>
286If you have several network interfaces, create extra <c>iface_eth</c> variables, 317
287like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 318<pre caption="Automatically obtaining an IP address for eth0">
288shouldn't be reproduced as you can only set one gateway per computer. 319config_eth0="dhcp"
320</pre>
321
322<p>
323Please read <path>/usr/share/doc/openrc-*/net.example.bz2</path> for a
324list of all available options. Be sure to also read your DHCP client manpage if
325you need to set specific DHCP options.
326</p>
327
328<p>
329If you have several network interfaces repeat the above steps for
330<c>config_eth1</c>, <c>config_eth2</c>, etc.
289</p> 331</p>
290 332
291<p> 333<p>
292Now save the configuration and exit to continue. 334Now save the configuration and exit to continue.
293</p> 335</p>
298<title>Automatically Start Networking at Boot</title> 340<title>Automatically Start Networking at Boot</title>
299<body> 341<body>
300 342
301<p> 343<p>
302To have your network interfaces activated at boot, you need to add them to the 344To 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 345default runlevel.
304the PCMCIA interfaces are started by the PCMCIA init script.
305</p> 346</p>
306 347
307<pre caption="Adding net.eth0 to the default runlevel"> 348<pre caption="Adding net.eth0 to the default runlevel">
349# <i>cd /etc/init.d</i>
350# <i>ln -s net.lo net.eth0</i>
308# <i>rc-update add net.eth0 default</i> 351# <i>rc-update add net.eth0 default</i>
309</pre> 352</pre>
310 353
311<p> 354<p>
312If you have several network interfaces, you need to create the appropriate 355If 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 356<path>net.*</path> files just like you did with <path>net.eth0</path>.
314use <c>ln</c> to do this: 357</p>
358
315</p> 359<p>
316 360If you later find out the assumption about the network interface name (which we
317<pre caption="Creating extra initscripts"> 361currently document as eth0) was wrong, then
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>
363
364<ol>
365<li>
366update the <path>/etc/conf.d/net</path> file with the correct interface name (like enp3s0
367instead of eth0),
368</li>
369<li>
370create new symbolic link (like <path>/etc/init.d/net.enp3s0</path>),
371</li>
372<li>
373remove the old symbolic link (<c>rm /etc/init.d/net.eth0</c>),
374</li>
375<li>
376add the new one to the default runlevel, and
377</li>
378<li>
379remove the old one using <c>rc-update del net.eth0 default</c>.
380</li>
381</ol>
322 382
323</body> 383</body>
324</subsection> 384</subsection>
325<subsection> 385<subsection>
326<title>Writing Down Network Information</title> 386<title>Writing Down Network Information</title>
327<body> 387<body>
328 388
329<p> 389<p>
330You now need to inform Linux about your network. This is defined in 390You 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 391<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 392hosts 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), 393You 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 394set up your own internal DNS system.
335open <path>/etc/hosts</path> and fill in the values:
336</p> 395</p>
337 396
338<pre caption="Opening /etc/hosts"> 397<pre caption="Opening /etc/hosts">
339# <i>nano -w /etc/hosts</i> 398# <i>nano -w /etc/hosts</i>
340</pre> 399</pre>
341 400
342<pre caption="Filling in the networking information"> 401<pre caption="Filling in the networking information">
343127.0.0.1 localhost 402<comment>(This defines the current system)</comment>
403127.0.0.1 tux.homenetwork tux localhost
404
405<comment>(Define extra systems on your network,
406they need to have a static IP to be defined this way.)</comment>
344192.168.0.5 jenny.homenetwork jenny 407192.168.0.5 jenny.homenetwork jenny
345192.168.0.6 benny.homenetwork benny 408192.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> 409</pre>
358 410
359<p> 411<p>
360Save and exit the editor to continue. 412Save and exit the editor to continue.
361</p> 413</p>
362 414
363<p> 415<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 416If you don't have PCMCIA, you can now continue with <uri
365link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 417link="#sysinfo">System Information</uri>. PCMCIA-users should read the
366following topic on PCMCIA. 418following topic on PCMCIA.
367</p> 419</p>
368 420
369</body> 421</body>
370</subsection> 422</subsection>
371<subsection> 423<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> 424<title>Optional: Get PCMCIA Working</title>
373<body> 425<body>
374 426
375<note>
376pcmcia-cs is only available for x86, amd64 and ppc platforms.
377</note>
378
379<p> 427<p>
380PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 428PCMCIA 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> 429</p>
385 430
386<pre caption="Installing pcmcia-cs"> 431<pre caption="Installing pcmciautils">
387# <i>USE="-X" emerge pcmcia-cs</i> 432# <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> 433</pre>
398 434
399</body> 435</body>
400</subsection> 436</subsection>
401</section> 437</section>
402<section> 438
439<section id="sysinfo">
403<title>System Information</title> 440<title>System Information</title>
404<subsection> 441<subsection>
405<title>Root Password</title> 442<title>Root Password</title>
406<body> 443<body>
407 444
411 448
412<pre caption="Setting the root password"> 449<pre caption="Setting the root password">
413# <i>passwd</i> 450# <i>passwd</i>
414</pre> 451</pre>
415 452
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> 453</body>
426</subsection> 454</subsection>
427<subsection> 455<subsection>
428<title>System Information</title> 456<title>System Information</title>
429<body> 457<body>
430 458
431<p> 459<p>
432Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 460Gentoo uses <path>/etc/rc.conf</path> to configure the services, startup,
433Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) 461and shutdown of your system. Open up <path>/etc/rc.conf</path> and enjoy all
462the comments in the file.
434</p> 463</p>
435 464
436<pre caption="Opening /etc/rc.conf"> 465<pre caption="Configuring services">
437# <i>nano -w /etc/rc.conf</i> 466# <i>nano -w /etc/rc.conf</i>
438</pre> 467</pre>
439 468
440<p> 469<p>
441As you can see, this file is well commented to help you set up the necessary 470When you're finished configuring these two files, save them and exit.
442configuration variables. Take special care with the <c>KEYMAP</c> setting: if 471</p>
443you select the wrong <c>KEYMAP</c> you will get weird results when typing on 472
444your keyboard.
445</p> 473<p>
474Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
475Edit it to configure your keyboard.
476</p>
477
478<pre caption="Opening /etc/conf.d/keymaps">
479# <i>nano -w /etc/conf.d/keymaps</i>
480</pre>
481
482<p>
483Take special care with the <c>keymap</c> variable. If you select the wrong
484<c>keymap</c>, you will get weird results when typing on your keyboard.
485</p>
486
487<note test="substring(func:keyval('arch'),1,3)='PPC'">
488PPC uses x86 keymaps on most systems.
489</note>
490
491<p>
492When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
493exit.
494</p>
495
496<p>
497Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
498according to your needs.
499</p>
500
501<pre caption="Opening /etc/conf.d/hwclock">
502# <i>nano -w /etc/conf.d/hwclock</i>
503</pre>
504
505<p>
506If your hardware clock is not using UTC, you need to add <c>clock="local"</c>
507to the file. Otherwise you will notice some clock skew.
508</p>
509
510<p>
511When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and
512exit.
513</p>
514
515</body>
516</subsection>
517
518<subsection>
519<title>Configure locales</title>
520<body>
521
522<p>
523You will probably only use one or maybe two locales on your system. You have to
524specify locales you will need in <path>/etc/locale.gen</path>.
525</p>
526
527<pre caption="Opening /etc/locale.gen">
528# <i>nano -w /etc/locale.gen</i>
529</pre>
530
531<p>
532The following locales are an example to get both English (United States) and
533German (Germany) with the accompanying character formats (like UTF-8).
534</p>
535
536<pre caption="Specify your locales">
537en_US ISO-8859-1
538en_US.UTF-8 UTF-8
539de_DE ISO-8859-1
540de_DE@euro ISO-8859-15
541</pre>
446 542
447<note> 543<note>
448Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 544You can select your desired locales in the list given by running <c>locale -a</c>.
449select an i386 keymap (such as "us") instead of "sunkeymap".
450</note> 545</note>
451 546
452<p> 547<warn>
453<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 548We strongly suggest that you should use at least one UTF-8 locale because some
454ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 549applications may require it.
455to set a mac/ppc keymap in <path>rc.conf</path>. 550</warn>
551
456</p> 552<p>
457 553The next step is to run <c>locale-gen</c>. It will generates all the locales you
554have specified in the <path>/etc/locale.gen</path> file.
458<p> 555</p>
459When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 556
557<pre caption="Running locale-gen">
558# <i>locale-gen</i>
559</pre>
560
561<p>
562Once done, you now have the possibility to set the system-wide locale settings
563in the <path>/etc/env.d/02locale</path> file:
564</p>
565
566<pre caption="Setting the default system locale in /etc/env.d/02locale">
567LANG="de_DE.UTF-8"
568LC_COLLATE="C"
569</pre>
570
571<p>
572And reload your environment:
573</p>
574
575<pre caption="Reload shell environment">
576# env-update &amp;&amp; source /etc/profile
577</pre>
578
579<p>
580We made a full <uri link="https://wiki.gentoo.org/wiki/Localization/HOWTO">Localization
581Guide</uri> to help you through this process. You can also read the detailed
582<uri link="https://wiki.gentoo.org/wiki/UTF-8">UTF-8 article</uri> for very specific
583informations to enable UTF-8 on your system.
584</p>
585
586<p test="not(func:keyval('arch')='PPC64')">
460continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 587Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
461Tools</uri>. 588Tools</uri>.
589</p>
590
591</body>
592</subsection>
593<subsection test="func:keyval('arch')='PPC64'">
594<title>Configuring the Console</title>
595<body>
596
597<p>
598If you are using a virtual console, you must uncomment the appropriate line in
599<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
600</p>
601
602<pre caption="Enabling hvc or hvsi support in /etc/inittab">
603hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
604hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
605</pre>
606
607<p>
608You should also take this time to verify that the appropriate console is
609listed in <path>/etc/securetty</path>.
610</p>
611
612<p>
613You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
614System Tools</uri>.
462</p> 615</p>
463 616
464</body> 617</body>
465</subsection> 618</subsection>
466</section> 619</section>

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

  ViewVC Help
Powered by ViewVC 1.1.20