/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-config.xml

Diff of /xml/htdocs/doc/en/handbook/hb-install-config.xml

Parent Directory | Revision Log | View Patch Patch

Revision 1.17		Revision 1.67
		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/1.0 -->
3		6
4	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.17 2004/01/06 10:08:38 swift Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.67 2005/06/24 18:47:21 fox2mike Exp $ -->
5		8
6	<sections>	9	<sections>
7	<section>
8	<title>Timezone</title>
9	<body>
10		10
11	<p>	11	<version>2.9</version>
12	You now need to select your timezone so that your system knows where it is	12	<date>2005-06-24</date>
13	located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
14	symlink to <path>/etc/localtime</path> using <c>ln</c>:
15	</p>
16		13
17	<pre caption="Setting the timezone information">
18	# <i>ls /usr/share/zoneinfo</i>
19	<comment>(Suppose you want to use GMT:)</comment>
20	# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
21	</pre>
22
23	</body>
24	</section>
25	<section>	14	<section>
26	<title>Filesystem Information</title>	15	<title>Filesystem Information</title>
27	<subsection>	16	<subsection>
28	<title>What is fstab?</title>	17	<title>What is fstab?</title>
29	<body>	18	<body>
30		19
31	<p>	20	<p>
32	Under Linux, all partitions used by the system must be listed in	21	Under Linux, all partitions used by the system must be listed in
33	<path>/etc/fstab</path>. This file contains the mountpoints of those partitions	22	<path>/etc/fstab</path>. This file contains the mountpoints of those partitions
34	(where they are seen in the file system structure), how they should be mounted	23	(where they are seen in the file system structure), how they should be mounted
35	(special options) and when (automatically or not, can users mount those or not,	24	and with what special options (automatically or not, whether users can mount
36	etc.).	25	them or not, etc.)
37	</p>	26	</p>
38		27
39	</body>	28	</body>
40	</subsection>	29	</subsection>
41	<subsection>	30	<subsection>
…		…
61	The third field shows the <b>filesystem</b> used by the partition	50	The third field shows the <b>filesystem</b> used by the partition
62	</li>	51	</li>
63	<li>	52	<li>
64	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it	53	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it
65	wants to mount the partition. As every filesystem has its own mountoptions,	54	wants to mount the partition. As every filesystem has its own mountoptions,
66	you are encouraged to read the mount manpage (<c>man mount</c>) for a full	55	you are encouraged to read the mount man page (<c>man mount</c>) for a full
67	listing. Multiple mountoptions are comma-separated.	56	listing. Multiple mountoptions are comma-separated.
68	</li>	57	</li>
69	<li>	58	<li>
70	The fifth field is used by <c>dump</c> to determine if the partition needs to	59	The fifth field is used by <c>dump</c> to determine if the partition needs to
71	be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).	60	be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
72	</li>	61	</li>
73	<li>	62	<li>
74	The sixth field is used by <c>fsck</c> to determine the order in which	63	The sixth field is used by <c>fsck</c> to determine the order in which
75	filesystems should be <b>check</b>ed if the system wasn't shut down properly.	64	filesystems should be <b>check</b>ed if the system wasn't shut down properly.
76	The root filesystem should have <c>1</c> while the rest should have <c>2</c>	65	The root filesystem should have <c>1</c> while the rest should have <c>2</c>
77	(or <c>0</c> in case a filesystem check isn't necessary).	66	(or <c>0</c> if a filesystem check isn't necessary).
78	</li>	67	</li>
79	</ul>	68	</ul>
80		69
81	<p>	70	<p>
		71	The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
