/[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.75		Revision 1.103
…		…
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/2.5 -->	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.75 2006/02/27 00:55:34 fox2mike Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.103 2011/08/02 17:43:17 jkt 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.17</version>	17	<version>10</version>
12	<date>2006-02-27</date>	18	<date>2011-08-02</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 Apple <b>PPC</b> machines), don't copy it	91	<path>/boot</path>, don't copy it.
84	verbatim.
85	</p>
86
87	<p>	92	</p>
		93
		94	<p>
88	In our default x86 partitioning example <path>/boot</path> is the	95	In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
89	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.	96	usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
90	It needs to be checked during boot, so we would write down:	97	filesystem. It needs to be checked during boot, so we would write down:
91	</p>	98	</p>
92		99
93	<pre caption="An example /boot line for /etc/fstab">	100	<pre caption="An example /boot line for /etc/fstab">
94	/dev/hda1 /boot ext2 defaults 1 2	101	<keyval id="/boot"/> /boot ext2 defaults 1 2
95	</pre>	102	</pre>
96		103
97	<p>	104	<p>
98	Some users don't want their <path>/boot</path> partition to be mounted	105	Some users don't want their <path>/boot</path> partition to be mounted
99	automatically to improve their system's security. Those people should	106	automatically to improve their system's security. Those people should
100	substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to	107	substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
101	manually mount this partition every time you want to use it.	108	manually mount this partition every time you want to use it.
102	</p>	109	</p>
103		110
104	<p>	111	</body>
105	Now, to improve performance, most users would want to add the <c>noatime</c>	112	<body>
106	option as mountoption, which results in a faster system since access times	113
107	aren't registered (you don't need those generally anyway):
108	</p>	114	<p>
109		115	Add the rules that match your partitioning scheme and append rules for
110	<pre caption="An improved /boot line for /etc/fstab">	116	your CD-ROM drive(s), and of course, if you have other partitions or drives,
111	/dev/hda1 /boot ext2 defaults,noatime 1 2	117	for those too.
112	</pre>
113
114	<p>	118	</p>
115	If we continue with this, we would end up with the following three lines (for	119
116	<path>/boot</path>, <path>/</path> and the swap partition):
117	</p>	120	<p>
		121	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
		122	</p>
118		123
119	<pre caption="Three /etc/fstab lines">	124	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
120	/dev/hda1 /boot ext2 defaults,noatime 1 2	125	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
121	/dev/hda2 none swap sw 0 0	126	/dev/sda3 none swap sw 0 0
122	/dev/hda3 / ext3 noatime 0 1	127	/dev/sda4 / ext3 noatime 0 1
123	</pre>
124		128
125	<p>	129	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
126	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>	130
127	(required) and for your CD-ROM drive (and of course, if you have other	131	proc /proc proc defaults 0 0
128	partitions or drives, for those too):	132	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
129	</p>	133	</pre>
130		134
131	<pre caption="A full /etc/fstab example">	135	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'">
132	/dev/hda1 /boot ext2 defaults,noatime 1 2	136	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
133	/dev/hda2 none swap sw 0 0	137	/dev/sda2 none swap sw 0 0
134	/dev/hda3 / ext3 noatime 0 1	138	/dev/sda3 / ext3 noatime 0 1
135		139
		140	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		141
136	none /proc proc defaults 0 0	142	proc /proc proc defaults 0 0
137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0	143	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		144	</pre>
138		145
		146	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
		147	/dev/sda1 / ext3 noatime 0 1
		148	/dev/sda2 none swap sw 0 0
		149	/dev/sda4 /usr ext3 noatime 0 2
		150	/dev/sda5 /var ext3 noatime 0 2
		151	/dev/sda6 /home ext3 noatime 0 2
		152
		153	<comment># You must add the rules for openprom</comment>
		154	openprom /proc/openprom openpromfs defaults 0 0
		155
139	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	156	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		157
		158	proc /proc proc defaults 0 0
		159	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
		160	</pre>
		161
		162	<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC' or
		163	func:keyval('arch')='PPC64'">
		164	/dev/sda4 / ext3 noatime 0 1
		165	/dev/sda3 none swap sw 0 0
		166
		167	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
		168
		169	proc /proc proc defaults 0 0
		170	shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
