/[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.76		Revision 1.96
…		…
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.76 2006/03/28 10:35:59 neysx Exp $ -->	7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.96 2008/02/29 15:54:59 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.18</version>	17	<version>8.3</version>
12	<date>2006-03-28</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 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 test="contains(func:keyval('/boot'), '/dev/hd')">
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 (or
		97	<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
90	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:
91	</p>	105	</p>
92		106
93	<pre caption="An example /boot line for /etc/fstab">	107	<pre caption="An example /boot line for /etc/fstab">
94	/dev/hda1 /boot ext2 defaults 1 2	108	<keyval id="/boot"/> /boot ext2 defaults 1 2
95	</pre>	109	</pre>
96		110
97	<p>	111	<p>
98	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
99	automatically to improve their system's security. Those people should	113	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	114	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.	115	manually mount this partition every time you want to use it.
102	</p>	116	</p>
103		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.
104	<p>	125	</p>
105	Now, to improve performance, most users would want to add the <c>noatime</c>
106	option as mountoption, which results in a faster system since access times
107	aren't registered (you don't need those generally anyway):
108	</p>
109		126
110	<pre caption="An improved /boot line for /etc/fstab">	127	<p test="func:keyval('arch')='SPARC'">
111	/dev/hda1 /boot ext2 defaults,noatime 1 2	128	Add the rules that match your partitioning schema and append rules for
112	</pre>	129	<path>/proc/openprom</path>, for your CD-ROM drive(s), and of course, if
113		130	you have other partitions or drives, for those too.
114	<p>	131	</p>
115	If we continue with this, we would end up with the following three lines (for	132
116	<path>/boot</path>, <path>/</path> and the swap partition):
117	</p>	133	<p>
118		134	Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
119	<pre caption="Three /etc/fstab lines">
120	/dev/hda1 /boot ext2 defaults,noatime 1 2
121	/dev/hda2 none swap sw 0 0
122	/dev/hda3 / ext3 noatime 0 1
123	</pre>
124
125	<p>	135	</p>
126	To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
127	(required) and for your CD-ROM drive (and of course, if you have other
128	partitions or drives, for those too):
129	</p>
130		136
131	<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'">
132	/dev/hda1 /boot ext2 defaults,noatime 1 2	138	<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
133	/dev/hda2 none swap sw 0 0	139	/dev/hda2 none swap sw 0 0
134	/dev/hda3 / ext3 noatime 0 1	140	/dev/hda3 / ext3 noatime 0 1
135		141
136	none /proc proc defaults 0 0	142	/dev/cdrom /mnt/cdrom auto noauto,user 0 0
137	none /dev/shm tmpfs nodev,nosuid,noexec 0 0	143	</pre>
138		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
139	/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
140	</pre>	190	</pre>
141		191
142	<p>	192	<p>
143	<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
144	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
145	<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.
146	</p>	196	</p>
147		197
148	<p>	198	<p>
149	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>
150	<b>SPARC</b>-user, you should add the following line to your	200	mount option, which results in a faster system since access times
151	<path>/etc/fstab</path>	201	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>	202	</p>
158		203
159	<p>	204	<p>
160	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.
161	</p>	206	</p>
162		207
…		…
164	</subsection>	209	</subsection>
165	</section>	210	</section>
166	<section>	211	<section>
167	<title>Networking Information</title>	212	<title>Networking Information</title>
168	<subsection>	213	<subsection>
169	<title>Hostname, Domainname etc.</title>	214	<title>Host name, Domainname, etc</title>
170	<body>	215	<body>
171		216
172	<p>	217	<p>
173	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
174	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
175	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
176	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
177	<c>tux</c> and domain <c>homenetwork</c>.	222	<c>tux</c> and domain <c>homenetwork</c>.
178	</p>	223	</p>
179		224
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">	225	<pre caption="Setting the host name">
185	# <i>nano -w /etc/conf.d/hostname</i>	226	# <i>nano -w /etc/conf.d/hostname</i>
186		227
187	<comment>(Set the HOSTNAME variable to your hostname)</comment>	228	<comment>(Set the HOSTNAME variable to your host name)</comment>
188	HOSTNAME="<i>tux</i>"	229	HOSTNAME="<i>tux</i>"
189	</pre>	230	</pre>
190		231
191	<p>	232	<p>
192	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.
193	</p>	237	</p>
194		238
195	<pre caption="Setting the domainname">	239	<pre caption="Setting the domainname">
196	# <i>nano -w /etc/conf.d/domainname</i>	240	# <i>nano -w /etc/conf.d/net</i>
197		241
198	<comment>(Set the DNSDOMAIN variable to your domain name)</comment>	242	<comment>(Set the dns_domain variable to your domain name)</comment>
199	DNSDOMAIN="<i>homenetwork</i>"	243	dns_domain_lo="<i>homenetwork</i>"
200	</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>
201		251
202	<p>	252	<p>
203	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
204	one), you need to define that one too:	254	one), you need to define that one too:
205	</p>	255	</p>
206		256
207	<pre caption="Setting the NIS domainname">	257	<pre caption="Setting the NIS domainname">
208	# <i>nano -w /etc/conf.d/domainname</i>	258	# <i>nano -w /etc/conf.d/net</i>
209		259
210	<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>	260	<comment>(Set the nis_domain variable to your NIS domain name)</comment>
211	NISDOMAIN="<i>my-nisdomain</i>"	261	nis_domain_lo="<i>my-nisdomain</i>"
212	</pre>	262	</pre>
		263
		264	<note>
		265	For more information on configuring DNS and NIS, please read the examples
		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>
