/[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.61		Revision 1.99
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.61 2005/05/23 18:13:34 swift Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.99 2008/05/02 08:04:23 nightmorph 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.3</version>	17	<version>9.2</version>
12	<date>2005-05-23</date>	18	<date>2008-05-02</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 1 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 1 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 1 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>/etc/conf.d/net.example</path>. Also, you may want to emerge
		236	<c>openresolv</c> to help manage your DNS/NIS setup.
		237	</note>
211		238
212	</body>	239	</body>
213	</subsection>	240	</subsection>
214	<subsection>	241	<subsection>
215	<title>Configuring your Network</title>	242	<title>Configuring your Network</title>
216	<body>	243	<body>
217		244
218	<p>	245	<p>
219	Before you get that "Hey, we've had that already"-feeling, you should remember	246	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	247	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	248	just for the installation. Right now you are going to configure networking for
222	your Gentoo system permanently.	249	your Gentoo system permanently.
223	</p>	250	</p>
224		251
		252	<note>
		253	More detailed information about networking, including advanced topics like
		254	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
		255	link="?part=4">Gentoo Network Configuration</uri> section.
		256	</note>
		257
225	<p>	258	<p>
226	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	259	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	260	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 :)	261	networking manually. But don't fear, we'll explain everything. A fully
229	</p>	262	commented example that covers many different configurations is available in
230		263	<path>/etc/conf.d/net.example</path>.
231	<p>	264	</p>
		265
		266	<p>
		267	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		268	client. This is described later in <uri
		269	link="?part=1&chap=9#networking-tools">Installing Necessary System
		270	Tools</uri>. Do not forget to install a DHCP client.
		271	</p>
		272
		273	<p>
		274	If you need to configure your network connection either because you need
		275	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>	276	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
233	is used in this example):	277	this example):
234	</p>	278	</p>
235		279
236	<pre caption="Opening /etc/conf.d/net for editing">	280	<pre caption="Opening /etc/conf.d/net for editing">
237	# <i>nano -w /etc/conf.d/net</i>	281	# <i>nano -w /etc/conf.d/net</i>
238	</pre>	282	</pre>
239		283
240	<!-- Old baselayout - current stable -->
241
242	<p>
243	The first variable you'll find is <c>iface_eth0</c>. It uses the following
244	syntax:
245	</p>	284	<p>
246		285	You will see the following file:
247	<pre caption="iface_eth0 syntaxis">
248	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
249	</pre>
250
251	<p>	286	</p>
252	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	287
253	to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.	288	<pre caption="Default /etc/conf.d/net">
254	If you need to set up your network manually and you're	289	# This blank configuration will automatically use DHCP for any net.*
255	not familiar with all the above terms, please read the section on <uri	290	# scripts in /etc/init.d. To create a more complete configuration,
256	link="?part=1&chap=3#network_term">Understanding Network	291	# please review /etc/conf.d/net.example and save your configuration
257	Terminology</uri> if you haven't done so already.	292	# in /etc/conf.d/net (this file :]!).
		293	</pre>
		294
258	</p>	295	<p>
259		296	To enter your own IP address, netmask and gateway, you need
		297	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
260	<p>	298	</p>
261	So let us give three examples; the first one uses DHCP, the second one a static	299
262	IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and	300	<pre caption="Manually setting IP information for eth0">
263	gateway 192.168.0.1 while the third one just activates the interface for	301	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
264	rp-pppoe usage:	302	routes_eth0=( "default via 192.168.0.1" )
		303	</pre>
		304
