/[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.42		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.42 2004/08/06 12:16:52 neysx 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 <b>PPC</b>), 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.	90	usually the <path><keyval id="/boot"/></path> partition (or
		91	<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
84	It needs to be checked during boot, so we 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:
85	</p>	99	</p>
86		100
87	<pre caption="An example /boot line for /etc/fstab">	101	<pre caption="An example /boot line for /etc/fstab">
88	/dev/hda1 /boot ext2 defaults 1 2	102	<keyval id="/boot"/> /boot ext2 defaults 1 2
89	</pre>	103	</pre>
90		104
91	<p>	105	<p>
92	Some users don't want their <path>/boot</path> partition to be mounted	106	Some users don't want their <path>/boot</path> partition to be mounted
93	automatically. Those people should substitute <c>defaults</c> with	107	automatically to improve their system's security. Those people should
94	<c>noauto</c>. This does mean that you need to manually mount this partition	108	substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
95	every time you want to use it.	109	manually mount this partition every time you want to use it.
96	</p>
97
98	<p>	110	</p>
99	Now, to improve performance, most users would want to add the <c>noatime</c>
100	option as mountoption, which results in a faster system since access times
101	aren't registered (you don't need those generally anyway):
102	</p>
103		111
104	<pre caption="An improved /boot line for /etc/fstab">	112	</body>
105	/dev/hda1 /boot ext2 noauto,noatime 1 2	113	<body>
106	</pre>
107		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.
108	<p>	119	</p>
109	If we continue with this, we would end up with the following three lines (for	120
110	<path>/boot</path>, <path>/</path> and the swap partition):	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
111	</p>	127	<p>
		128	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
		129	</p>
112		130
113	<pre caption="Three /etc/fstab lines">	131	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
114	/dev/hda1 /boot ext2 noauto,noatime 1 2	132	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
115	/dev/hda2 none swap sw 0 0	133	/dev/hda2 none swap sw 0 0
116	/dev/hda3 / ext3 noatime 0 1	134	/dev/hda3 / ext3 noatime 0 1
117	</pre>
118		135
119	<p>
120	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
121	(required) and for your CD-ROM drive (and of course, if you have other
122	partitions or drives, for those too):
123	</p>
124
125	<pre caption="A full /etc/fstab example">
126	/dev/hda1 /boot ext2 noauto,noatime 1 2
127	/dev/hda2 none swap sw 0 0
128	/dev/hda3 / ext3 noatime 0 1
129
130	none /proc proc defaults 0 0	136	none /proc proc defaults 0 0
131	none /dev/shm tmpfs defaults 0 0	137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
132		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
133	/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
134	</pre>	201	</pre>
135		202
136	<p>	203	<p>
137	<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
138	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
139	<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.
140	</p>	207	</p>
141		208
142	<p>	209	<p>
143	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>
144	<b>SPARC</b>-user, you should add the following line to your	211	mount option, which results in a faster system since access times
145	<path>/etc/fstab</path>	212	aren't registered (you don't need those generally anyway).
146	too:
147	</p>
148
149	<pre caption="Adding openprom filesystem to /etc/fstab">
150	none /proc/openprom openpromfs defaults 0 0
151	</pre>
152
153	<p>	213	</p>
154	If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
155	</p>
156
157	<pre caption="Adding usbfs filesystem to /etc/fstab">
158	none /proc/bus/usb usbfs defaults 0 0
159	</pre>
160		214
161	<p>	215	<p>
162	Double-check your <path>/etc/fstab</path>, save and quit to continue.	216	Double-check your <path>/etc/fstab</path>, save and quit to continue.
163	</p>	217	</p>
164		218
…		…
166	</subsection>	220	</subsection>
167	</section>	221	</section>
168	<section>	222	<section>
169	<title>Networking Information</title>	223	<title>Networking Information</title>
170	<subsection>	224	<subsection>
171	<title>Hostname, Domainname etc.</title>	225	<title>Host name</title>
172	<body>	226	<body>
173		227
174	<p>	228	<p>
175	One of the choices the user has to make is name his/her PC. This seems to be	229	One of the choices the user has to make is name his/her PC. This seems to be
176	quite easy, but <e>lots</e> of users are having difficulties finding the	230	quite easy, but <e>lots</e> of users are having difficulties finding the
177	appropriate name for their Linux-pc. To speed things up, know that any name you	231	appropriate name for their Linux-pc. To speed things up, know that any name you
178	choose can 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
179	<c>tux</c> and domain <c>homenetwork</c>.	233	<c>tux</c> and domain <c>homenetwork</c>.
180	</p>	234	</p>
181		235
182	<p>
183	We use these values in the next examples. First we set the hostname:
184	</p>
185
186	<pre caption="Setting the hostname">	236	<pre caption="Setting the host name">
187	# <i>echo tux > /etc/hostname</i>	237	# <i>nano -w /etc/conf.d/hostname</i>
188	</pre>
189		238
190	<p>	239	<comment>(Set the HOSTNAME variable to your host name)</comment>
191	Second we set the domainname:	240	HOSTNAME="<i>tux</i>"
192	</p>
193
194	<pre caption="Setting the domainname">
195	# <i>echo homenetwork > /etc/dnsdomainname</i>
196	</pre>
197
198	<p>
199	If you have a NIS domain (if you don't know what that is, then you don't have
200	one), you need to define that one too:
201	</p>
202
203	<pre caption="Setting the NIS domainname">
204	# <i>echo nis.homenetwork > /etc/nisdomainname</i>
205	</pre>
206
207	<p>
208	Now add the <c>domainname</c> script to the default runlevel:
209	</p>
210
211	<pre caption="Adding domainname to the default runlevel">
212	# <i>rc-update add domainname default</i>
213	</pre>	241	</pre>
214		242
215	</body>	243	</body>
216	</subsection>	244	</subsection>
217	<subsection>	245	<subsection>
218	<title>Configuring your Network</title>	246	<title>Configuring your Network</title>
219	<body>	247	<body>
220		248
221	<p>	249	<p>
222	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
223	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
224	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
225	your Gentoo system permanently.	253	your Gentoo system permanently.
226	</p>	254	</p>
227		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
228	<p>	262	<p>
229	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
230	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
231	networking manually. But don't fear, we'll explain everything :)	265	networking manually. But don't fear, we'll explain everything. A fully
232	</p>	266	commented example that covers many different configurations is available in
233		267	<path>/etc/conf.d/net.example</path>.
234	<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
235	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
236	is used in this example):	278	this example):
237	</p>	279	</p>
238		280
239	<pre caption="Opening /etc/conf.d/net for editing">	281	<pre caption="Opening /etc/conf.d/net for editing">
240	# <i>nano -w /etc/conf.d/net</i>	282	# <i>nano -w /etc/conf.d/net</i>
241	</pre>	283	</pre>
242		284
243	<p>	285	<p>
244	The first variable you'll find is <c>iface_eth0</c>. It uses the following	286	You will see the following file:
245	syntax:
246	</p>
247
248	<pre caption="iface_eth0 syntaxis">
249	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
250	</pre>
251
252	<p>	287	</p>
253	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	288
254	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">
255	If you need to setup your network manually and you're	290	# This blank configuration will automatically use DHCP for any net.*
256	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,
257	link="?part=1&chap=3#network_term">Understanding Network	292	# please review /etc/conf.d/net.example and save your configuration
258	Terminology</uri> if you haven't done so already.	293	# in /etc/conf.d/net (this file :]!).
		294	</pre>
		295