213		269
214	</body>	270	</body>
215	</subsection>	271	</subsection>
216	<subsection>	272	<subsection>
217	<title>Configuring your Network</title>	273	<title>Configuring your Network</title>
…		…
237	commented example that covers many different configurations is available in	293	commented example that covers many different configurations is available in
238	<path>/etc/conf.d/net.example</path>.	294	<path>/etc/conf.d/net.example</path>.
239	</p>	295	</p>
240		296
241	<p>	297	<p>
242	DHCP is used by default and does not require any further configuration.	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.
243	</p>	302	</p>
244		303
245	<p>	304	<p>
246	If you need to configure your network connection either because you need	305	If you need to configure your network connection either because you need
247	specific DHCP options or because you do not use DHCP at all, open	306	specific DHCP options or because you do not use DHCP at all, open
…		…
269	to set both <c>config_eth0</c> and <c>routes_eth0</c>:	328	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
270	</p>	329	</p>
271		330
272	<pre caption="Manually setting IP information for eth0">	331	<pre caption="Manually setting IP information for eth0">
273	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )	332	config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
274	routes_eth0=( "default gw 192.168.0.1" )	333	routes_eth0=( "default via 192.168.0.1" )
275	</pre>	334	</pre>
276		335
277	<p>	336	<p>
278	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and	337	To use DHCP and add specific DHCP options, define <c>config_eth0</c> and
279	<c>dhcp_eth0</c>:	338	<c>dhcp_eth0</c>:
…		…
304	<title>Automatically Start Networking at Boot</title>	363	<title>Automatically Start Networking at Boot</title>
305	<body>	364	<body>
306		365
307	<p>	366	<p>
308	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
309	default runlevel. If you have PCMCIA interfaces you should skip this action as	368	default runlevel.
310	the PCMCIA interfaces are started by the PCMCIA init script.
311	</p>	369	</p>
312		370
313	<pre caption="Adding net.eth0 to the default runlevel">	371	<pre caption="Adding net.eth0 to the default runlevel">
314	# <i>rc-update add net.eth0 default</i>	372	# <i>rc-update add net.eth0 default</i>
315	</pre>	373	</pre>
…		…
320	use <c>ln</c> to do this:	378	use <c>ln</c> to do this:
321	</p>	379	</p>
322		380
323	<pre caption="Creating extra initscripts">	381	<pre caption="Creating extra initscripts">
324	# <i>cd /etc/init.d</i>	382	# <i>cd /etc/init.d</i>
325	# <i>ln -s net.eth0 net.eth1</i>	383	# <i>ln -s net.lo net.eth1</i>
326	# <i>rc-update add net.eth1 default</i>	384	# <i>rc-update add net.eth1 default</i>
327	</pre>	385	</pre>
328		386
329	</body>	387	</body>
330	</subsection>	388	</subsection>
…		…
332	<title>Writing Down Network Information</title>	390	<title>Writing Down Network Information</title>
333	<body>	391	<body>
334		392
335	<p>	393	<p>
336	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
337	<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
338	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.
339	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
340	<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.
341	open <path>/etc/hosts</path> and fill in the values:
342	</p>	399	</p>
343		400
344	<pre caption="Opening /etc/hosts">	401	<pre caption="Opening /etc/hosts">
345	# <i>nano -w /etc/hosts</i>	402	# <i>nano -w /etc/hosts</i>
346	</pre>	403	</pre>
347		404
348	<pre caption="Filling in the networking information">	405	<pre caption="Filling in the networking information">
349	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>
350	192.168.0.5 jenny.homenetwork jenny	411	192.168.0.5 jenny.homenetwork jenny
351	192.168.0.6 benny.homenetwork benny	412	192.168.0.6 benny.homenetwork benny
352	192.168.0.7 tux.homenetwork tux
353	</pre>
354
355	<p>
356	If your system is the only system (or the nameservers handle all name
357	resolution) a single line is sufficient. For instance, if you want to call your
358	system <c>tux</c>:
359	</p>
360
361	<pre caption="/etc/hosts for lonely or fully integrated PCs">
362	127.0.0.1 localhost tux
363	</pre>	413	</pre>
364		414
365	<p>	415	<p>
366	Save and exit the editor to continue.	416	Save and exit the editor to continue.
367	</p>	417	</p>
368		418
369	<p>	419	<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
370	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
371	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the	421	link="#sysinfo">System Information</uri>. PCMCIA-users should read the
372	following topic on PCMCIA.	422	following topic on PCMCIA.
373	</p>	423	</p>
374		424
375	</body>	425	</body>
376	</subsection>	426	</subsection>
377	<subsection>	427	<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
378	<title>Optional: Get PCMCIA Working</title>	428	<title>Optional: Get PCMCIA Working</title>
379	<body>	429	<body>
380		430
381	<note>
382	pcmcia-cs is only available for x86, amd64 and ppc platforms.
383	</note>
384
385	<p>	431	<p>
386	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also	432	PCMCIA users should first install the <c>pcmciautils</c> package.
387	includes users who will be working with a 2.6 kernel (even though they won't be
388	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
389	to avoid installing xorg-x11 at this moment:
390	</p>	433	</p>
391		434
392	<pre caption="Installing pcmcia-cs">	435	<pre caption="Installing pcmciautils">
393	# <i>USE="-X" emerge pcmcia-cs</i>	436	# <i>emerge pcmciautils</i>
394	</pre>
395
396	<p>
397	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
398	runlevel:
399	</p>
400
401	<pre caption="Adding pcmcia to the default runlevel">
402	# <i>rc-update add pcmcia default</i>
403	</pre>	437	</pre>
404		438
405	</body>	439	</body>
406	</subsection>	440	</subsection>
407	</section>	441	</section>
408	<section>	442
		443	<section id="sysinfo">
409	<title>System Information</title>	444	<title>System Information</title>
410	<subsection>	445	<subsection>
411	<title>Root Password</title>	446	<title>Root Password</title>
412	<body>	447	<body>
413		448
…		…
415	First we set the root password by typing:	450	First we set the root password by typing:
416	</p>	451	</p>
417		452
418	<pre caption="Setting the root password">	453	<pre caption="Setting the root password">
419	# <i>passwd</i>	454	# <i>passwd</i>
420	</pre>
421
422	<p>
423	If you want root to be able to log on through the serial console, add
424	<c>tts/0</c> to <path>/etc/securetty</path>:
425	</p>
426
427	<pre caption="Adding tts/0 to /etc/securetty">
428	# <i>echo "tts/0" >> /etc/securetty</i>
429	</pre>	455	</pre>
430		456
431	</body>	457	</body>
432	</subsection>	458	</subsection>
433	<subsection>	459	<subsection>
…		…
465	<p>	491	<p>
466	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
467	<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.
468	</p>	494	</p>
469		495
470	<note>	496	<note test="substring(func:keyval('arch'),1,3)='PPC'">
471	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
472	select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86
473	keymaps on most systems. Users who want to be able to use ADB keymaps on boot	497	PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
474	have to enable ADB keycode sendings in their kernel and have to set a mac/ppc	498	keymaps on boot have to enable ADB keycode sendings in their kernel and have to
475	keymap in <path>/etc/conf.d/keymaps</path>.	499	set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
476	</note>	500	</note>
477		501
478	<p>	502	<p>
479	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
480	exit.	504	exit.
…		…
488	<pre caption="Opening /etc/conf.d/clock">	512	<pre caption="Opening /etc/conf.d/clock">
489	# <i>nano -w /etc/conf.d/clock</i>	513	# <i>nano -w /etc/conf.d/clock</i>
490	</pre>	514	</pre>
491		515
492	<p>	516	<p>
493	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>
494	the file. Otherwise you will notice some clock skew. Furthermore, Windows	518	to the file. Otherwise you will notice some clock skew.
495	assumes that your hardware clock uses local time, so if you want to dualboot,	519	</p>
496	you should set this variable appropriately, otherwise your clock will go crazy.	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>.
497	</p>	527	</p>
498		528
499	<p>	529	<p>
500	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
501	exit.	531	exit.
502	</p>	532	</p>
503		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>.
504	<p>	537	</p>
505	If you are not installing Gentoo on IBM PPC64 hardware, continue with
506	<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>.
507	</p>
508		538
509	</body>	539	</body>
510	</subsection>
511	<subsection>	540	</subsection>
		541	<subsection test="func:keyval('arch')='PPC64'">
512	<title>Configuring the Console</title>	542	<title>Configuring the Console</title>
513	<body>	543	<body>
514		544
515	<note>
516	The following section applies to the IBM PPC64 hardware platforms.
517	</note>
518
519	<p>	545	<p>
520	If you are running Gentoo on IBM PPC64 hardware and using a virtual console	546	If you are using a virtual console, you must uncomment the appropriate line in
521	you must uncomment the appropriate line in <path>/etc/inittab</path> for the	547	<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
522	virtual console to spawn a login prompt.
523	</p>	548	</p>
524		549
525	<pre caption="Enabling hvc or hvsi support in /etc/inittab">	550	<pre caption="Enabling hvc or hvsi support in /etc/inittab">
526	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0	551	hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
527	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0	552	hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

 Legend:



Removed from v.1.76
 


changed lines


 
Added in v.1.96
 Legend:



Removed from v.1.76
 


changed lines


 
Added in v.1.96
-Removed from v.1.76
+Added in v.1.96

	ViewVC Help
Powered by ViewVC 1.1.13