/[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.54 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.54 2004/12/26 14:17:25 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>1.51</version> 17<version>16</version>
12<date>2004-12-26</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>
157
158<p> 183</p>
159If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
160</p>
161
162<pre caption="Adding usbfs filesystem to /etc/fstab">
163none /proc/bus/usb usbfs defaults 0 0
164</pre>
165 184
166<p> 185<p>
167Double-check your <path>/etc/fstab</path>, save and quit to continue. 186Double-check your <path>/etc/fstab</path>, save and quit to continue.
168</p> 187</p>
169 188
171</subsection> 190</subsection>
172</section> 191</section>
173<section> 192<section>
174<title>Networking Information</title> 193<title>Networking Information</title>
175<subsection> 194<subsection>
176<title>Hostname, Domainname etc.</title> 195<title>Host name, Domainname, etc</title>
177<body> 196<body>
178 197
179<p> 198<p>
180One 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
181quite 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
182appropriate 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
183choose 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
184<c>tux</c> and domain <c>homenetwork</c>. 203<c>tux</c> and domain <c>homenetwork</c>.
185</p> 204</p>
186 205
187<p>
188We use these values in the next examples. First we set the hostname:
189</p>
190
191<pre caption="Setting the hostname"> 206<pre caption="Setting the host name">
192# <i>echo tux &gt; /etc/hostname</i> 207# <i>nano -w /etc/conf.d/hostname</i>
193</pre>
194 208
209<comment>(Set the hostname variable to your host name)</comment>
210hostname="<i>tux</i>"
211</pre>
212
195<p> 213<p>
196Second 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.
197</p> 218</p>
198 219
199<pre caption="Setting the domainname"> 220<pre caption="Setting the domainname">
200# <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>"
201</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>
202 232
203<p> 233<p>
204If 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
205one), you need to define that one too: 235one), you need to define that one too:
206</p> 236</p>
207 237
208<pre caption="Setting the NIS domainname"> 238<pre caption="Setting the NIS domainname">
209# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 239# <i>nano -w /etc/conf.d/net</i>
210</pre>
211 240
212<p> 241<comment>(Set the nis_domain variable to your NIS domain name)</comment>
213Now add the <c>domainname</c> script to the default runlevel: 242nis_domain_lo="<i>my-nisdomain</i>"
214</p> 243</pre>
215 244
216<pre caption="Adding domainname to the default runlevel"> 245<note>
217# <i>rc-update add domainname default</i> 246For more information on configuring DNS and NIS, please read the examples
218</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>
219 251
220</body> 252</body>
221</subsection> 253</subsection>
222<subsection> 254<subsection>
223<title>Configuring your Network</title> 255<title>Configuring your Network</title>
224<body> 256<body>
225 257
226<p> 258<p>
227Before 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
228that 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
229just 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
230your Gentoo system permanently. 262your Gentoo system permanently.
231</p> 263</p>
232 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
233<p> 271<p>
234All 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
235a 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
236networking manually. But don't fear, we'll explain everything :) 274networking manually. But don't fear, we'll explain everything. A fully
237</p> 275commented example that covers many different configurations is available in
238 276<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
239<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
240First 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
241is used in this example): 290this example):
242</p> 291</p>
243 292
244<pre caption="Opening /etc/conf.d/net for editing"> 293<pre caption="Opening /etc/conf.d/net for editing">
245# <i>nano -w /etc/conf.d/net</i> 294# <i>nano -w /etc/conf.d/net</i>
246</pre> 295</pre>
247 296
248<p> 297<p>
249The first variable you'll find is <c>iface_eth0</c>. It uses the following 298You will see the following file:
250syntax:
251</p>
252
253<pre caption="iface_eth0 syntaxis">
254iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
255</pre>
256
257<p> 299</p>
258If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 300
259to <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">
260If you need to set up your network manually and you're 302# This blank configuration will automatically use DHCP for any net.*
261not familiar with all the above terms, please read the section on <uri 303# scripts in /etc/init.d. To create a more complete configuration,
262link="?part=1&amp;chap=3#network_term">Understanding Network 304# please review /usr/share/doc/openrc-*/net.example.bz2 and save
263Terminology</uri> if you haven't done so already. 305# your configuration in /etc/conf.d/net (this file :]!).
306</pre>
307
264</p> 308<p>
265 309To enter your own IP address, netmask and gateway, you need
310to set both <c>config_eth0</c> and <c>routes_eth0</c>:
266<p> 311</p>
267So let us give three examples; the first one uses DHCP, the second one a static 312
268IP (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">
269gateway 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"
270rp-pppoe usage: 315routes_eth0="default via 192.168.0.1"
316</pre>
317
271</p> 318<p>
272 319To use DHCP, define <c>config_eth0</c>:
273<pre caption="Examples for /etc/conf.d/net">
274<comment>(For DHCP)</comment>
275iface_eth0="dhcp"
276<comment># Some network admins require that you use the</comment>
277<comment># hostname and domainname provided by the DHCP server.</comment>
278<comment># In that case, add the following to let dhcpcd use them.</comment>
279<comment># That will override your own hostname and domainname definitions.</comment>
280dhcpcd_eth0="-HD"
281<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
282<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
283dhcpcd_eth0="-N"
284
285<comment>(For static IP)</comment>
286iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
287gateway="eth0/192.168.0.1"
288
289<comment>(For rp-pppoe)</comment>
290iface_eth0="up"
291</pre>
292
293<p> 320</p>
294If you have several network interfaces, create extra <c>iface_eth</c> variables, 321
295like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 322<pre caption="Automatically obtaining an IP address for eth0">
296shouldn'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.
297</p> 335</p>
298 336
299<p> 337<p>
300Now save the configuration and exit to continue. 338Now save the configuration and exit to continue.
301</p> 339</p>
306<title>Automatically Start Networking at Boot</title> 344<title>Automatically Start Networking at Boot</title>
307<body> 345<body>
308 346
309<p> 347<p>
310To 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
311default runlevel. If you have PCMCIA interfaces you should skip this action as 349default runlevel.
312the PCMCIA interfaces are started by the PCMCIA init script.
313</p> 350</p>
314 351
315<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>
316# <i>rc-update add net.eth0 default</i> 355# <i>rc-update add net.eth0 default</i>
317</pre> 356</pre>
318 357
319<p> 358<p>
320If you have several network interfaces, you need to create the appropriate 359If you have several network interfaces, you need to create the appropriate
321<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
322use <c>ln</c> to do this: 361<path>net.eth0</path>.
323</p>
324
325<pre caption="Creating extra initscripts">
326# <i>cd /etc/init.d</i>
327# <i>ln -s net.eth0 net.eth1</i>
328# <i>rc-update add net.eth1 default</i>
329</pre> 362</p>
330 363
331</body> 364</body>
332</subsection> 365</subsection>
333<subsection> 366<subsection>
334<title>Writing Down Network Information</title> 367<title>Writing Down Network Information</title>
335<body> 368<body>
336 369
337<p> 370<p>
338You 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
339<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
340for 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.
341internal 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
342<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.
343open <path>/etc/hosts</path> and fill in the values:
344</p> 376</p>
345 377
346<pre caption="Opening /etc/hosts"> 378<pre caption="Opening /etc/hosts">
347# <i>nano -w /etc/hosts</i> 379# <i>nano -w /etc/hosts</i>
348</pre> 380</pre>
349 381
350<pre caption="Filling in the networking information"> 382<pre caption="Filling in the networking information">
351127.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>
352192.168.0.5 jenny.homenetwork jenny 388192.168.0.5 jenny.homenetwork jenny
353192.168.0.6 benny.homenetwork benny 389192.168.0.6 benny.homenetwork benny
354192.168.0.7 tux.homenetwork tux
355</pre>
356
357<p>
358If your system is the only system (or the nameservers handle all name
359resolution) a single line is sufficient. For instance, if you want to call your
360system <c>tux</c>:
361</p>
362
363<pre caption="/etc/hosts for lonely or fully integrated PCs">
364127.0.0.1 localhost tux
365</pre> 390</pre>
366 391
367<p> 392<p>
368Save and exit the editor to continue. 393Save and exit the editor to continue.
369</p> 394</p>
370 395
371<p> 396<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
372If you don't have PCMCIA, you can now continue with <uri 397If you don't have PCMCIA, you can now continue with <uri
373link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 398link="#sysinfo">System Information</uri>. PCMCIA-users should read the
374following topic on PCMCIA. 399following topic on PCMCIA.
375</p> 400</p>
376 401
377</body> 402</body>
378</subsection> 403</subsection>
379<subsection> 404<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
380<title>Optional: Get PCMCIA Working</title> 405<title>Optional: Get PCMCIA Working</title>
381<body> 406<body>
382 407
383<note>
384pcmcia-cs is only available for x86, amd64 and ppc platforms.
385</note>
386
387<p> 408<p>
388PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 409PCMCIA users should first install the <c>pcmciautils</c> package.
389includes users who will be working with a 2.6 kernel (even though they won't be
390using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
391to avoid installing xorg-x11 at this moment:
392</p> 410</p>
393 411
394<pre caption="Installing pcmcia-cs"> 412<pre caption="Installing pcmciautils">
395# <i>USE="-X" emerge pcmcia-cs</i> 413# <i>emerge pcmciautils</i>
396</pre>
397
398<p>
399When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
400runlevel:
401</p>
402
403<pre caption="Adding pcmcia to the default runlevel">
404# <i>rc-update add pcmcia default</i>
405</pre> 414</pre>
406 415
407</body> 416</body>
408</subsection> 417</subsection>
409</section> 418</section>
410<section> 419
420<section id="sysinfo">
411<title>System Information</title> 421<title>System Information</title>
412<subsection> 422<subsection>
413<title>Root Password</title> 423<title>Root Password</title>
414<body> 424<body>
415 425
419 429
420<pre caption="Setting the root password"> 430<pre caption="Setting the root password">
421# <i>passwd</i> 431# <i>passwd</i>
422</pre> 432</pre>
423 433
424<p>
425If you want root to be able to log on through the serial console, add
426<c>tts/0</c> to <path>/etc/securetty</path>:
427</p>
428
429<pre caption="Adding tts/0 to /etc/securetty">
430# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
431</pre>
432
433</body> 434</body>
434</subsection> 435</subsection>
435<subsection> 436<subsection>
436<title>System Information</title> 437<title>System Information</title>
437<body> 438<body>
444<pre caption="Opening /etc/rc.conf"> 445<pre caption="Opening /etc/rc.conf">
445# <i>nano -w /etc/rc.conf</i> 446# <i>nano -w /etc/rc.conf</i>
446</pre> 447</pre>
447 448
448<p> 449<p>
450When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
451</p>
452
453<p>
449As 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
450configuration variables. Take special care with the <c>KEYMAP</c> setting: if 455configuration variables. You can configure your system to use unicode and
451you 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).
452your keyboard. 457</p>
458
453</p> 459<p>
460Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
461Edit it to configure your keyboard.
462</p>
454 463
455<note> 464<pre caption="Opening /etc/conf.d/keymaps">
456Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 465# <i>nano -w /etc/conf.d/keymaps</i>
457select 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.
458</note> 475</note>
459 476
460<p> 477<p>
461<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
462ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 479exit.
463to set a mac/ppc keymap in <path>rc.conf</path>.
464</p>
465
466<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>
467When 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')">
468continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 511Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
469Tools</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>.
470</p> 539</p>
471 540
472</body> 541</body>
473</subsection> 542</subsection>
474</section> 543</section>

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

  ViewVC Help
Powered by ViewVC 1.1.20