/[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.62		Revision 1.116
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.62 2005/06/09 07:16:39 swift Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.116 2012/10/06 20:16:10 swift 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.4</version>	17	<version>22</version>
12	<date>2005-06-09</date>	18	<date>2012-10-06</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 0 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 0 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 0 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>echo tux > /etc/hostname</i>	195	# <i>nano -w /etc/conf.d/hostname</i>
185	</pre>
186		196
		197	<comment>(Set the hostname variable to your host name)</comment>
		198	hostname="<i>tux</i>"
		199	</pre>
		200
187	<p>	201	<p>
188	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.
189	</p>	206	</p>
190		207
191	<pre caption="Setting the domainname">	208	<pre caption="Setting the domainname">
192	# <i>echo homenetwork > /etc/dnsdomainname</i>	209	# <i>nano -w /etc/conf.d/net</i>
		210
		211	<comment>(Set the dns_domain variable to your domain name)</comment>
		212	dns_domain_lo="<i>homenetwork</i>"
193	</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>
194		220
195	<p>	221	<p>
196	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
197	one), you need to define that one too:	223	one), you need to define that one too:
198	</p>	224	</p>
199		225
200	<pre caption="Setting the NIS domainname">	226	<pre caption="Setting the NIS domainname">
201	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	227	# <i>nano -w /etc/conf.d/net</i>
202	</pre>
203		228
204	<p>	229	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
205	Now add the <c>domainname</c> script to the default runlevel:	230	nis_domain_lo="<i>my-nisdomain</i>"
206	</p>	231	</pre>
207		232
208	<pre caption="Adding domainname to the default runlevel">	233	<note>
209	# <i>rc-update add domainname default</i>	234	For more information on configuring DNS and NIS, please read the examples
210	</pre>	235	provided in <path>/usr/share/doc/openrc-*/net.example.bz2</path> which
		236	can be read using <c>bzless</c>. Also, you may want to emerge <c>openresolv</c>
		237	to help manage your DNS/NIS setup.
		238	</note>
211		239
212	</body>	240	</body>
213	</subsection>	241	</subsection>
214	<subsection>	242	<subsection>
215	<title>Configuring your Network</title>	243	<title>Configuring your Network</title>
216	<body>	244	<body>
217		245
218	<p>	246	<p>
219	Before you get that "Hey, we've had that already"-feeling, you should remember	247	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	248	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	249	just for the installation. Right now you are going to configure networking for
222	your Gentoo system permanently.	250	your Gentoo system permanently.
223	</p>	251	</p>
224		252
		253	<note>
		254	More detailed information about networking, including advanced topics like
		255	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
		256	link="?part=4">Gentoo Network Configuration</uri> section.
		257	</note>
		258
225	<p>	259	<p>
226	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	260	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	261	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 :)	262	networking manually. But don't fear, we'll explain everything. A fully
229	</p>	263	commented example that covers many different configurations is available in
230		264	<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
231	<p>	265	</p>
		266
		267	<p>
		268	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		269	client. This is described later in <uri
		270	link="?part=1&chap=9#networking-tools">Installing Necessary System
		271	Tools</uri>. Do not forget to install a DHCP client.
		272	</p>
		273
		274	<p>
		275	If you need to configure your network connection either because you need
		276	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>	277	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233	is used in this example):	278	this example):
234	</p>	279	</p>
235		280
236	<pre caption="Opening /etc/conf.d/net for editing">	281	<pre caption="Opening /etc/conf.d/net for editing">
237	# <i>nano -w /etc/conf.d/net</i>	282	# <i>nano -w /etc/conf.d/net</i>
238	</pre>	283	</pre>
239		284
240	<p>	285	<p>
241	The first variable you'll find is called <c>config_eth0</c>. As you can probably	286	You will see the following file:
242	imagine, this variable configured the eth0 network interface. If the interface
243	needs to automatically obtain an IP through DHCP, you should set it like so:
244	</p>
245
246	<pre caption="Automatically obtaining an IP for eth0">
247	config_eth0=( "dhcp" )
248	</pre>
249
250	<p>	287	</p>
		288
		289	<pre caption="Default /etc/conf.d/net">
		290	# This blank configuration will automatically use DHCP for any net.*
		291	# scripts in /etc/init.d. To create a more complete configuration,
		292	# please review /usr/share/doc/openrc-*/net.example.bz2 and save
		293	# your configuration in /etc/conf.d/net (this file :]!).
		294	</pre>
		295
		296	<p>
