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

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

  ViewVC Help
Powered by ViewVC 1.1.20