/[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.76		Revision 1.115
…		…
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.76 2006/03/28 10:35:59 neysx Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.115 2012/04/29 16:52:20 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.18</version>	17	<version>21</version>
12	<date>2006-03-28</date>	18	<date>2012-04-29</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 Apple <b>PPC</b> machines), don't copy it	91	<path>/boot</path>, don't copy it.
84	verbatim.
85	</p>
86
87	<p>	92	</p>
		93
		94	<p>
88	In our default x86 partitioning example <path>/boot</path> is the	95	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
89	<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
90	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:
91	</p>	98	</p>
92		99
93	<pre caption="An example /boot line for /etc/fstab">	100	<pre caption="An example /boot line for /etc/fstab">
94	/dev/hda1 /boot ext2 defaults 1 2	101	<keyval id="/boot"/> /boot ext2 defaults 1 2
95	</pre>	102	</pre>
96		103
97	<p>	104	<p>
98	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
99	automatically to improve their system's security. Those people should	106	automatically to improve their system's security. Those people should
100	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
101	manually mount this partition every time you want to use it.	108	manually mount this partition every time you want to use it.
102	</p>	109	</p>
103		110
104	<p>	111	</body>
105	Now, to improve performance, most users would want to add the <c>noatime</c>	112	<body>
106	option as mountoption, which results in a faster system since access times	113
107	aren't registered (you don't need those generally anyway):
108	</p>	114	<p>
109		115	Add the rules that match your partitioning scheme and append rules for
110	<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,
111	/dev/hda1 /boot ext2 defaults,noatime 1 2	117	for those too.
112	</pre>
113
114	<p>	118	</p>
115	If we continue with this, we would end up with the following three lines (for	119
116	<path>/boot</path>, <path>/</path> and the swap partition):
117	</p>	120	<p>
		121	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
		122	</p>
118		123
119	<pre caption="Three /etc/fstab lines">	124	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
120	/dev/hda1 /boot ext2 defaults,noatime 1 2	125	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
121	/dev/hda2 none swap sw 0 0	126	/dev/sda3 none swap sw 0 0
122	/dev/hda3 / ext3 noatime 0 1	127	/dev/sda4 / ext3 noatime 0 1
123	</pre>
124		128
125	<p>	129	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
126	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
127	(required) and for your CD-ROM drive (and of course, if you have other
128	partitions or drives, for those too):
129	</p>	130	</pre>
130		131
131	<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'">
132	/dev/hda1 /boot ext2 defaults,noatime 1 2	133	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
133	/dev/hda2 none swap sw 0 0	134	/dev/sda2 none swap sw 0 0
134	/dev/hda3 / ext3 noatime 0 1	135	/dev/sda3 / ext3 noatime 0 1
135		136
136	none /proc proc defaults 0 0	137	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0	138	</pre>
138		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
139	/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
140	</pre>	159	</pre>
141		160
142	<p>	161	<p>
143	<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
144	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
145	<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.
146	</p>	165	</p>
147		166
148	<p>	167	<p>
149	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>
150	<b>SPARC</b>-user, you should add the following line to your	169	mount option, which results in a faster system since access times
151	<path>/etc/fstab</path>	170	aren't registered (you don't need those generally anyway).
152	too:
153	</p>
154
155	<pre caption="Adding openprom filesystem to /etc/fstab">
156	none /proc/openprom openpromfs defaults 0 0
157	</pre>	171	</p>
158		172
159	<p>	173	<p>
160	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.
161	</p>	175	</p>
162		176
…		…
164	</subsection>	178	</subsection>
165	</section>	179	</section>
166	<section>	180	<section>
167	<title>Networking Information</title>	181	<title>Networking Information</title>
168	<subsection>	182	<subsection>
169	<title>Hostname, Domainname etc.</title>	183	<title>Host name, Domainname, etc</title>
170	<body>	184	<body>
171		185
172	<p>	186	<p>
173	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
174	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
175	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
176	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
177	<c>tux</c> and domain <c>homenetwork</c>.	191	<c>tux</c> and domain <c>homenetwork</c>.
178	</p>	192	</p>
179		193
180	<p>
181	We use these values in the next examples. First we set the hostname:
182	</p>
183
184	<pre caption="Setting the hostname">	194	<pre caption="Setting the host name">
185	# <i>nano -w /etc/conf.d/hostname</i>	195	# <i>nano -w /etc/conf.d/hostname</i>
186		196
187	<comment>(Set the HOSTNAME variable to your hostname)</comment>	197	<comment>(Set the hostname variable to your host name)</comment>
188	HOSTNAME="<i>tux</i>"	198	hostname="<i>tux</i>"
189	</pre>	199	</pre>
190		200
191	<p>	201	<p>
192	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.
193	</p>	206	</p>
194		207
195	<pre caption="Setting the domainname">	208	<pre caption="Setting the domainname">
196	# <i>nano -w /etc/conf.d/domainname</i>	209	# <i>nano -w /etc/conf.d/net</i>
197		210
198	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>	211	<comment>(Set the dns_domain variable to your domain name)</comment>
199	DNSDOMAIN="<i>homenetwork</i>"	212	dns_domain_lo="<i>homenetwork</i>"
200	</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>
201		220
202	<p>	221	<p>
203	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
204	one), you need to define that one too:	223	one), you need to define that one too:
205	</p>	224	</p>
206		225
207	<pre caption="Setting the NIS domainname">	226	<pre caption="Setting the NIS domainname">
208	# <i>nano -w /etc/conf.d/domainname</i>	227	# <i>nano -w /etc/conf.d/net</i>
209		228
210	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>	229	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
211	NISDOMAIN="<i>my-nisdomain</i>"	230	nis_domain_lo="<i>my-nisdomain</i>"
212	</pre>	231	</pre>
		232
		233	<note>
		234	For more information on configuring DNS and NIS, please read the examples
		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>
