/[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.34		Revision 1.103
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.34 2004/06/03 20:58:34 neysx Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.103 2011/08/02 17:43:17 jkt Exp $ -->
8		8
9	<sections>	9	<sections>
		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
		17	<version>10</version>
		18	<date>2011-08-02</date>
		19
10	<section>	20	<section>
11	<title>Filesystem Information</title>	21	<title>Filesystem Information</title>
12	<subsection>	22	<subsection>
13	<title>What is fstab?</title>	23	<title>What is fstab?</title>
14	<body>	24	<body>
15		25
16	<p>	26	<p>
17	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
18	<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
19	(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
20	(special options) and when (automatically or not, can users mount those or not,	30	and with what special options (automatically or not, whether users can mount
21	etc.).	31	them or not, etc.)
22	</p>	32	</p>
23		33
24	</body>	34	</body>
25	</subsection>	35	</subsection>
26	<subsection>	36	<subsection>
…		…
37	<li>	47	<li>
38	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
39	file)	49	file)
40	</li>	50	</li>
41	<li>	51	<li>
42	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
43	mounted	53	mounted
44	</li>	54	</li>
45	<li>	55	<li>
46	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
47	</li>	57	</li>
48	<li>	58	<li>
49	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
50	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,
51	you are encouraged to read the mount manpage (<c>man mount</c>) for a full	61	you are encouraged to read the mount man page (<c>man mount</c>) for a full
52	listing. Multiple mountoptions are comma-separated.	62	listing. Multiple mount options are comma-separated.
53	</li>	63	</li>
54	<li>	64	<li>
55	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
56	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).
57	</li>	67	</li>
58	<li>	68	<li>
59	The sixth field is used by <c>fsck</c> to determine the order in which	69	The sixth field is used by <c>fsck</c> to determine the order in which
60	filesystems should be <b>check</b>ed if the system wasn't shut down properly.	70	filesystems should be <b>check</b>ed if the system wasn't shut down properly.
61	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>
62	(or <c>0</c> in case a filesystem check isn't necessary).	72	(or <c>0</c> if a filesystem check isn't necessary).
63	</li>	73	</li>
64	</ul>	74	</ul>
65		75
66	<p>	76	<impo>
67	So start <c>nano</c> (or your favorite editor) to create your	77	The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
68	<path>/etc/fstab</path>:	78	fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>.
69	</p>	79	</impo>
70		80
71	<pre caption="Opening /etc/fstab">	81	<pre caption="Opening /etc/fstab">
72	# <i>nano -w /etc/fstab</i>	82	# <i>nano -w /etc/fstab</i>
73	</pre>	83	</pre>
74		84
		85	</body>
		86	<body test="func:keyval('/boot')">
		87
75	<p>	88	<p>
76	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>
77	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
78	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.	91	<path>/boot</path>, don't copy it.
79	</p>
80
81	<p>	92	</p>
		93
		94	<p>
82	In our default x86 partitioning example <path>/boot</path> is the	95	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
83	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't	96	usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
84	be mounted automatically (<c>noauto</c>) but does need to be checked. So we	97	filesystem. It needs to be checked during boot, so we would write down:
85	would write down:
86	</p>	98	</p>
87		99
88	<pre caption="An example /boot line for /etc/fstab">	100	<pre caption="An example /boot line for /etc/fstab">
89	/dev/hda1 /boot ext2 noauto 1 2	101	<keyval id="/boot"/> /boot ext2 defaults 1 2
90	</pre>	102	</pre>
91		103
92	<p>
93	Now, to improve performance, most users would want to add the <c>noatime</c>
94	option as mountoption, which results in a faster system since access times
95	aren't registered (you don't need those generally anyway):
96	</p>	104	<p>
97		105	Some users don't want their <path>/boot</path> partition to be mounted
98	<pre caption="An improved /boot line for /etc/fstab">	106	automatically to improve their system's security. Those people should
99	/dev/hda1 /boot ext2 noauto,noatime 1 2	107	substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
100	</pre>	108	manually mount this partition every time you want to use it.
101
102	<p>	109	</p>
103	If we continue with this, we would end up with the following three lines (for	110
104	<path>/boot</path>, <path>/</path> and the swap partition):	111	</body>
		112	<body>
		113
