[519ee45] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
| 7 |
|
---|
| 8 | <sect1 id="ch-bootable-kernel" role="wrap">
|
---|
| 9 | <?dbhtml filename="kernel.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Linux-&linux-version;</title>
|
---|
| 12 |
|
---|
| 13 | <indexterm zone="ch-bootable-kernel">
|
---|
| 14 | <primary sortas="a-Linux">Linux</primary>
|
---|
| 15 | </indexterm>
|
---|
| 16 |
|
---|
| 17 | <sect2 role="package">
|
---|
| 18 | <title/>
|
---|
| 19 |
|
---|
| 20 | <para>The Linux package contains the Linux kernel.</para>
|
---|
| 21 |
|
---|
| 22 | <segmentedlist>
|
---|
| 23 | <segtitle>&buildtime;</segtitle>
|
---|
| 24 | <segtitle>&diskspace;</segtitle>
|
---|
| 25 |
|
---|
| 26 | <seglistitem>
|
---|
| 27 | <seg>&linux-ch8-sbu;</seg>
|
---|
| 28 | <seg>&linux-ch8-du;</seg>
|
---|
| 29 | </seglistitem>
|
---|
| 30 | </segmentedlist>
|
---|
| 31 |
|
---|
| 32 | </sect2>
|
---|
| 33 |
|
---|
| 34 | <sect2 role="installation">
|
---|
| 35 | <title>Installation of the kernel</title>
|
---|
| 36 |
|
---|
| 37 | <para>Building the kernel involves a few steps—configuration,
|
---|
| 38 | compilation, and installation. Read the <filename>README</filename> file
|
---|
| 39 | in the kernel source tree for alternative methods to the way this book
|
---|
| 40 | configures the kernel.</para>
|
---|
| 41 |
|
---|
| 42 | <para>By default, the Linux kernel generates wrong sequences of bytes when
|
---|
| 43 | dead keys are used in UTF-8 keyboard mode. Also, one cannot copy and paste
|
---|
| 44 | non-ASCII characters when UTF-8 mode is active. Fix these issues with the
|
---|
| 45 | patch:</para>
|
---|
| 46 |
|
---|
| 47 | <screen><userinput>patch -Np1 -i ../&linux-utf8-patch;</userinput></screen>
|
---|
| 48 |
|
---|
| 49 | <para>Prepare for compilation by running the following command:</para>
|
---|
| 50 |
|
---|
| 51 | <screen><userinput>make mrproper</userinput></screen>
|
---|
| 52 |
|
---|
| 53 | <para>This ensures that the kernel tree is absolutely clean. The
|
---|
| 54 | kernel team recommends that this command be issued prior to each
|
---|
| 55 | kernel compilation. Do not rely on the source tree being clean after
|
---|
| 56 | un-tarring.</para>
|
---|
| 57 |
|
---|
| 58 | <!-- Support for compiling a keymap into the kernel is deliberately removed -->
|
---|
| 59 |
|
---|
| 60 | <para>Configure the kernel via a menu-driven interface. BLFS has some
|
---|
| 61 | information regarding particular kernel configuration requirements of
|
---|
| 62 | packages outside of LFS at <ulink
|
---|
| 63 | url="&blfs-root;view/svn/longindex.html#kernel-config-index"/>:</para>
|
---|
| 64 |
|
---|
| 65 | <screen role="nodump"><userinput>make menuconfig</userinput></screen>
|
---|
| 66 |
|
---|
| 67 | <para>Alternatively, <command>make oldconfig</command> may be more
|
---|
| 68 | appropriate in some situations. See the <filename>README</filename>
|
---|
| 69 | file for more information.</para>
|
---|
| 70 |
|
---|
| 71 | <para>If desired, skip kernel configuration by copying the kernel
|
---|
| 72 | config file, <filename>.config</filename>, from the host system
|
---|
| 73 | (assuming it is available) to the unpacked <filename
|
---|
| 74 | class="directory">linux-&linux-version;</filename> directory. However,
|
---|
| 75 | we do not recommend this option. It is often better to explore all the
|
---|
| 76 | configuration menus and create the kernel configuration from
|
---|
| 77 | scratch.</para>
|
---|
| 78 |
|
---|
| 79 | <para>Compile the kernel image and modules:</para>
|
---|
| 80 |
|
---|
| 81 | <screen><userinput>make</userinput></screen>
|
---|
| 82 |
|
---|
| 83 | <para>If using kernel modules, an <filename>/etc/modprobe.conf</filename>
|
---|
| 84 | file may be needed. Information pertaining to modules and kernel
|
---|
| 85 | configuration is located in <xref linkend="ch-scripts-udev"/> and in the
|
---|
| 86 | kernel documentation in the <filename
|
---|
| 87 | class="directory">linux-&linux-version;/Documentation</filename> directory.
|
---|
| 88 | Also, <filename>modprobe.conf(5)</filename> may be of interest.</para>
|
---|
| 89 |
|
---|
| 90 | <para>Install the modules, if the kernel configuration uses them:</para>
|
---|
| 91 |
|
---|
| 92 | <screen><userinput>make modules_install</userinput></screen>
|
---|
| 93 |
|
---|
| 94 | <para>After kernel compilation is complete, additional steps are
|
---|
| 95 | required to complete the installation. Some files need to be copied to
|
---|
| 96 | the <filename class="directory">/boot</filename> directory.</para>
|
---|
| 97 |
|
---|
| 98 | <para>The path to the kernel image may vary depending on the platform
|
---|
| 99 | being used. The following command assumes an x86 architecture:</para>
|
---|
| 100 |
|
---|
| 101 | <screen><userinput>cp -v arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen>
|
---|
| 102 |
|
---|
| 103 | <para><filename>System.map</filename> is a symbol file for the kernel.
|
---|
| 104 | It maps the function entry points of every function in the kernel API,
|
---|
| 105 | as well as the addresses of the kernel data structures for the running
|
---|
| 106 | kernel. Issue the following command to install the map file:</para>
|
---|
| 107 |
|
---|
| 108 | <screen><userinput>cp -v System.map /boot/System.map-&linux-version;</userinput></screen>
|
---|
| 109 |
|
---|
| 110 | <para>The kernel configuration file <filename>.config</filename>
|
---|
| 111 | produced by the <command>make menuconfig</command> step
|
---|
| 112 | above contains all the configuration selections for the kernel
|
---|
| 113 | that was just compiled. It is a good idea to keep this file for future
|
---|
| 114 | reference:</para>
|
---|
| 115 |
|
---|
| 116 | <screen><userinput>cp -v .config /boot/config-&linux-version;</userinput></screen>
|
---|
| 117 |
|
---|
| 118 | <para>Install the documentation for the Linux kernel:</para>
|
---|
| 119 |
|
---|
| 120 | <screen>install -d /usr/share/doc/linux-&linux-version; &&
|
---|
| 121 | cp -r Documentation/* /usr/share/doc/linux-&linux-version;</screen>
|
---|
| 122 |
|
---|
| 123 | <para>It is important to note that the files in the kernel source
|
---|
| 124 | directory are not owned by <emphasis>root</emphasis>. Whenever a
|
---|
| 125 | package is unpacked as user <emphasis>root</emphasis> (like we did
|
---|
| 126 | inside chroot), the files have the user and group IDs of whatever
|
---|
| 127 | they were on the packager's computer. This is usually not a problem
|
---|
| 128 | for any other package to be installed because the source tree is
|
---|
| 129 | removed after the installation. However, the Linux source tree is
|
---|
| 130 | often retained for a long time. Because of this, there is a chance
|
---|
| 131 | that whatever user ID the packager used will be assigned to somebody
|
---|
| 132 | on the machine. That person would then have write access to the kernel
|
---|
| 133 | source.</para>
|
---|
| 134 |
|
---|
| 135 | <para>If the kernel source tree is going to be retained, run
|
---|
| 136 | <command>chown -R 0:0</command> on the <filename
|
---|
| 137 | class="directory">linux-&linux-version;</filename> directory to ensure
|
---|
| 138 | all files are owned by user <emphasis>root</emphasis>.</para>
|
---|
| 139 |
|
---|
| 140 | <warning>
|
---|
| 141 | <para>Some kernel documentation recommends creating a symlink from
|
---|
| 142 | <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
|
---|
| 143 | source directory. This is specific to kernels prior to the 2.6 series and
|
---|
| 144 | <emphasis>must not</emphasis> be created on an LFS system as it can cause
|
---|
| 145 | problems for packages you may wish to build once your base LFS system is
|
---|
| 146 | complete.</para>
|
---|
| 147 |
|
---|
| 148 | <para>Also, the headers in the system's
|
---|
| 149 | <filename class="directory">include</filename> directory should
|
---|
| 150 | <emphasis>always</emphasis> be the ones against which Glibc was compiled,
|
---|
| 151 | that is, the ones from the Linux-Libc-Headers package, and therefore, should
|
---|
| 152 | <emphasis>never</emphasis> be replaced by the kernel headers.</para>
|
---|
| 153 | </warning>
|
---|
| 154 |
|
---|
| 155 | </sect2>
|
---|
| 156 |
|
---|
| 157 |
|
---|
| 158 | <sect2 id="contents-kernel" role="content">
|
---|
| 159 | <title>Contents of Linux</title>
|
---|
| 160 |
|
---|
| 161 | <segmentedlist>
|
---|
| 162 | <segtitle>Installed files</segtitle>
|
---|
| 163 |
|
---|
| 164 | <seglistitem>
|
---|
| 165 | <seg>config-&linux-version;, lfskernel-&linux-version;, and
|
---|
| 166 | System.map-&linux-version;</seg>
|
---|
| 167 | </seglistitem>
|
---|
| 168 | </segmentedlist>
|
---|
| 169 |
|
---|
| 170 | <variablelist>
|
---|
| 171 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
| 172 | <?dbfo list-presentation="list"?>
|
---|
| 173 | <?dbhtml list-presentation="table"?>
|
---|
| 174 |
|
---|
| 175 | <varlistentry id="config">
|
---|
| 176 | <term><filename>config-&linux-version;</filename></term>
|
---|
| 177 | <listitem>
|
---|
| 178 | <para>Contains all the configuration selections for the kernel</para>
|
---|
| 179 | <indexterm zone="ch-bootable-kernel config">
|
---|
| 180 | <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
|
---|
| 181 | </indexterm>
|
---|
| 182 | </listitem>
|
---|
| 183 | </varlistentry>
|
---|
| 184 |
|
---|
| 185 | <varlistentry id="lfskernel">
|
---|
| 186 | <term><filename>lfskernel-&linux-version;</filename></term>
|
---|
| 187 | <listitem>
|
---|
| 188 | <para>The engine of the Linux system. When turning on the computer,
|
---|
| 189 | the kernel is the first part of the operating system that gets loaded.
|
---|
| 190 | It detects and initializes all components of the computer's hardware,
|
---|
| 191 | then makes these components available as a tree of files to the
|
---|
| 192 | software and turns a single CPU into a multitasking machine capable
|
---|
| 193 | of running scores of programs seemingly at the same time</para>
|
---|
| 194 | <indexterm zone="ch-bootable-kernel lfskernel">
|
---|
| 195 | <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
|
---|
| 196 | </indexterm>
|
---|
| 197 | </listitem>
|
---|
| 198 | </varlistentry>
|
---|
| 199 |
|
---|
| 200 | <varlistentry id="System.map">
|
---|
| 201 | <term><filename>System.map-&linux-version;</filename></term>
|
---|
| 202 | <listitem>
|
---|
| 203 | <para>A list of addresses and symbols; it maps the entry points and
|
---|
| 204 | addresses of all the functions and data structures in the
|
---|
| 205 | kernel</para>
|
---|
| 206 | <indexterm zone="ch-bootable-kernel System.map">
|
---|
| 207 | <primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
|
---|
| 208 | </indexterm>
|
---|
| 209 | </listitem>
|
---|
| 210 | </varlistentry>
|
---|
| 211 |
|
---|
| 212 | </variablelist>
|
---|
| 213 |
|
---|
| 214 | </sect2>
|
---|
| 215 |
|
---|
| 216 | </sect1>
|
---|