82	So start <c>nano</c> (or your favorite editor) to create your	72	file</e>, so start <c>nano</c> (or your favorite editor) to create your
83	<path>/etc/fstab</path>:	73	<path>/etc/fstab</path>:
84	</p>	74	</p>
85		75
86	<pre caption="Opening /etc/fstab">	76	<pre caption="Opening /etc/fstab">
87	# <i>nano -w /etc/fstab</i>	77	# <i>nano -w /etc/fstab</i>
88	</pre>	78	</pre>
89		79
90	<p>	80	<p>
91	Let us take a look at how we write down the options for the <path>/boot</path>	81	Let us take a look at how we write down the options for the <path>/boot</path>
92	partition. This is just an example, so if your architecture doesn't require a	82	partition. This is just an example, so if your architecture doesn't require a
93	<path>/boot</path> partition, don't copy it verbatim.	83	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
94	</p>	84	</p>
95		85
96	<p>	86	<p>
97	In our default x86 partitioning example <path>/boot</path> is the	87	In our default x86 partitioning example <path>/boot</path> is the
98	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't	88	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
99	be mounted automatically (<c>noauto</c>) but does need to be checked. So we	89	It needs to be checked during boot, so we would write down:
100	would write down:
101	</p>	90	</p>
102		91
103	<pre caption="An example /boot line for /etc/fstab">	92	<pre caption="An example /boot line for /etc/fstab">
104	/dev/hda1 /boot ext2 noauto 1 2	93	/dev/hda1 /boot ext2 defaults 1 2
		94	</pre>
		95
		96	<p>
		97	Some users don't want their <path>/boot</path> partition to be mounted
		98	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
		100	manually mount this partition every time you want to use it.
105	</pre>	101	</p>
106		102
107	<p>	103	<p>
108	Now, to improve performance, most users would want to add the <c>noatime</c>	104	Now, to improve performance, most users would want to add the <c>noatime</c>
109	option as mountoption, which results in a faster system since access times	105	option as mountoption, which results in a faster system since access times
110	aren't registered (you don't need those generally anyway):	106	aren't registered (you don't need those generally anyway):
111	</p>	107	</p>
112		108
113	<pre caption="An improved /boot line for /etc/fstab">	109	<pre caption="An improved /boot line for /etc/fstab">
114	/dev/hda1 /boot ext2 noauto,noatime 1 2	110	/dev/hda1 /boot ext2 defaults,noatime 1 2
115	</pre>	111	</pre>
116		112
117	<p>	113	<p>
118	If we continue with this, we would end up with the following three lines (for	114	If we continue with this, we would end up with the following three lines (for
119	<path>/boot</path>, <path>/</path> and the swap partition):	115	<path>/boot</path>, <path>/</path> and the swap partition):
120	</p>	116	</p>
121		117
122	<pre caption="Three /etc/fstab lines">	118	<pre caption="Three /etc/fstab lines">
123	/dev/hda1 /boot ext2 noauto,noatime 1 2	119	/dev/hda1 /boot ext2 defaults,noatime 1 2
124	/dev/hda2 none swap sw 0 0	120	/dev/hda2 none swap sw 0 0
125	/dev/hda3 / ext3 noatime 0 1	121	/dev/hda3 / ext3 noatime 0 1
126	</pre>	122	</pre>
127		123
128	<p>	124	<p>
…		…
130	(required) and for your CD-ROM drive (and of course, if you have other	126	(required) and for your CD-ROM drive (and of course, if you have other
131	partitions or drives, for those too):	127	partitions or drives, for those too):
132	</p>	128	</p>
133		129
134	<pre caption="A full /etc/fstab example">	130	<pre caption="A full /etc/fstab example">
135	/dev/hda1 /boot ext2 noauto,noatime 1 2	131	/dev/hda1 /boot ext2 defaults,noatime 1 2
136	/dev/hda2 none swap sw 0 0	132	/dev/hda2 none swap sw 0 0
137	/dev/hda3 / ext3 noatime 0 1	133	/dev/hda3 / ext3 noatime 0 1
138		134
139	none /proc proc defaults 0 0	135	none /proc proc defaults 0 0
140	none /dev/shm tmpfs defaults 0 0	136	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
141		137
142	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	138	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
143	</pre>	139	</pre>
144		140
145	<p>	141	<p>
…		…
148	<c>user</c> makes it possible for non-root users to mount the CD.	144	<c>user</c> makes it possible for non-root users to mount the CD.
149	</p>	145	</p>
150		146
151	<p>	147	<p>
152	Now use the above example to create your <path>/etc/fstab</path>. If you are a	148	Now use the above example to create your <path>/etc/fstab</path>. If you are a
153	SPARC-user, you should add the following line to your <path>/etc/fstab</path>	149	<b>SPARC</b>-user, you should add the following line to your
		150	<path>/etc/fstab</path>
