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

Legend:
Removed from v.1.65  
changed lines
  Added in v.1.123

  ViewVC Help
Powered by ViewVC 1.1.20