Attachment #79452 for bug #122406

Lines 101-106 Link Here

(-)2006.0.orig/handbook-ppc.xml (-2 / +5 lines)
101	<author title="Editor">	101	<author title="Editor">
102	<mail link="neysx@gentoo.org">Xavier Neys</mail>	102	<mail link="neysx@gentoo.org">Xavier Neys</mail>
103	</author>	103	</author>
		104	<author title="Editor">
		105	<mail link="josejx@gentoo.org">Joseph Jezak</mail>
		106	</author>
104	<author title="Reviewer">	107	<author title="Reviewer">
105	<mail link="g2boojum@gentoo.org">Grant Goodyear</mail>	108	<mail link="g2boojum@gentoo.org">Grant Goodyear</mail>
106	</author>	109	</author>
Lines 124-131 Link Here
124	<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->	127	<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
125	<license/>	128	<license/>
126		129
127	<version>5.2</version>	130	<version>5.3</version>
128	<date>2005-10-13</date>	131	<date>2006-02-09</date>
129		132
130	<part>	133	<part>
131	<title>Installing Gentoo</title>	134	<title>Installing Gentoo</title>





<sections>

<version>5.4</version>
<date>2006-02-09</date>

<section>
<title>Filesystem Information</title>

<p>
Let us take a look at how we write down the options for the <path>/boot</path>
partition. This is just an example, so if your architecture doesn't require a
<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it
verbatim.
</p>

<p>





<sections>

<version>5.4</version>
<date>2006-02-09</date>

<section>
<title>Choosing a Bootloader</title>

</impo>

<p>
In order to find the boot devices, yaboot needs access to the device nodes
created by udev on startup and the sysfs filesystem.  These two filesystems
are found at <path>/dev</path> and <path>sys</path> respectively.  To do this,
you will need to "bind mount" these filesystems from the Installation CD's root
to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot.
If you have already bind mounted these filesystems, there is no need to do it
again.
</p>

<pre caption="Bind-mounting the device and sysfs filesystems">
# <i>exit </i> # this will exit the chroot
# <i>mount -o bind /dev /mnt/gentoo/dev</i>
# <i>mount -o bind /sys /mnt/gentoo/sys</i>
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
</pre>


<p>
To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
and <path>/etc/fstab</path> must be configured to reflect your Linux 
partitions. These steps should have already been completed before, but check
<path>/etc/fstab</path> before proceeding.  Now, ensure that you have the 
latest <c>yaboot</c> installed.
</p>

<pre caption = "Installing yaboot with GRP">

</pre>

<p>
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First,
the program will confirm the location of the bootstrap partition.  If you are
using the suggested disk partitioning scheme, your bootstrap partition should
be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your
<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup, 
create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. 
<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install 
the yaboot configuration file into it.  After this enter the chroot again.
</p>

<pre caption="Re-enter the chroot">
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i>
</pre>

<body>

<p>
First make sure you have the latest <c>yaboot</c> installed on your system:
system:
</p>

<pre caption = "Installing yaboot">

page</uri> for more information.
</p>

<impo>
Make sure that you have support for HFS and HFS+ filesystems in your kernel,
otherwise you will not be able to upgrade or change the kernel on your MacOS 
partition.
</impo>

<p>
Now reboot again and boot into Linux, then continue with <uri
link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.

System</uri>.
</p>


</body>
</section>
<section id="reboot">





<sections>

<version>5.2</version>
<date>2006-02-09</date>

<section>
<title>Introduction to Block Devices</title>

</p>

<p>
To begin, we'll introduce <e>block devices</e>. The most common block device is
the one that represents the first IDE drive in a Linux system, namely
<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA 
drives, then your first hard drive would be <path>/dev/sda</path>.
</p>

<p>

  <ti>(Not applicable)</ti>
  <ti><path>/dev/hda2</path> (If using quik)</ti>
  <ti><path>/dev/hda1</path></ti>
  <ti>(Not applicable)</ti>
  <ti>ext2</ti>
  <ti>32MB</ti>
  <ti>Boot partition</ti>

Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not 
planning to use MacOS 9 you can delete them, because MacOS X and Linux don't 
need them.  To delete them, either use parted or erase the whole disk by 
initializing the partition map.
</note>

