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

Legend:
Removed from v.1.19  
changed lines
  Added in v.1.88

  ViewVC Help
Powered by ViewVC 1.1.20