/[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.20 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.20 2004/01/19 18:48:52 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
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>9.1</version>
18<date>2008-04-17</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
20(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
21etc.). 31them or not, etc.)
22</p> 32</p>
23 33
24</body> 34</body>
25</subsection> 35</subsection>
26<subsection> 36<subsection>
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>
58<li> 68<li>
59 The sixth field is used by <c>fsck</c> to determine the order in which 69 The sixth field is used by <c>fsck</c> to determine the order in which
60 filesystems should be <b>check</b>ed if the system wasn't shut down properly. 70 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
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> in case 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>
67So 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
68<path>/etc/fstab</path>: 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
69</p> 79</impo>
70 80
71<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
72# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
73</pre> 83</pre>
74 84
85</body>
86<body test="func:keyval('/boot')">
87
75<p> 88<p>
76Let 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>
77partition. 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
78<path>/boot</path> partition, don't copy it verbatim. 91<path>/boot</path>, don't copy it.
79</p>
80
81<p> 92</p>
93
94<p test="contains(func:keyval('/boot'), '/dev/hd')">
82In our default x86 partitioning example <path>/boot</path> is the 95In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
83<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't 96usually the <path><keyval id="/boot"/></path> partition (or
84be 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
85would 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 noauto 1 2 108<keyval id="/boot"/> /boot ext2 defaults 1 2
90</pre> 109</pre>
91 110
92<p>
93Now, to improve performance, most users would want to add the <c>noatime</c>
94option as mountoption, which results in a faster system since access times
95aren't registered (you don't need those generally anyway):
96</p> 111<p>
97 112Some users don't want their <path>/boot</path> partition to be mounted
98<pre caption="An improved /boot line for /etc/fstab"> 113automatically to improve their system's security. Those people should
99/dev/hda1 /boot ext2 noauto,noatime 1 2 114substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
100</pre> 115manually mount this partition every time you want to use it.
101
102<p> 116</p>
103If we continue with this, we would end up with the following three lines (for 117
104<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
105</p> 133<p>
134Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
135</p>
106 136
107<pre caption="Three /etc/fstab lines"> 137<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
108/dev/hda1 /boot ext2 noauto,noatime 1 2 138<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
109/dev/hda2 none swap sw 0 0 139/dev/hda2 none swap sw 0 0
110/dev/hda3 / ext3 noatime 0 1 140/dev/hda3 / ext3 noatime 0 1
111</pre>
112 141
113<p> 142/dev/cdrom /mnt/cdrom auto noauto,user 0 0
114To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
115(required) and for your CD-ROM drive (and of course, if you have other
116partitions or drives, for those too):
117</p> 143</pre>
118 144
119<pre caption="A full /etc/fstab example"> 145<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
120/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
121/dev/hda2 none swap sw 0 0 155/dev/sda2 none swap sw 0 0
122/dev/hda3 / ext3 noatime 0 1 156/dev/sda3 / ext3 noatime 0 1
123 157
124none /proc proc defaults 0 0 158/dev/cdrom /mnt/cdrom auto noauto,user 0 0
125none /dev/shm tmpfs defaults 0 0 159</pre>
126 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
127/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
128</pre> 190</pre>
129 191
130<p> 192<p>
131<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
132removable 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
133<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.
134</p> 196</p>
135 197
136<p> 198<p>
137Now 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>
138SPARC-user, you should add the following line to your <path>/etc/fstab</path> 200mount option, which results in a faster system since access times
139too: 201aren't registered (you don't need those generally anyway).
140</p>
141
142<pre caption="Adding openprom filesystem to /etc/fstab">
143none /proc/openprom openpromfs defaults 0 0
144</pre>
145
146<p> 202</p>
147If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>: 203
148</p> 204<p>
149
150<pre caption="Adding usbfs filesystem to /etc/fstab">
151none /proc/bus/usb usbfs defaults 0 0
152</pre>
153
154<p>
155Reread your <path>/etc/fstab</path>, save and quit to continue. 205Double-check your <path>/etc/fstab</path>, save and quit to continue.
156</p> 206</p>
157 207
158</body> 208</body>
159</subsection> 209</subsection>
160</section> 210</section>
161<section> 211<section>
162<title>Networking Information</title> 212<title>Networking Information</title>
163<subsection> 213<subsection>
164<title>Hostname, Domainname etc.</title> 214<title>Host name, Domainname, etc</title>
165<body> 215<body>
166 216
167<p> 217<p>
168One 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
169easy, 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
170name 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
171be 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
172<c>tux</c> and domain <c>homenetwork</c>. 222<c>tux</c> and domain <c>homenetwork</c>.
173</p> 223</p>
174 224
175<p>
176We use these values in the next examples. First we set the hostname:
177</p>
178
179<pre caption="Setting the hostname"> 225<pre caption="Setting the host name">
180# <i>echo tux &gt; /etc/hostname</i> 226# <i>nano -w /etc/conf.d/hostname</i>
181</pre>
182 227
228<comment>(Set the HOSTNAME variable to your host name)</comment>
229HOSTNAME="<i>tux</i>"
230</pre>
231
183<p> 232<p>
184Second 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.
185</p> 237</p>
186 238
187<pre caption="Setting the domainname"> 239<pre caption="Setting the domainname">
188# <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>"
189</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>
190 251
191<p> 252<p>
192If 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
193one), you need to define that one too: 254one), you need to define that one too:
194</p> 255</p>
195 256
196<pre caption="Setting the NIS domainname"> 257<pre caption="Setting the NIS domainname">
197# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 258# <i>nano -w /etc/conf.d/net</i>
198</pre>
199 259
200<p> 260<comment>(Set the nis_domain variable to your NIS domain name)</comment>
201Now add the <c>domainname</c> script to the default runlevel: 261nis_domain_lo="<i>my-nisdomain</i>"
202</p> 262</pre>
203 263
204<pre caption="Adding domainname to the default runlevel"> 264<note>
205# <i>rc-update add domainname default</i> 265For more information on configuring DNS and NIS, please read the examples
206</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>
207 269
208</body> 270</body>
209</subsection> 271</subsection>
210<subsection> 272<subsection>
211<title>Configuring your Network</title> 273<title>Configuring your Network</title>
212<body> 274<body>
213 275
214<p> 276<p>
215Before 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
216that 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
217just 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
218your Gentoo system permanently. 280your Gentoo system permanently.
219</p> 281</p>
220 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
221<p> 289<p>
222All 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
223a 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
224networking manually. But don't fear, we'll explain everything :) 292networking manually. But don't fear, we'll explain everything. A fully
225</p> 293commented example that covers many different configurations is available in
226 294<path>/etc/conf.d/net.example</path>.
227<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
228First 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
229is used in this example): 308this example):
230</p> 309</p>
231 310
232<pre caption="Opening /etc/conf.d/net for editing"> 311<pre caption="Opening /etc/conf.d/net for editing">
233# <i>nano -w /etc/conf.d/net</i> 312# <i>nano -w /etc/conf.d/net</i>
234</pre> 313</pre>
235 314
236<p> 315<p>
237The first variable you'll find is <c>iface_eth0</c>. It uses the following 316You will see the following file:
238syntax:
239</p>
240
241<pre caption="iface_eth0 syntaxis">
242iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
243</pre>
244
245<p> 317</p>
246If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 318
247to <c>dhcp</c>. However, if you need to setup your network manually and you're 319<pre caption="Default /etc/conf.d/net">
248not familiar with all the above terms, please read the section on <uri 320# This blank configuration will automatically use DHCP for any net.*
249link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 321# scripts in /etc/init.d. To create a more complete configuration,
250Terminology</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
251</p> 326<p>
252 327To enter your own IP address, netmask and gateway, you need
328to set both <c>config_eth0</c> and <c>routes_eth0</c>:
253<p> 329</p>
254So let us give two examples; the first one uses DHCP, the second one a static IP 330
255(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">
256192.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
257</p> 336<p>
258 337To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
259<pre caption="Examples for /etc/conf.d/net"> 338<c>dhcp_eth0</c>:
260<comment>(For DHCP:)</comment>
261iface_eth0="dhcp"
262
263<comment>(For static IP:)</comment>
264iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
265gateway="eth0/192.168.0.1"
266</pre>
267
268<p> 339</p>
269If you have several network interfaces, create extra <c>iface_eth</c> variables, 340
270like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 341<pre caption="Automatically obtaining an IP address for eth0">
271shouldn'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.
272</p> 354</p>
273 355
274<p> 356<p>
275Now save the configuration and exit to continue. 357Now save the configuration and exit to continue.
276</p> 358</p>
280<subsection> 362<subsection>
281<title>Automatically Start Networking at Boot</title> 363<title>Automatically Start Networking at Boot</title>
282<body> 364<body>
283 365
284<p> 366<p>
285To 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
286default runlevel. If you have PCMCIA interfaces you should skip this action as 368default runlevel.
287the PCMCIA interfaces are started by the PCMCIA init script.
288</p> 369</p>
289 370
290<pre caption="Adding net.eth0 to the default runlevel"> 371<pre caption="Adding net.eth0 to the default runlevel">
291# <i>rc-update add net.eth0 default</i> 372# <i>rc-update add net.eth0 default</i>
292</pre> 373</pre>
297use <c>ln</c> to do this: 378use <c>ln</c> to do this:
298</p> 379</p>
299 380
300<pre caption="Creating extra initscripts"> 381<pre caption="Creating extra initscripts">
301# <i>cd /etc/init.d</i> 382# <i>cd /etc/init.d</i>
302# <i>ln -s net.eth0 net.eth1</i> 383# <i>ln -s net.lo net.eth1</i>
303# <i>rc-update add net.eth1 default</i> 384# <i>rc-update add net.eth1 default</i>
304</pre> 385</pre>
305 386
306</body> 387</body>
307</subsection> 388</subsection>
309<title>Writing Down Network Information</title> 390<title>Writing Down Network Information</title>
310<body> 391<body>
311 392
312<p> 393<p>
313You 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
314<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
315for 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.
316internal 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
317<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.
318open <path>/etc/hosts</path> and fill in the values:
319</p> 399</p>
320 400
321<pre caption="Opening /etc/hosts"> 401<pre caption="Opening /etc/hosts">
322# <i>nano -w /etc/hosts</i> 402# <i>nano -w /etc/hosts</i>
323</pre> 403</pre>
324 404
325<pre caption="Filling in the networking information"> 405<pre caption="Filling in the networking information">
326127.0.0.1 localhost 406<comment>(This defines the current system)</comment>
327192.168.0.5 jenny 407127.0.0.1 tux.homenetwork tux localhost
328192.168.0.6 benny
329192.168.0.7 tux
330</pre>
331 408
332<p> 409<comment>(Define extra systems on your network,
333If 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>
334resolution) a single line is sufficient: 411192.168.0.5 jenny.homenetwork jenny
335</p> 412192.168.0.6 benny.homenetwork benny
336
337<pre caption="/etc/hosts for lonely or fully integrated PCs">
338127.0.0.1 localhost tux
339</pre> 413</pre>
340 414
341<p> 415<p>
342Save and exit the editor to continue. 416Save and exit the editor to continue.
343</p> 417</p>
344 418
345<p> 419<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
346If you don't have PCMCIA, you can now continue with <uri 420If you don't have PCMCIA, you can now continue with <uri
347link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 421link="#sysinfo">System Information</uri>. PCMCIA-users should read the
348following topic on PCMCIA. 422following topic on PCMCIA.
349</p> 423</p>
350 424
351</body> 425</body>
352</subsection> 426</subsection>
353<subsection> 427<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
354<title>Optional: Get PCMCIA Working</title> 428<title>Optional: Get PCMCIA Working</title>
355<body> 429<body>
356 430
357<p> 431<p>
358PCMCIA-users should first install the <c>pcmcia-cs</c> package: 432PCMCIA users should first install the <c>pcmciautils</c> package.
359</p> 433</p>
360 434
361<pre caption="Installing pcmcia-cs"> 435<pre caption="Installing pcmciautils">
362# <i>emerge --usepkg pcmcia-cs</i> 436# <i>emerge pcmciautils</i>
363</pre>
364
365<p>
366When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
367runlevel:
368</p>
369
370<pre caption="Adding pcmcia to the default runlevel">
371# <i>rc-update add pcmcia default</i>
372</pre> 437</pre>
373 438
374</body> 439</body>
375</subsection> 440</subsection>
376</section> 441</section>
442
443<section id="sysinfo">
444<title>System Information</title>
377<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>
378<title>System Information</title> 460<title>System Information</title>
379<body> 461<body>
380 462
381<p> 463<p>
382Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 464Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
386<pre caption="Opening /etc/rc.conf"> 468<pre caption="Opening /etc/rc.conf">
387# <i>nano -w /etc/rc.conf</i> 469# <i>nano -w /etc/rc.conf</i>
388</pre> 470</pre>
389 471
390<p> 472<p>
473When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
474</p>
475
476<p>
391As 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
392configuration variables. Take special care with the <c>KEYMAP</c> setting: if 478configuration variables. You can configure your system to use unicode and
393you 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).
394your keyboard. 480</p>
481
395</p> 482<p>
483Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
484Edit it to configure your keyboard.
485</p>
396 486
397<note> 487<pre caption="Opening /etc/conf.d/keymaps">
398Users of USB-based SPARC systems and SPARC clones might need to select an i386 488# <i>nano -w /etc/conf.d/keymaps</i>
399keymap (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>.
400</note> 500</note>
401 501
402<p> 502<p>
403When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 503When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
404continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 504exit.
505</p>
506
405</p> 507<p>
508Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
509according to your needs.
510</p>
406 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>
407</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>
408</section> 567</section>
409</sections> 568</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20