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

 Legend:



Removed from v.1.42
 


changed lines


 
Added in v.1.92
 Legend:



Removed from v.1.42
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.20