/[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.72		Revision 1.82
…		…
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.72 2005/08/15 09:00:27 swift Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.82 2006/09/04 09:11:39 nightmorph Exp $ -->
8		8
9	<sections>	9	<sections>
10		10
11	<version>2.13</version>	11	<version>7.1</version>
12	<date>2005-08-15</date>	12	<date>2006-09-04</date>
13		13
14	<section>	14	<section>
15	<title>Filesystem Information</title>	15	<title>Filesystem Information</title>
16	<subsection>	16	<subsection>
17	<title>What is fstab?</title>	17	<title>What is fstab?</title>
18	<body>	18	<body>
19		19
20	<p>	20	<p>
21	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
22	<path>/etc/fstab</path>. This file contains the mountpoints of those partitions	22	<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	23	(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	24	and with what special options (automatically or not, whether users can mount
25	them or not, etc.)	25	them or not, etc.)
26	</p>	26	</p>
27		27
…		…
41	<li>	41	<li>
42	The first field shows the <b>partition</b> described (the path to the device	42	The first field shows the <b>partition</b> described (the path to the device
43	file)	43	file)
44	</li>	44	</li>
45	<li>	45	<li>
46	The second field shows the <b>mountpoint</b> at which the partition should be	46	The second field shows the <b>mount point</b> at which the partition should be
47	mounted	47	mounted
48	</li>	48	</li>
49	<li>	49	<li>
50	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
51	</li>	51	</li>
52	<li>	52	<li>
53	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it	53	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,	54	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	55	you are encouraged to read the mount man page (<c>man mount</c>) for a full
56	listing. Multiple mountoptions are comma-separated.	56	listing. Multiple mount options are comma-separated.
57	</li>	57	</li>
58	<li>	58	<li>
59	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
60	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).
61	</li>	61	</li>
…		…
65	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>
66	(or <c>0</c> if a filesystem check isn't necessary).	66	(or <c>0</c> if a filesystem check isn't necessary).
67	</li>	67	</li>
68	</ul>	68	</ul>
69		69
70	<p>	70	<impo>
71	The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab	71	The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72	file</e>, so start <c>nano</c> (or your favorite editor) to create your	72	fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>.
73	<path>/etc/fstab</path>:	73	</impo>
74	</p>
75		74
76	<pre caption="Opening /etc/fstab">	75	<pre caption="Opening /etc/fstab">
77	# <i>nano -w /etc/fstab</i>	76	# <i>nano -w /etc/fstab</i>
78	</pre>	77	</pre>
79		78
		79	</body>
		80	<body test="func:keyval('/boot')">
		81
80	<p>	82	<p>
81	Let us take a look at how we write down the options for the <path>/boot</path>	83	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	84	partition. This is just an example, if you didn't or couldn't create a
83	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.	85	<path>/boot</path>, don't copy it.
84	</p>
85
86	<p>	86	</p>
		87
		88	<p test="contains(func:keyval('/boot'), '/dev/hd')">
87	In our default x86 partitioning example <path>/boot</path> is the	89	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
88	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.	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
89	It needs to be checked during boot, so we would write down:	92	filesystem. It needs to be checked during boot, so we would write down:
		93	</p>
		94
		95	<p test="contains(func:keyval('/boot'), '/dev/sd')">
		96	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
		98	filesystem. It needs to be checked during boot, so we would write down:
90	</p>	99	</p>
91		100
92	<pre caption="An example /boot line for /etc/fstab">	101	<pre caption="An example /boot line for /etc/fstab">
93	/dev/hda1 /boot ext2 defaults 1 2	102	<keyval id="/boot"/> /boot ext2 defaults 1 2
94	</pre>	103	</pre>
95		104
96	<p>	105	<p>
97	Some users don't want their <path>/boot</path> partition to be mounted	106	Some users don't want their <path>/boot</path> partition to be mounted
98	automatically to improve their system's security. Those people should	107	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	108	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.	109	manually mount this partition every time you want to use it.
101	</p>	110	</p>
102		111
		112	</body>
		113	<body>
		114
		115	<p test="not(func:keyval('arch')='SPARC')">
		116	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.
