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

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.103

  ViewVC Help
Powered by ViewVC 1.1.20