251	However, if you have to enter your own IP address, netmask and gateway, you need	297	To enter your own IP address, netmask and gateway, you need
252	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>:
253	</p>	299	</p>
254		300
255	<pre caption="Manually setting IP information for eth0">	301	<pre caption="Manually setting IP information for eth0">
256	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"
257	routes_eth0=( "default gw 192.168.0.1" )	303	routes_eth0="default via 192.168.0.1"
		304	</pre>
		305
		306	<p>
		307	To use DHCP, define <c>config_eth0</c>:
258	</pre>	308	</p>
		309
		310	<pre caption="Automatically obtaining an IP address for eth0">
		311	config_eth0="dhcp"
		312	</pre>
		313
		314	<p>
		315	Please read <path>/usr/share/doc/openrc-*/net.example.bz2</path> for a
		316	list of all available options. Be sure to also read your DHCP client manpage if
		317	you need to set specific DHCP options.
		318	</p>
259		319
260	<p>	320	<p>
261	If you have several network interfaces repeat the above steps for	321	If you have several network interfaces repeat the above steps for
262	<c>config_eth1</c>, <c>config_eth2</c>, etc.	322	<c>config_eth1</c>, <c>config_eth2</c>, etc.
263	</p>	323	</p>
…		…
272	<title>Automatically Start Networking at Boot</title>	332	<title>Automatically Start Networking at Boot</title>
273	<body>	333	<body>
274		334
275	<p>	335	<p>
276	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
277	default runlevel. If you have PCMCIA interfaces you should skip this action as	337	default runlevel.
278	the PCMCIA interfaces are started by the PCMCIA init script.
279	</p>	338	</p>
280		339
281	<pre caption="Adding net.eth0 to the default runlevel">	340	<pre caption="Adding net.eth0 to the default runlevel">
		341	# <i>cd /etc/init.d</i>
		342	# <i>ln -s net.lo net.eth0</i>
282	# <i>rc-update add net.eth0 default</i>	343	# <i>rc-update add net.eth0 default</i>
283	</pre>	344	</pre>
284		345
285	<p>	346	<p>
286	If you have several network interfaces, you need to create the appropriate	347	If you have several network interfaces, you need to create the appropriate
287	<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can	348	<path>net.eth1</path>, <path>net.eth2</path> etc. just like you did with
288	use <c>ln</c> to do this:	349	<path>net.eth0</path>.
289	</p>
290
291	<pre caption="Creating extra initscripts">
292	# <i>cd /etc/init.d</i>
293	# <i>ln -s net.eth0 net.eth1</i>
294	# <i>rc-update add net.eth1 default</i>
295	</pre>	350	</p>
296		351
297	</body>	352	</body>
298	</subsection>	353	</subsection>
299	<subsection>	354	<subsection>
300	<title>Writing Down Network Information</title>	355	<title>Writing Down Network Information</title>
301	<body>	356	<body>
302		357
303	<p>	358	<p>
304	You now need to inform Linux about your network. This is defined in	359	You now need to inform Linux about your network. This is defined in
305	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	360	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
306	for hosts that aren't resolved by your nameserver. For instance, if your	361	hosts that aren't resolved by your nameserver. You need to define your system.
307	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	362	You may also want to define other systems on your network if you don't want to
308	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	363	set up your own internal DNS system.
309	open <path>/etc/hosts</path> and fill in the values:
310	</p>	364	</p>
311		365
312	<pre caption="Opening /etc/hosts">	366	<pre caption="Opening /etc/hosts">
313	# <i>nano -w /etc/hosts</i>	367	# <i>nano -w /etc/hosts</i>
314	</pre>	368	</pre>
315		369
316	<pre caption="Filling in the networking information">	370	<pre caption="Filling in the networking information">
317	127.0.0.1 localhost	371	<comment>(This defines the current system)</comment>
		372	127.0.0.1 tux.homenetwork tux localhost
		373
		374	<comment>(Define extra systems on your network,
		375	they need to have a static IP to be defined this way.)</comment>
