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

Legend:
Removed from v.1.64  
changed lines
  Added in v.1.91

  ViewVC Help
Powered by ViewVC 1.1.20