140	</pre>	171	</pre>
141		172
142	<p>	173	<p>
143	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for	174	<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
144	removable media as they can be created with one of many filesystems) and	175	removable media as they can be created with one of many filesystems) and
145	<c>user</c> makes it possible for non-root users to mount the CD.	176	<c>user</c> makes it possible for non-root users to mount the CD.
146	</p>	177	</p>
147		178
148	<p>	179	<p>
149	Now use the above example to create your <path>/etc/fstab</path>. If you are a	180	To improve performance, most users would want to add the <c>noatime</c>
150	<b>SPARC</b>-user, you should add the following line to your	181	mount option, which results in a faster system since access times
151	<path>/etc/fstab</path>	182	aren't registered (you don't need those generally anyway).
152	too:
153	</p>
154
155	<pre caption="Adding openprom filesystem to /etc/fstab">
156	none /proc/openprom openpromfs defaults 0 0
157	</pre>	183	</p>
158		184
159	<p>	185	<p>
160	Double-check your <path>/etc/fstab</path>, save and quit to continue.	186	Double-check your <path>/etc/fstab</path>, save and quit to continue.
161	</p>	187	</p>
162		188
…		…
164	</subsection>	190	</subsection>
165	</section>	191	</section>
166	<section>	192	<section>
167	<title>Networking Information</title>	193	<title>Networking Information</title>
168	<subsection>	194	<subsection>
169	<title>Hostname, Domainname etc.</title>	195	<title>Host name, Domainname, etc</title>
170	<body>	196	<body>
171		197
172	<p>	198	<p>
173	One of the choices the user has to make is name his/her PC. This seems to be	199	One of the choices the user has to make is name his/her PC. This seems to be
174	quite easy, but <e>lots</e> of users are having difficulties finding the	200	quite easy, but <e>lots</e> of users are having difficulties finding the
175	appropriate name for their Linux-pc. To speed things up, know that any name you	201	appropriate name for their Linux-pc. To speed things up, know that any name you
176	choose can be changed afterwards. For all we care, you can just call your system	202	choose can be changed afterwards. For all we care, you can just call your system
177	<c>tux</c> and domain <c>homenetwork</c>.	203	<c>tux</c> and domain <c>homenetwork</c>.
178	</p>	204	</p>
179		205
180	<p>
181	We use these values in the next examples. First we set the hostname:
182	</p>
183
184	<pre caption="Setting the hostname">	206	<pre caption="Setting the host name">
185	# <i>nano -w /etc/conf.d/hostname</i>	207	# <i>nano -w /etc/conf.d/hostname</i>
186		208
187	<comment>(Set the HOSTNAME variable to your hostname)</comment>	209	<comment>(Set the HOSTNAME variable to your host name)</comment>
188	HOSTNAME="<i>tux</i>"	210	HOSTNAME="<i>tux</i>"
189	</pre>	211	</pre>
190		212
191	<p>	213	<p>
192	Second we set the domainname:	214	Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>.
		215	You only need a domain if your ISP or network administrator says so, or if you
		216	have a DNS server but not a DHCP server. You don't need to worry about DNS or
		217	domainnames if your networking is setup for DHCP.
193	</p>	218	</p>
194		219
195	<pre caption="Setting the domainname">	220	<pre caption="Setting the domainname">
196	# <i>nano -w /etc/conf.d/domainname</i>	221	# <i>nano -w /etc/conf.d/net</i>
197		222
198	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>	223	<comment>(Set the dns_domain variable to your domain name)</comment>
199	DNSDOMAIN="<i>homenetwork</i>"	224	dns_domain_lo="<i>homenetwork</i>"
200	</pre>	225	</pre>
		226
		227	<note>
		228	If you choose not to set a domainname, you can get rid of the "This is
		229	hostname.(none)" messages at your login screen by editing
		230	<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file.
		231	</note>