318	192.168.0.5 jenny.homenetwork jenny	376	192.168.0.5 jenny.homenetwork jenny
319	192.168.0.6 benny.homenetwork benny	377	192.168.0.6 benny.homenetwork benny
320	192.168.0.7 tux.homenetwork tux
321	</pre>
322
323	<p>
324	If your system is the only system (or the nameservers handle all name
325	resolution) a single line is sufficient. For instance, if you want to call your
326	system <c>tux</c>:
327	</p>
328
329	<pre caption="/etc/hosts for lonely or fully integrated PCs">
330	127.0.0.1 localhost tux
331	</pre>	378	</pre>
332		379
333	<p>	380	<p>
334	Save and exit the editor to continue.	381	Save and exit the editor to continue.
335	</p>	382	</p>
336		383
337	<p>	384	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
338	If you don't have PCMCIA, you can now continue with <uri	385	If you don't have PCMCIA, you can now continue with <uri
339	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	386	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
340	following topic on PCMCIA.	387	following topic on PCMCIA.
341	</p>	388	</p>
342		389
343	</body>	390	</body>
344	</subsection>	391	</subsection>
345	<subsection>	392	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
346	<title>Optional: Get PCMCIA Working</title>	393	<title>Optional: Get PCMCIA Working</title>
347	<body>	394	<body>
348		395
349	<note>
350	pcmcia-cs is only available for x86, amd64 and ppc platforms.
351	</note>
352
353	<p>	396	<p>
354	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	397	PCMCIA users should first install the <c>pcmciautils</c> package.
355	includes users who will be working with a 2.6 kernel (even though they won't be
356	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
357	to avoid installing xorg-x11 at this moment:
358	</p>	398	</p>
359		399
360	<pre caption="Installing pcmcia-cs">	400	<pre caption="Installing pcmciautils">
361	# <i>USE="-X" emerge pcmcia-cs</i>	401	# <i>emerge pcmciautils</i>
362	</pre>
363
364	<p>
365	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
366	runlevel:
367	</p>
368
369	<pre caption="Adding pcmcia to the default runlevel">
370	# <i>rc-update add pcmcia default</i>
371	</pre>	402	</pre>
372		403
373	</body>	404	</body>
374	</subsection>	405	</subsection>
375	</section>	406	</section>
376	<section>	407
		408	<section id="sysinfo">
377	<title>System Information</title>	409	<title>System Information</title>
378	<subsection>	410	<subsection>
379	<title>Root Password</title>	411	<title>Root Password</title>
380	<body>	412	<body>
381		413
…		…
385		417
386	<pre caption="Setting the root password">	418	<pre caption="Setting the root password">
387	# <i>passwd</i>	419	# <i>passwd</i>
388	</pre>	420	</pre>
389		421
390	<p>
391	If you want root to be able to log on through the serial console, add
392	<c>tts/0</c> to <path>/etc/securetty</path>:
393	</p>
394
395	<pre caption="Adding tts/0 to /etc/securetty">
396	# <i>echo "tts/0" >> /etc/securetty</i>
397	</pre>
398
399	</body>	422	</body>
400	</subsection>	423	</subsection>
401	<subsection>	424	<subsection>
402	<title>System Information</title>	425	<title>System Information</title>
403	<body>	426	<body>
404		427
405	<p>	428	<p>
406	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.	429	Gentoo uses <path>/etc/rc.conf</path> to configure the services, startup,
407	Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)	430	and shutdown of your system. Open up <path>/etc/rc.conf</path> and enjoy all
		431	the comments in the file.
408	</p>	432	</p>
409		433
410	<pre caption="Opening /etc/rc.conf">	434	<pre caption="Configuring services">
411	# <i>nano -w /etc/rc.conf</i>	435	# <i>nano -w /etc/rc.conf</i>
412	</pre>	436	</pre>
413		437
414	<p>	438	<p>
415	As you can see, this file is well commented to help you set up the necessary	439	When you're finished configuring these two files, save them and exit.
416	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	440	</p>
417	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	441
418	your keyboard.
419	</p>	442	<p>
		443	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		444	Edit it to configure your keyboard.
		445	</p>
		446
		447	<pre caption="Opening /etc/conf.d/keymaps">
		448	# <i>nano -w /etc/conf.d/keymaps</i>
		449	</pre>
		450
		451	<p>
		452	Take special care with the <c>keymap</c> variable. If you select the wrong
		453	<c>keymap</c>, you will get weird results when typing on your keyboard.
		454	</p>
		455
		456	<note test="substring(func:keyval('arch'),1,3)='PPC'">
		457	PPC uses x86 keymaps on most systems.
		458	</note>
		459
		460	<p>
		461	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
		462	exit.
		463	</p>
		464
		465	<p>
		466	Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
		467	according to your needs.
		468	</p>
		469
		470	<pre caption="Opening /etc/conf.d/hwclock">
		471	# <i>nano -w /etc/conf.d/hwclock</i>
		472	</pre>
		473
		474	<p>
		475	If your hardware clock is not using UTC, you need to add <c>clock="local"</c>
		476	to the file. Otherwise you will notice some clock skew.
		477	</p>
		478
		479	<p>
		480	When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and
		481	exit.
		482	</p>
		483
		484	<p>
		485	You should define the timezone that you previously copied to
		486	<path>/etc/localtime</path> in the <path>/etc/timezone</path> file so that
		487	further upgrades of the <c>sys-libs/timezone-data</c> package can update
		488	<path>/etc/localtime</path> automatically. For instance, if you used the
		489	Europe/Brussels timezone, you would write <c>Europe/Brussels</c> in the
		490	<path>/etc/timezone</path> file.
		491	</p>
		492
		493	</body>
		494	</subsection>
		495
		496	<subsection>
		497	<title>Configure locales</title>
		498	<body>
		499
		500	<p>
		501	You will probably only use one or maybe two locales on your system. You have to
		502	specify locales you will need in <path>/etc/locale.gen</path>.
		503	</p>
		504
		505	<pre caption="Opening /etc/locale.gen">
		506	# <i>nano -w /etc/locale.gen</i>
		507	</pre>
		508
		509	<p>
		510	The following locales are an example to get both English (United States) and
		511	German (Germany) with the accompanying character formats (like UTF-8).
		512	</p>
		513
		514	<pre caption="Specify your locales">
		515	en_US ISO-8859-1
		516	en_US.UTF-8 UTF-8
		517	de_DE ISO-8859-1
		518	de_DE@euro ISO-8859-15
		519	</pre>
