source: chapter10/kernel.xml@ 44674e4c

12.0 12.0-rc1 12.1 12.1-rc1 multilib trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/update-glibc
Last change on this file since 44674e4c was 44674e4c, checked in by Xi Ruoyao <xry111@…>, 10 months ago

sysv: Mount cgroup fs for memory pressure information early

Prepare for systemd-254 update. See #5293 for details.
  • Property mode set to 100644
File size: 24.6 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/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 <sect1info condition="script">
12 <productname>kernel</productname>
13 <productnumber>&linux-version;</productnumber>
14 <address>&linux-url;</address>
15 </sect1info>
16
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>
27
28 <segmentedlist>
29 <segtitle>&buildtime;</segtitle>
30 <segtitle>&diskspace;</segtitle>
31
32 <seglistitem>
33 <seg>&linux-knl-sbu;</seg>
34 <seg>&linux-knl-du;</seg>
35 </seglistitem>
36 </segmentedlist>
37
38 </sect2>
39
40 <sect2 role="installation">
41 <title>Installation of the kernel</title>
42
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>
47
48 <important>
49 <para>
50 Building the linux kernel for the first time is one of the most
51 challenging tasks in LFS. Getting it right depends on the specific
52 hardware for the target system and your specific needs. There are
53 almost 12,000 configuration items that are available for the kernel
54 although only about a third of them are needed for most computers. The
55 LFS editors recommend that users not familiar with this process follow
56 the procedures below fairly closely. The objective is to get an
57 initial system to a point where you can log in at the command line when
58 you reboot later in <xref linkend="ch-finish-reboot"/>. At this point
59 optimization and customization is not a goal.
60 </para>
61
62
63 <para>
64 For general information on kernel configuration see <ulink
65 url="&hints-root;kernel-configuration.txt"/>. Additional information
66 about configuring and building the kernel can be found at <ulink
67 url="&anduin-sources;/kernel-nutshell/"/>.
68 These references are a bit
69 dated, but still give a reasonable overview of the process.
70 </para>
71
72 <para>
73 If all else fails, you can ask for help on the <ulink
74 url="https://www.linuxfromscratch.org/mail.html">lfs-support</ulink>
75 mailing list. Note that subscribing is required in order for the list
76 to avoid spam.
77 </para>
78 </important>
79
80 <para>Prepare for compilation by running the following command:</para>
81
82<screen><userinput remap="pre">make mrproper</userinput></screen>
83
84 <para>This ensures that the kernel tree is absolutely clean. The
85 kernel team recommends that this command be issued prior to each
86 kernel compilation. Do not rely on the source tree being clean after
87 un-tarring.</para>
88
89 <para>There are several ways to configure the kernel options. Usually,
90 This is done through a menu-driven interface, for example:</para>
91
92<screen role="nodump"><userinput>make menuconfig</userinput></screen>
93
94 <variablelist>
95 <title>The meaning of optional make environment variables:</title>
96
97 <varlistentry>
98 <term><parameter>LANG=&lt;host_LANG_value&gt; LC_ALL=</parameter></term>
99 <listitem>
100 <para>This establishes the locale setting to the one used on the
101 host. This may be needed for a proper menuconfig ncurses interface
102 line drawing on a UTF-8 linux text console.</para>
103
104 <para>If used, be sure to replace
105 <replaceable>&lt;host_LANG_value&gt;</replaceable> by the value of
106 the <envar>$LANG</envar> variable from your host. You can
107 alternatively use instead the host's value of <envar>$LC_ALL</envar>
108 or <envar>$LC_CTYPE</envar>.</para>
109 </listitem>
110 </varlistentry>
111
112 <varlistentry>
113 <term><command>make menuconfig</command></term>
114 <listitem>
115 <para>This launches an ncurses menu-driven interface. For other
116 (graphical) interfaces, type <command>make help</command>.</para>
117 </listitem>
118 </varlistentry>
119 </variablelist>
120
121 <!-- Support for compiling a keymap into the kernel is deliberately removed -->
122
123
124 <note>
125 <para>A good starting place for setting up the kernel configuration is to
126 run <command>make defconfig</command>. This will set the base
127 configuration to a good state that takes your current system architecture
128 into account.</para>
129
130 <para>Be sure to enable/disable/set the following features or the system might
131 not work correctly or boot at all:</para>
132
133 <screen role="nodump" revision="sysv">Processor type and features ---&gt;
134 [*] Build a relocatable kernel [CONFIG_RELOCATABLE]
135 [*] Randomize the address of the kernel image (KASLR) [CONFIG_RANDOMIZE_BASE]
136General setup ---&gt;
137 [ ] Compile the kernel with warnings as errors [CONFIG_WERROR]
138 CPU/Task time and stats accounting ---&gt;
139 [*] Pressure stall information tracking [CONFIG_PSI]
140 [ ] Require boot parameter to enable pressure stall information tracking [CONFIG_PSI_DEFAULT_DISABLED]
141 &lt; &gt; Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS]
142 [*] Control Group support [CONFIG_CGROUPS] ---&gt;
143 [*] Memory controller [CONFIG_MEMCG]
144 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT]
145General architecture-dependent options ---&gt;
146 [*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR]
147 [*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
148Device Drivers ---&gt;
149 Graphics support ---&gt;
150 Frame buffer Devices ---&gt;
151 &lt;*&gt; Support for frame buffer devices ---&gt;
152 Console display driver support ---&gt;
153 [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
154 Generic Driver Options ---&gt;
155 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
156 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
157 [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs [CONFIG_DEVTMPFS_MOUNT]</screen>
158
159 <screen role="nodump" revision="systemd">Processor type and features ---&gt;
160 [*] Build a relocatable kernel [CONFIG_RELOCATABLE]
161 [*] Randomize the address of the kernel image (KASLR) [CONFIG_RANDOMIZE_BASE]
162General setup ---&gt;
163 [ ] Compile the kernel with warnings as errors [CONFIG_WERROR]
164 [ ] Auditing Support [CONFIG_AUDIT]
165 CPU/Task time and stats accounting ---&gt;
166 [*] Pressure stall information tracking [CONFIG_PSI]
167 [ ] Require boot parameter to enable pressure stall information tracking [CONFIG_PSI_DEFAULT_DISABLED]
168 &lt; &gt; Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS]
169 [*] Control Group support [CONFIG_CGROUPS] ---&gt;
170 [*] Memory controller [CONFIG_MEMCG]
171 [ ] Configure standard kernel features (expert users) [CONFIG_EXPERT]
172General architecture-dependent options ---&gt;
173 [*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
174 [*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR]
175 [*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
176[*] Networking support ---&gt; [CONFIG_NET]
177 Networking options ---&gt;
178 [*] TCP/IP networking [CONFIG_INET]
179 &lt;*&gt; The IPv6 protocol [CONFIG_IPV6]
180Device Drivers ---&gt;
181 Generic Driver Options ---&gt;
182 [ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
183 [*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
184 [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs [CONFIG_DEVTMPFS_MOUNT]
185 Firmware Loader ---&gt;
186 [ ] Enable the firmware sysfs fallback mechanism [CONFIG_FW_LOADER_USER_HELPER]
187 Firmware Drivers ---&gt;
188 [*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
189 Graphics support ---&gt;
190 Frame buffer Devices ---&gt;
191 &lt;*&gt; Support for frame buffer devices ---&gt;
192 Console display driver support ---&gt;
193 [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
194File systems ---&gt;
195 [*] Inotify support for userspace [CONFIG_INOTIFY_USER]
196 Pseudo filesystems ---&gt;
197 [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen>
198
199 <para>Enable some additional features if you are building a 64-bit
200 system. If you are using menuconfig, enable them in the order of
201 <parameter>CONFIG_PCI_MSI</parameter> first, then
202 <parameter>CONFIG_IRQ_REMAP</parameter>, at last
203 <parameter>CONFIG_X86_X2APIC</parameter> because an option only
204 shows up after its dependencies are selected.</para>
205
206 <screen role="nodump">Processor type and features ---&gt;
207 [*] Support x2apic [CONFIG_X86_X2APIC]
208Device Drivers ---&gt;
209 [*] PCI Support ---&gt; [CONFIG_PCI]
210 [*] Message Signaled Interrupts (MSI and MSI-X) [CONFIG_PCI_MSI]
211 [*] IOMMU Hardware Support ---&gt; [CONFIG_IOMMU_SUPPORT]
212 [*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen>
213
214 <para>If you are building a 32-bit system running on a hardware
215 with RAM more than 4GB, adjust the configuration so the kernel will
216 be able to use up to 64GB physical RAM:</para>
217
218 <screen role="nodump">Processor type and features ---&gt;
219 High Memory Support ---&gt;
220 (X) 64GB [CONFIG_HIGHMEM64G]</screen>
221
222 <para>If the partition for the LFS system is in a NVME SSD (i. e. the
223 device node for the partition is <filename>/dev/nvme*</filename>
224 instead of <filename>/dev/sd*</filename>), enable NVME support or
225 the LFS system won't boot:</para>
226
227 <screen role="nodump">Device Drivers ---&gt;
228 NVME Support ---&gt;
229 &lt;*&gt; NVM Express block device [CONFIG_BLK_DEV_NVME]</screen>
230 </note>
231
232 <note revision="systemd">
233 <para>While "The IPv6 Protocol" is not strictly
234 required, it is highly recommended by the systemd developers.</para>
235 </note>
236
237 <para>There are several other options that may be desired
238 depending on the requirements for the system. For a list of options needed
239 for BLFS packages, see the <ulink
240 url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
241 Index of Kernel Settings</ulink>.</para>
242
243 <note>
244 <para>If your host hardware is using UEFI and you wish to boot the
245 LFS system with it, you should adjust some kernel configuration
246 following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel">
247 the BLFS page</ulink> <emphasis role='bold'>even if you'll use the
248 UEFI bootloader from the host distro</emphasis>.</para>
249 </note>
250
251 <variablelist>
252 <title>The rationale for the above configuration items:</title>
253
254 <varlistentry>
255 <term><parameter>Randomize the address of the kernel image (KASLR)</parameter></term>
256 <listitem>
257 <para>Enable ASLR for kernel image, to mitigate some attacks based
258 on fixed addresses of sensitive data or code in the kernel.</para>
259 </listitem>
260 </varlistentry>
261
262 <varlistentry>
263 <term>
264 <parameter>
265 Compile the kernel with warnings as errors
266 </parameter>
267 </term>
268 <listitem>
269 <para>This may cause building failure if the compiler and/or
270 configuration are different from those of the kernel
271 developers.</para>
272 </listitem>
273 </varlistentry>
274
275 <varlistentry>
276 <term>
277 <parameter>
278 Enable kernel headers through /sys/kernel/kheaders.tar.xz
279 </parameter>
280 </term>
281 <listitem>
282 <para>This will require <command>cpio</command> building the kernel.
283 <command>cpio</command> is not installed by LFS.</para>
284 </listitem>
285 </varlistentry>
286
287 <varlistentry>
288 <term>
289 <parameter>
290 Configure standard kernel features (expert users)
291 </parameter>
292 </term>
293 <listitem>
294 <para>This will make some options show up in the configuration
295 interface but changing those options may be dangerous. Do not use
296 this unless you know what you are doing.</para>
297 </listitem>
298 </varlistentry>
299
300 <varlistentry>
301 <term><parameter>Strong Stack Protector</parameter></term>
302 <listitem>
303 <para>Enable SSP for the kernel. We've enabled it for the entire
304 userspace with <parameter>--enable-default-ssp</parameter>
305 configuring GCC, but the kernel does not use GCC default setting
306 for SSP. We enable it explicitly here.</para>
307 </listitem>
308 </varlistentry>
309
310 <varlistentry>
311 <term><parameter>Support for uevent helper</parameter></term>
312 <listitem>
313 <para>Having this option set may interfere with device
314 management when using Udev.</para>
315 </listitem>
316 </varlistentry>
317
318 <varlistentry>
319 <term><parameter>Maintain a devtmpfs</parameter></term>
320 <listitem>
321 <para>This will create automated device nodes which are populated by the
322 kernel, even without Udev running. Udev then runs on top of this,
323 managing permissions and adding symlinks. This configuration
324 item is required for all users of Udev.</para>
325 </listitem>
326 </varlistentry>
327
328 <varlistentry>
329 <term><parameter>Automount devtmpfs at /dev</parameter></term>
330 <listitem>
331 <para>This will mount the kernel view of the devices on /dev
332 upon switching to root filesystem just before starting
333 init.</para>
334 </listitem>
335 </varlistentry>
336
337 <varlistentry>
338 <term><parameter>Framebuffer Console support</parameter></term>
339 <listitem>
340 <para>This is needed to display the Linux console on a frame
341 buffer device. To allow the kernel to print debug messages at an
342 early boot stage, it shouldn't be built as a kernel module
343 unless an initramfs will be used. And, if
344 <option>CONFIG_DRM</option> (Direct Rendering Manager) is enabled,
345 it's likely <option>CONFIG_DRM_FBDEV_EMULATION</option> (Enable
346 legacy fbdev support for your modesetting driver) should be
347 enabled as well.</para>
348 </listitem>
349 </varlistentry>
350
351 <varlistentry>
352 <term><parameter>Support x2apic</parameter></term>
353 <listitem>
354 <para>Support running the interrupt controller of 64-bit x86
355 processors in x2APIC mode. x2APIC may be enabled by firmware on
356 64-bit x86 systems, and a kernel without this option enabled will
357 panic on boot if x2APIC is enabled by firmware. This option has
358 has no effect, but also does no harm if x2APIC is disabled by the
359 firmware.</para>
360 </listitem>
361 </varlistentry>
362
363 </variablelist>
364
365 <para>Alternatively, <command>make oldconfig</command> may be more
366 appropriate in some situations. See the <filename>README</filename>
367 file for more information.</para>
368
369 <para>If desired, skip kernel configuration by copying the kernel
370 config file, <filename>.config</filename>, from the host system
371 (assuming it is available) to the unpacked <filename
372 class="directory">linux-&linux-version;</filename> directory. However,
373 we do not recommend this option. It is often better to explore all the
374 configuration menus and create the kernel configuration from
375 scratch.</para>
376
377 <para>Compile the kernel image and modules:</para>
378
379<screen><userinput remap="make">make</userinput></screen>
380
381 <para>If using kernel modules, module configuration in <filename
382 class="directory">/etc/modprobe.d</filename> may be required.
383 Information pertaining to modules and kernel configuration is
384 located in <xref linkend="ch-config-udev"/> and in the kernel
385 documentation in the <filename
386 class="directory">linux-&linux-version;/Documentation</filename> directory.
387 Also, <filename>modprobe.d(5)</filename> may be of interest.</para>
388
389 <para>Unless module support has been disabled in the kernel configuration,
390 install the modules with:</para>
391
392<screen><userinput remap="install">make modules_install</userinput></screen>
393
394 <para>After kernel compilation is complete, additional steps are
395 required to complete the installation. Some files need to be copied to
396 the <filename class="directory">/boot</filename> directory.</para>
397
398 <caution>
399 <para>If you've decided to use a separate &boot-dir; partition for the
400 LFS system (maybe sharing a &boot-dir; partition with the host
401 distro) , the files copied below should go there. The easiest way to
402 do that is to create the entry for &boot-dir; in &fstab; first (read
403 the previous section for details), then issue the following command
404 as the &root; user in the
405 <emphasis>chroot environment</emphasis>:</para>
406
407<screen role="nodump"><userinput>mount /boot</userinput></screen>
408
409 <para>The path to the device node is omitted in the command because
410 <command>mount</command> can read it from &fstab;.</para>
411 </caution>
412
413 <para>The path to the kernel image may vary depending on the platform being
414 used. The filename below can be changed to suit your taste, but the stem of
415 the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
416 the automatic setup of the boot process described in the next section. The
417 following command assumes an x86 architecture:</para>
418
419<screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
420
421 <para><filename>System.map</filename> is a symbol file for the kernel.
422 It maps the function entry points of every function in the kernel API,
423 as well as the addresses of the kernel data structures for the running
424 kernel. It is used as a resource when investigating kernel problems.
425 Issue the following command to install the map file:</para>
426
427<screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen>
428
429 <para>The kernel configuration file <filename>.config</filename>
430 produced by the <command>make menuconfig</command> step
431 above contains all the configuration selections for the kernel
432 that was just compiled. It is a good idea to keep this file for future
433 reference:</para>
434
435<screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
436
437 <para>Install the documentation for the Linux kernel:</para>
438
439<screen><userinput remap="install">cp -r Documentation -T /usr/share/doc/linux-&linux-version;</userinput></screen>
440
441 <para>It is important to note that the files in the kernel source
442 directory are not owned by <emphasis>root</emphasis>. Whenever a
443 package is unpacked as user <emphasis>root</emphasis> (like we did
444 inside chroot), the files have the user and group IDs of whatever
445 they were on the packager's computer. This is usually not a problem
446 for any other package to be installed because the source tree is
447 removed after the installation. However, the Linux source tree is
448 often retained for a long time. Because of this, there is a chance
449 that whatever user ID the packager used will be assigned to somebody
450 on the machine. That person would then have write access to the kernel
451 source.</para>
452
453 <note>
454 <para>In many cases, the configuration of the kernel will need to be
455 updated for packages that will be installed later in BLFS. Unlike
456 other packages, it is not necessary to remove the kernel source tree
457 after the newly built kernel is installed.</para>
458
459 <para>If the kernel source tree is going to be retained, run
460 <command>chown -R 0:0</command> on the <filename
461 class="directory">linux-&linux-version;</filename> directory to ensure
462 all files are owned by user <emphasis>root</emphasis>.</para>
463 </note>
464
465 <warning>
466 <para>Some kernel documentation recommends creating a symlink from
467 <filename class="symlink">/usr/src/linux</filename> pointing to the kernel
468 source directory. This is specific to kernels prior to the 2.6 series and
469 <emphasis>must not</emphasis> be created on an LFS system as it can cause
470 problems for packages you may wish to build once your base LFS system is
471 complete.</para>
472 </warning>
473
474 <warning>
475 <para>The headers in the system's <filename
476 class="directory">include</filename> directory (<filename
477 class="directory">/usr/include</filename>) should
478 <emphasis>always</emphasis> be the ones against which Glibc was compiled,
479 that is, the sanitised headers installed in <xref
480 linkend="ch-tools-linux-headers"/>. Therefore, they should
481 <emphasis>never</emphasis> be replaced by either the raw kernel headers
482 or any other kernel sanitized headers.</para>
483 </warning>
484
485 </sect2>
486
487 <sect2 id="conf-modprobe" role="configuration">
488 <title>Configuring Linux Module Load Order</title>
489
490 <indexterm zone="conf-modprobe">
491 <primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
492 </indexterm>
493
494 <para>Most of the time Linux modules are loaded automatically, but
495 sometimes it needs some specific direction. The program that loads
496 modules, <command>modprobe</command> or <command>insmod</command>, uses
497 <filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
498 needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
499 uhci_hcd) have been built as modules, they will be loaded in the correct
500 order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
501 to avoid a warning being output at boot time.</para>
502
503 <para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
504 the following:</para>
505
506<screen><userinput>install -v -m755 -d /etc/modprobe.d
507cat &gt; /etc/modprobe.d/usb.conf &lt;&lt; "EOF"
508<literal># Begin /etc/modprobe.d/usb.conf
509
510install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
511install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
512
513# End /etc/modprobe.d/usb.conf</literal>
514EOF</userinput></screen>
515
516 </sect2>
517
518 <sect2 id="contents-kernel" role="content">
519 <title>Contents of Linux</title>
520
521 <segmentedlist>
522 <segtitle>Installed files</segtitle>
523 <segtitle>Installed directories</segtitle>
524
525 <seglistitem>
526 <seg>config-&linux-version;,
527 vmlinuz-&linux-version;-lfs-&version;,
528 and System.map-&linux-version;</seg>
529 <seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
530 </seglistitem>
531 </segmentedlist>
532
533 <variablelist>
534 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
535 <?dbfo list-presentation="list"?>
536 <?dbhtml list-presentation="table"?>
537
538 <varlistentry id="config">
539 <term><filename>config-&linux-version;</filename></term>
540 <listitem>
541 <para>Contains all the configuration selections for the kernel</para>
542 <indexterm zone="ch-bootable-kernel config">
543 <primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
544 </indexterm>
545 </listitem>
546 </varlistentry>
547
548 <varlistentry id="lfskernel">
549 <term><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
550 <listitem>
551 <para>The engine of the Linux system. When turning on the computer,
552 the kernel is the first part of the operating system that gets loaded.
553 It detects and initializes all components of the computer's hardware,
554 then makes these components available as a tree of files to the
555 software and turns a single CPU into a multitasking machine capable
556 of running scores of programs seemingly at the same time</para>
557 <indexterm zone="ch-bootable-kernel lfskernel">
558 <primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
559 </indexterm>
560 </listitem>
561 </varlistentry>
562
563 <varlistentry id="System.map">
564 <term><filename>System.map-&linux-version;</filename></term>
565 <listitem>
566 <para>A list of addresses and symbols; it maps the entry points and
567 addresses of all the functions and data structures in the
568 kernel</para>
569 <indexterm zone="ch-bootable-kernel System.map">
570 <primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
571 </indexterm>
572 </listitem>
573 </varlistentry>
574
575 </variablelist>
576
577 </sect2>
578
579</sect1>
Note: See TracBrowser for help on using the repository browser.