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

Legend:
Removed from v.1.34  
changed lines
  Added in v.1.109

  ViewVC Help
Powered by ViewVC 1.1.20