213		239
214	</body>	240	</body>
215	</subsection>	241	</subsection>
216	<subsection>	242	<subsection>
217	<title>Configuring your Network</title>	243	<title>Configuring your Network</title>
…		…
233	<p>	259	<p>
234	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
235	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
236	networking manually. But don't fear, we'll explain everything. A fully	262	networking manually. But don't fear, we'll explain everything. A fully
237	commented example that covers many different configurations is available in	263	commented example that covers many different configurations is available in
238	<path>/etc/conf.d/net.example</path>.	264	<path>/usr/share/doc/openrc-*/net.example.bz2</path>.
239	</p>
240
241	<p>	265	</p>
242	DHCP is used by default and does not require any further configuration.	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.
243	</p>	272	</p>
244		273
245	<p>	274	<p>
246	If you need to configure your network connection either because you need	275	If you need to configure your network connection either because you need
247	specific DHCP options or because you do not use DHCP at all, open	276	specific DHCP options or because you do not use DHCP at all, open
…		…
258	</p>	287	</p>
259		288
260	<pre caption="Default /etc/conf.d/net">	289	<pre caption="Default /etc/conf.d/net">
261	# This blank configuration will automatically use DHCP for any net.*	290	# This blank configuration will automatically use DHCP for any net.*
262	# scripts in /etc/init.d. To create a more complete configuration,	291	# scripts in /etc/init.d. To create a more complete configuration,
263	# please review /etc/conf.d/net.example and save your configuration	292	# please review /usr/share/doc/openrc-*/net.example.bz2 and save
264	# in /etc/conf.d/net (this file :]!).	293	# your configuration in /etc/conf.d/net (this file :]!).
265	</pre>	294	</pre>
266		295
267	<p>	296	<p>
268	To enter your own IP address, netmask and gateway, you need	297	To enter your own IP address, netmask and gateway, you need
269	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>:
270	</p>	299	</p>
271		300
272	<pre caption="Manually setting IP information for eth0">	301	<pre caption="Manually setting IP information for eth0">
273	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )	302	config_eth0="192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255"
274	routes_eth0=( "default gw 192.168.0.1" )	303	routes_eth0="default via 192.168.0.1"
275	</pre>	304	</pre>
276		305
277	<p>	306	<p>
278	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and	307	To use DHCP, define <c>config_eth0</c>:
279	<c>dhcp_eth0</c>:
280	</p>	308	</p>
281		309
282	<pre caption="Automatically obtaining an IP address for eth0">	310	<pre caption="Automatically obtaining an IP address for eth0">
283	config_eth0=( "dhcp" )	311	config_eth0="dhcp"
284	dhcp_eth0="nodns nontp nonis"
285	</pre>	312	</pre>
286		313
287	<p>	314	<p>
288	Please read <path>/etc/conf.d/net.example</path> for a list of all available	315	Please read <path>/usr/share/doc/openrc-*/net.example.bz2</path> for a
289	options.	316	list of all available options. Be sure to also read your DHCP client manpage if
		317	you need to set specific DHCP options.
