/[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.7		Revision 1.58
		1	<?xml version='1.0' encoding='UTF-8'?>
		2	<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
		3
1	<!-- 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 -->
2	<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->	5	<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3		6
		7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.58 2005/04/08 12:03:44 swift Exp $ -->
		8
4	<sections>	9	<sections>
5	<section>
6	<title>Timezone</title>
7	<body>
8		10
9	<p>	11	<version>2.1</version>
10	You now need to select your timezone so that your system knows where it is	12	<date>2005-04-07</date>
11	located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
12	symlink to <path>/etc/localtime</path> using <c>ln</c>:
13	</p>
14		13
15	<pre caption="Setting the timezone information">
16	# <i>ls /usr/share/zoneinfo</i>
17	<comment>(Suppose you want to use GTM:)</comment>
18	# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
19	</pre>
20
21	</body>
22	</section>
23	<section>	14	<section>
24	<title>Filesystem Information</title>	15	<title>Filesystem Information</title>
25	<subsection>	16	<subsection>
26	<title>What is fstab?</title>	17	<title>What is fstab?</title>
27	<body>	18	<body>
28		19
29	<p>	20	<p>
30	Under Linux, all partitions used by the system must be listed in	21	Under Linux, all partitions used by the system must be listed in
31	<path>/etc/fstab</path>. This file contains the mountpoints of those partitions	22	<path>/etc/fstab</path>. This file contains the mountpoints of those partitions
32	(where they are seen in the file system structure), how they should be mounted	23	(where they are seen in the file system structure), how they should be mounted
33	(special options) and when (automatically or not, can users mount those or not,	24	and with what special options (automatically or not, whether users can mount
34	etc.).	25	them or not, etc.)
35	</p>	26	</p>
36		27
37	</body>	28	</body>
38	</subsection>	29	</subsection>
39	<subsection>	30	<subsection>
40	<title>Creating /etc/fstab</title>	31	<title>Creating /etc/fstab</title>
41	<body>	32	<body>
42		33
43	<p>	34	<p>
44	<path>/etc/fstab</path> uses a special syntaxis. Every line consists of six	35	<path>/etc/fstab</path> uses a special syntax. Every line consists of six
45	fields, seperated by whitespace (space(s), tabs or a mixture). Each field has	36	fields, separated by whitespace (space(s), tabs or a mixture). Each field has
46	its own meaning:	37	its own meaning:
47	</p>	38	</p>
48		39
49	<ul>	40	<ul>
50	<li>	41	<li>
…		…
59	The third field shows the <b>filesystem</b> used by the partition	50	The third field shows the <b>filesystem</b> used by the partition
60	</li>	51	</li>
61	<li>	52	<li>
62	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it	53	The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it
63	wants to mount the partition. As every filesystem has its own mountoptions,	54	wants to mount the partition. As every filesystem has its own mountoptions,
64	you are encouraged to read the mount manpage (<c>man mount</c>) for a full	55	you are encouraged to read the mount man page (<c>man mount</c>) for a full
65	listing. Multiple mountoptions are comma-seperated.	56	listing. Multiple mountoptions are comma-separated.
66	</li>	57	</li>
67	<li>	58	<li>
68	The fifth field is used by <c>dump</c> to determine if the partition needs to	59	The fifth field is used by <c>dump</c> to determine if the partition needs to
69	be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).	60	be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
70	</li>	61	</li>
71	<li>	62	<li>
72	The sixth field is used by <c>fsck</c> the order in which filesystems should	63	The sixth field is used by <c>fsck</c> to determine the order in which
73	be <b>check</b>ed if the system wasn't shut down properly. The root filesystem	64	filesystems should be <b>check</b>ed if the system wasn't shut down properly.
74	should have <c>1</c> while the rest should have <c>2</c> (or <c>0</c> in case	65	The root filesystem should have <c>1</c> while the rest should have <c>2</c>
75	a filesystem check isn't necessary).	66	(or <c>0</c> if a filesystem check isn't necessary).
76	</li>	67	</li>
77	</ul>	68	</ul>
78		69
79	<p>	70	<p>
		71	The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab
80	So start <c>nano</c> (or your favorite editor) to create your	72	file</e>, so start <c>nano</c> (or your favorite editor) to create your
81	<path>/etc/fstab</path>:	73	<path>/etc/fstab</path>:
82	</p>	74	</p>
83		75
84	<pre caption="Opening /etc/fstab">	76	<pre caption="Opening /etc/fstab">
85	# <i>nano -w /etc/fstab</i>	77	# <i>nano -w /etc/fstab</i>
86	</pre>	78	</pre>
87		79
88	<p>	80	<p>
89	Lets take a look at how we write down the options for the <path>/boot</path>	81	Let us take a look at how we write down the options for the <path>/boot</path>
90	partition. This is just an example, so if your architecture doesn't require a	82	partition. This is just an example, so if your architecture doesn't require a
91	<path>/boot</path> partition, don't copy it verbatim.	83	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
92	</p>	84	</p>
93		85
94	<p>	86	<p>
95	In our default x86 partitioning example <path>/boot</path> is the	87	In our default x86 partitioning example <path>/boot</path> is the
96	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't	88	<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
97	be mounted automatically (<c>noauto</c>) but does need to be checked. So we	89	It needs to be checked during boot, so we would write down:
98	would write down:
99	</p>	90	</p>
100		91
101	<pre caption="An example /boot line for /etc/fstab">	92	<pre caption="An example /boot line for /etc/fstab">
102	/dev/hda1 /boot ext2 noauto 1 2	93	/dev/hda1 /boot ext2 defaults 1 2
		94	</pre>
		95
		96	<p>
		97	Some users don't want their <path>/boot</path> partition to be mounted
		98	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
		100	manually mount this partition every time you want to use it.
103	</pre>	101	</p>
104		102
105	<p>	103	<p>
106	Now, to improve performance, most users would want to add the <c>noatime</c>	104	Now, to improve performance, most users would want to add the <c>noatime</c>
107	option as mountoption, which results in a faster system since access times	105	option as mountoption, which results in a faster system since access times
108	aren't registered (you don't need those generally anyway):	106	aren't registered (you don't need those generally anyway):
109	</p>	107	</p>
110		108
111	<pre caption="An improved /boot line for /etc/fstab">	109	<pre caption="An improved /boot line for /etc/fstab">
112	/dev/hda1 /boot ext2 noauto,noatime 1 2	110	/dev/hda1 /boot ext2 defaults,noatime 1 2
113	</pre>	111	</pre>
114		112
115	<p>	113	<p>
116	If we continue with this, we would end up with the following three lines (for	114	If we continue with this, we would end up with the following three lines (for
117	<path>/boot</path>, <path>/</path> and the swap partition):	115	<path>/boot</path>, <path>/</path> and the swap partition):
118	</p>	116	</p>
119		117
120	<pre caption="Three /etc/fstab lines">	118	<pre caption="Three /etc/fstab lines">
121	/dev/hda1 /boot ext2 noauto,noatime 1 2	119	/dev/hda1 /boot ext2 defaults,noatime 1 2
122	/dev/hda2 none swap sw 0 0	120	/dev/hda2 none swap sw 0 0
123	/dev/hda3 / ext3 noatime 0 1	121	/dev/hda3 / ext3 noatime 0 1
124	</pre>	122	</pre>
125		123
126	<p>	124	<p>
…		…
128	(required) and for your CD-ROM drive (and of course, if you have other	126	(required) and for your CD-ROM drive (and of course, if you have other
129	partitions or drives, for those too):	127	partitions or drives, for those too):
130	</p>	128	</p>
131		129
132	<pre caption="A full /etc/fstab example">	130	<pre caption="A full /etc/fstab example">
133	/dev/hda1 /boot ext2 noauto,noatime 1 2	131	/dev/hda1 /boot ext2 defaults,noatime 1 2
134	/dev/hda2 none swap sw 0 0	132	/dev/hda2 none swap sw 0 0
135	/dev/hda3 / ext3 noatime 0 1	133	/dev/hda3 / ext3 noatime 0 1
136		134
137	none /proc proc defaults 0 0	135	none /proc proc defaults 0 0
138	none /dev/shm tmpfs defaults 0 0	136	none /dev/shm tmpfs nodev,nosuid,noexec 0 0
139		137
140	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0	138	/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
141	</pre>	139	</pre>
142		140
143	<p>	141	<p>
…		…
146	<c>user</c> makes it possible for non-root users to mount the CD.	144	<c>user</c> makes it possible for non-root users to mount the CD.
147	</p>	145	</p>
148		146
149	<p>	147	<p>
150	Now use the above example to create your <path>/etc/fstab</path>. If you are a	148	Now use the above example to create your <path>/etc/fstab</path>. If you are a
151	SPARC-user, you should add the following line to your <path>/etc/fstab</path>	149	<b>SPARC</b>-user, you should add the following line to your
		150	<path>/etc/fstab</path>
