swift 05/05/23 18:40:25 Modified: xml/htdocs/doc/en kernel-upgrade.xml Log: Some more spelling mistakes - no content change
Revision Changes Path 1.5 +14 -14 xml/htdocs/doc/en/kernel-upgrade.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kernel-upgrade.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo Index: kernel-upgrade.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- kernel-upgrade.xml 23 May 2005 18:35:47 -0000 1.4 +++ kernel-upgrade.xml 23 May 2005 18:40:25 -0000 1.5 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.4 2005/05/23 18:35:47 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.5 2005/05/23 18:40:25 swift Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/kernel-upgrade.xml"> @@ -173,7 +173,7 @@ You can also use extra parameters for other genkernel functionality. For example, if you wish to configure some extra kernel options using <c>menuconfig</c> and you wish genkernel to automatically update your grub -bootloader config, then invoke genkernel as follows: +boot loader configuration, then invoke genkernel as follows: </p> <pre caption="Invoking genkernel with some common arguments"> @@ -228,8 +228,8 @@ </pre> <p> -Finally, you should update your bootloader config, adding an entry for the -new kernel (don't delete the old one just yet!) and unmount the +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 <uri link="/doc/en/handbook/index.xml">Gentoo Handbook</uri> for detailed instructions on this procedure. @@ -268,7 +268,7 @@ <p> Next, close all applications and reboot your system. If you followed the above -instructions correctly, the bootloader menu should include an entry for the +instructions correctly, the boot loader menu should include an entry for the new kernel. Select the new kernel and let the system boot. </p> @@ -280,12 +280,12 @@ <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 bootloader that corresponds to the +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, -ethernet adapter, etc.) +Ethernet adapter, etc.) </p> </body> @@ -306,9 +306,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 bootloader -config). Every time you boot up, you will be presented with a choice of which -kernel to boot into. +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> </body> @@ -348,7 +348,7 @@ <p> Finally, you can mount your <path>/boot</path> partition and remove the <path>bzImage</path> and <path>System.map</path> files for the kernel(s) -you are pruning. You should also edit your bootloader config so that it +you are pruning. You should also edit your boot loader configuration so that it no longer references such kernel(s). </p> @@ -381,9 +381,9 @@ </p> <p> -To reuse your old config, you simply need to copy it over and then run <c>make -oldconfig</c>. In the following example, we take the config from -<c>gentoo-sources-2.6.9-r1</c> and import it into +To reuse your old <path>.config</path>, you simply need to copy it over and then +run <c>make oldconfig</c>. In the following example, we take the configuration +from <c>gentoo-sources-2.6.9-r1</c> and import it into <c>gentoo-sources-2.6.9-r2</c>. </p> -- [email protected] mailing list
