| 1 |
nightmorph 07/04/02 00:47:47 |
| 2 |
|
| 3 |
Modified: hb-install-ppc-kernel.xml |
| 4 |
Log: |
| 5 |
minor cosmetic changes |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.32 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.32&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.32&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?r1=1.31&r2=1.32 |
| 13 |
|
| 14 |
Index: hb-install-ppc-kernel.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v |
| 17 |
retrieving revision 1.31 |
| 18 |
retrieving revision 1.32 |
| 19 |
diff -u -r1.31 -r1.32 |
| 20 |
--- hb-install-ppc-kernel.xml 19 Mar 2007 09:24:46 -0000 1.31 |
| 21 |
+++ hb-install-ppc-kernel.xml 2 Apr 2007 00:47:47 -0000 1.32 |
| 22 |
@@ -4,7 +4,7 @@ |
| 23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v 1.31 2007/03/19 09:24:46 nightmorph Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml,v 1.32 2007/04/02 00:47:47 nightmorph Exp $ --> |
| 28 |
|
| 29 |
<sections> |
| 30 |
|
| 31 |
@@ -56,10 +56,9 @@ |
| 32 |
|
| 33 |
<p> |
| 34 |
If you take a look in <path>/usr/src</path> you should see a symlink named |
| 35 |
-<path>linux</path> pointing to your newly emerged kernel source. In this case, |
| 36 |
-the installed kernel source points to <c>gentoo-sources-<keyval |
| 37 |
-id="kernel-version"/></c>. Your installed version may be different, so keep this |
| 38 |
-in mind. |
| 39 |
+<path>linux</path> pointing to your current kernel source. In this case, the |
| 40 |
+installed kernel source points to <c>gentoo-sources-<keyval |
| 41 |
+id="kernel-version"/></c>. Your version may be different, so keep this in mind. |
| 42 |
</p> |
| 43 |
|
| 44 |
<pre caption="Viewing the kernel source symlink"> |
| 45 |
@@ -301,11 +300,11 @@ |
| 46 |
</p> |
| 47 |
|
| 48 |
<p> |
| 49 |
-Yaboot and BootX expect to use an uncompressed kernel unlike many other |
| 50 |
+Yaboot and BootX expect to use an uncompressed kernel unlike many other |
| 51 |
bootloaders. The uncompressed kernel is called vmlinux and it is placed in |
| 52 |
-<path>/usr/src/linux</path> after the kernel has finished compiling. If you |
| 53 |
-are using a Pegasos machine, the Pegasos firmware requires a compressed |
| 54 |
-kernel called zImage which can be found in |
| 55 |
+<path>/usr/src/linux</path> after the kernel has finished compiling. If you are |
| 56 |
+using a Pegasos machine, the Pegasos firmware requires a compressed kernel |
| 57 |
+called zImage which can be found in |
| 58 |
<path>/usr/src/linux/arch/powerpc/boot/images</path>. |
| 59 |
</p> |
| 60 |
|
| 61 |
@@ -374,14 +373,15 @@ |
| 62 |
<body> |
| 63 |
|
| 64 |
<p> |
| 65 |
-Now that your kernel source tree is installed, it's now time to compile your |
| 66 |
-kernel by using the <c>genkernel</c> script to automatically build a kernel for |
| 67 |
-you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 68 |
-way our Installation CD kernel is configured. This means that when you use |
| 69 |
-<c>genkernel</c> to build your kernel, your system will generally detect all |
| 70 |
-your hardware at boot-time, just like the Installation CD does. Since |
| 71 |
-genkernel doesn't require any manual kernel configuration, it is an ideal |
| 72 |
-solution for those users who may not be comfortable compiling their own kernels. |
| 73 |
+Now that your kernel source tree is installed, it's now time to compile your |
| 74 |
+kernel by using our <c>genkernel</c> script to automatically build a kernel for |
| 75 |
+you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 76 |
+way our Installation CD kernel is configured. This means that when you use |
| 77 |
+<c>genkernel</c> to build your kernel, your system will generally detect all |
| 78 |
+your hardware at boot-time, just like our Installation CD does. Because |
| 79 |
+genkernel doesn't require any manual kernel configuration, it is an ideal |
| 80 |
+solution for those users who may not be comfortable compiling their own |
| 81 |
+kernels. |
| 82 |
</p> |
| 83 |
|
| 84 |
<p> |
| 85 |
@@ -423,9 +423,11 @@ |
| 86 |
</pre> |
| 87 |
|
| 88 |
<p> |
| 89 |
-Now, compile your kernel sources by running <c>genkernel all</c>. Be aware, |
| 90 |
-since <c>genkernel</c> compiles a kernel that supports almost all hardware, |
| 91 |
-this compilation can take quite a while to finish! |
| 92 |
+Now, compile your kernel sources by running <c>genkernel --genzimage all</c>. |
| 93 |
+For Pegasos, we will need to use a different config and create a zImage instead |
| 94 |
+of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> |
| 95 |
+compiles a kernel that supports almost all hardware, this compilation can take |
| 96 |
+quite a while to finish! |
| 97 |
</p> |
| 98 |
|
| 99 |
<p> |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
-- |
| 104 |
gentoo-doc-cvs@g.o mailing list |
Archives