[gentoo-doc-cvs] cvs commit: hb-install-ppc-kernel.xml

[Sven Vermeulen]

swift       08/08/21 14:47:23

  Modified:             hb-install-ppc-kernel.xml
  Log:
  Some coding style changes (trailing whitespace, no tabs)

Revision  Changes    Path
1.60                 xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.60&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?rev=1.60&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml?r1=1.59&r2=1.60

Index: hb-install-ppc-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- hb-install-ppc-kernel.xml	21 Aug 2008 14:44:44 -0000	1.59
+++ hb-install-ppc-kernel.xml	21 Aug 2008 14:47:23 -0000	1.60
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.59 2008/08/21 14:44:44 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-kernel.xml,v 1.60 2008/08/21 14:47:23 swift Exp $ -->
 
 <sections>
 
@@ -41,9 +41,9 @@
 <p>
 The core around which all distributions are built is the Linux kernel. It is the
 layer between the user programs and your system hardware. Gentoo provides its
-users several possible kernels to choose from. A full listing with description 
-is available at the 
-<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. 
+users several possible kernels to choose from. A full listing with description
+is available at the
+<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>.
 </p>
 
 <p>
@@ -67,16 +67,16 @@
 </pre>
 
 <p>
-Now it is time to configure and compile your kernel source. You can use 
-<c>genkernel</c> for this, which will build a generic kernel as used by the 
+Now it is time to configure and compile your kernel source. You can use
+<c>genkernel</c> for this, which will build a generic kernel as used by the
 Installation CD. We explain the "manual" configuration first though, as it is
 a more efficient configuration.
 </p>
 
 <p>
 If you want to manually configure your kernel, continue now with <uri
-link="#manual">Default: Manual Configuration</uri>. If you want to use 
-<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using 
+link="#manual">Default: Manual Configuration</uri>. If you want to use
+<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
 genkernel</uri> instead.
 </p>
 
@@ -97,13 +97,13 @@
 
 <p>
 However, one thing <e>is</e> true: you must know your system when you start
-configuring a kernel manually. Most information can be gathered by emerging 
-pciutils (<c>emerge pciutils</c>) which contains the program 
+configuring a kernel manually. Most information can be gathered by emerging
+pciutils (<c>emerge pciutils</c>) which contains the program
 <c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted
 environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib:
 cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively,
 you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results
-are the same. You can also run <c>lsmod</c> to see what kernel modules the 
+are the same. You can also run <c>lsmod</c> to see what kernel modules the
 Installation CD uses (it might provide you with a nice hint on what to enable).
 Another place to look for clues as to what components to enable is to check the
 kernel message logs from the successful boot that got you this far.  Type
@@ -215,14 +215,14 @@
 <p>
 At this time, full kernel preemption may still be unstable on PPC and may cause
 compilation failures and random segfaults.  It is <e>strongly</e> suggested
-that you do not use this feature.  Both <e>Voluntary Preemption</e> and 
+that you do not use this feature.  Both <e>Voluntary Preemption</e> and
 <e>No Forced Preemption</e> should be safe.
 </p>
 
 <pre caption="Ensure the Preemptible Kernel Option is Off">
 Kernel options ---&gt;
 <comment>(Select One)</comment>
-  Preemption Model 
+  Preemption Model
     (X) No Forced Preemption (Server)
     (X) Voluntary Kernel Preemption (Desktop)
 </pre>
@@ -293,7 +293,7 @@
 <body>
 
 <p>
-Now that your kernel is configured, it is time to compile and install it. Exit 
+Now that your kernel is configured, it is time to compile and install it. Exit
 the configuration menu and run the following commands:
 </p>
 
@@ -304,7 +304,7 @@
 <p>
 When the kernel has finished compiling, copy the kernel image to
 <path>/boot</path> as shown below. If you have a separate boot partition, as
-on Pegasos computers, be sure that it is mounted properly. If you are using 
+on Pegasos computers, be sure that it is mounted properly. If you are using
 BootX to boot, we'll copy the kernel later.
 </p>
 
@@ -323,7 +323,7 @@
 <comment>(Apple/IBM)</comment>
 # <i>cp vmlinux /boot/<keyval id="kernel-name"/></i>
 <comment>(Pegasos)</comment>
-# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name" /></i> 
+# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name" /></i>
 </pre>
 
 <p>
@@ -358,7 +358,7 @@
 </pre>
 
 <p>
-Next, copy over the kernel configuration used by the Installation CD to the 
+Next, copy over the kernel configuration used by the Installation CD to the
 location where genkernel looks for the default kernel configuration:
 </p>
 
@@ -367,7 +367,7 @@
 </pre>
 
 <p>
-If you are using firewire or USB to boot, you'll need to add modules to the 
+If you are using firewire or USB to boot, you'll need to add modules to the
 initrd.  Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change
 <c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or
 <c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support.
@@ -384,21 +384,21 @@
 <pre caption="Removing /boot from /etc/fstab on machines without a boot partition">
 # <i>nano -w /etc/fstab</i>
 <comment>Remove this line</comment>
-/dev/BOOT		/boot		ext2		noauto,noatime	1 2
+/dev/BOOT  /boot    ext2    noauto,noatime    1 2
 </pre>
 
 <p>
 Now, compile your kernel sources by running <c>genkernel --genzimage all</c>.
 For Pegasos, we will need to use a different config and create a zImage instead
-of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> 
-compiles a kernel that supports almost all hardware, this compilation can take 
+of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c>
+compiles a kernel that supports almost all hardware, this compilation can take
 quite a while to finish!
 </p>
 
 <p>
 Note that, if your partition where the kernel should be located doesn't use ext2
 or ext3 as filesystem you might need to manually configure your kernel using
-<c>genkernel --menuconfig all</c> and add support for your 
+<c>genkernel --menuconfig all</c> and add support for your
 filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or
 LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as
 well.
@@ -413,12 +413,12 @@
 </pre>
 
 <p>
-Once <c>genkernel</c> completes, a kernel, full set of modules and 
-<e>initial root disk</e> (initrd) will be created. We will use the kernel 
+Once <c>genkernel</c> completes, a kernel, full set of modules and
+<e>initial root disk</e> (initrd) will be created. We will use the kernel
 and initrd when configuring a boot loader later in this document. Write
 down the names of the kernel and initrd as you will need them when writing
-the bootloader configuration file. The initrd will be started immediately after 
-booting to perform hardware autodetection (just like on the Installation CD) 
+the bootloader configuration file. The initrd will be started immediately after
+booting to perform hardware autodetection (just like on the Installation CD)
 before your "real" system starts up.  Be sure to also copy down the required
 boot arguments, these are required for a successful boot with genkernel.
 </p>