201		232
202	<p>	233	<p>
203	If you have a NIS domain (if you don't know what that is, then you don't have	234	If you have a NIS domain (if you don't know what that is, then you don't have
204	one), you need to define that one too:	235	one), you need to define that one too:
205	</p>	236	</p>
206		237
207	<pre caption="Setting the NIS domainname">	238	<pre caption="Setting the NIS domainname">
208	# <i>nano -w /etc/conf.d/domainname</i>	239	# <i>nano -w /etc/conf.d/net</i>
209		240
210	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>	241	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
211	NISDOMAIN="<i>my-nisdomain</i>"	242	nis_domain_lo="<i>my-nisdomain</i>"
212	</pre>
213
214	<p>
215	Now add the <c>domainname</c> script to the default runlevel:
216	</p>	243	</pre>
217		244
218	<pre caption="Adding domainname to the default runlevel">	245	<note>
219	# <i>rc-update add domainname default</i>	246	For more information on configuring DNS and NIS, please read the examples
220	</pre>	247	provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge
		248	<c>openresolv</c> to help manage your DNS/NIS setup.
		249	</note>
221		250
222	</body>	251	</body>
223	</subsection>	252	</subsection>
224	<subsection>	253	<subsection>
225	<title>Configuring your Network</title>	254	<title>Configuring your Network</title>
…		…
245	commented example that covers many different configurations is available in	274	commented example that covers many different configurations is available in
246	<path>/etc/conf.d/net.example</path>.	275	<path>/etc/conf.d/net.example</path>.
247	</p>	276	</p>
248		277
249	<p>	278	<p>
250	DHCP is used by default and does not require any further configuration.	279	DHCP is used by default. For DHCP to work, you will need to install a DHCP
		280	client. This is described later in <uri
		281	link="?part=1&chap=9#networking-tools">Installing Necessary System
		282	Tools</uri>. Do not forget to install a DHCP client.
251	</p>	283	</p>
252		284
253	<p>	285	<p>
254	If you need to configure your network connection either because you need	286	If you need to configure your network connection either because you need
255	specific DHCP options or because you do not use DHCP at all, open	287	specific DHCP options or because you do not use DHCP at all, open
…		…
277	to set both <c>config_eth0</c> and <c>routes_eth0</c>:	309	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
278	</p>	310	</p>
279		311
280	<pre caption="Manually setting IP information for eth0">	312	<pre caption="Manually setting IP information for eth0">
281	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )	313	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
282	routes_eth0=( "default gw 192.168.0.1" )	314	routes_eth0=( "default via 192.168.0.1" )
283	</pre>	315	</pre>
284		316
285	<p>	317	<p>
286	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and	318	To use DHCP, define <c>config_eth0</c>:
287	<c>dhcp_eth0</c>:
288	</p>	319	</p>
289		320
290	<pre caption="Automatically obtaining an IP address for eth0">	321	<pre caption="Automatically obtaining an IP address for eth0">
291	config_eth0=( "dhcp" )	322	config_eth0=( "dhcp" )
292	dhcp_eth0="nodns nontp nonis"
293	</pre>	323	</pre>
294		324
295	<p>	325	<p>
296	Please read <path>/etc/conf.d/net.example</path> for a list of all available	326	Please read <path>/etc/conf.d/net.example</path> for a list of all available
297	options.	327	options. Be sure to also read your DHCP client manpage if you need to set
		328	specific DHCP options.
298	</p>	329	</p>
299		330
300	<p>	331	<p>
301	If you have several network interfaces repeat the above steps for	332	If you have several network interfaces repeat the above steps for
302	<c>config_eth1</c>, <c>config_eth2</c>, etc.	333	<c>config_eth1</c>, <c>config_eth2</c>, etc.
…		…
312	<title>Automatically Start Networking at Boot</title>	343	<title>Automatically Start Networking at Boot</title>
313	<body>	344	<body>
314		345
315	<p>	346	<p>
316	To have your network interfaces activated at boot, you need to add them to the	347	To have your network interfaces activated at boot, you need to add them to the
317	default runlevel. If you have PCMCIA interfaces you should skip this action as	348	default runlevel.
318	the PCMCIA interfaces are started by the PCMCIA init script.
319	</p>	349	</p>
320		350
321	<pre caption="Adding net.eth0 to the default runlevel">	351	<pre caption="Adding net.eth0 to the default runlevel">
		352	# <i>cd /etc/init.d</i>
		353	# <i>ln -s net.lo net.eth0</i>