154	too:	151	too:
155	</p>	152	</p>
156		153
157	<pre caption="Adding openprom filesystem to /etc/fstab">	154	<pre caption="Adding openprom filesystem to /etc/fstab">
158	none /proc/openprom openpromfs defaults 0 0	155	none /proc/openprom openpromfs defaults 0 0
159	</pre>	156	</pre>
160		157
161	<p>	158	<p>
162	If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
163	</p>
164
165	<pre caption="Adding usbfs filesystem to /etc/fstab">
166	none /proc/bus/usb usbfs defaults 0 0
167	</pre>
168
169	<p>
170	Reread your <path>/etc/fstab</path>, save and quit to continue.	159	Double-check your <path>/etc/fstab</path>, save and quit to continue.
171	</p>	160	</p>
172		161
173	</body>	162	</body>
174	</subsection>	163	</subsection>
175	</section>	164	</section>
…		…
178	<subsection>	167	<subsection>
179	<title>Hostname, Domainname etc.</title>	168	<title>Hostname, Domainname etc.</title>
180	<body>	169	<body>
181		170
182	<p>	171	<p>
183	One of the choices the user has to make is name his PC. This seems to be quite	172	One of the choices the user has to make is name his/her PC. This seems to be
184	easy, but <e>lots</e> of users are having difficulties finding the appropriate	173	quite easy, but <e>lots</e> of users are having difficulties finding the
185	name for their Linux-pc. To speed things up, know that any name you choose can	174	appropriate name for their Linux-pc. To speed things up, know that any name you
186	be changed afterwards. For all we care, you can just call your system	175	choose can be changed afterwards. For all we care, you can just call your system
187	<c>tux</c> and domain <c>homenetwork</c>.	176	<c>tux</c> and domain <c>homenetwork</c>.
188	</p>	177	</p>
189		178
190	<p>	179	<p>
191	We use these values in the next examples. First we set the hostname:	180	We use these values in the next examples. First we set the hostname:
192	</p>	181	</p>
193		182
194	<pre caption="Setting the hostname">	183	<pre caption="Setting the hostname">
195	# <i>echo tux > /etc/hostname</i>	184	# <i>nano -w /etc/conf.d/hostname</i>
		185
		186	<comment>(Set the HOSTNAME variable to your hostname)</comment>
		187	HOSTNAME="<i>tux</i>"
196	</pre>	188	</pre>
197		189
198	<p>	190	<p>
199	Second we set the domainname:	191	Second we set the domainname:
200	</p>	192	</p>
201		193
202	<pre caption="Setting the domainname">	194	<pre caption="Setting the domainname">
203	# <i>echo homenetwork > /etc/dnsdomainname</i>	195	# <i>nano -w /etc/conf.d/domainname</i>
		196
		197	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>
		198	DNSDOMAIN="<i>homenetwork</i>"
204	</pre>	199	</pre>
205		200
206	<p>	201	<p>
207	If you have a NIS domain (if you don't know what that is, then you don't have	202	If you have a NIS domain (if you don't know what that is, then you don't have
208	one), you need to define that one too:	203	one), you need to define that one too:
209	</p>	204	</p>
210		205
211	<pre caption="Setting the NIS domainname">	206	<pre caption="Setting the NIS domainname">
212	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	207	# <i>nano -w /etc/conf.d/domainname</i>
		208
		209	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
		210	NISDOMAIN="<i>my-nisdomain</i>"
