source: chapter10/kernel.xml@ 384c707

Last change on this file since 384c707 was 384c707, checked in by Thomas Trepl (Moody) <thomas@…>, 9 months ago

Add more info about kernel requirements for multilib

  • Property mode set to 100644
File size: 17.4 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
8<sect1 id="ch-bootable-kernel" role="wrap">
9 <?dbhtml filename="kernel.html"?>
11 <sect1info condition="script">
12 <productname>kernel</productname>
13 <productnumber>&linux-version;</productnumber>
14 <address>&linux-url;</address>
15 </sect1info>
17 <title>Linux-&linux-version;</title>
19 <indexterm zone="ch-bootable-kernel">
20 <primary sortas="a-Linux">Linux</primary>
21 </indexterm>
23 <sect2 role="package">
24 <title/>
26 <para>The Linux package contains the Linux kernel.</para>
28 <segmentedlist>
29 <segtitle>&buildtime;</segtitle>
30 <segtitle>&diskspace;</segtitle>
32 <seglistitem>
33 <seg>&linux-knl-sbu;</seg>
34 <seg>&linux-knl-du;</seg>
35 </seglistitem>
36 </segmentedlist>
38 </sect2>
40 <sect2 role="installation">
41 <title>Installation of the kernel</title>
43 <para>Building the kernel involves a few steps&mdash;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>
48 <para>Prepare for compilation by running the following command:</para>
50<screen><userinput remap="pre">make mrproper</userinput></screen>
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>
57 <para>There are several ways to configure the kernel options. Usually,
58 This is done through a menu-driven interface, for example:</para>
60<screen role="nodump"><userinput>make menuconfig</userinput></screen>
62 <variablelist>
63 <title>The meaning of optional make environment variables:</title>
65 <varlistentry>
66 <term><parameter>LANG=&lt;host_LANG_value&gt; LC_ALL=</parameter></term>
67 <listitem>
68 <para>This establishes the locale setting to the one used on the
69 host. This may be needed for a proper menuconfig ncurses interface
70 line drawing on a UTF-8 linux text console.</para>
72 <para>If used, be sure to replace
73 <replaceable>&lt;host_LANG_value&gt;</replaceable> by the value of
74 the <envar>$LANG</envar> variable from your host. You can
75 alternatively use instead the host's value of <envar>$LC_ALL</envar>
76 or <envar>$LC_CTYPE</envar>.</para>
77 </listitem>
78 </varlistentry>
80 <varlistentry>
81 <term><command>make menuconfig</command></term>
82 <listitem>
83 <para>This launches an ncurses menu-driven interface. For other
84 (graphical) interfaces, type <command>make help</command>.</para>
85 </listitem>
86 </varlistentry>
87 </variablelist>
89 <!-- Support for compiling a keymap into the kernel is deliberately removed -->
91 <para>For general information on kernel configuration see <ulink
92 url="&hints-root;kernel-configuration.txt"/>. BLFS has some information
93 regarding particular kernel configuration requirements of packages outside
94 of LFS at <ulink
95 url="&blfs-book;longindex.html#kernel-config-index"/>. Additional
96 information about configuring and building the kernel can be found at
97 <ulink url=""/> </para>
99 <note>
100 <para>A good starting place for setting up the kernel configuration is to
101 run <command>make defconfig</command>. This will set the base
102 configuration to a good state that takes your current system architecture
103 into account.</para>
105 <para>Be sure to enable/disable/set the following features or the system might
106 not work correctly or boot at all:</para>
108 <screen role="nodump" revision="sysv">Device Drivers ---&gt;
109 Generic Driver Options ---&gt;
110 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
111 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]</screen>
113 <screen role="nodump" revision="systemd">General setup -->
114 [ ] Auditing Support [CONFIG_AUDIT]
115 [*] Control Group support [CONFIG_CGROUPS]
116 [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED]
117 [*] Configure standard kernel features (expert users) [CONFIG_EXPERT] ---&gt;
118 [*] open by fhandle syscalls [CONFIG_FHANDLE]
119Firmware Drivers ---&gt;
120 [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
121General architecture-dependent options ---&gt;
122 [*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
123Networking support ---&gt;
124 Networking options ---&gt;
125 &lt;*&gt; The IPv6 protocol [CONFIG_IPV6]
126Device Drivers ---&gt;
127 Generic Driver Options ---&gt;
128 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
129 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
130 Firmware Loader ---&gt;
131 [ ] Enable the firmware sysfs fallback mechanism [CONFIG_FW_LOADER_USER_HELPER]
132File systems ---&gt;
133 [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
134 Pseudo filesystems ---&gt;
135 [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen>
136 </note>
138 <note revision="systemd">
139 <para>While "The IPv6 Protocol" is not strictly
140 required, it is highly recommended by the systemd developers.</para>
141 </note>
143 <para revision="sysv">There are several other options that may be desired
144 depending on the requirements for the system. For a list of options needed
145 for BLFS packages, see the <ulink
146 url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
147 Index of Kernel Settings</ulink>
148 (&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index).</para>
150 <note>
151 <para>If your host hardware is using UEFI and you wish to boot the
152 LFS system with it, you should adjust some kernel configuration
153 following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel">
154 the BLFS page</ulink>.</para>
155 </note>
157 <note arch="ml_32,ml_x32,ml_all">
158 <para>
159 The kernel on a multilib system needs to be able to
160 identify and start binaries compiled for different architectures
161 than the default.
162 </para>
164 <para arch="ml_32,ml_all">
165 If support for any 32bit ABI was built, make sure that the option
166 "IA32 Emulation" is selected. The option 'IA32 a.out support' is
167 optional.
168 </para>
170 <para arch="ml_x32,ml_all">
171 If support for the x32bit ABI was built, make sure that the option
172 "x32 ABI for 64-bit mode" is selected.
173 </para>
175<screen arch="ml_32">Binary Emulations ---&gt;
176 [*] IA32 Emulation [CONFIG_IA32_EMULATION]
177 &lt;M&gt; IA32 a.out support [CONFIG_IA32_AOUT]
179<screen arch="ml_x32">Binary Emulations ---&gt;
180 [*] x32 ABI for 64-bit mode [CONFIG_X86_X32]
182<screen arch="ml_all">Binary Emulations ---&gt;
183 [*] IA32 Emulation [CONFIG_IA32_EMULATION]
184 &lt;M&gt; IA32 a.out support [CONFIG_IA32_AOUT]
185 [*] x32 ABI for 64-bit mode [CONFIG_X86_X32]
187 </note>
189 <variablelist>
190 <title>The rationale for the above configuration items:</title>
192 <varlistentry>
193 <term><parameter>Support for uevent helper</parameter></term>
194 <listitem>
195 <para>Having this option set may interfere with device
196 management when using Udev/Eudev. </para>
197 </listitem>
198 </varlistentry>
200 <varlistentry>
201 <term><parameter>Maintain a devtmpfs</parameter></term>
202 <listitem>
203 <para>This will create automated device nodes which are populated by the
204 kernel, even without Udev running. Udev then runs on top of this,
205 managing permissions and adding symlinks. This configuration
206 item is required for all users of Udev/Eudev.</para>
207 </listitem>
208 </varlistentry>
210 </variablelist>
212 <para>Alternatively, <command>make oldconfig</command> may be more
213 appropriate in some situations. See the <filename>README</filename>
214 file for more information.</para>
216 <para>If desired, skip kernel configuration by copying the kernel
217 config file, <filename>.config</filename>, from the host system
218 (assuming it is available) to the unpacked <filename
219 class="directory">linux-&linux-version;</filename> directory. However,
220 we do not recommend this option. It is often better to explore all the
221 configuration menus and create the kernel configuration from
222 scratch.</para>
224 <para>Compile the kernel image and modules:</para>
226<screen><userinput remap="make">make</userinput></screen>
228 <para>If using kernel modules, module configuration in <filename
229 class="directory">/etc/modprobe.d</filename> may be required.
230 Information pertaining to modules and kernel configuration is
231 located in <xref linkend="ch-config-udev"/> and in the kernel
232 documentation in the <filename
233 class="directory">linux-&linux-version;/Documentation</filename> directory.
234 Also, <filename>modprobe.d(5)</filename> may be of interest.</para>
236 <para>Unless module support has been disabled in the kernel configuration,
237 install the modules with:</para>
239<screen><userinput remap="install">make modules_install</userinput></screen>
241 <para>After kernel compilation is complete, additional steps are
242 required to complete the installation. Some files need to be copied to
243 the <filename class="directory">/boot</filename> directory.</para>
245 <caution>
246 <para>If the host system has a separate /boot partition, the files copied
247 below should go there. The easiest way to do that is to bind /boot on the
248 host (outside chroot) to /mnt/lfs/boot before proceeding. As the root
249 user in the <emphasis>host system</emphasis>:</para>
251<screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen>
252 </caution>
254 <para>The path to the kernel image may vary depending on the platform being
255 used. The filename below can be changed to suit your taste, but the stem of
256 the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
257 the automatic setup of the boot process described in the next section. The
258 following command assumes an x86 architecture:</para>
260<screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
262 <para><filename></filename> is a symbol file for the kernel.
263 It maps the function entry points of every function in the kernel API,
264 as well as the addresses of the kernel data structures for the running
265 kernel. It is used as a resource when investigating kernel problems.
266 Issue the following command to install the map file:</para>
268<screen><userinput remap="install">cp -iv /boot/;</userinput></screen>
270 <para>The kernel configuration file <filename>.config</filename>
271 produced by the <command>make menuconfig</command> step
272 above contains all the configuration selections for the kernel
273 that was just compiled. It is a good idea to keep this file for future
274 reference:</para>
276<screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
278 <para>Install the documentation for the Linux kernel:</para>
280<screen><userinput remap="install">install -d /usr/share/doc/linux-&linux-version;
281cp -r Documentation/* /usr/share/doc/linux-&linux-version;</userinput></screen>
283 <para>It is important to note that the files in the kernel source
284 directory are not owned by <emphasis>root</emphasis>. Whenever a
285 package is unpacked as user <emphasis>root</emphasis> (like we did
286 inside chroot), the files have the user and group IDs of whatever
287 they were on the packager's computer. This is usually not a problem
288 for any other package to be installed because the source tree is
289 removed after the installation. However, the Linux source tree is
290 often retained for a long time. Because of this, there is a chance
291 that whatever user ID the packager used will be assigned to somebody
292 on the machine. That person would then have write access to the kernel
293 source.</para>
295 <note>
296 <para>In many cases, the configuration of the kernel will need to be
297 updated for packages that will be installed later in BLFS. Unlike
298 other packages, it is not necessary to remove the kernel source tree
299 after the newly built kernel is installed.</para>
301 <para>If the kernel source tree is going to be retained, run
302 <command>chown -R 0:0</command> on the <filename
303 class="directory">linux-&linux-version;</filename> directory to ensure
304 all files are owned by user <emphasis>root</emphasis>.</para>
305 </note>
307 <warning>
308 <para>Some kernel documentation recommends creating a symlink from
309 <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
310 source directory. This is specific to kernels prior to the 2.6 series and
311 <emphasis>must not</emphasis> be created on an LFS system as it can cause
312 problems for packages you may wish to build once your base LFS system is
313 complete.</para>
314 </warning>
316 <warning>
317 <para>The headers in the system's <filename
318 class="directory">include</filename> directory (<filename
319 class="directory">/usr/include</filename>) should
320 <emphasis>always</emphasis> be the ones against which Glibc was compiled,
321 that is, the sanitised headers installed in <xref
322 linkend="ch-tools-linux-headers"/>. Therefore, they should
323 <emphasis>never</emphasis> be replaced by either the raw kernel headers
324 or any other kernel sanitized headers.</para>
325 </warning>
327 </sect2>
329 <sect2 id="conf-modprobe" role="configuration">
330 <title>Configuring Linux Module Load Order</title>
332 <indexterm zone="conf-modprobe">
333 <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
334 </indexterm>
336 <para>Most of the time Linux modules are loaded automatically, but
337 sometimes it needs some specific direction. The program that loads
338 modules, <command>modprobe</command> or <command>insmod</command>, uses
339 <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
340 needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
341 uhci_hcd) have been built as modules, they will be loaded in the correct
342 order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
343 to avoid a warning being output at boot time.</para>
345 <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
346 the following:</para>
348<screen><userinput>install -v -m755 -d /etc/modprobe.d
349cat &gt; /etc/modprobe.d/usb.conf &lt;&lt; "EOF"
350<literal># Begin /etc/modprobe.d/usb.conf
352install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
353install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
355# End /etc/modprobe.d/usb.conf</literal>
358 </sect2>
360 <sect2 id="contents-kernel" role="content">
361 <title>Contents of Linux</title>
363 <segmentedlist>
364 <segtitle>Installed files</segtitle>
365 <segtitle>Installed directories</segtitle>
367 <seglistitem>
368 <seg>config-&linux-version;,
369 vmlinuz-&linux-version;-lfs-&version;,
370 and;</seg>
371 <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
372 </seglistitem>
373 </segmentedlist>
375 <variablelist>
376 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
377 <?dbfo list-presentation="list"?>
378 <?dbhtml list-presentation="table"?>
380 <varlistentry id="config">
381 <term><filename>config-&linux-version;</filename></term>
382 <listitem>
383 <para>Contains all the configuration selections for the kernel</para>
384 <indexterm zone="ch-bootable-kernel config">
385 <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
386 </indexterm>
387 </listitem>
388 </varlistentry>
390 <varlistentry id="lfskernel">
391 <term><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
392 <listitem>
393 <para>The engine of the Linux system. When turning on the computer,
394 the kernel is the first part of the operating system that gets loaded.
395 It detects and initializes all components of the computer's hardware,
396 then makes these components available as a tree of files to the
397 software and turns a single CPU into a multitasking machine capable
398 of running scores of programs seemingly at the same time</para>
399 <indexterm zone="ch-bootable-kernel lfskernel">
400 <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
401 </indexterm>
402 </listitem>
403 </varlistentry>
405 <varlistentry id="">
406 <term><filename>;</filename></term>
407 <listitem>
408 <para>A list of addresses and symbols; it maps the entry points and
409 addresses of all the functions and data structures in the
410 kernel</para>
411 <indexterm zone="ch-bootable-kernel">
412 <primary sortas="e-/boot/">/boot/;</primary>
413 </indexterm>
414 </listitem>
415 </varlistentry>
417 </variablelist>
419 </sect2>
Note: See TracBrowser for help on using the repository browser.