/[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.30		Revision 1.67
…		…
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/1.0 -->
6		6
7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.30 2004/03/21 10:21:35 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 $ -->
8		8
9	<sections>	9	<sections>
		10
		11	<version>2.9</version>
		12	<date>2005-06-24</date>
		13
10	<section>	14	<section>
11	<title>Filesystem Information</title>	15	<title>Filesystem Information</title>
12	<subsection>	16	<subsection>
13	<title>What is fstab?</title>	17	<title>What is fstab?</title>
14	<body>	18	<body>
15		19
16	<p>	20	<p>
17	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
18	<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
19	(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
20	(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
21	etc.).	25	them or not, etc.)
22	</p>	26	</p>
23		27
24	</body>	28	</body>
25	</subsection>	29	</subsection>
26	<subsection>	30	<subsection>
…		…
46	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
47	</li>	51	</li>
48	<li>	52	<li>
49	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
50	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,
51	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
52	listing. Multiple mountoptions are comma-separated.	56	listing. Multiple mountoptions are comma-separated.
53	</li>	57	</li>
54	<li>	58	<li>
55	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
56	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).
57	</li>	61	</li>
58	<li>	62	<li>
59	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
60	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.
61	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>
62	(or <c>0</c> in case a filesystem check isn't necessary).	66	(or <c>0</c> if a filesystem check isn't necessary).
63	</li>	67	</li>
64	</ul>	68	</ul>
65		69
66	<p>	70	<p>
		71	The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
67	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
68	<path>/etc/fstab</path>:	73	<path>/etc/fstab</path>:
69	</p>	74	</p>
70		75
71	<pre caption="Opening /etc/fstab">	76	<pre caption="Opening /etc/fstab">
72	# <i>nano -w /etc/fstab</i>	77	# <i>nano -w /etc/fstab</i>
73	</pre>	78	</pre>
74		79
75	<p>	80	<p>
76	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>
77	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
78	<path>/boot</path> partition (such as PPC), don't copy it verbatim.	83	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
79	</p>	84	</p>
80		85
81	<p>	86	<p>
82	In our default x86 partitioning example <path>/boot</path> is the	87	In our default x86 partitioning example <path>/boot</path> is the
83	<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.
84	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:
85	would write down:
86	</p>	90	</p>
87		91
88	<pre caption="An example /boot line for /etc/fstab">	92	<pre caption="An example /boot line for /etc/fstab">
89	/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.
90	</pre>	101	</p>
91		102
92	<p>	103	<p>
93	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>
94	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
95	aren't registered (you don't need those generally anyway):	106	aren't registered (you don't need those generally anyway):
96	</p>	107	</p>
97		108
98	<pre caption="An improved /boot line for /etc/fstab">	109	<pre caption="An improved /boot line for /etc/fstab">
99	/dev/hda1 /boot ext2 noauto,noatime 1 2	110	/dev/hda1 /boot ext2 defaults,noatime 1 2
100	</pre>	111	</pre>
101		112
102	<p>	113	<p>
103	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
104	<path>/boot</path>, <path>/</path> and the swap partition):	115	<path>/boot</path>, <path>/</path> and the swap partition):
105	</p>	116	</p>
106		117
107	<pre caption="Three /etc/fstab lines">	118	<pre caption="Three /etc/fstab lines">
108	/dev/hda1 /boot ext2 noauto,noatime 1 2	119	/dev/hda1 /boot ext2 defaults,noatime 1 2
109	/dev/hda2 none swap sw 0 0	120	/dev/hda2 none swap sw 0 0
110	/dev/hda3 / ext3 noatime 0 1	121	/dev/hda3 / ext3 noatime 0 1
111	</pre>	122	</pre>
112		123
113	<p>	124	<p>
…		…
115	(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
116	partitions or drives, for those too):	127	partitions or drives, for those too):
117	</p>	128	</p>
118		129
119	<pre caption="A full /etc/fstab example">	130	<pre caption="A full /etc/fstab example">
120	/dev/hda1 /boot ext2 noauto,noatime 1 2	131	/dev/hda1 /boot ext2 defaults,noatime 1 2
121	/dev/hda2 none swap sw 0 0	132	/dev/hda2 none swap sw 0 0
122	/dev/hda3 / ext3 noatime 0 1	133	/dev/hda3 / ext3 noatime 0 1
123		134
124	none /proc proc defaults 0 0	135	none /proc proc defaults 0 0
125	none /dev/shm tmpfs defaults 0 0	136	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
126		137
127	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	138	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
128	</pre>	139	</pre>
129		140
130	<p>	141	<p>
…		…
133	<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.
134	</p>	145	</p>
135		146
136	<p>	147	<p>
137	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
138	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>
139	too:	151	too:
140	</p>	152	</p>
141		153
142	<pre caption="Adding openprom filesystem to /etc/fstab">	154	<pre caption="Adding openprom filesystem to /etc/fstab">
143	none /proc/openprom openpromfs defaults 0 0	155	none /proc/openprom openpromfs defaults 0 0
144	</pre>	156	</pre>
145		157
146	<p>	158	<p>
147	If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
148	</p>
149
150	<pre caption="Adding usbfs filesystem to /etc/fstab">
151	none /proc/bus/usb usbfs defaults 0 0
152	</pre>
153
154	<p>
155	Reread your <path>/etc/fstab</path>, save and quit to continue.	159	Double-check your <path>/etc/fstab</path>, save and quit to continue.
156	</p>	160	</p>
157		161
158	</body>	162	</body>
159	</subsection>	163	</subsection>
160	</section>	164	</section>
…		…
163	<subsection>	167	<subsection>
164	<title>Hostname, Domainname etc.</title>	168	<title>Hostname, Domainname etc.</title>
165	<body>	169	<body>
166		170
167	<p>	171	<p>
168	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
169	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
170	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
171	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
172	<c>tux</c> and domain <c>homenetwork</c>.	176	<c>tux</c> and domain <c>homenetwork</c>.
173	</p>	177	</p>
174		178
175	<p>	179	<p>
176	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:
177	</p>	181	</p>
178		182
179	<pre caption="Setting the hostname">	183	<pre caption="Setting the hostname">
180	# <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>"
181	</pre>	188	</pre>
182		189
183	<p>	190	<p>
184	Second we set the domainname:	191	Second we set the domainname:
185	</p>	192	</p>
186		193
187	<pre caption="Setting the domainname">	194	<pre caption="Setting the domainname">
188	# <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>"
189	</pre>	199	</pre>
190		200
191	<p>	201	<p>
192	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
193	one), you need to define that one too:	203	one), you need to define that one too:
194	</p>	204	</p>
195		205
196	<pre caption="Setting the NIS domainname">	206	<pre caption="Setting the NIS domainname">
197	# <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>"
198	</pre>	211	</pre>
199		212
200	<p>	213	<p>
201	Now add the <c>domainname</c> script to the default runlevel:	214	Now add the <c>domainname</c> script to the default runlevel:
202	</p>	215	</p>
…		…
211	<title>Configuring your Network</title>	224	<title>Configuring your Network</title>
212	<body>	225	<body>
213		226
214	<p>	227	<p>
215	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
216	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
217	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
218	your Gentoo system permanently.	231	your Gentoo system permanently.
219	</p>	232	</p>
220		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
221	<p>	240	<p>
222	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
223	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
224	networking manually. But don't fear, we'll explain everything :)	243	networking manually. But don't fear, we'll explain everything :)
225	</p>	244	</p>
226		245
227	<p>	246	<p>
228	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>
…		…
232	<pre caption="Opening /etc/conf.d/net for editing">	251	<pre caption="Opening /etc/conf.d/net for editing">
233	# <i>nano -w /etc/conf.d/net</i>	252	# <i>nano -w /etc/conf.d/net</i>
234	</pre>	253	</pre>
235		254
236	<p>	255	<p>
237	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
238	syntax:	257	imagine, this variable configured the eth0 network interface. If the interface
239	</p>	258	needs to automatically obtain an IP address through DHCP, you should set it
240		259	like so:
241	<pre caption="iface_eth0 syntaxis">
242	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
243	</pre>
244
245	<p>	260	</p>
246	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	261
247	to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.	262	<pre caption="Automatically obtaining an IP address for eth0">
248	If you need to setup your network manually and you're	263	config_eth0=( "dhcp" )
249	not familiar with all the above terms, please read the section on <uri	264	</pre>
250	link="?part=1&chap=3#doc_chap4_sect3">Understanding Network	265
251	Terminology</uri> if you haven't done so already.
252	</p>	266	<p>
253		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>:
254	<p>	269	</p>
255	So let us give three examples; the first one uses DHCP, the second one a static	270
256	IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and	271	<pre caption="Manually setting IP information for eth0">
257	gateway 192.168.0.1 while the third one just activates the interface for	272	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
258	rp-pppoe usage:	273	routes_eth0=( "default gw 192.168.0.1" )
		274	</pre>
		275
259	</p>	276	<p>
260		277	If you have several network interfaces repeat the above steps for
261	<pre caption="Examples for /etc/conf.d/net">	278	<c>config_eth1</c>, <c>config_eth2</c>, etc.
262	<comment>(For DHCP)</comment>
263	iface_eth0="dhcp"
264
265	<comment>(For static IP)</comment>
266	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
267	gateway="eth0/192.168.0.1"
268
269	<comment>(For rp-pppoe)</comment>
270	iface_eth0="up"
271	</pre>
272
273	<p>
274	If you have several network interfaces, create extra <c>iface_eth</c> variables,
275	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
276	shouldn't be reproduced as you can only set one gateway per computer.
277	</p>	279	</p>
278		280
279	<p>	281	<p>
280	Now save the configuration and exit to continue.	282	Now save the configuration and exit to continue.
281	</p>	283	</p>
…		…
285	<subsection>	287	<subsection>
286	<title>Automatically Start Networking at Boot</title>	288	<title>Automatically Start Networking at Boot</title>
287	<body>	289	<body>
288		290
289	<p>	291	<p>
290	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
291	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
292	the PCMCIA interfaces are started by the PCMCIA init script.	294	the PCMCIA interfaces are started by the PCMCIA init script.
293	</p>	295	</p>
294		296
295	<pre caption="Adding net.eth0 to the default runlevel">	297	<pre caption="Adding net.eth0 to the default runlevel">
…		…
334	192.168.0.7 tux.homenetwork tux	336	192.168.0.7 tux.homenetwork tux
335	</pre>	337	</pre>
336		338
337	<p>	339	<p>
338	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
339	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>:
340	</p>	343	</p>
341		344
342	<pre caption="/etc/hosts for lonely or fully integrated PCs">	345	<pre caption="/etc/hosts for lonely or fully integrated PCs">
343	127.0.0.1 localhost	346	127.0.0.1 localhost tux
344	</pre>	347	</pre>
345		348
346	<p>	349	<p>
347	Save and exit the editor to continue.	350	Save and exit the editor to continue.
348	</p>	351	</p>
…		…
357	</subsection>	360	</subsection>
358	<subsection>	361	<subsection>
359	<title>Optional: Get PCMCIA Working</title>	362	<title>Optional: Get PCMCIA Working</title>
360	<body>	363	<body>
361		364
		365	<note>
		366	pcmcia-cs is only available for x86, amd64 and ppc platforms.
		367	</note>
		368
362	<p>	369	<p>
363	PCMCIA-users should first install the <c>pcmcia-cs</c> package. The	370	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
364	<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:	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:
365	</p>	374	</p>
366		375
367	<pre caption="Installing pcmcia-cs">	376	<pre caption="Installing pcmcia-cs">
368	# <i>USE="-X" emerge pcmcia-cs</i>	377	# <i>USE="-X" emerge pcmcia-cs</i>
369	</pre>	378	</pre>
…		…
380	</body>	389	</body>
381	</subsection>	390	</subsection>
382	</section>	391	</section>
383	<section>	392	<section>
384	<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>
385	<body>	419	<body>
386		420
387	<p>	421	<p>
388	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.
389	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 :)
…		…
392	<pre caption="Opening /etc/rc.conf">	426	<pre caption="Opening /etc/rc.conf">
393	# <i>nano -w /etc/rc.conf</i>	427	# <i>nano -w /etc/rc.conf</i>
394	</pre>	428	</pre>
395		429
396	<p>	430	<p>
		431	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		432	</p>
		433
		434	<p>
397	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
398	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	436	configuration variables. Among other settings, you can configure your console
399	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).
400	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.
401	</p>	452	</p>
402		453
403	<note>	454	<note>
404	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
405	keymap (such as "us") instead of "sunkeymap".	456	select an i386 keymap (such as "us") instead of "sunkeymap".
406	</note>	457	</note>
407		458
408	<p>	459	<p>
409	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB	460	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
410	keymaps on boot have to enable ADB keycode sendings in their kernel and have to	461	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
411	set a mac/ppc keymap in <path>rc.conf</path>.	462	to set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
412	</p>
413
414	<p>	463	</p>
415	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then	464
416	continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>.
417	</p>	465	<p>
		466	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
		467	exit.
		468	</p>
418		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>
419	</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>
420	</section>	520	</section>
421	</sections>	521	</sections>

 Legend:



Removed from v.1.30
 


changed lines


 
Added in v.1.67
 Legend:



Removed from v.1.30
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.20