[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">
|
---|
[6070f51] | 12 | <productname>kernel</productname>
|
---|
[e747759] | 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
|
---|
[0ee07e5] | 64 | url="&blfs-book;longindex.html#kernel-config-index"/>. Additional
|
---|
[f873610] | 65 | information about configuring and building the kernel can be found at
|
---|
| 66 | <ulink url="http://www.kroah.com/lkn/"/> </para>
|
---|
[e9ba8aa8] | 67 |
|
---|
[1118b17] | 68 | <note>
|
---|
| 69 |
|
---|
| 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>
|
---|
[7e3a289] | 74 |
|
---|
[25332b5] | 75 | <para>Be sure to enable/disable/set the following features or the system might
|
---|
[1118b17] | 76 | not work correctly or boot at all:</para>
|
---|
[cba2d4e] | 77 |
|
---|
[1118b17] | 78 | <screen role="nodump" revision="sysv">
|
---|
[cba2d4e] | 79 | Device Drivers --->
|
---|
[e9ba8aa8] | 80 | Generic Driver Options --->
|
---|
[040ecb6] | 81 | [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
|
---|
[25332b5] | 82 | [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
|
---|
| 83 |
|
---|
| 84 | Kernel hacking --->
|
---|
| 85 | Choose kernel unwinder (Frame pointer unwinder) ---> [CONFIG_UNWINDER_FRAME_POINTER]</screen>
|
---|
[1118b17] | 86 |
|
---|
| 87 | <screen role="nodump" revision="systemd">
|
---|
[de5d133] | 88 | General setup -->
|
---|
[840b7db] | 89 | [*] Control Group support [CONFIG_CGROUPS]
|
---|
[de5d133] | 90 | [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED]
|
---|
[6cf2844] | 91 | [*] Configure standard kernel features (expert users) [CONFIG_EXPERT] --->
|
---|
| 92 | [*] open by fhandle syscalls [CONFIG_FHANDLE]
|
---|
[de5d133] | 93 | [ ] Auditing support [CONFIG_AUDIT]
|
---|
[1118b17] | 94 | Processor type and features --->
|
---|
[de5d133] | 95 | [*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
|
---|
[6cf2844] | 96 | Firmware Drivers --->
|
---|
| 97 | [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
|
---|
[1118b17] | 98 | Networking support --->
|
---|
| 99 | Networking options --->
|
---|
[de5d133] | 100 | <*> The IPv6 protocol [CONFIG_IPV6]
|
---|
[1118b17] | 101 | Device Drivers --->
|
---|
| 102 | Generic Driver Options --->
|
---|
[de5d133] | 103 | [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
|
---|
| 104 | [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
|
---|
[6cf2844] | 105 | Firmware Loader --->
|
---|
| 106 | [ ] Enable the firmware sysfs fallback mechanism [CONFIG_FW_LOADER_USER_HELPER]
|
---|
[1118b17] | 107 | File systems --->
|
---|
[de5d133] | 108 | [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
|
---|
[6cf2844] | 109 | <*> Kernel automounter support (supports v3, v4, and v5) [CONFIG_AUTOFS_FS]
|
---|
[1118b17] | 110 | Pseudo filesystems --->
|
---|
[de5d133] | 111 | [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]
|
---|
[840b7db] | 112 | [*] Tmpfs extended attributes [CONFIG_TMPFS_XATTR]</screen>
|
---|
[1118b17] | 113 | </note>
|
---|
| 114 |
|
---|
| 115 | <note revision="systemd">
|
---|
| 116 | <para>While "The IPv6 Protocol" is not strictly
|
---|
| 117 | required, it is highly recommended by the systemd developers.</para>
|
---|
| 118 | </note>
|
---|
| 119 |
|
---|
| 120 | <para revision="sysv">There are several other options that may be desired
|
---|
| 121 | depending on the requirements for the system. For a list of options needed
|
---|
| 122 | for BLFS packages, see the <ulink
|
---|
| 123 | url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
|
---|
| 124 | Index of Kernel Settings</ulink>
|
---|
[d13c6db] | 125 | (&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index).</para>
|
---|
[4e7d6a6] | 126 |
|
---|
[8e65a6a] | 127 | <note>
|
---|
| 128 | <para>If your host hardware is using UEFI, then the 'make defconfig'
|
---|
| 129 | above should automatically add in some EFI-related kernel options.</para>
|
---|
| 130 |
|
---|
| 131 | <para>In order to allow your LFS kernel to be booted from within your
|
---|
| 132 | host's UEFI boot environment, your kernel must have this option
|
---|
| 133 | selected:</para>
|
---|
| 134 |
|
---|
| 135 | <screen role="nodump">Processor type and features --->
|
---|
| 136 | [*] EFI stub support [CONFIG_EFI_STUB]</screen>
|
---|
| 137 |
|
---|
| 138 | <para>A fuller description of managing UEFI environments from within LFS
|
---|
| 139 | is covered by the lfs-uefi.txt hint at
|
---|
| 140 | <ulink
|
---|
[adbc3e5] | 141 | url="&hints-root;lfs-uefi.txt"/>.
|
---|
[8e65a6a] | 142 | </para>
|
---|
| 143 | </note>
|
---|
| 144 |
|
---|
[4e7d6a6] | 145 | <variablelist>
|
---|
| 146 | <title>The rationale for the above configuration items:</title>
|
---|
| 147 |
|
---|
| 148 | <varlistentry>
|
---|
[3aee2ac2] | 149 | <term><parameter>Support for uevent helper</parameter></term>
|
---|
[4e7d6a6] | 150 | <listitem>
|
---|
[edbeeb5] | 151 | <para>Having this option set may interfere with device
|
---|
[5c9a7bf] | 152 | management when using Udev/Eudev. </para>
|
---|
[4e7d6a6] | 153 | </listitem>
|
---|
| 154 | </varlistentry>
|
---|
| 155 |
|
---|
| 156 | <varlistentry>
|
---|
| 157 | <term><parameter>Maintain a devtmpfs</parameter></term>
|
---|
| 158 | <listitem>
|
---|
| 159 | <para>This will create automated device nodes which are populated by the
|
---|
[5c9a7bf] | 160 | kernel, even without Udev running. Udev then runs on top of this,
|
---|
[4e7d6a6] | 161 | managing permissions and adding symlinks. This configuration
|
---|
[fba870f] | 162 | item is required for all users of Udev/Eudev.</para>
|
---|
[4e7d6a6] | 163 | </listitem>
|
---|
| 164 | </varlistentry>
|
---|
| 165 |
|
---|
| 166 | </variablelist>
|
---|
[2081905] | 167 |
|
---|
[230381d] | 168 | <screen role="nodump"><userinput>make menuconfig</userinput></screen>
|
---|
[2ccccf7] | 169 |
|
---|
| 170 | <variablelist>
|
---|
[230381d] | 171 | <title>The meaning of optional make environment variables:</title>
|
---|
[2ccccf7] | 172 |
|
---|
| 173 | <varlistentry>
|
---|
| 174 | <term><parameter>LANG=<host_LANG_value> LC_ALL=</parameter></term>
|
---|
| 175 | <listitem>
|
---|
[230381d] | 176 | <para>This establishes the locale setting to the one used on the
|
---|
| 177 | host. This may be needed for a proper menuconfig ncurses interface
|
---|
| 178 | line drawing on a UTF-8 linux text console.</para>
|
---|
| 179 |
|
---|
| 180 | <para>If used, be sure to replace
|
---|
| 181 | <replaceable><host_LANG_value></replaceable> by the value of
|
---|
| 182 | the <envar>$LANG</envar> variable from your host. You can
|
---|
| 183 | alternatively use instead the host's value of <envar>$LC_ALL</envar>
|
---|
[2ccccf7] | 184 | or <envar>$LC_CTYPE</envar>.</para>
|
---|
| 185 | </listitem>
|
---|
| 186 | </varlistentry>
|
---|
| 187 |
|
---|
| 188 | </variablelist>
|
---|
[2081905] | 189 |
|
---|
[b78c747] | 190 | <para>Alternatively, <command>make oldconfig</command> may be more
|
---|
| 191 | appropriate in some situations. See the <filename>README</filename>
|
---|
| 192 | file for more information.</para>
|
---|
| 193 |
|
---|
| 194 | <para>If desired, skip kernel configuration by copying the kernel
|
---|
| 195 | config file, <filename>.config</filename>, from the host system
|
---|
| 196 | (assuming it is available) to the unpacked <filename
|
---|
| 197 | class="directory">linux-&linux-version;</filename> directory. However,
|
---|
| 198 | we do not recommend this option. It is often better to explore all the
|
---|
| 199 | configuration menus and create the kernel configuration from
|
---|
| 200 | scratch.</para>
|
---|
| 201 |
|
---|
| 202 | <para>Compile the kernel image and modules:</para>
|
---|
[2081905] | 203 |
|
---|
[0445a3d] | 204 | <screen><userinput remap="make">make</userinput></screen>
|
---|
[2081905] | 205 |
|
---|
[b67f2d6] | 206 | <para>If using kernel modules, module configuration in <filename
|
---|
| 207 | class="directory">/etc/modprobe.d</filename> may be required.
|
---|
| 208 | Information pertaining to modules and kernel configuration is
|
---|
[afcfd74] | 209 | located in <xref linkend="ch-config-udev"/> and in the kernel
|
---|
[b67f2d6] | 210 | documentation in the <filename
|
---|
[b78c747] | 211 | class="directory">linux-&linux-version;/Documentation</filename> directory.
|
---|
[fba870f] | 212 | Also, <filename>modprobe.d(5)</filename> may be of interest.</para>
|
---|
[4b59d59] | 213 |
|
---|
[2e836fe] | 214 | <para>Unless module support has been disabled in the kernel configuration,
|
---|
| 215 | install the modules with:</para>
|
---|
[2081905] | 216 |
|
---|
[11ebea6] | 217 | <screen><userinput remap="install">make modules_install</userinput></screen>
|
---|
[2081905] | 218 |
|
---|
[b78c747] | 219 | <para>After kernel compilation is complete, additional steps are
|
---|
| 220 | required to complete the installation. Some files need to be copied to
|
---|
| 221 | the <filename class="directory">/boot</filename> directory.</para>
|
---|
[81fd230] | 222 |
|
---|
[230381d] | 223 | <caution>
|
---|
[0d84af1] | 224 | <para>If the host system has a separate /boot partition, the files copied
|
---|
| 225 | below should go there. The easiest way to do that is to bind /boot on the
|
---|
| 226 | host (outside chroot) to /mnt/lfs/boot before proceeding. As the root
|
---|
| 227 | user in the <emphasis>host system</emphasis>:</para>
|
---|
[230381d] | 228 |
|
---|
[11ebea6] | 229 | <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen>
|
---|
[230381d] | 230 | </caution>
|
---|
| 231 |
|
---|
[f9bcaec] | 232 | <para>The path to the kernel image may vary depending on the platform being
|
---|
| 233 | used. The filename below can be changed to suit your taste, but the stem of
|
---|
[fe1643e] | 234 | the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
|
---|
[f9bcaec] | 235 | the automatic setup of the boot process described in the next section. The
|
---|
| 236 | following command assumes an x86 architecture:</para>
|
---|
[2081905] | 237 |
|
---|
[0d84af1] | 238 | <screen revision="sysv"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
|
---|
[e787b1f] | 239 |
|
---|
[0d84af1] | 240 | <screen revision="systemd"><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&versiond;</userinput></screen>
|
---|
[2081905] | 241 |
|
---|
[b78c747] | 242 | <para><filename>System.map</filename> is a symbol file for the kernel.
|
---|
| 243 | It maps the function entry points of every function in the kernel API,
|
---|
| 244 | as well as the addresses of the kernel data structures for the running
|
---|
[2ca8941] | 245 | kernel. It is used as a resource when investigating kernel problems.
|
---|
[6028823] | 246 | Issue the following command to install the map file:</para>
|
---|
[81fd230] | 247 |
|
---|
[0d84af1] | 248 | <screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen>
|
---|
[2081905] | 249 |
|
---|
[b78c747] | 250 | <para>The kernel configuration file <filename>.config</filename>
|
---|
| 251 | produced by the <command>make menuconfig</command> step
|
---|
| 252 | above contains all the configuration selections for the kernel
|
---|
| 253 | that was just compiled. It is a good idea to keep this file for future
|
---|
| 254 | reference:</para>
|
---|
[81fd230] | 255 |
|
---|
[0d84af1] | 256 | <screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
|
---|
[2081905] | 257 |
|
---|
[a1e18fa] | 258 | <para>Install the documentation for the Linux kernel:</para>
|
---|
| 259 |
|
---|
[0445a3d] | 260 | <screen><userinput remap="install">install -d /usr/share/doc/linux-&linux-version;
|
---|
[c226182] | 261 | cp -r Documentation/* /usr/share/doc/linux-&linux-version;</userinput></screen>
|
---|
[a1e18fa] | 262 |
|
---|
[b78c747] | 263 | <para>It is important to note that the files in the kernel source
|
---|
| 264 | directory are not owned by <emphasis>root</emphasis>. Whenever a
|
---|
| 265 | package is unpacked as user <emphasis>root</emphasis> (like we did
|
---|
| 266 | inside chroot), the files have the user and group IDs of whatever
|
---|
| 267 | they were on the packager's computer. This is usually not a problem
|
---|
| 268 | for any other package to be installed because the source tree is
|
---|
| 269 | removed after the installation. However, the Linux source tree is
|
---|
| 270 | often retained for a long time. Because of this, there is a chance
|
---|
| 271 | that whatever user ID the packager used will be assigned to somebody
|
---|
| 272 | on the machine. That person would then have write access to the kernel
|
---|
| 273 | source.</para>
|
---|
| 274 |
|
---|
[1c5e434] | 275 | <note>
|
---|
| 276 | <para>In many cases, the configuration of the kernel will need to be
|
---|
| 277 | updated for packages that will be installed later in BLFS. Unlike
|
---|
| 278 | other packages, it is not necessary to remove the kernel source tree
|
---|
| 279 | after the newly built kernel is installed.</para>
|
---|
| 280 |
|
---|
| 281 | <para>If the kernel source tree is going to be retained, run
|
---|
| 282 | <command>chown -R 0:0</command> on the <filename
|
---|
| 283 | class="directory">linux-&linux-version;</filename> directory to ensure
|
---|
| 284 | all files are owned by user <emphasis>root</emphasis>.</para>
|
---|
| 285 | </note>
|
---|
[b78c747] | 286 |
|
---|
| 287 | <warning>
|
---|
| 288 | <para>Some kernel documentation recommends creating a symlink from
|
---|
| 289 | <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
|
---|
| 290 | source directory. This is specific to kernels prior to the 2.6 series and
|
---|
| 291 | <emphasis>must not</emphasis> be created on an LFS system as it can cause
|
---|
| 292 | problems for packages you may wish to build once your base LFS system is
|
---|
| 293 | complete.</para>
|
---|
[6c75ca3] | 294 | </warning>
|
---|
[b78c747] | 295 |
|
---|
[6c75ca3] | 296 | <warning>
|
---|
[4a32085] | 297 | <para>The headers in the system's <filename
|
---|
| 298 | class="directory">include</filename> directory (<filename
|
---|
| 299 | class="directory">/usr/include</filename>) should
|
---|
[b78c747] | 300 | <emphasis>always</emphasis> be the ones against which Glibc was compiled,
|
---|
[4a32085] | 301 | that is, the sanitised headers installed in <xref
|
---|
| 302 | linkend="ch-system-linux-headers"/>. Therefore, they should
|
---|
| 303 | <emphasis>never</emphasis> be replaced by either the raw kernel headers
|
---|
| 304 | or any other kernel sanitized headers.</para>
|
---|
[b78c747] | 305 | </warning>
|
---|
| 306 |
|
---|
| 307 | </sect2>
|
---|
| 308 |
|
---|
[200e466] | 309 | <sect2 id="conf-modprobe" role="configuration">
|
---|
| 310 | <title>Configuring Linux Module Load Order</title>
|
---|
| 311 |
|
---|
| 312 | <indexterm zone="conf-modprobe">
|
---|
[b67f2d6] | 313 | <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
|
---|
[200e466] | 314 | </indexterm>
|
---|
| 315 |
|
---|
[cdd87ad] | 316 | <para>Most of the time Linux modules are loaded automatically, but
|
---|
| 317 | sometimes it needs some specific direction. The program that loads
|
---|
| 318 | modules, <command>modprobe</command> or <command>insmod</command>, uses
|
---|
| 319 | <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
|
---|
| 320 | needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
|
---|
| 321 | uhci_hcd) have been built as modules, they will be loaded in the correct
|
---|
| 322 | order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
|
---|
| 323 | to avoid a warning being output at boot time.</para>
|
---|
[200e466] | 324 |
|
---|
[b67f2d6] | 325 | <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
|
---|
[200e466] | 326 | the following:</para>
|
---|
| 327 |
|
---|
[23ba7a00] | 328 | <screen><userinput>install -v -m755 -d /etc/modprobe.d
|
---|
[b67f2d6] | 329 | cat > /etc/modprobe.d/usb.conf << "EOF"
|
---|
| 330 | <literal># Begin /etc/modprobe.d/usb.conf
|
---|
[200e466] | 331 |
|
---|
| 332 | install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
|
---|
| 333 | install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
|
---|
| 334 |
|
---|
[b67f2d6] | 335 | # End /etc/modprobe.d/usb.conf</literal>
|
---|
[200e466] | 336 | EOF</userinput></screen>
|
---|
| 337 |
|
---|
| 338 | </sect2>
|
---|
| 339 |
|
---|
[b78c747] | 340 | <sect2 id="contents-kernel" role="content">
|
---|
| 341 | <title>Contents of Linux</title>
|
---|
| 342 |
|
---|
| 343 | <segmentedlist>
|
---|
| 344 | <segtitle>Installed files</segtitle>
|
---|
[fe05b08] | 345 | <segtitle>Installed directories</segtitle>
|
---|
[b78c747] | 346 |
|
---|
| 347 | <seglistitem>
|
---|
[2ca8941] | 348 | <seg>config-&linux-version;,
|
---|
[e787b1f] | 349 | <phrase revision="sysv">vmlinuz-&linux-version;-lfs-&version;,</phrase>
|
---|
| 350 | <phrase revision="systemd">vmlinuz-&linux-version;-lfs-&versiond;,</phrase>
|
---|
| 351 | and System.map-&linux-version;</seg>
|
---|
[fe05b08] | 352 | <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
|
---|
[b78c747] | 353 | </seglistitem>
|
---|
| 354 | </segmentedlist>
|
---|
| 355 |
|
---|
| 356 | <variablelist>
|
---|
| 357 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
| 358 | <?dbfo list-presentation="list"?>
|
---|
| 359 | <?dbhtml list-presentation="table"?>
|
---|
| 360 |
|
---|
| 361 | <varlistentry id="config">
|
---|
| 362 | <term><filename>config-&linux-version;</filename></term>
|
---|
| 363 | <listitem>
|
---|
| 364 | <para>Contains all the configuration selections for the kernel</para>
|
---|
| 365 | <indexterm zone="ch-bootable-kernel config">
|
---|
| 366 | <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
|
---|
| 367 | </indexterm>
|
---|
| 368 | </listitem>
|
---|
| 369 | </varlistentry>
|
---|
| 370 |
|
---|
| 371 | <varlistentry id="lfskernel">
|
---|
[e787b1f] | 372 | <term revision="sysv"><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
|
---|
| 373 | <term revision="systemd"><filename>vmlinuz-&linux-version;-lfs-&versiond;</filename></term>
|
---|
[b78c747] | 374 | <listitem>
|
---|
| 375 | <para>The engine of the Linux system. When turning on the computer,
|
---|
| 376 | the kernel is the first part of the operating system that gets loaded.
|
---|
| 377 | It detects and initializes all components of the computer's hardware,
|
---|
| 378 | then makes these components available as a tree of files to the
|
---|
| 379 | software and turns a single CPU into a multitasking machine capable
|
---|
| 380 | of running scores of programs seemingly at the same time</para>
|
---|
| 381 | <indexterm zone="ch-bootable-kernel lfskernel">
|
---|
| 382 | <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
|
---|
| 383 | </indexterm>
|
---|
| 384 | </listitem>
|
---|
| 385 | </varlistentry>
|
---|
| 386 |
|
---|
| 387 | <varlistentry id="System.map">
|
---|
| 388 | <term><filename>System.map-&linux-version;</filename></term>
|
---|
| 389 | <listitem>
|
---|
| 390 | <para>A list of addresses and symbols; it maps the entry points and
|
---|
| 391 | addresses of all the functions and data structures in the
|
---|
| 392 | kernel</para>
|
---|
| 393 | <indexterm zone="ch-bootable-kernel System.map">
|
---|
| 394 | <primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
|
---|
| 395 | </indexterm>
|
---|
| 396 | </listitem>
|
---|
| 397 | </varlistentry>
|
---|
| 398 |
|
---|
| 399 | </variablelist>
|
---|
| 400 |
|
---|
| 401 | </sect2>
|
---|
[673b0d8] | 402 |
|
---|
[6370fa6] | 403 | </sect1>
|
---|