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

Legend:
Removed from v.1.18  
changed lines
  Added in v.1.111

  ViewVC Help
Powered by ViewVC 1.1.20