/[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.55 Revision 1.98
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.55 2005/01/04 18:11:20 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.98 2008/04/17 21:11:30 nightmorph 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>9.1</version>
12<date>2004-12-26</date> 18<date>2008-04-17</date>
13 19
14<section> 20<section>
15<title>Filesystem Information</title> 21<title>Filesystem Information</title>
16<subsection> 22<subsection>
17<title>What is fstab?</title> 23<title>What is fstab?</title>
18<body> 24<body>
19 25
20<p> 26<p>
21Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 28<path>/etc/fstab</path>. This file contains the mount points of those partitions
23(where they are seen in the file system structure), how they should be mounted 29(where they are seen in the file system structure), how they should be mounted
24and with what special options (automatically or not, whether users can mount 30and with what special options (automatically or not, whether users can mount
25them or not, etc.) 31them or not, etc.)
26</p> 32</p>
27 33
41<li> 47<li>
42 The first field shows the <b>partition</b> described (the path to the device 48 The first field shows the <b>partition</b> described (the path to the device
43 file) 49 file)
44</li> 50</li>
45<li> 51<li>
46 The second field shows the <b>mountpoint</b> at which the partition should be 52 The second field shows the <b>mount point</b> at which the partition should be
47 mounted 53 mounted
48</li> 54</li>
49<li> 55<li>
50 The third field shows the <b>filesystem</b> used by the partition 56 The third field shows the <b>filesystem</b> used by the partition
51</li> 57</li>
52<li> 58<li>
53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 59 The fourth field shows the <b>mount options</b> used by <c>mount</c> when it
54 wants to mount the partition. As every filesystem has its own mountoptions, 60 wants to mount the partition. As every filesystem has its own mount options,
55 you are encouraged to read the mount man page (<c>man mount</c>) for a full 61 you are encouraged to read the mount man page (<c>man mount</c>) for a full
56 listing. Multiple mountoptions are comma-separated. 62 listing. Multiple mount options are comma-separated.
57</li> 63</li>
58<li> 64<li>
59 The fifth field is used by <c>dump</c> to determine if the partition needs to 65 The fifth field is used by <c>dump</c> to determine if the partition needs to
60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 66 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
61</li> 67</li>
65 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 71 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
66 (or <c>0</c> if a filesystem check isn't necessary). 72 (or <c>0</c> if a filesystem check isn't necessary).
67</li> 73</li>
68</ul> 74</ul>
69 75
70<p> 76<impo>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab 77The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72file</e>, so start <c>nano</c> (or your favorite editor) to create your 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
73<path>/etc/fstab</path>: 79</impo>
74</p>
75 80
76<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
77# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
78</pre> 83</pre>
79 84
85</body>
86<body test="func:keyval('/boot')">
87
80<p> 88<p>
81Let us take a look at how we write down the options for the <path>/boot</path> 89Let us take a look at how we write down the options for the <path>/boot</path>
82partition. This is just an example, so if your architecture doesn't require a 90partition. This is just an example, if you didn't or couldn't create a
83<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. 91<path>/boot</path>, don't copy it.
84</p>
85
86<p> 92</p>
93
94<p test="contains(func:keyval('/boot'), '/dev/hd')">
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 (or
97<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
89It 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:
90</p> 105</p>
91 106
92<pre caption="An example /boot line for /etc/fstab"> 107<pre caption="An example /boot line for /etc/fstab">
93/dev/hda1 /boot ext2 defaults 1 2 108<keyval id="/boot"/> /boot ext2 defaults 1 2
94</pre> 109</pre>
95 110
96<p> 111<p>
97Some 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
98automatically to improve their system's security. Those people should 113automatically to improve their system's security. Those people should
99substitute <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
100manually mount this partition every time you want to use it. 115manually mount this partition every time you want to use it.
101</p> 116</p>
102 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
123your CD-ROM drive(s), and of course, if you have other partitions or drives,
124for those too.
103<p> 125</p>
104Now, to improve performance, most users would want to add the <c>noatime</c>
105option as mountoption, which results in a faster system since access times
106aren't registered (you don't need those generally anyway):
107</p>
108 126
109<pre caption="An improved /boot line for /etc/fstab"> 127<p test="func:keyval('arch')='SPARC'">
110/dev/hda1 /boot ext2 defaults,noatime 1 2 128Add the rules that match your partitioning schema and append rules for
111</pre> 129<path>/proc/openprom</path>, for your CD-ROM drive(s), and of course, if
112 130you have other partitions or drives, for those too.
113<p> 131</p>
114If we continue with this, we would end up with the following three lines (for 132
115<path>/boot</path>, <path>/</path> and the swap partition):
116</p> 133<p>
117 134Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
118<pre caption="Three /etc/fstab lines">
119/dev/hda1 /boot ext2 defaults,noatime 1 2
120/dev/hda2 none swap sw 0 0
121/dev/hda3 / ext3 noatime 0 1
122</pre>
123
124<p> 135</p>
125To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
126(required) and for your CD-ROM drive (and of course, if you have other
127partitions or drives, for those too):
128</p>
129 136
130<pre caption="A full /etc/fstab example"> 137<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
131/dev/hda1 /boot ext2 defaults,noatime 1 2 138<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132/dev/hda2 none swap sw 0 0 139/dev/hda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 140/dev/hda3 / ext3 noatime 0 1
134 141
135none /proc proc defaults 0 0 142/dev/cdrom /mnt/cdrom auto noauto,user 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 143</pre>
137 144
145<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
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
155/dev/sda2 none swap sw 0 0
156/dev/sda3 / ext3 noatime 0 1
157
158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
159</pre>
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
138/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
139</pre> 190</pre>
140 191
141<p> 192<p>
142<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
143removable 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
144<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.
145</p> 196</p>
146 197
147<p> 198<p>
148Now 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>
149<b>SPARC</b>-user, you should add the following line to your 200mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 201aren'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> 202</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 203
166<p> 204<p>
167Double-check your <path>/etc/fstab</path>, save and quit to continue. 205Double-check your <path>/etc/fstab</path>, save and quit to continue.
168</p> 206</p>
169 207
171</subsection> 209</subsection>
172</section> 210</section>
173<section> 211<section>
174<title>Networking Information</title> 212<title>Networking Information</title>
175<subsection> 213<subsection>
176<title>Hostname, Domainname etc.</title> 214<title>Host name, Domainname, etc</title>
177<body> 215<body>
178 216
179<p> 217<p>
180One 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
181quite 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
182appropriate 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
183choose 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
184<c>tux</c> and domain <c>homenetwork</c>. 222<c>tux</c> and domain <c>homenetwork</c>.
185</p> 223</p>
186 224
187<p>
188We use these values in the next examples. First we set the hostname:
189</p>
190
191<pre caption="Setting the hostname"> 225<pre caption="Setting the host name">
192# <i>echo tux &gt; /etc/hostname</i> 226# <i>nano -w /etc/conf.d/hostname</i>
193</pre>
194 227
228<comment>(Set the HOSTNAME variable to your host name)</comment>
229HOSTNAME="<i>tux</i>"
230</pre>
231
195<p> 232<p>
196Second 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.
197</p> 237</p>
198 238
199<pre caption="Setting the domainname"> 239<pre caption="Setting the domainname">
200# <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>"
201</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>
202 251
203<p> 252<p>
204If 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
205one), you need to define that one too: 254one), you need to define that one too:
206</p> 255</p>
207 256
208<pre caption="Setting the NIS domainname"> 257<pre caption="Setting the NIS domainname">
209# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 258# <i>nano -w /etc/conf.d/net</i>
210</pre>
211 259
212<p> 260<comment>(Set the nis_domain variable to your NIS domain name)</comment>
213Now add the <c>domainname</c> script to the default runlevel: 261nis_domain_lo="<i>my-nisdomain</i>"
214</p> 262</pre>
215 263
216<pre caption="Adding domainname to the default runlevel"> 264<note>
217# <i>rc-update add domainname default</i> 265For more information on configuring DNS and NIS, please read the examples
218</pre> 266provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
267<c>openresolv</c> to help manage your DNS/NIS setup.
268</note>
219 269
220</body> 270</body>
221</subsection> 271</subsection>
222<subsection> 272<subsection>
223<title>Configuring your Network</title> 273<title>Configuring your Network</title>
224<body> 274<body>
225 275
226<p> 276<p>
227Before 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
228that 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
229just 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
230your Gentoo system permanently. 280your Gentoo system permanently.
231</p> 281</p>
232 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
233<p> 289<p>
234All 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
235a straightforward yet not intuitive syntax if you don't know how to set up 291a straightforward yet not intuitive syntax if you don't know how to set up
236networking manually. But don't fear, we'll explain everything :) 292networking manually. But don't fear, we'll explain everything. A fully
237</p> 293commented example that covers many different configurations is available in
238 294<path>/etc/conf.d/net.example</path>.
239<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
240First 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
241is used in this example): 308this example):
242</p> 309</p>
243 310
244<pre caption="Opening /etc/conf.d/net for editing"> 311<pre caption="Opening /etc/conf.d/net for editing">
245# <i>nano -w /etc/conf.d/net</i> 312# <i>nano -w /etc/conf.d/net</i>
246</pre> 313</pre>
247 314
248<p> 315<p>
249The first variable you'll find is <c>iface_eth0</c>. It uses the following 316You 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> 317</p>
258If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 318
259to <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">
260If you need to set up your network manually and you're 320# This blank configuration will automatically use DHCP for any net.*
261not familiar with all the above terms, please read the section on <uri 321# scripts in /etc/init.d. To create a more complete configuration,
262link="?part=1&amp;chap=3#network_term">Understanding Network 322# please review /etc/conf.d/net.example and save your configuration
263Terminology</uri> if you haven't done so already. 323# in /etc/conf.d/net (this file :]!).
324</pre>
325
264</p> 326<p>
265 327To enter your own IP address, netmask and gateway, you need
328to set both <c>config_eth0</c> and <c>routes_eth0</c>:
266<p> 329</p>
267So let us give three examples; the first one uses DHCP, the second one a static 330
268IP (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">
269gateway 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" )
270rp-pppoe usage: 333routes_eth0=( "default via 192.168.0.1" )
334</pre>
335
271</p> 336<p>
272 337To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
273<pre caption="Examples for /etc/conf.d/net"> 338<c>dhcp_eth0</c>:
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> 339</p>
294If you have several network interfaces, create extra <c>iface_eth</c> variables, 340
295like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 341<pre caption="Automatically obtaining an IP address for eth0">
296shouldn'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.
297</p> 354</p>
298 355
299<p> 356<p>
300Now save the configuration and exit to continue. 357Now save the configuration and exit to continue.
301</p> 358</p>
306<title>Automatically Start Networking at Boot</title> 363<title>Automatically Start Networking at Boot</title>
307<body> 364<body>
308 365
309<p> 366<p>
310To have your network interfaces activated at boot, you need to add them to the 367To 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 368default runlevel.
312the PCMCIA interfaces are started by the PCMCIA init script.
313</p> 369</p>
314 370
315<pre caption="Adding net.eth0 to the default runlevel"> 371<pre caption="Adding net.eth0 to the default runlevel">
316# <i>rc-update add net.eth0 default</i> 372# <i>rc-update add net.eth0 default</i>
317</pre> 373</pre>
322use <c>ln</c> to do this: 378use <c>ln</c> to do this:
323</p> 379</p>
324 380
325<pre caption="Creating extra initscripts"> 381<pre caption="Creating extra initscripts">
326# <i>cd /etc/init.d</i> 382# <i>cd /etc/init.d</i>
327# <i>ln -s net.eth0 net.eth1</i> 383# <i>ln -s net.lo net.eth1</i>
328# <i>rc-update add net.eth1 default</i> 384# <i>rc-update add net.eth1 default</i>
329</pre> 385</pre>
330 386
331</body> 387</body>
332</subsection> 388</subsection>
334<title>Writing Down Network Information</title> 390<title>Writing Down Network Information</title>
335<body> 391<body>
336 392
337<p> 393<p>
338You 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
339<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
340for 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.
341internal 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
342<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.
343open <path>/etc/hosts</path> and fill in the values:
344</p> 399</p>
345 400
346<pre caption="Opening /etc/hosts"> 401<pre caption="Opening /etc/hosts">
347# <i>nano -w /etc/hosts</i> 402# <i>nano -w /etc/hosts</i>
348</pre> 403</pre>
349 404
350<pre caption="Filling in the networking information"> 405<pre caption="Filling in the networking information">
351127.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>
352192.168.0.5 jenny.homenetwork jenny 411192.168.0.5 jenny.homenetwork jenny
353192.168.0.6 benny.homenetwork benny 412192.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> 413</pre>
366 414
367<p> 415<p>
368Save and exit the editor to continue. 416Save and exit the editor to continue.
369</p> 417</p>
370 418
371<p> 419<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 420If you don't have PCMCIA, you can now continue with <uri
373link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 421link="#sysinfo">System Information</uri>. PCMCIA-users should read the
374following topic on PCMCIA. 422following topic on PCMCIA.
375</p> 423</p>
376 424
377</body> 425</body>
378</subsection> 426</subsection>
379<subsection> 427<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> 428<title>Optional: Get PCMCIA Working</title>
381<body> 429<body>
382 430
383<note>
384pcmcia-cs is only available for x86, amd64 and ppc platforms.
385</note>
386
387<p> 431<p>
388PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 432PCMCIA 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> 433</p>
393 434
394<pre caption="Installing pcmcia-cs"> 435<pre caption="Installing pcmciautils">
395# <i>USE="-X" emerge pcmcia-cs</i> 436# <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> 437</pre>
406 438
407</body> 439</body>
408</subsection> 440</subsection>
409</section> 441</section>
410<section> 442
443<section id="sysinfo">
411<title>System Information</title> 444<title>System Information</title>
412<subsection> 445<subsection>
413<title>Root Password</title> 446<title>Root Password</title>
414<body> 447<body>
415 448
419 452
420<pre caption="Setting the root password"> 453<pre caption="Setting the root password">
421# <i>passwd</i> 454# <i>passwd</i>
422</pre> 455</pre>
423 456
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> 457</body>
434</subsection> 458</subsection>
435<subsection> 459<subsection>
436<title>System Information</title> 460<title>System Information</title>
437<body> 461<body>
444<pre caption="Opening /etc/rc.conf"> 468<pre caption="Opening /etc/rc.conf">
445# <i>nano -w /etc/rc.conf</i> 469# <i>nano -w /etc/rc.conf</i>
446</pre> 470</pre>
447 471
448<p> 472<p>
473When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
474</p>
475
476<p>
449As 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
450configuration variables. Take special care with the <c>KEYMAP</c> setting: if 478configuration 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 479define your default editor and your display manager (like gdm or kdm).
452your keyboard. 480</p>
481
453</p> 482<p>
483Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
484Edit it to configure your keyboard.
485</p>
454 486
455<note> 487<pre caption="Opening /etc/conf.d/keymaps">
456Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 488# <i>nano -w /etc/conf.d/keymaps</i>
457select 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>.
458</note> 500</note>
459 501
460<p> 502<p>
461<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
462ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 504exit.
463to set a mac/ppc keymap in <path>rc.conf</path>.
464</p>
465
466<p> 505</p>
506
507<p>
508Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
509according to your needs.
510</p>
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>
467When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 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')">
468continue with <uri link="?part=1&amp;chap=9">Installing Necessary System 535Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
469Tools</uri>. 536Tools</uri>.
537</p>
538
539</body>
540</subsection>
541<subsection test="func:keyval('arch')='PPC64'">
542<title>Configuring the Console</title>
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>.
470</p> 563</p>
471 564
472</body> 565</body>
473</subsection> 566</subsection>
474</section> 567</section>

Legend:
Removed from v.1.55  
changed lines
  Added in v.1.98

  ViewVC Help
Powered by ViewVC 1.1.20