/[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.71		Revision 1.99
…		…
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.71 2005/08/13 21:03:21 jkt Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.99 2008/05/02 08:04:23 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.12</version>	17	<version>9.2</version>
12	<date>2005-08-13</date>	18	<date>2008-05-02</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 no valid fstab	77	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	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 <b>PPC</b>), don't copy it verbatim.	91	<path>/boot</path>, don't copy it.
84	</p>
85
86	<p>	92	</p>
		93
		94	<p>
87	In our default x86 partitioning example <path>/boot</path> is the	95	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
88	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.	96	usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
89	It needs to be checked during boot, so we would write down:	97	filesystem. It needs to be checked during boot, so we would write down:
90	</p>	98	</p>
91		99
92	<pre caption="An example /boot line for /etc/fstab">	100	<pre caption="An example /boot line for /etc/fstab">
93	/dev/hda1 /boot ext2 defaults 1 2	101	<keyval id="/boot"/> /boot ext2 defaults 1 2
94	</pre>	102	</pre>
95		103
96	<p>	104	<p>
97	Some users don't want their <path>/boot</path> partition to be mounted	105	Some users don't want their <path>/boot</path> partition to be mounted
98	automatically to improve their system's security. Those people should	106	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	107	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.	108	manually mount this partition every time you want to use it.
101	</p>	109	</p>
102		110
103	<p>	111	</body>
104	Now, to improve performance, most users would want to add the <c>noatime</c>	112	<body>
105	option as mountoption, which results in a faster system since access times	113
106	aren't registered (you don't need those generally anyway):
107	</p>	114	<p>
108		115	Add the rules that match your partitioning scheme and append rules for
109	<pre caption="An improved /boot line for /etc/fstab">	116	your CD-ROM drive(s), and of course, if you have other partitions or drives,
110	/dev/hda1 /boot ext2 defaults,noatime 1 2	117	for those too.
111	</pre>
112
113	<p>	118	</p>
114	If we continue with this, we would end up with the following three lines (for	119
115	<path>/boot</path>, <path>/</path> and the swap partition):
116	</p>	120	<p>
		121	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
		122	</p>
117		123
118	<pre caption="Three /etc/fstab lines">	124	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
119	/dev/hda1 /boot ext2 defaults,noatime 1 2	125	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
120	/dev/hda2 none swap sw 0 0	126	/dev/sda3 none swap sw 0 0
121	/dev/hda3 / ext3 noatime 0 1	127	/dev/sda4 / ext3 noatime 0 1
122	</pre>
123		128
124	<p>	129	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
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>	130	</pre>
129		131
130	<pre caption="A full /etc/fstab example">	132	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'">
131	/dev/hda1 /boot ext2 defaults,noatime 1 2	133	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
132	/dev/hda2 none swap sw 0 0	134	/dev/sda2 none swap sw 0 0
133	/dev/hda3 / ext3 noatime 0 1	135	/dev/sda3 / ext3 noatime 0 1
134		136
135	none /proc proc defaults 0 0	137	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
136	none /dev/shm tmpfs nodev,nosuid,noexec 0 0	138	</pre>
137		139
		140	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
		141	/dev/sda1 / ext3 noatime 0 1
		142	/dev/sda2 none swap sw 0 0
		143	/dev/sda4 /usr ext3 noatime 0 2
		144	/dev/sda5 /var ext3 noatime 0 2
		145	/dev/sda6 /home ext3 noatime 0 2
		146
		147	<comment># You must add the rules for openprom</comment>
		148	openprom /proc/openprom openpromfs defaults 0 0
		149
138	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	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')='PPC' or
		154	func:keyval('arch')='PPC64'">
		155	/dev/sda4 / ext3 noatime 0 1
		156	/dev/sda3 none swap sw 0 0
		157
		158	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
