chapter06/kernel.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70

<sect1 id="ch-system-kernel-headers">
<title>Installing Linux-&kernel-version; headers</title>
<?dbhtml filename="kernel.html" dir="chapter06"?>

<screen>&buildtime; &kernel-time-headers;
&diskspace; &kernel-compsize-headers;</screen>

<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>

<sect2>
<title>Installation of the kernel headers</title>

<para>We won't be compiling a new kernel yet -- we'll do that when we have
finished the installation of all the packages. But as some packages need the
kernel header files, we're going to unpack the kernel archive now, set it up
and copy the header files so they can be found by these packages.</para>

<para>It is important to note that the files in the kernel source directory
are not owned by <emphasis>root</emphasis>. Whenever you unpack a package as
user <emphasis>root</emphasis> (like we do here inside chroot), the files end
up having the user and group IDs of whatever they were on the packager's
computer. This is usually not a
problem for any other package you install because you remove the source
tree after the installation. But the Linux kernel source tree is often kept
around for a long time, so there's a chance that whatever user ID the packager
used will be assigned to somebody on your machine and then that person would
have write access to the kernel source.</para>

<para>In light of this, you might want to run <userinput>chown -R 0:0</userinput>
on the <filename>linux-&kernel-version;</filename> directory
to ensure all files are owned by user <emphasis>root</emphasis>.</para>

<para>Prepare for header installation:</para>

<screen><userinput>make mrproper</userinput></screen>

<para>This ensures that the kernel tree is absolutely clean. The kernel team
recommends that this command be issued prior to <emphasis>each</emphasis> kernel
compilation. You shouldn't rely on the source tree being clean after
untarring.</para>

<para>Create the <filename>include/linux/version.h</filename> file:</para>

<screen><userinput>make include/linux/version.h</userinput></screen>

<para>Create the platform-specific <filename>include/asm</filename>
symlink:</para>

<screen><userinput>make symlinks</userinput></screen>

<para>Install the platform specific-header files:</para>

<screen><userinput>cp -HR include/asm /usr/include
cp -R include/asm-generic /usr/include</userinput></screen>

<para>Install the cross-platform kernel header files:</para>

<screen><userinput>cp -R include/linux /usr/include</userinput></screen>

<para>There are a few kernel header files which make use of the
<filename>autoconf.h</filename> header file. Since we do not yet configure the
kernel, we need to create this file ourselves in order to avoid compilation
failures. Create an empty <filename>autoconf.h</filename> file:</para>

<screen><userinput>touch /usr/include/linux/autoconf.h</userinput></screen>

</sect2>
&c6-kernel-exp-headers;
</sect1>