259	</p>	296	<p>
260		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>:
261	<p>	299	</p>
262	So let us give three examples; the first one uses DHCP, the second one a static	300
263	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">
264	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" )
265	rp-pppoe usage:	303	routes_eth0=( "default gw 192.168.0.1" )
		304	</pre>
		305
266	</p>	306	<p>
267		307	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
268	<pre caption="Examples for /etc/conf.d/net">	308	<c>dhcp_eth0</c>:
269	<comment>(For DHCP)</comment>
270	iface_eth0="dhcp"
271	<comment># Some network admins require that you use the</comment>
272	<comment># hostname and domainname provided by the DHCP server.</comment>
273	<comment># In that case, add the following to let dhcpcd use them.</comment>
274	<comment># That will override your own hostname and domainname definitions.</comment>
275	dhcpcd_eth0="-HD"
276	<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
277	<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
278	dhcpcd_eth0="-N"
279
280	<comment>(For static IP)</comment>
281	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
282	gateway="eth0/192.168.0.1"
283
284	<comment>(For rp-pppoe)</comment>
285	iface_eth0="up"
286	</pre>
287
288	<p>	309	</p>
289	If you have several network interfaces, create extra <c>iface_eth</c> variables,	310
290	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">
291	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.
292	</p>	324	</p>
293		325
294	<p>	326	<p>
295	Now save the configuration and exit to continue.	327	Now save the configuration and exit to continue.
296	</p>	328	</p>
…		…
300	<subsection>	332	<subsection>
301	<title>Automatically Start Networking at Boot</title>	333	<title>Automatically Start Networking at Boot</title>
302	<body>	334	<body>
303		335
304	<p>	336	<p>
305	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
306	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
307	the PCMCIA interfaces are started by the PCMCIA init script.	339	the PCMCIA interfaces are started by the PCMCIA init script.
308	</p>	340	</p>
309		341
310	<pre caption="Adding net.eth0 to the default runlevel">	342	<pre caption="Adding net.eth0 to the default runlevel">
…		…
317	use <c>ln</c> to do this:	349	use <c>ln</c> to do this:
318	</p>	350	</p>
319		351
320	<pre caption="Creating extra initscripts">	352	<pre caption="Creating extra initscripts">
321	# <i>cd /etc/init.d</i>	353	# <i>cd /etc/init.d</i>
322	# <i>ln -s net.eth0 net.eth1</i>	354	# <i>ln -s net.lo net.eth1</i>
323	# <i>rc-update add net.eth1 default</i>	355	# <i>rc-update add net.eth1 default</i>
324	</pre>	356	</pre>
325		357
326	</body>	358	</body>
327	</subsection>	359	</subsection>
…		…
329	<title>Writing Down Network Information</title>	361	<title>Writing Down Network Information</title>
330	<body>	362	<body>
331		363
332	<p>	364	<p>
333	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
334	<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
335	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.
336	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
337	<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.
338	open <path>/etc/hosts</path> and fill in the values:
339	</p>	370	</p>
340		371
341	<pre caption="Opening /etc/hosts">	372	<pre caption="Opening /etc/hosts">
342	# <i>nano -w /etc/hosts</i>	373	# <i>nano -w /etc/hosts</i>
343	</pre>	374	</pre>
344		375
345	<pre caption="Filling in the networking information">	376	<pre caption="Filling in the networking information">
346	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>
347	192.168.0.5 jenny.homenetwork jenny	382	192.168.0.5 jenny.homenetwork jenny
348	192.168.0.6 benny.homenetwork benny	383	192.168.0.6 benny.homenetwork benny
349	192.168.0.7 tux.homenetwork tux
350	</pre>
351
352	<p>
353	If your system is the only system (or the nameservers handle all name
354	resolution) a single line is sufficient. For instance, if you want to call your
355	system <c>tux.homenetwork</c>:
356	</p>
357
358	<pre caption="/etc/hosts for lonely or fully integrated PCs">
359	127.0.0.1 tux.homenetwork tux localhost
360	</pre>	384	</pre>
361		385
362	<p>	386	<p>
363	Save and exit the editor to continue.	387	Save and exit the editor to continue.
364	</p>	388	</p>
365		389
366	<p>	390	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
367	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
368	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	392	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
369	following topic on PCMCIA.	393	following topic on PCMCIA.
370	</p>	394	</p>
371		395
372	</body>	396	</body>
373	</subsection>	397	</subsection>
374	<subsection>	398	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
375	<title>Optional: Get PCMCIA Working</title>	399	<title>Optional: Get PCMCIA Working</title>
376	<body>	400	<body>
377		401
378	<note>
379	pcmcia-cs is only available for x86, amd64 and ppc platforms.
380	</note>
381
382	<p>	402	<p>
383	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
		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
