/[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.130
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.130 2014/04/11 16:03:58 swift Exp $ -->
5 8
6<sections> 9<sections>
7<section>
8<title>Timezone</title>
9<body>
10 10
11<p> 11<abstract>
12You now need to select your timezone so that your system knows where it is 12You need to edit some important configuration files. In this chapter
13located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a 13you receive an overview of these files and an explanation on how to
14symlink to <path>/etc/localtime</path> using <c>ln</c>: 14proceed.
15</p> 15</abstract>
16 16
17<pre caption="Setting the timezone information"> 17<version>36</version>
18# <i>ls /usr/share/zoneinfo</i> 18<date>2014-04-11</date>
19<comment>(Suppose you want to use GMT:)</comment>
20# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
21</pre>
22 19
23</body>
24</section>
25<section> 20<section>
26<title>Filesystem Information</title> 21<title>Filesystem Information</title>
27<subsection> 22<subsection>
28<title>What is fstab?</title> 23<title>What is fstab?</title>
29<body> 24<body>
30 25
31<p> 26<p>
32Under Linux, all partitions used by the system must be listed in 27Under Linux, all partitions used by the system must be listed in
33<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
34(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
35(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
36etc.). 31them or not, etc.)
37</p> 32</p>
38 33
39</body> 34</body>
40</subsection> 35</subsection>
41<subsection> 36<subsection>
42<title>Creating /etc/fstab</title> 37<title>Creating /etc/fstab</title>
43<body> 38<body>
44 39
45<p> 40<p>
46<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six 41<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 42fields, separated by whitespace (space(s), tabs or a mixture). Each field has
48its own meaning: 43its own meaning:
49</p> 44</p>
50 45
51<ul> 46<ul>
52<li> 47<li>
53 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
54 file) 49 file)
55</li> 50</li>
56<li> 51<li>
57 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
58 mounted 53 mounted
59</li> 54</li>
60<li> 55<li>
61 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
62</li> 57</li>
63<li> 58<li>
64 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
65 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,
66 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
67 listing. Multiple mountoptions are comma-separated. 62 listing. Multiple mount options are comma-separated.
68</li> 63</li>
69<li> 64<li>
70 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
71 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).
72</li> 67</li>
73<li> 68<li>
74 The sixth field is used by <c>fsck</c> the order in which filesystems should 69 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 70 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 71 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
77 a filesystem check isn't necessary). 72 (or <c>0</c> if a filesystem check isn't necessary).
78</li> 73</li>
79</ul> 74</ul>
80 75
81<p> 76<impo>
82So 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
83<path>/etc/fstab</path>: 78fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
84</p> 79</impo>
85 80
86<pre caption="Opening /etc/fstab"> 81<pre caption="Opening /etc/fstab">
87# <i>nano -w /etc/fstab</i> 82# <i>nano -w /etc/fstab</i>
88</pre> 83</pre>
89 84
90<p> 85<p>
86In the remainder of the text, we use the default <path>/dev/sd*</path> block
87device files as partition. You can also opt to use the symbolic links in the
88<path>/dev/disk/byid</path> or <path>/dev/disk/by-uuid</path>. These names are
89not likely to change, whereas the default block device files naming depends on
90a number of factors (such as how and in what order the disks are attached to
91your system). However, if you do not intend to fiddle with the disk ordering,
92you can continue with the default block device files safely.
93</p>
94
95</body>
96<body test="func:keyval('/boot')">
97
98<p>
91Lets take a look at how we write down the options for the <path>/boot</path> 99Let 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 100partition. This is just an example, if you didn't or couldn't create a
93<path>/boot</path> partition, don't copy it verbatim. 101<path>/boot</path>, don't copy it.
94</p>
95
96<p> 102</p>
103
104<p>
97In our default x86 partitioning example <path>/boot</path> is the 105In 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 106usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
99be mounted automatically (<c>noauto</c>) but does need to be checked. So we 107filesystem. It needs to be checked during boot, so we would write down:
100would write down:
101</p> 108</p>
102 109
103<pre caption="An example /boot line for /etc/fstab"> 110<pre caption="An example /boot line for /etc/fstab">
104/dev/hda1 /boot ext2 noauto 1 2 111<keyval id="/boot"/> /boot ext2 defaults 0 2
105</pre> 112</pre>
106 113
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> 114<p>
112 115Some users don't want their <path>/boot</path> partition to be mounted
113<pre caption="An improved /boot line for /etc/fstab"> 116automatically to improve their system's security. Those people should
114/dev/hda1 /boot ext2 noauto,noatime 1 2 117substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
115</pre> 118manually mount this partition every time you want to use it.
116
117<p> 119</p>
118If we continue with this, we would end up with the following three lines (for 120
119<path>/boot</path>, <path>/</path> and the swap partition): 121</body>
122<body>
123
120</p> 124<p>
125Add the rules that match your partitioning scheme and append rules for
126your CD-ROM drive(s), and of course, if you have other partitions or drives,
127for those too.
128</p>
121 129
122<pre caption="Three /etc/fstab lines"> 130<p>
123/dev/hda1 /boot ext2 noauto,noatime 1 2 131Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
132</p>
133
134<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'">
135<keyval id="/boot"/> /boot ext2 defaults,noatime 0 2
136/dev/sda3 none swap sw 0 0
137/dev/sda4 / ext4 noatime 0 1
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')='Alpha' or func:keyval('arch')='MIPS'">
143<keyval id="/boot"/> /boot ext2 defaults,noatime 0 2
124/dev/hda2 none swap sw 0 0 144/dev/sda2 none swap sw 0 0
125/dev/hda3 / ext3 noatime 0 1 145/dev/sda3 / ext4 noatime 0 1
126</pre>
127 146
128<p> 147/dev/cdrom /mnt/cdrom auto noauto,user 0 0
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> 148</pre>
133 149
134<pre caption="A full /etc/fstab example"> 150<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
135/dev/hda1 /boot ext2 noauto,noatime 1 2 151/dev/sda1 / ext4 noatime 0 1
152/dev/sda2 none swap sw 0 0
153/dev/sda4 /usr ext4 noatime 0 2
154/dev/sda5 /var ext4 noatime 0 2
155/dev/sda6 /home ext4 noatime 0 2
156
157<comment># You must add the rules for openprom</comment>
158openprom /proc/openprom openpromfs defaults 0 0
159
160/dev/cdrom /mnt/cdrom auto noauto,user 0 0
161</pre>
162
163<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or
164func:keyval('arch')='PPC64'">
165/dev/sda4 / ext4 noatime 0 1
136/dev/hda2 none swap sw 0 0 166/dev/sda3 none swap sw 0 0
137/dev/hda3 / ext3 noatime 0 1
138 167
139none /proc proc defaults 0 0
140none /dev/shm tmpfs defaults 0 0
141
142/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 168/dev/cdrom /mnt/cdrom auto noauto,user 0 0
143</pre> 169</pre>
144 170
145<p> 171<p>
146<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 172<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 173removable 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. 174<c>user</c> makes it possible for non-root users to mount the CD.
149</p> 175</p>
150 176
151<p> 177<p>
152Now use the above example to create your <path>/etc/fstab</path>. If you are a 178To 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> 179mount option, which results in a faster system since access times
154too: 180aren't registered (you don't need those generally anyway). This is also
155</p> 181recommended for solid state drive (SSD) users, who should also enable
156 182the <c>discard</c> mount option (ext4 and btrfs only for now) which
157<pre caption="Adding openprom filesystem to /etc/fstab"> 183makes the TRIM command work.
158none /proc/openprom openpromfs defaults 0 0
159</pre>
160
161<p> 184</p>
162If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>: 185
163</p> 186<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. 187Double-check your <path>/etc/fstab</path>, save and quit to continue.
171</p> 188</p>
172 189
173</body> 190</body>
174</subsection> 191</subsection>
175</section> 192</section>
176<section> 193<section>
177<title>Networking Information</title> 194<title>Networking Information</title>
178<subsection> 195<subsection>
179<title>Hostname, Domainname etc.</title> 196<title>Host name, Domainname, etc</title>
180<body> 197<body>
181 198
182<p> 199<p>
183One of the choices the user has to make is name his PC. This seems to be quite 200One 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 201quite 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 202appropriate 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 203choose can be changed afterwards. For all we care, you can just call your system
187<c>tux</c> and domain <c>homenetwork</c>. 204<c>tux</c> and domain <c>homenetwork</c>.
188</p> 205</p>
189 206
190<p>
191We use these values in the next examples. First we set the hostname:
192</p>
193
194<pre caption="Setting the hostname"> 207<pre caption="Setting the host name">
195# <i>echo tux &gt; /etc/hostname</i> 208# <i>nano -w /etc/conf.d/hostname</i>
196</pre>
197 209
198<p> 210<comment>(Set the hostname variable to your host name)</comment>
199Second we set the domainname: 211hostname="<i>tux</i>"
212</pre>
213
200</p> 214<p>
215Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
216You only need a domain if your ISP or network administrator says so, or if you
217have a DNS server but not a DHCP server. You don't need to worry about DNS or
218domainnames if your networking is setup for DHCP.
219</p>
220
221<note>
222The <path>/etc/conf.d/net</path> file does not exist by default, so you might
223need to create it.
224</note>
201 225
202<pre caption="Setting the domainname"> 226<pre caption="Setting the domainname">
203# <i>echo homenetwork &gt; /etc/dnsdomainname</i> 227# <i>nano -w /etc/conf.d/net</i>
228
229<comment>(Set the dns_domain variable to your domain name)</comment>
230dns_domain_lo="<i>homenetwork</i>"
204</pre> 231</pre>
232
233<note>
234If you choose not to set a domainname, you can get rid of the "This is
235hostname.(none)" messages at your login screen by editing
236<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
237</note>
205 238
206<p> 239<p>
207If you have a NIS domain (if you don't know what that is, then you don't have 240If 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: 241one), you need to define that one too:
209</p> 242</p>
210 243
211<pre caption="Setting the NIS domainname"> 244<pre caption="Setting the NIS domainname">
212# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 245# <i>nano -w /etc/conf.d/net</i>
213</pre>
214 246
215<p> 247<comment>(Set the nis_domain variable to your NIS domain name)</comment>
216Now add the <c>domainname</c> script to the default runlevel: 248nis_domain_lo="<i>my-nisdomain</i>"
217</p> 249</pre>
218 250
219<pre caption="Adding domainname to the default runlevel"> 251<note>
220# <i>rc-update add domainname default</i> 252For more information on configuring DNS and NIS, please read the examples
221</pre> 253provided in <path>/usr/share/doc/netifrc-*/net.example.bz2</path> which
254can be read using <c>bzless</c>. Also, you may want to emerge <c>openresolv</c>
255to help manage your DNS/NIS setup.
256</note>
222 257
223</body> 258</body>
224</subsection> 259</subsection>
225<subsection> 260<subsection>
226<title>Configuring your Network</title> 261<title>Configuring your Network</title>
227<body> 262<body>
228 263
229<p> 264<p>
230Before you get that "Hey, we've had that already"-feeling, you should remember 265Before 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 266that 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 267just for the installation. Right now you are going to configure networking for
233your Gentoo system permanently. 268your Gentoo system permanently.
234</p> 269</p>
235 270
271<note>
272More detailed information about networking, including advanced topics like
273bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
274link="?part=4">Gentoo Network Configuration</uri> section.
275</note>
276
236<p> 277<p>
237All networking information is gathered in <path>/etc/conf.d/net</path>. It uses 278All 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 279a straightforward yet not intuitive syntax if you don't know how to set up
239networking manually. But don't fear, we'll explain everything :) 280networking manually. But don't fear, we'll explain everything. A fully
240</p> 281commented example that covers many different configurations is available in
241 282<path>/usr/share/doc/netifrc-*/net.example.bz2</path>.
242<p> 283</p>
284
285<p>
286Let's first install <c>netifrc</c>:
287</p>
288
289<pre caption="Installing netifrc">
290# <i>emerge --noreplace netifrc</i>
291</pre>
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
243First 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
244is used in this example): 304this example):
245</p> 305</p>
246 306
247<pre caption="Opening /etc/conf.d/net for editing"> 307<pre caption="Opening /etc/conf.d/net for editing">
248# <i>nano -w /etc/conf.d/net</i> 308# <i>nano -w /etc/conf.d/net</i>
249</pre> 309</pre>
250 310
251<p> 311<p>
252The first variable you'll find is <c>iface_eth0</c>. It uses the following 312To enter your own IP address, netmask and gateway, you need
253syntax: 313to set both <c>config_eth0</c> and <c>routes_eth0</c>:
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> 314</p>
261If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 315
262to <c>dhcp</c>. However, if you need to setup your network manually and you're 316<note>
263not familiar with all the above terms, please read the section on <uri 317This assumes that your network interface will be called eth0. This is, however,
264link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 318very system dependent. It is recommended to assume that the interface is named
265Terminology</uri> if you haven't done so already. 319the same as the interface name when booted from the installation media <e>if</e>
320the installation media is sufficiently recent. More information can be found in
321<uri link="?part=4&amp;chap=2#doc_chap4">Network Interface Naming</uri>.
322</note>
323
324<pre caption="Manually setting IP information for eth0">
325config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255"
326routes_eth0="default via 192.168.0.1"
327</pre>
328
266</p> 329<p>
267 330To use DHCP, define <c>config_eth0</c>:
268<p> 331</p>
269So lets give two examples; the first one uses DHCP, the second one a static IP 332
270(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 333<pre caption="Automatically obtaining an IP address for eth0">
271192.168.0.1: 334config_eth0="dhcp"
335</pre>
336
272</p> 337<p>
273 338Please read <path>/usr/share/doc/netifrc-*/net.example.bz2</path> for a
274<pre caption="Examples for /etc/conf.d/net"> 339list of all available options. Be sure to also read your DHCP client manpage if
275<comment>(For DHCP:)</comment> 340you need to set specific DHCP options.
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> 341</p>
284If you have several network interfaces, create extra <c>iface_eth</c> variables, 342
285like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 343<p>
286shouldn't be reproduced as you can only set one gateway per computer. 344If you have several network interfaces repeat the above steps for
345<c>config_eth1</c>, <c>config_eth2</c>, etc.
287</p> 346</p>
288 347
289<p> 348<p>
290Now save the configuration and exit to continue. 349Now save the configuration and exit to continue.
291</p> 350</p>
295<subsection> 354<subsection>
296<title>Automatically Start Networking at Boot</title> 355<title>Automatically Start Networking at Boot</title>
297<body> 356<body>
298 357
299<p> 358<p>
300To have your network interfaces activated at boot, you need to add those to the 359To 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 360default runlevel.
302the PCMCIA interfaces are started by the PCMCIA init script.
303</p> 361</p>
304 362
305<pre caption="Adding net.eth0 to the default runlevel"> 363<pre caption="Adding net.eth0 to the default runlevel">
364# <i>cd /etc/init.d</i>
365# <i>ln -s net.lo net.eth0</i>
306# <i>rc-update add net.eth0 default</i> 366# <i>rc-update add net.eth0 default</i>
307</pre> 367</pre>
308 368
309<p> 369<p>
310If you have several network interfaces, you need to create the appropriate 370If you have several network interfaces, you need to create the appropriate
311<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can 371<path>net.*</path> files just like you did with <path>net.eth0</path>.
312use <c>ln</c> to do this: 372</p>
373
313</p> 374<p>
314 375If you later find out the assumption about the network interface name (which we
315<pre caption="Creating extra initscripts"> 376currently document as eth0) was wrong, then
316# <i>cd /etc/init.d</i>
317# <i>ln -s net.eth0 net.eth1</i>
318# <i>rc-update add net.eth1 default</i>
319</pre> 377</p>
378
379<ol>
380<li>
381update the <path>/etc/conf.d/net</path> file with the correct interface name (like enp3s0
382instead of eth0),
383</li>
384<li>
385create new symbolic link (like <path>/etc/init.d/net.enp3s0</path>),
386</li>
387<li>
388remove the old symbolic link (<c>rm /etc/init.d/net.eth0</c>),
389</li>
390<li>
391add the new one to the default runlevel, and
392</li>
393<li>
394remove the old one using <c>rc-update del net.eth0 default</c>.
395</li>
396</ol>
320 397
321</body> 398</body>
322</subsection> 399</subsection>
323<subsection> 400<subsection>
324<title>Writing Down Network Information</title> 401<title>Writing Down Network Information</title>
325<body> 402<body>
326 403
327<p> 404<p>
328You now need to inform Linux about your network. This is defined in 405You 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 406<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 407hosts 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), 408You 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 409set up your own internal DNS system.
333open <path>/etc/hosts</path> and fill in the values:
334</p> 410</p>
335 411
336<pre caption="Opening /etc/hosts"> 412<pre caption="Opening /etc/hosts">
337# <i>nano -w /etc/hosts</i> 413# <i>nano -w /etc/hosts</i>
338</pre> 414</pre>
339 415
340<pre caption="Filling in the networking information"> 416<pre caption="Filling in the networking information">
341127.0.0.1 localhost 417<comment>(This defines the current system)</comment>
342192.168.0.5 jenny 418127.0.0.1 tux.homenetwork tux localhost
343192.168.0.6 benny
344192.168.0.7 tux
345</pre>
346 419
347<p> 420<comment>(Define extra systems on your network,
348If your system is the only system (or the nameservers handle all name 421they need to have a static IP to be defined this way.)</comment>
349resolution) a single line is sufficient: 422192.168.0.5 jenny.homenetwork jenny
350</p> 423192.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> 424</pre>
355 425
356<p> 426<p>
357Save and exit the editor to continue. 427Save and exit the editor to continue.
358</p> 428</p>
359 429
360<p> 430<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 431If you don't have PCMCIA, you can now continue with <uri
362link="#doc_chap4">System Information</uri>. PCMCIA-users should read the 432link="#sysinfo">System Information</uri>. PCMCIA-users should read the
363following topic on PCMCIA. 433following topic on PCMCIA.
364</p> 434</p>
365 435
366</body> 436</body>
367</subsection> 437</subsection>
368<subsection> 438<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> 439<title>Optional: Get PCMCIA Working</title>
370<body> 440<body>
371 441
372<p> 442<p>
373PCMCIA-users should first install the <c>pcmcia-cs</c> package: 443PCMCIA users should first install the <c>pcmciautils</c> package.
374</p> 444</p>
375 445
376<pre caption="Installing pcmcia-cs"> 446<pre caption="Installing pcmciautils">
377# <i>emerge --usepkg pcmcia-cs</i> 447# <i>emerge pcmciautils</i>
378</pre>
379
380<p>
381When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>
382runlevel:
383</p>
384
385<pre caption="Adding pcmcia to the boot runlevel">
386# <i>rc-update add pcmcia boot</i>
387</pre> 448</pre>
388 449
389</body> 450</body>
390</subsection> 451</subsection>
391</section> 452</section>
392<section> 453
454<section id="sysinfo">
393<title>System Information</title> 455<title>System Information</title>
456<subsection>
457<title>Root Password</title>
458<body>
459
460<p>
461First we set the root password by typing:
462</p>
463
464<pre caption="Setting the root password">
465# <i>passwd</i>
466</pre>
467
394<body> 468</body>
469</subsection>
470<subsection>
471<title>System Information</title>
472<body>
395 473
396<p>
397Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
398Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
399</p> 474<p>
475Gentoo uses <path>/etc/rc.conf</path> to configure the services, startup,
476and shutdown of your system. Open up <path>/etc/rc.conf</path> and enjoy all
477the comments in the file.
478</p>
400 479
401<pre caption="Opening /etc/rc.conf"> 480<pre caption="Configuring services">
402# <i>nano -w /etc/rc.conf</i> 481# <i>nano -w /etc/rc.conf</i>
403</pre> 482</pre>
404 483
405<p> 484<p>
406As you can see, this file is well commented to help you set up the necessary 485When you're finished configuring these two files, save them and exit.
407configuration variables. When you're finished configuring 486</p>
408<path>/etc/rc.conf</path>, save and exit to continue. 487
409</p> 488<p>
489Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
490Edit it to configure your keyboard.
491</p>
410 492
493<pre caption="Opening /etc/conf.d/keymaps">
494# <i>nano -w /etc/conf.d/keymaps</i>
495</pre>
496
497<p>
498Take special care with the <c>keymap</c> variable. If you select the wrong
499<c>keymap</c>, you will get weird results when typing on your keyboard.
500</p>
501
502<note test="substring(func:keyval('arch'),1,3)='PPC'">
503PPC uses x86 keymaps on most systems.
504</note>
505
506<p>
507When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
508exit.
509</p>
510
511<p>
512Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
513according to your needs.
514</p>
515
516<pre caption="Opening /etc/conf.d/hwclock">
517# <i>nano -w /etc/conf.d/hwclock</i>
518</pre>
519
520<p>
521If your hardware clock is not using UTC, you need to add <c>clock="local"</c>
522to the file. Otherwise you will notice some clock skew.
523</p>
524
525<p>
526When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and
527exit.
528</p>
529
530</body>
531</subsection>
532
533<subsection test="func:keyval('arch')='PPC64'">
534<title>Configuring the Console</title>
411</body> 535<body>
536
537<p>
538If you are using a virtual console, you must uncomment the appropriate line in
539<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
540</p>
541
542<pre caption="Enabling hvc or hvsi support in /etc/inittab">
543hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
544hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
545</pre>
546
547<p>
548You should also take this time to verify that the appropriate console is
549listed in <path>/etc/securetty</path>.
550</p>
551
552<p>
553You may now continue with <uri link="?part=1&amp;chap=9">Installing Necessary
554System Tools</uri>.
555</p>
556
557</body>
558</subsection>
412</section> 559</section>
413</sections> 560</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20