en/handbook/hb-install-finalise.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->

<!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-finalise.xml,v 1.25 2004/04/15 07:06:36 swift Exp $ -->

<sections>
<section>
<title>User Administration</title>
<subsection>
<title>Setting a root Password</title>
<body>

<p>
Before you forget, set the root password by typing:
</p>

<pre caption="Setting the root password">
# <i>passwd</i>
</pre>

<p>
If you want root to be able to log on through the serial console, add
<c>tts/0</c> to <path>/etc/securetty</path>:
</p>

<pre caption="Adding tts/0 to /etc/securetty">
# <i>echo "tts/0" &gt;&gt; /etc/securetty</i>
</pre>

</body>
</subsection>
<subsection>
<title>Adding a User for Daily Use</title>
<body>

<p>
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided
as much as possible. Therefore it is <e>strongly</e> recommended to add a user 
for day-to-day use.
</p>

<p>
For instance, to create a user called <c>john</c> who is member of the
<c>wheel</c> group (be able to change to root using <c>su</c>), <c>users</c>
group (default for all users) and <c>audio</c> group (be able to use audio
devices):
</p>

<pre caption="Adding a user for day-to-day use">
# <i>useradd john -m -G users,wheel,audio -s /bin/bash</i>
# <i>passwd john</i>
Password: <comment>(Enter the password for john)</comment>
Re-enter password: <comment>(Re-enter the password to verify)</comment>
</pre>

<p>
If a user ever needs to perform some task as root, they can use <c>su -</c>
to temporarily receive root privileges. Another way is to use the <c>sudo</c> 
package which is, if correctly configured, very secure.
</p>

</body>
</subsection>
</section>
<section>
<title>Reboot and Enjoy</title>
<subsection>
<title>Rebooting</title>
<body>

<p>
Congratulations! Your Gentoo system is now ready. Exit the chrooted environment 
and unmount all mounted partitions. Then type in that 
one magical command you have been waiting for: <c>reboot</c>.
</p>

<pre caption="Rebooting the system">
# <i>exit</i>
# <i>cd /</i>
# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
# <i>reboot</i>
</pre>

<p>
Of course, don't forget to remove the bootable CD, otherwise the CD will be
booted again instead of your new Gentoo system.
</p>

<p>
OldWorld <b>PPC</b> users will boot in MacOS since their bootloader
isn't installed yet. Those users should read <uri
link="#doc_chap2_sect2">Optional: Configuring BootX</uri>. <b>MIPS</b> users 
will have to do some more tweaking in their MIPS PROM to get Gentoo to work. 
Those users should read <uri link="#doc_chap2_sect3">Optional: Getting 
Gentoo/MIPS to Work</uri>. 
</p>

<p>
GRP users can continue with <uri link="#doc_chap2_sect4">Optional: 
Install GRP Packages</uri>, all the rest can finish up with <uri 
link="?part=1&amp;chap=12">Where to go from here?</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Configuring BootX</title>
<body>

<impo>
This subsection is <e>only</e> for <b>PPC</b> users who want to use BootX as
bootloader. All other readers should skip this subsection.
</impo>

<p>
Now your machine is booted in MacOS, open the BootX control panel.
Select <c>Options</c>, and uncheck <c>Used specified RAM disk</c>. When you 
return to the BootX main screen, you will now find an option to specify your
machine's root disk and partition. Fill these in with the appropriate
values.
</p>

<p>
BootX can be configured to start Linux upon boot. If you do this, you will
first see your machine boot into MacOS then, during startup, BootX will
load and start Linux. See the <uri
link="http://penguinppc.org/projects/bootx/">BootX home page</uri> for more 
information.
</p>

<p>
If you are a GRP users you can continue with <uri
link="#doc_chap2_sect4">Optional: Install GRP Packages</uri>, otherwise go to
<uri link="?part=1&amp;chap=12">Where to go from here?</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Getting Gentoo/MIPS to Work</title>
<body>

<impo>
This subsection is <e>only</e> for <b>MIPS</b> users! All other readers should 
skip this subsection.
</impo>

<p>
When you are rebooted, go to the <e>System Maintenance Menu</e> and select
<e>Enter Command Monitor</e> (<c>5</c>). If you want to test your new Gentoo
installation, you can just run <c>boot -f &lt;kernel name&gt;</c>. To have your
system permanently boot into the Gentoo installation, you need to set some
variables in the MIPS PROM:
</p>

<pre caption="Configuring the PROM to Boot Gentoo">
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor

Option? <i>5</i>
Command Monitor.  Type "exit" to return to the menu.

<comment>(&lt;root device&gt; = Gentoo's root partition, e.g. /dev/sda3)</comment>
&gt;&gt; <i>setenv OSLoadPartition &lt;root device&gt;</i>

<comment>(To list the available kernels, type "ls")</comment>
&gt;&gt; <i>setenv OSLoader &lt;kernel name&gt;</i>
&gt;&gt; <i>setenv OSLoadFilename &lt;kernel name&gt;</i>

<comment>(Declare the kernel parameters you want to pass)</comment>
&gt;&gt; <i>setenv OSLoadOptions &lt;kernel parameters&gt;</i>

<comment>(Provide the location of the Volume Header)</comment>
&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>

<comment>(Automatically boot Gentoo)</comment>
&gt;&gt; <i>setenv AutoLoad Yes</i>

<comment>(Set the timezone)</comment>
&gt;&gt; <i>setenv TimeZone EST5EDT</i>

<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
&gt;&gt; <i>setenv console d1</i>
</pre>

<p>
Now you're ready to enjoy Gentoo!
</p>

</body>
</subsection>
<subsection>
<title>Optional: Install GRP Packages</title>
<body>

<impo>
This part is for GRP users only. Other users should skip this part and continue
with <uri link="?part=1&amp;chap=12">Where to go from here?</uri>.
</impo>

<p>
Now that your system is booted, log on as the user you created (for instance,
<c>john</c>) and use <c>su -</c> to gain root privileges:
</p>

<pre caption="Gaining root privileges">
$ <i>su -</i>
Password: <comment>(Enter your root password)</comment>
</pre>

<p>
Now we need to change the Portage configuration to look for the prebuilt 
binaries from the second CD (Gentoo Packages CD). First mount this CD:
</p>

<pre caption="Mount the Packages CD">
# <i>mkdir /mnt/cdrom</i>
<comment>(Put the Gentoo Packages CD in the CD tray)</comment>
# <i>mount /mnt/cdrom</i>
</pre>

<p>
Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages:
</p>

<pre caption="Configuring Portage to use /mnt/cdrom">
# <i>ls /mnt/cdrom</i>

<comment>(If there is a /mnt/cdrom/packages directory:)</comment>
# <i>export PKGDIR="/mnt/cdrom/packages"</i>

<comment>(Otherwise:)</comment>
# <i>export PKGDIR="/mnt/cdrom"</i>
</pre>

<p>
Now install the packages you want. The Packages CD contains several prebuilt 
binaries, for instance KDE:
</p>

<pre caption="Installing KDE">
# <i>USE="bindist" emerge --usepkg kde</i>
</pre>

<p>
The <c>USE="bindist"</c> is needed when you install XFree (either directly or as
a dependency). It prevents the downloading of Microsoft's core fonts (which we
cannot distribute on our LiveCDs).
</p>

<p>
Be sure to install the binaries now. When you do an <c>emerge sync</c> to update
Portage (as you will learn later), the prebuilt binaries might not match against
the ebuilds in your updated Portage. You can try to circumvent this by using
<c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>.
</p>

<p>
Congratulations, your system is now fully equiped! Continue with <uri
link="?part=1&amp;chap=12">Where to go from here?</uri> to learn more about
Gentoo.
</p>