384	<c>USE="-X"</c> is necessary to avoid installing xorg-x11 at this moment:	406	to avoid installing xorg-x11 at this moment:
385	</p>	407	</p>
386		408
387	<pre caption="Installing pcmcia-cs">	409	<pre caption="Installing pcmcia-cs">
388	# <i>USE="-X" emerge pcmcia-cs</i>	410	# <i>USE="-X" emerge pcmcia-cs</i>
389	</pre>	411	</pre>
…		…
398	</pre>	420	</pre>
399		421
400	</body>	422	</body>
401	</subsection>	423	</subsection>
402	</section>	424	</section>
403	<section>	425
		426	<section id="sysinfo">
404	<title>System Information</title>	427	<title>System Information</title>
405	<subsection>	428	<subsection>
406	<title>Root Password</title>	429	<title>Root Password</title>
407	<body>	430	<body>
408		431
…		…
437	<pre caption="Opening /etc/rc.conf">	460	<pre caption="Opening /etc/rc.conf">
438	# <i>nano -w /etc/rc.conf</i>	461	# <i>nano -w /etc/rc.conf</i>
439	</pre>	462	</pre>
440		463
441	<p>	464	<p>
		465	When you're finished configuring <path>/etc/rc.conf</path>, save and exit.
		466	</p>
		467
		468	<p>
442	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
443	configuration variables. Take special care with the <c>KEYMAP</c> setting: if	470	configuration variables. You can configure your system to use unicode and
444	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).
445	your keyboard.	472	</p>
		473
446	</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>
447		478
448	<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'">
449	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	489	Users of USB-based SPARC systems and SPARC clones might need to select an i386
450	select an i386 keymap (such as "us") instead of "sunkeymap".	490	keymap (such as "us") instead of "sunkeymap".
451	</note>	491	</note>
452		492
453	<p>	493	<note test="substring(func:keyval('arch'),1,3)='PPC'">
454	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use	494	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
455	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have	495	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
456	to 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
457	</p>	499	<p>
458		500	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
		501	exit.
459	<p>	502	</p>
		503
		504	<p>
		505	Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it
		506	according to your needs.
		507	</p>
		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>
460	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then	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')">
461	continue with <uri link="?part=1&chap=9">Installing Necessary System	526	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
462	Tools</uri>.	527	Tools</uri>.
		528	</p>
		529
		530	</body>
		531	</subsection>
		532	<subsection test="func:keyval('arch')='PPC64'">
		533	<title>Configuring the Console</title>
		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>.
463	</p>	554	</p>
464		555
465	</body>	556	</body>
466	</subsection>	557	</subsection>
467	</section>	558	</section>

 Legend:



Removed from v.1.42
 


changed lines


 
Added in v.1.81
 Legend:



Removed from v.1.42
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.20