/[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.45		Revision 1.78
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.45 2004/08/30 17:44:00 neysx Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.78 2006/05/27 13:02:15 neysx Exp $ -->
8		8
9	<sections>	9	<sections>
		10
		11	<version>2.19</version>
		12	<date>2006-05-27</date>
		13
10	<section>	14	<section>
11	<title>Filesystem Information</title>	15	<title>Filesystem Information</title>
12	<subsection>	16	<subsection>
13	<title>What is fstab?</title>	17	<title>What is fstab?</title>
14	<body>	18	<body>
…		…
46	The third field shows the <b>filesystem</b> used by the partition	50	The third field shows the <b>filesystem</b> used by the partition
47	</li>	51	</li>
48	<li>	52	<li>
49	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it	53	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it
50	wants to mount the partition. As every filesystem has its own mountoptions,	54	wants to mount the partition. As every filesystem has its own mountoptions,
51	you are encouraged to read the mount manpage (<c>man mount</c>) for a full	55	you are encouraged to read the mount man page (<c>man mount</c>) for a full
52	listing. Multiple mountoptions are comma-separated.	56	listing. Multiple mountoptions are comma-separated.
53	</li>	57	</li>
54	<li>	58	<li>
55	The fifth field is used by <c>dump</c> to determine if the partition needs to	59	The fifth field is used by <c>dump</c> to determine if the partition needs to
56	be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).	60	be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
…		…
62	(or <c>0</c> if a filesystem check isn't necessary).	66	(or <c>0</c> if a filesystem check isn't necessary).
63	</li>	67	</li>
64	</ul>	68	</ul>
65		69
66	<p>	70	<p>
67	The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab	71	The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
68	file</e>, so start <c>nano</c> (or your favorite editor) to create your	72	fstab file</e>, so start <c>nano</c> (or your favorite editor) to create your
69	<path>/etc/fstab</path>:	73	<path>/etc/fstab</path>:
70	</p>	74	</p>
71		75
72	<pre caption="Opening /etc/fstab">	76	<pre caption="Opening /etc/fstab">
73	# <i>nano -w /etc/fstab</i>	77	# <i>nano -w /etc/fstab</i>
74	</pre>	78	</pre>
75		79
76	<p>	80	<p>
77	Let us take a look at how we write down the options for the <path>/boot</path>	81	Let us take a look at how we write down the options for the <path>/boot</path>
78	partition. This is just an example, so if your architecture doesn't require a	82	partition. This is just an example, so if your architecture doesn't require a
79	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.	83	<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it
		84	verbatim.
80	</p>	85	</p>
81		86
82	<p>	87	<p>
83	In our default x86 partitioning example <path>/boot</path> is the	88	In our default x86 partitioning example <path>/boot</path> is the
84	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.	89	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
…		…
122	(required) and for your CD-ROM drive (and of course, if you have other	127	(required) and for your CD-ROM drive (and of course, if you have other
123	partitions or drives, for those too):	128	partitions or drives, for those too):
124	</p>	129	</p>
125		130
126	<pre caption="A full /etc/fstab example">	131	<pre caption="A full /etc/fstab example">
127	/dev/hda1 /boot ext2 noauto,noatime 1 2	132	/dev/hda1 /boot ext2 defaults,noatime 1 2
128	/dev/hda2 none swap sw 0 0	133	/dev/hda2 none swap sw 0 0
129	/dev/hda3 / ext3 noatime 0 1	134	/dev/hda3 / ext3 noatime 0 1
130		135
131	none /proc proc defaults 0 0	136	none /proc proc defaults 0 0
132	none /dev/shm tmpfs defaults 0 0	137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
133		138
134	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	139	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
135	</pre>	140	</pre>
136		141
137	<p>	142	<p>
…		…
147	too:	152	too:
148	</p>	153	</p>
149		154
150	<pre caption="Adding openprom filesystem to /etc/fstab">	155	<pre caption="Adding openprom filesystem to /etc/fstab">
151	none /proc/openprom openpromfs defaults 0 0	156	none /proc/openprom openpromfs defaults 0 0
152	</pre>
153
154	<p>
155	If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
156	</p>
157
158	<pre caption="Adding usbfs filesystem to /etc/fstab">
159	none /proc/bus/usb usbfs defaults 0 0
160	</pre>	157	</pre>
161		158
162	<p>	159	<p>
163	Double-check your <path>/etc/fstab</path>, save and quit to continue.	160	Double-check your <path>/etc/fstab</path>, save and quit to continue.
164	</p>	161	</p>
…		…
183	<p>	180	<p>
184	We use these values in the next examples. First we set the hostname:	181	We use these values in the next examples. First we set the hostname:
185	</p>	182	</p>
186		183
187	<pre caption="Setting the hostname">	184	<pre caption="Setting the hostname">
188	# <i>echo tux > /etc/hostname</i>	185	# <i>nano -w /etc/conf.d/hostname</i>
		186
		187	<comment>(Set the HOSTNAME variable to your hostname)</comment>
		188	HOSTNAME="<i>tux</i>"
189	</pre>	189	</pre>
190		190
191	<p>	191	<p>
192	Second we set the domainname:	192	Second we set the domainname:
193	</p>	193	</p>
194		194
195	<pre caption="Setting the domainname">	195	<pre caption="Setting the domainname">
196	# <i>echo homenetwork > /etc/dnsdomainname</i>	196	# <i>nano -w /etc/conf.d/domainname</i>
		197
		198	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>
		199	DNSDOMAIN="<i>homenetwork</i>"
197	</pre>	200	</pre>
198		201
199	<p>	202	<p>
200	If you have a NIS domain (if you don't know what that is, then you don't have	203	If you have a NIS domain (if you don't know what that is, then you don't have
201	one), you need to define that one too:	204	one), you need to define that one too:
202	</p>	205	</p>
203		206
204	<pre caption="Setting the NIS domainname">	207	<pre caption="Setting the NIS domainname">
205	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	208	# <i>nano -w /etc/conf.d/domainname</i>
206	</pre>
207		209
208	<p>	210	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
209	Now add the <c>domainname</c> script to the default runlevel:	211	NISDOMAIN="<i>my-nisdomain</i>"
210	</p>
211
212	<pre caption="Adding domainname to the default runlevel">
213	# <i>rc-update add domainname default</i>
214	</pre>	212	</pre>
215		213
216	</body>	214	</body>
217	</subsection>	215	</subsection>
218	<subsection>	216	<subsection>
219	<title>Configuring your Network</title>	217	<title>Configuring your Network</title>
220	<body>	218	<body>
221		219
222	<p>	220	<p>
223	Before you get that "Hey, we've had that already"-feeling, you should remember	221	Before you get that "Hey, we've had that already"-feeling, you should remember
224	that the networking you set up in the beginning of the gentoo installation was	222	that the networking you set up in the beginning of the Gentoo installation was
225	just for the installation. Right now you are going to configure networking for	223	just for the installation. Right now you are going to configure networking for
226	your Gentoo system permanently.	224	your Gentoo system permanently.
227	</p>	225	</p>
228		226
		227	<note>
		228	More detailed information about networking, including advanced topics like
		229	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
		230	link="?part=4">Gentoo Network Configuration</uri> section.
		231	</note>
		232
229	<p>	233	<p>
230	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	234	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
231	a straightforward yet not intuitive syntax if you don't know how to setup	235	a straightforward yet not intuitive syntax if you don't know how to set up
232	networking manually. But don't fear, we'll explain everything :)	236	networking manually. But don't fear, we'll explain everything. A fully
233	</p>	237	commented example that covers many different configurations is available in
234		238	<path>/etc/conf.d/net.example</path>.
235	<p>	239	</p>
		240
		241	<p>
		242	DHCP is used by default and does not require any further configuration.
		243	</p>
		244
		245	<p>
		246	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
236	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>	248	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
237	is used in this example):	249	this example):
238	</p>	250	</p>
239		251
240	<pre caption="Opening /etc/conf.d/net for editing">	252	<pre caption="Opening /etc/conf.d/net for editing">
241	# <i>nano -w /etc/conf.d/net</i>	253	# <i>nano -w /etc/conf.d/net</i>
242	</pre>	254	</pre>
243		255
244	<p>	256	<p>
245	The first variable you'll find is <c>iface_eth0</c>. It uses the following	257	You will see the following file:
246	syntax:
247	</p>
248
249	<pre caption="iface_eth0 syntaxis">
250	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
251	</pre>
252
253	<p>	258	</p>
254	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	259
255	to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.	260	<pre caption="Default /etc/conf.d/net">
256	If you need to setup your network manually and you're	261	# This blank configuration will automatically use DHCP for any net.*
257	not familiar with all the above terms, please read the section on <uri	262	# scripts in /etc/init.d. To create a more complete configuration,
258	link="?part=1&chap=3#network_term">Understanding Network	263	# please review /etc/conf.d/net.example and save your configuration
259	Terminology</uri> if you haven't done so already.	264	# in /etc/conf.d/net (this file :]!).
		265	</pre>
		266
260	</p>	267	<p>
261		268	To enter your own IP address, netmask and gateway, you need
		269	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
262	<p>	270	</p>
263	So let us give three examples; the first one uses DHCP, the second one a static	271
264	IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and	272	<pre caption="Manually setting IP information for eth0">
265	gateway 192.168.0.1 while the third one just activates the interface for	273	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
266	rp-pppoe usage:	274	routes_eth0=( "default gw 192.168.0.1" )
		275	</pre>
		276
267	</p>	277	<p>
268		278	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
269	<pre caption="Examples for /etc/conf.d/net">	279	<c>dhcp_eth0</c>:
270	<comment>(For DHCP)</comment>
271	iface_eth0="dhcp"
272	<comment># Some network admins require that you use the</comment>
273	<comment># hostname and domainname provided by the DHCP server.</comment>
274	<comment># In that case, add the following to let dhcpcd use them.</comment>
275	<comment># That will override your own hostname and domainname definitions.</comment>
276	dhcpcd_eth0="-HD"
277	<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
278	<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
279	dhcpcd_eth0="-N"
280
281	<comment>(For static IP)</comment>
282	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
283	gateway="eth0/192.168.0.1"
284
285	<comment>(For rp-pppoe)</comment>
286	iface_eth0="up"
287	</pre>
288
289	<p>	280	</p>
290	If you have several network interfaces, create extra <c>iface_eth</c> variables,	281
291	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable	282	<pre caption="Automatically obtaining an IP address for eth0">
292	shouldn't be reproduced as you can only set one gateway per computer.	283	config_eth0=( "dhcp" )
		284	dhcp_eth0="nodns nontp nonis"
		285	</pre>
		286
		287	<p>
		288	Please read <path>/etc/conf.d/net.example</path> for a list of all available
		289	options.
		290	</p>
		291
		292	<p>
		293	If you have several network interfaces repeat the above steps for
		294	<c>config_eth1</c>, <c>config_eth2</c>, etc.
293	</p>	295	</p>
294		296
295	<p>	297	<p>
296	Now save the configuration and exit to continue.	298	Now save the configuration and exit to continue.
297	</p>	299	</p>
…		…
330	<title>Writing Down Network Information</title>	332	<title>Writing Down Network Information</title>
331	<body>	333	<body>
332		334
333	<p>	335	<p>
334	You now need to inform Linux about your network. This is defined in	336	You now need to inform Linux about your network. This is defined in
335	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	337	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for
336	for hosts that aren't resolved by your nameserver. For instance, if your	338	hosts that aren't resolved by your nameserver. You need to define your system.
337	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	339	You may also want to define other systems on your network if you don't want to
338	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	340	set up your own internal DNS system.
339	open <path>/etc/hosts</path> and fill in the values:
340	</p>	341	</p>
341		342
342	<pre caption="Opening /etc/hosts">	343	<pre caption="Opening /etc/hosts">
343	# <i>nano -w /etc/hosts</i>	344	# <i>nano -w /etc/hosts</i>
344	</pre>	345	</pre>
345		346
346	<pre caption="Filling in the networking information">	347	<pre caption="Filling in the networking information">
347	127.0.0.1 localhost	348	<comment>(This defines the current system)</comment>
		349	127.0.0.1 tux.homenetwork tux localhost
		350
		351	<comment>(Define extra systems on your network,
		352	they need to have a static IP to be defined this way.)</comment>
348	192.168.0.5 jenny.homenetwork jenny	353	192.168.0.5 jenny.homenetwork jenny
349	192.168.0.6 benny.homenetwork benny	354	192.168.0.6 benny.homenetwork benny
350	192.168.0.7 tux.homenetwork tux
351	</pre>
352
353	<p>
354	If your system is the only system (or the nameservers handle all name
355	resolution) a single line is sufficient. For instance, if you want to call your
356	system <c>tux.homenetwork</c>:
357	</p>
358
359	<pre caption="/etc/hosts for lonely or fully integrated PCs">
360	127.0.0.1 tux.homenetwork tux localhost
361	</pre>	355	</pre>
362		356
363	<p>	357	<p>
364	Save and exit the editor to continue.	358	Save and exit the editor to continue.
365	</p>	359	</p>
…		…
379	<note>	373	<note>
380	pcmcia-cs is only available for x86, amd64 and ppc platforms.	374	pcmcia-cs is only available for x86, amd64 and ppc platforms.
381	</note>	375	</note>
382		376
383	<p>	377	<p>
384	PCMCIA-users should first install the <c>pcmcia-cs</c> package. The	378	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
		379	includes users who will be working with a 2.6 kernel (even though they won't be
		380	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
385	<c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment:	381	to avoid installing xorg-x11 at this moment:
386	</p>	382	</p>
387		383
388	<pre caption="Installing pcmcia-cs">	384	<pre caption="Installing pcmcia-cs">
389	# <i>USE="-X" emerge pcmcia-cs</i>	385	# <i>USE="-X" emerge pcmcia-cs</i>
390	</pre>	386	</pre>
…		…
438	<pre caption="Opening /etc/rc.conf">	434	<pre caption="Opening /etc/rc.conf">
439	# <i>nano -w /etc/rc.conf</i>	435	# <i>nano -w /etc/rc.conf</i>
440	</pre>	436	</pre>
441		437
442	<p>	438	<p>
		439	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		440	</p>
		441
		442	<p>
443	As you can see, this file is well commented to help you set up the necessary	443	As you can see, this file is well commented to help you set up the necessary
444	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	444	configuration variables. You can configure your system to use unicode and
445	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	445	define your default editor and your display manager (like gdm or kdm).
446	your keyboard.	446	</p>
		447
		448	<p>
		449	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		450	Edit it to configure your keyboard.
		451	</p>
		452
		453	<pre caption="Opening /etc/conf.d/keymaps">
		454	# <i>nano -w /etc/conf.d/keymaps</i>
		455	</pre>
		456
		457	<p>
		458	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
		459	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
447	</p>	460	</p>
448		461
449	<note>	462	<note>
450	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	463	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
451	select an i386 keymap (such as "us") instead of "sunkeymap".	464	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
		465	keymaps on most systems. Users who want to be able to use ADB keymaps on boot
		466	have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
		467	keymap in <path>/etc/conf.d/keymaps</path>.
452	</note>	468	</note>
453		469
454	<p>	470	<p>
455	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	471	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
456	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	472	exit.
457	to set a mac/ppc keymap in <path>rc.conf</path>.
458	</p>
459
460	<p>	473	</p>
		474
		475	<p>
		476	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		477	according to your needs.
		478	</p>
		479
		480	<pre caption="Opening /etc/conf.d/clock">
		481	# <i>nano -w /etc/conf.d/clock</i>
		482	</pre>
		483
		484	<p>
		485	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to
		486	the file. Otherwise you will notice some clock skew. Furthermore, Windows
		487	assumes that your hardware clock uses local time, so if you want to dualboot,
		488	you should set this variable appropriately, otherwise your clock will go crazy.
		489	</p>
		490
		491	<p>
461	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then	492	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
		493	exit.
		494	</p>
		495
		496	<p>
		497	If you are not installing Gentoo on IBM PPC64 hardware, continue with
		498	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
		499	</p>
		500
		501	</body>
		502	</subsection>
		503	<subsection>
		504	<title>Configuring the Console</title>
		505	<body>
		506
		507	<note>
		508	The following section applies to the IBM PPC64 hardware platforms.
		509	</note>
		510
		511	<p>
		512	If you are running Gentoo on IBM PPC64 hardware and using a virtual console
		513	you must uncomment the appropriate line in <path>/etc/inittab</path> for the
		514	virtual console to spawn a login prompt.
		515	</p>
		516
		517	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
		518	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		519	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		520	</pre>
		521
		522	<p>
		523	You should also take this time to verify that the appropriate console is
		524	listed in <path>/etc/securetty</path>.
		525	</p>
		526
		527	<p>
462	continue with <uri link="?part=1&chap=9">Installing Necessary System	528	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
463	Tools</uri>.	529	System Tools</uri>.
464	</p>	530	</p>
465		531
466	</body>	532	</body>
467	</subsection>	533	</subsection>
468	</section>	534	</section>

 Legend:



Removed from v.1.45
 


changed lines


 
Added in v.1.78
 Legend:



Removed from v.1.45
 


changed lines


 
Added in v.1.78
-Removed from v.1.45
+Added in v.1.78

	ViewVC Help
Powered by ViewVC 1.1.13