/[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.64		Revision 1.85
1	<?xml version='1.0' encoding='UTF-8'?>	1	<?xml version='1.0' encoding='UTF-8'?>
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/2.5 -->
6		6
7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.64 2005/06/11 18:25:09 fox2mike Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.85 2006/10/21 01:13:51 nightmorph Exp $ -->
8		8
9	<sections>	9	<sections>
10		10
11	<version>2.6</version>	11	<version>7.4</version>
12	<date>2005-06-11</date>	12	<date>2006-10-20</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, Domainname, etc</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>echo tux > /etc/hostname</i>	237	# <i>nano -w /etc/conf.d/hostname</i>
185	</pre>
186		238
		239	<comment>(Set the HOSTNAME variable to your host name)</comment>
		240	HOSTNAME="<i>tux</i>"
		241	</pre>
		242
187	<p>	243	<p>
188	Second we set the domainname:	244	Second we set the domainname in <path>/etc/conf.d/net</path>:
189	</p>	245	</p>
190		246
191	<pre caption="Setting the domainname">	247	<pre caption="Setting the domainname">
192	# <i>echo homenetwork > /etc/dnsdomainname</i>	248	# <i>nano -w /etc/conf.d/net</i>
		249
		250	<comment>(Set the dns_domain variable to your domain name)</comment>
		251	dns_domain_lo="<i>homenetwork</i>"
193	</pre>	252	</pre>
194		253
195	<p>	254	<p>
196	If you have a NIS domain (if you don't know what that is, then you don't have	255	If you have a NIS domain (if you don't know what that is, then you don't have
197	one), you need to define that one too:	256	one), you need to define that one too:
198	</p>	257	</p>
199		258
200	<pre caption="Setting the NIS domainname">	259	<pre caption="Setting the NIS domainname">
201	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	260	# <i>nano -w /etc/conf.d/net</i>
202	</pre>
203		261
204	<p>	262	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
205	Now add the <c>domainname</c> script to the default runlevel:	263	nis_domain_lo="<i>my-nisdomain</i>"
206	</p>	264	</pre>
207		265
208	<pre caption="Adding domainname to the default runlevel">	266	<note>
209	# <i>rc-update add domainname default</i>	267	For more information on configuring DNS and NIS, please read the examples
210	</pre>	268	provided in <path>/etc/conf.d/net.example</path>.
		269	</note>
211		270
212	</body>	271	</body>
213	</subsection>	272	</subsection>
214	<subsection>	273	<subsection>
215	<title>Configuring your Network</title>	274	<title>Configuring your Network</title>
216	<body>	275	<body>
217		276
218	<p>	277	<p>
219	Before you get that "Hey, we've had that already"-feeling, you should remember	278	Before you get that "Hey, we've had that already"-feeling, you should remember
220	that the networking you set up in the beginning of the gentoo installation was	279	that the networking you set up in the beginning of the Gentoo installation was
221	just for the installation. Right now you are going to configure networking for	280	just for the installation. Right now you are going to configure networking for
222	your Gentoo system permanently.	281	your Gentoo system permanently.
223	</p>	282	</p>
224		283
		284	<note>
		285	More detailed information about networking, including advanced topics like
		286	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
		287	link="?part=4">Gentoo Network Configuration</uri> section.
		288	</note>
		289
225	<p>	290	<p>
226	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	291	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
227	a straightforward yet not intuitive syntax if you don't know how to set up	292	a straightforward yet not intuitive syntax if you don't know how to set up
228	networking manually. But don't fear, we'll explain everything :)	293	networking manually. But don't fear, we'll explain everything. A fully
229	</p>	294	commented example that covers many different configurations is available in
230		295	<path>/etc/conf.d/net.example</path>.
231	<p>	296	</p>
		297
		298	<p>
		299	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		300	client. This is described later in <uri
		301	link="?part=1&chap=9#networking-tools">Installing Necessary System
		302	Tools</uri>. Do not forget to install a DHCP client.
		303	</p>
		304
		305	<p>
		306	If you need to configure your network connection either because you need
		307	specific DHCP options or because you do not use DHCP at all, open