</body>
</subsection>
</section>
</sections>
1	swift	1.14	<?xml version='1.0' encoding='UTF-8'?>
2			<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4	swift	1.5	<!-- The content of this document is licensed under the CC-BY-SA license -->
5			<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6
7	swift	1.26	<!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-finalise.xml,v 1.25 2004/04/15 07:06:36 swift Exp $ -->
8	swift	1.7
9	swift	1.3	<sections>
10	swift	1.1	<section>
11			<title>User Administration</title>
12	swift	1.4	<subsection>
13			<title>Setting a root Password</title>
14	swift	1.1	<body>
15
16			<p>
17	swift	1.4	Before you forget, set the root password by typing:
18			</p>
19
20			<pre caption="Setting the root password">
21			# <i>passwd</i>
22			</pre>
23
24	swift	1.11	<p>
25			If you want root to be able to log on through the serial console, add
26	swift	1.22	<c>tts/0</c> to <path>/etc/securetty</path>:
27	swift	1.11	</p>
28
29	swift	1.22	<pre caption="Adding tts/0 to /etc/securetty">
30			# <i>echo "tts/0" >> /etc/securetty</i>
31	swift	1.11	</pre>
32
33	swift	1.4	</body>
34			</subsection>
35			<subsection>
36			<title>Adding a User for Daily Use</title>
37			<body>
38
39			<p>
40			Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided
41	swift	1.10	as much as possible. Therefore it is <e>strongly</e> recommended to add a user
42	swift	1.4	for day-to-day use.
43			</p>
44
45			<p>
46			For instance, to create a user called <c>john</c> who is member of the
47			<c>wheel</c> group (be able to change to root using <c>su</c>), <c>users</c>
48			group (default for all users) and <c>audio</c> group (be able to use audio
49			devices):
50			</p>
51
52			<pre caption="Adding a user for day-to-day use">
53			# <i>useradd john -m -G users,wheel,audio -s /bin/bash</i>
54			# <i>passwd john</i>
55			Password: <comment>(Enter the password for john)</comment>
56			Re-enter password: <comment>(Re-enter the password to verify)</comment>
57			</pre>
58
59			<p>
60	swift	1.26	If a user ever needs to perform some task as root, they can use <c>su -</c>
61	swift	1.25	to temporarily receive root privileges. Another way is to use the <c>sudo</c>
62	swift	1.4	package which is, if correctly configured, very secure.
63	swift	1.1	</p>
64
65			</body>
66	swift	1.4	</subsection>
67	swift	1.3	</section>
68			<section>
69			<title>Reboot and Enjoy</title>
70	swift	1.1	<subsection>
71	swift	1.2	<title>Rebooting</title>
72	swift	1.1	<body>
73
74			<p>
75	swift	1.18	Congratulations! Your Gentoo system is now ready. Exit the chrooted environment
76	swift	1.23	and unmount all mounted partitions. Then type in that
77	swift	1.15	one magical command you have been waiting for: <c>reboot</c>.
78	swift	1.4	</p>
79
80			<pre caption="Rebooting the system">
81			# <i>exit</i>
82			# <i>cd /</i>
83			# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
84			# <i>reboot</i>
85			</pre>
86
87			<p>
88	swift	1.6	Of course, don't forget to remove the bootable CD, otherwise the CD will be
89	swift	1.4	booted again instead of your new Gentoo system.
90			</p>
91
92			<p>
93	swift	1.24	OldWorld <b>PPC</b> users will boot in MacOS since their bootloader
94	swift	1.4	isn't installed yet. Those users should read <uri
95	swift	1.24	link="#doc_chap2_sect2">Optional: Configuring BootX</uri>. <b>MIPS</b> users
96			will have to do some more tweaking in their MIPS PROM to get Gentoo to work.
97			Those users should read <uri link="#doc_chap2_sect3">Optional: Getting
98			Gentoo/MIPS to Work</uri>.
99	swift	1.19	</p>
100
101			<p>
102			GRP users can continue with <uri link="#doc_chap2_sect4">Optional:
103			Install GRP Packages</uri>, all the rest can finish up with <uri
104	swift	1.4	link="?part=1&chap=12">Where to go from here?</uri>.
105	swift	1.1	</p>
106
107			</body>
108	swift	1.3	</subsection>
109			<subsection>
110	swift	1.2	<title>Optional: Configuring BootX</title>
111			<body>
112
113	swift	1.4	<impo>
114	swift	1.24	This subsection is <e>only</e> for <b>PPC</b> users who want to use BootX as
115	swift	1.3	bootloader. All other readers should skip this subsection.
116	swift	1.4	</impo>
117	swift	1.2
118			<p>
119			Now your machine is booted in MacOS, open the BootX control panel.
120			Select <c>Options</c>, and uncheck <c>Used specified RAM disk</c>. When you
121			return to the BootX main screen, you will now find an option to specify your
122			machine's root disk and partition. Fill these in with the appropriate
123			values.
124			</p>
125
126			<p>
127			BootX can be configured to start Linux upon boot. If you do this, you will
128			first see your machine boot into MacOS then, during startup, BootX will
129			load and start Linux. See the <uri
130			link="http://penguinppc.org/projects/bootx/">BootX home page</uri> for more
131			information.
132			</p>
133
134	swift	1.4	<p>
135			If you are a GRP users you can continue with <uri
136	swift	1.19	link="#doc_chap2_sect4">Optional: Install GRP Packages</uri>, otherwise go to
137	swift	1.4	<uri link="?part=1&chap=12">Where to go from here?</uri>.
138			</p>
139
140	swift	1.2	</body>
141	swift	1.1	</subsection>
142	swift	1.4	<subsection>
143	swift	1.11	<title>Optional: Getting Gentoo/MIPS to Work</title>
144			<body>
145
146	swift	1.24	<impo>
147			This subsection is <e>only</e> for <b>MIPS</b> users! All other readers should
148			skip this subsection.
149			</impo>
150
151	swift	1.11	<p>
152			When you are rebooted, go to the <e>System Maintenance Menu</e> and select
153			<e>Enter Command Monitor</e> (<c>5</c>). If you want to test your new Gentoo
154			installation, you can just run <c>boot -f <kernel name></c>. To have your
155			system permanently boot into the Gentoo installation, you need to set some
156			variables in the MIPS PROM:
157			</p>
158
159			<pre caption="Configuring the PROM to Boot Gentoo">
160			1) Start System
161			2) Install System Software
162			3) Run Diagnostics
163			4) Recover System
164			5) Enter Command Monitor
165
166			Option? <i>5</i>
167			Command Monitor. Type "exit" to return to the menu.
168
169			<comment>(<root device> = Gentoo's root partition, e.g. /dev/sda3)</comment>
170			>> <i>setenv OSLoadPartition <root device></i>
171
172			<comment>(To list the available kernels, type "ls")</comment>
173			>> <i>setenv OSLoader <kernel name></i>
174			>> <i>setenv OSLoadFilename <kernel name></i>
175
176			<comment>(Declare the kernel parameters you want to pass)</comment>
177			>> <i>setenv OSLoadOptions <kernel parameters></i>
178
179			<comment>(Provide the location of the Volume Header)</comment>
180			>> <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
181
182			<comment>(Automatically boot Gentoo)</comment>
183			>> <i>setenv AutoLoad Yes</i>
184
185			<comment>(Set the timezone)</comment>
186			>> <i>setenv TimeZone EST5EDT</i>
187
188			<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
189			>> <i>setenv console d1</i>
190			</pre>
191
192			<p>
193			Now you're ready to enjoy Gentoo!
194			</p>
195
196			</body>
197			</subsection>
198			<subsection>
199	swift	1.19	<title>Optional: Install GRP Packages</title>
200	swift	1.1	<body>
201
202	swift	1.4	<impo>
203			This part is for GRP users only. Other users should skip this part and continue
204			with <uri link="?part=1&chap=12">Where to go from here?</uri>.
205			</impo>
206
207			<p>
208			Now that your system is booted, log on as the user you created (for instance,
209			<c>john</c>) and use <c>su -</c> to gain root privileges:
210			</p>
211
212			<pre caption="Gaining root privileges">
213			$ <i>su -</i>
214			Password: <comment>(Enter your root password)</comment>
215			</pre>
216
217			<p>
218	swift	1.20	Now we need to change the Portage configuration to look for the prebuilt
219	swift	1.21	binaries from the second CD (Gentoo Packages CD). First mount this CD:
220	swift	1.4	</p>
221
222	swift	1.21	<pre caption="Mount the Packages CD">
223	swift	1.17	# <i>mkdir /mnt/cdrom</i>
224	swift	1.21	<comment>(Put the Gentoo Packages CD in the CD tray)</comment>
225	swift	1.4	# <i>mount /mnt/cdrom</i>
226			</pre>
227
228	swift	1.1	<p>
229	swift	1.20	Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages:
230	swift	1.4	</p>
231
232	swift	1.20	<pre caption="Configuring Portage to use /mnt/cdrom">
233			# <i>ls /mnt/cdrom</i>
234
235			<comment>(If there is a /mnt/cdrom/packages directory:)</comment>
236			# <i>export PKGDIR="/mnt/cdrom/packages"</i>
237
238			<comment>(Otherwise:)</comment>
239			# <i>export PKGDIR="/mnt/cdrom"</i>
240	swift	1.4	</pre>
241
242			<p>
243	swift	1.21	Now install the packages you want. The Packages CD contains several prebuilt
244			binaries, for instance KDE:
245	swift	1.4	</p>
246
247			<pre caption="Installing KDE">
248	swift	1.19	# <i>USE="bindist" emerge --usepkg kde</i>
249	swift	1.4	</pre>
250
251			<p>
252	swift	1.19	The <c>USE="bindist"</c> is needed when you install XFree (either directly or as
253			a dependency). It prevents the downloading of Microsoft's core fonts (which we
254			cannot distribute on our LiveCDs).
255			</p>
256
257			<p>
258	swift	1.4	Be sure to install the binaries now. When you do an <c>emerge sync</c> to update
259			Portage (as you will learn later), the prebuilt binaries might not match against
260			the ebuilds in your updated Portage. You can try to circumvent this by using
261	swift	1.9	<c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>.
262	swift	1.4	</p>
263
264			<p>
265			Congratulations, your system is now fully equiped! Continue with <uri
266			link="?part=1&chap=12">Where to go from here?</uri> to learn more about
267			Gentoo.
268	swift	1.1	</p>
269
270			</body>
271	swift	1.4	</subsection>
272	swift	1.1	</section>
273	swift	1.3	</sections>