<warn>
<c>parted</c> is able to resize partitions including HFS+. Unfortunately it is
not possible to resize HFS+ journaled filesystems, so switch off journaling in
Mac OS X before resizing.  Remeber that any resizing operation is dangerous,
so attempt at your own risk!  Be sure to always have a backup of your data 
before resizing!
</warn>

<p>

also holds for <path>/var/tmp</path>.
</note>


<p>
We will have to mount the proc filesystem (a virtual interface with the
kernel) on <path>/proc</path>. But first we will need to place our files on the





<sections>

<version>5.5</version>
<date>2006-02-09</date>

<section>
<title>Timezone</title>

<p>
If you take a look in <path>/usr/src</path> you should see a symlink named
<path>linux</path> pointing to your current kernel source. In this case, the
installed kernel source points to <c>gentoo-sources-2.6.15</c>. Your version
may be different, so keep this in mind.
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -&gt; linux-2.6.15
</pre>

<p>


<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path> (be sure that it is mounted properly on Pegasos computers).
If you are using BootX to boot, we'll copy the kernel later.
</p>

<p>
Yaboot and BootX expect to use an uncompressed kernel unlike many other 
bootloaders.  The uncompressed kernel is called vmlinux and it is placed in
<path>/usr/src/linux</path> after the kernel has finished compiling.  If you
are using a Pegasos machine, the Pegasos firmware requires a compressed
kernel called zImage.chrp which can be found in 
<path>/usr/src/linux/arch/ppc/boot/images</path>.
</p>

<pre caption="Installing the kernel">
# <i>cd /usr/src/linux</i>
<comment>replace &lt;kernel-version&gt; with your kernel version</comment>
<comment>(Apple/IBM)</comment>
# <i>cp vmlinux /boot/&lt;kernel-version&gt;</i> 
<comment>(Pegasos)</comment>
# <i>cp arch/ppc/boot/images/zImage.chrp /boot/&lt;kernel-version&gt;</i> 
</pre>

<p>





<sections>

<version>5.4</version>
<date>2006-02-09</date>

<section>
<title>Hardware Requirements</title>

</table>

<p>
Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri>
for help with some common installation related issues or if you're unsure as to
just what's in that PowerPC machine you've got sitting on your desk right now.
</p>

</body>

</p>

<p>
We provide one generic kernel, <e>ppc32</e>. This kernel is built with support
for multiple CPUs, but it will boot on single processor machines as well.
support for multiple CPUs, but they will boot on single processor machines as
well.
</p>

<p>
You can tweak some kernel options at this prompt. The following table lists 
some of the available boot options you can add:
</p>

<table>

  <ti><c>video</c></ti>
  <ti>
    This option takes one of the following vendor-specific tags:
    <c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, 
    <c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution 
    refresh rate and color depth you want to use. For instance,
    <c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer
    at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of
    32 bits. If you are uncertain what to choose, and the default doesn't work,
    <c>video=ofonly</c> will most certainly work.
  </ti>
</tr>
<tr>

On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type
<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose
between several preconfigured video configs. If you need any special boot
options you can append them to the command-line just like with Yaboot above. 
For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.
The default kernel options (in case something goes wrong and you need it) are 
preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc 
looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>.
</p>


<p>
If you have an OldWorld Mac the bootable portion of the livecd can't be used.
The most simple solution is to use MacOS to bootstrap into a Linux environment
with a tool called BootX.  
MacOS, but they are not available at this time.
</p>

<p>

archive into <c>Extensions Folder</c> and the BootX App Control Panel into
<c>Control Panels</c>, both of which are located in your MacOS System Folder.
Next, create a folder called "Linux Kernels" in your System folder and copy the
<c>ppc32</c> kernel from the CD to this folder.  Finally, copy <c>ppc32.igz</c> 
from the Installation CD <path>boot</path> folder into the MacOS 
<c>System Folder</c>.
</p>

<p>
To prepare BootX, start the BootX App Control Panel.  First select the Options
dialog and check <c>Use Specified RAM Disk</c> and select <c>ppc32.igz</c> from
your System Folder.  Continue back to the initial screen and ensure that the
ramdisk size is at least <c>32000</c>.  Finally, set the kernel arguments as
shown below:

</pre>

<note>
The kernel parameters in the yaboot section above are also applicable here. You
can append any of those options to the kernel arguments above.
</note>