322	# <i>rc-update add net.eth0 default</i>	354	# <i>rc-update add net.eth0 default</i>
323	</pre>	355	</pre>
324		356
325	<p>	357	<p>
326	If you have several network interfaces, you need to create the appropriate	358	If you have several network interfaces, you need to create the appropriate
327	<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can	359	<path>net.eth1</path>, <path>net.eth2</path> etc. just like you did with
328	use <c>ln</c> to do this:	360	<path>net.eth0</path>.
329	</p>
330
331	<pre caption="Creating extra initscripts">
332	# <i>cd /etc/init.d</i>
333	# <i>ln -s net.eth0 net.eth1</i>
334	# <i>rc-update add net.eth1 default</i>
335	</pre>	361	</p>
336		362
337	</body>	363	</body>
338	</subsection>	364	</subsection>
339	<subsection>	365	<subsection>
340	<title>Writing Down Network Information</title>	366	<title>Writing Down Network Information</title>
341	<body>	367	<body>
342		368
343	<p>	369	<p>
344	You now need to inform Linux about your network. This is defined in	370	You now need to inform Linux about your network. This is defined in
345	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	371	<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
346	for hosts that aren't resolved by your nameserver. For instance, if your	372	hosts that aren't resolved by your nameserver. You need to define your system.
347	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	373	You may also want to define other systems on your network if you don't want to
348	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would	374	set up your own internal DNS system.
349	open <path>/etc/hosts</path> and fill in the values:
350	</p>	375	</p>
351		376
352	<pre caption="Opening /etc/hosts">	377	<pre caption="Opening /etc/hosts">
353	# <i>nano -w /etc/hosts</i>	378	# <i>nano -w /etc/hosts</i>
354	</pre>	379	</pre>
355		380
356	<pre caption="Filling in the networking information">	381	<pre caption="Filling in the networking information">
357	127.0.0.1 localhost	382	<comment>(This defines the current system)</comment>
		383	127.0.0.1 tux.homenetwork tux localhost
		384
		385	<comment>(Define extra systems on your network,
		386	they need to have a static IP to be defined this way.)</comment>
