/[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.20		Revision 1.84
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.20 2004/01/19 18:48:52 swift Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.84 2006/09/12 20:07:02 nightmorph Exp $ -->
8		8
9	<sections>	9	<sections>
		10
		11	<version>7.3</version>
		12	<date>2006-09-12</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, 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, Domainname, etc</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
		239	<comment>(Set the HOSTNAME variable to your host name)</comment>
		240	HOSTNAME="<i>tux</i>"
		241	</pre>
		242
183	<p>	243	<p>
184	Second we set the domainname:	244	Second we set the domainname in <path>/etc/conf.d/net</path>:
185	</p>	245	</p>
186		246
187	<pre caption="Setting the domainname">	247	<pre caption="Setting the domainname">
188	# <i>echo homenetwork > /etc/dnsdomainname</i>	248	# <i>nano -w /etc/conf.d/net</i>
		249
		250	<comment>(Set the dns_domain variable to your domain name)</comment>
		251	dns_domain_lo="<i>homenetwork</i>"
189	</pre>	252	</pre>
190		253
191	<p>	254	<p>
192	If you have a NIS domain (if you don't know what that is, then you don't have	255	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:	256	one), you need to define that one too:
194	</p>	257	</p>
195		258
196	<pre caption="Setting the NIS domainname">	259	<pre caption="Setting the NIS domainname">
197	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	260	# <i>nano -w /etc/conf.d/net</i>
198	</pre>
199		261
200	<p>	262	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
201	Now add the <c>domainname</c> script to the default runlevel:	263	nis_domain_lo="<i>my-nisdomain</i>"
202	</p>
203
204	<pre caption="Adding domainname to the default runlevel">
205	# <i>rc-update add domainname default</i>
206	</pre>	264	</pre>
207		265
208	</body>	266	</body>
209	</subsection>	267	</subsection>
210	<subsection>	268	<subsection>
211	<title>Configuring your Network</title>	269	<title>Configuring your Network</title>
212	<body>	270	<body>
213		271
214	<p>	272	<p>
215	Before you get that "Hey, we've had that already"-feeling, you should remember	273	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	274	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	275	just for the installation. Right now you are going to configure networking for
218	your Gentoo system permanently.	276	your Gentoo system permanently.
219	</p>	277	</p>
220		278
		279	<note>
		280	More detailed information about networking, including advanced topics like
		281	bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri
		282	link="?part=4">Gentoo Network Configuration</uri> section.
		283	</note>
		284
221	<p>	285	<p>
222	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	286	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	287	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 :)	288	networking manually. But don't fear, we'll explain everything. A fully
225	</p>	289	commented example that covers many different configurations is available in
226		290	<path>/etc/conf.d/net.example</path>.
227	<p>	291	</p>
		292
		293	<p>
		294	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		295	client. This is described later in <uri
		296	link="?part=1&chap=9#networking-tools">Installing Necessary System
		297	Tools</uri>. Do not forget to install a DHCP client.
		298	</p>
		299
		300	<p>
		301	If you need to configure your network connection either because you need
		302	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>	303	<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in
229	is used in this example):	304	this example):
230	</p>	305	</p>
231		306
232	<pre caption="Opening /etc/conf.d/net for editing">	307	<pre caption="Opening /etc/conf.d/net for editing">
233	# <i>nano -w /etc/conf.d/net</i>	308	# <i>nano -w /etc/conf.d/net</i>
234	</pre>	309	</pre>
235		310
236	<p>	311	<p>
237	The first variable you'll find is <c>iface_eth0</c>. It uses the following	312	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>	313	</p>
246	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	314
247	to <c>dhcp</c>. However, if you need to setup your network manually and you're	315	<pre caption="Default /etc/conf.d/net">
248	not familiar with all the above terms, please read the section on <uri	316	# This blank configuration will automatically use DHCP for any net.*
249	link="?part=1&chap=3#doc_chap4_sect3">Understanding Network	317	# scripts in /etc/init.d. To create a more complete configuration,
250	Terminology</uri> if you haven't done so already.	318	# please review /etc/conf.d/net.example and save your configuration
		319	# in /etc/conf.d/net (this file :]!).
		320	</pre>
		321
251	</p>	322	<p>
252		323	To enter your own IP address, netmask and gateway, you need
		324	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
