/[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.97
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.97 2008/04/01 08:53:46 nightmorph 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>9.0</version>
16# <i>ls /usr/share/zoneinfo</i> 18<date>2008-04-01</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
123your CD-ROM drive(s), and of course, if you have other partitions or drives,
124for 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>, for your CD-ROM drive(s), and of course, if
130you 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> 142/dev/cdrom /mnt/cdrom auto noauto,user 0 0
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> 143</pre>
131 144
132<pre caption="A full /etc/fstab example"> 145<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
133/dev/hda1 /boot ext2 noauto,noatime 1 2 146<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
147/dev/sda3 none swap sw 0 0
148/dev/sda4 / ext3 noatime 0 1
149
150/dev/cdrom /mnt/cdrom auto noauto,user 0 0
151</pre>
152
153<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'">
154<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
134/dev/hda2 none swap sw 0 0 155/dev/sda2 none swap sw 0 0
135/dev/hda3 / ext3 noatime 0 1 156/dev/sda3 / ext3 noatime 0 1
136 157
137none /proc proc defaults 0 0 158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
138none /dev/shm tmpfs defaults 0 0 159</pre>
139 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
140/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
141</pre> 190</pre>
142 191
143<p> 192<p>
144<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
145removable 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
146<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.
147</p> 196</p>
148 197
149<p> 198<p>
150Now 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>
151SPARC-user, you should add the following line to your <path>/etc/fstab</path> 200mount option, which results in a faster system since access times
152too: 201aren'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> 202</p>
160If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>: 203
161</p> 204<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. 205Double-check your <path>/etc/fstab</path>, save and quit to continue.
169</p> 206</p>
170 207
171</body> 208</body>
172</subsection> 209</subsection>
173</section> 210</section>
174<section> 211<section>
175<title>Networking Information</title> 212<title>Networking Information</title>
176<subsection> 213<subsection>
177<title>Hostname, Domainname etc.</title> 214<title>Host name, Domainname, etc</title>
178<body> 215<body>
179 216
180<p> 217<p>
181One of the choices the user has to make is name his PC. This seems to be quite 218One 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 219quite 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 220appropriate 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 221choose can be changed afterwards. For all we care, you can just call your system
185<c>tux</c> and domain <c>homenetwork</c>. 222<c>tux</c> and domain <c>homenetwork</c>.
186</p> 223</p>
187 224
188<p>
189We use these values in the next examples. First we set the hostname:
190</p>
191
192<pre caption="Setting the hostname"> 225<pre caption="Setting the host name">
193# <i>echo tux &gt; /etc/hostname</i> 226# <i>nano -w /etc/conf.d/hostname</i>
194</pre>
195 227
228<comment>(Set the HOSTNAME variable to your host name)</comment>
229HOSTNAME="<i>tux</i>"
230</pre>
231
196<p> 232<p>
197Second 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.
198</p> 237</p>
199 238
200<pre caption="Setting the domainname"> 239<pre caption="Setting the domainname">
201# <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>"
202</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>
203 251
204<p> 252<p>
205If 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
206one), you need to define that one too: 254one), you need to define that one too:
207</p> 255</p>
208 256
209<pre caption="Setting the NIS domainname"> 257<pre caption="Setting the NIS domainname">
210# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 258# <i>nano -w /etc/conf.d/net</i>
259
260<comment>(Set the nis_domain variable to your NIS domain name)</comment>
261nis_domain_lo="<i>my-nisdomain</i>"
211</pre> 262</pre>
263
264<note>
265For more information on configuring DNS and NIS, please read the examples
266provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
267<c>resolvconf-gentoo</c> to help manage your DNS/NIS setup.
268</note>
212 269
213</body> 270</body>
214</subsection> 271</subsection>
215<subsection> 272<subsection>
216<title>Configuring your Network</title> 273<title>Configuring your Network</title>
217<body> 274<body>
218 275
219<p> 276<p>
220Before 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
221that 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
222just 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
223your Gentoo system permanently. 280your Gentoo system permanently.
224</p> 281</p>
225 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
226<p> 289<p>
227All 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
228a straightforward yet not intuitive syntax if you don't know how to setup 291a straightforward yet not intuitive syntax if you don't know how to set up
229networking manually. But don't fear, we'll explain everything :) 292networking manually. But don't fear, we'll explain everything. A fully
230</p> 293commented example that covers many different configurations is available in
231 294<path>/etc/conf.d/net.example</path>.
232<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
233First 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
234is used in this example): 308this example):
235</p> 309</p>
236 310
237<pre caption="Opening /etc/conf.d/net for editing"> 311<pre caption="Opening /etc/conf.d/net for editing">
238# <i>nano -w /etc/conf.d/net</i> 312# <i>nano -w /etc/conf.d/net</i>
239</pre> 313</pre>
240 314
241<p> 315<p>
242The first variable you'll find is <c>iface_eth0</c>. It uses the following 316You 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> 317</p>
251If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 318
252to <c>dhcp</c>. However, if you need to setup your network manually and you're 319<pre caption="Default /etc/conf.d/net">
253not familiar with all the above terms, please read the section on <uri 320# This blank configuration will automatically use DHCP for any net.*
254link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 321# scripts in /etc/init.d. To create a more complete configuration,
255Terminology</uri> if you haven't done so already. 322# please review /etc/conf.d/net.example and save your configuration
323# in /etc/conf.d/net (this file :]!).
324</pre>
325
256</p> 326<p>
257 327To enter your own IP address, netmask and gateway, you need
328to set both <c>config_eth0</c> and <c>routes_eth0</c>:
258<p> 329</p>
259So lets give two examples; the first one uses DHCP, the second one a static IP 330
260(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 331<pre caption="Manually setting IP information for eth0">
261192.168.0.1: 332config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
333routes_eth0=( "default via 192.168.0.1" )
334</pre>
335
262</p> 336<p>
263 337To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
264<pre caption="Examples for /etc/conf.d/net"> 338<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> 339</p>
274If you have several network interfaces, create extra <c>iface_eth</c> variables, 340
275like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 341<pre caption="Automatically obtaining an IP address for eth0">
276shouldn'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.
277</p> 354</p>
278 355
279<p> 356<p>
280Now save the configuration and exit to continue. 357Now save the configuration and exit to continue.
281</p> 358</p>
285<subsection> 362<subsection>
286<title>Automatically Start Networking at Boot</title> 363<title>Automatically Start Networking at Boot</title>
287<body> 364<body>
288 365
289<p> 366<p>
290To have your network interfaces activated at boot, you need to add those to the 367To have your network interfaces activated at boot, you need to add them to the
291default runlevel. If you have PCMCIA interfaces you should skip this action as 368default runlevel.
292the PCMCIA interfaces are started by the PCMCIA init script.
293</p> 369</p>
294 370
295<pre caption="Adding net.eth0 to the default runlevel"> 371<pre caption="Adding net.eth0 to the default runlevel">
296# <i>rc-update add net.eth0 default</i> 372# <i>rc-update add net.eth0 default</i>
297</pre> 373</pre>
302use <c>ln</c> to do this: 378use <c>ln</c> to do this:
303</p> 379</p>
304 380
305<pre caption="Creating extra initscripts"> 381<pre caption="Creating extra initscripts">
306# <i>cd /etc/init.d</i> 382# <i>cd /etc/init.d</i>
307# <i>ln -s net.eth0 net.eth1</i> 383# <i>ln -s net.lo net.eth1</i>
308# <i>rc-update add net.eth1 default</i> 384# <i>rc-update add net.eth1 default</i>
309</pre> 385</pre>
310 386
311</body> 387</body>
312</subsection> 388</subsection>
314<title>Writing Down Network Information</title> 390<title>Writing Down Network Information</title>
315<body> 391<body>
316 392
317<p> 393<p>
318You 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
319<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
320for 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.
321internal 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
322<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would 398set up your own internal DNS system.
323open <path>/etc/hosts</path> and fill in the values:
324</p> 399</p>
325 400
326<pre caption="Opening /etc/hosts"> 401<pre caption="Opening /etc/hosts">
327# <i>nano -w /etc/hosts</i> 402# <i>nano -w /etc/hosts</i>
328</pre> 403</pre>
329 404
330<pre caption="Filling in the networking information"> 405<pre caption="Filling in the networking information">
406<comment>(This defines the current system)</comment>
331127.0.0.1 tux.homenetwork localhost 407127.0.0.1 tux.homenetwork tux localhost
332192.168.0.5 jenny
333192.168.0.56 benny
334</pre>
335 408
336<p> 409<comment>(Define extra systems on your network,
337If your system is the only system (or the nameservers handle all name 410they need to have a static IP to be defined this way.)</comment>
338resolution) a single line is sufficient: 411192.168.0.5 jenny.homenetwork jenny
339</p> 412192.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> 413</pre>
344 414
345<p> 415<p>
346Save and exit the editor to continue. 416Save and exit the editor to continue.
347</p> 417</p>
348 418
349<p> 419<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 420If you don't have PCMCIA, you can now continue with <uri
351link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 421link="#sysinfo">System Information</uri>. PCMCIA-users should read the
352following topic on PCMCIA. 422following topic on PCMCIA.
353</p> 423</p>
354 424
355</body> 425</body>
356</subsection> 426</subsection>
357<subsection> 427<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> 428<title>Optional: Get PCMCIA Working</title>
359<body> 429<body>
360 430
361<p> 431<p>
362PCMCIA-users should first install the <c>pcmcia-cs</c> package: 432PCMCIA users should first install the <c>pcmciautils</c> package.
363</p> 433</p>
364 434
365<pre caption="Installing pcmcia-cs"> 435<pre caption="Installing pcmciautils">
366# <i>emerge -k pcmcia-cs</i> 436# <i>emerge pcmciautils</i>
367</pre>
368
369<p>
370When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>
371runlevel:
372</p>
373
374<pre caption="Adding pcmcia to the default runlevel">
375# <i>rc-update add pcmcia boot</i>
376</pre> 437</pre>
377 438
378</body> 439</body>
379</subsection> 440</subsection>
380</section> 441</section>
442
443<section id="sysinfo">
444<title>System Information</title>
381<section> 445<subsection>
446<title>Root Password</title>
447<body>
448
449<p>
450First we set the root password by typing:
451</p>
452
453<pre caption="Setting the root password">
454# <i>passwd</i>
455</pre>
456
457</body>
458</subsection>
459<subsection>
382<title>System Information</title> 460<title>System Information</title>
383<body> 461<body>
384 462
385<p> 463<p>
386Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 464Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
390<pre caption="Opening /etc/rc.conf"> 468<pre caption="Opening /etc/rc.conf">
391# <i>nano -w /etc/rc.conf</i> 469# <i>nano -w /etc/rc.conf</i>
392</pre> 470</pre>
393 471
394<p> 472<p>
473When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
474</p>
475
476<p>
395As 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
396configuration variables. When you're finished configuring 478configuration variables. You can configure your system to use unicode and
397<path>/etc/rc.conf</path>, save and exit to continue. 479define your default editor and your display manager (like gdm or kdm).
480</p>
481
398</p> 482<p>
483Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
484Edit it to configure your keyboard.
485</p>
399 486
487<pre caption="Opening /etc/conf.d/keymaps">
488# <i>nano -w /etc/conf.d/keymaps</i>
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>.
500</note>
501
502<p>
503When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
504exit.
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>
530When you're finished configuring <path>/etc/conf.d/clock</path>, save and
531exit.
532</p>
533
534<p test="not(func:keyval('arch')='PPC64')">
535Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
536Tools</uri>.
537</p>
538
539</body>
540</subsection>
541<subsection test="func:keyval('arch')='PPC64'">
542<title>Configuring the Console</title>
400</body> 543<body>
544
545<p>
546If you are using a virtual console, you must uncomment the appropriate line in
547<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
548</p>
549
550<pre caption="Enabling hvc or hvsi support in /etc/inittab">
551hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
552hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
553</pre>
554
555<p>
556You should also take this time to verify that the appropriate console is
557listed in <path>/etc/securetty</path>.
558</p>
559
560<p>
561You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
562System Tools</uri>.
563</p>
564
565</body>
566</subsection>
401</section> 567</section>
402</sections> 568</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20