358	192.168.0.5 jenny.homenetwork jenny	387	192.168.0.5 jenny.homenetwork jenny
359	192.168.0.6 benny.homenetwork benny	388	192.168.0.6 benny.homenetwork benny
360	192.168.0.7 tux.homenetwork tux
361	</pre>
362
363	<p>
364	If your system is the only system (or the nameservers handle all name
365	resolution) a single line is sufficient. For instance, if you want to call your
366	system <c>tux</c>:
367	</p>
368
369	<pre caption="/etc/hosts for lonely or fully integrated PCs">
370	127.0.0.1 localhost tux
371	</pre>	389	</pre>
372		390
373	<p>	391	<p>
374	Save and exit the editor to continue.	392	Save and exit the editor to continue.
375	</p>	393	</p>
376		394
377	<p>	395	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
378	If you don't have PCMCIA, you can now continue with <uri	396	If you don't have PCMCIA, you can now continue with <uri
379	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	397	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
380	following topic on PCMCIA.	398	following topic on PCMCIA.
381	</p>	399	</p>
382		400
383	</body>	401	</body>
384	</subsection>	402	</subsection>
385	<subsection>	403	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
386	<title>Optional: Get PCMCIA Working</title>	404	<title>Optional: Get PCMCIA Working</title>
387	<body>	405	<body>
388		406
389	<note>
390	pcmcia-cs is only available for x86, amd64 and ppc platforms.
391	</note>
392
393	<p>	407	<p>
394	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	408	PCMCIA users should first install the <c>pcmciautils</c> package.
395	includes users who will be working with a 2.6 kernel (even though they won't be
396	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
397	to avoid installing xorg-x11 at this moment:
398	</p>	409	</p>
399		410
400	<pre caption="Installing pcmcia-cs">	411	<pre caption="Installing pcmciautils">
401	# <i>USE="-X" emerge pcmcia-cs</i>	412	# <i>emerge pcmciautils</i>
402	</pre>
403
404	<p>
405	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
406	runlevel:
407	</p>
408
409	<pre caption="Adding pcmcia to the default runlevel">
410	# <i>rc-update add pcmcia default</i>
411	</pre>	413	</pre>
412		414
413	</body>	415	</body>
414	</subsection>	416	</subsection>
415	</section>	417	</section>
416	<section>	418
		419	<section id="sysinfo">
417	<title>System Information</title>	420	<title>System Information</title>
418	<subsection>	421	<subsection>
419	<title>Root Password</title>	422	<title>Root Password</title>
420	<body>	423	<body>
421		424
…		…
423	First we set the root password by typing:	426	First we set the root password by typing:
424	</p>	427	</p>
425		428
426	<pre caption="Setting the root password">	429	<pre caption="Setting the root password">
427	# <i>passwd</i>	430	# <i>passwd</i>
428	</pre>
429
430	<p>
431	If you want root to be able to log on through the serial console, add
432	<c>tts/0</c> to <path>/etc/securetty</path>:
433	</p>
434
435	<pre caption="Adding tts/0 to /etc/securetty">
436	# <i>echo "tts/0" >> /etc/securetty</i>
437	</pre>	431	</pre>
438		432
439	</body>	433	</body>
440	</subsection>	434	</subsection>
441	<subsection>	435	<subsection>
…		…
473	<p>	467	<p>
474	Take special care with the <c>KEYMAP</c> variable. If you select the wrong	468	Take special care with the <c>KEYMAP</c> variable. If you select the wrong
475	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.	469	<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
476	</p>	470	</p>
477		471
478	<note>	472	<note test="substring(func:keyval('arch'),1,3)='PPC'">
479	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to	473	PPC uses x86 keymaps on most systems.
480	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
481	keymaps on most systems. Users who want to be able to use ADB keymaps on boot
482	have to enable ADB keycode sendings in their kernel and have to set a mac/ppc
483	keymap in <path>/etc/conf.d/keymaps</path>.
484	</note>	474	</note>
485		475
486	<p>	476	<p>
487	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and	477	When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
488	exit.	478	exit.
…		…
496	<pre caption="Opening /etc/conf.d/clock">	486	<pre caption="Opening /etc/conf.d/clock">
497	# <i>nano -w /etc/conf.d/clock</i>	487	# <i>nano -w /etc/conf.d/clock</i>
498	</pre>	488	</pre>
499		489
500	<p>	490	<p>
501	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to	491	If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c>
502	the file. Otherwise you will notice some clock skew. Furthermore, Windows	492	to the file. Otherwise you will notice some clock skew.
503	assumes that your hardware clock uses local time, so if you want to dualboot,	493	</p>
504	you should set this variable appropriately, otherwise your clock will go crazy.	494
		495	<p>
		496	You should define the timezone that you previously copied to
		497	<path>/etc/localtime</path> so that further upgrades of the
		498	<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path>
		499	automatically. For instance, if you used the GMT timezone, you would add
		500	<c>TIMEZONE="GMT"</c>
505	</p>	501	</p>
506		502
507	<p>	503	<p>
508	When you're finished configuring <path>/etc/conf.d/clock</path>, save and	504	When you're finished configuring <path>/etc/conf.d/clock</path>, save and
509	exit.	505	exit.
510	</p>	506	</p>
511		507
		508	<p test="not(func:keyval('arch')='PPC64')">
		509	Please continue with <uri link="?part=1&chap=9">Installing Necessary System
		510	Tools</uri>.
512	<p>	511	</p>
513	If you are not installing Gentoo on IBM PPC64 hardware, continue with
514	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
515	</p>
516		512
517	</body>	513	</body>
518	</subsection>
519	<subsection>	514	</subsection>
		515	<subsection test="func:keyval('arch')='PPC64'">
520	<title>Configuring the Console</title>	516	<title>Configuring the Console</title>
521	<body>	517	<body>
522		518
523	<note>
524	The following section applies to the IBM PPC64 hardware platforms.
525	</note>
526
527	<p>	519	<p>
528	If you are running Gentoo on IBM PPC64 hardware and using a virtual console	520	If you are using a virtual console, you must uncomment the appropriate line in
529	you must uncomment the appropriate line in <path>/etc/inittab</path> for the	521	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
530	virtual console to spawn a login prompt.
531	</p>	522	</p>
532		523
533	<pre caption="Enabling hvc or hvsi support in /etc/inittab">	524	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
534	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0	525	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
535	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0	526	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

 Legend:



Removed from v.1.75
 


changed lines


 
Added in v.1.103
 Legend:



Removed from v.1.75
 


changed lines


 
Added in v.1.103
-Removed from v.1.75
+Added in v.1.103

	ViewVC Help
Powered by ViewVC 1.1.20