1 |
swift |
1.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 |
swift |
1.24 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc64-medium.xml,v 1.23 2005/09/15 09:51:47 rane Exp $ --> |
8 |
swift |
1.1 |
|
9 |
|
|
<sections> |
10 |
swift |
1.10 |
|
11 |
swift |
1.24 |
<version>2.7</version> |
12 |
|
|
<date>2005-10-09</date> |
13 |
swift |
1.10 |
|
14 |
swift |
1.1 |
<section> |
15 |
|
|
<title>Hardware Requirements</title> |
16 |
|
|
<subsection> |
17 |
|
|
<title>Introduction</title> |
18 |
|
|
<body> |
19 |
|
|
|
20 |
|
|
<p> |
21 |
|
|
Before we start, we first list what hardware requirements you need to |
22 |
swift |
1.14 |
successfully install Gentoo on your box. |
23 |
swift |
1.1 |
</p> |
24 |
|
|
|
25 |
|
|
</body> |
26 |
|
|
</subsection> |
27 |
|
|
<subsection> |
28 |
swift |
1.14 |
<title>Hardware Requirements</title> |
29 |
swift |
1.1 |
<body> |
30 |
|
|
|
31 |
swift |
1.14 |
<table> |
32 |
|
|
<tr> |
33 |
|
|
<th>CPU</th> |
34 |
|
|
<ti>Any PowerPC64 CPU</ti> |
35 |
|
|
</tr> |
36 |
|
|
<tr> |
37 |
|
|
<th>Systems</th> |
38 |
|
|
<ti> |
39 |
rane |
1.23 |
IBM RS/6000s, Power Macintosh G5, IBM pSeries and IBM iSeries |
40 |
swift |
1.14 |
</ti> |
41 |
|
|
</tr> |
42 |
|
|
<tr> |
43 |
|
|
<th>Memory</th> |
44 |
|
|
<ti>64 MB</ti> |
45 |
|
|
</tr> |
46 |
|
|
<tr> |
47 |
|
|
<th>Diskspace</th> |
48 |
|
|
<ti>1.5 GB (excluding swap space)</ti> |
49 |
|
|
</tr> |
50 |
|
|
<tr> |
51 |
|
|
<th>Swap space</th> |
52 |
|
|
<ti>At least 256 MB</ti> |
53 |
|
|
</tr> |
54 |
|
|
</table> |
55 |
|
|
|
56 |
swift |
1.1 |
<p> |
57 |
swift |
1.14 |
For a full list of supported systems, please go to |
58 |
|
|
<uri>http://www.linuxppc64.org/hardware.shtml</uri>. |
59 |
swift |
1.1 |
</p> |
60 |
|
|
|
61 |
|
|
</body> |
62 |
|
|
</subsection> |
63 |
|
|
</section> |
64 |
swift |
1.14 |
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
65 |
|
|
<!-- START --> |
66 |
swift |
1.1 |
<section> |
67 |
swift |
1.14 |
<title>The Gentoo Installation Approaches</title> |
68 |
swift |
1.1 |
<subsection> |
69 |
|
|
<title>Introduction</title> |
70 |
|
|
<body> |
71 |
|
|
|
72 |
|
|
<p> |
73 |
swift |
1.14 |
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. |
74 |
|
|
A stage file is a tarball (compressed archive) that contains a minimal |
75 |
|
|
environment. |
76 |
swift |
1.1 |
</p> |
77 |
|
|
|
78 |
|
|
<ul> |
79 |
swift |
1.14 |
<li> |
80 |
|
|
A stage1 file contains nothing more than a compiler, Portage (Gentoo's |
81 |
|
|
software management system) and a couple of packages on which the compiler |
82 |
|
|
or Portage depends. |
83 |
|
|
</li> |
84 |
|
|
<li> |
85 |
|
|
A stage2 file contains a so-called bootstrapped system, a minimal |
86 |
|
|
environment from which one can start building all other necessary |
87 |
|
|
applications that make a Gentoo environment complete. |
88 |
|
|
</li> |
89 |
|
|
<li> |
90 |
|
|
A stage3 file contains a prebuilt minimal system which is almost fully |
91 |
|
|
deployable. It only lacks a few applications where you, the Gentoo user, |
92 |
|
|
needs to choose which one you want to install. |
93 |
|
|
</li> |
94 |
swift |
1.1 |
</ul> |
95 |
|
|
|
96 |
|
|
<p> |
97 |
swift |
1.14 |
To help you decide what stage file you want to use, we have written down the |
98 |
|
|
major advantages and disadvantages of each stage file. |
99 |
swift |
1.1 |
</p> |
100 |
|
|
|
101 |
|
|
</body> |
102 |
|
|
</subsection> |
103 |
|
|
<subsection> |
104 |
swift |
1.14 |
<title>A Stage1 Approach</title> |
105 |
swift |
1.1 |
<body> |
106 |
|
|
|
107 |
|
|
<p> |
108 |
swift |
1.14 |
A <e>stage1</e> is used when you want to bootstrap and build the entire system |
109 |
|
|
from scratch. |
110 |
swift |
1.1 |
</p> |
111 |
|
|
|
112 |
|
|
<p> |
113 |
swift |
1.24 |
This approach builds core system packages that are vital to your system and is |
114 |
|
|
used by Gentoo developers to prepare the Gentoo release media. It is a great |
115 |
|
|
installation method for those who would like to learn more about the inner |
116 |
|
|
workings of bootstrapping, toolchains and the like. |
117 |
|
|
</p> |
118 |
|
|
|
119 |
|
|
<p> |
120 |
|
|
However, if you do not plan to tweak the bootstrapping instructions in the |
121 |
|
|
<path>bootstrap.sh</path> script written by the Gentoo developers, then a |
122 |
|
|
stage1 approach has no benefits for you. |
123 |
swift |
1.1 |
</p> |
124 |
|
|
|
125 |
|
|
<table> |
126 |
|
|
<tr> |
127 |
|
|
<th>Stage1</th> |
128 |
|
|
<th>Pros and Cons</th> |
129 |
|
|
</tr> |
130 |
|
|
<tr> |
131 |
|
|
<th>+</th> |
132 |
|
|
<ti> |
133 |
swift |
1.24 |
Allows you to have total control over the installation routine, bootstrap |
134 |
|
|
sequence, etc. |
135 |
swift |
1.1 |
</ti> |
136 |
|
|
</tr> |
137 |
|
|
<tr> |
138 |
|
|
<th>+</th> |
139 |
swift |
1.24 |
<ti>Suitable for powerusers and developers who know what they are doing</ti> |
140 |
swift |
1.1 |
</tr> |
141 |
|
|
<tr> |
142 |
|
|
<th>-</th> |
143 |
swift |
1.24 |
<ti> |
144 |
|
|
Takes a long time to finish the installation (it is the lengthiest approach) |
145 |
|
|
</ti> |
146 |
swift |
1.1 |
</tr> |
147 |
|
|
<tr> |
148 |
|
|
<th>-</th> |
149 |
|
|
<ti> |
150 |
swift |
1.14 |
If you don't intend to tweak the settings, it is a waste of time |
151 |
swift |
1.1 |
</ti> |
152 |
|
|
</tr> |
153 |
swift |
1.19 |
<tr> |
154 |
|
|
<th>-</th> |
155 |
|
|
<ti> |
156 |
|
|
Requires a working Internet connection during the installation |
157 |
|
|
</ti> |
158 |
|
|
</tr> |
159 |
swift |
1.1 |
</table> |
160 |
|
|
|
161 |
swift |
1.14 |
</body> |
162 |
|
|
</subsection> |
163 |
|
|
<subsection> |
164 |
|
|
<title>A Stage2 Approach</title> |
165 |
|
|
<body> |
166 |
|
|
|
167 |
swift |
1.1 |
<p> |
168 |
swift |
1.14 |
A <e>stage2</e> is used for building the entire system from a bootstrapped |
169 |
|
|
"semi-compiled" state. |
170 |
swift |
1.1 |
</p> |
171 |
|
|
|
172 |
|
|
<p> |
173 |
swift |
1.24 |
When you perform a stage2 installation approach, you will build all system |
174 |
|
|
packages (core packages, including toolchain) using your specific <c>USE</c>, |
175 |
|
|
<c>CFLAGS</c> and <c>CXXFLAGS</c> settings. Any package build will therefore be |
176 |
|
|
optimized to your preference. |
177 |
|
|
</p> |
178 |
|
|
|
179 |
|
|
<p> |
180 |
|
|
However, this installation takes some time and if you do not intend to change |
181 |
|
|
the <c>CFLAGS</c> and <c>CXXFLAGS</c> settings that we have defined as a "good |
182 |
|
|
default", using this approach only makes sense if your <c>USE</c> variable is |
183 |
|
|
sufficiently different from the default <c>USE</c> we provide. |
184 |
swift |
1.1 |
</p> |
185 |
|
|
|
186 |
|
|
<table> |
187 |
|
|
<tr> |
188 |
|
|
<th>Stage2</th> |
189 |
|
|
<th>Pros and Cons</th> |
190 |
|
|
</tr> |
191 |
|
|
<tr> |
192 |
|
|
<th>+</th> |
193 |
|
|
<ti>You don't need to bootstrap</ti> |
194 |
|
|
</tr> |
195 |
|
|
<tr> |
196 |
|
|
<th>+</th> |
197 |
|
|
<ti>Faster than starting with stage1</ti> |
198 |
|
|
</tr> |
199 |
|
|
<tr> |
200 |
|
|
<th>+</th> |
201 |
|
|
<ti>You can still tweak your settings</ti> |
202 |
|
|
</tr> |
203 |
|
|
<tr> |
204 |
|
|
<th>-</th> |
205 |
swift |
1.14 |
<ti>It's still not the fastest way to install Gentoo</ti> |
206 |
swift |
1.1 |
</tr> |
207 |
|
|
<tr> |
208 |
|
|
<th>-</th> |
209 |
swift |
1.19 |
<ti> |
210 |
|
|
Requires a working Internet connection during the installation |
211 |
|
|
</ti> |
212 |
|
|
</tr> |
213 |
swift |
1.1 |
</table> |
214 |
|
|
|
215 |
swift |
1.14 |
</body> |
216 |
|
|
</subsection> |
217 |
|
|
<subsection> |
218 |
|
|
<title>A Stage3 Approach</title> |
219 |
|
|
<body> |
220 |
|
|
|
221 |
|
|
<p> |
222 |
|
|
A <e>stage3</e> installation contains a basic Gentoo Linux system that has been |
223 |
swift |
1.24 |
built for you. You will only need to build a few packages (such as system |
224 |
|
|
logger, networking tools, ...) before you can boot into a base Gentoo |
225 |
|
|
installation. |
226 |
swift |
1.14 |
</p> |
227 |
|
|
|
228 |
swift |
1.1 |
<p> |
229 |
swift |
1.14 |
Choosing to go with a stage3 allows for the fastest install of Gentoo |
230 |
swift |
1.1 |
Linux, but also means that your base system will have the optimization |
231 |
|
|
settings that we chose for you (which to be honest, are good settings |
232 |
|
|
and were carefully chosen to enhance performance while maintaining |
233 |
swift |
1.14 |
stability). Stage3 is also required if you want to install Gentoo using |
234 |
swift |
1.1 |
prebuilt packages or without a network connection. |
235 |
|
|
</p> |
236 |
|
|
|
237 |
|
|
<table> |
238 |
|
|
<tr> |
239 |
|
|
<th>Stage3</th> |
240 |
|
|
<th>Pros and Cons</th> |
241 |
|
|
</tr> |
242 |
|
|
<tr> |
243 |
|
|
<th>+</th> |
244 |
|
|
<ti>Fastest way to get a Gentoo base system</ti> |
245 |
|
|
</tr> |
246 |
|
|
<tr> |
247 |
swift |
1.24 |
<th>+</th> |
248 |
|
|
<ti> |
249 |
|
|
You can still tweak your system |
250 |
|
|
</ti> |
251 |
swift |
1.1 |
</tr> |
252 |
|
|
</table> |
253 |
|
|
|
254 |
|
|
<p> |
255 |
swift |
1.14 |
You might be interested to know that, if you decide to use different |
256 |
|
|
optimization settings after having installed Gentoo, you will be able to |
257 |
swift |
1.24 |
recompile your entire system with the new optimization settings. The same goes |
258 |
|
|
for any <c>USE</c> flag changes: Portage is intelligent enough to know what |
259 |
|
|
packages need to be rebuild. |
260 |
swift |
1.1 |
</p> |
261 |
|
|
|
262 |
|
|
</body> |
263 |
|
|
</subsection> |
264 |
swift |
1.14 |
</section> |
265 |
swift |
1.24 |
|
266 |
swift |
1.14 |
<section> |
267 |
swift |
1.17 |
<title>The Gentoo Installation CDs</title> |
268 |
swift |
1.1 |
<subsection> |
269 |
swift |
1.14 |
<title>Introduction</title> |
270 |
swift |
1.1 |
<body> |
271 |
|
|
|
272 |
|
|
<p> |
273 |
swift |
1.17 |
The <e>Gentoo Installation CDs</e> are bootable CDs which contain a |
274 |
swift |
1.1 |
self-sustained Gentoo environment. They allow you to boot Linux from the CD. |
275 |
|
|
During the boot process your hardware is detected and the appropriate drivers |
276 |
|
|
are loaded. They are maintained by Gentoo developers. |
277 |
|
|
</p> |
278 |
|
|
|
279 |
|
|
<p> |
280 |
swift |
1.17 |
All Installation CDs allow you to boot, set up networking, initialize your |
281 |
swift |
1.14 |
partitions and start installing Gentoo from the Internet. We currently provide |
282 |
swift |
1.17 |
two Installation CDs which are equaly suitable to install Gentoo from, as long |
283 |
|
|
as you're planning on performing an Internet-based installation using the |
284 |
|
|
latest version of the available packages. |
285 |
swift |
1.14 |
</p> |
286 |
|
|
|
287 |
|
|
<p> |
288 |
swift |
1.15 |
If you wish to install Gentoo without a working Internet connection, please use |
289 |
swift |
1.14 |
the installation instructions described in the <uri |
290 |
swift |
1.21 |
link="2005.1/index.xml">Gentoo 2005.1 Handbooks</uri>. This is currently not |
291 |
swift |
1.14 |
supported for the PPC64 architecture though. |
292 |
swift |
1.1 |
</p> |
293 |
|
|
|
294 |
|
|
<p> |
295 |
swift |
1.17 |
For the PowerPC64 architecture, we only supply a <e>Minimal</e> Installation CD, |
296 |
swift |
1.14 |
a small, no-nonsense, bootable CD which sole purpose is to boot the system, |
297 |
|
|
prepare the networking and continue with the Gentoo installation. |
298 |
swift |
1.1 |
</p> |
299 |
|
|
|
300 |
|
|
</body> |
301 |
|
|
</subsection> |
302 |
|
|
<subsection> |
303 |
swift |
1.17 |
<title>Gentoo's Minimal Installation CD</title> |
304 |
swift |
1.1 |
<body> |
305 |
|
|
|
306 |
|
|
<p> |
307 |
swift |
1.17 |
The Minimal Installation CD is called |
308 |
swift |
1.21 |
<c>install-ppc64-g5-minimal-2005.1.iso</c> or |
309 |
|
|
<c>install-ppc64-ibm-minimal-2005.1.iso</c> and takes up only 350 MB of |
310 |
swift |
1.17 |
diskspace. You can use this Installation CD to install Gentoo, but always with a |
311 |
swift |
1.14 |
working Internet connection only. |
312 |
swift |
1.1 |
</p> |
313 |
|
|
|
314 |
|
|
<table> |
315 |
|
|
<tr> |
316 |
swift |
1.17 |
<th>Minimal Installation CD</th> |
317 |
swift |
1.1 |
<th>Pros and Cons</th> |
318 |
|
|
</tr> |
319 |
|
|
<tr> |
320 |
|
|
<th>+</th> |
321 |
|
|
<ti>Smallest download</ti> |
322 |
|
|
</tr> |
323 |
|
|
<tr> |
324 |
|
|
<th>+</th> |
325 |
|
|
<ti> |
326 |
|
|
You can do a stage1, stage2 or stage3 by getting the stage tarball off the |
327 |
|
|
net |
328 |
|
|
</ti> |
329 |
|
|
</tr> |
330 |
|
|
<tr> |
331 |
|
|
<th>-</th> |
332 |
|
|
<ti> |
333 |
swift |
1.14 |
Contains no stages, no Portage snapshot, no prebuilt packages and is |
334 |
|
|
therefore not suitable for networkless installation |
335 |
swift |
1.1 |
</ti> |
336 |
|
|
</tr> |
337 |
|
|
</table> |
338 |
|
|
|
339 |
|
|
</body> |
340 |
|
|
</subsection> |
341 |
|
|
</section> |
342 |
swift |
1.14 |
<!-- STOP --> |
343 |
swift |
1.1 |
<section> |
344 |
swift |
1.17 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
345 |
swift |
1.1 |
<subsection> |
346 |
swift |
1.17 |
<title>Downloading and Burning the Installation CDs</title> |
347 |
swift |
1.1 |
<body> |
348 |
|
|
|
349 |
|
|
<p> |
350 |
swift |
1.17 |
You have chosen to use a Gentoo Installation CD. We'll first start by |
351 |
|
|
downloading and burning the chosen Installation CD. We previously discussed the |
352 |
|
|
several available Installation CDs, but where can you find them? |
353 |
swift |
1.14 |
</p> |
354 |
|
|
|
355 |
|
|
<p> |
356 |
swift |
1.17 |
You can download any of the Installation CDs (and, if you want to, a Packages |
357 |
|
|
CD as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The |
358 |
swift |
1.21 |
Installation CDs are located in the <path>releases/ppc64/2005.1/installcd</path> |
359 |
swift |
1.17 |
directory. |
360 |
swift |
1.1 |
</p> |
361 |
|
|
|
362 |
|
|
<p> |
363 |
swift |
1.14 |
Inside that directory you'll find so-called ISO-files. Those are full CD images |
364 |
swift |
1.1 |
which you can write on a CD-R. |
365 |
|
|
</p> |
366 |
|
|
|
367 |
|
|
<p> |
368 |
swift |
1.14 |
In case you wonder if your downloaded file is corrupted or not, you can |
369 |
|
|
check its MD5 checksum and compare it with the MD5 checksum we provide (such as |
370 |
swift |
1.21 |
<path>install-ppc64-g5-minimal-2005.1.iso.md5</path>). You can check the MD5 |
371 |
swift |
1.1 |
checksum with the <c>md5sum</c> tool under Linux/Unix or <uri |
372 |
|
|
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows. |
373 |
|
|
</p> |
374 |
|
|
|
375 |
|
|
<p> |
376 |
swift |
1.14 |
Another way to check the validity of the downloaded file is to use GnuPG to |
377 |
|
|
verify the cryptographic signature that we provide (the file ending with |
378 |
|
|
<path>.asc</path>). Download the signature file and obtain the public key: |
379 |
swift |
1.1 |
</p> |
380 |
|
|
|
381 |
swift |
1.14 |
<pre caption="Obtaining the public key"> |
382 |
|
|
$ <i>gpg --keyserver pgp.mit.edu --recv-keys 17072058</i> |
383 |
swift |
1.1 |
</pre> |
384 |
|
|
|
385 |
|
|
<p> |
386 |
swift |
1.14 |
Now verify the signature: |
387 |
swift |
1.1 |
</p> |
388 |
|
|
|
389 |
swift |
1.14 |
<pre caption="Verify the cryptographic signature"> |
390 |
|
|
$ <i>gpg --verify <signature file> <downloaded iso></i> |
391 |
|
|
</pre> |
392 |
swift |
1.1 |
|
393 |
|
|
<p> |
394 |
|
|
To burn the downloaded ISO(s), you have to select raw-burning. How you |
395 |
swift |
1.14 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
396 |
|
|
<c>K3B</c> here; more information can be found in our <uri |
397 |
|
|
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
398 |
swift |
1.1 |
</p> |
399 |
|
|
|
400 |
|
|
<ul> |
401 |
|
|
<li> |
402 |
swift |
1.14 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
403 |
|
|
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's |
404 |
swift |
1.16 |
device path). |
405 |
swift |
1.1 |
</li> |
406 |
|
|
<li> |
407 |
swift |
1.14 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
408 |
swift |
1.1 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
409 |
|
|
<c>Start</c>. |
410 |
|
|
</li> |
411 |
swift |
1.7 |
<li> |
412 |
|
|
With Mac OS X Panther, launch <c>Disk Utility</c> from |
413 |
|
|
<path>Applications/Utilities</path>, select <c>Open</c> from the |
414 |
|
|
<c>Images</c> menu, select the mounted disk image in the main window and |
415 |
|
|
select <c>Burn</c> in the <c>Images</c> menu. |
416 |
|
|
</li> |
417 |
|
|
<li> |
418 |
|
|
With Mac OS X Jaguar, launch <c>Disk Copy</c> from |
419 |
|
|
<path>Applications/Utilities</path>, select <c>Burn Image</c> from the |
420 |
|
|
<c>File</c> menu, select the ISO and click the <c>Burn</c> button. |
421 |
|
|
</li> |
422 |
swift |
1.1 |
</ul> |
423 |
|
|
|
424 |
|
|
</body> |
425 |
|
|
</subsection> |
426 |
|
|
<subsection> |
427 |
swift |
1.17 |
<title>Default: Booting the Installation CD on an Apple/IBM</title> |
428 |
swift |
1.1 |
<body> |
429 |
|
|
|
430 |
|
|
<p> |
431 |
swift |
1.17 |
Place the Installation CD in the CD-ROM and reboot the system. Hold down the |
432 |
|
|
'C' key at bootup. You will be greeted by a friendly welcome message and a |
433 |
|
|
<e>boot:</e> prompt at the bottom of the screen. |
434 |
swift |
1.1 |
</p> |
435 |
|
|
|
436 |
|
|
<p> |
437 |
|
|
You are also able to tweak some kernel options at this prompt. The following |
438 |
|
|
table lists the available boot options you can add: |
439 |
|
|
</p> |
440 |
|
|
|
441 |
|
|
<table> |
442 |
|
|
<tr> |
443 |
|
|
<th>Boot Option</th> |
444 |
|
|
<th>Description</th> |
445 |
|
|
</tr> |
446 |
|
|
<tr> |
447 |
|
|
<ti><c>video</c></ti> |
448 |
|
|
<ti> |
449 |
|
|
This option takes one of the following vendor-specific tags: |
450 |
|
|
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or |
451 |
|
|
<c>ofonly</c>. You can follow this tag with the resolution and refreshrate |
452 |
|
|
you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are |
453 |
|
|
uncertain what to choose, <c>ofonly</c> will most certainly work. |
454 |
|
|
</ti> |
455 |
|
|
</tr> |
456 |
|
|
<tr> |
457 |
|
|
<ti><c>nol3</c></ti> |
458 |
|
|
<ti> |
459 |
|
|
Disables level 3 cache on some powerbooks (needed for at least the 17'') |
460 |
|
|
</ti> |
461 |
|
|
</tr> |
462 |
|
|
<tr> |
463 |
|
|
<ti><c>debug</c></ti> |
464 |
|
|
<ti> |
465 |
|
|
Enables verbose booting, spawns an initrd shell that can be used to debug |
466 |
swift |
1.17 |
the Installation CD |
467 |
swift |
1.1 |
</ti> |
468 |
|
|
</tr> |
469 |
|
|
<tr> |
470 |
|
|
<ti><c>sleep=X</c></ti> |
471 |
|
|
<ti> |
472 |
|
|
Wait X seconds before continuing; this can be needed by some very old SCSI |
473 |
|
|
CD-ROMs which don't speed up the CD quick enough |
474 |
|
|
</ti> |
475 |
|
|
</tr> |
476 |
|
|
<tr> |
477 |
|
|
<ti><c>bootfrom=X</c></ti> |
478 |
|
|
<ti> |
479 |
|
|
Boot from a different device |
480 |
|
|
</ti> |
481 |
|
|
</tr> |
482 |
|
|
</table> |
483 |
|
|
|
484 |
|
|
<p> |
485 |
|
|
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
486 |
|
|
loaded from the CD. Continue with <uri link="#booted">And When You're |
487 |
|
|
Booted...</uri>. |
488 |
|
|
</p> |
489 |
|
|
|
490 |
|
|
</body> |
491 |
|
|
</subsection> |
492 |
|
|
<subsection> |
493 |
|
|
<title>IBM pSeries</title> |
494 |
|
|
<body> |
495 |
|
|
|
496 |
|
|
<p> |
497 |
|
|
For pSeries boxes, sometimes the cds might not autoboot. You might have |
498 |
swift |
1.6 |
to set up your cdrom as a bootable device in the multi-boot menu. (F1 at |
499 |
swift |
1.1 |
startup) The other option is to jump into OF and do it from there: |
500 |
|
|
</p> |
501 |
|
|
|
502 |
|
|
<p> |
503 |
|
|
1) Boot into OF (this is 8 from the serial cons or F8 from a graphics |
504 |
|
|
cons, start hitting the key when you see the keyboard mouse etc etc |
505 |
|
|
messages |
506 |
|
|
</p> |
507 |
|
|
<p> |
508 |
|
|
2) run the command 0> boot cdrom:1,yaboot |
509 |
|
|
</p> |
510 |
|
|
<p> |
511 |
|
|
3) stand back and enjoy! |
512 |
|
|
</p> |
513 |
|
|
|
514 |
|
|
</body> |
515 |
|
|
</subsection> |
516 |
|
|
<subsection id="booted"> |
517 |
|
|
<title>And When You're Booted...</title> |
518 |
|
|
<body> |
519 |
|
|
|
520 |
|
|
<p> |
521 |
|
|
You will be greeted by a root ("#") prompt on the current console. You can also |
522 |
|
|
switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get |
523 |
|
|
back to the one you started on by pressing Alt-fn-F1. |
524 |
|
|
</p> |
525 |
|
|
|
526 |
|
|
<p> |
527 |
|
|
If you are installing Gentoo on a system with a non-US keyboard, use |
528 |
|
|
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
529 |
|
|
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
530 |
|
|
</p> |
531 |
|
|
|
532 |
|
|
<pre caption="Listing available keymaps"> |
533 |
|
|
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
534 |
swift |
1.17 |
on the Installation CD are ADB keymaps and unusable with the |
535 |
|
|
Installation CD kernel)</comment> |
536 |
swift |
1.1 |
# <i>ls /usr/share/keymaps/i386</i> |
537 |
|
|
</pre> |
538 |
|
|
|
539 |
|
|
<p> |
540 |
|
|
Now load the keymap of your choice: |
541 |
|
|
</p> |
542 |
|
|
|
543 |
|
|
<pre caption="Loading a keymap"> |
544 |
|
|
# <i>loadkeys be-latin1</i> |
545 |
|
|
</pre> |
546 |
|
|
|
547 |
|
|
<p> |
548 |
|
|
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
549 |
|
|
</p> |
550 |
|
|
|
551 |
|
|
</body> |
552 |
|
|
</subsection> |
553 |
|
|
<subsection id="hardware"> |
554 |
|
|
<title>Extra Hardware Configuration</title> |
555 |
|
|
<body> |
556 |
|
|
|
557 |
|
|
<p> |
558 |
swift |
1.17 |
When the Installation CD boots, it tries to detect all your hardware devices and |
559 |
swift |
1.1 |
loads the appropriate kernel modules to support your hardware. In the |
560 |
swift |
1.17 |
vast majority of cases, it does a very good job. However, in some cases it may |
561 |
|
|
not auto-load the kernel |
562 |
swift |
1.1 |
modules you need. If the PCI auto-detection missed some of your system's |
563 |
|
|
hardware, you will have to load the appropriate kernel modules manually. |
564 |
|
|
</p> |
565 |
|
|
|
566 |
|
|
<p> |
567 |
|
|
In the next example we try to load the <c>8139too</c> module (support for |
568 |
|
|
certain kinds of network interfaces): |
569 |
|
|
</p> |
570 |
|
|
|
571 |
|
|
<pre caption="Loading kernel modules"> |
572 |
|
|
# <i>modprobe 8139too</i> |
573 |
|
|
</pre> |
574 |
|
|
|
575 |
|
|
</body> |
576 |
|
|
</subsection> |
577 |
|
|
<subsection> |
578 |
|
|
<title>Optional: Tweaking Hard Disk Performance</title> |
579 |
|
|
<body> |
580 |
|
|
|
581 |
|
|
<p> |
582 |
|
|
If you are an advanced user, you might want to tweak the IDE hard disk |
583 |
|
|
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
584 |
|
|
test the performance of your disk (execute it several times to get a |
585 |
|
|
more precise impression): |
586 |
|
|
</p> |
587 |
|
|
|
588 |
|
|
<pre caption="Testing disk performance"> |
589 |
|
|
# <i>hdparm -tT /dev/hda</i> |
590 |
|
|
</pre> |
591 |
|
|
|
592 |
|
|
<p> |
593 |
|
|
To tweak, you can use any of the following examples (or experiment |
594 |
|
|
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
595 |
|
|
disk): |
596 |
|
|
</p> |
597 |
|
|
|
598 |
|
|
<pre caption="Tweaking hard disk performance"> |
599 |
|
|
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
600 |
|
|
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
601 |
|
|
</pre> |
602 |
|
|
|
603 |
|
|
</body> |
604 |
|
|
</subsection> |
605 |
swift |
1.2 |
<subsection id="useraccounts"> |
606 |
swift |
1.1 |
<title>Optional: User Accounts</title> |
607 |
|
|
<body> |
608 |
|
|
|
609 |
|
|
<p> |
610 |
|
|
If you plan on giving other people access to your installation |
611 |
|
|
environment or you want to chat using <c>irssi</c> without root privileges (for |
612 |
|
|
security reasons), you need to create the necessary user accounts and change |
613 |
|
|
the root password. |
614 |
|
|
</p> |
615 |
|
|
|
616 |
|
|
<p> |
617 |
|
|
To change the root password, use the <c>passwd</c> utility: |
618 |
|
|
</p> |
619 |
|
|
|
620 |
|
|
<pre caption="Changing the root password"> |
621 |
|
|
# <i>passwd</i> |
622 |
|
|
New password: <comment>(Enter your new password)</comment> |
623 |
|
|
Re-enter password: <comment>(Re-enter your password)</comment> |
624 |
|
|
</pre> |
625 |
|
|
|
626 |
|
|
<p> |
627 |
|
|
To create a user account, we first enter their credentials, followed by |
628 |
|
|
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
629 |
|
|
In the next example, we create a user called "john". |
630 |
|
|
</p> |
631 |
|
|
|
632 |
|
|
<pre caption="Creating a user account"> |
633 |
swift |
1.8 |
# <i>useradd -m -G users john</i> |
634 |
swift |
1.1 |
# <i>passwd john</i> |
635 |
|
|
New password: <comment>(Enter john's password)</comment> |
636 |
|
|
Re-enter password: <comment>(Re-enter john's password)</comment> |
637 |
|
|
</pre> |
638 |
|
|
|
639 |
|
|
<p> |
640 |
|
|
You can change your user id from root to the newly created user by using |
641 |
|
|
<c>su</c>: |
642 |
|
|
</p> |
643 |
|
|
|
644 |
|
|
<pre caption="Changing user id"> |
645 |
swift |
1.4 |
# <i>su - john</i> |
646 |
swift |
1.1 |
</pre> |
647 |
|
|
|
648 |
|
|
</body> |
649 |
|
|
</subsection> |
650 |
|
|
<subsection> |
651 |
swift |
1.2 |
<title>Optional: Viewing Documentation while Installing</title> |
652 |
|
|
<body> |
653 |
|
|
|
654 |
|
|
<p> |
655 |
neysx |
1.20 |
If you want to view the Gentoo Handbook during the installation, make sure you |
656 |
|
|
have created a user account (see <uri link="#useraccounts">Optional: User |
657 |
|
|
Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in. |
658 |
swift |
1.2 |
</p> |
659 |
|
|
|
660 |
|
|
<p> |
661 |
|
|
If you want to view the documentation on the CD you can immediately run |
662 |
|
|
<c>links2</c> to read it: |
663 |
|
|
</p> |
664 |
|
|
|
665 |
|
|
<pre caption="Viewing the on-CD documentation"> |
666 |
neysx |
1.20 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
667 |
swift |
1.2 |
</pre> |
668 |
|
|
|
669 |
|
|
<p> |
670 |
|
|
However, it is preferred that you use the online Gentoo Handbook as it will be |
671 |
neysx |
1.20 |
more recent than the one provided on the CD. |
672 |
swift |
1.2 |
</p> |
673 |
|
|
|
674 |
|
|
<pre caption="Viewing the Online Documentation"> |
675 |
|
|
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i> |
676 |
|
|
</pre> |
677 |
|
|
|
678 |
|
|
<p> |
679 |
|
|
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
680 |
|
|
</p> |
681 |
|
|
|
682 |
|
|
</body> |
683 |
|
|
</subsection> |
684 |
|
|
<subsection> |
685 |
swift |
1.1 |
<title>Optional: Starting the SSH Daemon</title> |
686 |
|
|
<body> |
687 |
|
|
|
688 |
|
|
<p> |
689 |
|
|
If you want to allow other users to access your computer during the |
690 |
|
|
Gentoo installation (perhaps because those users are going to help you |
691 |
|
|
install Gentoo, or even do it for you), you need to create a user |
692 |
|
|
account for them and perhaps even provide them with your root password |
693 |
|
|
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
694 |
|
|
</p> |
695 |
|
|
|
696 |
|
|
<p> |
697 |
|
|
To fire up the SSH daemon, execute the following command: |
698 |
|
|
</p> |
699 |
|
|
|
700 |
|
|
<pre caption="Starting the SSH daemon"> |
701 |
|
|
# <i>/etc/init.d/sshd start</i> |
702 |
|
|
</pre> |
703 |
|
|
|
704 |
|
|
<p> |
705 |
swift |
1.6 |
To be able to use sshd, you first need to set up your networking. Continue with |
706 |
swift |
1.1 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
707 |
|
|
</p> |
708 |
|
|
|
709 |
|
|
</body> |
710 |
|
|
</subsection> |
711 |
|
|
</section> |
712 |
|
|
</sections> |