/[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.11 - (show annotations) (download) (as text)
Wed Dec 17 05:29:14 2003 UTC (10 years, 11 months ago) by swift
Branch: MAIN
Changes since 1.10: +66 -4 lines
File MIME type: application/xml
Add MIPS instructions to the hanbook

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

  ViewVC Help
Powered by ViewVC 1.1.20