/[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.45 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.45 2004/08/30 17:44:00 neysx 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
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>7.6</version>
18<date>2006-11-27</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
20and with what special options (automatically or not, whether users can mount 30and with what special options (automatically or not, whether users can mount
21them or not, etc.) 31them or not, etc.)
22</p> 32</p>
23 33
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>
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> if 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>
67The 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
68file</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>.
69<path>/etc/fstab</path>: 79</impo>
70</p>
71 80
72<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
73# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
74</pre> 83</pre>
75 84
85</body>
86<body test="func:keyval('/boot')">
87
76<p> 88<p>
77Let 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>
78partition. 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
79<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. 91<path>/boot</path>, don't copy it.
80</p>
81
82<p> 92</p>
93
94<p test="contains(func:keyval('/boot'), '/dev/hd')">
83In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
84<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
85It 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:
86</p> 105</p>
87 106
88<pre caption="An example /boot line for /etc/fstab"> 107<pre caption="An example /boot line for /etc/fstab">
89/dev/hda1 /boot ext2 defaults 1 2 108<keyval id="/boot"/> /boot ext2 defaults 1 2
90</pre> 109</pre>
91 110
92<p> 111<p>
93Some 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
94automatically to improve their system's security. Those people should 113automatically to improve their system's security. Those people should
95substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 114substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
96manually mount this partition every time you want to use it. 115manually mount this partition every time you want to use it.
97</p> 116</p>
98 117
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.
99<p> 125</p>
100Now, to improve performance, most users would want to add the <c>noatime</c>
101option as mountoption, which results in a faster system since access times
102aren't registered (you don't need those generally anyway):
103</p>
104 126
105<pre caption="An improved /boot line for /etc/fstab"> 127<p test="func:keyval('arch')='SPARC'">
106/dev/hda1 /boot ext2 defaults,noatime 1 2 128Add the rules that match your partitioning schema and append rules for
107</pre> 129<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
108 130drive(s), and of course, if you have other partitions or drives, for those too.
109<p> 131</p>
110If we continue with this, we would end up with the following three lines (for 132
111<path>/boot</path>, <path>/</path> and the swap partition):
112</p> 133<p>
134Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
135</p>
113 136
114<pre caption="Three /etc/fstab lines"> 137<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
115/dev/hda1 /boot ext2 defaults,noatime 1 2 138<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
116/dev/hda2 none swap sw 0 0 139/dev/hda2 none swap sw 0 0
117/dev/hda3 / ext3 noatime 0 1 140/dev/hda3 / ext3 noatime 0 1
118</pre>
119 141
120<p> 142proc /proc proc defaults 0 0
121To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> 143shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
122(required) and for your CD-ROM drive (and of course, if you have other 144
123partitions or drives, for those too): 145/dev/cdrom /mnt/cdrom auto noauto,user 0 0
124</p> 146</pre>
125 147
126<pre caption="A full /etc/fstab example"> 148<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
127/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
128/dev/hda2 none swap sw 0 0 161/dev/sda2 none swap sw 0 0
129/dev/hda3 / ext3 noatime 0 1 162/dev/sda3 / ext3 noatime 0 1
130 163
131none /proc proc defaults 0 0 164proc /proc proc defaults 0 0
132none /dev/shm tmpfs defaults 0 0 165shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
133 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
134/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
135</pre> 207</pre>
136 208
137<p> 209<p>
138<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
139removable 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
140<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.
141</p> 213</p>
142 214
143<p> 215<p>
144Now 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>
145<b>SPARC</b>-user, you should add the following line to your 217mount option, which results in a faster system since access times
146<path>/etc/fstab</path> 218aren't registered (you don't need those generally anyway).
147too:
148</p>
149
150<pre caption="Adding openprom filesystem to /etc/fstab">
151none /proc/openprom openpromfs defaults 0 0
152</pre>
153
154<p> 219</p>
155If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
156</p>
157
158<pre caption="Adding usbfs filesystem to /etc/fstab">
159none /proc/bus/usb usbfs defaults 0 0
160</pre>
161 220
162<p> 221<p>
163Double-check your <path>/etc/fstab</path>, save and quit to continue. 222Double-check your <path>/etc/fstab</path>, save and quit to continue.
164</p> 223</p>
165 224
167</subsection> 226</subsection>
168</section> 227</section>
169<section> 228<section>
170<title>Networking Information</title> 229<title>Networking Information</title>
171<subsection> 230<subsection>
172<title>Hostname, Domainname etc.</title> 231<title>Host name, Domainname, etc</title>
173<body> 232<body>
174 233
175<p> 234<p>
176One of the choices the user has to make is name his/her PC. This seems to be 235One of the choices the user has to make is name his/her PC. This seems to be
177quite easy, but <e>lots</e> of users are having difficulties finding the 236quite easy, but <e>lots</e> of users are having difficulties finding the
178appropriate name for their Linux-pc. To speed things up, know that any name you 237appropriate name for their Linux-pc. To speed things up, know that any name you
179choose can be 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
180<c>tux</c> and domain <c>homenetwork</c>. 239<c>tux</c> and domain <c>homenetwork</c>.
181</p> 240</p>
182 241
183<p>
184We use these values in the next examples. First we set the hostname:
185</p>
186
187<pre caption="Setting the hostname"> 242<pre caption="Setting the host name">
188# <i>echo tux &gt; /etc/hostname</i> 243# <i>nano -w /etc/conf.d/hostname</i>
189</pre>
190 244
245<comment>(Set the HOSTNAME variable to your host name)</comment>
246HOSTNAME="<i>tux</i>"
247</pre>
248
191<p> 249<p>
192Second we set the domainname: 250Second we set the domainname in <path>/etc/conf.d/net</path>:
193</p> 251</p>
194 252
195<pre caption="Setting the domainname"> 253<pre caption="Setting the domainname">
196# <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>"
197</pre> 258</pre>
198 259
199<p> 260<p>
200If 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
201one), you need to define that one too: 262one), you need to define that one too:
202</p> 263</p>
203 264
204<pre caption="Setting the NIS domainname"> 265<pre caption="Setting the NIS domainname">
205# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 266# <i>nano -w /etc/conf.d/net</i>
206</pre>
207 267
208<p> 268<comment>(Set the nis_domain variable to your NIS domain name)</comment>
209Now add the <c>domainname</c> script to the default runlevel: 269nis_domain_lo="<i>my-nisdomain</i>"
210</p> 270</pre>
211 271
212<pre caption="Adding domainname to the default runlevel"> 272<note>
213# <i>rc-update add domainname default</i> 273For more information on configuring DNS and NIS, please read the examples
214</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>
215 277
216</body> 278</body>
217</subsection> 279</subsection>
218<subsection> 280<subsection>
219<title>Configuring your Network</title> 281<title>Configuring your Network</title>
220<body> 282<body>
221 283
222<p> 284<p>
223Before 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
224that 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
225just 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
226your Gentoo system permanently. 288your Gentoo system permanently.
227</p> 289</p>
228 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
229<p> 297<p>
230All 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
231a 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
232networking manually. But don't fear, we'll explain everything :) 300networking manually. But don't fear, we'll explain everything. A fully
233</p> 301commented example that covers many different configurations is available in
234 302<path>/etc/conf.d/net.example</path>.
235<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
236First 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
237is used in this example): 316this example):
238</p> 317</p>
239 318
240<pre caption="Opening /etc/conf.d/net for editing"> 319<pre caption="Opening /etc/conf.d/net for editing">
241# <i>nano -w /etc/conf.d/net</i> 320# <i>nano -w /etc/conf.d/net</i>
242</pre> 321</pre>
243 322
244<p> 323<p>
245The first variable you'll find is <c>iface_eth0</c>. It uses the following 324You will see the following file:
246syntax:
247</p>
248
249<pre caption="iface_eth0 syntaxis">
250iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
251</pre>
252
253<p> 325</p>
254If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 326
255to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 327<pre caption="Default /etc/conf.d/net">
256If you need to setup your network manually and you're 328# This blank configuration will automatically use DHCP for any net.*
257not familiar with all the above terms, please read the section on <uri 329# scripts in /etc/init.d. To create a more complete configuration,
258link="?part=1&amp;chap=3#network_term">Understanding Network 330# please review /etc/conf.d/net.example and save your configuration
259Terminology</uri> if you haven't done so already. 331# in /etc/conf.d/net (this file :]!).
332</pre>
333
260</p> 334<p>
261 335To enter your own IP address, netmask and gateway, you need
336to set both <c>config_eth0</c> and <c>routes_eth0</c>:
262<p> 337</p>
263So let us give three examples; the first one uses DHCP, the second one a static 338
264IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 339<pre caption="Manually setting IP information for eth0">
265gateway 192.168.0.1 while the third one just activates the interface for 340config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
266rp-pppoe usage: 341routes_eth0=( "default gw 192.168.0.1" )
342</pre>
343
267</p> 344<p>
268 345To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
269<pre caption="Examples for /etc/conf.d/net"> 346<c>dhcp_eth0</c>:
270<comment>(For DHCP)</comment>
271iface_eth0="dhcp"
272<comment># Some network admins require that you use the</comment>
273<comment># hostname and domainname provided by the DHCP server.</comment>
274<comment># In that case, add the following to let dhcpcd use them.</comment>
275<comment># That will override your own hostname and domainname definitions.</comment>
276dhcpcd_eth0="-HD"
277<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
278<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
279dhcpcd_eth0="-N"
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
285<comment>(For rp-pppoe)</comment>
286iface_eth0="up"
287</pre>
288
289<p> 347</p>
290If you have several network interfaces, create extra <c>iface_eth</c> variables, 348
291like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 349<pre caption="Automatically obtaining an IP address for eth0">
292shouldn'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.
293</p> 362</p>
294 363
295<p> 364<p>
296Now save the configuration and exit to continue. 365Now save the configuration and exit to continue.
297</p> 366</p>
318use <c>ln</c> to do this: 387use <c>ln</c> to do this:
319</p> 388</p>
320 389
321<pre caption="Creating extra initscripts"> 390<pre caption="Creating extra initscripts">
322# <i>cd /etc/init.d</i> 391# <i>cd /etc/init.d</i>
323# <i>ln -s net.eth0 net.eth1</i> 392# <i>ln -s net.lo net.eth1</i>
324# <i>rc-update add net.eth1 default</i> 393# <i>rc-update add net.eth1 default</i>
325</pre> 394</pre>
326 395
327</body> 396</body>
328</subsection> 397</subsection>
330<title>Writing Down Network Information</title> 399<title>Writing Down Network Information</title>
331<body> 400<body>
332 401
333<p> 402<p>
334You 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
335<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
336for 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.
337internal 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
338<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.
339open <path>/etc/hosts</path> and fill in the values:
340</p> 408</p>
341 409
342<pre caption="Opening /etc/hosts"> 410<pre caption="Opening /etc/hosts">
343# <i>nano -w /etc/hosts</i> 411# <i>nano -w /etc/hosts</i>
344</pre> 412</pre>
345 413
346<pre caption="Filling in the networking information"> 414<pre caption="Filling in the networking information">
347127.0.0.1 localhost 415<comment>(This defines the current system)</comment>
416127.0.0.1 tux.homenetwork tux localhost
417
418<comment>(Define extra systems on your network,
419they need to have a static IP to be defined this way.)</comment>
348192.168.0.5 jenny.homenetwork jenny 420192.168.0.5 jenny.homenetwork jenny
349192.168.0.6 benny.homenetwork benny 421192.168.0.6 benny.homenetwork benny
350192.168.0.7 tux.homenetwork tux
351</pre>
352
353<p>
354If your system is the only system (or the nameservers handle all name
355resolution) a single line is sufficient. For instance, if you want to call your
356system <c>tux.homenetwork</c>:
357</p>
358
359<pre caption="/etc/hosts for lonely or fully integrated PCs">
360127.0.0.1 tux.homenetwork tux localhost
361</pre> 422</pre>
362 423
363<p> 424<p>
364Save and exit the editor to continue. 425Save and exit the editor to continue.
365</p> 426</p>
366 427
367<p> 428<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
368If you don't have PCMCIA, you can now continue with <uri 429If you don't have PCMCIA, you can now continue with <uri
369link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 430link="#sysinfo">System Information</uri>. PCMCIA-users should read the
370following topic on PCMCIA. 431following topic on PCMCIA.
371</p> 432</p>
372 433
373</body> 434</body>
374</subsection> 435</subsection>
375<subsection> 436<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
376<title>Optional: Get PCMCIA Working</title> 437<title>Optional: Get PCMCIA Working</title>
377<body> 438<body>
378 439
379<note>
380pcmcia-cs is only available for x86, amd64 and ppc platforms.
381</note>
382
383<p> 440<p>
384PCMCIA-users should first install the <c>pcmcia-cs</c> package. The 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
385<c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment: 444to avoid installing xorg-x11 at this moment:
386</p> 445</p>
387 446
388<pre caption="Installing pcmcia-cs"> 447<pre caption="Installing pcmcia-cs">
389# <i>USE="-X" emerge pcmcia-cs</i> 448# <i>USE="-X" emerge pcmcia-cs</i>
390</pre> 449</pre>
399</pre> 458</pre>
400 459
401</body> 460</body>
402</subsection> 461</subsection>
403</section> 462</section>
404<section> 463
464<section id="sysinfo">
405<title>System Information</title> 465<title>System Information</title>
406<subsection> 466<subsection>
407<title>Root Password</title> 467<title>Root Password</title>
408<body> 468<body>
409 469
438<pre caption="Opening /etc/rc.conf"> 498<pre caption="Opening /etc/rc.conf">
439# <i>nano -w /etc/rc.conf</i> 499# <i>nano -w /etc/rc.conf</i>
440</pre> 500</pre>
441 501
442<p> 502<p>
503When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
504</p>
505
506<p>
443As 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
444configuration variables. Take special care with the <c>KEYMAP</c> setting: if 508configuration variables. You can configure your system to use unicode and
445you 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).
446your keyboard. 510</p>
511
447</p> 512<p>
513Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
514Edit it to configure your keyboard.
515</p>
448 516
449<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'">
450Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 527Users of USB-based SPARC systems and SPARC clones might need to select an i386
451select an i386 keymap (such as "us") instead of "sunkeymap". 528keymap (such as "us") instead of "sunkeymap".
452</note> 529</note>
453 530
454<p> 531<note test="substring(func:keyval('arch'),1,3)='PPC'">
455<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 532PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
456ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 533keymaps on boot have to enable ADB keycode sendings in their kernel and have to
457to set a mac/ppc keymap in <path>rc.conf</path>. 534set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
535</note>
536
458</p> 537<p>
459 538When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
539exit.
460<p> 540</p>
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>
461When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 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')">
462continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 562Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
463Tools</uri>. 563Tools</uri>.
564</p>
565
566</body>
567</subsection>
568<subsection test="func:keyval('arch')='PPC64'">
569<title>Configuring the Console</title>
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>.
464</p> 590</p>
465 591
466</body> 592</body>
467</subsection> 593</subsection>
468</section> 594</section>

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

  ViewVC Help
Powered by ViewVC 1.1.20