/[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.60 Revision 1.81
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.60 2005/04/29 15:30:23 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.81 2006/08/30 22:52:28 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>2.2</version> 11<version>7.0</version>
12<date>2005-04-20</date> 12<date>2006-08-30</date>
13 13
14<section> 14<section>
15<title>Filesystem Information</title> 15<title>Filesystem Information</title>
16<subsection> 16<subsection>
17<title>What is fstab?</title> 17<title>What is fstab?</title>
18<body> 18<body>
19 19
20<p> 20<p>
21Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 22<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 23(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 24and with what special options (automatically or not, whether users can mount
25them or not, etc.) 25them or not, etc.)
26</p> 26</p>
27 27
41<li> 41<li>
42 The first field shows the <b>partition</b> described (the path to the device 42 The first field shows the <b>partition</b> described (the path to the device
43 file) 43 file)
44</li> 44</li>
45<li> 45<li>
46 The second field shows the <b>mountpoint</b> at which the partition should be 46 The second field shows the <b>mount point</b> at which the partition should be
47 mounted 47 mounted
48</li> 48</li>
49<li> 49<li>
50 The third field shows the <b>filesystem</b> used by the partition 50 The third field shows the <b>filesystem</b> used by the partition
51</li> 51</li>
52<li> 52<li>
53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 53 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, 54 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 55 you are encouraged to read the mount man page (<c>man mount</c>) for a full
56 listing. Multiple mountoptions are comma-separated. 56 listing. Multiple mount options are comma-separated.
57</li> 57</li>
58<li> 58<li>
59 The fifth field is used by <c>dump</c> to determine if the partition needs to 59 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). 60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
61</li> 61</li>
65 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 65 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). 66 (or <c>0</c> if a filesystem check isn't necessary).
67</li> 67</li>
68</ul> 68</ul>
69 69
70<p> 70<impo>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab 71The 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 72fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>.
73<path>/etc/fstab</path>: 73</impo>
74</p>
75 74
76<pre caption="Opening /etc/fstab"> 75<pre caption="Opening /etc/fstab">
77# <i>nano -w /etc/fstab</i> 76# <i>nano -w /etc/fstab</i>
78</pre> 77</pre>
79 78
79</body>
80<body test="func:keyval('/boot')">
81
80<p> 82<p>
81Let us take a look at how we write down the options for the <path>/boot</path> 83Let 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 84partition. 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. 85<path>/boot</path>, don't copy it.
84</p>
85
86<p> 86</p>
87
88<p test="contains(func:keyval('/boot'), '/dev/hd')">
87In our default x86 partitioning example <path>/boot</path> is the 89In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
88<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 90usually the <path><keyval id="/boot"/></path> partition (or
91<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: 92filesystem. It needs to be checked during boot, so we would write down:
93</p>
94
95<p test="contains(func:keyval('/boot'), '/dev/sd')">
96In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
97usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
98filesystem. It needs to be checked during boot, so we would write down:
90</p> 99</p>
91 100
92<pre caption="An example /boot line for /etc/fstab"> 101<pre caption="An example /boot line for /etc/fstab">
93/dev/hda1 /boot ext2 defaults 1 2 102<keyval id="/boot"/> /boot ext2 defaults 1 2
94</pre> 103</pre>
95 104
96<p> 105<p>
97Some users don't want their <path>/boot</path> partition to be mounted 106Some users don't want their <path>/boot</path> partition to be mounted
98automatically to improve their system's security. Those people should 107automatically to improve their system's security. Those people should
99substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 108substitute <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. 109manually mount this partition every time you want to use it.
101</p> 110</p>
102 111
112</body>
113<body>
114
115<p test="not(func:keyval('arch')='SPARC')">
116Add the rules that match your partitioning scheme and append rules for
117<path>/proc</path>, <c>tmpfs</c>, for your CD-ROM drive(s), and of course, if
118you have other partitions or drives, for those too.
103<p> 119</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 120
109<pre caption="An improved /boot line for /etc/fstab"> 121<p test="func:keyval('arch')='SPARC'">
110/dev/hda1 /boot ext2 defaults,noatime 1 2 122Add the rules that match your partitioning schema and append rules for
111</pre> 123<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
112 124drive(s), and of course, if you have other partitions or drives, for those too.
113<p> 125</p>
114If we continue with this, we would end up with the following three lines (for 126
115<path>/boot</path>, <path>/</path> and the swap partition):
116</p> 127<p>
117 128Now 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> 129</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 130
130<pre caption="A full /etc/fstab example"> 131<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 132<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
133/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
134 135
135none /proc proc defaults 0 0 136none /proc proc defaults 0 0
136none /dev/shm tmpfs nodev,nosuid,noexec 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
137 138
139/dev/cdrom /mnt/cdrom auto noauto,user 0 0
140</pre>
141
142<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
143<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
144/dev/sda3 none swap sw 0 0
145/dev/sda4 / ext3 noatime 0 1
146
147none /proc proc defaults 0 0
148none /dev/shm tmpfs nodev,nosuid,noexec 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')='Alpha' or func:keyval('arch')='MIPS'">
154<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
155/dev/sda2 none swap sw 0 0
156/dev/sda3 / ext3 noatime 0 1
157
158none /proc proc defaults 0 0
159none /dev/shm tmpfs nodev,nosuid,noexec 0 0
160
161/dev/cdrom /mnt/cdrom auto noauto,user 0 0
162</pre>
163
164<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
165/dev/sda1 / ext3 noatime 0 1
166/dev/sda2 none swap sw 0 0
167/dev/sda4 /usr ext3 noatime 0 2
168/dev/sda5 /var ext3 noatime 0 2
169/dev/sda6 /home ext3 noatime 0 2
170
171none /proc/openprom openpromfs defaults 0 0
172none /proc proc defaults 0 0
173none /dev/shm tmpfs nodev,nosuid,noexec 0 0
174
138/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 175/dev/cdrom /mnt/cdrom auto noauto,user 0 0
176</pre>
177
178<note test="func:keyval('arch')='PPC'">
179There are important variations between PPC machine types. Please make sure you
180adapt the following example to your system.
181</note>
182
183<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'">
184/dev/hda4 / ext3 noatime 0 1
185/dev/hda3 none swap sw 0 0
186
187none /proc proc defaults 0 0
188none /dev/shm tmpfs nodev,nosuid,noexec 0 0
189
190/dev/cdrom /mnt/cdrom auto noauto,user 0 0
191</pre>
192
193<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'">
194/dev/sda4 / ext3 noatime 0 1
195/dev/sda3 none swap sw 0 0
196
197none /proc proc defaults 0 0
198none /dev/shm tmpfs nodev,nosuid,noexec 0 0
199
200/dev/cdrom /mnt/cdrom auto noauto,user 0 0
139</pre> 201</pre>
140 202
141<p> 203<p>
142<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 204<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 205removable 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. 206<c>user</c> makes it possible for non-root users to mount the CD.
145</p> 207</p>
146 208
147<p> 209<p>
148Now use the above example to create your <path>/etc/fstab</path>. If you are a 210To 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 211mount option, which results in a faster system since access times
150<path>/etc/fstab</path> 212aren'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> 213</p>
157 214
158<p> 215<p>
159Double-check your <path>/etc/fstab</path>, save and quit to continue. 216Double-check your <path>/etc/fstab</path>, save and quit to continue.
160</p> 217</p>
161 218
163</subsection> 220</subsection>
164</section> 221</section>
165<section> 222<section>
166<title>Networking Information</title> 223<title>Networking Information</title>
167<subsection> 224<subsection>
168<title>Hostname, Domainname etc.</title> 225<title>Host name</title>
169<body> 226<body>
170 227
171<p> 228<p>
172One of the choices the user has to make is name his/her PC. This seems to be 229One 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 230quite 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 231appropriate 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 232choose can be changed afterwards. For all we care, you can just call your system
176<c>tux</c> and domain <c>homenetwork</c>. 233<c>tux</c> and domain <c>homenetwork</c>.
177</p> 234</p>
178 235
179<p>
180We use these values in the next examples. First we set the hostname:
181</p>
182
183<pre caption="Setting the hostname"> 236<pre caption="Setting the host name">
184# <i>echo tux &gt; /etc/hostname</i> 237# <i>nano -w /etc/conf.d/hostname</i>
185</pre>
186 238
187<p> 239<comment>(Set the HOSTNAME variable to your host name)</comment>
188Second we set the domainname: 240HOSTNAME="<i>tux</i>"
189</p>
190
191<pre caption="Setting the domainname">
192# <i>echo homenetwork &gt; /etc/dnsdomainname</i>
193</pre>
194
195<p>
196If 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:
198</p>
199
200<pre caption="Setting the NIS domainname">
201# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
202</pre>
203
204<p>
205Now add the <c>domainname</c> script to the default runlevel:
206</p>
207
208<pre caption="Adding domainname to the default runlevel">
209# <i>rc-update add domainname default</i>
210</pre> 241</pre>
211 242
212</body> 243</body>
213</subsection> 244</subsection>
214<subsection> 245<subsection>
215<title>Configuring your Network</title> 246<title>Configuring your Network</title>
216<body> 247<body>
217 248
218<p> 249<p>
219Before you get that "Hey, we've had that already"-feeling, you should remember 250Before 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 251that 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 252just for the installation. Right now you are going to configure networking for
222your Gentoo system permanently. 253your Gentoo system permanently.
223</p> 254</p>
224 255
256<note>
257More detailed information about networking, including advanced topics like
258bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
259link="?part=4">Gentoo Network Configuration</uri> section.
260</note>
261
225<p> 262<p>
226All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 263All 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 264a straightforward yet not intuitive syntax if you don't know how to set up
228networking manually. But don't fear, we'll explain everything :) 265networking manually. But don't fear, we'll explain everything. A fully
229</p> 266commented example that covers many different configurations is available in
230 267<path>/etc/conf.d/net.example</path>.
231<p> 268</p>
269
270<p>
271DHCP is used by default and does not require any further configuration.
272</p>
273
274<p>
275If you need to configure your network connection either because you need
276specific 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> 277<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233is used in this example): 278this example):
234</p> 279</p>
235 280
236<pre caption="Opening /etc/conf.d/net for editing"> 281<pre caption="Opening /etc/conf.d/net for editing">
237# <i>nano -w /etc/conf.d/net</i> 282# <i>nano -w /etc/conf.d/net</i>
238</pre> 283</pre>
239 284
240<!-- Old baselayout - current stable -->
241
242<p>
243The first variable you'll find is <c>iface_eth0</c>. It uses the following
244syntax:
245</p> 285<p>
246 286You will see the following file:
247<pre caption="iface_eth0 syntaxis">
248iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
249</pre>
250
251<p> 287</p>
252If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 288
253to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 289<pre caption="Default /etc/conf.d/net">
254If you need to set up your network manually and you're 290# This blank configuration will automatically use DHCP for any net.*
255not familiar with all the above terms, please read the section on <uri 291# scripts in /etc/init.d. To create a more complete configuration,
256link="?part=1&amp;chap=3#network_term">Understanding Network 292# please review /etc/conf.d/net.example and save your configuration
257Terminology</uri> if you haven't done so already. 293# in /etc/conf.d/net (this file :]!).
294</pre>
295
258</p> 296<p>
259 297To enter your own IP address, netmask and gateway, you need
298to set both <c>config_eth0</c> and <c>routes_eth0</c>:
260<p> 299</p>
261So let us give three examples; the first one uses DHCP, the second one a static 300
262IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and 301<pre caption="Manually setting IP information for eth0">
263gateway 192.168.0.1 while the third one just activates the interface for 302config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
264rp-pppoe usage: 303routes_eth0=( "default gw 192.168.0.1" )
304</pre>
305
265</p> 306<p>
266 307To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
267<pre caption="Examples for /etc/conf.d/net"> 308<c>dhcp_eth0</c>:
268<comment>(For DHCP)</comment>
269iface_eth0="dhcp"
270<comment># Some network admins require that you use the</comment>
271<comment># hostname and domainname provided by the DHCP server.</comment>
272<comment># In that case, add the following to let dhcpcd use them.</comment>
273<comment># That will override your own hostname and domainname definitions.</comment>
274dhcpcd_eth0="-HD"
275<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
276<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
277dhcpcd_eth0="-N"
278
279<comment>(For static IP)</comment>
280iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
281gateway="eth0/192.168.0.1"
282
283<comment>(For rp-pppoe)</comment>
284iface_eth0="up"
285</pre>
286
287<p> 309</p>
288If you have several network interfaces, create extra <c>iface_eth</c> variables,
289like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
290shouldn't be reproduced as you can only set one gateway per computer.
291</p>
292 310
293<!-- New baselayout - current testing
294
295<p>
296The first variable you'll find is called <c>config_eth0</c>. As you can probably
297imagine, this variable configured the eth0 network interface. If the interface
298needs to automatically obtain an IP through DHCP, you should set it like so:
299</p>
300
301<pre caption="Automatically obtaining an IP for eth0"> 311<pre caption="Automatically obtaining an IP address for eth0">
302config_eth0=( "dhcp" ) 312config_eth0=( "dhcp" )
313dhcp_eth0="nodns nontp nonis"
303</pre> 314</pre>
304 315
305<p>
306However, if you have to enter your own IP address, netmask and gateway, you need
307to set both <c>config_eth0</c> and <c>routes_eth0</c>:
308</p> 316<p>
309 317Please read <path>/etc/conf.d/net.example</path> for a list of all available
310<pre caption="Manually setting IP information for eth0"> 318options.
311config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
312routes_eth0=( "default gw 192.168.0.1" )
313</pre> 319</p>
314 320
315<p> 321<p>
316If you have several network interfaces repeat the above steps for 322If you have several network interfaces repeat the above steps for
317<c>config_eth1</c>, <c>config_eth2</c>, etc. 323<c>config_eth1</c>, <c>config_eth2</c>, etc.
318</p> 324</p>
319
320-->
321 325
322<p> 326<p>
323Now save the configuration and exit to continue. 327Now save the configuration and exit to continue.
324</p> 328</p>
325 329
345use <c>ln</c> to do this: 349use <c>ln</c> to do this:
346</p> 350</p>
347 351
348<pre caption="Creating extra initscripts"> 352<pre caption="Creating extra initscripts">
349# <i>cd /etc/init.d</i> 353# <i>cd /etc/init.d</i>
350# <i>ln -s net.eth0 net.eth1</i> 354# <i>ln -s net.lo net.eth1</i>
351# <i>rc-update add net.eth1 default</i> 355# <i>rc-update add net.eth1 default</i>
352</pre> 356</pre>
353 357
354</body> 358</body>
355</subsection> 359</subsection>
357<title>Writing Down Network Information</title> 361<title>Writing Down Network Information</title>
358<body> 362<body>
359 363
360<p> 364<p>
361You now need to inform Linux about your network. This is defined in 365You now need to inform Linux about your network. This is defined in
362<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 366<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
363for hosts that aren't resolved by your nameserver. For instance, if your 367hosts that aren't resolved by your nameserver. You need to define your system.
364internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 368You may also want to define other systems on your network if you don't want to
365<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 369set up your own internal DNS system.
366open <path>/etc/hosts</path> and fill in the values:
367</p> 370</p>
368 371
369<pre caption="Opening /etc/hosts"> 372<pre caption="Opening /etc/hosts">
370# <i>nano -w /etc/hosts</i> 373# <i>nano -w /etc/hosts</i>
371</pre> 374</pre>
372 375
373<pre caption="Filling in the networking information"> 376<pre caption="Filling in the networking information">
374127.0.0.1 localhost 377<comment>(This defines the current system)</comment>
378127.0.0.1 tux.homenetwork tux localhost
379
380<comment>(Define extra systems on your network,
381they need to have a static IP to be defined this way.)</comment>
375192.168.0.5 jenny.homenetwork jenny 382192.168.0.5 jenny.homenetwork jenny
376192.168.0.6 benny.homenetwork benny 383192.168.0.6 benny.homenetwork benny
377192.168.0.7 tux.homenetwork tux
378</pre>
379
380<p>
381If your system is the only system (or the nameservers handle all name
382resolution) a single line is sufficient. For instance, if you want to call your
383system <c>tux</c>:
384</p>
385
386<pre caption="/etc/hosts for lonely or fully integrated PCs">
387127.0.0.1 localhost tux
388</pre> 384</pre>
389 385
390<p> 386<p>
391Save and exit the editor to continue. 387Save and exit the editor to continue.
392</p> 388</p>
393 389
394<p> 390<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
395If you don't have PCMCIA, you can now continue with <uri 391If you don't have PCMCIA, you can now continue with <uri
396link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 392link="#sysinfo">System Information</uri>. PCMCIA-users should read the
397following topic on PCMCIA. 393following topic on PCMCIA.
398</p> 394</p>
399 395
400</body> 396</body>
401</subsection> 397</subsection>
402<subsection> 398<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
403<title>Optional: Get PCMCIA Working</title> 399<title>Optional: Get PCMCIA Working</title>
404<body> 400<body>
405
406<note>
407pcmcia-cs is only available for x86, amd64 and ppc platforms.
408</note>
409 401
410<p> 402<p>
411PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 403PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
412includes users who will be working with a 2.6 kernel (even though they won't be 404includes users who will be working with a 2.6 kernel (even though they won't be
413using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary 405using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
428</pre> 420</pre>
429 421
430</body> 422</body>
431</subsection> 423</subsection>
432</section> 424</section>
433<section> 425
426<section id="sysinfo">
434<title>System Information</title> 427<title>System Information</title>
435<subsection> 428<subsection>
436<title>Root Password</title> 429<title>Root Password</title>
437<body> 430<body>
438 431
467<pre caption="Opening /etc/rc.conf"> 460<pre caption="Opening /etc/rc.conf">
468# <i>nano -w /etc/rc.conf</i> 461# <i>nano -w /etc/rc.conf</i>
469</pre> 462</pre>
470 463
471<p> 464<p>
465When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
466</p>
467
468<p>
472As you can see, this file is well commented to help you set up the necessary 469As you can see, this file is well commented to help you set up the necessary
473configuration variables. Take special care with the <c>KEYMAP</c> setting: if 470configuration variables. You can configure your system to use unicode and
474you select the wrong <c>KEYMAP</c> you will get weird results when typing on 471define your default editor and your display manager (like gdm or kdm).
475your keyboard. 472</p>
473
476</p> 474<p>
475Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
476Edit it to configure your keyboard.
477</p>
477 478
478<note> 479<pre caption="Opening /etc/conf.d/keymaps">
480# <i>nano -w /etc/conf.d/keymaps</i>
481</pre>
482
483<p>
484Take special care with the <c>KEYMAP</c> variable. If you select the wrong
485<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
486</p>
487
488<note test="func:keyval('arch')='SPARC'">
479Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 489Users of USB-based SPARC systems and SPARC clones might need to select an i386
480select an i386 keymap (such as "us") instead of "sunkeymap". 490keymap (such as "us") instead of "sunkeymap".
481</note> 491</note>
482 492
483<p> 493<note test="substring(func:keyval('arch'),1,3)='PPC'">
484<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use 494PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
485ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have 495keymaps on boot have to enable ADB keycode sendings in their kernel and have to
486to set a mac/ppc keymap in <path>rc.conf</path>. 496set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
497</note>
498
487</p> 499<p>
488 500When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
501exit.
489<p> 502</p>
503
504<p>
505Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
506according to your needs.
507</p>
508
509<pre caption="Opening /etc/conf.d/clock">
510# <i>nano -w /etc/conf.d/clock</i>
511</pre>
512
513<p>
514If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
515the file. Otherwise you will notice some clock skew. Furthermore, Windows
516assumes that your hardware clock uses local time, so if you want to dualboot,
517you should set this variable appropriately, otherwise your clock will go crazy.
518</p>
519
520<p>
490When you're finished configuring <path>/etc/rc.conf</path>, save and exit. 521When you're finished configuring <path>/etc/conf.d/clock</path>, save and
491</p> 522exit.
492
493<p> 523</p>
494If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with 524
525<p test="not(func:keyval('arch')='PPC64')">
495<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>. 526Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
527Tools</uri>.
496</p> 528</p>
497 529
498</body> 530</body>
499</subsection>
500<subsection> 531</subsection>
532<subsection test="func:keyval('arch')='PPC64'">
501<title>Configuring the Console</title> 533<title>Configuring the Console</title>
502<body> 534<body>
503 535
504<note>
505The following section applies to the IBM POWER5 and JS20 hardware platforms.
506</note>
507
508<p>
509If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
510the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
511</p> 536<p>
537If you are using a virtual console, you must uncomment the appropriate line in
538<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
539</p>
512 540
513<pre caption="Enabling hvc support in /etc/inittab"> 541<pre caption="Enabling hvc or hvsi support in /etc/inittab">
514hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220 542hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
543hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
544</pre>
545
546<p>
547You should also take this time to verify that the appropriate console is
548listed in <path>/etc/securetty</path>.
515</pre> 549</p>
516 550
517<p> 551<p>
518You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary 552You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
519System Tools</uri>. 553System Tools</uri>.
520</p> 554</p>

Legend:
Removed from v.1.60  
changed lines
  Added in v.1.81

  ViewVC Help
Powered by ViewVC 1.1.20