| 1 |
nightmorph 07/06/22 07:01:11 |
| 2 |
|
| 3 |
Modified: kernel-upgrade.xml |
| 4 |
Log: |
| 5 |
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 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.17 xml/htdocs/doc/en/kernel-upgrade.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.17&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml?rev=1.17&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml?r1=1.16&r2=1.17 |
| 13 |
|
| 14 |
Index: kernel-upgrade.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v |
| 17 |
retrieving revision 1.16 |
| 18 |
retrieving revision 1.17 |
| 19 |
diff -u -r1.16 -r1.17 |
| 20 |
--- kernel-upgrade.xml 23 Jul 2006 12:27:14 -0000 1.16 |
| 21 |
+++ kernel-upgrade.xml 22 Jun 2007 07:01:11 -0000 1.17 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.16 2006/07/23 12:27:14 neysx Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kernel-upgrade.xml,v 1.17 2007/06/22 07:01:11 nightmorph Exp $ --> |
| 26 |
|
| 27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 28 |
<guide link="/doc/en/kernel-upgrade.xml"> |
| 29 |
@@ -17,8 +17,8 @@ |
| 30 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 31 |
<license/> |
| 32 |
|
| 33 |
-<version>0.5</version> |
| 34 |
-<date>2006-07-23</date> |
| 35 |
+<version>0.6</version> |
| 36 |
+<date>2007-06-22</date> |
| 37 |
|
| 38 |
<chapter> |
| 39 |
<title>Introduction</title> |
| 40 |
@@ -440,6 +440,19 @@ |
| 41 |
<c>menuconfig</c> configuration process. |
| 42 |
</p> |
| 43 |
|
| 44 |
+<p> |
| 45 |
+A much safer upgrading method is to copy your config as previously shown, and |
| 46 |
+then simply run <c>make menuconfig</c>. This avoids the problems of <c>make |
| 47 |
+oldconfig</c> mentioned previously, as <c>make menuconfig</c> will load up your |
| 48 |
+previous configuration as much as possible into the menu. Now all you have to |
| 49 |
+do is go through each option and look for new sections, removals, and so on. By |
| 50 |
+using <c>menuconfig</c>, you gain context for all the new changes, and can |
| 51 |
+easily view the new choices and review help screens much easier. You can even |
| 52 |
+use this for upgrades such as 2.6.8 to 2.6.9; just make sure you read through |
| 53 |
+the options carefully. Once you've finished, compile and install your kernel as |
| 54 |
+normal. |
| 55 |
+</p> |
| 56 |
+ |
| 57 |
</body> |
| 58 |
</section> |
| 59 |
</chapter> |
| 60 |
|
| 61 |
|
| 62 |
|
| 63 |
-- |
| 64 |
gentoo-doc-cvs@g.o mailing list |
Archives