265	</p>	305	<p>
266		306	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
267	<pre caption="Examples for /etc/conf.d/net">	307	<c>dhcp_eth0</c>:
268	<comment>(For DHCP)</comment>
269	iface_eth0="dhcp"
270	<comment># Some network admins require that you use the</comment>
271	<comment># hostname and domainname provided by the DHCP server.</comment>
272	<comment># In that case, add the following to let dhcpcd use them.</comment>
273	<comment># That will override your own hostname and domainname definitions.</comment>
274	dhcpcd_eth0="-HD"
275	<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
276	<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
277	dhcpcd_eth0="-N"
278
279	<comment>(For static IP)</comment>
280	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
281	gateway="eth0/192.168.0.1"
282
283	<comment>(For rp-pppoe)</comment>
284	iface_eth0="up"
285	</pre>
286
287	<p>	308	</p>
288	If you have several network interfaces, create extra <c>iface_eth</c> variables,
289	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
290	shouldn't be reproduced as you can only set one gateway per computer.
291	</p>
292		309
293	<!-- New baselayout - current testing
294
295	<p>
296	The first variable you'll find is called <c>config_eth0</c>. As you can probably
297	imagine, this variable configured the eth0 network interface. If the interface
298	needs to automatically obtain an IP through DHCP, you should set it like so:
299	</p>
300
301	<pre caption="Automatically obtaining an IP for eth0">	310	<pre caption="Automatically obtaining an IP address for eth0">
302	config_eth0=( "dhcp" )	311	config_eth0=( "dhcp" )
		312	dhcp_eth0="nodns nontp nonis"
303	</pre>	313	</pre>
304		314
305	<p>
306	However, if you have to enter your own IP address, netmask and gateway, you need
307	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
308	</p>	315	<p>
309		316	Please read <path>/etc/conf.d/net.example</path> for a list of all available
310	<pre caption="Manually setting IP information for eth0">	317	options.
311	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
312	routes_eth0=( "default gw 192.168.0.1" )
313	</pre>	318	</p>
314		319
315	<p>	320	<p>
316	If you have several network interfaces repeat the above steps for	321	If you have several network interfaces repeat the above steps for
317	<c>config_eth1</c>, <c>config_eth2</c>, etc.	322	<c>config_eth1</c>, <c>config_eth2</c>, etc.
318	</p>	323	</p>
319		324
320	-->
321
322	<p>	325	<p>
323	Now save the configuration and exit to continue.	326	Now save the configuration and exit to continue.
324	</p>	327	</p>
325		328
326	</body>	329	</body>
…		…
329	<title>Automatically Start Networking at Boot</title>	332	<title>Automatically Start Networking at Boot</title>
330	<body>	333	<body>
331		334
332	<p>	335	<p>
333	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
334	default runlevel. If you have PCMCIA interfaces you should skip this action as	337	default runlevel.
335	the PCMCIA interfaces are started by the PCMCIA init script.
336	</p>	338	</p>
337		339
338	<pre caption="Adding net.eth0 to the default runlevel">	340	<pre caption="Adding net.eth0 to the default runlevel">
339	# <i>rc-update add net.eth0 default</i>	341	# <i>rc-update add net.eth0 default</i>
340	</pre>	342	</pre>
…		…
345	use <c>ln</c> to do this:	347	use <c>ln</c> to do this:
346	</p>	348	</p>
347		349
348	<pre caption="Creating extra initscripts">	350	<pre caption="Creating extra initscripts">
349	# <i>cd /etc/init.d</i>	351	# <i>cd /etc/init.d</i>
350	# <i>ln -s net.eth0 net.eth1</i>	352	# <i>ln -s net.lo net.eth1</i>
351	# <i>rc-update add net.eth1 default</i>	353	# <i>rc-update add net.eth1 default</i>
352	</pre>	354	</pre>
353		355
354	</body>	356	</body>
355	</subsection>	357	</subsection>
…		…
357	<title>Writing Down Network Information</title>	359	<title>Writing Down Network Information</title>
358	<body>	360	<body>
359		361
360	<p>	362	<p>
361	You now need to inform Linux about your network. This is defined in	363	You now need to inform Linux about your network. This is defined in
362	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	364	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
363	for hosts that aren't resolved by your nameserver. For instance, if your	365	hosts that aren't resolved by your nameserver. You need to define your system.
364	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	366	You may also want to define other systems on your network if you don't want to
365	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	367	set up your own internal DNS system.
366	open <path>/etc/hosts</path> and fill in the values:
367	</p>	368	</p>
368		369
369	<pre caption="Opening /etc/hosts">	370	<pre caption="Opening /etc/hosts">
370	# <i>nano -w /etc/hosts</i>	371	# <i>nano -w /etc/hosts</i>
371	</pre>	372	</pre>
372		373
373	<pre caption="Filling in the networking information">	374	<pre caption="Filling in the networking information">
374	127.0.0.1 localhost	375	<comment>(This defines the current system)</comment>
		376	127.0.0.1 tux.homenetwork tux localhost
		377
		378	<comment>(Define extra systems on your network,
		379	they need to have a static IP to be defined this way.)</comment>
375	192.168.0.5 jenny.homenetwork jenny	380	192.168.0.5 jenny.homenetwork jenny
376	192.168.0.6 benny.homenetwork benny	381	192.168.0.6 benny.homenetwork benny
377	192.168.0.7 tux.homenetwork tux
378	</pre>
379
380	<p>
381	If your system is the only system (or the nameservers handle all name
382	resolution) a single line is sufficient. For instance, if you want to call your
383	system <c>tux</c>:
384	</p>
385
386	<pre caption="/etc/hosts for lonely or fully integrated PCs">
387	127.0.0.1 localhost tux
388	</pre>	382	</pre>
389		383
390	<p>	384	<p>
391	Save and exit the editor to continue.	385	Save and exit the editor to continue.
392	</p>	386	</p>
393		387
394	<p>	388	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
395	If you don't have PCMCIA, you can now continue with <uri	389	If you don't have PCMCIA, you can now continue with <uri
396	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	390	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
397	following topic on PCMCIA.	391	following topic on PCMCIA.
398	</p>	392	</p>
399		393
400	</body>	394	</body>
401	</subsection>	395	</subsection>
402	<subsection>	396	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
403	<title>Optional: Get PCMCIA Working</title>	397	<title>Optional: Get PCMCIA Working</title>
404	<body>	398	<body>
405		399
406	<note>
407	pcmcia-cs is only available for x86, amd64 and ppc platforms.
408	</note>
409
410	<p>	400	<p>
411	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	401	PCMCIA users should first install the <c>pcmciautils</c> package.
412	includes users who will be working with a 2.6 kernel (even though they won't be
413	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
414	to avoid installing xorg-x11 at this moment:
415	</p>	402	</p>
416		403
417	<pre caption="Installing pcmcia-cs">	404	<pre caption="Installing pcmciautils">
418	# <i>USE="-X" emerge pcmcia-cs</i>	405	# <i>emerge pcmciautils</i>
419	</pre>
420
421	<p>
422	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
423	runlevel:
424	</p>
425
426	<pre caption="Adding pcmcia to the default runlevel">
427	# <i>rc-update add pcmcia default</i>
428	</pre>	406	</pre>
429		407
430	</body>	408	</body>
431	</subsection>	409	</subsection>
432	</section>	410	</section>
433	<section>	411
		412	<section id="sysinfo">
434	<title>System Information</title>	413	<title>System Information</title>
435	<subsection>	414	<subsection>
436	<title>Root Password</title>	415	<title>Root Password</title>
437	<body>	416	<body>
438		417
…		…
442		421
443	<pre caption="Setting the root password">	422	<pre caption="Setting the root password">
444	# <i>passwd</i>	423	# <i>passwd</i>
445	</pre>	424	</pre>
446		425
447	<p>
448	If you want root to be able to log on through the serial console, add
449	<c>tts/0</c> to <path>/etc/securetty</path>:
450	</p>
451
452	<pre caption="Adding tts/0 to /etc/securetty">
453	# <i>echo "tts/0" >> /etc/securetty</i>
454	</pre>
455
456	</body>	426	</body>
457	</subsection>	427	</subsection>
458	<subsection>	428	<subsection>
459	<title>System Information</title>	429	<title>System Information</title>
460	<body>	430	<body>
…		…
467	<pre caption="Opening /etc/rc.conf">	437	<pre caption="Opening /etc/rc.conf">
468	# <i>nano -w /etc/rc.conf</i>	438	# <i>nano -w /etc/rc.conf</i>
469	</pre>	439	</pre>
470		440
471	<p>	441	<p>
		442	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		443	</p>
		444
		445	<p>
472	As you can see, this file is well commented to help you set up the necessary	446	As you can see, this file is well commented to help you set up the necessary
473	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	447	configuration variables. You can configure your system to use unicode and
474	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	448	define your default editor and your display manager (like gdm or kdm).
475	your keyboard.	449	</p>
		450
476	</p>	451	<p>
		452	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		453	Edit it to configure your keyboard.
		454	</p>
477		455
478	<note>	456	<pre caption="Opening /etc/conf.d/keymaps">
479	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	457	# <i>nano -w /etc/conf.d/keymaps</i>
480	select an i386 keymap (such as "us") instead of "sunkeymap".	458	</pre>
		459
		460	<p>
		461	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
		462	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
		463	</p>
		464
		465	<note test="substring(func:keyval('arch'),1,3)='PPC'">
		466	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
		467	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
		468	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
481	</note>	469	</note>
482		470
483	<p>	471	<p>
484	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	472	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
485	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	473	exit.
486	to set a mac/ppc keymap in <path>rc.conf</path>.
487	</p>
488
489	<p>	474	</p>
		475
		476	<p>
		477	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		478	according to your needs.
		479	</p>
		480
		481	<pre caption="Opening /etc/conf.d/clock">
		482	# <i>nano -w /etc/conf.d/clock</i>
		483	</pre>
		484
		485	<p>
490	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	486	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
491	the file. Otherwise you will notice some clock skew.	487	to the file. Otherwise you will notice some clock skew.
492	</p>
493
494	<p>	488	</p>
		489
		490	<p>
		491	You should define the timezone that you previously copied to
		492	<path>/etc/localtime</path> so that further upgrades of the
		493	<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
		494	automatically. For instance, if you used the GMT timezone, you would add
		495	<c>TIMEZONE="GMT"</c>
		496	</p>
		497
		498	<p>
495	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.	499	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
496	</p>	500	exit.
497
498	<p>	501	</p>
499	If you are not installing Gentoo on an IBM POWER5 or JS20 system, continue with	502
		503	<p test="not(func:keyval('arch')='PPC64')">
500	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.	504	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		505	Tools</uri>.
501	</p>	506	</p>
502		507
503	</body>	508	</body>
504	</subsection>
505	<subsection>	509	</subsection>
		510	<subsection test="func:keyval('arch')='PPC64'">
506	<title>Configuring the Console</title>	511	<title>Configuring the Console</title>
507	<body>	512	<body>
508		513
509	<note>
510	The following section applies to the IBM POWER5 and JS20 hardware platforms.
511	</note>
512
513	<p>
514	If you are running Gentoo in an LPAR or on a JS20 blade, you must uncomment
515	the hvc line in /etc/inittab for the virtual console to spawn a login prompt.
516	</p>	514	<p>
		515	If you are using a virtual console, you must uncomment the appropriate line in
		516	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
		517	</p>
517		518
518	<pre caption="Enabling hvc support in /etc/inittab">	519	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
519	hvc:12345:respawn:/sbin/agetty -nl /bin/bashlogin 9600 hvc0 vt220	520	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		521	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		522	</pre>
		523
		524	<p>
		525	You should also take this time to verify that the appropriate console is
		526	listed in <path>/etc/securetty</path>.
520	</pre>	527	</p>
521		528
522	<p>	529	<p>
523	You may now continue with <uri link="?part=1&chap=9">Installing Necessary	530	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
524	System Tools</uri>.	531	System Tools</uri>.
525	</p>	532	</p>

 Legend:



Removed from v.1.61
 


changed lines


 
Added in v.1.99
 Legend:



Removed from v.1.61
 


changed lines


 
Added in v.1.99
-Removed from v.1.61
+Added in v.1.99

	ViewVC Help
Powered by ViewVC 1.1.13