%general-entities; ]> linux &linux-version;

&linux-url;

Linux Building the kernel involves a few steps—configuration, compilation, and installation. Read the README file in the kernel source tree for alternative methods to the way this book configures the kernel. Prepare for compilation by running the following command: make mrproper This ensures that the kernel tree is absolutely clean. The kernel team recommends that this command be issued prior to each kernel compilation. Do not rely on the source tree being clean after un-tarring. Configure the kernel via a menu-driven interface. BLFS has some information regarding particular kernel configuration requirements of packages outside of LFS at : make LANG=<host_LANG_value> LC_ALL= menuconfig LANG=<host_LANG_value> LC_ALL= This establishes the locale setting to the one used on the host. This is needed for a proper menuconfig ncurses interface line drawing on UTF-8 linux text console. Be sure to replace <host_LANG_value> by the value of the $LANG variable from your host. If not set, you could use instead the host's value of $LC_ALL or $LC_CTYPE. Alternatively, make oldconfig may be more appropriate in some situations. See the README file for more information. If desired, skip kernel configuration by copying the kernel config file, .config, from the host system (assuming it is available) to the unpacked linux-&linux-version; directory. However, we do not recommend this option. It is often better to explore all the configuration menus and create the kernel configuration from scratch. Compile the kernel image and modules: make If using kernel modules, an /etc/modprobe.conf file may be needed. Information pertaining to modules and kernel configuration is located in and in the kernel documentation in the linux-&linux-version;/Documentation directory. Also, modprobe.conf(5) may be of interest. Install the modules, if the kernel configuration uses them: make modules_install After kernel compilation is complete, additional steps are required to complete the installation. Some files need to be copied to the /boot directory. The path to the kernel image may vary depending on the platform being used. The following command assumes an x86 architecture: cp -v arch/x86/boot/bzImage /boot/lfskernel-&linux-version; System.map is a symbol file for the kernel. It maps the function entry points of every function in the kernel API, as well as the addresses of the kernel data structures for the running kernel. Issue the following command to install the map file: cp -v System.map /boot/System.map-&linux-version; The kernel configuration file .config produced by the make menuconfig step above contains all the configuration selections for the kernel that was just compiled. It is a good idea to keep this file for future reference: cp -v .config /boot/config-&linux-version; Install the documentation for the Linux kernel: install -d /usr/share/doc/linux-&linux-version; cp -r Documentation/* /usr/share/doc/linux-&linux-version; It is important to note that the files in the kernel source directory are not owned by root. Whenever a package is unpacked as user root (like we did inside chroot), the files have the user and group IDs of whatever they were on the packager's computer. This is usually not a problem for any other package to be installed because the source tree is removed after the installation. However, the Linux source tree is often retained for a long time. Because of this, there is a chance that whatever user ID the packager used will be assigned to somebody on the machine. That person would then have write access to the kernel source. If the kernel source tree is going to be retained, run chown -R 0:0 on the linux-&linux-version; directory to ensure all files are owned by user root. Some kernel documentation recommends creating a symlink from /usr/src/linux pointing to the kernel source directory. This is specific to kernels prior to the 2.6 series and must not be created on an LFS system as it can cause problems for packages you may wish to build once your base LFS system is complete. The headers in the system's include directory should always be the ones against which Glibc was compiled, that is, the sanitised headers from this Linux kernel tarball. Therefore, they should never be replaced by either the raw kernel headers or any other kernel sanitized headers. Installed files config-&linux-version;, lfskernel-&linux-version;, and System.map-&linux-version; Short Descriptions config-&linux-version; Contains all the configuration selections for the kernel /boot/config-&linux-version; lfskernel-&linux-version; The engine of the Linux system. When turning on the computer, the kernel is the first part of the operating system that gets loaded. It detects and initializes all components of the computer's hardware, then makes these components available as a tree of files to the software and turns a single CPU into a multitasking machine capable of running scores of programs seemingly at the same time lfskernel-&linux-version; System.map-&linux-version; A list of addresses and symbols; it maps the entry points and addresses of all the functions and data structures in the kernel /boot/System.map-&linux-version;