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

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.86

  ViewVC Help
Powered by ViewVC 1.1.20