1 |
swift 05/08/08 13:21:15 |
2 |
|
3 |
Added: xml/htdocs/doc/en/handbook/2005.1 handbook-ppc64.xml |
4 |
hb-install-ppc64-bootloader.xml |
5 |
hb-install-ppc64-disk.xml |
6 |
hb-install-ppc64-kernel.xml |
7 |
hb-install-ppc64-medium.xml |
8 |
Log: |
9 |
New architecture for 2005.1: ppc64 |
10 |
|
11 |
Revision Changes Path |
12 |
1.1 xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.xml |
13 |
|
14 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
15 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
16 |
|
17 |
Index: handbook-ppc64.xml |
18 |
=================================================================== |
19 |
<?xml version='1.0' encoding='UTF-8'?> |
20 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
21 |
|
22 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/handbook-ppc64.xml,v 1.1 2005/08/08 13:21:15 swift Exp $ --> |
23 |
|
24 |
<book link="handbook-ppc64.xml"> |
25 |
<title>Gentoo Linux 2005.1 PPC64 Handbook</title> |
26 |
|
27 |
<author title="Author"> |
28 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
29 |
</author> |
30 |
<author title="Author"> |
31 |
<mail link="uberlord@g.o">Roy Marples</mail> |
32 |
</author> |
33 |
<author title="Author"> |
34 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
35 |
</author> |
36 |
<author title="Author"> |
37 |
<mail link="chouser@g.o">Chris Houser</mail> |
38 |
</author> |
39 |
<author title="Author"> |
40 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
41 |
</author> |
42 |
<author title="Gentoo x86 Developer"> |
43 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
44 |
</author> |
45 |
<author title="Gentoo Alpha Developer"> |
46 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
47 |
</author><!-- Does not want to be listed on the rendered page |
48 |
<author title="Gentoo Developer"> |
49 |
Aron Griffis |
50 |
</author> |
51 |
--> |
52 |
<author title="Gentoo AMD64 Developer"> |
53 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
54 |
</author> |
55 |
<author title="Gentoo HPPA developer"> |
56 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
57 |
</author> |
58 |
<author title="Gentoo PPC developer"> |
59 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
60 |
</author> |
61 |
<author title="Gentoo SPARC developer"> |
62 |
<mail link="blademan@g.o">Joe Kallar</mail> |
63 |
</author> |
64 |
<author title="Editor"> |
65 |
<mail link="zhen@g.o">John P. Davis</mail> |
66 |
</author> |
67 |
<author title="Editor">Pierre-Henri Jondot</author> |
68 |
<author title="Editor"> |
69 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
70 |
</author> |
71 |
<author title="Editor"> |
72 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
73 |
</author> |
74 |
<author title="Editor"> |
75 |
<mail link="seo@g.o">Jungmin Seo</mail> |
76 |
</author> |
77 |
<author title="Editor"> |
78 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
79 |
</author> |
80 |
<author title="Editor"> |
81 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
82 |
</author> |
83 |
<author title="Editor"> |
84 |
<mail link="peitolm@g.o">Colin Morey</mail> |
85 |
</author> |
86 |
<author title="Editor"> |
87 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
88 |
</author> |
89 |
<author title="Editor"> |
90 |
<mail link="carl@g.o">Carl Anderson</mail> |
91 |
</author> |
92 |
<author title="Editor"> |
93 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
94 |
</author> |
95 |
<author title="Editor"> |
96 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
97 |
</author> |
98 |
<author title="Editor"> |
99 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
100 |
</author> |
101 |
<author title="Editor"> |
102 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
103 |
</author> |
104 |
<author title="Editor"> |
105 |
<mail link="erwin@g.o">Erwin</mail> |
106 |
</author> |
107 |
<author title="Editor"> |
108 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
109 |
</author> |
110 |
<author title="Reviewer"> |
111 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
112 |
</author> |
113 |
<author title="Reviewer"> |
114 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
115 |
</author> |
116 |
<author title="Reviewer"> |
117 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
118 |
</author> |
119 |
<author title="Reviewer"> |
120 |
<mail link="antifa@g.o">Ken Nowack</mail> |
121 |
</author> |
122 |
<author title="Contributor"> |
123 |
<mail link="pylon@g.o">Lars Weiler</mail> |
124 |
</author> |
125 |
<author title="Editor"> |
126 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
127 |
</author> |
128 |
|
129 |
<abstract> |
130 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux |
131 |
information. |
132 |
</abstract> |
133 |
|
134 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
135 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
136 |
<license/> |
137 |
|
138 |
<version>5.0</version> |
139 |
<date>2005-08-08</date> |
140 |
|
141 |
<part> |
142 |
<title>Installing Gentoo</title> |
143 |
<abstract> |
144 |
In this part you learn how to install Gentoo on your system. |
145 |
</abstract> |
146 |
|
147 |
<chapter> |
148 |
<title>About the Gentoo Linux Installation</title> |
149 |
<abstract> |
150 |
Users not familiar with Gentoo do not always know that choice is what |
151 |
Gentoo is all about. |
152 |
</abstract> |
153 |
<include href="hb-install-about.xml"/> |
154 |
</chapter> |
155 |
|
156 |
<chapter> |
157 |
<title>Booting the Universal Installation CD</title> |
158 |
<abstract> |
159 |
Using our Universal Installation CD you can boot up your system into a running |
160 |
environment that allows you to install Gentoo. |
161 |
</abstract> |
162 |
<include href="hb-install-ppc64-medium.xml"/> |
163 |
</chapter> |
164 |
|
165 |
<chapter> |
166 |
<title>Configuring your Network</title> |
167 |
<abstract> |
168 |
If you need networking, this is the place where the network (and Internet |
169 |
connection) is configured. |
170 |
</abstract> |
171 |
<include href="hb-install-network.xml"/> |
172 |
</chapter> |
173 |
|
174 |
<chapter> |
175 |
<title>Preparing the Disks</title> |
176 |
<abstract> |
177 |
To be able to install Gentoo, you must create the necessary partitions. |
178 |
This chapter describes how to partition a disk for future usage. |
179 |
</abstract> |
180 |
<include href="hb-install-ppc64-disk.xml"/> |
181 |
</chapter> |
182 |
|
183 |
<chapter> |
184 |
<title>Installing the Gentoo Installation Files</title> |
185 |
<abstract> |
186 |
In this chapter we describe how you extract a stage3 file and how to configure |
187 |
Portage. |
188 |
</abstract> |
189 |
<include href="hb-install-stage.xml"/> |
190 |
</chapter> |
191 |
|
192 |
<chapter> |
193 |
<title>Chrooting into the Gentoo Base System</title> |
194 |
<abstract> |
195 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
196 |
the USE variable. |
197 |
</abstract> |
198 |
<include href="hb-install-system.xml"/> |
199 |
</chapter> |
200 |
|
201 |
<chapter> |
202 |
<title>Configuring the Kernel</title> |
203 |
<abstract> |
204 |
The Linux kernel is the core of every distribution. This chapter |
205 |
explains how to configure your kernel. |
206 |
</abstract> |
207 |
<include href="hb-install-ppc64-kernel.xml"/> |
208 |
</chapter> |
209 |
|
210 |
<chapter> |
211 |
<title>Configuring your System</title> |
212 |
<abstract> |
213 |
You need to edit some important configuration files. In this chapter |
214 |
you receive an overview of these files and an explanation on how to |
215 |
proceed. |
216 |
</abstract> |
217 |
<include href="hb-install-config.xml"/> |
218 |
|
219 |
|
220 |
|
221 |
1.1 xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-bootloader.xml |
222 |
|
223 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
224 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
225 |
|
226 |
Index: hb-install-ppc64-bootloader.xml |
227 |
=================================================================== |
228 |
<?xml version='1.0' encoding='UTF-8'?> |
229 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
230 |
|
231 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
232 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
233 |
|
234 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-bootloader.xml,v 1.1 2005/08/08 13:21:15 swift Exp $ --> |
235 |
|
236 |
<sections> |
237 |
|
238 |
<version>5.0</version> |
239 |
<date>2005-08-08</date> |
240 |
|
241 |
<section> |
242 |
<title>Making your Choice</title> |
243 |
<subsection> |
244 |
<title>Introduction</title> |
245 |
<body> |
246 |
|
247 |
<p> |
248 |
Now that your kernel is configured and compiled and the necessary system |
249 |
configuration files are filled in correctly, it is time to install a |
250 |
program that will fire up your kernel when you start the system. Such a |
251 |
program is called a <e>bootloader</e>. |
252 |
</p> |
253 |
|
254 |
<p> |
255 |
On Linux/PPC64 we have only yaBoot as a bootloader untill grub2 is |
256 |
finished. |
257 |
</p> |
258 |
|
259 |
</body> |
260 |
</subsection> |
261 |
</section> |
262 |
<section id="yaboot"> |
263 |
<title>Using yaBoot</title> |
264 |
<subsection> |
265 |
<title>Introduction</title> |
266 |
<body> |
267 |
|
268 |
<impo> |
269 |
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't |
270 |
compile on 64bit userland systems. For a 32bit userland use yaboot as you |
271 |
normally would. |
272 |
</impo> |
273 |
|
274 |
<p> |
275 |
There are two ways to configure yaBoot for your system. You can use the |
276 |
new and improved <c>yabootconfig</c> included with |
277 |
<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If |
278 |
for some reason you do not want to run <c>yabootconfig</c> to |
279 |
automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo |
280 |
on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit |
281 |
the sample file already installed on your system. |
282 |
</p> |
283 |
|
284 |
<impo> |
285 |
If you are installing on a G5 using an online install and have not used the |
286 |
G5 optimized stages you must change what profile you are linked to now. If you |
287 |
do not you will not get dependencies necessary for yaboot to run on Apple |
288 |
equipment. In the command below replace <c>(userland)</c> with your chosen |
289 |
userland bit level. If you are installing on a G5 using an offline install |
290 |
you have to install these packages by hand. |
291 |
</impo> |
292 |
|
293 |
<pre caption = "(ONLINE INSTALL FOR G5 USERS ONLY) Changing your profile"> |
294 |
# <i>rm /etc/make.profile</i> |
295 |
# <i>ln -sf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/970/pmac /etc/make.profile</i> |
296 |
</pre> |
297 |
|
298 |
<pre caption = "(OFFLINE INSTALL FOR G5 USERS ONLY) Installing Necessary File System Tools"> |
299 |
# <i>emerge hfsutils hfsplusutils</i> |
300 |
</pre> |
301 |
|
302 |
<pre caption = "Installing the bootloader"> |
303 |
<comment>(64bit userland)</comment> |
304 |
# <i>emerge --update yaboot-static</i> |
305 |
<comment>(32bit userland)</comment> |
306 |
# <i>emerge --update yaboot</i> |
307 |
</pre> |
308 |
|
309 |
<impo> |
310 |
yabootconfig/ybin won't work on IBM. You have to install yaboot another way: |
311 |
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri> |
312 |
</impo> |
313 |
|
314 |
<note> |
315 |
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a |
316 |
kernel parameter. JFS must be able to replay its log in read-only mode before it |
317 |
gets mounted read-write. |
318 |
</note> |
319 |
|
320 |
<ul> |
321 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
322 |
<li> |
323 |
<uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri> |
324 |
</li> |
325 |
</ul> |
326 |
|
327 |
</body> |
328 |
</subsection> |
329 |
<subsection id="yabootconfig"> |
330 |
<title>Default: Using yabootconfig</title> |
331 |
<body> |
332 |
|
333 |
<p> |
334 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
335 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS |
336 |
X. |
337 |
</p> |
338 |
|
339 |
<p> |
340 |
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and |
341 |
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of |
342 |
these should have been done already in the steps above. To start, ensure that |
343 |
you have the latest version of yaboot installed by running <c>emerge --update |
344 |
yaboot-static</c>. This is necessary as the latest version will be available via |
345 |
Portage, but it may not have made it into the stage files. |
346 |
</p> |
347 |
|
348 |
<p> |
349 |
Now run <c>yabootconfig</c>. The program will run and it will confirm |
350 |
the location of the bootstrap partition. Type <c>Y</c> if it is correct. If |
351 |
not, double check <path>/etc/fstab</path>. yabootconfig will then scan your |
352 |
system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for |
353 |
you. <c>mkofboot</c> is used to format the bootstrap partition, and install |
354 |
the yaboot configuration file into it. |
355 |
</p> |
356 |
|
357 |
<p> |
358 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If |
359 |
you make changes to <path>/etc/yaboot.conf</path> (like setting the |
360 |
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the |
361 |
bootstrap partition. |
362 |
</p> |
363 |
|
364 |
<p> |
365 |
Now continue with <uri link="#reboot">Rebooting your System</uri>. |
366 |
</p> |
367 |
|
368 |
</body> |
369 |
</subsection> |
370 |
<subsection id="manual_yaboot"> |
371 |
<title>Alternative: Manual yaBoot Configuration</title> |
372 |
<body> |
373 |
|
374 |
<p> |
375 |
Below you find a completed <path>yaboot.conf</path> file. Alter it at |
376 |
will. |
377 |
</p> |
378 |
|
379 |
<pre caption = "/etc/yaboot.conf"> |
380 |
<comment>## /etc/yaboot.conf |
381 |
## |
382 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
383 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
384 |
## |
385 |
## For a dual-boot menu, add one or more of: |
386 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
387 |
|
388 |
## our bootstrap partition:</comment> |
389 |
|
390 |
boot=/dev/hda2 |
391 |
|
392 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
393 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
394 |
## you pass the necessary arguments to the mkofboot/ybin program). |
395 |
## hd:X means /dev/sdaX (or /dev/hdaX).</comment> |
396 |
|
397 |
ofboot=hd:2 |
398 |
|
399 |
<comment>## hd: is open firmware speak for hda</comment> |
400 |
device=hd: |
401 |
|
402 |
delay=5 |
403 |
defaultos=macosx |
404 |
timeout=30 |
405 |
install=/usr/lib/yaboot/yaboot |
406 |
magicboot=/usr/lib/yaboot/ofboot |
407 |
|
408 |
<comment>################# |
409 |
## This section can be duplicated if you have more than one kernel or set of |
410 |
## boot options - replace 2.6.12-gentoo-r4 with your kernel-version |
411 |
#################</comment> |
412 |
image=/boot/kernel-2.6.12-gentoo-r4 |
413 |
label=Linux |
414 |
root=/dev/hda3 |
415 |
partition=3 |
416 |
read-only |
417 |
|
418 |
macos=hd:13 |
419 |
macosx=hd:12 |
420 |
enablecdboot |
421 |
enableofboot |
422 |
</pre> |
423 |
|
424 |
<p> |
425 |
Once <path>yaboot.conf</path> is set up the way you want it, you run |
426 |
<c>mkofboot -v</c> to install the settings in the bootstrap partition. |
427 |
|
428 |
|
429 |
|
430 |
1.1 xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-disk.xml |
431 |
|
432 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
433 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
434 |
|
435 |
Index: hb-install-ppc64-disk.xml |
436 |
=================================================================== |
437 |
<?xml version='1.0' encoding='UTF-8'?> |
438 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
439 |
|
440 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
441 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
442 |
|
443 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-disk.xml,v 1.1 2005/08/08 13:21:15 swift Exp $ --> |
444 |
|
445 |
<sections> |
446 |
|
447 |
<version>5.0</version> |
448 |
<date>2005-08-08</date> |
449 |
|
450 |
<section> |
451 |
<title>Introduction to Block Devices</title> |
452 |
<subsection> |
453 |
<title>Block Devices</title> |
454 |
<body> |
455 |
|
456 |
<p> |
457 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
458 |
and Linux in general, including Linux filesystems, partitions and block devices. |
459 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
460 |
you'll be guided through the process of setting up partitions and filesystems |
461 |
for your Gentoo Linux installation. |
462 |
</p> |
463 |
|
464 |
<p> |
465 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
466 |
probably the one that represents the first IDE drive in a Linux system, namely |
467 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
468 |
drive would be <path>/dev/sda</path>. Serial ATA drives are also |
469 |
<path>/dev/sda</path> even if they are IDE drives. |
470 |
</p> |
471 |
|
472 |
<p> |
473 |
The block devices above represent an abstract interface to the disk. User |
474 |
programs can use these block devices to interact with your disk without worrying |
475 |
about whether your drives are IDE, SCSI or something else. The program can |
476 |
simply address the storage on the disk as a bunch of contiguous, |
477 |
randomly-accessible 512-byte blocks. |
478 |
</p> |
479 |
|
480 |
</body> |
481 |
</subsection> |
482 |
<subsection> |
483 |
<title>Partitions and Slices</title> |
484 |
<body> |
485 |
|
486 |
<p> |
487 |
Although it is theoretically possible to use a full disk to house your Linux |
488 |
system, this is almost never done in practice. Instead, full disk block devices |
489 |
are split up in smaller, more manageable block devices. On most systems, |
490 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
491 |
called <e>slices</e>. |
492 |
</p> |
493 |
|
494 |
</body> |
495 |
</subsection> |
496 |
</section> |
497 |
<section> |
498 |
<title>Designing a Partitioning Scheme</title> |
499 |
<subsection> |
500 |
<title>Default Partitioning Scheme</title> |
501 |
<body> |
502 |
|
503 |
<p> |
504 |
If you are not interested in drawing up a partitioning scheme for your system, |
505 |
you can use the partitioning scheme we use throughout this book: |
506 |
</p> |
507 |
|
508 |
<table> |
509 |
<tr> |
510 |
<th>Partition</th> |
511 |
<th>Filesystem</th> |
512 |
<th>Size</th> |
513 |
<th>Description</th> |
514 |
</tr> |
515 |
<tr> |
516 |
<ti><path>/dev/sda1</path></ti> |
517 |
<ti>Partition map</ti> |
518 |
<ti>31.5k</ti> |
519 |
<ti>Partition map</ti> |
520 |
</tr> |
521 |
<tr> |
522 |
<ti><path>/dev/sda2</path></ti> |
523 |
<ti>(bootstrap)</ti> |
524 |
<ti>800k</ti> |
525 |
<ti>Apple_Bootstrap</ti> |
526 |
</tr> |
527 |
<tr> |
528 |
<ti><path>/dev/sda3</path></ti> |
529 |
<ti>(swap)</ti> |
530 |
<ti>512M</ti> |
531 |
<ti>Swap partition</ti> |
532 |
</tr> |
533 |
<tr> |
534 |
<ti><path>/dev/sda4</path></ti> |
535 |
<ti>ext3</ti> |
536 |
<ti>Rest of the disk</ti> |
537 |
<ti>Root partition</ti> |
538 |
</tr> |
539 |
</table> |
540 |
|
541 |
<note> |
542 |
There are some partitions named like this: <path>Apple_Driver43, |
543 |
Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, |
544 |
Apple_Patches</path>. If you are not planning to use MacOS 9 you can |
545 |
delete them, because MacOS X and Linux don't need them. |
546 |
You might have to use parted in order to delete them, as mac-fdisk can't delete them yet. |
547 |
</note> |
548 |
|
549 |
<p> |
550 |
If you are interested in knowing how big a partition should be, or even how |
551 |
many partitions you need, read on. Otherwise continue now with |
552 |
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your |
553 |
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition |
554 |
your Disk</uri> |
555 |
</p> |
556 |
|
557 |
</body> |
558 |
</subsection> |
559 |
<subsection> |
560 |
<title>How Many and How Big?</title> |
561 |
<body> |
562 |
|
563 |
<p> |
564 |
The number of partitions is highly dependent on your environment. For instance, |
565 |
if you have lots of users, you will most likely want to have your |
566 |
<path>/home</path> separate as it increases security and makes backups easier. |
567 |
If you are installing Gentoo to perform as a mailserver, your |
568 |
<path>/var</path> should be separate as all mails are stored inside |
569 |
<path>/var</path>. A good choice of filesystem will then maximise your |
570 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
571 |
servers are installed there. The reason is similar for <path>/home</path>: |
572 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
573 |
not only will it contain the majority of applications, the Portage tree alone |
574 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
575 |
</p> |
576 |
|
577 |
<p> |
578 |
As you can see, it very much depends on what you want to achieve. Separate |
579 |
partitions or volumes have the following advantages: |
580 |
</p> |
581 |
|
582 |
<ul> |
583 |
<li> |
584 |
You can choose the best performing filesystem for each partition or volume |
585 |
</li> |
586 |
<li> |
587 |
Your entire system cannot run out of free space if one defunct tool is |
588 |
continuously writing files to a partition or volume |
589 |
</li> |
590 |
<li> |
591 |
If necessary, file system checks are reduced in time, as multiple checks can |
592 |
be done in parallel (although this advantage is more with multiple disks than |
593 |
it is with multiple partitions) |
594 |
</li> |
595 |
<li> |
596 |
Security can be enhanced by mounting some partitions or volumes read-only, |
597 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
598 |
</li> |
599 |
</ul> |
600 |
|
601 |
<p> |
602 |
However, multiple partitions have one big disadvantage: if not configured |
603 |
properly, you might result in having a system with lots |
604 |
of free space on one partition and none on another. There is also a 15-partition |
605 |
limit for SCSI and SATA. |
606 |
</p> |
607 |
|
608 |
</body> |
609 |
</subsection> |
610 |
</section> |
611 |
<section id="mac-fdisk"> |
612 |
<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title> |
613 |
<body> |
614 |
|
615 |
<p> |
616 |
At this point, create your partitions using <c>mac-fdisk</c>: |
617 |
</p> |
618 |
|
619 |
<pre caption="Starting mac-fdisk"> |
620 |
# <i>mac-fdisk /dev/sda</i> |
621 |
</pre> |
622 |
|
623 |
<p> |
624 |
First delete the partitions you have cleared previously to make room for your |
625 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
626 |
It will ask for the partition number to delete. |
627 |
</p> |
628 |
|
629 |
<p> |
630 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
631 |
ask for what block you want to start. Enter the number of your first free |
632 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
633 |
</p> |
634 |
|
635 |
<note> |
636 |
|
637 |
|
638 |
|
639 |
1.1 xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-kernel.xml |
640 |
|
641 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
642 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
643 |
|
644 |
Index: hb-install-ppc64-kernel.xml |
645 |
=================================================================== |
646 |
<?xml version='1.0' encoding='UTF-8'?> |
647 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
648 |
|
649 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
650 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
651 |
|
652 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-kernel.xml,v 1.1 2005/08/08 13:21:15 swift Exp $ --> |
653 |
|
654 |
<sections> |
655 |
|
656 |
<version>5.0</version> |
657 |
<date>2005-08-08</date> |
658 |
|
659 |
<section> |
660 |
<title>Timezone</title> |
661 |
<body> |
662 |
|
663 |
<p> |
664 |
You first need to select your timezone so that your system knows where |
665 |
it is located. Look for your timezone in |
666 |
<path>/usr/share/zoneinfo</path>, then make a symlink to |
667 |
<path>/etc/localtime</path> using <c>ln</c>: |
668 |
</p> |
669 |
|
670 |
<pre caption="Setting the timezone information"> |
671 |
# <i>ls /usr/share/zoneinfo</i> |
672 |
<comment>(Suppose you want to use GMT)</comment> |
673 |
# <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i> |
674 |
</pre> |
675 |
|
676 |
</body> |
677 |
</section> |
678 |
<section> |
679 |
<title>Installing the Sources</title> |
680 |
<subsection> |
681 |
<title>Choosing a Kernel</title> |
682 |
<body> |
683 |
|
684 |
<p> |
685 |
The core around which all distributions are built is the Linux kernel. |
686 |
It is the layer between the user programs and your system hardware. |
687 |
Gentoo provides its users several possible kernel sources. A full |
688 |
listing with description is available at the <uri |
689 |
link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. |
690 |
</p> |
691 |
|
692 |
<p> |
693 |
For PPC64 you should use <c>gentoo-sources</c>. So let's continue with |
694 |
<c>emerge</c>'ing the kernel sources: |
695 |
</p> |
696 |
|
697 |
<pre caption="Installing a kernel source"> |
698 |
# <i>emerge gentoo-sources</i> |
699 |
</pre> |
700 |
|
701 |
<p> |
702 |
When you take a look in <path>/usr/src</path> you should see a symlink |
703 |
called <path>linux</path> pointing to your kernel source: |
704 |
</p> |
705 |
|
706 |
<pre caption="Viewing the kernel source symlink"> |
707 |
# <i>ls -l /usr/src/linux</i> |
708 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux |
709 |
-> linux-2.6.12-gentoo-r4 |
710 |
</pre> |
711 |
|
712 |
<p> |
713 |
If this isn't the case (i.e. the symlink points to a different kernel |
714 |
source) change the symlink before you continue: |
715 |
</p> |
716 |
|
717 |
<pre caption="Changing the kernel source symlink"> |
718 |
# <i>rm /usr/src/linux</i> |
719 |
# <i>cd /usr/src</i> |
720 |
# <i>ln -s linux-2.6.12-gentoo-r4 linux</i> |
721 |
</pre> |
722 |
|
723 |
<p> |
724 |
Now it is time to configure and compile your kernel source. There is the |
725 |
ability to use "genkernel" which would create a generic kernel like the |
726 |
ones used on the live cds, but it is not fully functional for PPC64 at |
727 |
the moment. |
728 |
</p> |
729 |
|
730 |
<p> |
731 |
Continue now with <uri link="#manual">Manual Configuration</uri>. |
732 |
</p> |
733 |
|
734 |
</body> |
735 |
</subsection> |
736 |
</section> |
737 |
<section id="manual"> |
738 |
<title>Manual Configuration</title> |
739 |
<subsection> |
740 |
<title>Introduction</title> |
741 |
<body> |
742 |
|
743 |
<p> |
744 |
Manually configuring a kernel is often seen as the most difficult procedure a |
745 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
746 |
couple of kernels you don't even remember that it was difficult ;) |
747 |
</p> |
748 |
|
749 |
<p> |
750 |
However, one thing <e>is</e> true: you must know your system when you |
751 |
configuring a kernel manually. Most information can be gathered by emerging |
752 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
753 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
754 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
755 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
756 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
757 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
758 |
uses (it might provide you with a nice hint on what to enable). |
759 |
</p> |
760 |
|
761 |
<p> |
762 |
Now go to your kernel source directory and execute <c>make |
763 |
menuconfig</c>. This will fire up an ncurses-based configuration menu. |
764 |
</p> |
765 |
|
766 |
<p> |
767 |
When compiling the kernel on a 32bit userland system add the following to |
768 |
the bottom of /etc/profile: |
769 |
</p> |
770 |
|
771 |
<pre caption="32bit userland make alias"> |
772 |
# <i>echo 'alias ppc64make="make ARCH=ppc64 CROSS_COMPILE=powerpc64-unknown-linux-gnu-"' >> /etc/profile</i> |
773 |
# <i>source /etc/profile</i> |
774 |
</pre> |
775 |
|
776 |
<pre caption="Invoking menuconfig"> |
777 |
# <i>cd /usr/src/linux</i> |
778 |
(64bit userland) # <i>make menuconfig</i> |
779 |
(32bit userland) # <i>ppc64make menuconfig</i> |
780 |
</pre> |
781 |
|
782 |
<p> |
783 |
You will be greeted with several configuration sections. We'll first |
784 |
list some options you must activate (otherwise Gentoo will not function, |
785 |
or not function properly without additional tweaks). |
786 |
</p> |
787 |
|
788 |
</body> |
789 |
</subsection> |
790 |
<subsection> |
791 |
<title>Activating Required Options</title> |
792 |
<body> |
793 |
|
794 |
<p> |
795 |
First of all, activate the use of development and experimental |
796 |
code/drivers. You need this, otherwise some very important code/drivers |
797 |
won't show up: |
798 |
</p> |
799 |
|
800 |
<pre caption="Selecting experimental code/drivers, General setup"> |
801 |
Code maturity level options ---> |
802 |
[*] Prompt for development and/or incomplete code/drivers |
803 |
General setup ---> |
804 |
[*] Support for hot-pluggable devices |
805 |
</pre> |
806 |
|
807 |
<p> |
808 |
Now go to <c>File Systems</c> and select support for the filesystems you |
809 |
use. <e>Don't</e> compile them as modules, otherwise your Gentoo system |
810 |
will not be able to mount your partitions. Also select <c>Virtual |
811 |
memory</c>, <c>/proc file system</c>, and <c>/dev/pts file system for |
812 |
Unix98 PTYs</c>: |
813 |
</p> |
814 |
|
815 |
<pre caption="Selecting necessary file systems"> |
816 |
File systems ---> |
817 |
[*] Virtual memory file system support (former shm fs) |
818 |
[*] /proc file system support |
819 |
[*] /dev/pts file system for Unix98 PTYs |
820 |
|
821 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
822 |
<*> Reiserfs support |
823 |
<*> Ext3 journalling file system support |
824 |
<*> JFS filesystem support |
825 |
<*> Second extended fs support |
826 |
<*> XFS filesystem support |
827 |
</pre> |
828 |
|
829 |
<note> |
830 |
You will find some of the mentioned options under <c>Pseudo |
831 |
filesystems</c> which is a subpart of <c>File systems</c>. |
832 |
</note> |
833 |
|
834 |
<p> |
835 |
If you are using PPPoE to connect to the Internet or you are using a |
836 |
dial-up modem, you will need the following options in the kernel (you |
837 |
will find the mentioned options under <c>Networking support</c> which is |
838 |
a subpart of <c>Device Drivers</c>): |
839 |
</p> |
840 |
|
841 |
<pre caption="Selecting PPPoE necessary drivers"> |
842 |
Network device support ---> |
843 |
<*> PPP (point-to-point protocol) support |
844 |
<*> PPP support for async serial ports |
845 |
|
846 |
|
847 |
|
848 |
1.1 xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-medium.xml |
849 |
|
850 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
851 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
852 |
|
853 |
Index: hb-install-ppc64-medium.xml |
854 |
=================================================================== |
855 |
<?xml version='1.0' encoding='UTF-8'?> |
856 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
857 |
|
858 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
859 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
860 |
|
861 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.1/hb-install-ppc64-medium.xml,v 1.1 2005/08/08 13:21:15 swift Exp $ --> |
862 |
|
863 |
<sections> |
864 |
|
865 |
<version>5.0</version> |
866 |
<date>2005-08-08</date> |
867 |
|
868 |
<section> |
869 |
<title>Hardware Requirements</title> |
870 |
<subsection> |
871 |
<title>Introduction</title> |
872 |
<body> |
873 |
|
874 |
<p> |
875 |
Before we start, we first list what hardware requirements you need to |
876 |
successfully install Gentoo on your box. |
877 |
</p> |
878 |
|
879 |
</body> |
880 |
</subsection> |
881 |
<subsection> |
882 |
<title>Hardware Requirements</title> |
883 |
<body> |
884 |
|
885 |
<table> |
886 |
<tr> |
887 |
<th>CPU</th> |
888 |
<ti>Any PowerPC64 CPU</ti> |
889 |
</tr> |
890 |
<tr> |
891 |
<th>Systems</th> |
892 |
<ti> |
893 |
IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower |
894 |
</ti> |
895 |
</tr> |
896 |
<tr> |
897 |
<th>Memory</th> |
898 |
<ti>64 MB</ti> |
899 |
</tr> |
900 |
<tr> |
901 |
<th>Diskspace</th> |
902 |
<ti>1.5 GB (excluding swap space)</ti> |
903 |
</tr> |
904 |
<tr> |
905 |
<th>Swap space</th> |
906 |
<ti>At least 256 MB</ti> |
907 |
</tr> |
908 |
</table> |
909 |
|
910 |
<p> |
911 |
For a full list of supported systems, please go to |
912 |
<uri>http://www.linuxppc64.org/hardware.shtml</uri>. |
913 |
</p> |
914 |
|
915 |
</body> |
916 |
</subsection> |
917 |
</section> |
918 |
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
919 |
<!-- START --> |
920 |
<section> |
921 |
<title>The Gentoo Universal Installation CD</title> |
922 |
<subsection> |
923 |
<title>Introduction</title> |
924 |
<body> |
925 |
|
926 |
<p> |
927 |
Gentoo Linux can be installed using one of three <e>stage</e> tarball files. A |
928 |
stage file is a tarball (compressed archive) that contains a minimal |
929 |
environment. |
930 |
</p> |
931 |
|
932 |
<p> |
933 |
The Gentoo/PPC64 team provides you with additional options at this point. |
934 |
You have the choice to use a 32bit or a 64bit userland; a full set of stages |
935 |
is provided for both options. |
936 |
</p> |
937 |
|
938 |
<ul> |
939 |
<li> |
940 |
A stage1 file contains nothing more than a compiler, Portage (Gentoo's |
941 |
software management system) and a couple of packages on which the |
942 |
compiler or Portage depends. |
943 |
</li> |
944 |
<li> |
945 |
A stage2 file contains a so-called bootstrapped system, a minimal |
946 |
environment from which one can start building all other necessary |
947 |
applications that make a Gentoo environment complete. |
948 |
</li> |
949 |
<li> |
950 |
A stage3 file contains a prebuilt minimal system which is almost fully |
951 |
deployable. It only lacks a few applications where you, the Gentoo user, |
952 |
needs to choose which one you want to install. |
953 |
</li> |
954 |
</ul> |
955 |
|
956 |
<p> |
957 |
We will opt for a stage3 installation throughout this document. If you want to |
958 |
perform a Gentoo installation using the stage1 or stage2 files, please use the |
959 |
installation instructions in the <uri |
960 |
link="/doc/en/handbook/handbook-ppc64.xml">Gentoo Handbook</uri>. They do |
961 |
require a working Internet connection though. |
962 |
</p> |
963 |
|
964 |
</body> |
965 |
</subsection> |
966 |
<subsection> |
967 |
<title>Gentoo Universal Installation CD</title> |
968 |
<body> |
969 |
|
970 |
<p> |
971 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
972 |
environment. It allows you to boot Linux from the CD. During the boot process |
973 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
974 |
Installation CDs are maintained by Gentoo developers. |
975 |
</p> |
976 |
|
977 |
<p> |
978 |
There currently are two Installation CDs available: |
979 |
</p> |
980 |
|
981 |
<ul> |
982 |
<li> |
983 |
The Universal Installation CD contains everything you need to install |
984 |
Gentoo. It provides stage3 files for common architectures, source code |
985 |
for the extra applications you need to choose from and, of course, the |
986 |
installation instructions for your architecture. |
987 |
</li> |
988 |
<li> |
989 |
The Minimal Installation CD contains only a minimal environment that allows |
990 |
you to boot up and configure your network so you can connect to the |
991 |
Internet. It does not contain any additional files and cannot be used |
992 |
during the current installation approach. |
993 |
</li> |
994 |
</ul> |
995 |
|
996 |
<p> |
997 |
Gentoo also provides a Package CD. This is no Installation CD but an additional |
998 |
resource that you can exploit during the installation of your Gentoo system. It |
999 |
contains prebuilt packages (the so-called GRP set) that allows you to easily |
1000 |
and quickly install additional applications immediately after the Gentoo |
1001 |
installation and right before you update your Portage tree. |
1002 |
</p> |
1003 |
|
1004 |
<p> |
1005 |
The use of the Package CD is covered later in this document. |
1006 |
</p> |
1007 |
|
1008 |
</body> |
1009 |
</subsection> |
1010 |
</section> |
1011 |
<!-- STOP --> |
1012 |
<section> |
1013 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
1014 |
<subsection> |
1015 |
<title>Downloading and Burning the Installation CDs</title> |
1016 |
<body> |
1017 |
|
1018 |
<p> |
1019 |
You can download the Universal Installation CD (and, if you want to, the |
1020 |
Packages CD as well) from one of our <uri |
1021 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
1022 |
in the <path>releases/ppc/2005.1/ppc64/installcd</path> directory; |
1023 |
the Package CDs are located in the <path>releases/ppc/2005.1/ppc64/packagecd</path> |
1024 |
directory. |
1025 |
</p> |
1026 |
|
1027 |
<p> |
1028 |
Inside those directories you'll find so-called ISO-files. Those are full CD |
1029 |
images which you can write on a CD-R. |
1030 |
</p> |
1031 |
|
1032 |
<p> |
1033 |
After downloading the file, you can verify its integrity to see if it is |
1034 |
corrupted or not: |
1035 |
</p> |
1036 |
|
1037 |
<ul> |
1038 |
<li> |
1039 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
1040 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
1041 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). How |
1042 |
to verify MD5 checksums with Mac OS X is described in the <uri |
1043 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
1044 |
</li> |
1045 |
<li> |
1046 |
You can verify the cryptographic signature that we provide. You need to |
1047 |
obtain the public key we use (0x17072058) before you proceed though. |
1048 |
</li> |
1049 |
</ul> |
1050 |
|
1051 |
<p> |
1052 |
To fetch our public key using the GnuPG application, run the following command: |
1053 |
</p> |
1054 |
|
1055 |
|
1056 |
|
1057 |
-- |
1058 |
gentoo-doc-cvs@g.o mailing list |