/[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.22 Revision 1.130
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.22 2004/02/07 18:24:26 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 $ -->
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>36</version>
18<date>2014-04-11</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
75<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>
76Let us 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>
77partition. 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
78<path>/boot</path> partition, don't copy it verbatim. 101<path>/boot</path>, don't copy it.
79</p>
80
81<p> 102</p>
103
104<p>
82In our default x86 partitioning example <path>/boot</path> is the 105In 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 106usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
84be 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:
85would write down:
86</p> 108</p>
87 109
88<pre caption="An example /boot line for /etc/fstab"> 110<pre caption="An example /boot line for /etc/fstab">
89/dev/hda1 /boot ext2 noauto 1 2 111<keyval id="/boot"/> /boot ext2 defaults 0 2
90</pre> 112</pre>
91 113
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> 114<p>
97 115Some users don't want their <path>/boot</path> partition to be mounted
98<pre caption="An improved /boot line for /etc/fstab"> 116automatically to improve their system's security. Those people should
99/dev/hda1 /boot ext2 noauto,noatime 1 2 117substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
100</pre> 118manually mount this partition every time you want to use it.
101
102<p> 119</p>
103If we continue with this, we would end up with the following three lines (for 120
104<path>/boot</path>, <path>/</path> and the swap partition): 121</body>
122<body>
123
105</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>
106 129
107<pre caption="Three /etc/fstab lines"> 130<p>
108/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
109/dev/hda2 none swap sw 0 0 144/dev/sda2 none swap sw 0 0
110/dev/hda3 / ext3 noatime 0 1 145/dev/sda3 / ext4 noatime 0 1
111</pre>
112 146
113<p> 147/dev/cdrom /mnt/cdrom auto noauto,user 0 0
114To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
115(required) and for your CD-ROM drive (and of course, if you have other
116partitions or drives, for those too):
117</p> 148</pre>
118 149
119<pre caption="A full /etc/fstab example"> 150<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
120/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
121/dev/hda2 none swap sw 0 0 166/dev/sda3 none swap sw 0 0
122/dev/hda3 / ext3 noatime 0 1
123 167
124none /proc proc defaults 0 0
125none /dev/shm tmpfs defaults 0 0
126
127/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 168/dev/cdrom /mnt/cdrom auto noauto,user 0 0
128</pre> 169</pre>
129 170
130<p> 171<p>
131<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
132removable 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
133<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.
134</p> 175</p>
135 176
136<p> 177<p>
137Now 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>
138SPARC-user, you should add the following line to your <path>/etc/fstab</path> 179mount option, which results in a faster system since access times
139too: 180aren't registered (you don't need those generally anyway). This is also
140</p> 181recommended for solid state drive (SSD) users, who should also enable
141 182the <c>discard</c> mount option (ext4 and btrfs only for now) which
142<pre caption="Adding openprom filesystem to /etc/fstab"> 183makes the TRIM command work.
143none /proc/openprom openpromfs defaults 0 0
144</pre>
145
146<p> 184</p>
147If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>: 185
148</p> 186<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. 187Double-check your <path>/etc/fstab</path>, save and quit to continue.
156</p> 188</p>
157 189
158</body> 190</body>
159</subsection> 191</subsection>
160</section> 192</section>
161<section> 193<section>
162<title>Networking Information</title> 194<title>Networking Information</title>
163<subsection> 195<subsection>
164<title>Hostname, Domainname etc.</title> 196<title>Host name, Domainname, etc</title>
165<body> 197<body>
166 198
167<p> 199<p>
168One 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
169easy, 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
170name 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
171be 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
172<c>tux</c> and domain <c>homenetwork</c>. 204<c>tux</c> and domain <c>homenetwork</c>.
173</p> 205</p>
174 206
175<p>
176We use these values in the next examples. First we set the hostname:
177</p>
178
179<pre caption="Setting the hostname"> 207<pre caption="Setting the host name">
180# <i>echo tux &gt; /etc/hostname</i> 208# <i>nano -w /etc/conf.d/hostname</i>
181</pre>
182 209
183<p> 210<comment>(Set the hostname variable to your host name)</comment>
184Second we set the domainname: 211hostname="<i>tux</i>"
212</pre>
213
185</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>
186 225
187<pre caption="Setting the domainname"> 226<pre caption="Setting the domainname">
188# <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>"
189</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>
190 238
191<p> 239<p>
192If 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
193one), you need to define that one too: 241one), you need to define that one too:
194</p> 242</p>
195 243
196<pre caption="Setting the NIS domainname"> 244<pre caption="Setting the NIS domainname">
197# <i>echo nis.homenetwork &gt; /etc/nisdomainname</i> 245# <i>nano -w /etc/conf.d/net</i>
198</pre>
199 246
200<p> 247<comment>(Set the nis_domain variable to your NIS domain name)</comment>
201Now add the <c>domainname</c> script to the default runlevel: 248nis_domain_lo="<i>my-nisdomain</i>"
202</p> 249</pre>
203 250
204<pre caption="Adding domainname to the default runlevel"> 251<note>
205# <i>rc-update add domainname default</i> 252For more information on configuring DNS and NIS, please read the examples
206</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>
207 257
208</body> 258</body>
209</subsection> 259</subsection>
210<subsection> 260<subsection>
211<title>Configuring your Network</title> 261<title>Configuring your Network</title>
212<body> 262<body>
213 263
214<p> 264<p>
215Before 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
216that 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
217just 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
218your Gentoo system permanently. 268your Gentoo system permanently.
219</p> 269</p>
220 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
221<p> 277<p>
222All 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
223a 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
224networking manually. But don't fear, we'll explain everything :) 280networking manually. But don't fear, we'll explain everything. A fully
225</p> 281commented example that covers many different configurations is available in
226 282<path>/usr/share/doc/netifrc-*/net.example.bz2</path>.
227<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
228First 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
229is used in this example): 304this example):
230</p> 305</p>
231 306
232<pre caption="Opening /etc/conf.d/net for editing"> 307<pre caption="Opening /etc/conf.d/net for editing">
233# <i>nano -w /etc/conf.d/net</i> 308# <i>nano -w /etc/conf.d/net</i>
234</pre> 309</pre>
235 310
236<p> 311<p>
237The 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
238syntax: 313to set both <c>config_eth0</c> and <c>routes_eth0</c>:
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> 314</p>
246If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 315
247to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>. 316<note>
248If you need to setup your network manually and you're 317This assumes that your network interface will be called eth0. This is, however,
249not familiar with all the above terms, please read the section on <uri 318very system dependent. It is recommended to assume that the interface is named
250link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 319the same as the interface name when booted from the installation media <e>if</e>
251Terminology</uri> if you haven't done so already. 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
252</p> 329<p>
253 330To use DHCP, define <c>config_eth0</c>:
254<p> 331</p>
255So let us give two examples; the first one uses DHCP, the second one a static IP 332
256(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">
257192.168.0.1: 334config_eth0="dhcp"
335</pre>
336
258</p> 337<p>
259 338Please read <path>/usr/share/doc/netifrc-*/net.example.bz2</path> for a
260<pre caption="Examples for /etc/conf.d/net"> 339list of all available options. Be sure to also read your DHCP client manpage if
261<comment>(For DHCP:)</comment> 340you need to set specific DHCP options.
262iface_eth0="dhcp"
263
264<comment>(For static IP:)</comment>
265iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
266gateway="eth0/192.168.0.1"
267</pre>
268
269<p> 341</p>
270If you have several network interfaces, create extra <c>iface_eth</c> variables, 342
271like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 343<p>
272shouldn'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.
273</p> 346</p>
274 347
275<p> 348<p>
276Now save the configuration and exit to continue. 349Now save the configuration and exit to continue.
277</p> 350</p>
281<subsection> 354<subsection>
282<title>Automatically Start Networking at Boot</title> 355<title>Automatically Start Networking at Boot</title>
283<body> 356<body>
284 357
285<p> 358<p>
286To 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
287default runlevel. If you have PCMCIA interfaces you should skip this action as 360default runlevel.
288the PCMCIA interfaces are started by the PCMCIA init script.
289</p> 361</p>
290 362
291<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>
292# <i>rc-update add net.eth0 default</i> 366# <i>rc-update add net.eth0 default</i>
293</pre> 367</pre>
294 368
295<p> 369<p>
296If you have several network interfaces, you need to create the appropriate 370If you have several network interfaces, you need to create the appropriate
297<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>.
298use <c>ln</c> to do this: 372</p>
373
299</p> 374<p>
300 375If you later find out the assumption about the network interface name (which we
301<pre caption="Creating extra initscripts"> 376currently document as eth0) was wrong, then
302# <i>cd /etc/init.d</i>
303# <i>ln -s net.eth0 net.eth1</i>
304# <i>rc-update add net.eth1 default</i>
305</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>
306 397
307</body> 398</body>
308</subsection> 399</subsection>
309<subsection> 400<subsection>
310<title>Writing Down Network Information</title> 401<title>Writing Down Network Information</title>
311<body> 402<body>
312 403
313<p> 404<p>
314You 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
315<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
316for 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.
317internal 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
318<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.
319open <path>/etc/hosts</path> and fill in the values:
320</p> 410</p>
321 411
322<pre caption="Opening /etc/hosts"> 412<pre caption="Opening /etc/hosts">
323# <i>nano -w /etc/hosts</i> 413# <i>nano -w /etc/hosts</i>
324</pre> 414</pre>
325 415
326<pre caption="Filling in the networking information"> 416<pre caption="Filling in the networking information">
327127.0.0.1 localhost 417<comment>(This defines the current system)</comment>
418127.0.0.1 tux.homenetwork tux localhost
419
420<comment>(Define extra systems on your network,
421they need to have a static IP to be defined this way.)</comment>
328192.168.0.5 jenny.homenetwork jenny 422192.168.0.5 jenny.homenetwork jenny
329192.168.0.6 benny.homenetwork benny 423192.168.0.6 benny.homenetwork benny
330192.168.0.7 tux.homenetwork tux
331</pre>
332
333<p>
334If your system is the only system (or the nameservers handle all name
335resolution) a single line is sufficient:
336</p>
337
338<pre caption="/etc/hosts for lonely or fully integrated PCs">
339127.0.0.1 localhost tux
340</pre> 424</pre>
341 425
342<p> 426<p>
343Save and exit the editor to continue. 427Save and exit the editor to continue.
344</p> 428</p>
345 429
346<p> 430<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
347If you don't have PCMCIA, you can now continue with <uri 431If you don't have PCMCIA, you can now continue with <uri
348link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 432link="#sysinfo">System Information</uri>. PCMCIA-users should read the
349following topic on PCMCIA. 433following topic on PCMCIA.
350</p> 434</p>
351 435
352</body> 436</body>
353</subsection> 437</subsection>
354<subsection> 438<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
355<title>Optional: Get PCMCIA Working</title> 439<title>Optional: Get PCMCIA Working</title>
356<body> 440<body>
357 441
358<p> 442<p>
359PCMCIA-users should first install the <c>pcmcia-cs</c> package: 443PCMCIA users should first install the <c>pcmciautils</c> package.
360</p> 444</p>
361 445
362<pre caption="Installing pcmcia-cs"> 446<pre caption="Installing pcmciautils">
363# <i>emerge --usepkg pcmcia-cs</i> 447# <i>emerge pcmciautils</i>
364</pre>
365
366<p>
367When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
368runlevel:
369</p>
370
371<pre caption="Adding pcmcia to the default runlevel">
372# <i>rc-update add pcmcia default</i>
373</pre> 448</pre>
374 449
375</body> 450</body>
376</subsection> 451</subsection>
377</section> 452</section>
378<section> 453
454<section id="sysinfo">
379<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
380<body> 468</body>
469</subsection>
470<subsection>
471<title>System Information</title>
472<body>
381 473
382<p>
383Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
384Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
385</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>
386 479
387<pre caption="Opening /etc/rc.conf"> 480<pre caption="Configuring services">
388# <i>nano -w /etc/rc.conf</i> 481# <i>nano -w /etc/rc.conf</i>
389</pre> 482</pre>
390 483
391<p> 484<p>
392As 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.
393configuration variables. Take special care with the <c>KEYMAP</c> setting: if 486</p>
394you select the wrong <c>KEYMAP</c> you will get weird results when typing on 487
395your keyboard.
396</p> 488<p>
489Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
490Edit it to configure your keyboard.
491</p>
397 492
398<note> 493<pre caption="Opening /etc/conf.d/keymaps">
399Users of USB-based SPARC systems and SPARC clones might need to select an i386 494# <i>nano -w /etc/conf.d/keymaps</i>
400keymap (such as "us") instead of "sunkeymap". 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.
401</note> 504</note>
402 505
403<p> 506<p>
404When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 507When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
405continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 508exit.
509</p>
510
406</p> 511<p>
512Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
513according to your needs.
514</p>
407 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>
408</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>
409</section> 559</section>
410</sections> 560</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20