420		520
421	<note>	521	<note>
422	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	522	You can select your desired locales in the list given by running <c>locale -a</c>.
423	select an i386 keymap (such as "us") instead of "sunkeymap".
424	</note>	523	</note>
425		524
426	<p>	525	<warn>
427	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	526	We strongly suggest that you should use at least one UTF-8 locale because some
428	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	527	applications may require it.
429	to set a mac/ppc keymap in <path>rc.conf</path>.	528	</warn>
		529
430	</p>	530	<p>
431		531	The next step is to run <c>locale-gen</c>. It will generates all the locales you
		532	have specified in the <path>/etc/locale.gen</path> file.
432	<p>	533	</p>
433	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	534
434	the file. Otherwise you will notice some clock skew.	535	<pre caption="Running locale-gen">
		536	# <i>locale-gen</i>
		537	</pre>
		538
435	</p>	539	<p>
436		540	Once done, you now have the possibility to set the system-wide locale settings
		541	in the <path>/etc/env.d/02locale</path> file:
437	<p>	542	</p>
438	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.	543
		544	<pre caption="Setting the default system locale in /etc/env.d/02locale">
		545	LANG="de_DE.UTF-8"
		546	LC_COLLATE="C"
		547	</pre>
		548
439	</p>	549	<p>
440		550	And reload your environment:
441	<p>	551	</p>
442	If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with	552
443	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.	553	<pre caption="Reload shell environment">
		554	# env-update && source /etc/profile
		555	</pre>
		556
444	</p>	557	<p>
		558	We made a full <uri link="../guide-localization.xml#doc_chap3">Localization
		559	Guide</uri> to help you through this process. You can also read our detailed
		560	<uri link="../utf-8.xml#doc_chap2">UTF-8 Guide</uri> for very specific
		561	informations to enable UTF-8 on your system.
		562	</p>
445		563
		564	<p test="not(func:keyval('arch')='PPC64')">
		565	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		566	Tools</uri>.
		567	</p>
		568
446	</body>	569	</body>
447	</subsection>
448	<subsection>	570	</subsection>
		571	<subsection test="func:keyval('arch')='PPC64'">
449	<title>Configuring the Console</title>	572	<title>Configuring the Console</title>
450	<body>	573	<body>
451		574
452	<note>
453	The following section applies to the IBM POWER5 and JS20 hardware platforms.
454	</note>
455
456	<p>
457	If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
458	the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
459	</p>	575	<p>
		576	If you are using a virtual console, you must uncomment the appropriate line in
		577	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
		578	</p>
460		579
461	<pre caption="Enabling hvc support in /etc/inittab">	580	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
462	hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220	581	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		582	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		583	</pre>
		584
		585	<p>
		586	You should also take this time to verify that the appropriate console is
		587	listed in <path>/etc/securetty</path>.
463	</pre>	588	</p>
464		589
465	<p>	590	<p>
466	You may now continue with <uri link="?part=1&chap=9">Installing Necessary	591	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
467	System Tools</uri>.	592	System Tools</uri>.
468	</p>	593	</p>

 Legend:



Removed from v.1.62
 


changed lines


 
Added in v.1.116
 Legend:



Removed from v.1.62
 


changed lines


 
Added in v.1.116
-Removed from v.1.62
+Added in v.1.116

	ViewVC Help
Powered by ViewVC 1.1.13