152	too:	151	too:
153	</p>	152	</p>
154		153
155	<pre caption="Adding openprom filesystem to /etc/fstab">	154	<pre caption="Adding openprom filesystem to /etc/fstab">
156	none /proc/openprom openpromfs defaults 0 0	155	none /proc/openprom openpromfs defaults 0 0
157	</pre>	156	</pre>
158		157
159	<p>	158	<p>
160	If you need <c>usbfs</c>, add the following line to <path>/etc/fstab</path>:
161	</p>
162
163	<pre caption="Adding usbfs filesystem to /etc/fstab">
164	none /proc/bus/usb usbfs defaults 0 0
165	</pre>
166
167	<p>
168	Reread your <path>/etc/fstab</path>, save and quit to continue.	159	Double-check your <path>/etc/fstab</path>, save and quit to continue.
169	</p>	160	</p>
170		161
171	</body>	162	</body>
172	</subsection>	163	</subsection>
173	</section>	164	</section>
…		…
176	<subsection>	167	<subsection>
177	<title>Hostname, Domainname etc.</title>	168	<title>Hostname, Domainname etc.</title>
178	<body>	169	<body>
179		170
180	<p>	171	<p>
181	One of the choices the user has to make is name his PC. This seems to be quite	172	One of the choices the user has to make is name his/her PC. This seems to be
182	easy, but <e>lots</e> of users are having difficulties finding the appropriate	173	quite easy, but <e>lots</e> of users are having difficulties finding the
183	name for their Linux-pc. To speed things up, know that any name you choose can	174	appropriate name for their Linux-pc. To speed things up, know that any name you
184	be changed afterwards. For all we care, you can just call your system	175	choose can be changed afterwards. For all we care, you can just call your system
185	<c>tux</c> and domain <c>homenetwork</c>.	176	<c>tux</c> and domain <c>homenetwork</c>.
186	</p>	177	</p>
187		178
188	<p>	179	<p>
189	We use these values in the next examples. First we set the hostname:	180	We use these values in the next examples. First we set the hostname:
…		…
206	one), you need to define that one too:	197	one), you need to define that one too:
207	</p>	198	</p>
208		199
209	<pre caption="Setting the NIS domainname">	200	<pre caption="Setting the NIS domainname">
210	# <i>echo nis.homenetwork > /etc/nisdomainname</i>	201	# <i>echo nis.homenetwork > /etc/nisdomainname</i>
		202	</pre>
		203
		204	<p>
		205	Now add the <c>domainname</c> script to the default runlevel:
		206	</p>
		207
		208	<pre caption="Adding domainname to the default runlevel">
		209	# <i>rc-update add domainname default</i>
