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

Legend:
Removed from v.1.41  
changed lines
  Added in v.1.99

  ViewVC Help
Powered by ViewVC 1.1.20