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

Legend:
Removed from v.1.36  
changed lines
  Added in v.1.97

  ViewVC Help
Powered by ViewVC 1.1.20