/[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.17 Revision 1.85
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.17 2004/01/06 10:08:38 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.85 2006/10/21 01:13:51 nightmorph Exp $ -->
5 8
6<sections> 9<sections>
7<section>
8<title>Timezone</title>
9<body>
10 10
11<p> 11<version>7.4</version>
12You now need to select your timezone so that your system knows where it is 12<date>2006-10-20</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>
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> to determine the order in which 63 The sixth field is used by <c>fsck</c> to determine the order in which
75 filesystems should be <b>check</b>ed if the system wasn't shut down properly. 64 filesystems should be <b>check</b>ed if the system wasn't shut down properly.
76 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>
77 (or <c>0</c> in case 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>
91Let 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>
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, Domainname, etc</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
239<comment>(Set the HOSTNAME variable to your host name)</comment>
240HOSTNAME="<i>tux</i>"
241</pre>
242
198<p> 243<p>
199Second we set the domainname: 244Second we set the domainname in <path>/etc/conf.d/net</path>:
200</p> 245</p>
201 246
202<pre caption="Setting the domainname"> 247<pre caption="Setting the domainname">
203# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 248# <i>nano -w /etc/conf.d/net</i>
249
250<comment>(Set the dns_domain variable to your domain name)</comment>
251dns_domain_lo="<i>homenetwork</i>"
204</pre> 252</pre>
205 253
206<p> 254<p>
207If you have a NIS domain (if you don't know what that is, then you don't have 255If 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: 256one), you need to define that one too:
209</p> 257</p>
210 258
211<pre caption="Setting the NIS domainname"> 259<pre caption="Setting the NIS domainname">
212# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 260# <i>nano -w /etc/conf.d/net</i>
213</pre>
214 261
215<p> 262<comment>(Set the nis_domain variable to your NIS domain name)</comment>
216Now add the <c>domainname</c> script to the default runlevel: 263nis_domain_lo="<i>my-nisdomain</i>"
217</p> 264</pre>
218 265
219<pre caption="Adding domainname to the default runlevel"> 266<note>
220# <i>rc-update add domainname default</i> 267For more information on configuring DNS and NIS, please read the examples
221</pre> 268provided in <path>/etc/conf.d/net.example</path>.
269</note>
222 270
223</body> 271</body>
224</subsection> 272</subsection>
225<subsection> 273<subsection>
226<title>Configuring your Network</title> 274<title>Configuring your Network</title>
227<body> 275<body>
228 276
229<p> 277<p>
230Before you get that "Hey, we've had that already"-feeling, you should remember 278Before 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 279that 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 280just for the installation. Right now you are going to configure networking for
233your Gentoo system permanently. 281your Gentoo system permanently.
234</p> 282</p>
235 283
284<note>
285More detailed information about networking, including advanced topics like
286bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
287link="?part=4">Gentoo Network Configuration</uri> section.
288</note>
289
236<p> 290<p>
237All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 291All 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 292a straightforward yet not intuitive syntax if you don't know how to set up
239networking manually. But don't fear, we'll explain everything :) 293networking manually. But don't fear, we'll explain everything. A fully
240</p> 294commented example that covers many different configurations is available in
241 295<path>/etc/conf.d/net.example</path>.
242<p> 296</p>
297
298<p>
299DHCP is used by default. For DHCP to work, you will need to install a DHCP
300client. This is described later in <uri
301link="?part=1&amp;chap=9#networking-tools">Installing Necessary System
302Tools</uri>. Do not forget to install a DHCP client.
303</p>
304
305<p>
306If you need to configure your network connection either because you need
307specific 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> 308<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
244is used in this example): 309this example):
245</p> 310</p>
246 311
247<pre caption="Opening /etc/conf.d/net for editing"> 312<pre caption="Opening /etc/conf.d/net for editing">
248# <i>nano -w /etc/conf.d/net</i> 313# <i>nano -w /etc/conf.d/net</i>
249</pre> 314</pre>
250 315
251<p> 316<p>
252The first variable you'll find is <c>iface_eth0</c>. It uses the following 317You 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> 318</p>
261If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 319
262to <c>dhcp</c>. However, if you need to setup your network manually and you're 320<pre caption="Default /etc/conf.d/net">
263not familiar with all the above terms, please read the section on <uri 321# This blank configuration will automatically use DHCP for any net.*
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 322# scripts in /etc/init.d. To create a more complete configuration,
265Terminology</uri> if you haven't done so already. 323# please review /etc/conf.d/net.example and save your configuration
324# in /etc/conf.d/net (this file :]!).
325</pre>
326
266</p> 327<p>
267 328To enter your own IP address, netmask and gateway, you need
329to set both <c>config_eth0</c> and <c>routes_eth0</c>:
268<p> 330</p>
269So let us give two examples; the first one uses DHCP, the second one a static IP 331
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 332<pre caption="Manually setting IP information for eth0">
271192.168.0.1: 333config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
334routes_eth0=( "default gw 192.168.0.1" )
335</pre>
336
272</p> 337<p>
273 338To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
274<pre caption="Examples for /etc/conf.d/net"> 339<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> 340</p>
284If you have several network interfaces, create extra <c>iface_eth</c> variables, 341
285like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 342<pre caption="Automatically obtaining an IP address for eth0">
286shouldn't be reproduced as you can only set one gateway per computer. 343config_eth0=( "dhcp" )
344dhcp_eth0="nodns nontp nonis"
345</pre>
346
347<p>
348Please read <path>/etc/conf.d/net.example</path> for a list of all available
349options.
350</p>
351
352<p>
353If you have several network interfaces repeat the above steps for
354<c>config_eth1</c>, <c>config_eth2</c>, etc.
287</p> 355</p>
288 356
289<p> 357<p>
290Now save the configuration and exit to continue. 358Now save the configuration and exit to continue.
291</p> 359</p>
295<subsection> 363<subsection>
296<title>Automatically Start Networking at Boot</title> 364<title>Automatically Start Networking at Boot</title>
297<body> 365<body>
298 366
299<p> 367<p>
300To have your network interfaces activated at boot, you need to add those to the 368To 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 369default runlevel. If you have PCMCIA interfaces you should skip this action as
302the PCMCIA interfaces are started by the PCMCIA init script. 370the PCMCIA interfaces are started by the PCMCIA init script.
303</p> 371</p>
304 372
305<pre caption="Adding net.eth0 to the default runlevel"> 373<pre caption="Adding net.eth0 to the default runlevel">
312use <c>ln</c> to do this: 380use <c>ln</c> to do this:
313</p> 381</p>
314 382
315<pre caption="Creating extra initscripts"> 383<pre caption="Creating extra initscripts">
316# <i>cd /etc/init.d</i> 384# <i>cd /etc/init.d</i>
317# <i>ln -s net.eth0 net.eth1</i> 385# <i>ln -s net.lo net.eth1</i>
318# <i>rc-update add net.eth1 default</i> 386# <i>rc-update add net.eth1 default</i>
319</pre> 387</pre>
320 388
321</body> 389</body>
322</subsection> 390</subsection>
324<title>Writing Down Network Information</title> 392<title>Writing Down Network Information</title>
325<body> 393<body>
326 394
327<p> 395<p>
328You now need to inform Linux about your network. This is defined in 396You 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 397<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 398hosts 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), 399You 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 400set up your own internal DNS system.
333open <path>/etc/hosts</path> and fill in the values:
334</p> 401</p>
335 402
336<pre caption="Opening /etc/hosts"> 403<pre caption="Opening /etc/hosts">
337# <i>nano -w /etc/hosts</i> 404# <i>nano -w /etc/hosts</i>
338</pre> 405</pre>
339 406
340<pre caption="Filling in the networking information"> 407<pre caption="Filling in the networking information">
341127.0.0.1 localhost 408<comment>(This defines the current system)</comment>
342192.168.0.5 jenny 409127.0.0.1 tux.homenetwork tux localhost
343192.168.0.6 benny
344192.168.0.7 tux
345</pre>
346 410
347<p> 411<comment>(Define extra systems on your network,
348If your system is the only system (or the nameservers handle all name 412they need to have a static IP to be defined this way.)</comment>
349resolution) a single line is sufficient: 413192.168.0.5 jenny.homenetwork jenny
350</p> 414192.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> 415</pre>
355 416
356<p> 417<p>
357Save and exit the editor to continue. 418Save and exit the editor to continue.
358</p> 419</p>
359 420
360<p> 421<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 422If you don't have PCMCIA, you can now continue with <uri
362link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 423link="#sysinfo">System Information</uri>. PCMCIA-users should read the
363following topic on PCMCIA. 424following topic on PCMCIA.
364</p> 425</p>
365 426
366</body> 427</body>
367</subsection> 428</subsection>
368<subsection> 429<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> 430<title>Optional: Get PCMCIA Working</title>
370<body> 431<body>
371 432
372<p> 433<p>
373PCMCIA-users should first install the <c>pcmcia-cs</c> package: 434PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
435includes users who will be working with a 2.6 kernel (even though they won't be
436using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
437to avoid installing xorg-x11 at this moment:
374</p> 438</p>
375 439
376<pre caption="Installing pcmcia-cs"> 440<pre caption="Installing pcmcia-cs">
377# <i>emerge --usepkg pcmcia-cs</i> 441# <i>USE="-X" emerge pcmcia-cs</i>
378</pre> 442</pre>
379 443
380<p> 444<p>
381When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e> 445When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
382runlevel: 446runlevel:
383</p> 447</p>
384 448
385<pre caption="Adding pcmcia to the boot runlevel"> 449<pre caption="Adding pcmcia to the default runlevel">
386# <i>rc-update add pcmcia boot</i> 450# <i>rc-update add pcmcia default</i>
387</pre> 451</pre>
388 452
389</body> 453</body>
390</subsection> 454</subsection>
391</section> 455</section>
456
457<section id="sysinfo">
458<title>System Information</title>
392<section> 459<subsection>
460<title>Root Password</title>
461<body>
462
463<p>
464First we set the root password by typing:
465</p>
466
467<pre caption="Setting the root password">
468# <i>passwd</i>
469</pre>
470
471<p>
472If you want root to be able to log on through the serial console, add
473<c>tts/0</c> to <path>/etc/securetty</path>:
474</p>
475
476<pre caption="Adding tts/0 to /etc/securetty">
477# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
478</pre>
479
480</body>
481</subsection>
482<subsection>
393<title>System Information</title> 483<title>System Information</title>
394<body> 484<body>
395 485
396<p> 486<p>
397Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. 487Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
401<pre caption="Opening /etc/rc.conf"> 491<pre caption="Opening /etc/rc.conf">
402# <i>nano -w /etc/rc.conf</i> 492# <i>nano -w /etc/rc.conf</i>
403</pre> 493</pre>
404 494
405<p> 495<p>
496When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
497</p>
498
499<p>
406As you can see, this file is well commented to help you set up the necessary 500As you can see, this file is well commented to help you set up the necessary
407configuration variables. Take special care with the <c>KEYMAP</c> setting: if 501configuration variables. You can configure your system to use unicode and
408you select the wrong <c>KEYMAP</c> you will get weird results when typing on 502define your default editor and your display manager (like gdm or kdm).
409your keyboard. 503</p>
504
410</p> 505<p>
506Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
507Edit it to configure your keyboard.
508</p>
411 509
412<note> 510<pre caption="Opening /etc/conf.d/keymaps">
511# <i>nano -w /etc/conf.d/keymaps</i>
512</pre>
513
514<p>
515Take special care with the <c>KEYMAP</c> variable. If you select the wrong
516<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
517</p>
518
519<note test="func:keyval('arch')='SPARC'">
413Users of USB-based SPARC systems and SPARC clones might need to select an i386 520Users of USB-based SPARC systems and SPARC clones might need to select an i386
414keymap (such as "us") instead of "sunkeymap". 521keymap (such as "us") instead of "sunkeymap".
415</note> 522</note>
416 523
417<p> 524<note test="substring(func:keyval('arch'),1,3)='PPC'">
418When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 525PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
419continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 526keymaps on boot have to enable ADB keycode sendings in their kernel and have to
527set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
528</note>
529
420</p> 530<p>
531When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
532exit.
533</p>
421 534
535<p>
536Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
537according to your needs.
538</p>
539
540<pre caption="Opening /etc/conf.d/clock">
541# <i>nano -w /etc/conf.d/clock</i>
542</pre>
543
544<p>
545If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
546to the file. Otherwise you will notice some clock skew.
547</p>
548
549<p>
550When you're finished configuring <path>/etc/conf.d/clock</path>, save and
551exit.
552</p>
553
554<p test="not(func:keyval('arch')='PPC64')">
555Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
556Tools</uri>.
557</p>
558
559</body>
560</subsection>
561<subsection test="func:keyval('arch')='PPC64'">
562<title>Configuring the Console</title>
422</body> 563<body>
564
565<p>
566If you are using a virtual console, you must uncomment the appropriate line in
567<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
568</p>
569
570<pre caption="Enabling hvc or hvsi support in /etc/inittab">
571hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
572hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
573</pre>
574
575<p>
576You should also take this time to verify that the appropriate console is
577listed in <path>/etc/securetty</path>.
578</p>
579
580<p>
581You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
582System Tools</uri>.
583</p>
584
585</body>
586</subsection>
423</section> 587</section>
424</sections> 588</sections>

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.85

  ViewVC Help
Powered by ViewVC 1.1.20