103	<p>	119	</p>
104	Now, to improve performance, most users would want to add the <c>noatime</c>
105	option as mountoption, which results in a faster system since access times
106	aren't registered (you don't need those generally anyway):
107	</p>
108		120
109	<pre caption="An improved /boot line for /etc/fstab">	121	<p test="func:keyval('arch')='SPARC'">
110	/dev/hda1 /boot ext2 defaults,noatime 1 2	122	Add the rules that match your partitioning schema and append rules for
111	</pre>	123	<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
112		124	drive(s), and of course, if you have other partitions or drives, for those too.
113	<p>	125	</p>
114	If we continue with this, we would end up with the following three lines (for	126
115	<path>/boot</path>, <path>/</path> and the swap partition):
116	</p>	127	<p>
117		128	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
118	<pre caption="Three /etc/fstab lines">
119	/dev/hda1 /boot ext2 defaults,noatime 1 2
120	/dev/hda2 none swap sw 0 0
121	/dev/hda3 / ext3 noatime 0 1
122	</pre>
123
124	<p>	129	</p>
125	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
126	(required) and for your CD-ROM drive (and of course, if you have other
127	partitions or drives, for those too):
128	</p>
129		130
130	<pre caption="A full /etc/fstab example">	131	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
131	/dev/hda1 /boot ext2 defaults,noatime 1 2	132	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132	/dev/hda2 none swap sw 0 0	133	/dev/hda2 none swap sw 0 0
133	/dev/hda3 / ext3 noatime 0 1	134	/dev/hda3 / ext3 noatime 0 1
134		135
135	none /proc proc defaults 0 0	136	none /proc proc defaults 0 0
136	none /dev/shm tmpfs nodev,nosuid,noexec 0 0	137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
137		138
		139	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		140	</pre>
		141
		142	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
		143	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
		144	/dev/sda3 none swap sw 0 0
		145	/dev/sda4 / ext3 noatime 0 1
		146
		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
		151	</pre>
		152
		153	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'">
		154	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
		155	/dev/sda2 none swap sw 0 0
		156	/dev/sda3 / ext3 noatime 0 1
		157
		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
		162	</pre>
		163
		164	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
		165	/dev/sda1 / ext3 noatime 0 1
		166	/dev/sda2 none swap sw 0 0
		167	/dev/sda4 /usr ext3 noatime 0 2
		168	/dev/sda5 /var ext3 noatime 0 2
		169	/dev/sda6 /home ext3 noatime 0 2
		170
		171	none /proc/openprom openpromfs defaults 0 0
		172	none /proc proc defaults 0 0
		173	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
		174
138	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	175	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		176	</pre>
		177
		178	<note test="func:keyval('arch')='PPC'">
		179	There are important variations between PPC machine types. Please make sure you
		180	adapt the following example to your system.
		181	</note>
		182
		183	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'">
		184	/dev/hda4 / ext3 noatime 0 1
		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
		195	/dev/sda3 none swap sw 0 0
		196
		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
