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

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

[Jan Kundrat]

jkt         05/10/06 19:16:11

  Modified:    xml/htdocs/doc/en kernel-upgrade.xml
  Log:
  word wrapping, *no content change*

Revision  Changes    Path
1.10      +4 -4      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.10&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.10&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.9&r2=1.10&cvsroot=gentoo

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- kernel-upgrade.xml	6 Oct 2005 19:13:03 -0000	1.9
+++ kernel-upgrade.xml	6 Oct 2005 19:16:11 -0000	1.10
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.9 2005/10/06 19:13:03 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.10 2005/10/06 19:16:11 jkt Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -359,9 +359,9 @@
 
 <p>
 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).
+<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).
 </p>
 
 </body>



-- 
gentoo-doc-cvs@gentoo.org mailing list

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

[swift]

swift       05/10/11 03:48:06

  Modified:    xml/htdocs/doc/en kernel-upgrade.xml
  Log:
  #104877 - Mention module-rebuild

Revision  Changes    Path
1.11      +8 -3      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.11&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.11&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.10&r2=1.11&cvsroot=gentoo

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- kernel-upgrade.xml	6 Oct 2005 19:16:11 -0000	1.10
+++ kernel-upgrade.xml	11 Oct 2005 03:48:06 -0000	1.11
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.10 2005/10/06 19:16:11 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.11 2005/10/11 03:48:06 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -17,8 +17,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.1.7</version>
-<date>2005-10-06</date>
+<version>0.1.8</version>
+<date>2005-10-11</date>
 
 <chapter>
 <title>Introduction</title>
@@ -269,6 +269,11 @@
 procedure will make sure that they are rebuilt to work with the new kernel.
 </p>
 
+<p>
+We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which
+rebuilds all the kernel modules you have installed using separate ebuilds.
+</p>
+
 </body>
 </section>
 </chapter>



-- 
gentoo-doc-cvs@gentoo.org mailing list

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

[Xavier Neys]

neysx       06/01/08 15:16:15

  Modified:    xml/htdocs/doc/en kernel-upgrade.xml
  Log:
  #118060 add a blurb about module-rebuild

Revision  Changes    Path
1.13      +25 -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.13&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.13&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.12&r2=1.13&cvsroot=gentoo

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- kernel-upgrade.xml	1 Jan 2006 11:51:43 -0000	1.12
+++ kernel-upgrade.xml	8 Jan 2006 15:16:15 -0000	1.13
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.12 2006/01/01 11:51:43 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.13 2006/01/08 15:16:15 neysx Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -17,8 +17,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.1.8</version>
-<date>2005-10-11</date>
+<version>0.2</version>
+<date>2006-01-06</date>
 
 <chapter>
 <title>Introduction</title>
@@ -258,20 +258,31 @@
 
 <p>
 If you use any kernel modules that are not included in the kernel source tree
-but are provided elsewhere in portage (e.g. NVIDIA or ATI graphics drivers),
-then you must reinstall these after upgrading the kernel. This is as simple as
-re-merging the packages involved. For more information, refer to the chapter on
-<e>Configuring the Kernel</e> in the <uri 
-link="/doc/en/handbook/index.xml">Gentoo Handbook</uri>.
-To ensure these packages will build against the source tree at
-<path>/usr/src/linux</path>, first uninstall the packages, then re-emerge them.
-If old sources for these packages are kept by portage, this uninstall/re-emerge
-procedure will make sure that they are rebuilt to work with the new kernel.
+but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or ATI
+graphics drivers), then you must reinstall these after upgrading the kernel.
+This is as simple as re-merging the packages involved. For more information,
+refer to the chapter on <e>Configuring the Kernel</e> in the <uri
+link="/doc/en/handbook/">Gentoo Handbook</uri>. To ensure these
+packages will build against the source tree at <path>/usr/src/linux</path>,
+first uninstall the packages, then re-emerge them. If old sources for these
+packages are kept by portage, this uninstall/re-emerge procedure will make sure
+that they are rebuilt to work with the new kernel.
 </p>
 
 <p>
 We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which
-rebuilds all the kernel modules you have installed using separate ebuilds.
+rebuilds all the kernel modules you have installed using separate ebuilds (for
+the <b>currently running</b> kernel, not necessarily the one in
+<path>/usr/src/linux</path>). Its use is straightforward. After emerging it,
+simply run <c>module-rebuild populate</c> to populate the database with a list
+of packages that will need to be rebuilt after upgrading the kernel. Once you
+have finished upgrading or recompiling your kernel, run <c>module-rebuild
+rebuild</c> to rebuild the drivers for your new kernel before you reboot.
+</p>
+
+<p>
+For more information, run <c>module-rebuild</c> without any options to see a
+list of commands that can be passed to the utility.
 </p>
 
 </body>
