Context Navigation

source: chapter10/kernel.xml@ 7d40eeb

Visit:

multilib

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

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

Download in other formats: