/[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.14 Revision 1.81
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
1<!-- 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 -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
3 6
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.14 2003/12/20 20:32:02 swift 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 $ -->
5 8
6<sections> 9<sections>
7<section>
8<title>Timezone</title>
9<body>
10 10
11<p> 11<version>7.0</version>
12You now need to select your timezone so that your system knows where it is 12<date>2006-08-30</date>
13located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
14symlink to <path>/etc/localtime</path> using <c>ln</c>:
15</p>
16 13
17<pre caption="Setting the timezone information">
18# <i>ls /usr/share/zoneinfo</i>
19<comment>(Suppose you want to use GMT:)</comment>
20# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
21</pre>
22
23</body>
24</section>
25<section> 14<section>
26<title>Filesystem Information</title> 15<title>Filesystem Information</title>
27<subsection> 16<subsection>
28<title>What is fstab?</title> 17<title>What is fstab?</title>
29<body> 18<body>
30 19
31<p> 20<p>
32Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
33<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
34(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
35(special options) and when (automatically or not, can users mount those or not, 24and with what special options (automatically or not, whether users can mount
36etc.). 25them or not, etc.)
37</p> 26</p>
38 27
39</body> 28</body>
40</subsection> 29</subsection>
41<subsection> 30<subsection>
42<title>Creating /etc/fstab</title> 31<title>Creating /etc/fstab</title>
43<body> 32<body>
44 33
45<p> 34<p>
46<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six 35<path>/etc/fstab</path> uses a special syntax. Every line consists of six
47fields, separated by whitespace (space(s), tabs or a mixture). Each field has 36fields, separated by whitespace (space(s), tabs or a mixture). Each field has
48its own meaning: 37its own meaning:
49</p> 38</p>
50 39
51<ul> 40<ul>
52<li> 41<li>
53 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
54 file) 43 file)
55</li> 44</li>
56<li> 45<li>
57 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
58 mounted 47 mounted
59</li> 48</li>
60<li> 49<li>
61 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
62</li> 51</li>
63<li> 52<li>
64 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
65 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,
66 you are encouraged to read the mount manpage (<c>man mount</c>) for a full 55 you are encouraged to read the mount man page (<c>man mount</c>) for a full
67 listing. Multiple mountoptions are comma-separated. 56 listing. Multiple mount options are comma-separated.
68</li> 57</li>
69<li> 58<li>
70 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
71 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).
72</li> 61</li>
73<li> 62<li>
74 The sixth field is used by <c>fsck</c> the order in which filesystems should 63 The sixth field is used by <c>fsck</c> to determine the order in which
75 be <b>check</b>ed if the system wasn't shut down properly. The root filesystem 64 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
76 should have <c>1</c> while the rest should have <c>2</c> (or <c>0</c> in case 65 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
77 a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
78</li> 67</li>
79</ul> 68</ul>
80 69
81<p> 70<impo>
82So start <c>nano</c> (or your favorite editor) to create your 71The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
83<path>/etc/fstab</path>: 72fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>.
84</p> 73</impo>
85 74
86<pre caption="Opening /etc/fstab"> 75<pre caption="Opening /etc/fstab">
87# <i>nano -w /etc/fstab</i> 76# <i>nano -w /etc/fstab</i>
88</pre> 77</pre>
89 78
79</body>
80<body test="func:keyval('/boot')">
81
90<p> 82<p>
91Lets 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>
92partition. 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
93<path>/boot</path> partition, don't copy it verbatim. 85<path>/boot</path>, don't copy it.
94</p>
95
96<p> 86</p>
87
88<p test="contains(func:keyval('/boot'), '/dev/hd')">
97In our default x86 partitioning example <path>/boot</path> is the 89In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
98<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't 90usually the <path><keyval id="/boot"/></path> partition (or
99be mounted automatically (<c>noauto</c>) but does need to be checked. So we 91<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
100would 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:
101</p> 99</p>
102 100
103<pre caption="An example /boot line for /etc/fstab"> 101<pre caption="An example /boot line for /etc/fstab">
104/dev/hda1 /boot ext2 noauto 1 2 102<keyval id="/boot"/> /boot ext2 defaults 1 2
105</pre> 103</pre>
106 104
107<p>
108Now, to improve performance, most users would want to add the <c>noatime</c>
109option as mountoption, which results in a faster system since access times
110aren't registered (you don't need those generally anyway):
111</p> 105<p>
112 106Some users don't want their <path>/boot</path> partition to be mounted
113<pre caption="An improved /boot line for /etc/fstab"> 107automatically to improve their system's security. Those people should
114/dev/hda1 /boot ext2 noauto,noatime 1 2 108substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
115</pre> 109manually mount this partition every time you want to use it.
116
117<p> 110</p>
118If we continue with this, we would end up with the following three lines (for 111
119<path>/boot</path>, <path>/</path> and the swap partition): 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.
119</p>
120
121<p test="func:keyval('arch')='SPARC'">
122Add the rules that match your partitioning schema and append rules for
123<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
124drive(s), and of course, if you have other partitions or drives, for those too.
125</p>
126
120</p> 127<p>
128Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
129</p>
121 130
122<pre caption="Three /etc/fstab lines"> 131<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
123/dev/hda1 /boot ext2 noauto,noatime 1 2 132<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
124/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
125/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
126</pre>
127 135
128<p>
129To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
130(required) and for your CD-ROM drive (and of course, if you have other
131partitions or drives, for those too):
132</p>
133
134<pre caption="A full /etc/fstab example">
135/dev/hda1 /boot ext2 noauto,noatime 1 2
136/dev/hda2 none swap sw 0 0
137/dev/hda3 / ext3 noatime 0 1
138
139none /proc proc defaults 0 0 136none /proc proc defaults 0 0
140none /dev/shm tmpfs defaults 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
141 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
142/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
143</pre> 201</pre>
144 202
145<p> 203<p>
146<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
147removable 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
148<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.
149</p> 207</p>
150 208
151<p> 209<p>
152Now 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>
153SPARC-user, you should add the following line to your <path>/etc/fstab</path> 211mount option, which results in a faster system since access times
154too: 212aren't registered (you don't need those generally anyway).
155</p>
156
157<pre caption="Adding openprom filesystem to /etc/fstab">
158none /proc/openprom openpromfs defaults 0 0
159</pre>
160
161<p> 213</p>
162If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>: 214
163</p> 215<p>
164
165<pre caption="Adding usbfs filesystem to /etc/fstab">
166none /proc/bus/usb usbfs defaults 0 0
167</pre>
168
169<p>
170Reread your <path>/etc/fstab</path>, save and quit to continue. 216Double-check your <path>/etc/fstab</path>, save and quit to continue.
171</p> 217</p>
172 218
173</body> 219</body>
174</subsection> 220</subsection>
175</section> 221</section>
176<section> 222<section>
177<title>Networking Information</title> 223<title>Networking Information</title>
178<subsection> 224<subsection>
179<title>Hostname, Domainname etc.</title> 225<title>Host name</title>
180<body> 226<body>
181 227
182<p> 228<p>
183One of the choices the user has to make is name his PC. This seems to be quite 229One of the choices the user has to make is name his/her PC. This seems to be
184easy, but <e>lots</e> of users are having difficulties finding the appropriate 230quite easy, but <e>lots</e> of users are having difficulties finding the
185name for their Linux-pc. To speed things up, know that any name you choose can 231appropriate name for their Linux-pc. To speed things up, know that any name you
186be 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
187<c>tux</c> and domain <c>homenetwork</c>. 233<c>tux</c> and domain <c>homenetwork</c>.
188</p> 234</p>
189 235
190<p>
191We use these values in the next examples. First we set the hostname:
192</p>
193
194<pre caption="Setting the hostname"> 236<pre caption="Setting the host name">
195# <i>echo tux &gt; /etc/hostname</i> 237# <i>nano -w /etc/conf.d/hostname</i>
196</pre>
197 238
198<p> 239<comment>(Set the HOSTNAME variable to your host name)</comment>
199Second we set the domainname: 240HOSTNAME="<i>tux</i>"
200</p>
201
202<pre caption="Setting the domainname">
203# <i>echo homenetwork &gt; /etc/dnsdomainname</i>
204</pre>
205
206<p>
207If you have a NIS domain (if you don't know what that is, then you don't have
208one), you need to define that one too:
209</p>
210
211<pre caption="Setting the NIS domainname">
212# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i>
213</pre>
214
215<p>
216Now add the <c>domainname</c> script to the default runlevel:
217</p>
218
219<pre caption="Adding domainname to the default runlevel">
220# <i>rc-update add domainname default</i>
221</pre> 241</pre>
222 242
223</body> 243</body>
224</subsection> 244</subsection>
225<subsection> 245<subsection>
226<title>Configuring your Network</title> 246<title>Configuring your Network</title>
227<body> 247<body>
228 248
229<p> 249<p>
230Before 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
231that 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
232just 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
233your Gentoo system permanently. 253your Gentoo system permanently.
234</p> 254</p>
235 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
236<p> 262<p>
237All 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
238a straightforward yet not intuitive syntax if you don't know how to setup 264a straightforward yet not intuitive syntax if you don't know how to set up
239networking manually. But don't fear, we'll explain everything :) 265networking manually. But don't fear, we'll explain everything. A fully
240</p> 266commented example that covers many different configurations is available in
241 267<path>/etc/conf.d/net.example</path>.
242<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
243First 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
244is used in this example): 278this example):
245</p> 279</p>
246 280
247<pre caption="Opening /etc/conf.d/net for editing"> 281<pre caption="Opening /etc/conf.d/net for editing">
248# <i>nano -w /etc/conf.d/net</i> 282# <i>nano -w /etc/conf.d/net</i>
249</pre> 283</pre>
250 284
251<p> 285<p>
252The first variable you'll find is <c>iface_eth0</c>. It uses the following 286You will see the following file:
253syntax:
254</p>
255
256<pre caption="iface_eth0 syntaxis">
257iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
258</pre>
259
260<p> 287</p>
261If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 288
262to <c>dhcp</c>. However, if you need to setup your network manually and you're 289<pre caption="Default /etc/conf.d/net">
263not familiar with all the above terms, please read the section on <uri 290# This blank configuration will automatically use DHCP for any net.*
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 291# scripts in /etc/init.d. To create a more complete configuration,
265Terminology</uri> if you haven't done so already. 292# please review /etc/conf.d/net.example and save your configuration
293# in /etc/conf.d/net (this file :]!).
294</pre>
295
266</p> 296<p>
267 297To enter your own IP address, netmask and gateway, you need
298to set both <c>config_eth0</c> and <c>routes_eth0</c>:
268<p> 299</p>
269So lets give two examples; the first one uses DHCP, the second one a static IP 300
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 301<pre caption="Manually setting IP information for eth0">
271192.168.0.1: 302config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
303routes_eth0=( "default gw 192.168.0.1" )
304</pre>
305
272</p> 306<p>
273 307To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
274<pre caption="Examples for /etc/conf.d/net"> 308<c>dhcp_eth0</c>:
275<comment>(For DHCP:)</comment>
276iface_eth0="dhcp"
277
278<comment>(For static IP:)</comment>
279iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
280gateway="eth0/192.168.0.1"
281</pre>
282
283<p> 309</p>
284If you have several network interfaces, create extra <c>iface_eth</c> variables, 310
285like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 311<pre caption="Automatically obtaining an IP address for eth0">
286shouldn't be reproduced as you can only set one gateway per computer. 312config_eth0=( "dhcp" )
313dhcp_eth0="nodns nontp nonis"
314</pre>
315
316<p>
317Please read <path>/etc/conf.d/net.example</path> for a list of all available
318options.
319</p>
320
321<p>
322If you have several network interfaces repeat the above steps for
323<c>config_eth1</c>, <c>config_eth2</c>, etc.
287</p> 324</p>
288 325
289<p> 326<p>
290Now save the configuration and exit to continue. 327Now save the configuration and exit to continue.
291</p> 328</p>
295<subsection> 332<subsection>
296<title>Automatically Start Networking at Boot</title> 333<title>Automatically Start Networking at Boot</title>
297<body> 334<body>
298 335
299<p> 336<p>
300To have your network interfaces activated at boot, you need to add those to the 337To have your network interfaces activated at boot, you need to add them to the
301default runlevel. If you have PCMCIA interfaces you should skip this action as 338default runlevel. If you have PCMCIA interfaces you should skip this action as
302the PCMCIA interfaces are started by the PCMCIA init script. 339the PCMCIA interfaces are started by the PCMCIA init script.
303</p> 340</p>
304 341
305<pre caption="Adding net.eth0 to the default runlevel"> 342<pre caption="Adding net.eth0 to the default runlevel">
312use <c>ln</c> to do this: 349use <c>ln</c> to do this:
313</p> 350</p>
314 351
315<pre caption="Creating extra initscripts"> 352<pre caption="Creating extra initscripts">
316# <i>cd /etc/init.d</i> 353# <i>cd /etc/init.d</i>
317# <i>ln -s net.eth0 net.eth1</i> 354# <i>ln -s net.lo net.eth1</i>
318# <i>rc-update add net.eth1 default</i> 355# <i>rc-update add net.eth1 default</i>
319</pre> 356</pre>
320 357
321</body> 358</body>
322</subsection> 359</subsection>
324<title>Writing Down Network Information</title> 361<title>Writing Down Network Information</title>
325<body> 362<body>
326 363
327<p> 364<p>
328You 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
329<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
330for 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.
331internal 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
332<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.
333open <path>/etc/hosts</path> and fill in the values:
334</p> 370</p>
335 371
336<pre caption="Opening /etc/hosts"> 372<pre caption="Opening /etc/hosts">
337# <i>nano -w /etc/hosts</i> 373# <i>nano -w /etc/hosts</i>
338</pre> 374</pre>
339 375
340<pre caption="Filling in the networking information"> 376<pre caption="Filling in the networking information">
341127.0.0.1 localhost 377<comment>(This defines the current system)</comment>
342192.168.0.5 jenny 378127.0.0.1 tux.homenetwork tux localhost
343192.168.0.6 benny
344192.168.0.7 tux
345</pre>
346 379
347<p> 380<comment>(Define extra systems on your network,
348If your system is the only system (or the nameservers handle all name 381they need to have a static IP to be defined this way.)</comment>
349resolution) a single line is sufficient: 382192.168.0.5 jenny.homenetwork jenny
350</p> 383192.168.0.6 benny.homenetwork benny
351
352<pre caption="/etc/hosts for lonely or fully integrated PCs">
353127.0.0.1 localhost tux
354</pre> 384</pre>
355 385
356<p> 386<p>
357Save and exit the editor to continue. 387Save and exit the editor to continue.
358</p> 388</p>
359 389
360<p> 390<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
361If you don't have PCMCIA, you can now continue with <uri 391If you don't have PCMCIA, you can now continue with <uri
362link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 392link="#sysinfo">System Information</uri>. PCMCIA-users should read the
363following topic on PCMCIA. 393following topic on PCMCIA.
364</p> 394</p>
365 395
366</body> 396</body>
367</subsection> 397</subsection>
368<subsection> 398<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
369<title>Optional: Get PCMCIA Working</title> 399<title>Optional: Get PCMCIA Working</title>
370<body> 400<body>
371 401
372<p> 402<p>
373PCMCIA-users should first install the <c>pcmcia-cs</c> package: 403PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
404includes users who will be working with a 2.6 kernel (even though they won't be
405using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
406to avoid installing xorg-x11 at this moment:
374</p> 407</p>
375 408
376<pre caption="Installing pcmcia-cs"> 409<pre caption="Installing pcmcia-cs">
377# <i>emerge --usepkg pcmcia-cs</i> 410# <i>USE="-X" emerge pcmcia-cs</i>
378</pre> 411</pre>
379 412
380<p> 413<p>
381When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 414When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
382runlevel: 415runlevel:
383</p> 416</p>
384 417
385<pre caption="Adding pcmcia to the boot runlevel"> 418<pre caption="Adding pcmcia to the default runlevel">
386# <i>rc-update add pcmcia boot</i> 419# <i>rc-update add pcmcia default</i>
387</pre> 420</pre>
388 421
389</body> 422</body>
390</subsection> 423</subsection>
391</section> 424</section>
425
426<section id="sysinfo">
427<title>System Information</title>
392<section> 428<subsection>
429<title>Root Password</title>
430<body>
431
432<p>
433First we set the root password by typing:
434</p>
435
436<pre caption="Setting the root password">
437# <i>passwd</i>
438</pre>
439
440<p>
441If you want root to be able to log on through the serial console, add
442<c>tts/0</c> to <path>/etc/securetty</path>:
443</p>
444
445<pre caption="Adding tts/0 to /etc/securetty">
446# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
447</pre>
448
449</body>
450</subsection>
451<subsection>
393<title>System Information</title> 452<title>System Information</title>
394<body> 453<body>
395 454
396<p> 455<p>
397Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 456Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
401<pre caption="Opening /etc/rc.conf"> 460<pre caption="Opening /etc/rc.conf">
402# <i>nano -w /etc/rc.conf</i> 461# <i>nano -w /etc/rc.conf</i>
403</pre> 462</pre>
404 463
405<p> 464<p>
465When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
466</p>
467
468<p>
406As 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
407configuration variables. When you're finished configuring 470configuration variables. You can configure your system to use unicode and
408<path>/etc/rc.conf</path>, save and exit to continue. 471define your default editor and your display manager (like gdm or kdm).
472</p>
473
409</p> 474<p>
475Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
476Edit it to configure your keyboard.
477</p>
410 478
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'">
489Users of USB-based SPARC systems and SPARC clones might need to select an i386
490keymap (such as "us") instead of "sunkeymap".
491</note>
492
493<note test="substring(func:keyval('arch'),1,3)='PPC'">
494PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
495keymaps on boot have to enable ADB keycode sendings in their kernel and have to
496set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
497</note>
498
499<p>
500When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
501exit.
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>
521When you're finished configuring <path>/etc/conf.d/clock</path>, save and
522exit.
523</p>
524
525<p test="not(func:keyval('arch')='PPC64')">
526Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
527Tools</uri>.
528</p>
529
530</body>
531</subsection>
532<subsection test="func:keyval('arch')='PPC64'">
533<title>Configuring the Console</title>
411</body> 534<body>
535
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>
540
541<pre caption="Enabling hvc or hvsi support in /etc/inittab">
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>.
549</p>
550
551<p>
552You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
553System Tools</uri>.
554</p>
555
556</body>
557</subsection>
412</section> 558</section>
413</sections> 559</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20