1 |
josejx 05/07/28 16:42:03 |
2 |
|
3 |
Modified: xml/htdocs/doc/en/handbook/draft/2005.1 |
4 |
hb-install-ppc-bootloader.xml |
5 |
hb-install-ppc-disk.xml hb-install-ppc-medium.xml |
6 |
Log: |
7 |
Yoswink, please don't stab me. (PPC 2005.1 handbook updates.) |
8 |
|
9 |
Revision Changes Path |
10 |
1.2 +195 -51 xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml |
11 |
|
12 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
13 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo |
14 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo |
15 |
|
16 |
Index: hb-install-ppc-bootloader.xml |
17 |
=================================================================== |
18 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml,v |
19 |
retrieving revision 1.1 |
20 |
retrieving revision 1.2 |
21 |
diff -u -r1.1 -r1.2 |
22 |
--- hb-install-ppc-bootloader.xml 5 Jul 2005 08:02:04 -0000 1.1 |
23 |
+++ hb-install-ppc-bootloader.xml 28 Jul 2005 16:42:03 -0000 1.2 |
24 |
@@ -4,7 +4,7 @@ |
25 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
26 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
27 |
|
28 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml,v 1.1 2005/07/05 08:02:04 swift Exp $ --> |
29 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-bootloader.xml,v 1.2 2005/07/28 16:42:03 josejx Exp $ --> |
30 |
|
31 |
<sections> |
32 |
|
33 |
@@ -12,25 +12,23 @@ |
34 |
<date>2005-03-19</date> |
35 |
|
36 |
<section> |
37 |
-<title>Making your Choice</title> |
38 |
+<title>Choosing a Bootloader</title> |
39 |
<subsection> |
40 |
<title>Introduction</title> |
41 |
<body> |
42 |
|
43 |
<p> |
44 |
-Now that your kernel is configured and compiled and the necessary system |
45 |
-configuration files are filled in correctly, it is time to install a |
46 |
-program that will fire up your kernel when you start the system. Such a |
47 |
-program is called a <e>bootloader</e>. But before you start, consider |
48 |
-your options... |
49 |
+Now that the kernel is configured and compiled, you'll need a <e>bootloader</e> |
50 |
+to start your new linux installation. The <e>bootloader</e> that you use will |
51 |
+depend upon the type of PPC machine you have. |
52 |
</p> |
53 |
|
54 |
<p> |
55 |
-Several bootloaders exist for Linux/PPC. We have <uri link="#yaboot">yaboot</uri> |
56 |
-(for NewWorld Apple and IBM machines) and <uri link="#bootx">BootX</uri> (for |
57 |
-OldWorld Apple and IBM machines). The Pegasos does not require a bootloader, but |
58 |
-we included the <uri link="#bootcreator">BootCreator</uri> for creating a |
59 |
-SmartFirmware bootmenu. |
60 |
+If you are using a NewWorld Apple or IBM machine, you need to use |
61 |
+<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options, |
62 |
+<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>. |
63 |
+The Pegasos does not require a bootloader, but you will need to emerge |
64 |
+<uri link="#bootcreator">BootCreator</uri> to create SmartFirmware bootmenus. |
65 |
</p> |
66 |
|
67 |
</body> |
68 |
@@ -47,9 +45,9 @@ |
69 |
</impo> |
70 |
|
71 |
<p> |
72 |
-First we have to create the <path>/dev</path> files in our new home, which is |
73 |
-needed during the bootloader installation. This could be done by "bind"-mapping |
74 |
-the <path>/dev</path>-filesystem from the Installation CD: |
75 |
+In order to find the boot devices, yaboot needs access to the <path>/dev</path> |
76 |
+filesystem. To do this, you will need to "bind-map" the <path>/dev</path> |
77 |
+filesystem from the Installation CD to <path>/dev</path> inside of the chroot. |
78 |
</p> |
79 |
|
80 |
<pre caption="Bind-mounting the /dev-filesystem"> |
81 |
@@ -60,14 +58,35 @@ |
82 |
</pre> |
83 |
|
84 |
<p> |
85 |
-There are two ways to configure yaboot for your system. You can use the |
86 |
-included <c>yabootconfig</c> to automatically set up yaboot. If |
87 |
-for some reason you do not want to run <c>yabootconfig</c> to |
88 |
-automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo |
89 |
-on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit |
90 |
-the sample file already installed on your system. |
91 |
+To set up yaboot, you can use <c>yabootconfig</c> to automatically create a |
92 |
+configuration file for you. If you are installing Gentoo on a G5 (where |
93 |
+<c>yabootconfig</c> does not always work), or you plan to boot from firewire |
94 |
+or USB, you will need to manually configure yaboot. |
95 |
</p> |
96 |
|
97 |
+<note> |
98 |
+You will need to manually edit the yaboot.conf when using genkernel, even if |
99 |
+yabootconfig is used. The kernel image section of yaboot.conf should be |
100 |
+modified as follows: |
101 |
+</note> |
102 |
+ |
103 |
+<pre caption="Adding genkernel boot arguments to yaboot.conf"> |
104 |
+<comment>########################################################### |
105 |
+## This section can be duplicated if you have more than one |
106 |
+## kernel or set of boot options - replace kernel-2.6.12 |
107 |
+## with the exact filename of your kernel. |
108 |
+###########################################################</comment> |
109 |
+image=/boot/kernel-2.6.12 |
110 |
+ label=Linux |
111 |
+ root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment> |
112 |
+ partition=3 |
113 |
+ append="real_root=/dev/hda3 init=/linuxrc" |
114 |
+ <comment># You can add additional kernel arguments to append such as |
115 |
+ # rootdelay=10 for a USB/Firewire Boot</comment> |
116 |
+ read-only |
117 |
+<comment>##########################################################</comment> |
118 |
+</pre> |
119 |
+ |
120 |
<ul> |
121 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
122 |
<li> |
123 |
@@ -138,10 +157,10 @@ |
124 |
</pre> |
125 |
|
126 |
<p> |
127 |
-Below you find a completed <path>yaboot.conf</path> file. Alter it at |
128 |
-will. G5 users should be aware that their disks are Serial ATA disks which are |
129 |
-seen as SCSI disks by the Linux kernel (so substitute <path>/dev/hda</path> with |
130 |
-<path>/dev/sda</path>). |
131 |
+An example <path>yaboot.conf</path> file is given below, but you will need to |
132 |
+alter it to fit your needs. G5 users and users booting from firewire and USB |
133 |
+should be aware that their disks are seen as SCSI disks by the Linux kernel, so |
134 |
+you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>). |
135 |
</p> |
136 |
|
137 |
<pre caption = "/etc/yaboot.conf"> |
138 |
@@ -166,9 +185,21 @@ |
139 |
|
140 |
#ofboot=hd:2 |
141 |
|
142 |
-## hd: is open firmware speak for hda</comment> |
143 |
+## Users booting from firewire should use something like this line: |
144 |
+# ofboot=fw/node/sbp-2/disk@0: |
145 |
+ |
146 |
+## Users booting from USB should use something like this line: |
147 |
+# ofboot=usb/disk@0: |
148 |
+ |
149 |
+## hd: is shorthand for the first hard drive OpenFirmware sees</comment> |
150 |
device=hd: |
151 |
|
152 |
+<comment>## Firewire and USB users will need to specify the whole OF device name |
153 |
+## This can be found using ofpath, which is included with yaboot. |
154 |
+ |
155 |
+# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0: |
156 |
+</comment> |
157 |
+ |
158 |
delay=5 |
159 |
defaultos=macosx |
160 |
timeout=30 |
161 |
@@ -183,7 +214,7 @@ |
162 |
label=Linux |
163 |
root=/dev/hda3 |
164 |
partition=3 |
165 |
- sysmap=/boot/System.map-2.6.9 |
166 |
+<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment> |
167 |
read-only |
168 |
<comment>################## |
169 |
|
170 |
@@ -198,17 +229,10 @@ |
171 |
</pre> |
172 |
|
173 |
<p> |
174 |
-Once <path>yaboot.conf</path> is set up the way you want it, you run |
175 |
-<c>mkofboot -v</c> to install the settings in the bootstrap partition. <e>Don't |
176 |
-forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new |
177 |
-filesystem. |
178 |
-</p> |
179 |
- |
180 |
-<p> |
181 |
-If all goes well, and you have the same options as the sample |
182 |
-above, your next reboot will give you a simple, five-entry boot menu. If you |
183 |
-update your yaboot config later on, you'll just need to run <c>ybin -v</c> to |
184 |
-update the bootstrap partition - <c>mkofboot</c> is for initial setup only. |
185 |
+Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format |
186 |
+the Apple_bootstrap partition and install the settings. If you change |
187 |
+yaboot.conf after the Apple_bootstrap partition has been created, you can |
188 |
+update the settings by running <c>ybin -v</c> |
189 |
</p> |
190 |
|
191 |
<p> |
192 |
@@ -226,22 +250,44 @@ |
193 |
<body> |
194 |
|
195 |
<impo> |
196 |
-BootX can only be used on OldWorld Apple and IBM systems! |
197 |
+BootX can only be used on OldWorld Apple systems! |
198 |
</impo> |
199 |
|
200 |
<p> |
201 |
-BootX requires that you reboot first. So, let's reboot shall we :) |
202 |
+Since BootX boots Linux from within MacOS, the kernel will need to be copied |
203 |
+from the Linux Partition to the MacOS partition. First, mount the MacOS |
204 |
+partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the |
205 |
+MacOS partition number, sda6 is used as an example here. Once the partition is |
206 |
+mounted, we'll copy the kernel to the system folder so BootX can find it. |
207 |
</p> |
208 |
|
209 |
+<pre caption="Copying the kernel to the MacOS partition"> |
210 |
+# <i>exit</i> |
211 |
+cdimage ~# <i>mkdir /mnt/mac</i> |
212 |
+cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
213 |
+cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i> |
214 |
+</pre> |
215 |
|
216 |
|
217 |
|
218 |
1.2 +24 -25 xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml |
219 |
|
220 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
221 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo |
222 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo |
223 |
|
224 |
Index: hb-install-ppc-disk.xml |
225 |
=================================================================== |
226 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml,v |
227 |
retrieving revision 1.1 |
228 |
retrieving revision 1.2 |
229 |
diff -u -r1.1 -r1.2 |
230 |
--- hb-install-ppc-disk.xml 5 Jul 2005 08:02:04 -0000 1.1 |
231 |
+++ hb-install-ppc-disk.xml 28 Jul 2005 16:42:03 -0000 1.2 |
232 |
@@ -4,7 +4,7 @@ |
233 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
234 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
235 |
|
236 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml,v 1.1 2005/07/05 08:02:04 swift Exp $ --> |
237 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-disk.xml,v 1.2 2005/07/28 16:42:03 josejx Exp $ --> |
238 |
|
239 |
<sections> |
240 |
|
241 |
@@ -43,15 +43,14 @@ |
242 |
</body> |
243 |
</subsection> |
244 |
<subsection> |
245 |
-<title>Partitions and Slices</title> |
246 |
+<title>Partitions</title> |
247 |
<body> |
248 |
|
249 |
<p> |
250 |
Although it is theoretically possible to use a full disk to house your Linux |
251 |
system, this is almost never done in practice. Instead, full disk block devices |
252 |
are split up in smaller, more manageable block devices. On most systems, |
253 |
-these are called <e>partitions</e>. Other architectures use a similar technique, |
254 |
-called <e>slices</e>. |
255 |
+these are called <e>partitions</e>. |
256 |
</p> |
257 |
|
258 |
</body> |
259 |
@@ -106,8 +105,8 @@ |
260 |
<ti>Type 0x41</ti> |
261 |
</tr> |
262 |
<tr> |
263 |
- <ti>(Not needed)</ti> |
264 |
- <ti>(Not needed)</ti> |
265 |
+ <ti>(Not applicable)</ti> |
266 |
+ <ti><path>/dev/hda2</path> (If using quik)</ti> |
267 |
<ti><path>/dev/hda1</path></ti> |
268 |
<ti>(Not needed)</ti> |
269 |
<ti>ext2</ti> |
270 |
@@ -116,7 +115,7 @@ |
271 |
</tr> |
272 |
<tr> |
273 |
<ti><path>/dev/hda3</path></ti> |
274 |
- <ti><path>/dev/hda2</path></ti> |
275 |
+ <ti><path>/dev/hda2</path> (<path>/dev/hda3</path> if using quik)</ti> |
276 |
<ti><path>/dev/hda2</path></ti> |
277 |
<ti><path>/dev/sda2</path></ti> |
278 |
<ti>(swap)</ti> |
279 |
@@ -125,7 +124,7 @@ |
280 |
</tr> |
281 |
<tr> |
282 |
<ti><path>/dev/hda4</path></ti> |
283 |
- <ti><path>/dev/hda3</path></ti> |
284 |
+ <ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti> |
285 |
<ti><path>/dev/hda3</path></ti> |
286 |
<ti><path>/dev/sda3</path></ti> |
287 |
<ti>ext3, xfs</ti> |
288 |
@@ -135,11 +134,11 @@ |
289 |
</table> |
290 |
|
291 |
<note> |
292 |
-There are some partitions named like this: <path>Apple_Driver43, |
293 |
-Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If |
294 |
-you are not planning to use MacOS 9 you can delete them, because MacOS X and |
295 |
-Linux don't need them. You might have to use <c>parted</c> in order to delete |
296 |
-them, as mac-fdisk can't delete them yet. |
297 |
+There are some partitions named: <path>Apple_Driver63, Apple_Driver_ATA, |
298 |
+Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not |
299 |
+planning to use MacOS 9 you can delete them, because MacOS X and Linux don't |
300 |
+need them. To delete them, either use parted or erase the whole disk by |
301 |
+initialing the partition map. |
302 |
</note> |
303 |
|
304 |
<warn> |
305 |
@@ -152,9 +151,9 @@ |
306 |
|
307 |
<p> |
308 |
If you are interested in knowing how big a partition should be, or even how many |
309 |
-partitions you need, read on. Otherwise continue now with <uri |
310 |
-link="#fdisk">Default: Using mac-fdisk (Apple/IBM) to Partition your Disk</uri> |
311 |
-or <uri link="#parted">Alternative: Using parted (especially Pegasos) to |
312 |
+partitions you need, read on. Otherwise continue now with |
313 |
+<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk |
314 |
+</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to |
315 |
Partition your Disk</uri>. |
316 |
</p> |
317 |
|
318 |
@@ -212,7 +211,7 @@ |
319 |
</body> |
320 |
</subsection> |
321 |
</section> |
322 |
-<section id="fdisk"> |
323 |
+<section id="mac-fdisk"> |
324 |
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title> |
325 |
<body> |
326 |
|
327 |
@@ -372,9 +371,8 @@ |
328 |
<body> |
329 |
|
330 |
<p> |
331 |
-Several filesystems are available. ext2, ext3 and XFS are found stable on the |
332 |
-PPC architecture. jfs is unsupported, ReiserFS still has some problems on ppc |
333 |
-and is not supported. |
334 |
+Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found |
335 |
+stable on the PPC architecture. |
336 |
</p> |
337 |
|
338 |
<p> |
339 |
@@ -403,8 +401,7 @@ |
340 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
341 |
solid and usable as both general-purpose filesystem and for extreme cases such |
342 |
as the creation of large filesystems, the use of many small files, very large |
343 |
-files and directories containing tens of thousands of files. Unfortunately we still have some |
344 |
-issues with ReiserFS on ppc. We do not encourage people to use this filesystem. |
345 |
+files and directories containing tens of thousands of files. |
346 |
</p> |
347 |
|
348 |
<p> |
349 |
@@ -466,9 +463,11 @@ |
350 |
</p> |
351 |
|
352 |
<note> |
353 |
-On OldWorld machines and the PegasosII your partition which holds the kernel must |
354 |
-be ext2 or ext3. NewWorld machines can boot from any of ext2, ext3, XFS, |
355 |
-ReiserFS or even HFS/HFS+ filesystems. |
356 |
+On the PegasosII your partition which holds the kernel must be ext2 or ext3. |
357 |
+NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or even |
358 |
+HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel must |
359 |
+be placed on an HFS partition, but this will be completed when you configure |
360 |
+your bootloader. |
361 |
</note> |
362 |
|
363 |
</body> |
364 |
|
365 |
|
366 |
|
367 |
1.3 +73 -28 xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml |
368 |
|
369 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
370 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo |
371 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo |
372 |
|
373 |
Index: hb-install-ppc-medium.xml |
374 |
=================================================================== |
375 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml,v |
376 |
retrieving revision 1.2 |
377 |
retrieving revision 1.3 |
378 |
diff -u -r1.2 -r1.3 |
379 |
--- hb-install-ppc-medium.xml 5 Jul 2005 09:07:02 -0000 1.2 |
380 |
+++ hb-install-ppc-medium.xml 28 Jul 2005 16:42:03 -0000 1.3 |
381 |
@@ -4,7 +4,7 @@ |
382 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
383 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
384 |
|
385 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml,v 1.2 2005/07/05 09:07:02 swift Exp $ --> |
386 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2005.1/hb-install-ppc-medium.xml,v 1.3 2005/07/28 16:42:03 josejx Exp $ --> |
387 |
|
388 |
<sections> |
389 |
|
390 |
@@ -30,16 +30,30 @@ |
391 |
|
392 |
<table> |
393 |
<tr> |
394 |
- <th>NewWorld machines</th> |
395 |
+ <th>Apple NewWorld Machines</th> |
396 |
<ti> |
397 |
Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook |
398 |
- PowerBook, Xserver, PowerMac, Genesi's Pegasos II |
399 |
+ PowerBook, Xserver, PowerMac |
400 |
</ti> |
401 |
</tr> |
402 |
<tr> |
403 |
- <th>OldWorld machines</th> |
404 |
+ <th>Apple OldWorld machines</th> |
405 |
<ti> |
406 |
- Limited support for IBM (RS/6000, iSeries, pSeries) and Amiga systems |
407 |
+ Apple Machines with an OpenFirmware revision less than 3, such as the Beige |
408 |
+ G3s, PCI PowerMacs and PCI PowerBooks. PCI based Apple Clones should also |
409 |
+ be supported. |
410 |
+ </ti> |
411 |
+</tr> |
412 |
+<tr> |
413 |
+ <th>Genesi's Pegasos</th> |
414 |
+ <ti> |
415 |
+ Pegasos I/II, Open Desktop Workstation |
416 |
+ </ti> |
417 |
+</tr> |
418 |
+<tr> |
419 |
+ <th>IBM</th> |
420 |
+ <ti> |
421 |
+ RS/6000, iSeries, pSeries |
422 |
</ti> |
423 |
</tr> |
424 |
<tr> |
425 |
@@ -182,8 +196,8 @@ |
426 |
<li> |
427 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
428 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
429 |
- <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). How |
430 |
- to verify MD5 checksums with Mac OS X is described in the <uri |
431 |
+ <uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). |
432 |
+ Verifying MD5 checksums with Mac OS X is described in the <uri |
433 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
434 |
</li> |
435 |
<li> |
436 |
@@ -231,7 +245,7 @@ |
437 |
</body> |
438 |
</subsection> |
439 |
<subsection> |
440 |
-<title>Default: Booting the Universal Installation CD on an Apple/IBM</title> |
441 |
+<title>Default: Booting the Installation CD with Yaboot</title> |
442 |
<body> |
443 |
|
444 |
<p> |
445 |
@@ -241,25 +255,6 @@ |
446 |
</p> |
447 |
|
448 |
<p> |
449 |
-If you have an OldWorld Mac the bootable portion of the Installation CD can't |
450 |
-be used. Instead you need to download <uri |
451 |
-link="http://penguinppc.org/projects/bootx/">BootX</uri> and have a working |
452 |
-MacOS installed on your system. You need to copy the <c>BootX Extension</c> from |
453 |
-the unpacked archive-file into the <c>Extensions Folder</c> and make a new |
454 |
-directory called <c>Linux Kernels</c> in the System Folder. In the next step you |
455 |
-need to copy the files <c>G3G4</c> and <c>G3G4.igz</c> from the |
456 |
-Installation CD <path>boot</path> folder into the <c>Linux Kernels</c> |
457 |
-directory. Then reboot the system and wait for BootX to load. After BootX |
458 |
-loaded you still have to set up a few items. In the options dialog you need |
459 |
-to check <c>Use Specified RAM Disk</c> and select the <c>G3G4.igz</c> |
460 |
-which you put in the <c>Linux Kernels</c> directory. The ramdisk size should |
461 |
-be set to at least <c>32000</c>. |
462 |
-Furthermore the kernel argument needs to be set to <c>rw init=/linuxrc |
463 |
-cdroot</c>. Eventually you are able to boot the Installation CD when you |
464 |
-select Linux on Startup. |
465 |
-</p> |
466 |
- |
467 |
-<p> |
468 |
After the Installation CD loaded, you will be greeted by a friendly welcome |
469 |
message and a <e>boot:</e> prompt at the bottom of the screen. |
470 |
</p> |
471 |
@@ -321,7 +316,7 @@ |
472 |
</body> |
473 |
</subsection> |
474 |
<subsection> |
475 |
-<title>Alternative: Booting the Universal Installation CD on a Pegasos</title> |
476 |
+<title>Alternative: Booting the Installation CD on a Pegasos</title> |
477 |
<body> |
478 |
|
479 |
<p> |
480 |
@@ -337,6 +332,56 @@ |
481 |
|
482 |
</body> |
483 |
</subsection> |
484 |
+ |
485 |
+<subsection> |
486 |
+<title>Alternative: Booting the Installation CD with BootX</title> |
487 |
+<body> |
488 |
+ |
489 |
+<p> |
490 |
+If you have an OldWorld Mac the bootable portion of the livecd can't be used. |
491 |
+The most simple solution is to use MacOS to bootstrap into a Linux environment |
492 |
+with a tool called BootX. Boot floppies are being prepared for Macs without |
493 |
+MacOS, but they are not available at this time. |
494 |
+</p> |
495 |
+ |
496 |
+<p> |
497 |
+First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri> |
498 |
+and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked |
499 |
+archive into <c>Extensions Folder</c> and the BootX App Control Panel into |
500 |
+<c>Control Panels</c>, both of which are located in your MacOS System Folder. |
501 |
+Next, create a folder called "Linux Kernels" in your System folder and copy the |
502 |
+<c>G3G4</c> kernel from the CD to this folder. Finally, copy <c>G3G4.igz</c> |
503 |
+from the Installation CD <path>boot</path> folder into the MacOS |
504 |
+<c>System Folder</c>. |
505 |
+</p> |
506 |
+ |
507 |
+<p> |
508 |
+To prepare BootX, start the BootX App Control Panel. First select the Options |
509 |
+dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from |
510 |
+your System Folder. Continue back to the initial screen and ensure that the |
511 |
+ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as |
512 |
+shown below: |
513 |
+</p> |
514 |
+ |
515 |
+<pre caption="BootX kernel arguments"> |
516 |
+cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev |
517 |
+</pre> |
518 |
+ |
519 |
+<note> |
520 |
+The kernel parameters in the yaboot section above are also applicable here. |
521 |
+</note> |
522 |
+ |
523 |
+<p> |
524 |
+Check once more to make sure the settings are correct and then save the |
525 |
+configuration. This saves typing just in case it doesn't boot or something is |
526 |
+missing. Press the Linux button at the top of the window to boot into the |
527 |
+Installation CD and continue with <uri link="#booted">And When |
528 |
+You're Booted...</uri> |
529 |
+</p> |
530 |
+ |
531 |
+</body> |
532 |
+</subsection> |
533 |
+ |
534 |
<subsection id="booted"> |
535 |
<title>And When You're Booted...</title> |
536 |
<body> |
537 |
|
538 |
|
539 |
|
540 |
-- |
541 |
gentoo-doc-cvs@g.o mailing list |