… | |
… | |
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/2.5 --> |
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.80 2006/08/23 19:31:53 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.108 2011/10/30 11:56:08 swift 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>2.21</version> |
17 | <version>15</version> |
12 | <date>2006-08-23</date> |
18 | <date>2011-10-30</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> |
… | |
… | |
67 | </li> |
73 | </li> |
68 | </ul> |
74 | </ul> |
69 | |
75 | |
70 | <impo> |
76 | <impo> |
71 | The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid |
77 | The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid |
72 | fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>. |
78 | fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>. |
73 | </impo> |
79 | </impo> |
74 | |
80 | |
75 | <pre caption="Opening /etc/fstab"> |
81 | <pre caption="Opening /etc/fstab"> |
76 | # <i>nano -w /etc/fstab</i> |
82 | # <i>nano -w /etc/fstab</i> |
77 | </pre> |
83 | </pre> |
… | |
… | |
83 | 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> |
84 | partition. This is just an example, if you didn't or couldn't create a |
90 | partition. This is just an example, if you didn't or couldn't create a |
85 | <path>/boot</path>, don't copy it. |
91 | <path>/boot</path>, don't copy it. |
86 | </p> |
92 | </p> |
87 | |
93 | |
88 | <p test="contains(func:keyval('/boot'), '/dev/hd')"> |
|
|
89 | In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is |
|
|
90 | usually the <path><keyval id="/boot"/></path> partition (or |
|
|
91 | <path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as |
|
|
92 | filesystem. It needs to be checked during boot, so we would write down: |
|
|
93 | </p> |
94 | <p> |
94 | |
|
|
95 | <p test="contains(func:keyval('/boot'), '/dev/sd')"> |
|
|
96 | In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is |
95 | In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is |
97 | usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as |
96 | usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as |
98 | filesystem. 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: |
99 | </p> |
98 | </p> |
100 | |
99 | |
… | |
… | |
110 | </p> |
109 | </p> |
111 | |
110 | |
112 | </body> |
111 | </body> |
113 | <body> |
112 | <body> |
114 | |
113 | |
115 | <p test="not(func:keyval('arch')='SPARC')"> |
114 | <p> |
116 | Add the rules that match your partitioning scheme and append rules for |
115 | Add the rules that match your partitioning scheme and append rules for |
117 | <path>/proc</path>, <c>tmpfs</c>, for your CD-ROM drive(s), and of course, if |
|
|
118 | you have other partitions or drives, for those too. |
|
|
119 | </p> |
|
|
120 | |
|
|
121 | <p test="func:keyval('arch')='SPARC'"> |
|
|
122 | Add the rules that match your partitioning schema and append rules for |
|
|
123 | <path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM |
|
|
124 | drive(s), and of course, if you have other partitions or drives, for those too. |
116 | your CD-ROM drive(s), and of course, if you have other partitions or drives, |
|
|
117 | for those too. |
125 | </p> |
118 | </p> |
126 | |
119 | |
127 | <p> |
120 | <p> |
128 | Now use the <e>example</e> below to create your <path>/etc/fstab</path>: |
121 | Now use the <e>example</e> below to create your <path>/etc/fstab</path>: |
129 | </p> |
122 | </p> |
130 | |
|
|
131 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'"> |
|
|
132 | <keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
|
|
133 | /dev/hda2 none swap sw 0 0 |
|
|
134 | /dev/hda3 / ext3 noatime 0 1 |
|
|
135 | |
|
|
136 | none /proc proc defaults 0 0 |
|
|
137 | none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
138 | |
|
|
139 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
|
|
140 | </pre> |
|
|
141 | |
123 | |
142 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'"> |
124 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'"> |
143 | <keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
125 | <keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
144 | /dev/sda3 none swap sw 0 0 |
126 | /dev/sda3 none swap sw 0 0 |
145 | /dev/sda4 / ext3 noatime 0 1 |
127 | /dev/sda4 / ext3 noatime 0 1 |
146 | |
128 | |
147 | none /proc proc defaults 0 0 |
|
|
148 | none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
149 | |
|
|
150 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
129 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
151 | </pre> |
|
|
152 | |
130 | |
|
|
131 | proc /proc proc defaults 0 0 |
|
|
132 | shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
133 | </pre> |
|
|
134 | |
153 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'"> |
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'"> |
154 | <keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
136 | <keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
155 | /dev/sda2 none swap sw 0 0 |
137 | /dev/sda2 none swap sw 0 0 |
156 | /dev/sda3 / ext3 noatime 0 1 |
138 | /dev/sda3 / ext3 noatime 0 1 |
157 | |
139 | |
158 | none /proc proc defaults 0 0 |
|
|
159 | none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
160 | |
|
|
161 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
140 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
|
|
141 | |
|
|
142 | proc /proc proc defaults 0 0 |
|
|
143 | shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
162 | </pre> |
144 | </pre> |
163 | |
145 | |
164 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'"> |
146 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'"> |
165 | /dev/sda1 / ext3 noatime 0 1 |
147 | /dev/sda1 / ext3 noatime 0 1 |
166 | /dev/sda2 none swap sw 0 0 |
148 | /dev/sda2 none swap sw 0 0 |
167 | /dev/sda4 /usr ext3 noatime 0 2 |
149 | /dev/sda4 /usr ext3 noatime 0 2 |
168 | /dev/sda5 /var ext3 noatime 0 2 |
150 | /dev/sda5 /var ext3 noatime 0 2 |
169 | /dev/sda6 /home ext3 noatime 0 2 |
151 | /dev/sda6 /home ext3 noatime 0 2 |
170 | |
152 | |
|
|
153 | <comment># You must add the rules for openprom</comment> |
171 | none /proc/openprom openpromfs defaults 0 0 |
154 | openprom /proc/openprom openpromfs defaults 0 0 |
172 | none /proc proc defaults 0 0 |
|
|
173 | none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
174 | |
155 | |
175 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
156 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
176 | </pre> |
|
|
177 | |
157 | |
178 | <note test="func:keyval('arch')='PPC'"> |
158 | proc /proc proc defaults 0 0 |
179 | There are important variations between PPC machine types. Please make sure you |
159 | shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
180 | adapt the following example to your system. |
160 | </pre> |
181 | </note> |
|
|
182 | |
161 | |
183 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'"> |
162 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or |
184 | /dev/hda4 / ext3 noatime 0 1 |
163 | func:keyval('arch')='PPC64'"> |
185 | /dev/hda3 none swap sw 0 0 |
|
|
186 | |
|
|
187 | none /proc proc defaults 0 0 |
|
|
188 | none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
189 | |
|
|
190 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
|
|
191 | </pre> |
|
|
192 | |
|
|
193 | <pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'"> |
|
|
194 | /dev/sda4 / ext3 noatime 0 1 |
164 | /dev/sda4 / ext3 noatime 0 1 |
195 | /dev/sda3 none swap sw 0 0 |
165 | /dev/sda3 none swap sw 0 0 |
196 | |
166 | |
197 | none /proc proc defaults 0 0 |
|
|
198 | none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
|
|
199 | |
|
|
200 | /dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
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 |
201 | </pre> |
171 | </pre> |
202 | |
172 | |
203 | <p> |
173 | <p> |
204 | <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 |
205 | 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 |
… | |
… | |
220 | </subsection> |
190 | </subsection> |
221 | </section> |
191 | </section> |
222 | <section> |
192 | <section> |
223 | <title>Networking Information</title> |
193 | <title>Networking Information</title> |
224 | <subsection> |
194 | <subsection> |
225 | <title>Host name</title> |
195 | <title>Host name, Domainname, etc</title> |
226 | <body> |
196 | <body> |
227 | |
197 | |
228 | <p> |
198 | <p> |
229 | 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 |
230 | 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 |
… | |
… | |
234 | </p> |
204 | </p> |
235 | |
205 | |
236 | <pre caption="Setting the host name"> |
206 | <pre caption="Setting the host name"> |
237 | # <i>nano -w /etc/conf.d/hostname</i> |
207 | # <i>nano -w /etc/conf.d/hostname</i> |
238 | |
208 | |
239 | <comment>(Set the HOSTNAME variable to your host name)</comment> |
209 | <comment>(Set the hostname variable to your host name)</comment> |
240 | HOSTNAME="<i>tux</i>" |
210 | hostname="<i>tux</i>" |
|
|
211 | </pre> |
|
|
212 | |
|
|
213 | <p> |
|
|
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. |
241 | </pre> |
218 | </p> |
|
|
219 | |
|
|
220 | <pre caption="Setting the domainname"> |
|
|
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>" |
|
|
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> |
|
|
232 | |
|
|
233 | <p> |
|
|
234 | If you have a NIS domain (if you don't know what that is, then you don't have |
|
|
235 | one), you need to define that one too: |
|
|
236 | </p> |
|
|
237 | |
|
|
238 | <pre caption="Setting the NIS domainname"> |
|
|
239 | # <i>nano -w /etc/conf.d/net</i> |
|
|
240 | |
|
|
241 | <comment>(Set the nis_domain variable to your NIS domain name)</comment> |
|
|
242 | nis_domain_lo="<i>my-nisdomain</i>" |
|
|
243 | </pre> |
|
|
244 | |
|
|
245 | <note> |
|
|
246 | For more information on configuring DNS and NIS, please read the examples |
|
|
247 | provided in <path>/usr/share/doc/openrc-*/net.example.bz2</path> which |
|
|
248 | can be read using <c>bzless</c>. Also, you may want to emerge <c>openresolv</c> |
|
|
249 | to help manage your DNS/NIS setup. |
|
|
250 | </note> |
242 | |
251 | |
243 | </body> |
252 | </body> |
244 | </subsection> |
253 | </subsection> |
245 | <subsection> |
254 | <subsection> |
246 | <title>Configuring your Network</title> |
255 | <title>Configuring your Network</title> |
… | |
… | |
262 | <p> |
271 | <p> |
263 | All networking information is gathered in <path>/etc/conf.d/net</path>. It uses |
272 | All networking information is gathered in <path>/etc/conf.d/net</path>. It uses |
264 | a straightforward yet not intuitive syntax if you don't know how to set up |
273 | a straightforward yet not intuitive syntax if you don't know how to set up |
265 | networking manually. But don't fear, we'll explain everything. A fully |
274 | networking manually. But don't fear, we'll explain everything. A fully |
266 | commented example that covers many different configurations is available in |
275 | commented example that covers many different configurations is available in |
267 | <path>/etc/conf.d/net.example</path>. |
276 | <path>/usr/share/doc/openrc-*/net.example.bz2</path>. |
268 | </p> |
|
|
269 | |
|
|
270 | <p> |
277 | </p> |
271 | DHCP is used by default and does not require any further configuration. |
278 | |
|
|
279 | <p> |
|
|
280 | DHCP is used by default. For DHCP to work, you will need to install a DHCP |
|
|
281 | client. This is described later in <uri |
|
|
282 | link="?part=1&chap=9#networking-tools">Installing Necessary System |
|
|
283 | Tools</uri>. Do not forget to install a DHCP client. |
272 | </p> |
284 | </p> |
273 | |
285 | |
274 | <p> |
286 | <p> |
275 | If you need to configure your network connection either because you need |
287 | If you need to configure your network connection either because you need |
276 | specific DHCP options or because you do not use DHCP at all, open |
288 | specific DHCP options or because you do not use DHCP at all, open |
… | |
… | |
287 | </p> |
299 | </p> |
288 | |
300 | |
289 | <pre caption="Default /etc/conf.d/net"> |
301 | <pre caption="Default /etc/conf.d/net"> |
290 | # This blank configuration will automatically use DHCP for any net.* |
302 | # This blank configuration will automatically use DHCP for any net.* |
291 | # scripts in /etc/init.d. To create a more complete configuration, |
303 | # scripts in /etc/init.d. To create a more complete configuration, |
292 | # please review /etc/conf.d/net.example and save your configuration |
304 | # please review /usr/share/doc/openrc-*/net.example.bz2 and save |
293 | # in /etc/conf.d/net (this file :]!). |
305 | # your configuration in /etc/conf.d/net (this file :]!). |
294 | </pre> |
306 | </pre> |
295 | |
307 | |
296 | <p> |
308 | <p> |
297 | To enter your own IP address, netmask and gateway, you need |
309 | To enter your own IP address, netmask and gateway, you need |
298 | to set both <c>config_eth0</c> and <c>routes_eth0</c>: |
310 | to set both <c>config_eth0</c> and <c>routes_eth0</c>: |
299 | </p> |
311 | </p> |
300 | |
312 | |
301 | <pre caption="Manually setting IP information for eth0"> |
313 | <pre caption="Manually setting IP information for eth0"> |
302 | config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" ) |
314 | config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" |
303 | routes_eth0=( "default gw 192.168.0.1" ) |
315 | routes_eth0="default via 192.168.0.1" |
304 | </pre> |
316 | </pre> |
305 | |
317 | |
306 | <p> |
318 | <p> |
307 | To use DHCP and add specific DHCP options, define <c>config_eth0</c> and |
319 | To use DHCP, define <c>config_eth0</c>: |
308 | <c>dhcp_eth0</c>: |
|
|
309 | </p> |
320 | </p> |
310 | |
321 | |
311 | <pre caption="Automatically obtaining an IP address for eth0"> |
322 | <pre caption="Automatically obtaining an IP address for eth0"> |
312 | config_eth0=( "dhcp" ) |
323 | config_eth0="dhcp" |
313 | dhcp_eth0="nodns nontp nonis" |
|
|
314 | </pre> |
324 | </pre> |
315 | |
325 | |
316 | <p> |
326 | <p> |
317 | Please read <path>/etc/conf.d/net.example</path> for a list of all available |
327 | Please read <path>/usr/share/doc/openrc-*/net.example.bz2</path> for a |
318 | options. |
328 | list of all available options. Be sure to also read your DHCP client manpage if |
|
|
329 | you need to set specific DHCP options. |
319 | </p> |
330 | </p> |
320 | |
331 | |
321 | <p> |
332 | <p> |
322 | If you have several network interfaces repeat the above steps for |
333 | If you have several network interfaces repeat the above steps for |
323 | <c>config_eth1</c>, <c>config_eth2</c>, etc. |
334 | <c>config_eth1</c>, <c>config_eth2</c>, etc. |
… | |
… | |
333 | <title>Automatically Start Networking at Boot</title> |
344 | <title>Automatically Start Networking at Boot</title> |
334 | <body> |
345 | <body> |
335 | |
346 | |
336 | <p> |
347 | <p> |
337 | To have your network interfaces activated at boot, you need to add them to the |
348 | To have your network interfaces activated at boot, you need to add them to the |
338 | default runlevel. If you have PCMCIA interfaces you should skip this action as |
349 | default runlevel. |
339 | the PCMCIA interfaces are started by the PCMCIA init script. |
|
|
340 | </p> |
350 | </p> |
341 | |
351 | |
342 | <pre caption="Adding net.eth0 to the default runlevel"> |
352 | <pre caption="Adding net.eth0 to the default runlevel"> |
|
|
353 | # <i>cd /etc/init.d</i> |
|
|
354 | # <i>ln -s net.lo net.eth0</i> |
343 | # <i>rc-update add net.eth0 default</i> |
355 | # <i>rc-update add net.eth0 default</i> |
344 | </pre> |
356 | </pre> |
345 | |
357 | |
346 | <p> |
358 | <p> |
347 | If you have several network interfaces, you need to create the appropriate |
359 | If you have several network interfaces, you need to create the appropriate |
348 | <path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can |
360 | <path>net.eth1</path>, <path>net.eth2</path> etc. just like you did with |
349 | use <c>ln</c> to do this: |
361 | <path>net.eth0</path>. |
350 | </p> |
|
|
351 | |
|
|
352 | <pre caption="Creating extra initscripts"> |
|
|
353 | # <i>cd /etc/init.d</i> |
|
|
354 | # <i>ln -s net.lo net.eth1</i> |
|
|
355 | # <i>rc-update add net.eth1 default</i> |
|
|
356 | </pre> |
362 | </p> |
357 | |
363 | |
358 | </body> |
364 | </body> |
359 | </subsection> |
365 | </subsection> |
360 | <subsection> |
366 | <subsection> |
361 | <title>Writing Down Network Information</title> |
367 | <title>Writing Down Network Information</title> |
… | |
… | |
398 | <subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'"> |
404 | <subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'"> |
399 | <title>Optional: Get PCMCIA Working</title> |
405 | <title>Optional: Get PCMCIA Working</title> |
400 | <body> |
406 | <body> |
401 | |
407 | |
402 | <p> |
408 | <p> |
403 | PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also |
409 | PCMCIA users should first install the <c>pcmciautils</c> package. |
404 | includes users who will be working with a 2.6 kernel (even though they won't be |
|
|
405 | using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary |
|
|
406 | to avoid installing xorg-x11 at this moment: |
|
|
407 | </p> |
410 | </p> |
408 | |
411 | |
409 | <pre caption="Installing pcmcia-cs"> |
412 | <pre caption="Installing pcmciautils"> |
410 | # <i>USE="-X" emerge pcmcia-cs</i> |
413 | # <i>emerge pcmciautils</i> |
411 | </pre> |
|
|
412 | |
|
|
413 | <p> |
|
|
414 | When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
|
|
415 | runlevel: |
|
|
416 | </p> |
|
|
417 | |
|
|
418 | <pre caption="Adding pcmcia to the default runlevel"> |
|
|
419 | # <i>rc-update add pcmcia default</i> |
|
|
420 | </pre> |
414 | </pre> |
421 | |
415 | |
422 | </body> |
416 | </body> |
423 | </subsection> |
417 | </subsection> |
424 | </section> |
418 | </section> |
… | |
… | |
433 | First we set the root password by typing: |
427 | First we set the root password by typing: |
434 | </p> |
428 | </p> |
435 | |
429 | |
436 | <pre caption="Setting the root password"> |
430 | <pre caption="Setting the root password"> |
437 | # <i>passwd</i> |
431 | # <i>passwd</i> |
438 | </pre> |
|
|
439 | |
|
|
440 | <p> |
|
|
441 | If you want root to be able to log on through the serial console, add |
|
|
442 | <c>tts/0</c> to <path>/etc/securetty</path>: |
|
|
443 | </p> |
|
|
444 | |
|
|
445 | <pre caption="Adding tts/0 to /etc/securetty"> |
|
|
446 | # <i>echo "tts/0" >> /etc/securetty</i> |
|
|
447 | </pre> |
432 | </pre> |
448 | |
433 | |
449 | </body> |
434 | </body> |
450 | </subsection> |
435 | </subsection> |
451 | <subsection> |
436 | <subsection> |
… | |
… | |
479 | <pre caption="Opening /etc/conf.d/keymaps"> |
464 | <pre caption="Opening /etc/conf.d/keymaps"> |
480 | # <i>nano -w /etc/conf.d/keymaps</i> |
465 | # <i>nano -w /etc/conf.d/keymaps</i> |
481 | </pre> |
466 | </pre> |
482 | |
467 | |
483 | <p> |
468 | <p> |
484 | Take special care with the <c>KEYMAP</c> variable. If you select the wrong |
469 | Take special care with the <c>keymap</c> variable. If you select the wrong |
485 | <c>KEYMAP</c>, you will get weird results when typing on your keyboard. |
470 | <c>keymap</c>, you will get weird results when typing on your keyboard. |
486 | </p> |
471 | </p> |
487 | |
|
|
488 | <note test="func:keyval('arch')='SPARC'"> |
|
|
489 | Users of USB-based SPARC systems and SPARC clones might need to select an i386 |
|
|
490 | keymap (such as "us") instead of "sunkeymap". |
|
|
491 | </note> |
|
|
492 | |
472 | |
493 | <note test="substring(func:keyval('arch'),1,3)='PPC'"> |
473 | <note test="substring(func:keyval('arch'),1,3)='PPC'"> |
494 | PPC uses x86 keymaps on most systems. Users who want to be able to use ADB |
474 | PPC uses x86 keymaps on most systems. |
495 | keymaps on boot have to enable ADB keycode sendings in their kernel and have to |
|
|
496 | set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>. |
|
|
497 | </note> |
475 | </note> |
498 | |
476 | |
499 | <p> |
477 | <p> |
500 | When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and |
478 | When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and |
501 | exit. |
479 | exit. |
502 | </p> |
480 | </p> |
503 | |
481 | |
504 | <p> |
482 | <p> |
505 | Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it |
483 | Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it |
506 | according to your needs. |
484 | according to your needs. |
507 | </p> |
485 | </p> |
508 | |
486 | |
509 | <pre caption="Opening /etc/conf.d/clock"> |
487 | <pre caption="Opening /etc/conf.d/hwclock"> |
510 | # <i>nano -w /etc/conf.d/clock</i> |
488 | # <i>nano -w /etc/conf.d/hwclock</i> |
511 | </pre> |
489 | </pre> |
512 | |
490 | |
513 | <p> |
491 | <p> |
514 | If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to |
492 | If your hardware clock is not using UTC, you need to add <c>clock="local"</c> |
515 | the file. Otherwise you will notice some clock skew. Furthermore, Windows |
493 | to the file. Otherwise you will notice some clock skew. |
516 | assumes that your hardware clock uses local time, so if you want to dualboot, |
|
|
517 | you should set this variable appropriately, otherwise your clock will go crazy. |
|
|
518 | </p> |
|
|
519 | |
|
|
520 | <p> |
494 | </p> |
|
|
495 | |
|
|
496 | <p> |
521 | When you're finished configuring <path>/etc/conf.d/clock</path>, save and |
497 | When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and |
522 | exit. |
498 | exit. |
|
|
499 | </p> |
|
|
500 | |
|
|
501 | <p> |
|
|
502 | You should define the timezone that you previously copied to |
|
|
503 | <path>/etc/localtime</path> in the <path>/etc/timezone</path> file so that |
|
|
504 | further upgrades of the <c>sys-libs/timezone-data</c> package can update |
|
|
505 | <path>/etc/localtime</path> automatically. For instance, if you used the GMT |
|
|
506 | timezone, you would write <c>GMT</c> in the <path>/etc/timezone</path> file. |
523 | </p> |
507 | </p> |
524 | |
508 | |
525 | <p test="not(func:keyval('arch')='PPC64')"> |
509 | <p test="not(func:keyval('arch')='PPC64')"> |
526 | Please continue with <uri link="?part=1&chap=9">Installing Necessary System |
510 | Please continue with <uri link="?part=1&chap=9">Installing Necessary System |
527 | Tools</uri>. |
511 | Tools</uri>. |