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