@@ -294,7 +305,7 @@
 in to resume whatever you were doing. If this is the case, then the upgrade is
 complete.
 </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 



-- 
gentoo-doc-cvs@gentoo.org mailing list

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

[Josh Saddler]

nightmorph    06/02/22 20:30:20

  Modified:    xml/htdocs/doc/en kernel-upgrade.xml
  Log:
  Fixed module-rebuild section for bug 119235

Revision  Changes    Path
1.14      +10 -15    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.14&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.14&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.13&r2=1.14&cvsroot=gentoo

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- kernel-upgrade.xml	8 Jan 2006 15:16:15 -0000	1.13
+++ kernel-upgrade.xml	22 Feb 2006 20:30:20 -0000	1.14
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.13 2006/01/08 15:16:15 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.14 2006/02/22 20:30:20 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -17,8 +17,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.2</version>
-<date>2006-01-06</date>
+<version>0.3</version>
+<date>2006-02-22</date>
 
 <chapter>
 <title>Introduction</title>
@@ -262,22 +262,17 @@
 graphics drivers), then you must reinstall these after upgrading the kernel.
 This is as simple as re-merging the packages involved. For more information,
 refer to the chapter on <e>Configuring the Kernel</e> in the <uri
-link="/doc/en/handbook/">Gentoo Handbook</uri>. To ensure these
-packages will build against the source tree at <path>/usr/src/linux</path>,
-first uninstall the packages, then re-emerge them. If old sources for these
-packages are kept by portage, this uninstall/re-emerge procedure will make sure
-that they are rebuilt to work with the new kernel.
+link="/doc/en/handbook/">Gentoo Handbook</uri>.
 </p>
 
 <p>
 We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which
-rebuilds all the kernel modules you have installed using separate ebuilds (for
-the <b>currently running</b> kernel, not necessarily the one in
-<path>/usr/src/linux</path>). Its use is straightforward. After emerging it,
-simply run <c>module-rebuild populate</c> to populate the database with a list
-of packages that will need to be rebuilt after upgrading the kernel. Once you
-have finished upgrading or recompiling your kernel, run <c>module-rebuild
-rebuild</c> to rebuild the drivers for your new kernel before you reboot.
+rebuilds all the kernel modules you have installed using separate ebuilds for
+the kernel at <path>/usr/src/linux</path>. Its use is straightforward. After
+emerging it, simply run <c>module-rebuild populate</c> to populate the
+database with a list of packages that will need to be rebuilt after upgrading
+the kernel. Once you have finished upgrading or recompiling your kernel, run
+<c>module-rebuild rebuild</c> to rebuild the drivers for your new kernel.
 </p>
 
 <p>



-- 
gentoo-doc-cvs@gentoo.org mailing list

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

[Shyam Mani]

fox2mike    06/05/04 16:49:14

  Modified:             kernel-upgrade.xml
  Log:
  Bug #113417 - Added a few lines on using eselect to change the kernel symlink. Thanks to Federico Galassi<federico@serversidestudio.it> for reporting.

Revision  Changes    Path
1.15                 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.15&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.15&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.14&r2=1.15&cvsroot=gentoo

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- kernel-upgrade.xml	22 Feb 2006 20:30:20 -0000	1.14
+++ kernel-upgrade.xml	4 May 2006 16:49:14 -0000	1.15
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.14 2006/02/22 20:30:20 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.15 2006/05/04 16:49:14 fox2mike Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -17,8 +17,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.3</version>
-<date>2006-02-22</date>
+<version>0.4</version>
+<date>2006-05-04</date>
 
 <chapter>
 <title>Introduction</title>
@@ -135,6 +135,22 @@
 </pre>
 
 <p>
