Skip to main content

A Step-by-Step Guide to the Linux Boot Process

 

A Step-by-Step Guide to the Linux Boot Process:

                             1. In Linux, the booting process is a technique of starting the computer system after it has been turned on.

                             2. The Linux operating system's booting system will be discussed here.


There are two styles of booting:
 
               1. Cold booting: When a computer is turned on after it has been turned off for an extended period. 

               2. Warm booting: When a machine crashes or freezes, the operating system is the only thing that gets restarted.



BIOS 

                1. The BIOS (Basic Input/Output System) is a computer operating system that allows you to input and output data.  

                2. BIOS gives control to the boot loader programme once it has been discovered and loaded into memory. 

               3. It gave or contains information about MBR. 

               4. The BIOS loads and run the MBR or BIOS loads and executes the MBR boot loader. 

MBR

                1. MBR --------> Master Boot Record

                2. It's in the bootable disk's first sector(/dev/hda, or /dev/sda). 

                3. MBR have a partition of 512 bytes 
                              446 bytes- primary boot loader. 
                              64 bytes - partition table.
                              2 bytes - MBR validation check.

                4. It gave information about GRUB.

               5. MBR loads and runs the GRUB boot loader.


GRUB 

               1. GRUB -------->Grand Unified Bootloader

              2. Grub configuration file - /boot/grub/grub.conf .

               3. It gave information about kernel and initrd image.

               4. GRUB loads and runs the kernel and initrd image


 Kernel

                1. Kernel is a heart of linux. 

                2. It loads temporary root filesystem

                3. Kernel runs first process called init or systemd [ Pid = 1 ].

                4. initrd -------> Initial RAM Disk.


Init 
              1. The Linux run level is determined by the /etc/inittab file. 
              2. The available run levels are listed below. 
                                0 – halt 
                                1 – Single user mode
                                2 – Multiuser, without NFS 
                                3 – Full multiuser mode 
                                4 – unused
                                5 – X11 [GUI] 
                                6 – reboot
Run level 
                1. The system will run applications from one of the following folders, depending on your default init level option.
                               Run level 0 – /etc/rc.d/rc0.d/ 
                               Run level 1 – /etc/rc.d/rc1.d/
                               Run level 2 – /etc/rc.d/rc2.d/ 
                               Run level 3 – /etc/rc.d/rc3.d/
                               Run level 4 – /etc/rc.d/rc4.d/ 
                               Run level 5 – /etc/rc.d/rc5.d/
                               Run level 6 – /etc/rc.d/rc6.d/
                 2. You can see that some of the files in the "/etc/rc.d/rc*.d/" directories begin with S and K
                 3. The beginning of the programmer is During starting, the letter S is utilized. S stands for "startup." 
                 4. During shutdown, programmers that begin with the letter K are used. K stands for kill. 
That is all there is to it. During the Linux boot process, this is what happens.











Comments

Popular posts from this blog

How to Check Hardware Details on Linux:

  Whether you're troubleshooting hardware issues, planning an upgrade, or just curious about your system’s specifications, Linux provides a variety of commands to gather comprehensive hardware information. Here are some essential commands: 1.  Use lscpu to get detailed information about the CPU, including architecture, cores, threads, and CPU speeds. # lscpu                                                 2. The lshw command provides a complete overview of hardware configuration, including CPU, memory, storage, and network. You’ll likely need superuser privileges to run it. # sudo lshw                                                                               ...

testing

09052025 T-1 { "volume_groups" : { "vgroot" : { "vgsize" : "304G" , "fs_type" : "xfs" } } , "logical_volumes" : { "root" : { "lvroot" : { "vgname" : "vgroot" , "lvname" : "lvroot" , "lvsize" : "12G" , "mountpoint" : "/" , "purpose" : "root filesystem" , "disk" : 1 , "partition" : 2 } } , "swap" : { "lvswap" : { "vgname" : "vgroot" , "lvname" : "lvswap" , "lvsize" : "4G" , "mountpoint" : "NA" , "purpose" : "swap" , "disk" : 1 , "partit...

How Virtual Machines are Created in OpenStack: A Complete Backend Workflow:

When creating a Virtual Machine (VM) in OpenStack, several components work together in the backend to provision the instance. Here's a step-by-step explanation of how the process flows: 1. User Request Interface Used : The user initiates the VM creation through the Horizon Dashboard (web UI), the OpenStack CLI ( openstack server create ), or the OpenStack API. Request Information : The request includes parameters such as: VM name. Image (the operating system or custom image to boot from). Flavor (the compute, memory, and storage specifications). Network (which network the VM will be connected to). Security Groups (firewall rules). Key Pair (for SSH access). 2. API (Nova API) Component : Nova (Compute service). Process : The request is received by the Nova API , which validates the request (checks if the requested resources like the image, flavor, and network exist). If valid, the API creates an entry in the database for the new instance. Nova's Role : Nova is the core service r...