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

 Legend:



Removed from v.1.30
 


changed lines


 
Added in v.1.81
 Legend:



Removed from v.1.30
 


changed lines


 
Added in v.1.81
-Removed from v.1.30
+Added in v.1.81

	ViewVC Help
Powered by ViewVC 1.1.13