139	</pre>	159	</pre>
140		160
141	<p>	161	<p>
142	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for	162	<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	163	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.	164	<c>user</c> makes it possible for non-root users to mount the CD.
145	</p>	165	</p>
146		166
147	<p>	167	<p>
148	Now use the above example to create your <path>/etc/fstab</path>. If you are a	168	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	169	mount option, which results in a faster system since access times
150	<path>/etc/fstab</path>	170	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>	171	</p>
157		172
158	<p>	173	<p>
159	Double-check your <path>/etc/fstab</path>, save and quit to continue.	174	Double-check your <path>/etc/fstab</path>, save and quit to continue.
160	</p>	175	</p>
161		176
…		…
163	</subsection>	178	</subsection>
164	</section>	179	</section>
165	<section>	180	<section>
166	<title>Networking Information</title>	181	<title>Networking Information</title>
167	<subsection>	182	<subsection>
168	<title>Hostname, Domainname etc.</title>	183	<title>Host name, Domainname, etc</title>
169	<body>	184	<body>
170		185
171	<p>	186	<p>
172	One of the choices the user has to make is name his/her PC. This seems to be	187	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	188	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	189	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	190	choose can be changed afterwards. For all we care, you can just call your system
176	<c>tux</c> and domain <c>homenetwork</c>.	191	<c>tux</c> and domain <c>homenetwork</c>.
177	</p>	192	</p>
178		193
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">	194	<pre caption="Setting the host name">
184	# <i>nano -w /etc/conf.d/hostname</i>	195	# <i>nano -w /etc/conf.d/hostname</i>
185		196
186	<comment>(Set the HOSTNAME variable to your hostname)</comment>	197	<comment>(Set the HOSTNAME variable to your host name)</comment>
187	HOSTNAME="<i>tux</i>"	198	HOSTNAME="<i>tux</i>"
188	</pre>	199	</pre>
189		200
190	<p>	201	<p>
191	Second we set the domainname:	202	Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
		203	You only need a domain if your ISP or network administrator says so, or if you
		204	have a DNS server but not a DHCP server. You don't need to worry about DNS or
		205	domainnames if your networking is setup for DHCP.
192	</p>	206	</p>
193		207
194	<pre caption="Setting the domainname">	208	<pre caption="Setting the domainname">
195	# <i>nano -w /etc/conf.d/domainname</i>	209	# <i>nano -w /etc/conf.d/net</i>
196		210
197	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>	211	<comment>(Set the dns_domain variable to your domain name)</comment>
198	DNSDOMAIN="<i>homenetwork</i>"	212	dns_domain_lo="<i>homenetwork</i>"
199	</pre>	213	</pre>
		214
		215	<note>
		216	If you choose not to set a domainname, you can get rid of the "This is
		217	hostname.(none)" messages at your login screen by editing
		218	<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
		219	</note>
200		220
201	<p>	221	<p>
202	If you have a NIS domain (if you don't know what that is, then you don't have	222	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:	223	one), you need to define that one too:
204	</p>	224	</p>
205		225
206	<pre caption="Setting the NIS domainname">	226	<pre caption="Setting the NIS domainname">
207	# <i>nano -w /etc/conf.d/domainname</i>	227	# <i>nano -w /etc/conf.d/net</i>
208		228
209	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>	229	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
210	NISDOMAIN="<i>my-nisdomain</i>"	230	nis_domain_lo="<i>my-nisdomain</i>"
211	</pre>
212
213	<p>
214	Now add the <c>domainname</c> script to the default runlevel:
215	</p>	231	</pre>
216		232
217	<pre caption="Adding domainname to the default runlevel">	233	<note>
218	# <i>rc-update add domainname default</i>	234	For more information on configuring DNS and NIS, please read the examples
219	</pre>	235	provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
		236	<c>openresolv</c> to help manage your DNS/NIS setup.
		237	</note>
220		238
221	</body>	239	</body>
222	</subsection>	240	</subsection>
223	<subsection>	241	<subsection>
224	<title>Configuring your Network</title>	242	<title>Configuring your Network</title>
…		…
231	your Gentoo system permanently.	249	your Gentoo system permanently.
232	</p>	250	</p>
233		251
234	<note>	252	<note>
235	More detailed information about networking, including advanced topics like	253	More detailed information about networking, including advanced topics like
236	bonding, bridging, 802.11q VLANs or wireless networking is covered in the <uri	254	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
237	link="?part=4">Gentoo Network Configuration</uri> section.	255	link="?part=4">Gentoo Network Configuration</uri> section.
238	</note>	256	</note>
239		257
240	<p>	258	<p>
241	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	259	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
…		…
244	commented example that covers many different configurations is available in	262	commented example that covers many different configurations is available in
245	<path>/etc/conf.d/net.example</path>.	263	<path>/etc/conf.d/net.example</path>.
246	</p>	264	</p>
247		265
248	<p>	266	<p>
249	DHCP is used by default and does not require any further configuration.	267	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		268	client. This is described later in <uri
		269	link="?part=1&chap=9#networking-tools">Installing Necessary System
		270	Tools</uri>. Do not forget to install a DHCP client.
