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

 Legend:



Removed from v.1.67
 


changed lines


 
Added in v.1.95
 Legend:



Removed from v.1.67
 


changed lines


 
Added in v.1.95
-Removed from v.1.67
+Added in v.1.95

	ViewVC Help
Powered by ViewVC 1.1.20