/[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.67		Revision 1.83
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.67 2005/06/24 18:47:21 fox2mike Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.83 2006/09/08 10:53:26 neysx Exp $ -->
8		8
9	<sections>	9	<sections>
10		10
11	<version>2.9</version>	11	<version>7.2</version>
12	<date>2005-06-24</date>	12	<date>2006-09-08</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>
…		…
231	your Gentoo system permanently.	253	your Gentoo system permanently.
232	</p>	254	</p>
233		255
234	<note>	256	<note>
235	More detailed information about networking, including advanced topics like	257	More detailed information about networking, including advanced topics like
236	bonding, bridging, 802.11q VLANs or wireless networking is covered in the <uri	258	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
237	link="?part=4">Gentoo Network Configuration</uri> section.	259	link="?part=4">Gentoo Network Configuration</uri> section.
238	</note>	260	</note>
239		261
240	<p>	262	<p>
241	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	263	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
242	a straightforward yet not intuitive syntax if you don't know how to set up	264	a straightforward yet not intuitive syntax if you don't know how to set up
243	networking manually. But don't fear, we'll explain everything :)	265	networking manually. But don't fear, we'll explain everything. A fully
244	</p>	266	commented example that covers many different configurations is available in
245		267	<path>/etc/conf.d/net.example</path>.
246	<p>	268	</p>
		269
		270	<p>
		271	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		272	client. This is described later in <uri
		273	link="?part=1&chap=9#networking-tools">Installing Necessary System
		274	Tools</uri>. Do not forget to install a DHCP client.
		275	</p>
		276
		277	<p>
		278	If you need to configure your network connection either because you need
		279	specific DHCP options or because you do not use DHCP at all, open
247	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>	280	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
248	is used in this example):	281	this example):
249	</p>	282	</p>
250		283
251	<pre caption="Opening /etc/conf.d/net for editing">	284	<pre caption="Opening /etc/conf.d/net for editing">
252	# <i>nano -w /etc/conf.d/net</i>	285	# <i>nano -w /etc/conf.d/net</i>
253	</pre>	286	</pre>
254		287
255	<p>	288	<p>
256	The first variable you'll find is called <c>config_eth0</c>. As you can probably	289	You will see the following file:
257	imagine, this variable configured the eth0 network interface. If the interface	290	</p>
258	needs to automatically obtain an IP address through DHCP, you should set it	291
259	like so:	292	<pre caption="Default /etc/conf.d/net">
		293	# This blank configuration will automatically use DHCP for any net.*
		294	# scripts in /etc/init.d. To create a more complete configuration,
		295	# please review /etc/conf.d/net.example and save your configuration
		296	# in /etc/conf.d/net (this file :]!).
		297	</pre>
		298
		299	<p>
		300	To enter your own IP address, netmask and gateway, you need
		301	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
		302	</p>
		303
		304	<pre caption="Manually setting IP information for eth0">
		305	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
		306	routes_eth0=( "default gw 192.168.0.1" )
		307	</pre>
		308
		309	<p>
		310	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
		311	<c>dhcp_eth0</c>:
260	</p>	312	</p>
261		313
262	<pre caption="Automatically obtaining an IP address for eth0">	314	<pre caption="Automatically obtaining an IP address for eth0">
263	config_eth0=( "dhcp" )	315	config_eth0=( "dhcp" )
		316	dhcp_eth0="nodns nontp nonis"