139	</pre>	201	</pre>
140		202
141	<p>	203	<p>
142	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for	204	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
143	removable media as they can be created with one of many filesystems) and	205	removable media as they can be created with one of many filesystems) and
144	<c>user</c> makes it possible for non-root users to mount the CD.	206	<c>user</c> makes it possible for non-root users to mount the CD.
145	</p>	207	</p>
146		208
147	<p>	209	<p>
148	Now use the above example to create your <path>/etc/fstab</path>. If you are a	210	To improve performance, most users would want to add the <c>noatime</c>
149	<b>SPARC</b>-user, you should add the following line to your	211	mount option, which results in a faster system since access times
150	<path>/etc/fstab</path>	212	aren't registered (you don't need those generally anyway).
151	too:
152	</p>
153
154	<pre caption="Adding openprom filesystem to /etc/fstab">
155	none /proc/openprom openpromfs defaults 0 0
156	</pre>	213	</p>
157		214
158	<p>	215	<p>
159	Double-check your <path>/etc/fstab</path>, save and quit to continue.	216	Double-check your <path>/etc/fstab</path>, save and quit to continue.
160	</p>	217	</p>
161		218
…		…
163	</subsection>	220	</subsection>
164	</section>	221	</section>
165	<section>	222	<section>
166	<title>Networking Information</title>	223	<title>Networking Information</title>
167	<subsection>	224	<subsection>
168	<title>Hostname, Domainname etc.</title>	225	<title>Host name</title>
169	<body>	226	<body>
170		227
171	<p>	228	<p>
172	One of the choices the user has to make is name his/her PC. This seems to be	229	One of the choices the user has to make is name his/her PC. This seems to be
173	quite easy, but <e>lots</e> of users are having difficulties finding the	230	quite easy, but <e>lots</e> of users are having difficulties finding the
174	appropriate name for their Linux-pc. To speed things up, know that any name you	231	appropriate name for their Linux-pc. To speed things up, know that any name you
175	choose can be changed afterwards. For all we care, you can just call your system	232	choose can be changed afterwards. For all we care, you can just call your system
176	<c>tux</c> and domain <c>homenetwork</c>.	233	<c>tux</c> and domain <c>homenetwork</c>.
177	</p>	234	</p>
178		235
179	<p>
180	We use these values in the next examples. First we set the hostname:
181	</p>
182
183	<pre caption="Setting the hostname">	236	<pre caption="Setting the host name">
184	# <i>nano -w /etc/conf.d/hostname</i>	237	# <i>nano -w /etc/conf.d/hostname</i>
185		238
186	<comment>(Set the HOSTNAME variable to your hostname)</comment>	239	<comment>(Set the HOSTNAME variable to your host name)</comment>
187	HOSTNAME="<i>tux</i>"	240	HOSTNAME="<i>tux</i>"
188	</pre>
189
190	<p>
191	Second we set the domainname:
192	</p>
193
194	<pre caption="Setting the domainname">
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>"
199	</pre>
200
201	<p>
202	If you have a NIS domain (if you don't know what that is, then you don't have
203	one), you need to define that one too:
204	</p>
205
206	<pre caption="Setting the NIS domainname">
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>"
211	</pre>
212
213	<p>
214	Now add the <c>domainname</c> script to the default runlevel:
215	</p>
216
217	<pre caption="Adding domainname to the default runlevel">
218	# <i>rc-update add domainname default</i>
219	</pre>	241	</pre>
220		242
221	</body>	243	</body>
222	</subsection>	244	</subsection>
223	<subsection>	245	<subsection>
…		…
275	To enter your own IP address, netmask and gateway, you need	297	To enter your own IP address, netmask and gateway, you need
276	to set both <c>config_eth0</c> and <c>routes_eth0</c>:	298	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
277	</p>	299	</p>
278		300
279	<pre caption="Manually setting IP information for eth0">	301	<pre caption="Manually setting IP information for eth0">
280	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )	302	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
281	routes_eth0=( "default gw 192.168.0.1" )	303	routes_eth0=( "default gw 192.168.0.1" )
282	</pre>	304	</pre>
283		305
284	<p>	306	<p>
285	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and	307	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
…		…
327	use <c>ln</c> to do this:	349	use <c>ln</c> to do this:
328	</p>	350	</p>
329		351
330	<pre caption="Creating extra initscripts">	352	<pre caption="Creating extra initscripts">
331	# <i>cd /etc/init.d</i>	353	# <i>cd /etc/init.d</i>
332	# <i>ln -s net.eth0 net.eth1</i>	354	# <i>ln -s net.lo net.eth1</i>
333	# <i>rc-update add net.eth1 default</i>	355	# <i>rc-update add net.eth1 default</i>
334	</pre>	356	</pre>
335		357
336	</body>	358	</body>
337	</subsection>	359	</subsection>
…		…
339	<title>Writing Down Network Information</title>	361	<title>Writing Down Network Information</title>
340	<body>	362	<body>
341		363
342	<p>	364	<p>
343	You now need to inform Linux about your network. This is defined in	365	You now need to inform Linux about your network. This is defined in
344	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	366	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
345	for hosts that aren't resolved by your nameserver. For instance, if your	367	hosts that aren't resolved by your nameserver. You need to define your system.
346	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	368	You may also want to define other systems on your network if you don't want to
347	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	369	set up your own internal DNS system.
348	open <path>/etc/hosts</path> and fill in the values:
349	</p>	370	</p>
350		371
351	<pre caption="Opening /etc/hosts">	372	<pre caption="Opening /etc/hosts">
352	# <i>nano -w /etc/hosts</i>	373	# <i>nano -w /etc/hosts</i>
353	</pre>	374	</pre>
354		375
355	<pre caption="Filling in the networking information">	376	<pre caption="Filling in the networking information">
356	127.0.0.1 localhost	377	<comment>(This defines the current system)</comment>
		378	127.0.0.1 tux.homenetwork tux localhost
		379
		380	<comment>(Define extra systems on your network,
		381	they need to have a static IP to be defined this way.)</comment>
