/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-finalise.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/hb-install-finalise.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.14 - (show annotations) (download) (as text)
Thu Jan 8 14:23:17 2004 UTC (10 years, 11 months ago) by swift
Branch: MAIN
Changes since 1.13: +4 -1 lines
File MIME type: application/xml
Add necessary xml constructs on top of all hb-files, tx to neysx

1 <?xml version='1.0' encoding='UTF-8'?>
2 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4 <!-- 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 <!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-finalise.xml,v 1.13 2004/01/06 10:16:50 swift Exp $ -->
8
9 <sections>
10 <section>
11 <title>User Administration</title>
12 <subsection>
13 <title>Setting a root Password</title>
14 <body>
15
16 <p>
17 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 <p>
25 If you want root to be able to log on through the serial console, add
26 <c>ttyS0</c> to <path>/etc/securetty</path>.
27 </p>
28
29 <pre caption="Adding ttyS0 to /etc/securetty">
30 # <i>echo "ttyS0" &gt;&gt; /etc/securetty</i>
31 </pre>
32
33 </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 as much as possible. Therefore it is <e>strongly</e> recommended to add a user
42 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 If this user ever needs to perform some task as root, he can use <c>su -</c> to
61 temporarily receive root privileges. Another way is to use the <c>sudo</c>
62 package which is, if correctly configured, very secure.
63 </p>
64
65 </body>
66 </subsection>
67 </section>
68 <section>
69 <title>Reboot and Enjoy</title>
70 <subsection>
71 <title>Rebooting</title>
72 <body>
73
74 <p>
75 Congratulations! Your Gentoo system is now ready. Run <c>etc-update</c> to
76 update the configuration files (if needed), exit the chrooted environment and
77 unmount all mounted partitions. Then type in that one magical command you have
78 been waiting for: <c>reboot</c>.
79 </p>
80
81 <pre caption="Rebooting the system">
82 # <i>etc-update</i>
83 # <i>exit</i>
84 # <i>cd /</i>
85 # <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
86 # <i>reboot</i>
87 </pre>
88
89 <p>
90 Of course, don't forget to remove the bootable CD, otherwise the CD will be
91 booted again instead of your new Gentoo system.
92 </p>
93
94 <p>
95 OldWorld PPC users will boot in MacOS since their bootloader
96 isn't installed yet. Those users should read <uri
97 link="#doc_chap2_sect2">Optional: Configuring BootX</uri>. MIPS users will have
98 to do some more tweaking in their MIPS PROM to get Gentoo to work. Those users
99 should read <uri link="#doc_chap2_sect3">Optional: Getting Gentoo/MIPS to
100 Work</uri>. GRP users can continue with <uri link="#doc_chap2_sect4">Optional:
101 Install Extra Packages</uri>, all the rest can finish up with <uri
102 link="?part=1&amp;chap=12">Where to go from here?</uri>.
103 </p>
104
105 </body>
106 </subsection>
107 <subsection>
108 <title>Optional: Configuring BootX</title>
109 <body>
110
111 <impo>
112 This subsection is <e>only</e> for PPC-users who want to use BootX as
113 bootloader. All other readers should skip this subsection.
114 </impo>
115
116 <p>
117 Now your machine is booted in MacOS, open the BootX control panel.
118 Select <c>Options</c>, and uncheck <c>Used specified RAM disk</c>. When you
119 return to the BootX main screen, you will now find an option to specify your
120 machine's root disk and partition. Fill these in with the appropriate
121 values.
122 </p>
123
124 <p>
125 BootX can be configured to start Linux upon boot. If you do this, you will
126 first see your machine boot into MacOS then, during startup, BootX will
127 load and start Linux. See the <uri
128 link="http://penguinppc.org/projects/bootx/">BootX home page</uri> for more
129 information.
130 </p>
131
132 <p>
133 If you are a GRP users you can continue with <uri
134 link="#doc_chap2_sect3">Optional: Install Extra Packages</uri>, otherwise go to
135 <uri link="?part=1&amp;chap=12">Where to go from here?</uri>.
136 </p>
137
138 </body>
139 </subsection>
140 <subsection>
141 <title>Optional: Getting Gentoo/MIPS to Work</title>
142 <body>
143
144 <p>
145 When you are rebooted, go to the <e>System Maintenance Menu</e> and select
146 <e>Enter Command Monitor</e> (<c>5</c>). If you want to test your new Gentoo
147 installation, you can just run <c>boot -f &lt;kernel name&gt;</c>. To have your
148 system permanently boot into the Gentoo installation, you need to set some
149 variables in the MIPS PROM:
150 </p>
151
152 <pre caption="Configuring the PROM to Boot Gentoo">
153 1) Start System
154 2) Install System Software
155 3) Run Diagnostics
156 4) Recover System
157 5) Enter Command Monitor
158
159 Option? <i>5</i>
160 Command Monitor. Type "exit" to return to the menu.
161
162 <comment>(&lt;root device&gt; = Gentoo's root partition, e.g. /dev/sda3)</comment>
163 &gt;&gt; <i>setenv OSLoadPartition &lt;root device&gt;</i>
164
165 <comment>(To list the available kernels, type "ls")</comment>
166 &gt;&gt; <i>setenv OSLoader &lt;kernel name&gt;</i>
167 &gt;&gt; <i>setenv OSLoadFilename &lt;kernel name&gt;</i>
168
169 <comment>(Declare the kernel parameters you want to pass)</comment>
170 &gt;&gt; <i>setenv OSLoadOptions &lt;kernel parameters&gt;</i>
171
172 <comment>(Provide the location of the Volume Header)</comment>
173 &gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
174
175 <comment>(Automatically boot Gentoo)</comment>
176 &gt;&gt; <i>setenv AutoLoad Yes</i>
177
178 <comment>(Set the timezone)</comment>
179 &gt;&gt; <i>setenv TimeZone EST5EDT</i>
180
181 <comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
182 &gt;&gt; <i>setenv console d1</i>
183 </pre>
184
185 <p>
186 Now you're ready to enjoy Gentoo!
187 </p>
188
189 </body>
190 </subsection>
191 <subsection>
192 <title>Optional: Install Extra Packages</title>
193 <body>
194
195 <impo>
196 This part is for GRP users only. Other users should skip this part and continue
197 with <uri link="?part=1&amp;chap=12">Where to go from here?</uri>.
198 </impo>
199
200 <p>
201 Now that your system is booted, log on as the user you created (for instance,
202 <c>john</c>) and use <c>su -</c> to gain root privileges:
203 </p>
204
205 <pre caption="Gaining root privileges">
206 $ <i>su -</i>
207 Password: <comment>(Enter your root password)</comment>
208 </pre>
209
210 <p>
211 Now we need to copy over the prebuilt binaries from the second CD (CD-2) if you
212 have it. First mount this CD:
213 </p>
214
215 <pre caption="Mount the CD-2">
216 <comment>(Put CD-2 in the CD tray)</comment>
217 # <i>mount /mnt/cdrom</i>
218 </pre>
219
220 <p>
221 Now copy over all prebuilt binaries from the CD to
222 <path>/usr/portage/packages</path>. Make sure you use the same copy-command!
223 </p>
224
225 <pre caption="Copy over prebuilt binaries">
226 # <i>cp /mnt/cdrom/packages/All/* /usr/portage/packages/All/</i>
227 </pre>
228
229 <p>
230 Now install the packages you want. CD-2 contains several prebuilt binaries, for
231 instance KDE:
232 </p>
233
234 <pre caption="Installing KDE">
235 # <i>emerge --usepkg kde</i>
236 </pre>
237
238 <p>
239 Be sure to install the binaries now. When you do an <c>emerge sync</c> to update
240 Portage (as you will learn later), the prebuilt binaries might not match against
241 the ebuilds in your updated Portage. You can try to circumvent this by using
242 <c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>.
243 </p>
244
245 <p>
246 Congratulations, your system is now fully equiped! Continue with <uri
247 link="?part=1&amp;chap=12">Where to go from here?</uri> to learn more about
248 Gentoo.
249 </p>
250
251 </body>
252 </subsection>
253 </section>
254 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20