232	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>	308	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233	is used in this example):	309	this example):
234	</p>	310	</p>
235		311
236	<pre caption="Opening /etc/conf.d/net for editing">	312	<pre caption="Opening /etc/conf.d/net for editing">
237	# <i>nano -w /etc/conf.d/net</i>	313	# <i>nano -w /etc/conf.d/net</i>
238	</pre>	314	</pre>
239		315
240	<p>	316	<p>
241	The first variable you'll find is called <c>config_eth0</c>. As you can probably	317	You will see the following file:
242	imagine, this variable configured the eth0 network interface. If the interface	318	</p>
243	needs to automatically obtain an IP address through DHCP, you should set it	319
244	like so:	320	<pre caption="Default /etc/conf.d/net">
		321	# This blank configuration will automatically use DHCP for any net.*
		322	# scripts in /etc/init.d. To create a more complete configuration,
		323	# please review /etc/conf.d/net.example and save your configuration
		324	# in /etc/conf.d/net (this file :]!).
		325	</pre>
		326
		327	<p>
		328	To enter your own IP address, netmask and gateway, you need
		329	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
		330	</p>
		331
		332	<pre caption="Manually setting IP information for eth0">
		333	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
		334	routes_eth0=( "default gw 192.168.0.1" )
		335	</pre>
		336
		337	<p>
		338	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
		339	<c>dhcp_eth0</c>:
245	</p>	340	</p>
246		341
247	<pre caption="Automatically obtaining an IP address for eth0">	342	<pre caption="Automatically obtaining an IP address for eth0">
248	config_eth0=( "dhcp" )	343	config_eth0=( "dhcp" )
		344	dhcp_eth0="nodns nontp nonis"
249	</pre>	345	</pre>
250		346
251	<p>
252	However, if you have to enter your own IP address, netmask and gateway, you need
253	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
254	</p>	347	<p>
255		348	Please read <path>/etc/conf.d/net.example</path> for a list of all available
256	<pre caption="Manually setting IP information for eth0">	349	options.
257	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
258	routes_eth0=( "default gw 192.168.0.1" )
259	</pre>	350	</p>
260		351
261	<p>	352	<p>
262	If you have several network interfaces repeat the above steps for	353	If you have several network interfaces repeat the above steps for
263	<c>config_eth1</c>, <c>config_eth2</c>, etc.	354	<c>config_eth1</c>, <c>config_eth2</c>, etc.
264	</p>	355	</p>
…		…
289	use <c>ln</c> to do this:	380	use <c>ln</c> to do this:
290	</p>	381	</p>
291		382
292	<pre caption="Creating extra initscripts">	383	<pre caption="Creating extra initscripts">
293	# <i>cd /etc/init.d</i>	384	# <i>cd /etc/init.d</i>
294	# <i>ln -s net.eth0 net.eth1</i>	385	# <i>ln -s net.lo net.eth1</i>
295	# <i>rc-update add net.eth1 default</i>	386	# <i>rc-update add net.eth1 default</i>
296	</pre>	387	</pre>
297		388
298	</body>	389	</body>
299	</subsection>	390	</subsection>
…		…
301	<title>Writing Down Network Information</title>	392	<title>Writing Down Network Information</title>
302	<body>	393	<body>
303		394
304	<p>	395	<p>
305	You now need to inform Linux about your network. This is defined in	396	You now need to inform Linux about your network. This is defined in
306	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	397	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
307	for hosts that aren't resolved by your nameserver. For instance, if your	398	hosts that aren't resolved by your nameserver. You need to define your system.
308	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	399	You may also want to define other systems on your network if you don't want to
309	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	400	set up your own internal DNS system.
310	open <path>/etc/hosts</path> and fill in the values:
311	</p>	401	</p>
312		402
313	<pre caption="Opening /etc/hosts">	403	<pre caption="Opening /etc/hosts">
314	# <i>nano -w /etc/hosts</i>	404	# <i>nano -w /etc/hosts</i>
315	</pre>	405	</pre>
316		406
317	<pre caption="Filling in the networking information">	407	<pre caption="Filling in the networking information">
318	127.0.0.1 localhost	408	<comment>(This defines the current system)</comment>
		409	127.0.0.1 tux.homenetwork tux localhost
		410
		411	<comment>(Define extra systems on your network,
		412	they need to have a static IP to be defined this way.)</comment>