250	</p>	271	</p>
251		272
252	<p>	273	<p>
253	If you need to configure your network connection either because you need	274	If you need to configure your network connection either because you need
254	specific DHCP options or because you do not use DHCP at all, open	275	specific DHCP options or because you do not use DHCP at all, open
…		…
275	To enter your own IP address, netmask and gateway, you need	296	To enter your own IP address, netmask and gateway, you need
276	to set both <c>config_eth0</c> and <c>routes_eth0</c>:	297	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
277	</p>	298	</p>
278		299
279	<pre caption="Manually setting IP information for eth0">	300	<pre caption="Manually setting IP information for eth0">
280	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )	301	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" )	302	routes_eth0=( "default via 192.168.0.1" )
282	</pre>	303	</pre>
283		304
284	<p>	305	<p>
285	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and	306	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
286	<c>dhcp_eth0</c>:	307	<c>dhcp_eth0</c>:
…		…
311	<title>Automatically Start Networking at Boot</title>	332	<title>Automatically Start Networking at Boot</title>
312	<body>	333	<body>
313		334
314	<p>	335	<p>
315	To have your network interfaces activated at boot, you need to add them to the	336	To have your network interfaces activated at boot, you need to add them to the
316	default runlevel. If you have PCMCIA interfaces you should skip this action as	337	default runlevel.
317	the PCMCIA interfaces are started by the PCMCIA init script.
318	</p>	338	</p>
319		339
320	<pre caption="Adding net.eth0 to the default runlevel">	340	<pre caption="Adding net.eth0 to the default runlevel">
321	# <i>rc-update add net.eth0 default</i>	341	# <i>rc-update add net.eth0 default</i>
322	</pre>	342	</pre>
…		…
327	use <c>ln</c> to do this:	347	use <c>ln</c> to do this:
328	</p>	348	</p>
329		349
330	<pre caption="Creating extra initscripts">	350	<pre caption="Creating extra initscripts">
331	# <i>cd /etc/init.d</i>	351	# <i>cd /etc/init.d</i>
332	# <i>ln -s net.eth0 net.eth1</i>	352	# <i>ln -s net.lo net.eth1</i>
333	# <i>rc-update add net.eth1 default</i>	353	# <i>rc-update add net.eth1 default</i>
334	</pre>	354	</pre>
335		355
336	</body>	356	</body>
337	</subsection>	357	</subsection>
…		…
339	<title>Writing Down Network Information</title>	359	<title>Writing Down Network Information</title>
340	<body>	360	<body>
341		361
342	<p>	362	<p>
343	You now need to inform Linux about your network. This is defined in	363	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	364	<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	365	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),	366	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	367	set up your own internal DNS system.
348	open <path>/etc/hosts</path> and fill in the values:
349	</p>	368	</p>
350		369
351	<pre caption="Opening /etc/hosts">	370	<pre caption="Opening /etc/hosts">
352	# <i>nano -w /etc/hosts</i>	371	# <i>nano -w /etc/hosts</i>
353	</pre>	372	</pre>
354		373
355	<pre caption="Filling in the networking information">	374	<pre caption="Filling in the networking information">
356	127.0.0.1 localhost	375	<comment>(This defines the current system)</comment>
		376	127.0.0.1 tux.homenetwork tux localhost
		377
		378	<comment>(Define extra systems on your network,
		379	they need to have a static IP to be defined this way.)</comment>
357	192.168.0.5 jenny.homenetwork jenny	380	192.168.0.5 jenny.homenetwork jenny
358	192.168.0.6 benny.homenetwork benny	381	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>	382	</pre>
371		383
372	<p>	384	<p>
373	Save and exit the editor to continue.	385	Save and exit the editor to continue.
374	</p>	386	</p>
375		387
376	<p>	388	<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	389	If you don't have PCMCIA, you can now continue with <uri
378	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	390	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
379	following topic on PCMCIA.	391	following topic on PCMCIA.
380	</p>	392	</p>
381		393
382	</body>	394	</body>
383	</subsection>	395	</subsection>
384	<subsection>	396	<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>	397	<title>Optional: Get PCMCIA Working</title>
386	<body>	398	<body>
387		399
388	<note>
389	pcmcia-cs is only available for x86, amd64 and ppc platforms.
390	</note>
391
392	<p>	400	<p>
393	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	401	PCMCIA users should first install the <c>pcmciautils</c> package.
394	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
396	to avoid installing xorg-x11 at this moment:
397	</p>	402	</p>
398		403
399	<pre caption="Installing pcmcia-cs">	404	<pre caption="Installing pcmciautils">
400	# <i>USE="-X" emerge pcmcia-cs</i>	405	# <i>emerge pcmciautils</i>
401	</pre>
402
403	<p>
404	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
405	runlevel:
406	</p>
407
408	<pre caption="Adding pcmcia to the default runlevel">
409	# <i>rc-update add pcmcia default</i>
410	</pre>	406	</pre>
411		407
412	</body>	408	</body>
413	</subsection>	409	</subsection>
414	</section>	410	</section>
415	<section>	411
		412	<section id="sysinfo">