253	<p>	325	</p>
254	So let us give two examples; the first one uses DHCP, the second one a static IP	326
255	(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway	327	<pre caption="Manually setting IP information for eth0">
256	192.168.0.1:	328	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
		329	routes_eth0=( "default gw 192.168.0.1" )
		330	</pre>
		331
257	</p>	332	<p>
258		333	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
259	<pre caption="Examples for /etc/conf.d/net">	334	<c>dhcp_eth0</c>:
260	<comment>(For DHCP:)</comment>
261	iface_eth0="dhcp"
262
263	<comment>(For static IP:)</comment>
264	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
265	gateway="eth0/192.168.0.1"
266	</pre>
267
268	<p>	335	</p>
269	If you have several network interfaces, create extra <c>iface_eth</c> variables,	336
270	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable	337	<pre caption="Automatically obtaining an IP address for eth0">
271	shouldn't be reproduced as you can only set one gateway per computer.	338	config_eth0=( "dhcp" )
		339	dhcp_eth0="nodns nontp nonis"
		340	</pre>
		341
		342	<p>
		343	Please read <path>/etc/conf.d/net.example</path> for a list of all available
		344	options.
		345	</p>
		346
		347	<p>
		348	If you have several network interfaces repeat the above steps for
		349	<c>config_eth1</c>, <c>config_eth2</c>, etc.
272	</p>	350	</p>
273		351
274	<p>	352	<p>
275	Now save the configuration and exit to continue.	353	Now save the configuration and exit to continue.
276	</p>	354	</p>
…		…
280	<subsection>	358	<subsection>
281	<title>Automatically Start Networking at Boot</title>	359	<title>Automatically Start Networking at Boot</title>
282	<body>	360	<body>
283		361
284	<p>	362	<p>
285	To have your network interfaces activated at boot, you need to add those to the	363	To have your network interfaces activated at boot, you need to add them to the
286	default runlevel. If you have PCMCIA interfaces you should skip this action as	364	default runlevel. If you have PCMCIA interfaces you should skip this action as
287	the PCMCIA interfaces are started by the PCMCIA init script.	365	the PCMCIA interfaces are started by the PCMCIA init script.
288	</p>	366	</p>
289		367
290	<pre caption="Adding net.eth0 to the default runlevel">	368	<pre caption="Adding net.eth0 to the default runlevel">
…		…
297	use <c>ln</c> to do this:	375	use <c>ln</c> to do this:
298	</p>	376	</p>
299		377
300	<pre caption="Creating extra initscripts">	378	<pre caption="Creating extra initscripts">
301	# <i>cd /etc/init.d</i>	379	# <i>cd /etc/init.d</i>
302	# <i>ln -s net.eth0 net.eth1</i>	380	# <i>ln -s net.lo net.eth1</i>
303	# <i>rc-update add net.eth1 default</i>	381	# <i>rc-update add net.eth1 default</i>
304	</pre>	382	</pre>
305		383
306	</body>	384	</body>
307	</subsection>	385	</subsection>
…		…
309	<title>Writing Down Network Information</title>	387	<title>Writing Down Network Information</title>
310	<body>	388	<body>
311		389
312	<p>	390	<p>
313	You now need to inform Linux about your network. This is defined in	391	You now need to inform Linux about your network. This is defined in
314	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	392	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
315	for hosts that aren't resolved by your nameserver. For instance, if your	393	hosts that aren't resolved by your nameserver. You need to define your system.
316	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	394	You may also want to define other systems on your network if you don't want to
317	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	395	set up your own internal DNS system.
318	open <path>/etc/hosts</path> and fill in the values:
319	</p>	396	</p>
320		397
321	<pre caption="Opening /etc/hosts">	398	<pre caption="Opening /etc/hosts">
322	# <i>nano -w /etc/hosts</i>	399	# <i>nano -w /etc/hosts</i>
323	</pre>	400	</pre>
324		401
325	<pre caption="Filling in the networking information">	402	<pre caption="Filling in the networking information">
326	127.0.0.1 localhost	403	<comment>(This defines the current system)</comment>
327	192.168.0.5 jenny	404	127.0.0.1 tux.homenetwork tux localhost
328	192.168.0.6 benny
329	192.168.0.7 tux
330	</pre>
331		405
332	<p>	406	<comment>(Define extra systems on your network,
333	If your system is the only system (or the nameservers handle all name	407	they need to have a static IP to be defined this way.)</comment>
334	resolution) a single line is sufficient:	408	192.168.0.5 jenny.homenetwork jenny
335	</p>	409	192.168.0.6 benny.homenetwork benny
336
337	<pre caption="/etc/hosts for lonely or fully integrated PCs">
338	127.0.0.1 localhost tux
339	</pre>	410	</pre>
340		411
341	<p>	412	<p>
342	Save and exit the editor to continue.	413	Save and exit the editor to continue.
343	</p>	414	</p>
344		415
345	<p>	416	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
346	If you don't have PCMCIA, you can now continue with <uri	417	If you don't have PCMCIA, you can now continue with <uri
347	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	418	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
348	following topic on PCMCIA.	419	following topic on PCMCIA.
349	</p>	420	</p>
350		421
351	</body>	422	</body>
352	</subsection>	423	</subsection>
353	<subsection>	424	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
354	<title>Optional: Get PCMCIA Working</title>	425	<title>Optional: Get PCMCIA Working</title>
355	<body>	426	<body>
356		427
357	<p>	428	<p>
358	PCMCIA-users should first install the <c>pcmcia-cs</c> package:	429	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
		430	includes users who will be working with a 2.6 kernel (even though they won't be
		431	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
		432	to avoid installing xorg-x11 at this moment:
359	</p>	433	</p>
360		434
361	<pre caption="Installing pcmcia-cs">	435	<pre caption="Installing pcmcia-cs">
362	# <i>emerge --usepkg pcmcia-cs</i>	436	# <i>USE="-X" emerge pcmcia-cs</i>
363	</pre>	437	</pre>
364		438
365	<p>	439	<p>
366	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>	440	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
367	runlevel:	441	runlevel:
…		…
372	</pre>	446	</pre>
373		447
374	</body>	448	</body>
375	</subsection>	449	</subsection>
376	</section>	450	</section>
		451
		452	<section id="sysinfo">
		453	<title>System Information</title>
377	<section>	454	<subsection>
		455	<title>Root Password</title>
		456	<body>
		457
		458	<p>
		459	First we set the root password by typing:
		460	</p>
		461
		462	<pre caption="Setting the root password">
		463	# <i>passwd</i>
		464	</pre>
		465
		466	<p>
		467	If you want root to be able to log on through the serial console, add
		468	<c>tts/0</c> to <path>/etc/securetty</path>:
		469	</p>
		470
		471	<pre caption="Adding tts/0 to /etc/securetty">
		472	# <i>echo "tts/0" >> /etc/securetty</i>
		473	</pre>
		474
		475	</body>
		476	</subsection>
		477	<subsection>
378	<title>System Information</title>	478	<title>System Information</title>
379	<body>	479	<body>
380		480
381	<p>	481	<p>
382	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.	482	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
…		…
386	<pre caption="Opening /etc/rc.conf">	486	<pre caption="Opening /etc/rc.conf">
387	# <i>nano -w /etc/rc.conf</i>	487	# <i>nano -w /etc/rc.conf</i>
388	</pre>	488	</pre>
389		489
390	<p>	490	<p>
		491	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		492	</p>
		493
		494	<p>
391	As you can see, this file is well commented to help you set up the necessary	495	As you can see, this file is well commented to help you set up the necessary
392	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	496	configuration variables. You can configure your system to use unicode and
393	you select the wrong <c>KEYMAP</c> you will get weird results when typing on	497	define your default editor and your display manager (like gdm or kdm).
394	your keyboard.	498	</p>
		499
395	</p>	500	<p>
		501	Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration.
		502	Edit it to configure your keyboard.
		503	</p>
396		504
397	<note>	505	<pre caption="Opening /etc/conf.d/keymaps">
		506	# <i>nano -w /etc/conf.d/keymaps</i>
		507	</pre>
		508
		509	<p>
		510	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
		511	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
		512	</p>
		513
		514	<note test="func:keyval('arch')='SPARC'">
398	Users of USB-based SPARC systems and SPARC clones might need to select an i386	515	Users of USB-based SPARC systems and SPARC clones might need to select an i386
399	keymap (such as "us") instead of "sunkeymap".	516	keymap (such as "us") instead of "sunkeymap".
400	</note>	517	</note>
401		518
402	<p>	519	<note test="substring(func:keyval('arch'),1,3)='PPC'">
403	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then	520	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
404	continue with <uri link="?part=1&chap=9">Configuring the Bootloader</uri>.	521	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
		522	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
		523	</note>
		524
405	</p>	525	<p>
		526	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
		527	exit.
		528	</p>
406		529
		530	<p>
		531	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		532	according to your needs.
		533	</p>
		534
		535	<pre caption="Opening /etc/conf.d/clock">
		536	# <i>nano -w /etc/conf.d/clock</i>
		537	</pre>
		538
		539	<p>
		540	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
		541	to the file. Otherwise you will notice some clock skew.
		542	</p>
		543
		544	<p>
		545	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
		546	exit.
		547	</p>
		548
		549	<p test="not(func:keyval('arch')='PPC64')">
		550	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		551	Tools</uri>.
		552	</p>
		553
		554	</body>
		555	</subsection>
		556	<subsection test="func:keyval('arch')='PPC64'">
		557	<title>Configuring the Console</title>
407	</body>	558	<body>
		559
		560	<p>
		561	If you are using a virtual console, you must uncomment the appropriate line in
		562	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
		563	</p>
		564
		565	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
		566	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
		567	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
		568	</pre>
		569
		570	<p>
		571	You should also take this time to verify that the appropriate console is
		572	listed in <path>/etc/securetty</path>.
		573	</p>
		574
		575	<p>
		576	You may now continue with <uri link="?part=1&chap=9">Installing Necessary
		577	System Tools</uri>.
		578	</p>
		579
		580	</body>
		581	</subsection>
408	</section>	582	</section>
409	</sections>	583	</sections>

 Legend:



Removed from v.1.20
 


changed lines


 
Added in v.1.84
 Legend:



Removed from v.1.20
 


changed lines


 
Added in v.1.84
-Removed from v.1.20
+Added in v.1.84

	ViewVC Help
Powered by ViewVC 1.1.13