1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
4 | %general-entities;
|
---|
5 | ]>
|
---|
6 | <sect1 id="ch-bootable-kernel" role="wrap" arch="alpha">
|
---|
7 | <title>Linux-&linux-alpha-version;</title>
|
---|
8 | <?dbhtml filename="kernel.html"?>
|
---|
9 |
|
---|
10 | <indexterm zone="ch-bootable-kernel"><primary sortas="a-Linux">Linux</primary></indexterm>
|
---|
11 |
|
---|
12 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
|
---|
13 | href="../chapter08/kernel.xml"
|
---|
14 | xpointer="xpointer(/sect1/sect2[@role='package'])"/>
|
---|
15 |
|
---|
16 | <sect2 role="installation">
|
---|
17 | <title>Installation of the kernel</title>
|
---|
18 |
|
---|
19 | <para>Building the kernel involves a few steps—configuration,
|
---|
20 | compilation, and installation. Read the <filename>README</filename>
|
---|
21 | file in the kernel source tree for alternate methods to the way this
|
---|
22 | book configures the kernel.</para>
|
---|
23 |
|
---|
24 | <para>Prepare for compilation by running the following command:</para>
|
---|
25 |
|
---|
26 | <screen><userinput>make mrproper</userinput></screen>
|
---|
27 |
|
---|
28 | <para>This ensures that the kernel tree is absolutely clean. The
|
---|
29 | kernel team recommends that this command be issued prior to each
|
---|
30 | kernel compilation. Do not rely on the source tree being clean after
|
---|
31 | un-tarring.</para>
|
---|
32 |
|
---|
33 | <para>Also, ensure that the kernel does not attempt to pass
|
---|
34 | hotplugging events to userspace until userspace specifies that it is
|
---|
35 | ready:</para>
|
---|
36 |
|
---|
37 | <screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen>
|
---|
38 |
|
---|
39 | <para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to
|
---|
40 | compile the keymap into the kernel, issue the command below:</para>
|
---|
41 |
|
---|
42 | <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \
|
---|
43 | drivers/char/defkeymap.c</userinput></screen>
|
---|
44 |
|
---|
45 | <para>For example, if using a Dutch keyboard, use
|
---|
46 | <phrase
|
---|
47 | condition="html"><filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename></phrase><phrase
|
---|
48 | condition="pdf"><filename>/usr/share/kbd/keymaps/i386/
|
---|
49 | qwerty/nl.map.gz</filename></phrase>.</para>
|
---|
50 |
|
---|
51 | <para>Configure the kernel via a menu-driven interface:</para>
|
---|
52 |
|
---|
53 | <screen><userinput>make menuconfig</userinput></screen>
|
---|
54 |
|
---|
55 | <para>Alternatively, <command>make oldconfig</command> may be more appropriate in some
|
---|
56 | situations. <phrase>This will build a basic system with no modules and
|
---|
57 | ext2 support only.</phrase> See the <filename>README</filename> file for more
|
---|
58 | information.</para>
|
---|
59 |
|
---|
60 | <para>If desired, skip kernel configuration by copying the kernel
|
---|
61 | config file, <filename>.config</filename>, from the host system
|
---|
62 | (assuming it is available) to the unpacked <filename
|
---|
63 | class="directory">linux-&linux-alpha-version;</filename> directory. However,
|
---|
64 | we do not recommend this option. It is often better to explore all the
|
---|
65 | configuration menus and create the kernel configuration from
|
---|
66 | scratch.</para>
|
---|
67 |
|
---|
68 | <para>For POSIX-shared memory support, ensure that the kernel config
|
---|
69 | option <quote>Virtual memory file system support</quote> is enabled.
|
---|
70 | It resides within the <quote>File systems</quote> menu and is normally
|
---|
71 | enabled by default.</para>
|
---|
72 |
|
---|
73 | <para>LFS bootscripts make the assumption that either both
|
---|
74 | <quote>Support for Host-side USB</quote> and <quote>USB device
|
---|
75 | filesystem</quote> have been compiled directly into the kernel, or
|
---|
76 | that neither is compiled at all. Bootscripts will not work properly
|
---|
77 | if it is a module (usbcore.ko).</para>
|
---|
78 |
|
---|
79 | <note><para>NPTL requires the kernel to be compiled with GCC 3.x, in
|
---|
80 | this case &gcc-version;. Compiling with 2.95.x is known to cause failures in
|
---|
81 | the glibc test suite, so it is not recommended to compile the kernel
|
---|
82 | with gcc 2.95.x.</para></note>
|
---|
83 |
|
---|
84 | <para>Compile the kernel image and modules:</para>
|
---|
85 |
|
---|
86 | <screen><userinput>make</userinput></screen>
|
---|
87 |
|
---|
88 | <para>If using kernel modules, an
|
---|
89 | <filename>/etc/modprobe.conf</filename> file may be needed.
|
---|
90 | Information pertaining to modules and kernel configuration is
|
---|
91 | located in the kernel documentation in the <filename
|
---|
92 | class="directory">linux-&linux-alpha-version;/Documentation</filename>
|
---|
93 | directory. The <emphasis>modprobe.conf</emphasis> man page may also be
|
---|
94 | of interest.</para>
|
---|
95 |
|
---|
96 | <para>Be very careful when reading other documentation because it
|
---|
97 | usually applies to 2.4.x kernels only. As far as we know, kernel
|
---|
98 | configuration issues specific to Hotplug and Udev are not documented.
|
---|
99 | The problem is that Udev will create a device node only if Hotplug or
|
---|
100 | a user-written script inserts the corresponding module into the
|
---|
101 | kernel, and not all modules are detectable by Hotplug. Note that
|
---|
102 | statements like the one below in the
|
---|
103 | <filename>/etc/modprobe.conf</filename> file do not work with
|
---|
104 | Udev:</para>
|
---|
105 |
|
---|
106 | <para><screen>alias char-major-XXX some-module</screen></para>
|
---|
107 |
|
---|
108 | <para>Because of the complications with Hotplug, Udev, and modules, we
|
---|
109 | strongly recommend starting with a completely non-modular kernel
|
---|
110 | configuration, especially if this is the first time using Udev.</para>
|
---|
111 |
|
---|
112 | <para>Install the modules, if the kernel configuration uses them:</para>
|
---|
113 |
|
---|
114 | <screen><userinput>make modules_install</userinput></screen>
|
---|
115 |
|
---|
116 | <para>If there are many modules and very little space, consider
|
---|
117 | stripping and compressing the modules. For most users, such
|
---|
118 | compression is not worth the time, but if the system is pressed for
|
---|
119 | space, see <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
|
---|
120 |
|
---|
121 | <para>After kernel compilation is complete, additional steps are
|
---|
122 | required to complete the installation. Some files need to be copied to
|
---|
123 | the <filename class="directory">/boot</filename> directory.</para>
|
---|
124 |
|
---|
125 | <para><!--The path to the kernel image may vary depending on the platform
|
---|
126 | being used. -->Issue the following command to install the kernel:</para>
|
---|
127 |
|
---|
128 | <screen><userinput>cp vmlinux /boot/vmlinux-&linux-version;</userinput></screen>
|
---|
129 |
|
---|
130 | <para><filename>System.map</filename> is a symbol file for the kernel.
|
---|
131 | It maps the function entry points of every function in the kernel API,
|
---|
132 | as well as the addresses of the kernel data structures for the running
|
---|
133 | kernel. Issue the following command to install the map file:</para>
|
---|
134 |
|
---|
135 | <screen><userinput>cp System.map /boot/System.map-&linux-alpha-version;</userinput></screen>
|
---|
136 |
|
---|
137 | <para>The kernel configuration file <filename>.config</filename>
|
---|
138 | produced by the <command>make menuconfig</command> step
|
---|
139 | above contains all the configuration selections for the kernel
|
---|
140 | that was just compiled. It is a good idea to keep this file for future
|
---|
141 | reference:</para>
|
---|
142 |
|
---|
143 | <screen><userinput>cp .config /boot/config-&linux-alpha-version;</userinput></screen>
|
---|
144 |
|
---|
145 | <para>It is important to note that the files in the kernel source
|
---|
146 | directory are not owned by <emphasis>root</emphasis>. Whenever a
|
---|
147 | package is unpacked as user <emphasis>root</emphasis> (like we did
|
---|
148 | inside chroot), the files have the user and group IDs of whatever
|
---|
149 | they were on the packager's computer. This is usually not a problem
|
---|
150 | for any other package to be installed because the source tree is
|
---|
151 | removed after the installation. However, the Linux source tree is
|
---|
152 | often retained for a long time. Because of this, there is a chance
|
---|
153 | that whatever user ID the packager used will be assigned to somebody
|
---|
154 | on the machine. That person would then have write access to the kernel
|
---|
155 | source.</para>
|
---|
156 |
|
---|
157 | <para>If the kernel source tree is going to retained, run
|
---|
158 | <command>chown -R 0:0</command> on the <filename
|
---|
159 | class="directory">linux-&linux-alpha-version;</filename> directory to ensure
|
---|
160 | all files are owned by user <emphasis>root</emphasis>.</para>
|
---|
161 | </sect2>
|
---|
162 |
|
---|
163 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
|
---|
164 | href="../chapter08/kernel.xml"
|
---|
165 | xpointer="xpointer(/sect1/sect2[@role='content'])"/>
|
---|
166 |
|
---|
167 | </sect1>
|
---|
168 |
|
---|