+Alternatively, you could use <c>app-admin/eselect</c> to modify the symlink.
+</p>
+
+<pre caption="Using eselect to symlink">
+<comment>(Install eselect if you don't have it)</comment>
+# <i>emerge eselect</i>
+<comment>(See the list of available kernels)</comment>
+# <i>eselect kernel list</i>
+Available kernel symlink targets:
+  [1]   linux-2.6.9-gentoo-r1
+  [2]   linux-2.6.9-gentoo-r2
+<comment>(Select the correct kernel)</comment>
+# <i>eselect kernel set 1</i>
+</pre>
+
+<p>
 If you really want to do it yourself, the following example shows you how to
 make the link point to <path>linux-2.6.9-gentoo-r2</path>:
 </p>



-- 
gentoo-doc-cvs@gentoo.org mailing list

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

[Xavier Neys]

neysx       06/07/23 12:27:14

  Modified:             kernel-upgrade.xml
  Log:
  #138582 no need for --udev w/ genkernel anymore, how to reuse config with genkernel

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

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

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- kernel-upgrade.xml	4 May 2006 16:49:14 -0000	1.15
+++ kernel-upgrade.xml	23 Jul 2006 12:27:14 -0000	1.16
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.15 2006/05/04 16:49:14 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.16 2006/07/23 12:27:14 neysx Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -17,8 +17,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.4</version>
-<date>2006-05-04</date>
+<version>0.5</version>
+<date>2006-07-23</date>
 
 <chapter>
 <title>Introduction</title>
@@ -171,9 +171,9 @@
 
 <p>
 For either of these options, you should refer to the instructions given in the
-<uri link="/doc/en/handbook/index.xml">Gentoo
-Handbook</uri> relating to <e>Configuring the Kernel</e> and <e>Configuring
-the Bootloader</e>. Below is an outline of the required actions:
+<uri link="/doc/en/handbook/">Gentoo Handbook</uri> relating to <e>Configuring
+the Kernel</e> and <e>Configuring the Bootloader</e>. Below is an outline of
+the required actions:
 </p>
 
 </body>
@@ -192,18 +192,14 @@
 </p>
 
 <pre caption="Invoking genkernel">
-<comment>(For 2.4 kernels:)</comment>
 # <i>genkernel all</i>
-
-<comment>(For 2.6 kernels:)</comment>
-# <i>genkernel --udev all</i>
 </pre>
 
 <p>
 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
-boot loader configuration, then invoke genkernel as follows:
+<c>menuconfig</c> and you wish genkernel to automatically update your grub boot
+loader configuration, then invoke genkernel as follows:
 </p>
 
 <pre caption="Invoking genkernel with some common arguments">
@@ -211,9 +207,8 @@
 </pre>
 
 <p>
-For more info, follow the
-<uri link="/doc/en/genkernel.xml">Gentoo Linux Genkernel
-Guide</uri>, or refer to the <uri link="/doc/en/handbook/index.xml">Gentoo
+For more info, follow the <uri link="/doc/en/genkernel.xml">Gentoo Linux
+Genkernel Guide</uri>, or refer to the <uri link="/doc/en/handbook/">Gentoo
 Handbook</uri>. Many of the options can be set in the configuration file for
 <c>genkernel</c>, <path>/etc/genkernel.conf</path>.
 </p>
@@ -420,9 +415,9 @@
 </p>
 
 <p>
-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 
+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>
 
@@ -432,6 +427,12 @@
 # <i>make oldconfig</i>
 </pre>
 
+<pre caption="Reusing your old config with genkernel">
+# <i>cd /etc/kernels</i>
+# <i>cp kernel-config-x86-2.6.9-gentoo-r1 kernel-config-x86-2.6.9-gentoo-r2</i>
+# <i>genkernel all</i>
+</pre>
+
 <p>
 At this point, you may be asked to produce answers for configuration options
 which have changed between the two versions. Once you have done that, you can



-- 
gentoo-doc-cvs@gentoo.org mailing list

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

[Josh Saddler]

nightmorph    07/06/22 07:01:11

  Modified:             kernel-upgrade.xml
  Log:
  added a better way of upgrading one's kernel that avoids the problems of oldconfig, thanks to mark_alec for addressing the section on IRC

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

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

Index: kernel-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- kernel-upgrade.xml	23 Jul 2006 12:27:14 -0000	1.16
+++ kernel-upgrade.xml	22 Jun 2007 07:01:11 -0000	1.17
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.16 2006/07/23 12:27:14 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.17 2007/06/22 07:01:11 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/kernel-upgrade.xml">
@@ -17,8 +17,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>0.5</version>
-<date>2006-07-23</date>
+<version>0.6</version>
+<date>2007-06-22</date>
 
 <chapter>
 <title>Introduction</title>
@@ -440,6 +440,19 @@
 <c>menuconfig</c> configuration process.
 </p>
 
+<p>
+A much safer upgrading method is to copy your config as previously shown, and
+then simply run <c>make menuconfig</c>. This avoids the problems of <c>make
+oldconfig</c> mentioned previously, as <c>make menuconfig</c> will load up your
+previous configuration as much as possible into the menu. Now all you have to
+do is go through each option and look for new sections, removals, and so on. By
+using <c>menuconfig</c>, you gain context for all the new changes, and can
+easily view the new choices and review help screens much easier. You can even
+use this for upgrades such as 2.6.8 to 2.6.9; just make sure you read through
+the options carefully. Once you've finished, compile and install your kernel as
+normal.
+</p>
+
 </body>
 </section>
 </chapter>



-- 
gentoo-doc-cvs@gentoo.org mailing list

[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@lists.gentoo.org mailing list