[gentoo-doc-cvs] cvs commit: kernel-upgrade.xml

[Sven Vermeulen]

swift       08/05/20 18:40:36

  Modified:             kernel-upgrade.xml
  Log:
  Coding style (trailing whitespace)

Revision  Changes    Path
1.18                 xml/htdocs/doc/en/kernel-upgrade.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.18&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.18&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml?r1=1.17&r2=1.18

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- kernel-upgrade.xml	22 Jun 2007 07:01:11 -0000	1.17
+++ kernel-upgrade.xml	20 May 2008 18:40:36 -0000	1.18
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.17 2007/06/22 07:01:11 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.18 2008/05/20 18:40:36 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -55,8 +55,8 @@
 <p>
 Generally, upgrading from one minor kernel release to the next won't bring any
 major differences. There are several reasons to upgrade the kernel. One is to
-take advantage of a specific new feature or driver; another is to be protected 
-against a security vulnerability, or just to maintain an up-to-date and healthy 
+take advantage of a specific new feature or driver; another is to be protected
+against a security vulnerability, or just to maintain an up-to-date and healthy
 system.
 </p>
 
@@ -104,8 +104,8 @@
 </pre>
 
 <p>
-The kernel sources will then be installed into a subdirectory of 
-<path>/usr/src</path>. In the above example, the new kernel sources will be 
+The kernel sources will then be installed into a subdirectory of
+<path>/usr/src</path>. In the above example, the new kernel sources will be
 installed at <path>/usr/src/linux-2.6.9-gentoo-r2</path>.
 </p>
 
@@ -251,9 +251,9 @@
 </pre>
 
 <p>
-Finally, you should update your boot loader configuration, adding an entry for 
+Finally, you should update your boot loader configuration, adding an entry for
 the new kernel (don't delete the old one just yet!) and unmount the
-<path>/boot</path> partition. Again, refer to the 
+<path>/boot</path> partition. Again, refer to the
 <uri link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>
 for detailed instructions on this procedure.
 </p>
@@ -313,12 +313,12 @@
 </p>
 
 <p>
-If you made a mistake and the system fails to boot with the new kernel, reboot 
-the system and select the entry from the boot loader that corresponds to the 
+If you made a mistake and the system fails to boot with the new kernel, reboot
+the system and select the entry from the boot loader that corresponds to the
 last known working kernel. You can then restart from the <uri link="#install">
-Configuring, compiling, and installing the new kernel</uri> stage -- making 
-the appropriate changes to correct your mistake. In some cases, you might not 
-even need to reboot to do this (e.g. you missed a driver for an audio device, 
+Configuring, compiling, and installing the new kernel</uri> stage -- making
+the appropriate changes to correct your mistake. In some cases, you might not
+even need to reboot to do this (e.g. you missed a driver for an audio device,
 Ethernet adapter, etc.)
 </p>
 
@@ -339,9 +339,9 @@
 
 <p>
 Switching between multiple kernels is as simple as leaving the kernel sources
-under <path>/usr/src/</path> and leaving the <path>bzImage</path> binaries on 
-your <path>/boot</path> partition (referenced by entries in your boot loader 
-configuration). Every time you boot up, you will be presented with a choice of 
+under <path>/usr/src/</path> and leaving the <path>bzImage</path> binaries on
+your <path>/boot</path> partition (referenced by entries in your boot loader
+configuration). Every time you boot up, you will be presented with a choice of
 which kernel to boot into.
 </p>
 
@@ -368,7 +368,7 @@
 
 <p>
 In most cases, temporary files used during compilation will still remain under
-the appropriate source directory under <path>/usr/src</path>. It is safe to 
+the appropriate source directory under <path>/usr/src</path>. It is safe to
 remove these using <c>rm</c>.
 </p>
 
@@ -380,7 +380,7 @@
 </p>
 
 <p>
-Finally, you can mount your <path>/boot</path> partition and remove the 
+Finally, you can mount your <path>/boot</path> partition and remove the
 <path>bzImage</path> file(s) for the kernel(s) you are pruning. You should also
 edit your boot loader configuration so that it no longer references such
 kernel(s).



-- 
gentoo-doc-cvs@l.g.o mailing list