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

Legend:
Removed from v.1.39  
changed lines
  Added in v.1.84

  ViewVC Help
Powered by ViewVC 1.1.20