319	192.168.0.5 jenny.homenetwork jenny	413	192.168.0.5 jenny.homenetwork jenny
320	192.168.0.6 benny.homenetwork benny	414	192.168.0.6 benny.homenetwork benny
321	192.168.0.7 tux.homenetwork tux
322	</pre>
323
324	<p>
325	If your system is the only system (or the nameservers handle all name
326	resolution) a single line is sufficient. For instance, if you want to call your
327	system <c>tux</c>:
328	</p>
329
330	<pre caption="/etc/hosts for lonely or fully integrated PCs">
331	127.0.0.1 localhost tux
332	</pre>	415	</pre>
333		416
334	<p>	417	<p>
335	Save and exit the editor to continue.	418	Save and exit the editor to continue.
336	</p>	419	</p>
337		420
338	<p>	421	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
339	If you don't have PCMCIA, you can now continue with <uri	422	If you don't have PCMCIA, you can now continue with <uri
340	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	423	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
341	following topic on PCMCIA.	424	following topic on PCMCIA.
342	</p>	425	</p>
343		426
344	</body>	427	</body>
345	</subsection>	428	</subsection>
346	<subsection>	429	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
347	<title>Optional: Get PCMCIA Working</title>	430	<title>Optional: Get PCMCIA Working</title>
348	<body>	431	<body>
349
350	<note>
351	pcmcia-cs is only available for x86, amd64 and ppc platforms.
352	</note>
353		432
354	<p>	433	<p>
355	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	434	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
356	includes users who will be working with a 2.6 kernel (even though they won't be	435	includes users who will be working with a 2.6 kernel (even though they won't be
357	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary	436	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
…		…
372	</pre>	451	</pre>
373		452
374	</body>	453	</body>
375	</subsection>	454	</subsection>
376	</section>	455	</section>
377	<section>	456
		457	<section id="sysinfo">
378	<title>System Information</title>	458	<title>System Information</title>
379	<subsection>	459	<subsection>
380	<title>Root Password</title>	460	<title>Root Password</title>
381	<body>	461	<body>
382		462
…		…
411	<pre caption="Opening /etc/rc.conf">	491	<pre caption="Opening /etc/rc.conf">
412	# <i>nano -w /etc/rc.conf</i>	492	# <i>nano -w /etc/rc.conf</i>
413	</pre>	493	</pre>
414		494
415	<p>	495	<p>
		496	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		497	</p>
		498
		499	<p>
416	As you can see, this file is well commented to help you set up the necessary	500	As you can see, this file is well commented to help you set up the necessary
417	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	501	configuration variables. You can configure your system to use unicode and
418	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	502	define your default editor and your display manager (like gdm or kdm).
419	your keyboard.	503	</p>
		504
420	</p>	505	<p>
		506	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		507	Edit it to configure your keyboard.
		508	</p>
421		509
422	<note>	510	<pre caption="Opening /etc/conf.d/keymaps">
		511	# <i>nano -w /etc/conf.d/keymaps</i>
		512	</pre>
		513
		514	<p>
		515	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
		516	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
		517	</p>
		518
		519	<note test="func:keyval('arch')='SPARC'">
423	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	520	Users of USB-based SPARC systems and SPARC clones might need to select an i386
424	select an i386 keymap (such as "us") instead of "sunkeymap".	521	keymap (such as "us") instead of "sunkeymap".
425	</note>	522	</note>
426		523
427	<p>	524	<note test="substring(func:keyval('arch'),1,3)='PPC'">
428	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	525	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
429	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	526	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
430	to set a mac/ppc keymap in <path>rc.conf</path>.	527	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
		528	</note>
		529
431	</p>	530	<p>
432		531	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
		532	exit.
433	<p>	533	</p>
		534
		535	<p>
		536	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		537	according to your needs.
		538	</p>
		539
		540	<pre caption="Opening /etc/conf.d/clock">
		541	# <i>nano -w /etc/conf.d/clock</i>
		542	</pre>
		543
		544	<p>
434	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	545	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
435	the file. Otherwise you will notice some clock skew.	546	to the file. Otherwise you will notice some clock skew.
436	</p>
437
438	<p>	547	</p>
		548
		549	<p>
439	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.	550	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
440	</p>	551	exit.
441
442	<p>	552	</p>
443	If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with	553
		554	<p test="not(func:keyval('arch')='PPC64')">
444	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.	555	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		556	Tools</uri>.
445	</p>	557	</p>
446		558
447	</body>	559	</body>
448	</subsection>
449	<subsection>	560	</subsection>
		561	<subsection test="func:keyval('arch')='PPC64'">
450	<title>Configuring the Console</title>	562	<title>Configuring the Console</title>
451	<body>	563	<body>
452		564
453	<note>
454	The following section applies to the IBM POWER5 and JS20 hardware platforms.
455	</note>
456
457	<p>
458	If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
459	the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
460	</p>	565	<p>
		566	If you are using a virtual console, you must uncomment the appropriate line in
		567	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
		568	</p>
461		569
462	<pre caption="Enabling hvc support in /etc/inittab">	570	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
463	hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220	571	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		572	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		573	</pre>
		574
		575	<p>
		576	You should also take this time to verify that the appropriate console is
		577	listed in <path>/etc/securetty</path>.
464	</pre>	578	</p>
465		579
466	<p>	580	<p>
467	You may now continue with <uri link="?part=1&chap=9">Installing Necessary	581	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
468	System Tools</uri>.	582	System Tools</uri>.
469	</p>	583	</p>

 Legend:



Removed from v.1.64
 


changed lines


 
Added in v.1.85
 Legend:



Removed from v.1.64
 


changed lines


 
Added in v.1.85
-Removed from v.1.64
+Added in v.1.85

	ViewVC Help
Powered by ViewVC 1.1.13