105	</p>	114	<p>
		115	Add the rules that match your partitioning scheme and append rules for
		116	your CD-ROM drive(s), and of course, if you have other partitions or drives,
		117	for those too.
		118	</p>
106		119
107	<pre caption="Three /etc/fstab lines">	120	<p>
108	/dev/hda1 /boot ext2 noauto,noatime 1 2	121	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
		122	</p>
		123
		124	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
		125	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
		126	/dev/sda3 none swap sw 0 0
		127	/dev/sda4 / ext3 noatime 0 1
		128
		129	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		130
		131	proc /proc proc defaults 0 0
		132	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		133	</pre>
		134
		135	<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'">
		136	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
109	/dev/hda2 none swap sw 0 0	137	/dev/sda2 none swap sw 0 0
110	/dev/hda3 / ext3 noatime 0 1	138	/dev/sda3 / ext3 noatime 0 1
111	</pre>
112		139
113	<p>	140	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
114	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>	141
115	(required) and for your CD-ROM drive (and of course, if you have other	142	proc /proc proc defaults 0 0
116	partitions or drives, for those too):	143	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
117	</p>	144	</pre>
118		145
119	<pre caption="A full /etc/fstab example">	146	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
120	/dev/hda1 /boot ext2 noauto,noatime 1 2	147	/dev/sda1 / ext3 noatime 0 1
121	/dev/hda2 none swap sw 0 0	148	/dev/sda2 none swap sw 0 0
		149	/dev/sda4 /usr ext3 noatime 0 2
		150	/dev/sda5 /var ext3 noatime 0 2
		151	/dev/sda6 /home ext3 noatime 0 2
		152
		153	<comment># You must add the rules for openprom</comment>
		154	openprom /proc/openprom openpromfs defaults 0 0
		155
		156	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		157
		158	proc /proc proc defaults 0 0
		159	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		160	</pre>
		161
		162	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or
		163	func:keyval('arch')='PPC64'">
122	/dev/hda3 / ext3 noatime 0 1	164	/dev/sda4 / ext3 noatime 0 1
		165	/dev/sda3 none swap sw 0 0
123		166
		167	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		168
124	none /proc proc defaults 0 0	169	proc /proc proc defaults 0 0
125	none /dev/shm tmpfs defaults 0 0	170	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
126
127	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
128	</pre>	171	</pre>
129		172
130	<p>	173	<p>
131	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for	174	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
132	removable media as they can be created with one of many filesystems) and	175	removable media as they can be created with one of many filesystems) and
133	<c>user</c> makes it possible for non-root users to mount the CD.	176	<c>user</c> makes it possible for non-root users to mount the CD.
134	</p>	177	</p>
135		178
136	<p>	179	<p>
137	Now use the above example to create your <path>/etc/fstab</path>. If you are a	180	To improve performance, most users would want to add the <c>noatime</c>
138	<b>SPARC</b>-user, you should add the following line to your	181	mount option, which results in a faster system since access times
139	<path>/etc/fstab</path>	182	aren't registered (you don't need those generally anyway).
140	too:
141	</p>
142
143	<pre caption="Adding openprom filesystem to /etc/fstab">
144	none /proc/openprom openpromfs defaults 0 0
145	</pre>
146
147	<p>	183	</p>
148	If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
149	</p>
150
151	<pre caption="Adding usbfs filesystem to /etc/fstab">
152	none /proc/bus/usb usbfs defaults 0 0
153	</pre>
154		184
155	<p>	185	<p>
156	Double-check your <path>/etc/fstab</path>, save and quit to continue.	186	Double-check your <path>/etc/fstab</path>, save and quit to continue.
157	</p>	187	</p>
158		188
…		…
160	</subsection>	190	</subsection>
161	</section>	191	</section>
162	<section>	192	<section>
163	<title>Networking Information</title>	193	<title>Networking Information</title>
164	<subsection>	194	<subsection>
165	<title>Hostname, Domainname etc.</title>	195	<title>Host name, Domainname, etc</title>
166	<body>	196	<body>
167		197
168	<p>	198	<p>
169	One of the choices the user has to make is name his/her PC. This seems to be	199	One of the choices the user has to make is name his/her PC. This seems to be
170	quite easy, but <e>lots</e> of users are having difficulties finding the	200	quite easy, but <e>lots</e> of users are having difficulties finding the
171	appropriate name for their Linux-pc. To speed things up, know that any name you	201	appropriate name for their Linux-pc. To speed things up, know that any name you
172	choose can be changed afterwards. For all we care, you can just call your system	202	choose can be changed afterwards. For all we care, you can just call your system
173	<c>tux</c> and domain <c>homenetwork</c>.	203	<c>tux</c> and domain <c>homenetwork</c>.
174	</p>	204	</p>
175		205
176	<p>
177	We use these values in the next examples. First we set the hostname:
178	</p>
179
180	<pre caption="Setting the hostname">	206	<pre caption="Setting the host name">
181	# <i>echo tux > /etc/hostname</i>	207	# <i>nano -w /etc/conf.d/hostname</i>
182	</pre>
183		208
		209	<comment>(Set the HOSTNAME variable to your host name)</comment>
		210	HOSTNAME="<i>tux</i>"
		211	</pre>
		212