290	</p>	318	</p>
291		319
292	<p>	320	<p>
293	If you have several network interfaces repeat the above steps for	321	If you have several network interfaces repeat the above steps for
294	<c>config_eth1</c>, <c>config_eth2</c>, etc.	322	<c>config_eth1</c>, <c>config_eth2</c>, etc.
…		…
304	<title>Automatically Start Networking at Boot</title>	332	<title>Automatically Start Networking at Boot</title>
305	<body>	333	<body>
306		334
307	<p>	335	<p>
308	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
309	default runlevel. If you have PCMCIA interfaces you should skip this action as	337	default runlevel.
310	the PCMCIA interfaces are started by the PCMCIA init script.
311	</p>	338	</p>
312		339
313	<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>
314	# <i>rc-update add net.eth0 default</i>	343	# <i>rc-update add net.eth0 default</i>
315	</pre>	344	</pre>
316		345
317	<p>	346	<p>
318	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
319	<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
320	use <c>ln</c> to do this:	349	<path>net.eth0</path>.
321	</p>
322
323	<pre caption="Creating extra initscripts">
324	# <i>cd /etc/init.d</i>
325	# <i>ln -s net.eth0 net.eth1</i>
326	# <i>rc-update add net.eth1 default</i>
327	</pre>	350	</p>
328		351
329	</body>	352	</body>
330	</subsection>	353	</subsection>
331	<subsection>	354	<subsection>
332	<title>Writing Down Network Information</title>	355	<title>Writing Down Network Information</title>
333	<body>	356	<body>
334		357
335	<p>	358	<p>
336	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
337	<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
338	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.
339	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
340	<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.
341	open <path>/etc/hosts</path> and fill in the values:
342	</p>	364	</p>
343		365
344	<pre caption="Opening /etc/hosts">	366	<pre caption="Opening /etc/hosts">
345	# <i>nano -w /etc/hosts</i>	367	# <i>nano -w /etc/hosts</i>
346	</pre>	368	</pre>
347		369
348	<pre caption="Filling in the networking information">	370	<pre caption="Filling in the networking information">
349	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>
350	192.168.0.5 jenny.homenetwork jenny	376	192.168.0.5 jenny.homenetwork jenny
351	192.168.0.6 benny.homenetwork benny	377	192.168.0.6 benny.homenetwork benny
352	192.168.0.7 tux.homenetwork tux
353	</pre>
354
355	<p>
356	If your system is the only system (or the nameservers handle all name
357	resolution) a single line is sufficient. For instance, if you want to call your
358	system <c>tux</c>:
359	</p>
360
361	<pre caption="/etc/hosts for lonely or fully integrated PCs">
362	127.0.0.1 localhost tux
363	</pre>	378	</pre>
364		379
365	<p>	380	<p>
366	Save and exit the editor to continue.	381	Save and exit the editor to continue.
367	</p>	382	</p>
368		383
369	<p>	384	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
370	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
371	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	386	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
372	following topic on PCMCIA.	387	following topic on PCMCIA.
373	</p>	388	</p>
374		389
375	</body>	390	</body>
376	</subsection>	391	</subsection>
377	<subsection>	392	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
378	<title>Optional: Get PCMCIA Working</title>	393	<title>Optional: Get PCMCIA Working</title>
379	<body>	394	<body>
380		395
381	<note>
382	pcmcia-cs is only available for x86, amd64 and ppc platforms.
383	</note>
384
385	<p>	396	<p>
386	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	397	PCMCIA users should first install the <c>pcmciautils</c> package.
387	includes users who will be working with a 2.6 kernel (even though they won't be
388	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
389	to avoid installing xorg-x11 at this moment:
390	</p>	398	</p>
391		399
392	<pre caption="Installing pcmcia-cs">	400	<pre caption="Installing pcmciautils">
393	# <i>USE="-X" emerge pcmcia-cs</i>	401	# <i>emerge pcmciautils</i>
394	</pre>
395
396	<p>
397	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
398	runlevel:
399	</p>
400
401	<pre caption="Adding pcmcia to the default runlevel">
402	# <i>rc-update add pcmcia default</i>
403	</pre>	402	</pre>
404		403
405	</body>	404	</body>
406	</subsection>	405	</subsection>
407	</section>	406	</section>
408	<section>	407
		408	<section id="sysinfo">
409	<title>System Information</title>	409	<title>System Information</title>
410	<subsection>	410	<subsection>
411	<title>Root Password</title>	411	<title>Root Password</title>
412	<body>	412	<body>
413		413
…		…
417		417
418	<pre caption="Setting the root password">	418	<pre caption="Setting the root password">
419	# <i>passwd</i>	419	# <i>passwd</i>
420	</pre>	420	</pre>
421		421
422	<p>
423	If you want root to be able to log on through the serial console, add
424	<c>tts/0</c> to <path>/etc/securetty</path>:
425	</p>
426
427	<pre caption="Adding tts/0 to /etc/securetty">
428	# <i>echo "tts/0" >> /etc/securetty</i>
429	</pre>
430
431	</body>	422	</body>
432	</subsection>	423	</subsection>
433	<subsection>	424	<subsection>
434	<title>System Information</title>	425	<title>System Information</title>
435	<body>	426	<body>
436		427
437	<p>	428	<p>
438	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,
439	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.
440	</p>	432	</p>
441		433
442	<pre caption="Opening /etc/rc.conf">	434	<pre caption="Configuring services">
443	# <i>nano -w /etc/rc.conf</i>	435	# <i>nano -w /etc/rc.conf</i>
444	</pre>	436	</pre>
445		437
446	<p>	438	<p>
447	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.	439	When you're finished configuring these two files, save them and exit.
448	</p>
449
450	<p>
451	As you can see, this file is well commented to help you set up the necessary
452	configuration variables. You can configure your system to use unicode and
453	define your default editor and your display manager (like gdm or kdm).
454	</p>	440	</p>
455		441
456	<p>	442	<p>
457	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.	443	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
458	Edit it to configure your keyboard.	444	Edit it to configure your keyboard.
…		…
461	<pre caption="Opening /etc/conf.d/keymaps">	447	<pre caption="Opening /etc/conf.d/keymaps">
462	# <i>nano -w /etc/conf.d/keymaps</i>	448	# <i>nano -w /etc/conf.d/keymaps</i>
463	</pre>	449	</pre>
464		450
465	<p>	451	<p>
466	Take special care with the <c>KEYMAP</c> variable. If you select the wrong	452	Take special care with the <c>keymap</c> variable. If you select the wrong
467	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.	453	<c>keymap</c>, you will get weird results when typing on your keyboard.
468	</p>	454	</p>
469		455
470	<note>	456	<note test="substring(func:keyval('arch'),1,3)='PPC'">
471	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	457	PPC uses x86 keymaps on most systems.
472	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
473	keymaps on most systems. Users who want to be able to use ADB keymaps on boot
474	have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
475	keymap in <path>/etc/conf.d/keymaps</path>.
476	</note>	458	</note>
477		459
478	<p>	460	<p>
479	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and	461	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
480	exit.	462	exit.
481	</p>	463	</p>
482		464
483	<p>	465	<p>
484	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it	466	Gentoo uses <path>/etc/conf.d/hwclock</path> to set clock options. Edit it
485	according to your needs.	467	according to your needs.
486	</p>	468	</p>
487		469
488	<pre caption="Opening /etc/conf.d/clock">	470	<pre caption="Opening /etc/conf.d/hwclock">
489	# <i>nano -w /etc/conf.d/clock</i>	471	# <i>nano -w /etc/conf.d/hwclock</i>
490	</pre>	472	</pre>
491		473
492	<p>	474	<p>
493	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	475	If your hardware clock is not using UTC, you need to add <c>clock="local"</c>
494	the file. Otherwise you will notice some clock skew. Furthermore, Windows	476	to the file. Otherwise you will notice some clock skew.
495	assumes that your hardware clock uses local time, so if you want to dualboot,
496	you should set this variable appropriately, otherwise your clock will go crazy.
497	</p>
498
499	<p>	477	</p>
		478
		479	<p>
500	When you're finished configuring <path>/etc/conf.d/clock</path>, save and	480	When you're finished configuring <path>/etc/conf.d/hwclock</path>, save and
501	exit.	481	exit.
502	</p>	482	</p>
503		483
504	<p>	484	<p>
505	If you are not installing Gentoo on IBM PPC64 hardware, continue with	485	You should define the timezone that you previously copied to
506	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.	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.
507	</p>	491	</p>
508		492
509	</body>	493	</body>
510	</subsection>
511	<subsection>	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>
		520
		521	<note>
		522	You can select your desired locales in the list given by running <c>locale -a</c>.
		523	</note>
		524
		525	<warn>
		526	We strongly suggest that you should use at least one UTF-8 locale because some
		527	applications may require it.
		528	</warn>
		529
		530	<p>
		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.
		533	</p>
		534
		535	<pre caption="Running locale-gen">
		536	# <i>locale-gen</i>
		537	</pre>
		538
		539	<p>
		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:
		542	</p>
		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
		549	<p>
		550	And reload your environment:
		551	</p>
		552
		553	<pre caption="Reload shell environment">
		554	# env-update && source /etc/profile
		555	</pre>
		556
		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>
		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
		569	</body>
		570	</subsection>
		571	<subsection test="func:keyval('arch')='PPC64'">
512	<title>Configuring the Console</title>	572	<title>Configuring the Console</title>
513	<body>	573	<body>
514		574
515	<note>
516	The following section applies to the IBM PPC64 hardware platforms.
517	</note>
518
519	<p>	575	<p>
520	If you are running Gentoo on IBM PPC64 hardware and using a virtual console	576	If you are using a virtual console, you must uncomment the appropriate line in
521	you must uncomment the appropriate line in <path>/etc/inittab</path> for the	577	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
522	virtual console to spawn a login prompt.
523	</p>	578	</p>
524		579
525	<pre caption="Enabling hvc or hvsi support in /etc/inittab">	580	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
526	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0	581	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
527	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0	582	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

 Legend:



Removed from v.1.76
 


changed lines


 
Added in v.1.115
 Legend:



Removed from v.1.76
 


changed lines


 
Added in v.1.115
-Removed from v.1.76
+Added in v.1.115

	ViewVC Help
Powered by ViewVC 1.1.13