211	</pre>	210	</pre>
212		211
213	</body>	212	</body>
214	</subsection>	213	</subsection>
215	<subsection>	214	<subsection>
…		…
223	your Gentoo system permanently.	222	your Gentoo system permanently.
224	</p>	223	</p>
225		224
226	<p>	225	<p>
227	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses	226	All networking information is gathered in <path>/etc/conf.d/net</path>. It uses
228	a straightforward yet not intuitive syntax if you don't know how to setup	227	a straightforward yet not intuitive syntax if you don't know how to set up
229	networking manually. But don't fear, we'll explain everything :)	228	networking manually. But don't fear, we'll explain everything :)
230	</p>	229	</p>
231		230
232	<p>	231	<p>
233	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>	232	First open <path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c>
…		…
236		235
237	<pre caption="Opening /etc/conf.d/net for editing">	236	<pre caption="Opening /etc/conf.d/net for editing">
238	# <i>nano -w /etc/conf.d/net</i>	237	# <i>nano -w /etc/conf.d/net</i>
239	</pre>	238	</pre>
240		239
		240	<!-- Old baselayout - current stable -->
		241
241	<p>	242	<p>
242	The first variable you'll find is <c>iface_eth0</c>. It uses the following	243	The first variable you'll find is <c>iface_eth0</c>. It uses the following
243	syntax:	244	syntax:
244	</p>	245	</p>
245		246
…		…
247	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"	248	iface_eth0="<i><your ip address></i> broadcast <i><your broadcast address></i> netmask <i><your netmask></i>"
248	</pre>	249	</pre>
249		250
250	<p>	251	<p>
251	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>	252	If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
		253	to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.