<p>
Check once more to make sure the settings are correct and then save the 
configuration.  This saves typing just in case it doesn't boot or something is
missing.  Press the Linux button at the top of the window.  If everything goes
correctly, it should boot into the Installation CD. Continue with 
<uri link="#booted">And When You're Booted...</uri>
</p>

</body>

<p>
You will be greeted by a root ("#") prompt on the current console. You can also 
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get 
back to the one you started on by pressing Alt-F1.  Due to the keyboard layout,
you may need to press Alt-fn-Fx on Apple machines.
</p>

<p>


<p>
In the next example we try to load the <c>airport</c> module.  This module
supports only the old Airport cards (802.11b).  Airport Extreme (802.11g) is not
supported on the InstallCD due to restrictions on firmware distribution.
</p>

<pre caption="Loading the airport module">
# <i>modprobe airport</i>
</pre>

<p>
On older iMacs, sometimes the network card is not detected properly.  These use
the BMAC driver:
</p>

<pre caption="Loading the bmac module">
# <i>modprobe bmac</i>
</pre>

</body>
</subsection>
<subsection>

Return to bug 122406

Lines 8-15 Link Here

(-)2006.0.orig/hb-install-ppc-kernel.xml (-7 / +20 lines)
8		8
9	<sections>	9	<sections>
10		10
11	<version>5.4</version>	11	<version>5.5</version>
12	<date>2006-01-06</date>	12	<date>2006-02-09</date>
13		13
14	<section>	14	<section>
15	<title>Timezone</title>	15	<title>Timezone</title>
Lines 62-74 Link Here
62	<p>	62	<p>
63	If you take a look in <path>/usr/src</path> you should see a symlink named	63	If you take a look in <path>/usr/src</path> you should see a symlink named
64	<path>linux</path> pointing to your current kernel source. In this case, the	64	<path>linux</path> pointing to your current kernel source. In this case, the
65	installed kernel source points to <c>gentoo-sources-2.6.12-r6</c>. Your version	65	installed kernel source points to <c>gentoo-sources-2.6.15</c>. Your version
66	may be different, so keep this in mind.	66	may be different, so keep this in mind.
67	</p>	67	</p>
68		68
69	<pre caption="Viewing the kernel source symlink">	69	<pre caption="Viewing the kernel source symlink">
70	# <i>ls -l /usr/src/linux</i>	70	# <i>ls -l /usr/src/linux</i>
71	lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -> linux-2.6.12-gentoo-r6	71	lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -> linux-2.6.15
72	</pre>	72	</pre>
73		73
74	<p>	74	<p>
Lines 295-307 Link Here
295		295
296	<p>	296	<p>
297	When the kernel has finished compiling, copy the kernel image to	297	When the kernel has finished compiling, copy the kernel image to
298	<path>/boot</path> (be sure that it is mounted properly on the Pegasos).	298	<path>/boot</path> (be sure that it is mounted properly on Pegasos computers).
		299	If you are using BootX to boot, we'll copy the kernel later.
		300	</p>
		301
		302	<p>
		303	Yaboot and BootX expect to use an uncompressed kernel unlike many other
		304	bootloaders. The uncompressed kernel is called vmlinux and it is placed in
		305	<path>/usr/src/linux</path> after the kernel has finished compiling. If you
		306	are using a Pegasos machine, the Pegasos firmware requires a compressed
		307	kernel called zImage.chrp which can be found in
		308	<path>/usr/src/linux/arch/ppc/boot/images</path>.
299	</p>	309	</p>
300		310
301	<pre caption="Installing the kernel">	311	<pre caption="Installing the kernel">
		312	# <i>cd /usr/src/linux</i>