213	</pre>	211	</pre>
214		212
215	<p>	213	<p>
216	Now add the <c>domainname</c> script to the default runlevel:	214	Now add the <c>domainname</c> script to the default runlevel:
217	</p>	215	</p>
…		…
226	<title>Configuring your Network</title>	224	<title>Configuring your Network</title>
227	<body>	225	<body>
228		226
229	<p>	227	<p>
230	Before you get that "Hey, we've had that already"-feeling, you should remember	228	Before you get that "Hey, we've had that already"-feeling, you should remember
231	that the networking you set up in the beginning of the gentoo installation was	229	that the networking you set up in the beginning of the Gentoo installation was
232	just for the installation. Right now you are going to configure networking for	230	just for the installation. Right now you are going to configure networking for
233	your Gentoo system permanently.	231	your Gentoo system permanently.
234	</p>	232	</p>
235		233
		234	<note>
		235	More detailed information about networking, including advanced topics like
		236	bonding, bridging, 802.11q VLANs or wireless networking is covered in the <uri
		237	link="?part=4">Gentoo Network Configuration</uri> section.
		238	</note>
		239
236	<p>	240	<p>
237	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	241	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
238	a straightforward yet not intuitive syntax if you don't know how to setup	242	a straightforward yet not intuitive syntax if you don't know how to set up
239	networking manually. But don't fear, we'll explain everything :)	243	networking manually. But don't fear, we'll explain everything :)
240	</p>	244	</p>
241		245
242	<p>	246	<p>
243	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>	247	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>
…		…
247	<pre caption="Opening /etc/conf.d/net for editing">	251	<pre caption="Opening /etc/conf.d/net for editing">
248	# <i>nano -w /etc/conf.d/net</i>	252	# <i>nano -w /etc/conf.d/net</i>
249	</pre>	253	</pre>
250		254
251	<p>	255	<p>
252	The first variable you'll find is <c>iface_eth0</c>. It uses the following	256	The first variable you'll find is called <c>config_eth0</c>. As you can probably
253	syntax:	257	imagine, this variable configured the eth0 network interface. If the interface
254	</p>	258	needs to automatically obtain an IP address through DHCP, you should set it
255		259	like so:
256	<pre caption="iface_eth0 syntaxis">
257	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
258	</pre>
259
260	<p>	260	</p>
261	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	261
262	to <c>dhcp</c>. However, if you need to setup your network manually and you're	262	<pre caption="Automatically obtaining an IP address for eth0">
263	not familiar with all the above terms, please read the section on <uri	263	config_eth0=( "dhcp" )
264	link="?part=1&chap=3#doc_chap4_sect3">Understanding Network	264	</pre>
265	Terminology</uri> if you haven't done so already.	265
266	</p>	266	<p>
267		267	However, if you have to enter your own IP address, netmask and gateway, you need
		268	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