252	to <c>dhcp</c>. However, if you need to setup your network manually and you're	254	If you need to set up your network manually and you're
253	not familiar with all the above terms, please read the section on <uri	255	not familiar with all the above terms, please read the section on <uri
254	link="?part=1&chap=3#doc_chap4_sect3">Understanding Network	256	link="?part=1&chap=3#network_term">Understanding Network
255	Terminology</uri> if you haven't done so already.	257	Terminology</uri> if you haven't done so already.
256	</p>	258	</p>
257		259
258	<p>	260	<p>
259	So lets give two examples; the first one uses DHCP, the second one a static IP	261	So let us give three examples; the first one uses DHCP, the second one a static
260	(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway	262	IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and
261	192.168.0.1:	263	gateway 192.168.0.1 while the third one just activates the interface for
		264	rp-pppoe usage:
262	</p>	265	</p>
263		266
264	<pre caption="Examples for /etc/conf.d/net">	267	<pre caption="Examples for /etc/conf.d/net">
265	<comment>(For DHCP:)</comment>	268	<comment>(For DHCP)</comment>
266	iface_eth0="dhcp"	269	iface_eth0="dhcp"
		270	<comment># Some network admins require that you use the</comment>
		271	<comment># hostname and domainname provided by the DHCP server.</comment>
		272	<comment># In that case, add the following to let dhcpcd use them.</comment>
		273	<comment># That will override your own hostname and domainname definitions.</comment>
		274	dhcpcd_eth0="-HD"
		275	<comment># If you intend on using NTP to keep your machine clock synchronized, use</comment>
		276	<comment># the -N option to prevent dhcpcd from overwriting your /etc/ntp.conf file</comment>
		277	dhcpcd_eth0="-N"
267		278
268	<comment>(For static IP:)</comment>	279	<comment>(For static IP)</comment>
269	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"	280	iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
270	gateway="eth0/192.168.0.1"	281	gateway="eth0/192.168.0.1"
		282
		283	<comment>(For rp-pppoe)</comment>
		284	iface_eth0="up"
271	</pre>	285	</pre>
272		286
273	<p>	287	<p>
274	If you have several network interfaces, create extra <c>iface_eth</c> variables,	288	If you have several network interfaces, create extra <c>iface_eth</c> variables,
275	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable	289	like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
276	shouldn't be reproduced as you can only set one gateway per computer.	290	shouldn't be reproduced as you can only set one gateway per computer.
277	</p>	291	</p>
278		292
		293	<!-- New baselayout - current testing
		294
		295	<p>
		296	The first variable you'll find is called <c>config_eth0</c>. As you can probably
		297	imagine, this variable configured the eth0 network interface. If the interface
		298	needs to automatically obtain an IP through DHCP, you should set it like so:
		299	</p>
		300
		301	<pre caption="Automatically obtaining an IP for eth0">
		302	config_eth0=( "dhcp" )
		303	</pre>
		304
		305	<p>
		306	However, if you have to enter your own IP address, netmask and gateway, you need
		307	to set both <c>config_eth0</c> and <c>routes_eth0</c>:
		308	</p>
		309
		310	<pre caption="Manually setting IP information for eth0">
		311	config_eth0=( "192.168.0.2 netmask 255.255.255.0" )
		312	routes_eth0=( "default gw 192.168.0.1" )
		313	</pre>
		314
		315	<p>
		316	If you have several network interfaces repeat the above steps for
		317	<c>config_eth1</c>, <c>config_eth2</c>, etc.
		318	</p>
		319
		320	-->
		321
279	<p>	322	<p>
280	Now save the configuration and exit to continue.	323	Now save the configuration and exit to continue.
281	</p>	324	</p>
282		325
283	</body>	326	</body>
…		…
285	<subsection>	328	<subsection>
286	<title>Automatically Start Networking at Boot</title>	329	<title>Automatically Start Networking at Boot</title>
287	<body>	330	<body>
288		331
289	<p>	332	<p>
290	To have your network interfaces activated at boot, you need to add those to the	333	To have your network interfaces activated at boot, you need to add them to the
291	default runlevel. If you have PCMCIA interfaces you should skip this action as	334	default runlevel. If you have PCMCIA interfaces you should skip this action as
292	the PCMCIA interfaces are started by the PCMCIA init script.	335	the PCMCIA interfaces are started by the PCMCIA init script.
293	</p>	336	</p>
294		337
295	<pre caption="Adding net.eth0 to the default runlevel">	338	<pre caption="Adding net.eth0 to the default runlevel">
…		…
317	<p>	360	<p>
318	You now need to inform Linux about your network. This is defined in	361	You now need to inform Linux about your network. This is defined in
319	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses	362	<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses
320	for hosts that aren't resolved by your nameserver. For instance, if your	363	for hosts that aren't resolved by your nameserver. For instance, if your
321	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),	364	internal network consists of three PCs called <c>jenny</c> (192.168.0.5),
322	<c>benny</c> (192.168.0.6) and <c>tux</c> (this system) you would	365	<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would
323	open <path>/etc/hosts</path> and fill in the values:	366	open <path>/etc/hosts</path> and fill in the values:
324	</p>	367	</p>
325		368
326	<pre caption="Opening /etc/hosts">	369	<pre caption="Opening /etc/hosts">
327	# <i>nano -w /etc/hosts</i>	370	# <i>nano -w /etc/hosts</i>
328	</pre>	371	</pre>
329		372
330	<pre caption="Filling in the networking information">	373	<pre caption="Filling in the networking information">
331	127.0.0.1 tux.homenetwork localhost	374	127.0.0.1 localhost
332	192.168.0.5 jenny	375	192.168.0.5 jenny.homenetwork jenny
333	192.168.0.56 benny	376	192.168.0.6 benny.homenetwork benny
		377	192.168.0.7 tux.homenetwork tux
334	</pre>	378	</pre>
335		379
336	<p>	380	<p>
337	If your system is the only system (or the nameservers handle all name	381	If your system is the only system (or the nameservers handle all name
338	resolution) a single line is sufficient:	382	resolution) a single line is sufficient. For instance, if you want to call your
		383	system <c>tux</c>:
339	</p>	384	</p>
340		385
341	<pre caption="/etc/hosts for lonely or fully integrated PCs">	386	<pre caption="/etc/hosts for lonely or fully integrated PCs">
342	127.0.0.1 localhost tux	387	127.0.0.1 localhost tux
343	</pre>	388	</pre>
344		389
345	<p>	390	<p>
346	Save and exit the editor to continue.	391	Save and exit the editor to continue.
347	</p>	392	</p>
348		393
349	<p>	394	<p>
350	If you don't have PCMCIA, you can now continue with <uri	395	If you don't have PCMCIA, you can now continue with <uri
351	link="#doc_chap4">System Information</uri>. PCMCIA-users should read the	396	link="#doc_chap3">System Information</uri>. PCMCIA-users should read the
352	following topic on PCMCIA.	397	following topic on PCMCIA.
353	</p>	398	</p>
354		399
355	</body>	400	</body>
356	</subsection>	401	</subsection>
357	<subsection>	402	<subsection>
358	<title>Optional: Get PCMCIA Working</title>	403	<title>Optional: Get PCMCIA Working</title>
359	<body>	404	<body>
360		405
		406	<note>
		407	pcmcia-cs is only available for x86, amd64 and ppc platforms.
		408	</note>
		409
