en/handbook/hb-install-finalise.xml

<!-- 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.7 2003/11/15 13:53:33 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>

</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. Therefor 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 this user ever needs to perform some task as root, he 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. Run <c>etc-update</c> to
update the configuration files (if needed), 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>etc-update</i>
# <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 PPC 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>. GRP users can
continue with <uri link="#doc_chap2_sect3">Optional: Install Extra 
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 PPC-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_sect3">Optional: Install Extra Packages</uri>, otherwise go to
<uri link="?part=1&amp;chap=12">Where to go from here?</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Install Extra 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 copy over the prebuild binaries from the second CD (CD-2) if you
have it. First mount this CD:
</p>

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

<p>
Now copy over all prebuild binaries from the CD to
<path>/usr/portage/packages</path>. Make sure you use the same copy-command!
</p>

<pre caption="Copy over prebuild binaries">
# <i>cp -a /mnt/cdrom/packages/* /usr/portage/packages/</i>
</pre>

<p>
Now install the packages you want. CD-2 contains several prebuild binaries, for
instance KDE:
</p>

<pre caption="Installing KDE">
# <i>emerge -k kde</i>
</pre>

<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 -K</c> instead of <c>emerge -k</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.5	<!-- The content of this document is licensed under the CC-BY-SA license -->
2			<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3
4	swift	1.8	<!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-finalise.xml,v 1.7 2003/11/15 13:53:33 swift Exp $ -->
5	swift	1.7
6	swift	1.3	<sections>
7	swift	1.1	<section>
8			<title>User Administration</title>
9	swift	1.4	<subsection>
10			<title>Setting a root Password</title>
11	swift	1.1	<body>
12
13			<p>
14	swift	1.4	Before you forget, set the root password by typing:
15			</p>
16
17			<pre caption="Setting the root password">
18			# <i>passwd</i>
19			</pre>
20
21			</body>
22			</subsection>
23			<subsection>
24			<title>Adding a User for Daily Use</title>
25			<body>
26
27			<p>
28			Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided
29			as much as possible. Therefor it is <e>strongly</e> recommended to add a user
30			for day-to-day use.
31			</p>
32
33			<p>
34			For instance, to create a user called <c>john</c> who is member of the
35			<c>wheel</c> group (be able to change to root using <c>su</c>), <c>users</c>
36			group (default for all users) and <c>audio</c> group (be able to use audio
37			devices):
38			</p>
39
40			<pre caption="Adding a user for day-to-day use">
41			# <i>useradd john -m -G users,wheel,audio -s /bin/bash</i>
42			# <i>passwd john</i>
43			Password: <comment>(Enter the password for john)</comment>
44			Re-enter password: <comment>(Re-enter the password to verify)</comment>
45			</pre>
46
47			<p>
48			If this user ever needs to perform some task as root, he can use <c>su -</c> to
49			temporarily receive root privileges. Another way is to use the <c>sudo</c>
50			package which is, if correctly configured, very secure.
51	swift	1.1	</p>
52
53			</body>
54	swift	1.4	</subsection>
55	swift	1.3	</section>
56			<section>
57			<title>Reboot and Enjoy</title>
58	swift	1.1	<subsection>
59	swift	1.2	<title>Rebooting</title>
60	swift	1.1	<body>
61
62			<p>
63	swift	1.4	Congratulations! Your Gentoo system is now ready. Run <c>etc-update</c> to
64			update the configuration files (if needed), exit the chrooted environment and
65			unmount all mounted partitions. Then type in that one magical command you have
66			been waiting for: <c>reboot</c>.
67			</p>
68
69			<pre caption="Rebooting the system">
70			# <i>etc-update</i>
71			# <i>exit</i>
72			# <i>cd /</i>
73			# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
74			# <i>reboot</i>
75			</pre>
76
77			<p>
78	swift	1.6	Of course, don't forget to remove the bootable CD, otherwise the CD will be
79	swift	1.4	booted again instead of your new Gentoo system.
80			</p>
81
82			<p>
83			OldWorld PPC users will boot in MacOS since their bootloader
84			isn't installed yet. Those users should read <uri
85			link="#doc_chap2_sect2">Optional: Configuring BootX</uri>. GRP users can
86			continue with <uri link="#doc_chap2_sect3">Optional: Install Extra
87			Packages</uri>, all the rest can finish up with <uri
88			link="?part=1&chap=12">Where to go from here?</uri>.
89	swift	1.1	</p>
90
91			</body>
92	swift	1.3	</subsection>
93			<subsection>
94	swift	1.2	<title>Optional: Configuring BootX</title>
95			<body>
96
97	swift	1.4	<impo>
98	swift	1.3	This subsection is <e>only</e> for PPC-users who want to use BootX as
99			bootloader. All other readers should skip this subsection.
100	swift	1.4	</impo>
101	swift	1.2
102			<p>
103			Now your machine is booted in MacOS, open the BootX control panel.
104			Select <c>Options</c>, and uncheck <c>Used specified RAM disk</c>. When you
105			return to the BootX main screen, you will now find an option to specify your
106			machine's root disk and partition. Fill these in with the appropriate
107			values.
108			</p>
109
110			<p>
111			BootX can be configured to start Linux upon boot. If you do this, you will
112			first see your machine boot into MacOS then, during startup, BootX will
113			load and start Linux. See the <uri
114			link="http://penguinppc.org/projects/bootx/">BootX home page</uri> for more
115			information.
116			</p>
117
118	swift	1.4	<p>
119			If you are a GRP users you can continue with <uri
120			link="#doc_chap2_sect3">Optional: Install Extra Packages</uri>, otherwise go to
121			<uri link="?part=1&chap=12">Where to go from here?</uri>.
122			</p>
123
124	swift	1.2	</body>
125	swift	1.1	</subsection>
126	swift	1.4	<subsection>
127	swift	1.1	<title>Optional: Install Extra Packages</title>
128			<body>
129
130	swift	1.4	<impo>
131			This part is for GRP users only. Other users should skip this part and continue
132			with <uri link="?part=1&chap=12">Where to go from here?</uri>.
133			</impo>
134
135			<p>
136			Now that your system is booted, log on as the user you created (for instance,
137			<c>john</c>) and use <c>su -</c> to gain root privileges:
138			</p>
139
140			<pre caption="Gaining root privileges">
141			$ <i>su -</i>
142			Password: <comment>(Enter your root password)</comment>
143			</pre>
144
145			<p>
146			Now we need to copy over the prebuild binaries from the second CD (CD-2) if you
147			have it. First mount this CD:
148			</p>
149
150			<pre caption="Mount the CD-2">
151			<comment>(Put CD-2 in the CD tray)</comment>
152			# <i>mount /mnt/cdrom</i>
153			</pre>
154
155	swift	1.1	<p>
156	swift	1.4	Now copy over all prebuild binaries from the CD to
157	swift	1.8	<path>/usr/portage/packages</path>. Make sure you use the same copy-command!
158	swift	1.4	</p>
159
160			<pre caption="Copy over prebuild binaries">
161	swift	1.8	# <i>cp -a /mnt/cdrom/packages/* /usr/portage/packages/</i>
162	swift	1.4	</pre>
163
164			<p>
165			Now install the packages you want. CD-2 contains several prebuild binaries, for
166			instance KDE:
167			</p>
168
169			<pre caption="Installing KDE">
170			# <i>emerge -k kde</i>
171			</pre>
172
173			<p>
174			Be sure to install the binaries now. When you do an <c>emerge sync</c> to update
175			Portage (as you will learn later), the prebuilt binaries might not match against
176			the ebuilds in your updated Portage. You can try to circumvent this by using
177			<c>emerge -K</c> instead of <c>emerge -k</c>.
178			</p>
179
180			<p>
181			Congratulations, your system is now fully equiped! Continue with <uri
182			link="?part=1&chap=12">Where to go from here?</uri> to learn more about
183			Gentoo.
184	swift	1.1	</p>
185
186			</body>
187	swift	1.4	</subsection>
188	swift	1.1	</section>
189	swift	1.3	</sections>