8.3.1. Installation of the kernel
        
        
          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. For general
          information on kernel configuration see 
          http://www.linuxfromscratch.org/hints/downloads/files/kernel-configuration.txt.
          BLFS has some information regarding particular kernel configuration
          requirements of packages outside of LFS at 
          http://www.linuxfromscratch.org/blfs/view/svn/longindex.html#kernel-config-index.
        
        
          ![[Note]](../images/note.png) 
          
            Note
          
          
            Due to recent changes in udev,
            be sure to select:
          
          Device Drivers  --->
  Generic Driver Options  --->
     Maintain a devtmpfs filesystem to mount at /dev
         
        make LANG=<host_LANG_value> LC_ALL= menuconfig
        
          
            The meaning of the make parameters:
          
          
            - 
              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$LANGvariable
                from your host. If not set, you could use instead the host's
                value of$LC_ALLor$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-3.5.2 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, module configuration in /etc/modprobe.d may be required. Information
          pertaining to modules and kernel configuration is located in
          Section 7.4,
          “Device and Module Handling on an LFS System” and
          in the kernel documentation in the linux-3.5.2/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 filename below can be changed to suit your taste,
          but the stem of the filename should be vmlinuz to be compatible with the
          automatic setup of the boot process described in the next section.
          The following command assumes an x86 architecture:
        
        cp -v arch/x86/boot/bzImage /boot/vmlinuz-3.5.2-lfs-7.2-rc1
        
          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. It is used as a resource when investigating
          kernel problems. Issue the following command to install the map
          file:
        
        cp -v System.map /boot/System.map-3.5.2
        
          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-3.5.2
        
          Install the documentation for the Linux kernel:
        
        install -d /usr/share/doc/linux-3.5.2
cp -r Documentation/* /usr/share/doc/linux-3.5.2
        
          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-3.5.2 directory to ensure all files are
          owned by user root.
        
        
          ![[Warning]](../images/warning.png) 
          
            Warning
          
          
            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.
          
         
        
          ![[Warning]](../images/warning.png) 
          
            Warning
          
          
            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.