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> -- [EMAIL PROTECTED] mailing list