361	<p>	410	<p>
362	PCMCIA-users should first install the <c>pcmcia-cs</c> package:	411	PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
		412	includes users who will be working with a 2.6 kernel (even though they won't be
		413	using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
		414	to avoid installing xorg-x11 at this moment:
363	</p>	415	</p>
364		416
365	<pre caption="Installing pcmcia-cs">	417	<pre caption="Installing pcmcia-cs">
366	# <i>emerge -k pcmcia-cs</i>	418	# <i>USE="-X" emerge pcmcia-cs</i>
367	</pre>	419	</pre>
368		420
369	<p>	421	<p>
370	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>boot</e>	422	When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
371	runlevel:	423	runlevel:
372	</p>	424	</p>
373		425
374	<pre caption="Adding pcmcia to the default runlevel">	426	<pre caption="Adding pcmcia to the default runlevel">
375	# <i>rc-update add pcmcia boot</i>	427	# <i>rc-update add pcmcia default</i>
376	</pre>	428	</pre>
377		429
378	</body>	430	</body>
379	</subsection>	431	</subsection>
380	</section>	432	</section>
381	<section>	433	<section>
382	<title>System Information</title>	434	<title>System Information</title>
		435	<subsection>
		436	<title>Root Password</title>
		437	<body>
		438
		439	<p>
		440	First we set the root password by typing:
		441	</p>
		442
		443	<pre caption="Setting the root password">
		444	# <i>passwd</i>
		445	</pre>
		446
		447	<p>
		448	If you want root to be able to log on through the serial console, add
		449	<c>tts/0</c> to <path>/etc/securetty</path>:
		450	</p>
		451
		452	<pre caption="Adding tts/0 to /etc/securetty">
		453	# <i>echo "tts/0" >> /etc/securetty</i>
		454	</pre>
		455
		456	</body>
		457	</subsection>
		458	<subsection>
		459	<title>System Information</title>
383	<body>	460	<body>
384		461
385	<p>	462	<p>
386	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.	463	Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration.
387	Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)	464	Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :)
…		…
391	# <i>nano -w /etc/rc.conf</i>	468	# <i>nano -w /etc/rc.conf</i>
392	</pre>	469	</pre>
393		470
394	<p>	471	<p>
395	As you can see, this file is well commented to help you set up the necessary	472	As you can see, this file is well commented to help you set up the necessary
396	configuration variables. When you're finished configuring	473	configuration variables. Take special care with the <c>KEYMAP</c> setting: if
397	<path>/etc/rc.conf</path>, save and exit to continue.	474	you select the wrong <c>KEYMAP</c> you will get weird results when typing on
		475	your keyboard.
		476	</p>
		477
		478	<note>
		479	Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
		480	select an i386 keymap (such as "us") instead of "sunkeymap".
		481	</note>
		482
398	</p>	483	<p>
		484	<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
		485	ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
		486	to set a mac/ppc keymap in <path>rc.conf</path>.
		487	</p>
399		488
		489	<p>
		490	When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
		491	continue with <uri link="?part=1&chap=9">Installing Necessary System
		492	Tools</uri>.
		493	</p>
		494
400	</body>	495	</body>
		496	</subsection>
401	</section>	497	</section>
402	</sections>	498	</sections>

 Legend:



Removed from v.1.7
 


changed lines


 
Added in v.1.58
 Legend:



Removed from v.1.7
 


changed lines


 
Added in v.1.58
-Removed from v.1.7
+Added in v.1.58

	ViewVC Help
Powered by ViewVC 1.1.13