Context Navigation

source: chapter10/kernel.xml@ 898d71a

Visit:

multilib xry111/multilib

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

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

Download in other formats: