/[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.78		Revision 1.88
…		…
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.78 2006/05/27 13:02:15 neysx Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.88 2006/11/28 07:40:38 nightmorph 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.19</version>	17	<version>7.6</version>
12	<date>2006-05-27</date>	18	<date>2006-11-27</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 not a valid	77	The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72	fstab 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 Apple <b>PPC</b> machines), don't copy it	91	<path>/boot</path>, don't copy it.
84	verbatim.
85	</p>
86
87	<p>	92	</p>
		93
		94	<p test="contains(func:keyval('/boot'), '/dev/hd')">
88	In our default x86 partitioning example <path>/boot</path> is the	95	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
89	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.	96	usually the <path><keyval id="/boot"/></path> partition (or
		97	<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
90	It needs to be checked during boot, so we would write down:	98	filesystem. It needs to be checked during boot, so we would write down:
		99	</p>
		100
		101	<p test="contains(func:keyval('/boot'), '/dev/sd')">
		102	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
		103	usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
		104	filesystem. It needs to be checked during boot, so we would write down:
91	</p>	105	</p>
92		106
93	<pre caption="An example /boot line for /etc/fstab">	107	<pre caption="An example /boot line for /etc/fstab">
94	/dev/hda1 /boot ext2 defaults 1 2	108	<keyval id="/boot"/> /boot ext2 defaults 1 2
95	</pre>	109	</pre>
96		110
97	<p>	111	<p>
98	Some users don't want their <path>/boot</path> partition to be mounted	112	Some users don't want their <path>/boot</path> partition to be mounted
99	automatically to improve their system's security. Those people should	113	automatically to improve their system's security. Those people should
100	substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to	114	substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
101	manually mount this partition every time you want to use it.	115	manually mount this partition every time you want to use it.
102	</p>	116	</p>
103		117
		118	</body>
		119	<body>
		120
		121	<p test="not(func:keyval('arch')='SPARC')">
		122	Add the rules that match your partitioning scheme and append rules for
		123	<path>/proc</path>, <c>tmpfs</c>, for your CD-ROM drive(s), and of course, if
		124	you have other partitions or drives, for those too.
104	<p>	125	</p>
105	Now, to improve performance, most users would want to add the <c>noatime</c>
106	option as mountoption, which results in a faster system since access times
107	aren't registered (you don't need those generally anyway):
108	</p>
109		126
110	<pre caption="An improved /boot line for /etc/fstab">	127	<p test="func:keyval('arch')='SPARC'">
111	/dev/hda1 /boot ext2 defaults,noatime 1 2	128	Add the rules that match your partitioning schema and append rules for
112	</pre>	129	<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
113		130	drive(s), and of course, if you have other partitions or drives, for those too.
114	<p>	131	</p>
115	If we continue with this, we would end up with the following three lines (for	132
116	<path>/boot</path>, <path>/</path> and the swap partition):
117	</p>	133	<p>
118		134	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
119	<pre caption="Three /etc/fstab lines">
120	/dev/hda1 /boot ext2 defaults,noatime 1 2
121	/dev/hda2 none swap sw 0 0
122	/dev/hda3 / ext3 noatime 0 1
123	</pre>
124
125	<p>	135	</p>
126	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
127	(required) and for your CD-ROM drive (and of course, if you have other
128	partitions or drives, for those too):
129	</p>
130		136
131	<pre caption="A full /etc/fstab example">	137	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
132	/dev/hda1 /boot ext2 defaults,noatime 1 2	138	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
133	/dev/hda2 none swap sw 0 0	139	/dev/hda2 none swap sw 0 0
134	/dev/hda3 / ext3 noatime 0 1	140	/dev/hda3 / ext3 noatime 0 1
135		141
136	none /proc proc defaults 0 0	142	proc /proc proc defaults 0 0
137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0	143	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
138		144
		145	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		146	</pre>
		147
		148	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
		149	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
		150	/dev/sda3 none swap sw 0 0
		151	/dev/sda4 / ext3 noatime 0 1
		152
		153	proc /proc proc defaults 0 0
		154	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		155
		156	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		157	</pre>
		158
		159	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'">
		160	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
		161	/dev/sda2 none swap sw 0 0
		162	/dev/sda3 / ext3 noatime 0 1
		163
		164	proc /proc proc defaults 0 0
		165	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		166
		167	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		168	</pre>
		169
		170	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
		171	/dev/sda1 / ext3 noatime 0 1
		172	/dev/sda2 none swap sw 0 0
		173	/dev/sda4 /usr ext3 noatime 0 2
		174	/dev/sda5 /var ext3 noatime 0 2
		175	/dev/sda6 /home ext3 noatime 0 2
		176
		177	openprom /proc/openprom openpromfs defaults 0 0
		178	proc /proc proc defaults 0 0
		179	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		180
139	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	181	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		182	</pre>
		183
		184	<note test="func:keyval('arch')='PPC'">
		185	There are important variations between PPC machine types. Please make sure you
		186	adapt the following example to your system.
		187	</note>
		188
		189	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'">
		190	/dev/hda4 / ext3 noatime 0 1
		191	/dev/hda3 none swap sw 0 0
		192
		193	proc /proc proc defaults 0 0
		194	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		195
		196	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		197	</pre>
		198
		199	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'">
		200	/dev/sda4 / ext3 noatime 0 1
		201	/dev/sda3 none swap sw 0 0
		202
		203	proc /proc proc defaults 0 0
		204	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		205
		206	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
140	</pre>	207	</pre>
141		208
142	<p>	209	<p>
143	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for	210	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
144	removable media as they can be created with one of many filesystems) and	211	removable media as they can be created with one of many filesystems) and
145	<c>user</c> makes it possible for non-root users to mount the CD.	212	<c>user</c> makes it possible for non-root users to mount the CD.
146	</p>	213	</p>
147		214
148	<p>	215	<p>
149	Now use the above example to create your <path>/etc/fstab</path>. If you are a	216	To improve performance, most users would want to add the <c>noatime</c>
150	<b>SPARC</b>-user, you should add the following line to your	217	mount option, which results in a faster system since access times
151	<path>/etc/fstab</path>	218	aren't registered (you don't need those generally anyway).
152	too:
153	</p>
154
155	<pre caption="Adding openprom filesystem to /etc/fstab">
156	none /proc/openprom openpromfs defaults 0 0
157	</pre>	219	</p>
158		220
159	<p>	221	<p>
160	Double-check your <path>/etc/fstab</path>, save and quit to continue.	222	Double-check your <path>/etc/fstab</path>, save and quit to continue.
161	</p>	223	</p>
162		224
…		…
164	</subsection>	226	</subsection>
165	</section>	227	</section>
166	<section>	228	<section>
167	<title>Networking Information</title>	229	<title>Networking Information</title>
168	<subsection>	230	<subsection>
169	<title>Hostname, Domainname etc.</title>	231	<title>Host name, Domainname, etc</title>
170	<body>	232	<body>
171		233
172	<p>	234	<p>
173	One of the choices the user has to make is name his/her PC. This seems to be	235	One of the choices the user has to make is name his/her PC. This seems to be
174	quite easy, but <e>lots</e> of users are having difficulties finding the	236	quite easy, but <e>lots</e> of users are having difficulties finding the
175	appropriate name for their Linux-pc. To speed things up, know that any name you	237	appropriate name for their Linux-pc. To speed things up, know that any name you
176	choose can be changed afterwards. For all we care, you can just call your system	238	choose can be changed afterwards. For all we care, you can just call your system
177	<c>tux</c> and domain <c>homenetwork</c>.	239	<c>tux</c> and domain <c>homenetwork</c>.
178	</p>	240	</p>
179		241
180	<p>
181	We use these values in the next examples. First we set the hostname:
182	</p>
183
184	<pre caption="Setting the hostname">	242	<pre caption="Setting the host name">
185	# <i>nano -w /etc/conf.d/hostname</i>	243	# <i>nano -w /etc/conf.d/hostname</i>
186		244
187	<comment>(Set the HOSTNAME variable to your hostname)</comment>	245	<comment>(Set the HOSTNAME variable to your host name)</comment>
188	HOSTNAME="<i>tux</i>"	246	HOSTNAME="<i>tux</i>"
189	</pre>	247	</pre>
190		248
191	<p>	249	<p>
192	Second we set the domainname:	250	Second we set the domainname in <path>/etc/conf.d/net</path>:
193	</p>	251	</p>
194		252
195	<pre caption="Setting the domainname">	253	<pre caption="Setting the domainname">
196	# <i>nano -w /etc/conf.d/domainname</i>	254	# <i>nano -w /etc/conf.d/net</i>
197		255
198	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>	256	<comment>(Set the dns_domain variable to your domain name)</comment>
199	DNSDOMAIN="<i>homenetwork</i>"	257	dns_domain_lo="<i>homenetwork</i>"
200	</pre>	258	</pre>
201		259
202	<p>	260	<p>
203	If you have a NIS domain (if you don't know what that is, then you don't have	261	If you have a NIS domain (if you don't know what that is, then you don't have
204	one), you need to define that one too:	262	one), you need to define that one too:
205	</p>	263	</p>
206		264
207	<pre caption="Setting the NIS domainname">	265	<pre caption="Setting the NIS domainname">
208	# <i>nano -w /etc/conf.d/domainname</i>	266	# <i>nano -w /etc/conf.d/net</i>
209		267
210	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>	268	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
211	NISDOMAIN="<i>my-nisdomain</i>"	269	nis_domain_lo="<i>my-nisdomain</i>"
212	</pre>	270	</pre>
		271
		272	<note>
		273	For more information on configuring DNS and NIS, please read the examples
		274	provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
		275	<c>resolvconf-gentoo</c> to help manage your DNS/NIS setup.
		276	</note>
213		277
214	</body>	278	</body>
215	</subsection>	279	</subsection>
216	<subsection>	280	<subsection>
217	<title>Configuring your Network</title>	281	<title>Configuring your Network</title>
…		…
237	commented example that covers many different configurations is available in	301	commented example that covers many different configurations is available in
238	<path>/etc/conf.d/net.example</path>.	302	<path>/etc/conf.d/net.example</path>.
239	</p>	303	</p>
240		304
241	<p>	305	<p>
242	DHCP is used by default and does not require any further configuration.	306	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		307	client. This is described later in <uri
		308	link="?part=1&chap=9#networking-tools">Installing Necessary System
		309	Tools</uri>. Do not forget to install a DHCP client.
243	</p>	310	</p>
244		311
245	<p>	312	<p>
246	If you need to configure your network connection either because you need	313	If you need to configure your network connection either because you need
247	specific DHCP options or because you do not use DHCP at all, open	314	specific DHCP options or because you do not use DHCP at all, open
…		…
320	use <c>ln</c> to do this:	387	use <c>ln</c> to do this:
321	</p>	388	</p>
322		389
323	<pre caption="Creating extra initscripts">	390	<pre caption="Creating extra initscripts">
324	# <i>cd /etc/init.d</i>	391	# <i>cd /etc/init.d</i>
325	# <i>ln -s net.eth0 net.eth1</i>	392	# <i>ln -s net.lo net.eth1</i>
326	# <i>rc-update add net.eth1 default</i>	393	# <i>rc-update add net.eth1 default</i>
327	</pre>	394	</pre>
328		395
329	</body>	396	</body>
330	</subsection>	397	</subsection>
…		…
332	<title>Writing Down Network Information</title>	399	<title>Writing Down Network Information</title>
333	<body>	400	<body>
334		401
335	<p>	402	<p>
336	You now need to inform Linux about your network. This is defined in	403	You now need to inform Linux about your network. This is defined in
337	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for	404	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
338	hosts that aren't resolved by your nameserver. You need to define your system.	405	hosts that aren't resolved by your nameserver. You need to define your system.
339	You may also want to define other systems on your network if you don't want to	406	You may also want to define other systems on your network if you don't want to
340	set up your own internal DNS system.	407	set up your own internal DNS system.
341	</p>	408	</p>
342		409
…		…
356		423
357	<p>	424	<p>
358	Save and exit the editor to continue.	425	Save and exit the editor to continue.
359	</p>	426	</p>
360		427
361	<p>	428	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
362	If you don't have PCMCIA, you can now continue with <uri	429	If you don't have PCMCIA, you can now continue with <uri
363	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	430	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
364	following topic on PCMCIA.	431	following topic on PCMCIA.
365	</p>	432	</p>
366		433
367	</body>	434	</body>
368	</subsection>	435	</subsection>
369	<subsection>	436	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
370	<title>Optional: Get PCMCIA Working</title>	437	<title>Optional: Get PCMCIA Working</title>
371	<body>	438	<body>
372
373	<note>
374	pcmcia-cs is only available for x86, amd64 and ppc platforms.
375	</note>
376		439
377	<p>	440	<p>
378	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	441	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
379	includes users who will be working with a 2.6 kernel (even though they won't be	442	includes users who will be working with a 2.6 kernel (even though they won't be
380	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary	443	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
…		…
395	</pre>	458	</pre>
396		459
397	</body>	460	</body>
398	</subsection>	461	</subsection>
399	</section>	462	</section>
400	<section>	463
		464	<section id="sysinfo">
401	<title>System Information</title>	465	<title>System Information</title>
402	<subsection>	466	<subsection>
403	<title>Root Password</title>	467	<title>Root Password</title>
404	<body>	468	<body>
405		469
…		…
457	<p>	521	<p>
458	Take special care with the <c>KEYMAP</c> variable. If you select the wrong	522	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
459	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.	523	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
460	</p>	524	</p>
461		525
		526	<note test="func:keyval('arch')='SPARC'">
		527	Users of USB-based SPARC systems and SPARC clones might need to select an i386
		528	keymap (such as "us") instead of "sunkeymap".
462	<note>	529	</note>
463	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	530
464	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86	531	<note test="substring(func:keyval('arch'),1,3)='PPC'">
465	keymaps on most systems. Users who want to be able to use ADB keymaps on boot	532	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
466	have to enable ADB keycode sendings in their kernel and have to set a mac/ppc	533	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
467	keymap in <path>/etc/conf.d/keymaps</path>.	534	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
468	</note>	535	</note>
469		536
470	<p>	537	<p>
471	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and	538	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
472	exit.	539	exit.
…		…
480	<pre caption="Opening /etc/conf.d/clock">	547	<pre caption="Opening /etc/conf.d/clock">
481	# <i>nano -w /etc/conf.d/clock</i>	548	# <i>nano -w /etc/conf.d/clock</i>
482	</pre>	549	</pre>
483		550
484	<p>	551	<p>
485	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	552	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
486	the file. Otherwise you will notice some clock skew. Furthermore, Windows	553	to the file. Otherwise you will notice some clock skew.
487	assumes that your hardware clock uses local time, so if you want to dualboot,
488	you should set this variable appropriately, otherwise your clock will go crazy.
489	</p>	554	</p>
490		555
491	<p>	556	<p>
492	When you're finished configuring <path>/etc/conf.d/clock</path>, save and	557	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
493	exit.	558	exit.
494	</p>	559	</p>
495		560
		561	<p test="not(func:keyval('arch')='PPC64')">
		562	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		563	Tools</uri>.
496	<p>	564	</p>
497	If you are not installing Gentoo on IBM PPC64 hardware, continue with
498	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
499	</p>
500		565
501	</body>	566	</body>
502	</subsection>
503	<subsection>	567	</subsection>
		568	<subsection test="func:keyval('arch')='PPC64'">
504	<title>Configuring the Console</title>	569	<title>Configuring the Console</title>
505	<body>	570	<body>
506		571
507	<note>
508	The following section applies to the IBM PPC64 hardware platforms.
509	</note>
510
511	<p>	572	<p>
512	If you are running Gentoo on IBM PPC64 hardware and using a virtual console	573	If you are using a virtual console, you must uncomment the appropriate line in
513	you must uncomment the appropriate line in <path>/etc/inittab</path> for the	574	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
514	virtual console to spawn a login prompt.
515	</p>	575	</p>
516		576
517	<pre caption="Enabling hvc or hvsi support in /etc/inittab">	577	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
518	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0	578	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
519	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0	579	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

 Legend:



Removed from v.1.78
 


changed lines


 
Added in v.1.88
 Legend:



Removed from v.1.78
 


changed lines


 
Added in v.1.88
-Removed from v.1.78
+Added in v.1.88

	ViewVC Help
Powered by ViewVC 1.1.13