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

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.87

  ViewVC Help
Powered by ViewVC 1.1.20