302	<comment>replace <kernel-version> with your kernel version</comment>	313	<comment>replace <kernel-version> with your kernel version</comment>
303	(Apple/IBM) # <i>cp vmlinux /boot/<kernel-version></i>	314	<comment>(Apple/IBM)</comment>
304	(Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/<kernel-version></i>	315	# <i>cp vmlinux /boot/<kernel-version></i>
		316	<comment>(Pegasos)</comment>
		317	# <i>cp arch/ppc/boot/images/zImage.chrp /boot/<kernel-version></i>
305	</pre>	318	</pre>
306		319
307	<p>	320	<p>

Lines 8-15 Link Here

(-)2006.0.orig/hb-install-ppc-medium.xml (-31 / +42 lines)
8		8
9	<sections>	9	<sections>
10		10
11	<version>5.3</version>	11	<version>5.4</version>
12	<date>2005-11-29</date>	12	<date>2006-02-09</date>
13		13
14	<section>	14	<section>
15	<title>Hardware Requirements</title>	15	<title>Hardware Requirements</title>
Lines 71-78 Link Here
71	</table>	71	</table>
72		72
73	<p>	73	<p>
74	Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo	74	Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri>
75	PPC FAQ</uri> before you begin.	75	for help with some common installation related issues or if you're unsure as to
		76	just what's in that PowerPC machine you've got sitting on your desk right now.
76	</p>	77	</p>
77		78
78	</body>	79	</body>
Lines 240-254 Link Here
240	</p>	241	</p>
241		242
242	<p>	243	<p>
243	At this prompt you are able to select a kernel for the subarchitecture you use.	244	We provide one generic kernel, <e>ppc32</e>. This kernel is built with support
244	We provide <c>G3</c>, <c>G4</c> and <c>G5</c>. All kernels are built with	245	for multiple CPUs, but it will boot on single processor machines as well.
245	support for multiple CPUs, but they will boot on single processor machines as
246	well.
247	</p>	246	</p>
248		247
249	<p>	248	<p>
250	You are also able to tweak some kernel options at this prompt. The following	249	You can tweak some kernel options at this prompt. The following table lists
251	table lists some of the available boot options you can add:	250	some of the available boot options you can add:
252	</p>	251	</p>
253		252
254	<table>	253	<table>
Lines 260-269 Link Here
260	<ti><c>video</c></ti>	259	<ti><c>video</c></ti>
261	<ti>	260	<ti>
262	This option takes one of the following vendor-specific tags:	261	This option takes one of the following vendor-specific tags:
263	<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or	262	<c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>,
264	<c>ofonly</c>. You can follow this tag with the resolution and refreshrate	263	<c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution
265	you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are	264	refresh rate and color depth you want to use. For instance,
266	uncertain what to choose, <c>ofonly</c> will most certainly work.	265	<c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer
		266	at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of
		267	32 bits. If you are uncertain what to choose, and the default doesn't work,
		268	<c>video=ofonly</c> will most certainly work.
267	</ti>	269	</ti>
268	</tr>	270	</tr>
269	<tr>	271	<tr>
Lines 303-312 Link Here
303	On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type	305	On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type
304	<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose	306	<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose
305	between several preconfigured video configs. If you need any special boot	307	between several preconfigured video configs. If you need any special boot
306	options you can append them to the command-line. For instance <c>boot cd	308	options you can append them to the command-line just like with Yaboot above.
307	/boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>. The complete list of	309	For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.
308	kernel appends (in case something goes wrong and you need it) is preconfigured	310	The default kernel options (in case something goes wrong and you need it) are
309	in the kernel with <c>console=ttyS0,115200 console=tty0 init=/linuxrc	311	preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc
310	looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>.	312	looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>.
311	</p>	313	</p>
312		314
Lines 320-327 Link Here
320	<p>	322	<p>
321	If you have an OldWorld Mac the bootable portion of the livecd can't be used.	323	If you have an OldWorld Mac the bootable portion of the livecd can't be used.
322	The most simple solution is to use MacOS to bootstrap into a Linux environment	324	The most simple solution is to use MacOS to bootstrap into a Linux environment
323	with a tool called BootX. Boot floppies are being prepared for Macs without	325	with a tool called BootX.
324	MacOS, but they are not available at this time.
325	</p>	326	</p>
326		327
327	<p>	328	<p>
Lines 330-343 Link Here
330	archive into <c>Extensions Folder</c> and the BootX App Control Panel into	331	archive into <c>Extensions Folder</c> and the BootX App Control Panel into
331	<c>Control Panels</c>, both of which are located in your MacOS System Folder.	332	<c>Control Panels</c>, both of which are located in your MacOS System Folder.
332	Next, create a folder called "Linux Kernels" in your System folder and copy the	333	Next, create a folder called "Linux Kernels" in your System folder and copy the
333	<c>G3G4</c> kernel from the CD to this folder. Finally, copy <c>G3G4.igz</c>	334	<c>ppc32</c> kernel from the CD to this folder. Finally, copy <c>ppc32.igz</c>
334	from the Installation CD <path>boot</path> folder into the MacOS	335	from the Installation CD <path>boot</path> folder into the MacOS
335	<c>System Folder</c>.	336	<c>System Folder</c>.
336	</p>	337	</p>
337		338
338	<p>	339	<p>
339	To prepare BootX, start the BootX App Control Panel. First select the Options	340	To prepare BootX, start the BootX App Control Panel. First select the Options
340	dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from	341	dialog and check <c>Use Specified RAM Disk</c> and select <c>ppc32.igz</c> from
341	your System Folder. Continue back to the initial screen and ensure that the	342	your System Folder. Continue back to the initial screen and ensure that the
342	ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as	343	ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as
343	shown below:	344	shown below:
Lines 348-362 Link Here
348	</pre>	349	</pre>
349		350
350	<note>	351	<note>
351	The kernel parameters in the yaboot section above are also applicable here.	352	The kernel parameters in the yaboot section above are also applicable here. You
		353	can append any of those options to the kernel arguments above.
352	</note>	354	</note>
353		355
354	<p>	356	<p>
355	Check once more to make sure the settings are correct and then save the	357	Check once more to make sure the settings are correct and then save the
356	configuration. This saves typing just in case it doesn't boot or something is	358	configuration. This saves typing just in case it doesn't boot or something is
357	missing. Press the Linux button at the top of the window to boot into the	359	missing. Press the Linux button at the top of the window. If everything goes
358	Installation CD and continue with <uri link="#booted">And When	360	correctly, it should boot into the Installation CD. Continue with
359	You're Booted...</uri>	361	<uri link="#booted">And When You're Booted...</uri>
360	</p>	362	</p>
361		363
362	</body>	364	</body>
Lines 369-376 Link Here
369	<p>	371	<p>
370	You will be greeted by a root ("#") prompt on the current console. You can also	372	You will be greeted by a root ("#") prompt on the current console. You can also
371	switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get	373	switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get
372	back to the one you started on by pressing Alt-F1. Probably you have to hit	374	back to the one you started on by pressing Alt-F1. Due to the keyboard layout,
373	Alt-fn-Fx on Apple machines.	375	you may need to press Alt-fn-Fx on Apple machines.
374	</p>	376	</p>
375		377
376	<p>	378	<p>
Lines 417-430 Link Here
417		419
418	<p>	420	<p>
419	In the next example we try to load the <c>airport</c> module. This module	421	In the next example we try to load the <c>airport</c> module. This module
420	supports only the old Airport cards (b-net). AirportExtreme is not supported	422	supports only the old Airport cards (802.11b). Airport Extreme (802.11g) is not
421	under Linux:	423	supported on the InstallCD due to restrictions on firmware distribution.
422	</p>	424	</p>
423		425
424	<pre caption="Loading kernel modules">	426	<pre caption="Loading the airport module">
425	# <i>modprobe airport</i>	427	# <i>modprobe airport</i>
426	</pre>	428	</pre>
427		429
		430	<p>
		431	On older iMacs, sometimes the network card is not detected properly. These use
		432	the BMAC driver:
		433	</p>
		434
		435	<pre caption="Loading the bmac module">
		436	# <i>modprobe bmac</i>
		437	</pre>
		438
428	</body>	439	</body>
429	</subsection>	440	</subsection>
430	<subsection>	441	<subsection>

Lines 8-15 Link Here

(-)2006.0.orig/hb-install-config.xml (-3 / +4 lines)
8		8
9	<sections>	9	<sections>
10		10
11	<version>5.3</version>	11	<version>5.4</version>
12	<date>2005-11-19</date>	12	<date>2006-02-09</date>
13		13
14	<section>	14	<section>
15	<title>Filesystem Information</title>	15	<title>Filesystem Information</title>
Lines 80-86 Link Here
80	<p>	80	<p>
81	Let us take a look at how we write down the options for the <path>/boot</path>	81	Let us take a look at how we write down the options for the <path>/boot</path>
82	partition. This is just an example, so if your architecture doesn't require a	82	partition. This is just an example, so if your architecture doesn't require a
83	<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.	83	<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it
		84	verbatim.
84	</p>	85	</p>
85		86
86	<p>	87	<p>

Lines 8-15 Link Here

(-)2006.0.orig/hb-install-ppc-bootloader.xml (-20 / +32 lines)
8		8
9	<sections>	9	<sections>
10		10
11	<version>5.3</version>	11	<version>5.4</version>
12	<date>2006-01-19</date>	12	<date>2006-02-09</date>
13		13
14	<section>	14	<section>
15	<title>Choosing a Bootloader</title>	15	<title>Choosing a Bootloader</title>
Lines 45-58 Link Here
45	</impo>	45	</impo>
46		46
47	<p>	47	<p>
48	In order to find the boot devices, yaboot needs access to the <path>/dev</path>	48	In order to find the boot devices, yaboot needs access to the device nodes
49	filesystem. To do this, you will need to "bind-map" the <path>/dev</path>	49	created by udev on startup and the sysfs filesystem. These two filesystems
50	filesystem from the Installation CD to <path>/dev</path> inside of the chroot.	50	are found at <path>/dev</path> and <path>sys</path> respectively. To do this,
		51	you will need to "bind mount" these filesystems from the Installation CD's root
		52	to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot.
		53	If you have already bind mounted these filesystems, there is no need to do it
		54	again.
51	</p>	55	</p>
52		56
53	<pre caption="Bind-mounting the /dev-filesystem">	57	<pre caption="Bind-mounting the device and sysfs filesystems">
54	# <i>exit </i> # this will exit the chroot	58	# <i>exit </i> # this will exit the chroot
55	# <i>mount -o bind /dev /mnt/gentoo/dev</i>	59	# <i>mount -o bind /dev /mnt/gentoo/dev</i>
		60	# <i>mount -o bind /sys /mnt/gentoo/sys</i>
56	# <i>chroot /mnt/gentoo /bin/bash</i>	61	# <i>chroot /mnt/gentoo /bin/bash</i>
57	# <i>/usr/sbin/env-update && source /etc/profile </i>	62	# <i>/usr/sbin/env-update && source /etc/profile </i>
58	</pre>	63	</pre>
Lines 107-115 Link Here
107		112
108	<p>	113	<p>
109	To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,	114	To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
110	and <path>/etc/fstab</path> must be configured with your Linux partitions. Both	115	and <path>/etc/fstab</path> must be configured to reflect your Linux
111	of these should have been done already in the steps above. To start, ensure that	116	partitions. These steps should have already been completed before, but check
112	you have the latest <c>yaboot</c> installed.	117	<path>/etc/fstab</path> before proceeding. Now, ensure that you have the
		118	latest <c>yaboot</c> installed.
113	</p>	119	</p>
114		120
115	<pre caption = "Installing yaboot with GRP">	121	<pre caption = "Installing yaboot with GRP">
Lines 117-131 Link Here
117	</pre>	123	</pre>
118		124
119	<p>	125	<p>
120	Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. The	126	Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First,
121	program will run and it will confirm the location of the bootstrap partition.	127	the program will confirm the location of the bootstrap partition. If you are
122	Type <c>Y</c> if it is correct. If not, double check <path>/etc/fstab</path>.	128	using the suggested disk partitioning scheme, your bootstrap partition should
123	yabootconfig will then scan your system setup, create	129	be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your
124	<path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. <c>mkofboot</c>	130	<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup,
125	is used to format the Apple_Bootstrap partition, and install the yaboot	131	create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you.
126	configuration file into it. After this enter the chroot again.	132	<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install
		133	the yaboot configuration file into it. After this enter the chroot again.
127	</p>	134	</p>
128	<pre caption="enter chroot">	135
		136	<pre caption="Re-enter the chroot">
129	# <i>chroot /mnt/gentoo /bin/bash</i>	137	# <i>chroot /mnt/gentoo /bin/bash</i>
130	# <i>/usr/sbin/env-update && source /etc/profile</i>	138	# <i>/usr/sbin/env-update && source /etc/profile</i>
131	</pre>	139	</pre>
Lines 148-155 Link Here
148	<body>	156	<body>
149		157
150	<p>	158	<p>
151	First make sure you have the latest <c>yaboot</c> installed on your	159	First make sure you have the latest <c>yaboot</c> installed on your system:
152	system:
153	</p>	160	</p>
154		161
155	<pre caption = "Installing yaboot">	162	<pre caption = "Installing yaboot">
Lines 313-318 Link Here
313	page</uri> for more information.	320	page</uri> for more information.
314	</p>	321	</p>
315		322
		323	<impo>
		324	Make sure that you have support for HFS and HFS+ filesystems in your kernel,
		325	otherwise you will not be able to upgrade or change the kernel on your MacOS
		326	partition.
		327	</impo>
		328
316	<p>	329	<p>
317	Now reboot again and boot into Linux, then continue with <uri	330	Now reboot again and boot into Linux, then continue with <uri
318	link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>.	331	link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>.
Lines 494-500 Link Here
494	System</uri>.	507	System</uri>.
495	</p>	508	</p>
496		509
497
498	</body>	510	</body>
499	</section>	511	</section>
500	<section id="reboot">	512	<section id="reboot">

Lines 8-15 Link Here

(-)2006.0.orig/hb-install-ppc-disk.xml (-14 / +13 lines)
8		8
9	<sections>	9	<sections>
10		10
11	<version>5.1</version>	11	<version>5.2</version>
12	<date>2005-08-25</date>	12	<date>2006-02-09</date>
13		13
14	<section>	14	<section>
15	<title>Introduction to Block Devices</title>	15	<title>Introduction to Block Devices</title>
Lines 26-35 Link Here
26	</p>	26	</p>
27		27
28	<p>	28	<p>
29	To begin, we'll introduce <e>block devices</e>. The most famous block device is	29	To begin, we'll introduce <e>block devices</e>. The most common block device is
30	probably the one that represents the first IDE drive in a Linux system, namely	30	the one that represents the first IDE drive in a Linux system, namely
31	<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your first	31	<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA
32	hard drive would be <path>/dev/sda</path>.	32	drives, then your first hard drive would be <path>/dev/sda</path>.
33	</p>	33	</p>
34		34
35	<p>	35	<p>
Lines 108-114 Link Here
108	<ti>(Not applicable)</ti>	108	<ti>(Not applicable)</ti>
109	<ti><path>/dev/hda2</path> (If using quik)</ti>	109	<ti><path>/dev/hda2</path> (If using quik)</ti>
110	<ti><path>/dev/hda1</path></ti>	110	<ti><path>/dev/hda1</path></ti>
111	<ti>(Not needed)</ti>	111	<ti>(Not applicable)</ti>
112	<ti>ext2</ti>	112	<ti>ext2</ti>
113	<ti>32MB</ti>	113	<ti>32MB</ti>
114	<ti>Boot partition</ti>	114	<ti>Boot partition</ti>
Lines 138-152 Link Here
138	Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not	138	Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not
139	planning to use MacOS 9 you can delete them, because MacOS X and Linux don't	139	planning to use MacOS 9 you can delete them, because MacOS X and Linux don't
140	need them. To delete them, either use parted or erase the whole disk by	140	need them. To delete them, either use parted or erase the whole disk by
141	initialing the partition map.	141	initializing the partition map.
142	</note>	142	</note>
143		143
144	<warn>	144	<warn>
145	<c>parted</c> is able to resize partitions. On the Installation CD there	145	<c>parted</c> is able to resize partitions including HFS+. Unfortunately it is
146	are patches included to resize HFS+ filesystem. Unfortunately it is not	146	not possible to resize HFS+ journaled filesystems, so switch off journaling in
147	possible to resize HFS+ journaled filesystems, even if the journaling has been	147	Mac OS X before resizing. Remeber that any resizing operation is dangerous,
148	switchedoff in Mac OS X. Everything you do with resizing in parted you do it	148	so attempt at your own risk! Be sure to always have a backup of your data
149	on your own risk! Be sure to have a backup of your data!	149	before resizing!
150	</warn>	150	</warn>
151		151
152	<p>	152	<p>
Lines 522-528 Link Here
522	also holds for <path>/var/tmp</path>.	522	also holds for <path>/var/tmp</path>.
523	</note>	523	</note>
524		524
525
526	<p>	525	<p>
527	We will have to mount the proc filesystem (a virtual interface with the	526	We will have to mount the proc filesystem (a virtual interface with the
528	kernel) on <path>/proc</path>. But first we will need to place our files on the	527	kernel) on <path>/proc</path>. But first we will need to place our files on the