[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[b06ca36] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
[673b0d8] | 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
[b78c747] | 7 |
|
---|
[81fd230] | 8 | <sect1 id="ch-bootable-kernel" role="wrap">
|
---|
[b78c747] | 9 | <?dbhtml filename="kernel.html"?>
|
---|
| 10 |
|
---|
[e747759] | 11 | <sect1info condition="script">
|
---|
| 12 | <productname>linux</productname>
|
---|
| 13 | <productnumber>&linux-version;</productnumber>
|
---|
| 14 | <address>&linux-url;</address>
|
---|
| 15 | </sect1info>
|
---|
| 16 |
|
---|
[b78c747] | 17 | <title>Linux-&linux-version;</title>
|
---|
| 18 |
|
---|
| 19 | <indexterm zone="ch-bootable-kernel">
|
---|
| 20 | <primary sortas="a-Linux">Linux</primary>
|
---|
| 21 | </indexterm>
|
---|
| 22 |
|
---|
| 23 | <sect2 role="package">
|
---|
| 24 | <title/>
|
---|
| 25 |
|
---|
| 26 | <para>The Linux package contains the Linux kernel.</para>
|
---|
[673b0d8] | 27 |
|
---|
[b78c747] | 28 | <segmentedlist>
|
---|
| 29 | <segtitle>&buildtime;</segtitle>
|
---|
| 30 | <segtitle>&diskspace;</segtitle>
|
---|
[6370fa6] | 31 |
|
---|
[b78c747] | 32 | <seglistitem>
|
---|
[e4a5635] | 33 | <seg>&linux-ch8-sbu;</seg>
|
---|
| 34 | <seg>&linux-ch8-du;</seg>
|
---|
[b78c747] | 35 | </seglistitem>
|
---|
| 36 | </segmentedlist>
|
---|
[a001133] | 37 |
|
---|
[b78c747] | 38 | </sect2>
|
---|
[2081905] | 39 |
|
---|
[b78c747] | 40 | <sect2 role="installation">
|
---|
| 41 | <title>Installation of the kernel</title>
|
---|
[81fd230] | 42 |
|
---|
[b78c747] | 43 | <para>Building the kernel involves a few steps—configuration,
|
---|
| 44 | compilation, and installation. Read the <filename>README</filename> file
|
---|
| 45 | in the kernel source tree for alternative methods to the way this book
|
---|
| 46 | configures the kernel.</para>
|
---|
| 47 |
|
---|
| 48 | <para>Prepare for compilation by running the following command:</para>
|
---|
[b9e738a] | 49 |
|
---|
[0445a3d] | 50 | <screen><userinput remap="pre">make mrproper</userinput></screen>
|
---|
[b9e738a] | 51 |
|
---|
[b78c747] | 52 | <para>This ensures that the kernel tree is absolutely clean. The
|
---|
| 53 | kernel team recommends that this command be issued prior to each
|
---|
| 54 | kernel compilation. Do not rely on the source tree being clean after
|
---|
| 55 | un-tarring.</para>
|
---|
[d72e04a] | 56 |
|
---|
[fa21b3d] | 57 | <!-- Support for compiling a keymap into the kernel is deliberately removed -->
|
---|
[81fd230] | 58 |
|
---|
[764b5cf] | 59 | <para>Configure the kernel via a menu-driven interface. For general
|
---|
| 60 | information on kernel configuration see <ulink
|
---|
[e9ba8aa8] | 61 | url="&hints-root;kernel-configuration.txt"/>. BLFS has some information
|
---|
[764b5cf] | 62 | regarding particular kernel configuration requirements of packages outside
|
---|
| 63 | of LFS at <ulink
|
---|
[f873610] | 64 | url="&blfs-root;view/svn/longindex.html#kernel-config-index"/>. Additional
|
---|
| 65 | information about configuring and building the kernel can be found at
|
---|
| 66 | <ulink url="http://www.kroah.com/lkn/"/> </para>
|
---|
[e9ba8aa8] | 67 |
|
---|
[7e3a289] | 68 | <note><para>A good starting place for setting up the kernel configuration
|
---|
| 69 | is to run <command>make defconfig</command>. This will set the base
|
---|
| 70 | configuration to a good state that takes your current system architecture
|
---|
| 71 | into account.</para>
|
---|
| 72 |
|
---|
[cba2d4e] | 73 | <para>Be sure to enable or disable following features:</para>
|
---|
| 74 |
|
---|
[4e7d6a6] | 75 | <screen role="nodump">
|
---|
[cba2d4e] | 76 | Device Drivers --->
|
---|
[e9ba8aa8] | 77 | Generic Driver Options --->
|
---|
[c858814a] | 78 | () path to uevent helper [CONFIG_UEVENT_HELPER_PATH]
|
---|
| 79 | [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]</screen></note>
|
---|
[d13c6db] | 80 |
|
---|
| 81 | <para>There are several other options that may be desired depending
|
---|
[c858814a] | 82 | on the requirements for the system. For a list of options needed
|
---|
[d13c6db] | 83 | for BLFS packages, see the <ulink
|
---|
| 84 | url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
|
---|
| 85 | Index of Kernel Settings</ulink>
|
---|
| 86 | (&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index).</para>
|
---|
[4e7d6a6] | 87 |
|
---|
| 88 | <variablelist>
|
---|
| 89 | <title>The rationale for the above configuration items:</title>
|
---|
| 90 |
|
---|
| 91 | <varlistentry>
|
---|
| 92 | <term><parameter>path to uevent helper</parameter></term>
|
---|
| 93 | <listitem>
|
---|
| 94 | <para>Having an entry in this space will interfere with device
|
---|
| 95 | management when using udev/eudev. </para>
|
---|
| 96 | </listitem>
|
---|
| 97 | </varlistentry>
|
---|
| 98 |
|
---|
| 99 | <varlistentry>
|
---|
| 100 | <term><parameter>Maintain a devtmpfs</parameter></term>
|
---|
| 101 | <listitem>
|
---|
| 102 | <para>This will create automated device nodes which are populated by the
|
---|
| 103 | kernel, even without udev running. Udev then runs on top of this,
|
---|
| 104 | managing permissions and adding symlinks. This configuration
|
---|
| 105 | itme is required for all users of udev/eudev. </para>
|
---|
| 106 | </listitem>
|
---|
| 107 | </varlistentry>
|
---|
| 108 |
|
---|
| 109 | </variablelist>
|
---|
[2081905] | 110 |
|
---|
[2ccccf7] | 111 | <screen role="nodump"><userinput>make LANG=<replaceable><host_LANG_value></replaceable> LC_ALL= menuconfig</userinput></screen>
|
---|
| 112 |
|
---|
| 113 | <variablelist>
|
---|
| 114 | <title>The meaning of the make parameters:</title>
|
---|
| 115 |
|
---|
| 116 | <varlistentry>
|
---|
| 117 | <term><parameter>LANG=<host_LANG_value> LC_ALL=</parameter></term>
|
---|
| 118 | <listitem>
|
---|
| 119 | <para>This establishes the locale setting to the one used on the host.
|
---|
| 120 | This is needed for a proper menuconfig ncurses interface line
|
---|
| 121 | drawing on UTF-8 linux text console.</para>
|
---|
| 122 |
|
---|
| 123 | <para>Be sure to replace <replaceable><host_LANG_value></replaceable>
|
---|
| 124 | by the value of the <envar>$LANG</envar> variable from your host.
|
---|
[01670aad] | 125 | If not set, you could use instead the host's value of <envar>$LC_ALL</envar>
|
---|
[2ccccf7] | 126 | or <envar>$LC_CTYPE</envar>.</para>
|
---|
| 127 | </listitem>
|
---|
| 128 | </varlistentry>
|
---|
| 129 |
|
---|
| 130 | </variablelist>
|
---|
[2081905] | 131 |
|
---|
[b78c747] | 132 | <para>Alternatively, <command>make oldconfig</command> may be more
|
---|
| 133 | appropriate in some situations. See the <filename>README</filename>
|
---|
| 134 | file for more information.</para>
|
---|
| 135 |
|
---|
| 136 | <para>If desired, skip kernel configuration by copying the kernel
|
---|
| 137 | config file, <filename>.config</filename>, from the host system
|
---|
| 138 | (assuming it is available) to the unpacked <filename
|
---|
| 139 | class="directory">linux-&linux-version;</filename> directory. However,
|
---|
| 140 | we do not recommend this option. It is often better to explore all the
|
---|
| 141 | configuration menus and create the kernel configuration from
|
---|
| 142 | scratch.</para>
|
---|
| 143 |
|
---|
| 144 | <para>Compile the kernel image and modules:</para>
|
---|
[2081905] | 145 |
|
---|
[0445a3d] | 146 | <screen><userinput remap="make">make</userinput></screen>
|
---|
[2081905] | 147 |
|
---|
[b67f2d6] | 148 | <para>If using kernel modules, module configuration in <filename
|
---|
| 149 | class="directory">/etc/modprobe.d</filename> may be required.
|
---|
| 150 | Information pertaining to modules and kernel configuration is
|
---|
| 151 | located in <xref linkend="ch-scripts-udev"/> and in the kernel
|
---|
| 152 | documentation in the <filename
|
---|
[b78c747] | 153 | class="directory">linux-&linux-version;/Documentation</filename> directory.
|
---|
| 154 | Also, <filename>modprobe.conf(5)</filename> may be of interest.</para>
|
---|
[4b59d59] | 155 |
|
---|
[b78c747] | 156 | <para>Install the modules, if the kernel configuration uses them:</para>
|
---|
[2081905] | 157 |
|
---|
[0445a3d] | 158 | <screen><userinput remap="install">make modules_install</userinput></screen>
|
---|
[2081905] | 159 |
|
---|
[b78c747] | 160 | <para>After kernel compilation is complete, additional steps are
|
---|
| 161 | required to complete the installation. Some files need to be copied to
|
---|
| 162 | the <filename class="directory">/boot</filename> directory.</para>
|
---|
[81fd230] | 163 |
|
---|
[f9bcaec] | 164 | <para>The path to the kernel image may vary depending on the platform being
|
---|
| 165 | used. The filename below can be changed to suit your taste, but the stem of
|
---|
[fe1643e] | 166 | the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
|
---|
[f9bcaec] | 167 | the automatic setup of the boot process described in the next section. The
|
---|
| 168 | following command assumes an x86 architecture:</para>
|
---|
[2081905] | 169 |
|
---|
[fe1643e] | 170 | <screen><userinput remap="install">cp -v arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
|
---|
[2081905] | 171 |
|
---|
[b78c747] | 172 | <para><filename>System.map</filename> is a symbol file for the kernel.
|
---|
| 173 | It maps the function entry points of every function in the kernel API,
|
---|
| 174 | as well as the addresses of the kernel data structures for the running
|
---|
[2ca8941] | 175 | kernel. It is used as a resource when investigating kernel problems.
|
---|
[6028823] | 176 | Issue the following command to install the map file:</para>
|
---|
[81fd230] | 177 |
|
---|
[0445a3d] | 178 | <screen><userinput remap="install">cp -v System.map /boot/System.map-&linux-version;</userinput></screen>
|
---|
[2081905] | 179 |
|
---|
[b78c747] | 180 | <para>The kernel configuration file <filename>.config</filename>
|
---|
| 181 | produced by the <command>make menuconfig</command> step
|
---|
| 182 | above contains all the configuration selections for the kernel
|
---|
| 183 | that was just compiled. It is a good idea to keep this file for future
|
---|
| 184 | reference:</para>
|
---|
[81fd230] | 185 |
|
---|
[0445a3d] | 186 | <screen><userinput remap="install">cp -v .config /boot/config-&linux-version;</userinput></screen>
|
---|
[2081905] | 187 |
|
---|
[a1e18fa] | 188 | <para>Install the documentation for the Linux kernel:</para>
|
---|
| 189 |
|
---|
[0445a3d] | 190 | <screen><userinput remap="install">install -d /usr/share/doc/linux-&linux-version;
|
---|
[c226182] | 191 | cp -r Documentation/* /usr/share/doc/linux-&linux-version;</userinput></screen>
|
---|
[a1e18fa] | 192 |
|
---|
[b78c747] | 193 | <para>It is important to note that the files in the kernel source
|
---|
| 194 | directory are not owned by <emphasis>root</emphasis>. Whenever a
|
---|
| 195 | package is unpacked as user <emphasis>root</emphasis> (like we did
|
---|
| 196 | inside chroot), the files have the user and group IDs of whatever
|
---|
| 197 | they were on the packager's computer. This is usually not a problem
|
---|
| 198 | for any other package to be installed because the source tree is
|
---|
| 199 | removed after the installation. However, the Linux source tree is
|
---|
| 200 | often retained for a long time. Because of this, there is a chance
|
---|
| 201 | that whatever user ID the packager used will be assigned to somebody
|
---|
| 202 | on the machine. That person would then have write access to the kernel
|
---|
| 203 | source.</para>
|
---|
| 204 |
|
---|
| 205 | <para>If the kernel source tree is going to be retained, run
|
---|
| 206 | <command>chown -R 0:0</command> on the <filename
|
---|
| 207 | class="directory">linux-&linux-version;</filename> directory to ensure
|
---|
| 208 | all files are owned by user <emphasis>root</emphasis>.</para>
|
---|
| 209 |
|
---|
| 210 | <warning>
|
---|
| 211 | <para>Some kernel documentation recommends creating a symlink from
|
---|
| 212 | <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
|
---|
| 213 | source directory. This is specific to kernels prior to the 2.6 series and
|
---|
| 214 | <emphasis>must not</emphasis> be created on an LFS system as it can cause
|
---|
| 215 | problems for packages you may wish to build once your base LFS system is
|
---|
| 216 | complete.</para>
|
---|
[6c75ca3] | 217 | </warning>
|
---|
[b78c747] | 218 |
|
---|
[6c75ca3] | 219 | <warning>
|
---|
[4a32085] | 220 | <para>The headers in the system's <filename
|
---|
| 221 | class="directory">include</filename> directory (<filename
|
---|
| 222 | class="directory">/usr/include</filename>) should
|
---|
[b78c747] | 223 | <emphasis>always</emphasis> be the ones against which Glibc was compiled,
|
---|
[4a32085] | 224 | that is, the sanitised headers installed in <xref
|
---|
| 225 | linkend="ch-system-linux-headers"/>. Therefore, they should
|
---|
| 226 | <emphasis>never</emphasis> be replaced by either the raw kernel headers
|
---|
| 227 | or any other kernel sanitized headers.</para>
|
---|
[b78c747] | 228 | </warning>
|
---|
| 229 |
|
---|
| 230 | </sect2>
|
---|
| 231 |
|
---|
[200e466] | 232 | <sect2 id="conf-modprobe" role="configuration">
|
---|
| 233 | <title>Configuring Linux Module Load Order</title>
|
---|
| 234 |
|
---|
| 235 | <indexterm zone="conf-modprobe">
|
---|
[b67f2d6] | 236 | <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
|
---|
[200e466] | 237 | </indexterm>
|
---|
| 238 |
|
---|
[cdd87ad] | 239 | <para>Most of the time Linux modules are loaded automatically, but
|
---|
| 240 | sometimes it needs some specific direction. The program that loads
|
---|
| 241 | modules, <command>modprobe</command> or <command>insmod</command>, uses
|
---|
| 242 | <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
|
---|
| 243 | needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
|
---|
| 244 | uhci_hcd) have been built as modules, they will be loaded in the correct
|
---|
| 245 | order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
|
---|
| 246 | to avoid a warning being output at boot time.</para>
|
---|
[200e466] | 247 |
|
---|
[b67f2d6] | 248 | <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
|
---|
[200e466] | 249 | the following:</para>
|
---|
| 250 |
|
---|
[23ba7a00] | 251 | <screen><userinput>install -v -m755 -d /etc/modprobe.d
|
---|
[b67f2d6] | 252 | cat > /etc/modprobe.d/usb.conf << "EOF"
|
---|
| 253 | <literal># Begin /etc/modprobe.d/usb.conf
|
---|
[200e466] | 254 |
|
---|
| 255 | install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
|
---|
| 256 | install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
|
---|
| 257 |
|
---|
[b67f2d6] | 258 | # End /etc/modprobe.d/usb.conf</literal>
|
---|
[200e466] | 259 | EOF</userinput></screen>
|
---|
| 260 |
|
---|
| 261 | </sect2>
|
---|
| 262 |
|
---|
[b78c747] | 263 | <sect2 id="contents-kernel" role="content">
|
---|
| 264 | <title>Contents of Linux</title>
|
---|
| 265 |
|
---|
| 266 | <segmentedlist>
|
---|
| 267 | <segtitle>Installed files</segtitle>
|
---|
[fe05b08] | 268 | <segtitle>Installed directories</segtitle>
|
---|
[b78c747] | 269 |
|
---|
| 270 | <seglistitem>
|
---|
[2ca8941] | 271 | <seg>config-&linux-version;,
|
---|
[f5250e60] | 272 | vmlinuz-&linux-version;-lfs-&version;, and
|
---|
[b78c747] | 273 | System.map-&linux-version;</seg>
|
---|
[fe05b08] | 274 | <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
|
---|
[b78c747] | 275 | </seglistitem>
|
---|
| 276 | </segmentedlist>
|
---|
| 277 |
|
---|
| 278 | <variablelist>
|
---|
| 279 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
| 280 | <?dbfo list-presentation="list"?>
|
---|
| 281 | <?dbhtml list-presentation="table"?>
|
---|
| 282 |
|
---|
| 283 | <varlistentry id="config">
|
---|
| 284 | <term><filename>config-&linux-version;</filename></term>
|
---|
| 285 | <listitem>
|
---|
| 286 | <para>Contains all the configuration selections for the kernel</para>
|
---|
| 287 | <indexterm zone="ch-bootable-kernel config">
|
---|
| 288 | <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
|
---|
| 289 | </indexterm>
|
---|
| 290 | </listitem>
|
---|
| 291 | </varlistentry>
|
---|
| 292 |
|
---|
| 293 | <varlistentry id="lfskernel">
|
---|
[de0e7714] | 294 | <term><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
|
---|
[b78c747] | 295 | <listitem>
|
---|
| 296 | <para>The engine of the Linux system. When turning on the computer,
|
---|
| 297 | the kernel is the first part of the operating system that gets loaded.
|
---|
| 298 | It detects and initializes all components of the computer's hardware,
|
---|
| 299 | then makes these components available as a tree of files to the
|
---|
| 300 | software and turns a single CPU into a multitasking machine capable
|
---|
| 301 | of running scores of programs seemingly at the same time</para>
|
---|
| 302 | <indexterm zone="ch-bootable-kernel lfskernel">
|
---|
| 303 | <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
|
---|
| 304 | </indexterm>
|
---|
| 305 | </listitem>
|
---|
| 306 | </varlistentry>
|
---|
| 307 |
|
---|
| 308 | <varlistentry id="System.map">
|
---|
| 309 | <term><filename>System.map-&linux-version;</filename></term>
|
---|
| 310 | <listitem>
|
---|
| 311 | <para>A list of addresses and symbols; it maps the entry points and
|
---|
| 312 | addresses of all the functions and data structures in the
|
---|
| 313 | kernel</para>
|
---|
| 314 | <indexterm zone="ch-bootable-kernel System.map">
|
---|
| 315 | <primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
|
---|
| 316 | </indexterm>
|
---|
| 317 | </listitem>
|
---|
| 318 | </varlistentry>
|
---|
| 319 |
|
---|
| 320 | </variablelist>
|
---|
| 321 |
|
---|
| 322 | </sect2>
|
---|
[673b0d8] | 323 |
|
---|
[6370fa6] | 324 | </sect1>
|
---|