source: chapter08/kernel.xml@ 997d961

multilib-10.1 multilib-before-cross
Last change on this file since 997d961 was 997d961, checked in by Thomas Trepl <thomas@…>, 3 years ago

MultiLib: Merge changes from trunk

git-svn-id: 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 18.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-ch8-sbu;</seg>
34 <seg>&linux-ch8-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 <!-- Support for compiling a keymap into the kernel is deliberately removed -->
59 <para>Configure the kernel via a menu-driven interface. For general
60 information on kernel configuration see <ulink
61 url="&hints-root;kernel-configuration.txt"/>. BLFS has some information
62 regarding particular kernel configuration requirements of packages outside
63 of LFS at <ulink
64 url="&blfs-book;longindex.html#kernel-config-index"/>. Additional
65 information about configuring and building the kernel can be found at
66 <ulink url=""/> </para>
68 <note>
70 <para>A good starting place for setting up the kernel configuration is to
71 run <command>make defconfig</command>. This will set the base
72 configuration to a good state that takes your current system architecture
73 into account.</para>
75 <para>Be sure to enable/disable/set the following features or the system might
76 not work correctly or boot at all:</para>
78 <screen role="nodump" revision="sysv">
79Device Drivers ---&gt;
80 Generic Driver Options ---&gt;
81 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
82 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
84Kernel hacking ---&gt;
85 Choose kernel unwinder (Frame pointer unwinder) ---&gt; [CONFIG_UNWINDER_FRAME_POINTER]</screen>
87 <screen role="nodump" revision="systemd">
88General setup -->
89 [*] Control Group support [CONFIG_CGROUPS]
90 [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED]
91 [*] Configure standard kernel features (expert users) [CONFIG_EXPERT] ---&gt;
92 [*] open by fhandle syscalls [CONFIG_FHANDLE]
93 [ ] Auditing support [CONFIG_AUDIT]
94Processor type and features ---&gt;
95 [*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
96Firmware Drivers ---&gt;
97 [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
98Networking support ---&gt;
99 Networking options ---&gt;
100 &lt;*&gt; The IPv6 protocol [CONFIG_IPV6]
101Device Drivers ---&gt;
102 Generic Driver Options ---&gt;
103 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
104 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
105 Firmware Loader ---&gt;
106 [ ] Enable the firmware sysfs fallback mechanism [CONFIG_FW_LOADER_USER_HELPER]
107File systems ---&gt;
108 [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
109 &lt;*&gt; Kernel automounter support (supports v3, v4, and v5) [CONFIG_AUTOFS_FS]
110 Pseudo filesystems ---&gt;
111 [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]
112 [*] Tmpfs extended attributes [CONFIG_TMPFS_XATTR]</screen>
114 </note>
116 <note revision="systemd">
117 <para>While "The IPv6 Protocol" is not strictly
118 required, it is highly recommended by the systemd developers.</para>
119 </note>
121 <para revision="sysv">There are several other options that may be desired
122 depending on the requirements for the system. For a list of options needed
123 for BLFS packages, see the <ulink
124 url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
125 Index of Kernel Settings</ulink>
126 (&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index).</para>
128 <note>
129 <para>If your host hardware is using UEFI, then the 'make defconfig'
130 above should automatically add in some EFI-related kernel options.</para>
132 <para>In order to allow your LFS kernel to be booted from within your
133 host's UEFI boot environment, your kernel must have this option
134 selected:</para>
136<screen role="nodump">Processor type and features ---&gt;
137 [*] EFI stub support [CONFIG_EFI_STUB]</screen>
139 <para>A fuller description of managing UEFI environments from within LFS
140 is covered by the lfs-uefi.txt hint at
141 <ulink
142 url="&hints-root;lfs-uefi.txt"/>.
143 </para>
144 </note>
146 <note arch="ml_32,ml_x32,ml_all">
147 <para>
148 Running a multilib system means also that the kernel has to be
149 configured proper. It is required that the kernel is able to
150 identify and start binaries compiled for different architectures
151 than the default. Setup the required parameter in the kernel
152 config:
153 </para>
154<screen>Binary Emulations ---&gt;
155 [*] IA32 Emulation
156 &lt;M&gt; IA32 a.out support
157 [*] x32 ABI for 64-bit mode
159 <para>Make sure that the option
160 'IA32 Emulation' is set if you built support for the 32bit ABI.
161 If you selected the x32 ABI or built support for both, also select
162 'x32 ABI for 64-bit mode'. The option 'IA32 a.out support' is
163 optional.
164 </para>
165 </note>
167 <variablelist>
168 <title>The rationale for the above configuration items:</title>
170 <varlistentry>
171 <term><parameter>Support for uevent helper</parameter></term>
172 <listitem>
173 <para>Having this option set may interfere with device
174 management when using Udev/Eudev. </para>
175 </listitem>
176 </varlistentry>
178 <varlistentry>
179 <term><parameter>Maintain a devtmpfs</parameter></term>
180 <listitem>
181 <para>This will create automated device nodes which are populated by the
182 kernel, even without Udev running. Udev then runs on top of this,
183 managing permissions and adding symlinks. This configuration
184 item is required for all users of Udev/Eudev.</para>
185 </listitem>
186 </varlistentry>
188 </variablelist>
190<screen role="nodump"><userinput>make menuconfig</userinput></screen>
192 <variablelist>
193 <title>The meaning of optional make environment variables:</title>
195 <varlistentry>
196 <term><parameter>LANG=&lt;host_LANG_value&gt; LC_ALL=</parameter></term>
197 <listitem>
198 <para>This establishes the locale setting to the one used on the
199 host. This may be needed for a proper menuconfig ncurses interface
200 line drawing on a UTF-8 linux text console.</para>
202 <para>If used, be sure to replace
203 <replaceable>&lt;host_LANG_value&gt;</replaceable> by the value of
204 the <envar>$LANG</envar> variable from your host. You can
205 alternatively use instead the host's value of <envar>$LC_ALL</envar>
206 or <envar>$LC_CTYPE</envar>.</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 arch="default" revision="sysv"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
262<screen arch="ml_32,ml_x32,ml_all" revision="sysv"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;-multilib</userinput></screen>
264<screen arch="default" revision="systemd"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;</userinput></screen>
266<screen arch="ml_32,ml_x32,ml_all" revision="systemd"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;-multilib</userinput></screen>
269 <para><filename></filename> is a symbol file for the kernel.
270 It maps the function entry points of every function in the kernel API,
271 as well as the addresses of the kernel data structures for the running
272 kernel. It is used as a resource when investigating kernel problems.
273 Issue the following command to install the map file:</para>
275<screen><userinput remap="install">cp -iv /boot/;</userinput></screen>
277 <para>The kernel configuration file <filename>.config</filename>
278 produced by the <command>make menuconfig</command> step
279 above contains all the configuration selections for the kernel
280 that was just compiled. It is a good idea to keep this file for future
281 reference:</para>
283<screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
285 <para>Install the documentation for the Linux kernel:</para>
287<screen><userinput remap="install">install -d /usr/share/doc/linux-&linux-version;
288cp -r Documentation/* /usr/share/doc/linux-&linux-version;</userinput></screen>
290 <para>It is important to note that the files in the kernel source
291 directory are not owned by <emphasis>root</emphasis>. Whenever a
292 package is unpacked as user <emphasis>root</emphasis> (like we did
293 inside chroot), the files have the user and group IDs of whatever
294 they were on the packager's computer. This is usually not a problem
295 for any other package to be installed because the source tree is
296 removed after the installation. However, the Linux source tree is
297 often retained for a long time. Because of this, there is a chance
298 that whatever user ID the packager used will be assigned to somebody
299 on the machine. That person would then have write access to the kernel
300 source.</para>
302 <note>
303 <para>In many cases, the configuration of the kernel will need to be
304 updated for packages that will be installed later in BLFS. Unlike
305 other packages, it is not necessary to remove the kernel source tree
306 after the newly built kernel is installed.</para>
308 <para>If the kernel source tree is going to be retained, run
309 <command>chown -R 0:0</command> on the <filename
310 class="directory">linux-&linux-version;</filename> directory to ensure
311 all files are owned by user <emphasis>root</emphasis>.</para>
312 </note>
314 <warning>
315 <para>Some kernel documentation recommends creating a symlink from
316 <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
317 source directory. This is specific to kernels prior to the 2.6 series and
318 <emphasis>must not</emphasis> be created on an LFS system as it can cause
319 problems for packages you may wish to build once your base LFS system is
320 complete.</para>
321 </warning>
323 <warning>
324 <para>The headers in the system's <filename
325 class="directory">include</filename> directory (<filename
326 class="directory">/usr/include</filename>) should
327 <emphasis>always</emphasis> be the ones against which Glibc was compiled,
328 that is, the sanitised headers installed in <xref
329 linkend="ch-system-linux-headers"/>. Therefore, they should
330 <emphasis>never</emphasis> be replaced by either the raw kernel headers
331 or any other kernel sanitized headers.</para>
332 </warning>
334 </sect2>
336 <sect2 id="conf-modprobe" role="configuration">
337 <title>Configuring Linux Module Load Order</title>
339 <indexterm zone="conf-modprobe">
340 <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
341 </indexterm>
343 <para>Most of the time Linux modules are loaded automatically, but
344 sometimes it needs some specific direction. The program that loads
345 modules, <command>modprobe</command> or <command>insmod</command>, uses
346 <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
347 needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
348 uhci_hcd) have been built as modules, they will be loaded in the correct
349 order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
350 to avoid a warning being output at boot time.</para>
352 <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
353 the following:</para>
355<screen><userinput>install -v -m755 -d /etc/modprobe.d
356cat &gt; /etc/modprobe.d/usb.conf &lt;&lt; "EOF"
357<literal># Begin /etc/modprobe.d/usb.conf
359install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
360install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
362# End /etc/modprobe.d/usb.conf</literal>
365 </sect2>
367 <sect2 id="contents-kernel" role="content">
368 <title>Contents of Linux</title>
370 <segmentedlist>
371 <segtitle>Installed files</segtitle>
372 <segtitle>Installed directories</segtitle>
374 <seglistitem>
375 <seg>config-&linux-version;,
376 <phrase arch="default" revision="sysv">vmlinuz-&linux-version;-lfs-&version;,</phrase>
377 <phrase arch="default" revision="systemd">vmlinuz-&linux-version;-lfs-&versiond;,</phrase>
378 <phrase arch="ml_32,ml_x32,ml_all" revision="sysv">vmlinuz-&linux-version;-lfs-&version;-multilib,</phrase>
379 <phrase arch="ml_32,ml_x32,ml_all" revision="systemd">vmlinuz-&linux-version;-lfs-&versiond;-multilib,</phrase>
380 and;</seg>
381 <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
382 </seglistitem>
383 </segmentedlist>
385 <variablelist>
386 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
387 <?dbfo list-presentation="list"?>
388 <?dbhtml list-presentation="table"?>
390 <varlistentry id="config">
391 <term><filename>config-&linux-version;</filename></term>
392 <listitem>
393 <para>Contains all the configuration selections for the kernel</para>
394 <indexterm zone="ch-bootable-kernel config">
395 <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
396 </indexterm>
397 </listitem>
398 </varlistentry>
400 <varlistentry id="lfskernel">
401 <term revision="sysv"><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
402 <term revision="systemd"><filename>vmlinuz-&linux-version;-lfs-&versiond;</filename></term>
403 <listitem>
404 <para>The engine of the Linux system. When turning on the computer,
405 the kernel is the first part of the operating system that gets loaded.
406 It detects and initializes all components of the computer's hardware,
407 then makes these components available as a tree of files to the
408 software and turns a single CPU into a multitasking machine capable
409 of running scores of programs seemingly at the same time</para>
410 <indexterm zone="ch-bootable-kernel lfskernel">
411 <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
412 </indexterm>
413 </listitem>
414 </varlistentry>
416 <varlistentry id="">
417 <term><filename>;</filename></term>
418 <listitem>
419 <para>A list of addresses and symbols; it maps the entry points and
420 addresses of all the functions and data structures in the
421 kernel</para>
422 <indexterm zone="ch-bootable-kernel">
423 <primary sortas="e-/boot/">/boot/;</primary>
424 </indexterm>
425 </listitem>
426 </varlistentry>
428 </variablelist>
430 </sect2>
Note: See TracBrowser for help on using the repository browser.