10:56 p.m.
Author: jtr
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26603
Modified Files:
kernel.xml
Log Message:
Added instructions to set the kernel Makefile variable EXTRAVERSION to
match the running kernel.
Index: kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/kernel.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- kernel.xml 22 Jun 2005 18:43:07 -0000 1.9
+++ kernel.xml 19 Jul 2005 03:56:19 -0000 1.10
@@ -23,7 +23,7 @@
features. For this reason, the &FC; kernel may not be
line-for-line equivalent to the so-called vanilla kernel from the
<ulink
- url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
+
url="http://www.kernel.org"><filename>kernel.org</filename></ulink>
web site.
</para>
<para>
@@ -42,12 +42,12 @@
<listitem>
<para>
Native kernel, in both uniprocessor and <abbrev>SMP</abbrev>
- varieties.
+ varieties.
</para>
<para>
Configured sources are available in the
-
<filename>kernel-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
- package.
+
<filename>kernel-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
+ package.
</para>
</listitem>
<listitem>
@@ -56,19 +56,19 @@
</para>
<para>
Configured sources are available in the
-
<filename>kernel-xen0-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
- package.
+
<filename>kernel-xen0-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
+ package.
</para>
</listitem>
</itemizedlist>
<para>
Sources for both kernel flavors may be installed at the same time.
The files will be installed into the
-
<filename>/usr/src/kernels/<replaceable><version></replaceable>[-xen0]-<replaceable><arch></replaceable>/</filename>
+
<filename>/usr/src/kernels/<replaceable><version></replaceable>[-xen0]-<replaceable><arch></replaceable>/</filename>
tree. Use the command:
</para>
<screen width="56">
-<command>rpm <parameter class="option">-Uvh</parameter>
<filename>kernel-devel[-xen0]-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename></command>
+<command>rpm <parameter class="option">-Uvh</parameter>
<filename>kernel-devel[-xen0]-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename></command>
</screen>
<para>
as appropriate.
@@ -77,11 +77,11 @@
<title>Following Generic Textbooks</title>
<para>
Many of the tutorials, examples, and textbooks about Linux
- kernel development assume the kernel sources are installed under
- the <filename>/usr/src/linux</filename> directory. If you make a
- symbolic link, as shown below, you should be able to use those
- learning materials with the &FC; packages. Install the
- appropriate kernel sources, as shown earlier, and then:
+ kernel development assume the kernel sources are installed under
+ the <filename>/usr/src/linux</filename> directory. If you make a
+ symbolic link, as shown below, you should be able to use those
+ learning materials with the &FC; packages. Install the
+ appropriate kernel sources, as shown earlier, and then:
</para>
<screen width="56">
<command>ln <parameter class="option">-s</parameter>
<filename>/usr/src/kernels/kernel-<replaceable><all-the-rest></replaceable></filename>
<filename>/usr/src/linux</filename></command>
@@ -112,7 +112,7 @@
<filename>kernel-source</filename> package provided by older
versions. Instead, configured sources are available as described
in <xref
- linkend="sn-kernel-flavors"/>. Users that require access to &FC;
+ linkend="sn-kernel-flavors"/>. Users that require access to &FC;
original kernel sources can find them in the
<filename>kernel</filename> <filename>.src.rpm</filename>
package.
To create an exploded source tree from this file, perform the
@@ -121,12 +121,12 @@
<important>
<title>These Instructions Refer to the Currently-running Kernel!</title>
<para>
- To simplify the following directions, we have assumed that you
- want to configure the kernel sources to match your
- currently-running kernel. In the steps below, you must
- understand that the phrase
- <replaceable><version></replaceable> refers to the kernel
- version shown by this command:
+ To simplify the following directions, we have assumed that you
+ want to configure the kernel sources to match your
+ currently-running kernel. In the steps below, you must
+ understand that the phrase
+ <replaceable><version></replaceable> refers to the kernel
+ version shown by this command:
</para>
<screen width="56">
<command>uname <parameter
class="option">-r</parameter></command>
@@ -136,15 +136,15 @@
<step>
<para>
Obtain the
-
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
- file from one of the following sources:
+
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
+ file from one of the following sources:
</para>
<itemizedlist>
<listitem>
<para>
- The <filename>SRPMS</filename> directory on the
- appropriate <wordasword>SRPMS</wordasword>
- <abbrev>CD</abbrev> <filename>iso</filename> image.
+ The <filename>SRPMS</filename> directory on the
+ appropriate <wordasword>SRPMS</wordasword>
+ <abbrev>CD</abbrev> <filename>iso</filename> image.
</para>
</listitem>
<listitem>
@@ -165,16 +165,16 @@
<step>
<para>
Install
-
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
- using the command:
+
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
+ using the command:
</para>
<screen width="56">
<command>rpm <parameter class="option">-Uvh</parameter>
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename></command>
</screen>
<para>
This writes the <abbrev>RPM</abbrev> contents into
- <filename>/usr/src/redhat/SOURCES</filename> and
- <filename>/usr/src/redhat/SPECS</filename>.
+ <filename>/usr/src/redhat/SOURCES</filename> and
+ <filename>/usr/src/redhat/SPECS</filename>.
</para>
</step>
<step>
@@ -187,12 +187,12 @@
</screen>
<para>
The kernel source tree will be located in the
-
<filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable><version></replaceable>
- directory. It is common practice to move the resulting
-
<filename>linux-</filename><replaceable><version></replaceable>
- directory to the <filename>/usr/src</filename> tree; while not
- strictly necessary, we suggest that you do this to match the
- generally-available documentation.
+
<filename>/usr/src/redhat/BUILD/kernel-</filename><replaceable><version></replaceable>
+ directory. It is common practice to move the resulting
+
<filename>linux-</filename><replaceable><version></replaceable>
+ directory to the <filename>/usr/src</filename> tree; while not
+ strictly necessary, we suggest that you do this to match the
+ generally-available documentation.
</para>
<screen width="56">
<command>cd
<filename>/usr/src/redhat/BUILD/kernel-<replaceable><version></replaceable></filename>
<filename>/usr/src/</filename></command>
@@ -205,16 +205,37 @@
<step>
<para>
The configurations for the specific kernels shipped in
- &DISTRO; &DISTROVER; are in the <filename>configs/</filename>
- directory. For example, the i686 SMP configuration file is
- named
-
<filename>configs/kernel-<replaceable><version></replaceable>-i686-smp.config</filename>.
- Issue the following command to place the desired configuration
- file in the proper place for building:
+ &DISTRO; &DISTROVER; are in the <filename>configs/</filename>
+ directory. For example, the i686 SMP configuration file is
+ named
+
<filename>configs/kernel-<replaceable><version></replaceable>-i686-smp.config</filename>.
+ Issue the following command to place the desired configuration
+ file in the proper place for building:
</para>
<screen width="56">
<command>cp
<filename>configs/<replaceable><desired-config-file></replaceable></filename>
<filename>.config</filename></command>
</screen>
+ <para>
+ You can also find the <filename>.config</filename> file that
matches your current kernel configuration in the
<filename>/lib/modules/</filename><replaceable><version></replaceable><filename>/build/.config</filename>
file.
+ </para>
+ </step>
+ <step>
+ <para>
+ Every kernel gets a name based on its version number.
+ This is the value the <command>uname -r</command> command
displays.
+ The kernel name is defined by the first four lines of the kernel
<filename>Makefile</filename>.
+ To protect the innocent, the <filename>Makefile</filename> has been
changed to generate a kernel with a different name from that of the running kernel.
+ Before a module will be accepted by the running kernel, that module must have
been compiled for a kernel with the correct name.
+ </para>
+ <para>
+ Assume that <command>uname -r</command> returns the string
<systemitem class="osname">2.6.11-1.234_FC4</systemitem> and correct
the kernel name by editing the kernel <filename>Makefile</filename>, changing
the <systemitem class="macro">EXTRAVERSION</systemitem> definition
from this:
+ </para>
+ <screen width="60">EXTRAVERSION = -prep</screen>
+ <para>to this:</para>
+ <screen width="60">EXTRAVERSION = -1.234_FC4</screen>
+ <para>
+ that is, substitude everything from the final dash onward.
+ </para>
</step>
<step>
<para>
@@ -263,13 +284,13 @@
utilities, such as management daemons. Consequently, to remove
such a kernel, perhaps after an update, you
<emphasis>cannot</emphasis> simply use the <command>rpm -e
- kernel-<replaceable><version></replaceable></command>
+ kernel-<replaceable><version></replaceable></command>
command as in earlier distributions because these userspace
packages depend on the kernel package. You may either list both
the kernel package and its userspace dependant packages on the
<command>rpm -e</command> command, or you may wish to use the
<command>yum remove
- kernel-<replaceable><version></replaceable></command>
+ kernel-<replaceable><version></replaceable></command>
command instead since <command>yum</command> automatically removes
dependant packages if necesssary.
</para>