268	<p>	269	</p>
269	So let us give two examples; the first one uses DHCP, the second one a static IP	270
270	(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway	271	<pre caption="Manually setting IP information for eth0">
271	192.168.0.1:	272	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
		273	routes_eth0=( "default gw 192.168.0.1" )
		274	</pre>
		275
272	</p>	276	<p>
273		277	If you have several network interfaces repeat the above steps for
274	<pre caption="Examples for /etc/conf.d/net">	278	<c>config_eth1</c>, <c>config_eth2</c>, etc.
275	<comment>(For DHCP:)</comment>
276	iface_eth0="dhcp"
277
278	<comment>(For static IP:)</comment>
279	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
280	gateway="eth0/192.168.0.1"
281	</pre>
282
283	<p>
284	If you have several network interfaces, create extra <c>iface_eth</c> variables,
285	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
286	shouldn't be reproduced as you can only set one gateway per computer.
287	</p>	279	</p>
288		280
289	<p>	281	<p>
290	Now save the configuration and exit to continue.	282	Now save the configuration and exit to continue.
291	</p>	283	</p>
…		…
295	<subsection>	287	<subsection>
296	<title>Automatically Start Networking at Boot</title>	288	<title>Automatically Start Networking at Boot</title>
297	<body>	289	<body>
298		290
299	<p>	291	<p>
300	To have your network interfaces activated at boot, you need to add those to the	292	To have your network interfaces activated at boot, you need to add them to the
301	default runlevel. If you have PCMCIA interfaces you should skip this action as	293	default runlevel. If you have PCMCIA interfaces you should skip this action as
302	the PCMCIA interfaces are started by the PCMCIA init script.	294	the PCMCIA interfaces are started by the PCMCIA init script.
303	</p>	295	</p>
304		296
305	<pre caption="Adding net.eth0 to the default runlevel">	297	<pre caption="Adding net.eth0 to the default runlevel">
…		…
337	# <i>nano -w /etc/hosts</i>	329	# <i>nano -w /etc/hosts</i>
338	</pre>	330	</pre>
339		331
340	<pre caption="Filling in the networking information">	332	<pre caption="Filling in the networking information">
341	127.0.0.1 localhost	333	127.0.0.1 localhost
342	192.168.0.5 jenny	334	192.168.0.5 jenny.homenetwork jenny
343	192.168.0.6 benny	335	192.168.0.6 benny.homenetwork benny
344	192.168.0.7 tux	336	192.168.0.7 tux.homenetwork tux
345	</pre>	337	</pre>
346		338
347	<p>	339	<p>
348	If your system is the only system (or the nameservers handle all name	340	If your system is the only system (or the nameservers handle all name
349	resolution) a single line is sufficient:	341	resolution) a single line is sufficient. For instance, if you want to call your
		342	system <c>tux</c>:
350	</p>	343	</p>
351		344
352	<pre caption="/etc/hosts for lonely or fully integrated PCs">	345	<pre caption="/etc/hosts for lonely or fully integrated PCs">
353	127.0.0.1 localhost tux	346	127.0.0.1 localhost tux
354	</pre>	347	</pre>
355		348
356	<p>	349	<p>
357	Save and exit the editor to continue.	350	Save and exit the editor to continue.
358	</p>	351	</p>
359		352
360	<p>	353	<p>
361	If you don't have PCMCIA, you can now continue with <uri	354	If you don't have PCMCIA, you can now continue with <uri
362	link="#doc_chap4">System Information</uri>. PCMCIA-users should read the	355	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
363	following topic on PCMCIA.	356	following topic on PCMCIA.
364	</p>	357	</p>
365		358
366	</body>	359	</body>
367	</subsection>	360	</subsection>
368	<subsection>	361	<subsection>
369	<title>Optional: Get PCMCIA Working</title>	362	<title>Optional: Get PCMCIA Working</title>
370	<body>	363	<body>
371		364
		365	<note>
		366	pcmcia-cs is only available for x86, amd64 and ppc platforms.
		367	</note>
		368
372	<p>	369	<p>
373	PCMCIA-users should first install the <c>pcmcia-cs</c> package:	370	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
		371	includes users who will be working with a 2.6 kernel (even though they won't be
		372	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
		373	to avoid installing xorg-x11 at this moment:
374	</p>	374	</p>
375		375
376	<pre caption="Installing pcmcia-cs">	376	<pre caption="Installing pcmcia-cs">
377	# <i>emerge --usepkg pcmcia-cs</i>	377	# <i>USE="-X" emerge pcmcia-cs</i>
378	</pre>	378	</pre>
379		379
380	<p>	380	<p>
381	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>	381	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
382	runlevel:	382	runlevel:
383	</p>	383	</p>
384		384
385	<pre caption="Adding pcmcia to the boot runlevel">	385	<pre caption="Adding pcmcia to the default runlevel">
386	# <i>rc-update add pcmcia boot</i>	386	# <i>rc-update add pcmcia default</i>
387	</pre>	387	</pre>
388		388
389	</body>	389	</body>
390	</subsection>	390	</subsection>
391	</section>	391	</section>
392	<section>	392	<section>
393	<title>System Information</title>	393	<title>System Information</title>
		394	<subsection>
		395	<title>Root Password</title>
		396	<body>
		397
		398	<p>
		399	First we set the root password by typing:
		400	</p>
		401
		402	<pre caption="Setting the root password">
		403	# <i>passwd</i>
		404	</pre>
		405
		406	<p>
		407	If you want root to be able to log on through the serial console, add
		408	<c>tts/0</c> to <path>/etc/securetty</path>:
		409	</p>
		410
		411	<pre caption="Adding tts/0 to /etc/securetty">
		412	# <i>echo "tts/0" >> /etc/securetty</i>
		413	</pre>
		414
		415	</body>
		416	</subsection>
		417	<subsection>
		418	<title>System Information</title>
394	<body>	419	<body>
395		420
396	<p>	421	<p>
397	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.	422	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
398	Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)	423	Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
…		…
401	<pre caption="Opening /etc/rc.conf">	426	<pre caption="Opening /etc/rc.conf">
402	# <i>nano -w /etc/rc.conf</i>	427	# <i>nano -w /etc/rc.conf</i>
403	</pre>	428	</pre>
404		429
405	<p>	430	<p>
		431	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		432	</p>
		433
		434	<p>
406	As you can see, this file is well commented to help you set up the necessary	435	As you can see, this file is well commented to help you set up the necessary
407	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	436	configuration variables. Among other settings, you can configure your console
408	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	437	fonts, your default editor and your display manager (like gdm or kdm).
409	your keyboard.	438	</p>
		439
		440	<p>
		441	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		442	Edit it to configure your keyboard.
		443	</p>
		444
		445	<pre caption="Opening /etc/conf.d/keymaps">
		446	# <i>nano -w /etc/conf.d/keymaps</i>
		447	</pre>
		448
		449	<p>
		450	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
		451	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
410	</p>	452	</p>
411		453
412	<note>	454	<note>
413	Users of USB-based SPARC systems and SPARC clones might need to select an i386	455	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
414	keymap (such as "us") instead of "sunkeymap".	456	select an i386 keymap (such as "us") instead of "sunkeymap".
415	</note>	457	</note>
416		458
417	<p>	459	<p>
418	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then	460	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
419	continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>.	461	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
		462	to set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
		463	</p>
		464
420	</p>	465	<p>
		466	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
		467	exit.
		468	</p>
421		469
		470	<p>
		471	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		472	according to your needs.
		473	</p>
		474
		475	<pre caption="Opening /etc/conf.d/clock">
		476	# <i>nano -w /etc/conf.d/clock</i>
		477	</pre>
		478
		479	<p>
		480	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
		481	the file. Otherwise you will notice some clock skew.
		482	</p>
		483
		484	<p>
		485	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
		486	exit.
		487	</p>
		488
		489	<p>
		490	If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with
		491	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
		492	</p>
		493
		494	</body>
		495	</subsection>
		496	<subsection>
		497	<title>Configuring the Console</title>
422	</body>	498	<body>
		499
		500	<note>
		501	The following section applies to the IBM POWER5 and JS20 hardware platforms.
		502	</note>
		503
		504	<p>
		505	If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
		506	the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
		507	</p>
		508
		509	<pre caption="Enabling hvc support in /etc/inittab">
		510	hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220
		511	</pre>
		512
		513	<p>
		514	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
		515	System Tools</uri>.
		516	</p>
		517
		518	</body>
		519	</subsection>
423	</section>	520	</section>
424	</sections>	521	</sections>

 Legend:



Removed from v.1.17
 


changed lines


 
Added in v.1.67
 Legend:



Removed from v.1.17
 


changed lines


 
Added in v.1.67
-Removed from v.1.17
+Added in v.1.67

	ViewVC Help
Powered by ViewVC 1.1.13