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



-- 
[email protected] mailing list

Reply via email to