416	<title>System Information</title>	413	<title>System Information</title>
417	<subsection>	414	<subsection>
418	<title>Root Password</title>	415	<title>Root Password</title>
419	<body>	416	<body>
420		417
…		…
422	First we set the root password by typing:	419	First we set the root password by typing:
423	</p>	420	</p>
424		421
425	<pre caption="Setting the root password">	422	<pre caption="Setting the root password">
426	# <i>passwd</i>	423	# <i>passwd</i>
427	</pre>
428
429	<p>
430	If you want root to be able to log on through the serial console, add
431	<c>tts/0</c> to <path>/etc/securetty</path>:
432	</p>
433
434	<pre caption="Adding tts/0 to /etc/securetty">
435	# <i>echo "tts/0" >> /etc/securetty</i>
436	</pre>	424	</pre>
437		425
438	</body>	426	</body>
439	</subsection>	427	</subsection>
440	<subsection>	428	<subsection>
…		…
472	<p>	460	<p>
473	Take special care with the <c>KEYMAP</c> variable. If you select the wrong	461	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.	462	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
475	</p>	463	</p>
476		464
477	<note>	465	<note test="substring(func:keyval('arch'),1,3)='PPC'">
478	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
479	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
480	keymaps on most systems. Users who want to be able to use ADB keymaps on boot	466	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	467	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
482	keymap in <path>/etc/conf.d/keymaps</path>.	468	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
483	</note>	469	</note>
484		470
485	<p>	471	<p>
486	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and	472	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
487	exit.	473	exit.
…		…
495	<pre caption="Opening /etc/conf.d/clock">	481	<pre caption="Opening /etc/conf.d/clock">
496	# <i>nano -w /etc/conf.d/clock</i>	482	# <i>nano -w /etc/conf.d/clock</i>
497	</pre>	483	</pre>
498		484
499	<p>	485	<p>
500	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	486	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.	487	to the file. Otherwise you will notice some clock skew.
		488	</p>
		489
		490	<p>
		491	You should define the timezone that you previously copied to
		492	<path>/etc/localtime</path> so that further upgrades of the
		493	<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
		494	automatically. For instance, if you used the GMT timezone, you would add
		495	<c>TIMEZONE="GMT"</c>
502	</p>	496	</p>
503		497
504	<p>	498	<p>
505	When you're finished configuring <path>/etc/conf.d/clock</path>, save and	499	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
506	exit.	500	exit.
507	</p>	501	</p>
508		502
		503	<p test="not(func:keyval('arch')='PPC64')">
		504	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		505	Tools</uri>.
509	<p>	506	</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		507
514	</body>	508	</body>
515	</subsection>
516	<subsection>	509	</subsection>
		510	<subsection test="func:keyval('arch')='PPC64'">
517	<title>Configuring the Console</title>	511	<title>Configuring the Console</title>
518	<body>	512	<body>
519		513
520	<note>
521	The following section applies to the IBM PPC64 hardware platforms.
522	</note>
523
524	<p>	514	<p>
525	If you are running Gentoo on IBM PPC64 hardware and using a virtual console	515	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	516	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
527	virtual console to spawn a login prompt.
528	</p>	517	</p>
529		518
530	<pre caption="Enabling hvc or hvsi support in /etc/inittab">	519	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
531	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0	520	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
532	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0	521	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

 Legend:



Removed from v.1.71
 


changed lines


 
Added in v.1.99
 Legend:



Removed from v.1.71
 


changed lines


 
Added in v.1.99
-Removed from v.1.71
+Added in v.1.99

	ViewVC Help
Powered by ViewVC 1.1.20