357	192.168.0.5 jenny.homenetwork jenny	382	192.168.0.5 jenny.homenetwork jenny
358	192.168.0.6 benny.homenetwork benny	383	192.168.0.6 benny.homenetwork benny
359	192.168.0.7 tux.homenetwork tux
360	</pre>
361
362	<p>
363	If your system is the only system (or the nameservers handle all name
364	resolution) a single line is sufficient. For instance, if you want to call your
365	system <c>tux</c>:
366	</p>
367
368	<pre caption="/etc/hosts for lonely or fully integrated PCs">
369	127.0.0.1 localhost tux
370	</pre>	384	</pre>
371		385
372	<p>	386	<p>
373	Save and exit the editor to continue.	387	Save and exit the editor to continue.
374	</p>	388	</p>
375		389
376	<p>	390	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
377	If you don't have PCMCIA, you can now continue with <uri	391	If you don't have PCMCIA, you can now continue with <uri
378	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	392	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
379	following topic on PCMCIA.	393	following topic on PCMCIA.
380	</p>	394	</p>
381		395
382	</body>	396	</body>
383	</subsection>	397	</subsection>
384	<subsection>	398	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
385	<title>Optional: Get PCMCIA Working</title>	399	<title>Optional: Get PCMCIA Working</title>
386	<body>	400	<body>
387
388	<note>
389	pcmcia-cs is only available for x86, amd64 and ppc platforms.
390	</note>
391		401
392	<p>	402	<p>
393	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	403	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
394	includes users who will be working with a 2.6 kernel (even though they won't be	404	includes users who will be working with a 2.6 kernel (even though they won't be
395	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary	405	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
…		…
410	</pre>	420	</pre>
411		421
412	</body>	422	</body>
413	</subsection>	423	</subsection>
414	</section>	424	</section>
415	<section>	425
		426	<section id="sysinfo">
416	<title>System Information</title>	427	<title>System Information</title>
417	<subsection>	428	<subsection>
418	<title>Root Password</title>	429	<title>Root Password</title>
419	<body>	430	<body>
420		431
…		…
472	<p>	483	<p>
473	Take special care with the <c>KEYMAP</c> variable. If you select the wrong	484	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
474	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.	485	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
475	</p>	486	</p>
476		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".
477	<note>	491	</note>
478	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	492
479	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86	493	<note test="substring(func:keyval('arch'),1,3)='PPC'">
480	keymaps on most systems. Users who want to be able to use ADB keymaps on boot	494	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
481	have to enable ADB keycode sendings in their kernel and have to set a mac/ppc	495	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
482	keymap in <path>/etc/conf.d/keymaps</path>.	496	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
483	</note>	497	</note>
484		498
485	<p>	499	<p>
486	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and	500	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
487	exit.	501	exit.
…		…
495	<pre caption="Opening /etc/conf.d/clock">	509	<pre caption="Opening /etc/conf.d/clock">
496	# <i>nano -w /etc/conf.d/clock</i>	510	# <i>nano -w /etc/conf.d/clock</i>
497	</pre>	511	</pre>
498		512
499	<p>	513	<p>
500	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	514	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
501	the file. Otherwise you will notice some clock skew.	515	to the file. Otherwise you will notice some clock skew.
502	</p>	516	</p>
503		517
504	<p>	518	<p>
505	When you're finished configuring <path>/etc/conf.d/clock</path>, save and	519	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
506	exit.	520	exit.
507	</p>	521	</p>
508		522
		523	<p test="not(func:keyval('arch')='PPC64')">
		524	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		525	Tools</uri>.
509	<p>	526	</p>
510	If you are not installing Gentoo on IBM PPC64 hardware, continue with
511	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
512	</p>
513		527
514	</body>	528	</body>
515	</subsection>
516	<subsection>	529	</subsection>
		530	<subsection test="func:keyval('arch')='PPC64'">
517	<title>Configuring the Console</title>	531	<title>Configuring the Console</title>
518	<body>	532	<body>
519		533
520	<note>
521	The following section applies to the IBM PPC64 hardware platforms.
522	</note>
523
524	<p>	534	<p>
525	If you are running Gentoo on IBM PPC64 hardware and using a virtual console	535	If you are using a virtual console, you must uncomment the appropriate line in
526	you must uncomment the appropriate line in <path>/etc/inittab</path> for the	536	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
527	virtual console to spawn a login prompt.
528	</p>	537	</p>
529		538
530	<pre caption="Enabling hvc or hvsi support in /etc/inittab">	539	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
531	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0	540	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
532	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0	541	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

 Legend:



Removed from v.1.72
 


changed lines


 
Added in v.1.82
 Legend:



Removed from v.1.72
 


changed lines


 
Added in v.1.82
-Removed from v.1.72
+Added in v.1.82

	ViewVC Help
Powered by ViewVC 1.1.13