264	</pre>	317	</pre>
265		318
266	<p>
267	However, if you have to enter your own IP address, netmask and gateway, you need
268	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
269	</p>	319	<p>
270		320	Please read <path>/etc/conf.d/net.example</path> for a list of all available
271	<pre caption="Manually setting IP information for eth0">	321	options.
272	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
273	routes_eth0=( "default gw 192.168.0.1" )
274	</pre>	322	</p>
275		323
276	<p>	324	<p>
277	If you have several network interfaces repeat the above steps for	325	If you have several network interfaces repeat the above steps for
278	<c>config_eth1</c>, <c>config_eth2</c>, etc.	326	<c>config_eth1</c>, <c>config_eth2</c>, etc.
279	</p>	327	</p>
…		…
304	use <c>ln</c> to do this:	352	use <c>ln</c> to do this:
305	</p>	353	</p>
306		354
307	<pre caption="Creating extra initscripts">	355	<pre caption="Creating extra initscripts">
308	# <i>cd /etc/init.d</i>	356	# <i>cd /etc/init.d</i>
309	# <i>ln -s net.eth0 net.eth1</i>	357	# <i>ln -s net.lo net.eth1</i>
310	# <i>rc-update add net.eth1 default</i>	358	# <i>rc-update add net.eth1 default</i>
311	</pre>	359	</pre>
312		360
313	</body>	361	</body>
314	</subsection>	362	</subsection>
…		…
316	<title>Writing Down Network Information</title>	364	<title>Writing Down Network Information</title>
317	<body>	365	<body>
318		366
319	<p>	367	<p>
320	You now need to inform Linux about your network. This is defined in	368	You now need to inform Linux about your network. This is defined in
321	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	369	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
322	for hosts that aren't resolved by your nameserver. For instance, if your	370	hosts that aren't resolved by your nameserver. You need to define your system.
323	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	371	You may also want to define other systems on your network if you don't want to
324	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	372	set up your own internal DNS system.
325	open <path>/etc/hosts</path> and fill in the values:
326	</p>	373	</p>
327		374
328	<pre caption="Opening /etc/hosts">	375	<pre caption="Opening /etc/hosts">
329	# <i>nano -w /etc/hosts</i>	376	# <i>nano -w /etc/hosts</i>
330	</pre>	377	</pre>
331		378
332	<pre caption="Filling in the networking information">	379	<pre caption="Filling in the networking information">
333	127.0.0.1 localhost	380	<comment>(This defines the current system)</comment>
		381	127.0.0.1 tux.homenetwork tux localhost
		382
		383	<comment>(Define extra systems on your network,
		384	they need to have a static IP to be defined this way.)</comment>
334	192.168.0.5 jenny.homenetwork jenny	385	192.168.0.5 jenny.homenetwork jenny
335	192.168.0.6 benny.homenetwork benny	386	192.168.0.6 benny.homenetwork benny
336	192.168.0.7 tux.homenetwork tux
337	</pre>
338
339	<p>
340	If your system is the only system (or the nameservers handle all name
341	resolution) a single line is sufficient. For instance, if you want to call your
342	system <c>tux</c>:
343	</p>
344
345	<pre caption="/etc/hosts for lonely or fully integrated PCs">
346	127.0.0.1 localhost tux
347	</pre>	387	</pre>
348		388
349	<p>	389	<p>
350	Save and exit the editor to continue.	390	Save and exit the editor to continue.
351	</p>	391	</p>
352		392
353	<p>	393	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
354	If you don't have PCMCIA, you can now continue with <uri	394	If you don't have PCMCIA, you can now continue with <uri
355	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	395	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
356	following topic on PCMCIA.	396	following topic on PCMCIA.
357	</p>	397	</p>
358		398
359	</body>	399	</body>
360	</subsection>	400	</subsection>
361	<subsection>	401	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
362	<title>Optional: Get PCMCIA Working</title>	402	<title>Optional: Get PCMCIA Working</title>
363	<body>	403	<body>
364
365	<note>
366	pcmcia-cs is only available for x86, amd64 and ppc platforms.
367	</note>
368		404
369	<p>	405	<p>
370	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	406	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
371	includes users who will be working with a 2.6 kernel (even though they won't be	407	includes users who will be working with a 2.6 kernel (even though they won't be
372	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary	408	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
…		…
387	</pre>	423	</pre>
388		424
389	</body>	425	</body>
390	</subsection>	426	</subsection>
391	</section>	427	</section>
392	<section>	428
		429	<section id="sysinfo">
393	<title>System Information</title>	430	<title>System Information</title>
394	<subsection>	431	<subsection>
395	<title>Root Password</title>	432	<title>Root Password</title>
396	<body>	433	<body>
397		434
…		…
431	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.	468	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
432	</p>	469	</p>
433		470
434	<p>	471	<p>
435	As you can see, this file is well commented to help you set up the necessary	472	As you can see, this file is well commented to help you set up the necessary
436	configuration variables. Among other settings, you can configure your console	473	configuration variables. You can configure your system to use unicode and
437	fonts, your default editor and your display manager (like gdm or kdm).	474	define your default editor and your display manager (like gdm or kdm).
438	</p>	475	</p>
439		476
440	<p>	477	<p>
441	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.	478	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
442	Edit it to configure your keyboard.	479	Edit it to configure your keyboard.
…		…
449	<p>	486	<p>
450	Take special care with the <c>KEYMAP</c> variable. If you select the wrong	487	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
451	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.	488	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
452	</p>	489	</p>
453		490
454	<note>	491	<note test="func:keyval('arch')='SPARC'">
455	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	492	Users of USB-based SPARC systems and SPARC clones might need to select an i386
456	select an i386 keymap (such as "us") instead of "sunkeymap".	493	keymap (such as "us") instead of "sunkeymap".
457	</note>	494	</note>
458		495
459	<p>	496	<note test="substring(func:keyval('arch'),1,3)='PPC'">
460	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	497	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
461	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	498	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
462	to set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.	499	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
463	</p>	500	</note>
464		501
465	<p>	502	<p>
466	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and	503	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
467	exit.	504	exit.
468	</p>	505	</p>
…		…
475	<pre caption="Opening /etc/conf.d/clock">	512	<pre caption="Opening /etc/conf.d/clock">
476	# <i>nano -w /etc/conf.d/clock</i>	513	# <i>nano -w /etc/conf.d/clock</i>
477	</pre>	514	</pre>
478		515
479	<p>	516	<p>
480	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	517	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
481	the file. Otherwise you will notice some clock skew.	518	to the file. Otherwise you will notice some clock skew.
482	</p>	519	</p>
483		520
484	<p>	521	<p>
485	When you're finished configuring <path>/etc/conf.d/clock</path>, save and	522	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
486	exit.	523	exit.
487	</p>	524	</p>
488		525
		526	<p test="not(func:keyval('arch')='PPC64')">
		527	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		528	Tools</uri>.
489	<p>	529	</p>
490	If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with
491	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
492	</p>
493		530
494	</body>	531	</body>
495	</subsection>
496	<subsection>	532	</subsection>
		533	<subsection test="func:keyval('arch')='PPC64'">
497	<title>Configuring the Console</title>	534	<title>Configuring the Console</title>
498	<body>	535	<body>
499		536
500	<note>
501	The following section applies to the IBM POWER5 and JS20 hardware platforms.
502	</note>
503
504	<p>
505	If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
506	the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
507	</p>	537	<p>
		538	If you are using a virtual console, you must uncomment the appropriate line in
		539	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
		540	</p>
508		541
509	<pre caption="Enabling hvc support in /etc/inittab">	542	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
510	hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220	543	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		544	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		545	</pre>
		546
		547	<p>
		548	You should also take this time to verify that the appropriate console is
		549	listed in <path>/etc/securetty</path>.
511	</pre>	550	</p>
512		551
513	<p>	552	<p>
514	You may now continue with <uri link="?part=1&chap=9">Installing Necessary	553	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
515	System Tools</uri>.	554	System Tools</uri>.
516	</p>	555	</p>

 Legend:



Removed from v.1.67
 


changed lines


 
Added in v.1.83
 Legend:



Removed from v.1.67
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.13