Context Navigation

source: chapter10/kernel.xml@ da2e8cb

Visit:

multilib xry111/multilib

Last change on this file since da2e8cb was da2e8cb, checked in by Thomas Trepl <thomas@…>, 14 months ago
Automatic merge of trunk into multilib
Property mode set to `100644`
File size: 25.9 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—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=<host_LANG_value> 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><host_LANG_value></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">General setup --->
134	[ ] Compile the kernel with warnings as errors [CONFIG_WERROR]
135	CPU/Task time and stats accounting --->
136	[*] Pressure stall information tracking [CONFIG_PSI]
137	[ ] Require boot parameter to enable pressure stall information tracking
138	[CONFIG_PSI_DEFAULT_DISABLED]
139	< > Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS]
140	[*] Control Group support [CONFIG_CGROUPS] --->
141	[*] Memory controller [CONFIG_MEMCG]
142	[ ] Configure standard kernel features (expert users) [CONFIG_EXPERT]
143
144	Processor type and features --->
145	[*] Build a relocatable kernel [CONFIG_RELOCATABLE]
146	[*] Randomize the address of the kernel image (KASLR) [CONFIG_RANDOMIZE_BASE]
147
148	General architecture-dependent options --->
149	[*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR]
150	[*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
151
152	Device Drivers --->
153	Generic Driver Options --->
154	[ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
155	[*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
156	[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs
157	[CONFIG_DEVTMPFS_MOUNT]
158	Graphics support --->
159	Frame buffer Devices --->
160	<*> Support for frame buffer devices --->
161	Console display driver support --->
162	[*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]</screen>
163
164	<screen role="nodump" revision="systemd">
165	General setup --->
166	[ ] Compile the kernel with warnings as errors [CONFIG_WERROR]
167	[ ] Auditing Support [CONFIG_AUDIT]
168	CPU/Task time and stats accounting --->
169	[*] Pressure stall information tracking [CONFIG_PSI]
170	[ ] Require boot parameter to enable pressure stall information tracking
171	[CONFIG_PSI_DEFAULT_DISABLED]
172	< > Enable kernel headers through /sys/kernel/kheaders.tar.xz [CONFIG_IKHEADERS]
173	[*] Control Group support [CONFIG_CGROUPS] --->
174	[*] Memory controller [CONFIG_MEMCG]
175	[ ] Configure standard kernel features (expert users) [CONFIG_EXPERT]
176
177	Processor type and features --->
178	[*] Build a relocatable kernel [CONFIG_RELOCATABLE]
179	[*] Randomize the address of the kernel image (KASLR) [CONFIG_RANDOMIZE_BASE]
180
181	General architecture-dependent options --->
182	[*] Enable seccomp to safely compute untrusted bytecode [CONFIG_SECCOMP]
183	[*] Stack Protector buffer overflow detection [CONFIG_STACKPROTECTOR]
184	[*] Strong Stack Protector [CONFIG_STACKPROTECTOR_STRONG]
185
186	[*] Networking support ---> [CONFIG_NET]
187	Networking options --->
188	[*] TCP/IP networking [CONFIG_INET]
189	<*> The IPv6 protocol [CONFIG_IPV6]
190
191	Device Drivers --->
192	Generic Driver Options --->
193	[ ] Support for uevent helper [CONFIG_UEVENT_HELPER]
194	[*] Maintain a devtmpfs filesystem to mount at /dev [CONFIG_DEVTMPFS]
195	[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs
196	[CONFIG_DEVTMPFS_MOUNT]
197	Firmware Loader --->
198	[ ] Enable the firmware sysfs fallback mechanism [CONFIG_FW_LOADER_USER_HELPER]
199	Firmware Drivers --->
200	[*] Export DMI identification via sysfs to userspace [CONFIG_DMIID]
201	Graphics support --->
202	Frame buffer Devices --->
203	<*> Support for frame buffer devices --->
204	Console display driver support --->
205	[*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
206
207	File systems --->
208	[*] Inotify support for userspace [CONFIG_INOTIFY_USER]
209	Pseudo filesystems --->
210	[*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]</screen>
211
212	<para>Enable some additional features if you are building a 64-bit
213	system. If you are using menuconfig, enable them in the order of
214	<parameter>CONFIG_PCI_MSI</parameter> first, then
215	<parameter>CONFIG_IRQ_REMAP</parameter>, at last
216	<parameter>CONFIG_X86_X2APIC</parameter> because an option only
217	shows up after its dependencies are selected.</para>
218
219	<screen role="nodump">Processor type and features --->
220	[*] Support x2apic [CONFIG_X86_X2APIC]
221
222	Device Drivers --->
223	[*] PCI Support ---> [CONFIG_PCI]
224	[*] Message Signaled Interrupts (MSI and MSI-X) [CONFIG_PCI_MSI]
225	[*] IOMMU Hardware Support ---> [CONFIG_IOMMU_SUPPORT]
226	[*] Support for Interrupt Remapping [CONFIG_IRQ_REMAP]</screen>
227
228	<para>If you are building a 32-bit system running on a hardware
229	with RAM more than 4GB, adjust the configuration so the kernel will
230	be able to use up to 64GB physical RAM:</para>
231
232	<screen role="nodump">Processor type and features --->
233	High Memory Support --->
234	(X) 64GB [CONFIG_HIGHMEM64G]</screen>
235
236	<para>If the partition for the LFS system is in a NVME SSD (i. e. the
237	device node for the partition is <filename>/dev/nvme*</filename>
238	instead of <filename>/dev/sd*</filename>), enable NVME support or
239	the LFS system won't boot:</para>
240
241	<screen role="nodump">Device Drivers --->
242	NVME Support --->
243	<*> NVM Express block device [CONFIG_BLK_DEV_NVME]</screen>
244	</note>
245
246	<note revision="systemd">
247	<para>While "The IPv6 Protocol" is not strictly
248	required, it is highly recommended by the systemd developers.</para>
249	</note>
250
251	<para>There are several other options that may be desired
252	depending on the requirements for the system. For a list of options needed
253	for BLFS packages, see the <ulink
254	url="&lfs-root;blfs/view/&short-version;/longindex.html#kernel-config-index">BLFS
255	Index of Kernel Settings</ulink>.</para>
256
257	<note>
258	<para>If your host hardware is using UEFI and you wish to boot the
259	LFS system with it, you should adjust some kernel configuration
260	following <ulink url="&blfs-book;postlfs/grub-setup.html#uefi-kernel">
261	the BLFS page</ulink> <emphasis role='bold'>even if you'll use the
262	UEFI bootloader from the host distro</emphasis>.</para>
263	</note>
264
265	<note arch="ml_32,ml_x32,ml_all">
266	<para>
267	The kernel on a multilib system needs to be able to
268	identify and start binaries compiled for different architectures
269	than the default.
270	</para>
271
272	<para arch="ml_32,ml_all">
273	If support for any 32bit ABI was built, make sure that the option
274	"IA32 Emulation" is selected. The option 'IA32 a.out support' is
275	optional.
276	</para>
277
278	<para arch="ml_x32,ml_all">
279	If support for the x32bit ABI was built, make sure that the option
280	"x32 ABI for 64-bit mode" is selected.
281	</para>
282
283	<screen arch="ml_32">Binary Emulations --->
284	[*] IA32 Emulation [CONFIG_IA32_EMULATION]
285	<M> IA32 a.out support [CONFIG_IA32_AOUT]
286	</screen>
287	<screen arch="ml_x32">Binary Emulations --->
288	[*] x32 ABI for 64-bit mode [CONFIG_X86_X32]
289	</screen>
290	<screen arch="ml_all">Binary Emulations --->
291	[*] IA32 Emulation [CONFIG_IA32_EMULATION]
292	<M> IA32 a.out support [CONFIG_IA32_AOUT]
293	[*] x32 ABI for 64-bit mode [CONFIG_X86_X32]
294	</screen>
295	</note>
296
297	<variablelist>
298	<title>The rationale for the above configuration items:</title>
299
300	<varlistentry>
301	<term><parameter>Randomize the address of the kernel image (KASLR)</parameter></term>
302	<listitem>
303	<para>Enable ASLR for kernel image, to mitigate some attacks based
304	on fixed addresses of sensitive data or code in the kernel.</para>
305	</listitem>
306	</varlistentry>
307
308	<varlistentry>
309	<term>
310	<parameter>
311	Compile the kernel with warnings as errors
312	</parameter>
313	</term>
314	<listitem>
315	<para>This may cause building failure if the compiler and/or
316	configuration are different from those of the kernel
317	developers.</para>
318	</listitem>
319	</varlistentry>
320
321	<varlistentry>
322	<term>
323	<parameter>
324	Enable kernel headers through /sys/kernel/kheaders.tar.xz
325	</parameter>
326	</term>
327	<listitem>
328	<para>This will require <command>cpio</command> building the kernel.
329	<command>cpio</command> is not installed by LFS.</para>
330	</listitem>
331	</varlistentry>
332
333	<varlistentry>
334	<term>
335	<parameter>
336	Configure standard kernel features (expert users)
337	</parameter>
338	</term>
339	<listitem>
340	<para>This will make some options show up in the configuration
341	interface but changing those options may be dangerous. Do not use
342	this unless you know what you are doing.</para>
343	</listitem>
344	</varlistentry>
345
346	<varlistentry>
347	<term><parameter>Strong Stack Protector</parameter></term>
348	<listitem>
349	<para>Enable SSP for the kernel. We've enabled it for the entire
350	userspace with <parameter>--enable-default-ssp</parameter>
351	configuring GCC, but the kernel does not use GCC default setting
352	for SSP. We enable it explicitly here.</para>
353	</listitem>
354	</varlistentry>
355
356	<varlistentry>
357	<term><parameter>Support for uevent helper</parameter></term>
358	<listitem>
359	<para>Having this option set may interfere with device
360	management when using Udev.</para>
361	</listitem>
362	</varlistentry>
363
364	<varlistentry>
365	<term><parameter>Maintain a devtmpfs</parameter></term>
366	<listitem>
367	<para>This will create automated device nodes which are populated by the
368	kernel, even without Udev running. Udev then runs on top of this,
369	managing permissions and adding symlinks. This configuration
370	item is required for all users of Udev.</para>
371	</listitem>
372	</varlistentry>
373
374	<varlistentry>
375	<term><parameter>Automount devtmpfs at /dev</parameter></term>
376	<listitem>
377	<para>This will mount the kernel view of the devices on /dev
378	upon switching to root filesystem just before starting
379	init.</para>
380	</listitem>
381	</varlistentry>
382
383	<varlistentry>
384	<term><parameter>Framebuffer Console support</parameter></term>
385	<listitem>
386	<para>This is needed to display the Linux console on a frame
387	buffer device. To allow the kernel to print debug messages at an
388	early boot stage, it shouldn't be built as a kernel module
389	unless an initramfs will be used. And, if
390	<option>CONFIG_DRM</option> (Direct Rendering Manager) is enabled,
391	it's likely <option>CONFIG_DRM_FBDEV_EMULATION</option> (Enable
392	legacy fbdev support for your modesetting driver) should be
393	enabled as well.</para>
394	</listitem>
395	</varlistentry>
396
397	<varlistentry>
398	<term><parameter>Support x2apic</parameter></term>
399	<listitem>
400	<para>Support running the interrupt controller of 64-bit x86
401	processors in x2APIC mode. x2APIC may be enabled by firmware on
402	64-bit x86 systems, and a kernel without this option enabled will
403	panic on boot if x2APIC is enabled by firmware. This option has
404	has no effect, but also does no harm if x2APIC is disabled by the
405	firmware.</para>
406	</listitem>
407	</varlistentry>
408
409	</variablelist>
410
411	<para>Alternatively, <command>make oldconfig</command> may be more
412	appropriate in some situations. See the <filename>README</filename>
413	file for more information.</para>
414
415	<para>If desired, skip kernel configuration by copying the kernel
416	config file, <filename>.config</filename>, from the host system
417	(assuming it is available) to the unpacked <filename
418	class="directory">linux-&linux-version;</filename> directory. However,
419	we do not recommend this option. It is often better to explore all the
420	configuration menus and create the kernel configuration from
421	scratch.</para>
422
423	<para>Compile the kernel image and modules:</para>
424
425	<screen><userinput remap="make">make</userinput></screen>
426
427	<para>If using kernel modules, module configuration in <filename
428	class="directory">/etc/modprobe.d</filename> may be required.
429	Information pertaining to modules and kernel configuration is
430	located in <xref linkend="ch-config-udev"/> and in the kernel
431	documentation in the <filename
432	class="directory">linux-&linux-version;/Documentation</filename> directory.
433	Also, <filename>modprobe.d(5)</filename> may be of interest.</para>
434
435	<para>Unless module support has been disabled in the kernel configuration,
436	install the modules with:</para>
437
438	<screen><userinput remap="install">make modules_install</userinput></screen>
439
440	<para>After kernel compilation is complete, additional steps are
441	required to complete the installation. Some files need to be copied to
442	the <filename class="directory">/boot</filename> directory.</para>
443
444	<caution>
445	<para>If you've decided to use a separate &boot-dir; partition for the
446	LFS system (maybe sharing a &boot-dir; partition with the host
447	distro) , the files copied below should go there. The easiest way to
448	do that is to create the entry for &boot-dir; in &fstab; first (read
449	the previous section for details), then issue the following command
450	as the &root; user in the
451	<emphasis>chroot environment</emphasis>:</para>
452
453	<screen role="nodump"><userinput>mount /boot</userinput></screen>
454
455	<para>The path to the device node is omitted in the command because
456	<command>mount</command> can read it from &fstab;.</para>
457	</caution>
458
459	<para>The path to the kernel image may vary depending on the platform being
460	used. The filename below can be changed to suit your taste, but the stem of
461	the filename should be <emphasis>vmlinuz</emphasis> to be compatible with
462	the automatic setup of the boot process described in the next section. The
463	following command assumes an x86 architecture:</para>
464
465	<screen><userinput remap="install">cp -iv arch/x86/boot/bzImage /boot/vmlinuz-&linux-version;-lfs-&version;</userinput></screen>
466
467	<para><filename>System.map</filename> is a symbol file for the kernel.
468	It maps the function entry points of every function in the kernel API,
469	as well as the addresses of the kernel data structures for the running
470	kernel. It is used as a resource when investigating kernel problems.
471	Issue the following command to install the map file:</para>
472
473	<screen><userinput remap="install">cp -iv System.map /boot/System.map-&linux-version;</userinput></screen>
474
475	<para>The kernel configuration file <filename>.config</filename>
476	produced by the <command>make menuconfig</command> step
477	above contains all the configuration selections for the kernel
478	that was just compiled. It is a good idea to keep this file for future
479	reference:</para>
480
481	<screen><userinput remap="install">cp -iv .config /boot/config-&linux-version;</userinput></screen>
482
483	<para>Install the documentation for the Linux kernel:</para>
484
485	<screen><userinput remap="install">cp -r Documentation -T /usr/share/doc/linux-&linux-version;</userinput></screen>
486
487	<para>It is important to note that the files in the kernel source
488	directory are not owned by <emphasis>root</emphasis>. Whenever a
489	package is unpacked as user <emphasis>root</emphasis> (like we did
490	inside chroot), the files have the user and group IDs of whatever
491	they were on the packager's computer. This is usually not a problem
492	for any other package to be installed because the source tree is
493	removed after the installation. However, the Linux source tree is
494	often retained for a long time. Because of this, there is a chance
495	that whatever user ID the packager used will be assigned to somebody
496	on the machine. That person would then have write access to the kernel
497	source.</para>
498
499	<note>
500	<para>In many cases, the configuration of the kernel will need to be
501	updated for packages that will be installed later in BLFS. Unlike
502	other packages, it is not necessary to remove the kernel source tree
503	after the newly built kernel is installed.</para>
504
505	<para>If the kernel source tree is going to be retained, run
506	<command>chown -R 0:0</command> on the <filename
507	class="directory">linux-&linux-version;</filename> directory to ensure
508	all files are owned by user <emphasis>root</emphasis>.</para>
509	</note>
510
511	<warning>
512	<para>Some kernel documentation recommends creating a symlink from
513	<filename class="symlink">/usr/src/linux</filename> pointing to the kernel
514	source directory. This is specific to kernels prior to the 2.6 series and
515	<emphasis>must not</emphasis> be created on an LFS system as it can cause
516	problems for packages you may wish to build once your base LFS system is
517	complete.</para>
518	</warning>
519
520	<warning>
521	<para>The headers in the system's <filename
522	class="directory">include</filename> directory (<filename
523	class="directory">/usr/include</filename>) should
524	<emphasis>always</emphasis> be the ones against which Glibc was compiled,
525	that is, the sanitised headers installed in <xref
526	linkend="ch-tools-linux-headers"/>. Therefore, they should
527	<emphasis>never</emphasis> be replaced by either the raw kernel headers
528	or any other kernel sanitized headers.</para>
529	</warning>
530
531	</sect2>
532
533	<sect2 id="conf-modprobe" role="configuration">
534	<title>Configuring Linux Module Load Order</title>
535
536	<indexterm zone="conf-modprobe">
537	<primary sortas="e-/etc/modprobe.d/usb.conf">/etc/modprobe.d/usb.conf</primary>
538	</indexterm>
539
540	<para>Most of the time Linux modules are loaded automatically, but
541	sometimes it needs some specific direction. The program that loads
542	modules, <command>modprobe</command> or <command>insmod</command>, uses
543	<filename>/etc/modprobe.d/usb.conf</filename> for this purpose. This file
544	needs to be created so that if the USB drivers (ehci_hcd, ohci_hcd and
545	uhci_hcd) have been built as modules, they will be loaded in the correct
546	order; ehci_hcd needs to be loaded prior to ohci_hcd and uhci_hcd in order
547	to avoid a warning being output at boot time.</para>
548
549	<para>Create a new file <filename>/etc/modprobe.d/usb.conf</filename> by running
550	the following:</para>
551
552	<screen><userinput>install -v -m755 -d /etc/modprobe.d
553	cat > /etc/modprobe.d/usb.conf << "EOF"
554	<literal># Begin /etc/modprobe.d/usb.conf
555
556	install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i ohci_hcd ; true
557	install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe -i uhci_hcd ; true
558
559	# End /etc/modprobe.d/usb.conf</literal>
560	EOF</userinput></screen>
561
562	</sect2>
563
564	<sect2 id="contents-kernel" role="content">
565	<title>Contents of Linux</title>
566
567	<segmentedlist>
568	<segtitle>Installed files</segtitle>
569	<segtitle>Installed directories</segtitle>
570
571	<seglistitem>
572	<seg>config-&linux-version;,
573	vmlinuz-&linux-version;-lfs-&version;,
574	and System.map-&linux-version;</seg>
575	<seg>/lib/modules, /usr/share/doc/linux-&linux-version;</seg>
576	</seglistitem>
577	</segmentedlist>
578
579	<variablelist>
580	<bridgehead renderas="sect3">Short Descriptions</bridgehead>
581	<?dbfo list-presentation="list"?>
582	<?dbhtml list-presentation="table"?>
583
584	<varlistentry id="config">
585	<term><filename>config-&linux-version;</filename></term>
586	<listitem>
587	<para>Contains all the configuration selections for the kernel</para>
588	<indexterm zone="ch-bootable-kernel config">
589	<primary sortas="e-/boot/config">/boot/config-&linux-version;</primary>
590	</indexterm>
591	</listitem>
592	</varlistentry>
593
594	<varlistentry id="lfskernel">
595	<term><filename>vmlinuz-&linux-version;-lfs-&version;</filename></term>
596	<listitem>
597	<para>The engine of the Linux system. When turning on the computer,
598	the kernel is the first part of the operating system that gets loaded.
599	It detects and initializes all components of the computer's hardware,
600	then makes these components available as a tree of files to the
601	software and turns a single CPU into a multitasking machine capable
602	of running scores of programs seemingly at the same time</para>
603	<indexterm zone="ch-bootable-kernel lfskernel">
604	<primary sortas="b-lfskernel">lfskernel-&linux-version;</primary>
605	</indexterm>
606	</listitem>
607	</varlistentry>
608
609	<varlistentry id="System.map">
610	<term><filename>System.map-&linux-version;</filename></term>
611	<listitem>
612	<para>A list of addresses and symbols; it maps the entry points and
613	addresses of all the functions and data structures in the
614	kernel</para>
615	<indexterm zone="ch-bootable-kernel System.map">
616	<primary sortas="e-/boot/System.map">/boot/System.map-&linux-version;</primary>
617	</indexterm>
618	</listitem>
619	</varlistentry>
620
621	</variablelist>
622
623	</sect2>
624
625	</sect1>

Note: See TracBrowser for help on using the repository browser.

Download in other formats: