{"id":19723,"date":"2023-07-11T04:53:21","date_gmt":"2023-07-11T04:53:21","guid":{"rendered":"https:\/\/linuxways.net\/?p=19723"},"modified":"2023-11-13T06:13:54","modified_gmt":"2023-11-13T06:13:54","slug":"linux-boot-process","status":"publish","type":"post","link":"https:\/\/linuxways.net\/de\/linux-commands\/linux-boot-process\/","title":{"rendered":"Linux Boot Process"},"content":{"rendered":"

When a user presses the system’s power button or restart button, the login screen appears on their monitor. After logging in, the machine begins to function. There are several steps that are involved from pressing the power button to getting the login screen; this process is called the boot process.<\/p>\n

Here, we will discuss and understand about the Linux boot process in details. We can divide the boot process into six steps:<\/p>\n

    \n
  1. The BIOS<\/a><\/li>\n
  2. MBR<\/a><\/li>\n
  3. GRUB<\/a><\/li>\n
  4. Kernel<\/a><\/li>\n
  5. Init<\/a><\/li>\n
  6. Runlevels<\/a><\/li>\n<\/ol>\n

    Here is one simple diagram to understand the whole Linux process.<\/p>\n

    <\/p>\n

    The BIOS (Basic Input Output System): Starting Point of the Booting Process<\/strong><\/h2>\n

    The BIOS is where the hardware and software first interact. When the system powers up, the power supply begins to distribute the current to the different parts of the computer so they can operate. When the CPU receives the current from the power supply, it searches for a special programme that helps load the operating system into the computer’s memory. This programme is called BIOS. The BIOS is a special programme which is hardwired into the motherboard itself.<\/p>\n

    BIOS first performs an integrity check which is called a \u201cPower On Self Test (POST)\u201d. The POST process verifies whether all of the computer’s hardware like RAM, hard drive, CD-ROM drive, keyboard, etc., are working fine or not. If no error occurs, the boot process will continue. But if any error is encountered, it generates a beep sound, and the computer will not boot up.<\/p>\n

    After the POST, the BIOS selects the first boot device and gives back the control to the CPU. If it does not find the first boot device, it checks for the second device, and so on. If it has not found any boot devices, it shows the “No Boot Device Found” error.<\/p>\n

    MBR (Master Boot Record)<\/strong><\/h2>\n

    After the BIOS, the control is back to the CPU. Now, the CPU loads the MBR to the memory.<\/p>\n

    The first sector of a hard drive contains the MBR that indicates the system about the hard drive details and loads the steps for the operating system.<\/p>\n

    MBR is a location on the disk with the following details:<\/p>\n

      \n
    • The primary boot loader information is stored in the first 446 bytes.<\/li>\n
    • The next 64 bytes store the Partition table information.<\/li>\n
    • The last 2 bytes store the magic number.<\/li>\n<\/ul>\n

      From given information, we can get the MBR as 512 bytes in size.<\/p>\n

      The primary boot loader information is the location of the actual boot loader. Using this location, the CPU loads the actual boot loader (GRUB).<\/p>\n

      MBR contains 64 bytes Partition table which stores the following data:<\/p>\n

        \n
      • First and last address of each partition.<\/li>\n
      • What is the size of partition?<\/li>\n
      • What is the type of partition?<\/li>\n<\/ul>\n

        The last 2 bytes of the MBR store the magic number. Here, the magic number is 0xAA55 which is used for validation check of the MBR.<\/p>\n

        So, the primary boot loader\u2019s task is to find and load the secondary boot loader.<\/p>\n

        GRUB (GRand Unified Bootloader)<\/strong><\/h2>\n

        The GRUB is a boot loader which is responsible to load the kernel.<\/p>\n

        This loader displays the GRUB menu from which we can choose the required operating system. If the user has not chosen any one from the menu with an optional timeout after the waiting time, the default one is loaded to the memory.<\/p>\n

        After loading the kernel, it gives control to the kernel.<\/p>\n

        Kernel<\/strong><\/h2>\n

        Here are the sequences that are followed in kernel:<\/p>\n

          \n
        1. The Linux kernel is first read into the memory.<\/li>\n
        2. After loading the kernel into memory, the following things happen:<\/li>\n<\/ol>\n

          The kernels are located in the \/boot directory in compressed format.<\/p>\n

          After loading inside memory, it unzips itself from the zipped version. At the beginning of the kernel image, there is a routine which is responsible to extract from the compressed version.<\/p>\n

          After self-extracting, the chosen kernel mounts the root file system which is specified in the \u201cgrub.conf\u201d file.<\/p>\n

          Here is one sample \u201cgrub.conf\u201d file content:<\/p>\n

          #boot=\/dev\/sda<\/span>
          \n
          \ndefault<\/span>=0<\/span>
          \n
          \ntimeout<\/span>=5<\/span>
          \n
          \nsplashimage<\/span>=(<\/span>hd0,0<\/span>)<\/span>\/<\/span>boot\/<\/span>grub\/<\/span>splash.xpm.gz
          \n
          \nhiddenmenu
          \n
          \ntitle CentOS (<\/span>7.2.18-324<\/span>.el5PAE)<\/span>
          \n
          \nroot (<\/span>hd0,0<\/span>)<\/span>
          \n
          \nkernel \/<\/span>boot\/<\/span>vmlinuz-7.2.18-324<\/span>.el5PAE ro root<\/span>=LABEL<\/span>=\/<\/span>
          \n
          \ninitrd \/<\/span>boot\/<\/span>initrd-7.2.18-324<\/span>.el5PAE.img<\/div><\/div>\n

          From the previous file, we can see the entry of the kernel and the initrd image.<\/p>\n

          Then, it starts the \/sbin\/init programme. Init is the first program which is executed by the kernel. So, the PID of init is 1. To get the init\u2019s PID, the following command can be used:<\/p>\n

          $ <\/span>ps<\/span> -ef<\/span> |<\/span> grep<\/span> init<\/div><\/div>\n

          It initialises and sets up all of the system’s hardware after being loaded into the memory.<\/p>\n

          Then, it searches for the compressed initramfs image(s) in a specific area of memory, decompresses them directly to \/sysroot\/, and loads all the required drivers.<\/p>\n

          It finishes the initramfs operations and releases all the memory that the disc image previously used by initializing the virtual devices that are connected to the file system.<\/p>\n

          The root device is then created by the kernel, along with the root partition which is mounted as read-only and any unused RAM are released.<\/p>\n

          The kernel is now active and loaded into the memory. There aren’t any user apps that allow the system to receive a significant input, so not much can be done with it. The kernel runs the \/sbin\/init programme to configure the user environment.<\/p>\n

          Init<\/strong><\/h2>\n

          The \/etc\/inittab contains a script that is read by init. The initial configuration script, which essentially takes care of everything a system has to do when it is initializing, is read by init. This includes the following:<\/p>\n

            \n
          • setting the clock<\/li>\n
          • initializing the serial port<\/li>\n
          • other tasks<\/li>\n<\/ul>\n

            Init decides how the system should be configured for each runlevel by reading this file, and it also establishes the default run level.<\/p>\n

            Init starts all background processes which are necessary to keep the system running after deciding on the system’s default runlevel. The kill scripts, whose file names begin with a K, are first executed with the stop option. To start all services and apps, it then executes all start scripts whose file names begin with S.<\/p>\n

            Runlevels<\/strong><\/h2>\n

            A runlevel is a Linux system software setting that only allows a predetermined set of processes to exist. Runlevels decide about the programmers which are allowed to run after the OS is running.<\/p>\n

            There are seven runlevels which are numbered from 0 to 6.<\/p>\n

            The following table describes the function of each runlevel:<\/p>\n\n\n\n\n\n\n\n\n\n\n
            Runlevel<\/strong><\/td>\nFunction<\/strong><\/td>\n<\/tr>\n
            0<\/td>\nIt shuts down the system.<\/td>\n<\/tr>\n
            1<\/td>\nIt operates in single user mode.<\/td>\n<\/tr>\n
            2<\/td>\nIt operates in multiuser mode without networking.<\/td>\n<\/tr>\n
            3<\/td>\nIt operates in multiuser mode with networking.<\/td>\n<\/tr>\n
            4<\/td>\nIt is defined by the user.<\/td>\n<\/tr>\n
            5<\/td>\nA multiuser with networking and X windows.<\/td>\n<\/tr>\n
            6<\/td>\nIt reboots or restarts the system.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            The runlevel 0 \u201cshuts down the system\u201d.<\/p>\n

            Runlevel 1 is a single-user mode in which the non-root logins are not permitted, the networking is not available, but the configuration files and passwords can be changed.<\/p>\n

            There are no networking daemons at runlevel 2, and multiple users are not supported.<\/p>\n

            Runlevel 3 allows networking and command line interface.<\/p>\n

            We are able to construct the new runlevels as of run level 4.<\/p>\n

            The runlevel 5 is used in maximum Linux systems.<\/p>\n

            The runlevel 6 \u201creboots or restarts the system\u201d.<\/p>\n

            The runlevel program can be executed from the following directories:<\/p>\n

            Runlevel 0<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc0.d\/<\/span>
            \n
            \nRunlevel 1<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc1.d\/<\/span>
            \n
            \nRunlevel 2<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc2.d\/<\/span>
            \n
            \nRunlevel 3<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc3.d\/<\/span>
            \n
            \nRunlevel 4<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc4.d\/<\/span>
            \n
            \nRunlevel 5<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc5.d\/<\/span>
            \n
            \nRunlevel 6<\/span> \u2013 \/<\/span>etc\/<\/span>rc.d\/<\/span>rc6.d\/<\/span><\/div><\/div>\n

            We can check all programs under \/etc\/rc.d\/rc*.d\/ folder. For example, if we want to see the runlevel in four files, we can check the \u201cls \/etc\/rc4.d\/\u201d directory.<\/p>\n

            If the program name starts with \u201cS\u201d, it is used at the start time. If the program name starts with \u201cK\u201d, it is used at the time of shutdown.<\/p>\n

            Here are the ways to change the runlevel:<\/p>\n

            – init command<\/p>\n

            – telinit command<\/p>\n

            The default runlevel in the \/etc\/inittab file can be modified by the user. Here is the command:<\/p>\n

            $init<\/span> <<\/span>runlevel_value><\/span>
            \n
            \n$ telinit <<\/span>runlevel_value><\/span><\/div><\/div>\n

            To interact with\u00a0init, the \/dev\/initctl\u00a0control channel should be used rather than\u00a0SIGPWR\u00a0and\u00a0\/etc\/powerstatus.<\/p>\n

            The \/<\/strong>sbin\/telinit\u00a0is linked up with\u00a0\/sbin\/init.\u00a0Telinit takes up an argument and send signals to \u00a0init\u00a0to do the required action.<\/p>\n

            Here is the table:<\/p>\n\n\n\n\n\n\n\n\n
            Argument<\/strong><\/td>\nFunction<\/strong><\/td>\n<\/tr>\n
            0,1,2,3,4,5,6<\/td>\nSwitch to specified runlevel<\/td>\n<\/tr>\n
            a, b, c<\/td>\nProcesses only the file entries from\u00a0\/<\/strong>etc\/inittab\u00a0having runlevel a,b, c<\/td>\n<\/tr>\n
            q or q<\/td>\nRe-examines the \/<\/strong>etc\/inittab file<\/td>\n<\/tr>\n
            s or s<\/td>\nSwitches to a single user mode<\/td>\n<\/tr>\n
            u or u<\/td>\nInit re-executes itself<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            If we want to find out our current system runlevel, we can use the following command:<\/p>\n

            $ <\/span>who<\/span> -r<\/span><\/div><\/div>\n

            To see all help related to Linux \u201crunlevel\u201d command, use the following commands:<\/p>\n

            $ runlevel \u2013h
            \n
            \nOr
            \n
            \n$ runlevel \u2013help<\/span>
            \n
            \nOr
            \n
            \n$ man<\/span> runlevel<\/div><\/div>\n

            These are the six processes which happen in background when the user presses the power button of the system.<\/p>\n

            Conclusion<\/strong><\/h2>\n

            We learned the Linux boot process in details. We also learned the booting component and run levels which are very important for system administrator, developer, and also for the users of the Linux operating system. There are many detailed steps in each area, but we tried to cover the overall process in this short article.<\/p>","protected":false},"excerpt":{"rendered":"

            Practical guide on the Linux boot process and the booting component and run levels for system administrator, developer, and users of the Linux operating system.<\/p>","protected":false},"author":111,"featured_media":19725,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1049],"tags":[],"class_list":["post-19723","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-commands"],"_links":{"self":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/19723","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/users\/111"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/comments?post=19723"}],"version-history":[{"count":0,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/19723\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media\/19725"}],"wp:attachment":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media?parent=19723"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/categories?post=19723"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/tags?post=19723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}