184	<p>	213	<p>
185	Second we set the domainname:	214	Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
		215	You only need a domain if your ISP or network administrator says so, or if you
		216	have a DNS server but not a DHCP server. You don't need to worry about DNS or
		217	domainnames if your networking is setup for DHCP.
186	</p>	218	</p>
187		219
188	<pre caption="Setting the domainname">	220	<pre caption="Setting the domainname">
189	# <i>echo homenetwork > /etc/dnsdomainname</i>	221	# <i>nano -w /etc/conf.d/net</i>
		222
		223	<comment>(Set the dns_domain variable to your domain name)</comment>
		224	dns_domain_lo="<i>homenetwork</i>"
190	</pre>	225	</pre>
		226
		227	<note>
		228	If you choose not to set a domainname, you can get rid of the "This is
		229	hostname.(none)" messages at your login screen by editing
		230	<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
		231	</note>
191		232
192	<p>	233	<p>
193	If you have a NIS domain (if you don't know what that is, then you don't have	234	If you have a NIS domain (if you don't know what that is, then you don't have
194	one), you need to define that one too:	235	one), you need to define that one too:
195	</p>	236	</p>
196		237
197	<pre caption="Setting the NIS domainname">	238	<pre caption="Setting the NIS domainname">
198	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	239	# <i>nano -w /etc/conf.d/net</i>
199	</pre>
200		240
201	<p>	241	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
202	Now add the <c>domainname</c> script to the default runlevel:	242	nis_domain_lo="<i>my-nisdomain</i>"
203	</p>	243	</pre>
204		244
205	<pre caption="Adding domainname to the default runlevel">	245	<note>
206	# <i>rc-update add domainname default</i>	246	For more information on configuring DNS and NIS, please read the examples
207	</pre>	247	provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
		248	<c>openresolv</c> to help manage your DNS/NIS setup.
		249	</note>
208		250
209	</body>	251	</body>
210	</subsection>	252	</subsection>
211	<subsection>	253	<subsection>
212	<title>Configuring your Network</title>	254	<title>Configuring your Network</title>
213	<body>	255	<body>
214		256
215	<p>	257	<p>
216	Before you get that "Hey, we've had that already"-feeling, you should remember	258	Before you get that "Hey, we've had that already"-feeling, you should remember
217	that the networking you set up in the beginning of the gentoo installation was	259	that the networking you set up in the beginning of the Gentoo installation was
218	just for the installation. Right now you are going to configure networking for	260	just for the installation. Right now you are going to configure networking for
219	your Gentoo system permanently.	261	your Gentoo system permanently.
220	</p>	262	</p>
221		263
		264	<note>
		265	More detailed information about networking, including advanced topics like
		266	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
		267	link="?part=4">Gentoo Network Configuration</uri> section.
		268	</note>
		269
222	<p>	270	<p>
223	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	271	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
224	a straightforward yet not intuitive syntax if you don't know how to setup	272	a straightforward yet not intuitive syntax if you don't know how to set up
225	networking manually. But don't fear, we'll explain everything :)	273	networking manually. But don't fear, we'll explain everything. A fully
226	</p>	274	commented example that covers many different configurations is available in
227		275	<path>/etc/conf.d/net.example</path>.
228	<p>	276	</p>
		277
		278	<p>
		279	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		280	client. This is described later in <uri
		281	link="?part=1&chap=9#networking-tools">Installing Necessary System
		282	Tools</uri>. Do not forget to install a DHCP client.
		283	</p>
		284
		285	<p>
		286	If you need to configure your network connection either because you need
		287	specific DHCP options or because you do not use DHCP at all, open
229	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>	288	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
230	is used in this example):	289	this example):
231	</p>	290	</p>
232		291
233	<pre caption="Opening /etc/conf.d/net for editing">	292	<pre caption="Opening /etc/conf.d/net for editing">
234	# <i>nano -w /etc/conf.d/net</i>	293	# <i>nano -w /etc/conf.d/net</i>
235	</pre>	294	</pre>
236		295
237	<p>	296	<p>
238	The first variable you'll find is <c>iface_eth0</c>. It uses the following	297	You will see the following file:
239	syntax:
240	</p>
241
242	<pre caption="iface_eth0 syntaxis">
243	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
244	</pre>
245
246	<p>	298	</p>
247	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	299
248	to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.	300	<pre caption="Default /etc/conf.d/net">
249	If you need to setup your network manually and you're	301	# This blank configuration will automatically use DHCP for any net.*
250	not familiar with all the above terms, please read the section on <uri	302	# scripts in /etc/init.d. To create a more complete configuration,
251	link="?part=1&chap=3#doc_chap4_sect3">Understanding Network	303	# please review /etc/conf.d/net.example and save your configuration
252	Terminology</uri> if you haven't done so already.	304	# in /etc/conf.d/net (this file :]!).
		305	</pre>
		306
253	</p>	307	<p>
254		308	To enter your own IP address, netmask and gateway, you need
		309	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
255	<p>	310	</p>
256	So let us give three examples; the first one uses DHCP, the second one a static	311
257	IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and	312	<pre caption="Manually setting IP information for eth0">
258	gateway 192.168.0.1 while the third one just activates the interface for	313	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
259	rp-pppoe usage:	314	routes_eth0=( "default via 192.168.0.1" )
		315	</pre>
		316
260	</p>	317	<p>
261		318	To use DHCP, define <c>config_eth0</c>:
262	<pre caption="Examples for /etc/conf.d/net">
263	<comment>(For DHCP)</comment>
264	iface_eth0="dhcp"
265
266	<comment>(For static IP)</comment>
267	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
268	gateway="eth0/192.168.0.1"
269
270	<comment>(For rp-pppoe)</comment>
271	iface_eth0="up"
272	</pre>
273
274	<p>	319	</p>
275	If you have several network interfaces, create extra <c>iface_eth</c> variables,	320
276	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable	321	<pre caption="Automatically obtaining an IP address for eth0">
277	shouldn't be reproduced as you can only set one gateway per computer.	322	config_eth0=( "dhcp" )
		323	</pre>
		324
		325	<p>
		326	Please read <path>/etc/conf.d/net.example</path> for a list of all available
		327	options. Be sure to also read your DHCP client manpage if you need to set
		328	specific DHCP options.
		329	</p>
		330
		331	<p>
		332	If you have several network interfaces repeat the above steps for
		333	<c>config_eth1</c>, <c>config_eth2</c>, etc.
278	</p>	334	</p>
279		335
280	<p>	336	<p>
281	Now save the configuration and exit to continue.	337	Now save the configuration and exit to continue.
282	</p>	338	</p>
…		…
286	<subsection>	342	<subsection>
287	<title>Automatically Start Networking at Boot</title>	343	<title>Automatically Start Networking at Boot</title>
288	<body>	344	<body>
289		345
290	<p>	346	<p>
291	To have your network interfaces activated at boot, you need to add those to the	347	To have your network interfaces activated at boot, you need to add them to the
292	default runlevel. If you have PCMCIA interfaces you should skip this action as	348	default runlevel.
293	the PCMCIA interfaces are started by the PCMCIA init script.
294	</p>	349	</p>
295		350
296	<pre caption="Adding net.eth0 to the default runlevel">	351	<pre caption="Adding net.eth0 to the default runlevel">
		352	# <i>cd /etc/init.d</i>
		353	# <i>ln -s net.lo net.eth0</i>
297	# <i>rc-update add net.eth0 default</i>	354	# <i>rc-update add net.eth0 default</i>
298	</pre>	355	</pre>
299		356
300	<p>	357	<p>
301	If you have several network interfaces, you need to create the appropriate	358	If you have several network interfaces, you need to create the appropriate
302	<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can	359	<path>net.eth1</path>, <path>net.eth2</path> etc. just like you did with
303	use <c>ln</c> to do this:	360	<path>net.eth0</path>.
304	</p>
305
306	<pre caption="Creating extra initscripts">
307	# <i>cd /etc/init.d</i>
308	# <i>ln -s net.eth0 net.eth1</i>
309	# <i>rc-update add net.eth1 default</i>
310	</pre>	361	</p>
311		362
312	</body>	363	</body>
313	</subsection>	364	</subsection>
314	<subsection>	365	<subsection>
315	<title>Writing Down Network Information</title>	366	<title>Writing Down Network Information</title>
316	<body>	367	<body>
317		368
318	<p>	369	<p>
319	You now need to inform Linux about your network. This is defined in	370	You now need to inform Linux about your network. This is defined in
320	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	371	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
321	for hosts that aren't resolved by your nameserver. For instance, if your	372	hosts that aren't resolved by your nameserver. You need to define your system.
322	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	373	You may also want to define other systems on your network if you don't want to
323	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	374	set up your own internal DNS system.
324	open <path>/etc/hosts</path> and fill in the values:
325	</p>	375	</p>
326		376
327	<pre caption="Opening /etc/hosts">	377	<pre caption="Opening /etc/hosts">
328	# <i>nano -w /etc/hosts</i>	378	# <i>nano -w /etc/hosts</i>
329	</pre>	379	</pre>
330		380
331	<pre caption="Filling in the networking information">	381	<pre caption="Filling in the networking information">
332	127.0.0.1 localhost	382	<comment>(This defines the current system)</comment>
		383	127.0.0.1 tux.homenetwork tux localhost
		384
		385	<comment>(Define extra systems on your network,
		386	they need to have a static IP to be defined this way.)</comment>
333	192.168.0.5 jenny.homenetwork jenny	387	192.168.0.5 jenny.homenetwork jenny
334	192.168.0.6 benny.homenetwork benny	388	192.168.0.6 benny.homenetwork benny
335	192.168.0.7 tux.homenetwork tux
336	</pre>
337
338	<p>
339	If your system is the only system (or the nameservers handle all name
340	resolution) a single line is sufficient:
341	</p>
342
343	<pre caption="/etc/hosts for lonely or fully integrated PCs">
344	127.0.0.1 localhost
345	</pre>	389	</pre>
346		390
347	<p>	391	<p>
348	Save and exit the editor to continue.	392	Save and exit the editor to continue.
349	</p>	393	</p>
350		394
351	<p>	395	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
352	If you don't have PCMCIA, you can now continue with <uri	396	If you don't have PCMCIA, you can now continue with <uri
353	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	397	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
354	following topic on PCMCIA.	398	following topic on PCMCIA.
355	</p>	399	</p>
356		400
357	</body>	401	</body>
358	</subsection>	402	</subsection>
359	<subsection>	403	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
360	<title>Optional: Get PCMCIA Working</title>	404	<title>Optional: Get PCMCIA Working</title>
361	<body>	405	<body>
362		406
363	<note>
364	pcmcia-cs is only available for x86, amd64 and ppc platforms.
365	</note>
366
367	<p>	407	<p>
368	PCMCIA-users should first install the <c>pcmcia-cs</c> package. The	408	PCMCIA users should first install the <c>pcmciautils</c> package.
369	<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:
370	</p>	409	</p>
371		410
372	<pre caption="Installing pcmcia-cs">	411	<pre caption="Installing pcmciautils">
373	# <i>USE="-X" emerge pcmcia-cs</i>	412	# <i>emerge pcmciautils</i>
374	</pre>
375
376	<p>
377	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
378	runlevel:
379	</p>
380
381	<pre caption="Adding pcmcia to the default runlevel">
382	# <i>rc-update add pcmcia default</i>
383	</pre>	413	</pre>
384		414
385	</body>	415	</body>
386	</subsection>	416	</subsection>
387	</section>	417	</section>
		418
		419	<section id="sysinfo">
		420	<title>System Information</title>
388	<section>	421	<subsection>
		422	<title>Root Password</title>
		423	<body>
		424
		425	<p>
		426	First we set the root password by typing:
		427	</p>
		428
		429	<pre caption="Setting the root password">
		430	# <i>passwd</i>
		431	</pre>
		432
		433	</body>
		434	</subsection>
		435	<subsection>
389	<title>System Information</title>	436	<title>System Information</title>
390	<body>	437	<body>
391		438
392	<p>	439	<p>
393	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.	440	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
…		…
397	<pre caption="Opening /etc/rc.conf">	444	<pre caption="Opening /etc/rc.conf">
398	# <i>nano -w /etc/rc.conf</i>	445	# <i>nano -w /etc/rc.conf</i>
399	</pre>	446	</pre>
400		447
401	<p>	448	<p>
		449	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		450	</p>
		451
		452	<p>
402	As you can see, this file is well commented to help you set up the necessary	453	As you can see, this file is well commented to help you set up the necessary
403	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	454	configuration variables. You can configure your system to use unicode and
404	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	455	define your default editor and your display manager (like gdm or kdm).
405	your keyboard.	456	</p>
		457
406	</p>	458	<p>
		459	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		460	Edit it to configure your keyboard.
		461	</p>
407		462
408	<note>	463	<pre caption="Opening /etc/conf.d/keymaps">
409	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	464	# <i>nano -w /etc/conf.d/keymaps</i>
410	select an i386 keymap (such as "us") instead of "sunkeymap".	465	</pre>
		466
		467	<p>
		468	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
		469	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
		470	</p>
		471
		472	<note test="substring(func:keyval('arch'),1,3)='PPC'">
		473	PPC uses x86 keymaps on most systems.
411	</note>	474	</note>
412		475
413	<p>	476	<p>
414	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	477	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
415	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	478	exit.
416	to set a mac/ppc keymap in <path>rc.conf</path>.
417	</p>
418
419	<p>	479	</p>
420	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then	480
421	continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>.
422	</p>	481	<p>
		482	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		483	according to your needs.
		484	</p>
423		485
		486	<pre caption="Opening /etc/conf.d/clock">
		487	# <i>nano -w /etc/conf.d/clock</i>
		488	</pre>
		489
		490	<p>
		491	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
		492	to the file. Otherwise you will notice some clock skew.
		493	</p>
		494
		495	<p>
		496	You should define the timezone that you previously copied to
		497	<path>/etc/localtime</path> so that further upgrades of the
		498	<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
		499	automatically. For instance, if you used the GMT timezone, you would add
		500	<c>TIMEZONE="GMT"</c>
		501	</p>
		502
		503	<p>
		504	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
		505	exit.
		506	</p>
		507
		508	<p test="not(func:keyval('arch')='PPC64')">
		509	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		510	Tools</uri>.
		511	</p>
		512
		513	</body>
		514	</subsection>
		515	<subsection test="func:keyval('arch')='PPC64'">
		516	<title>Configuring the Console</title>
424	</body>	517	<body>
		518
		519	<p>
		520	If you are using a virtual console, you must uncomment the appropriate line in
		521	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
		522	</p>
		523
		524	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
		525	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		526	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		527	</pre>
		528
		529	<p>
		530	You should also take this time to verify that the appropriate console is
		531	listed in <path>/etc/securetty</path>.
		532	</p>
		533
		534	<p>
		535	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
		536	System Tools</uri>.
		537	</p>
		538
		539	</body>
		540	</subsection>
425	</section>	541	</section>
426	</sections>	542	</sections>

 Legend:



Removed from v.1.34
 


changed lines


 
Added in v.1.103
 Legend:



Removed from v.1.34
 


changed lines


 
Added in v.1.103
-Removed from v.1.34
+Added in v.1.103

	ViewVC Help
Powered by ViewVC 1.1.20