Context Navigation

source: chapter10/kernel.xml@ 31e6ccb2

Visit:

multilib xry111/multilib

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

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

Download in other formats: