Skip to main content

unit 3

1. What do you mean by LILO? What is GNU GRUB? What is Linux swap partition and what does it do?​

LILO (LInux LOader):

  • LILO is a legacy boot loader for Linux systems.
  • It is used to load the Linux operating system into memory during the boot process.
  • LILO stores configuration information in the Master Boot Record (MBR) of the boot device.
  • LILO has limitations compared to modern boot loaders like GRUB, including a lack of support for some file systems and less flexibility in configuration.

GNU GRUB (GRand Unified Bootloader):

  • GNU GRUB (commonly referred to as GRUB) is a modern and highly flexible bootloader for Linux and other operating systems.
  • It is widely used in Linux distributions.
  • GRUB allows users to select from multiple installed operating systems or kernels during boot.
  • It supports various filesystems, configurations, and an interactive command-line interface.
  • GRUB can be configured to load different operating systems, kernel versions, or even custom configurations.

Linux Swap Partition:

  • A Linux swap partition is a dedicated partition on a Linux system used for virtual memory management.
  • It acts as an extension of physical RAM and is used when the physical RAM is fully utilized.
  • When the RAM is full, the Linux kernel can move less frequently used data from RAM to the swap partition to free up space for more important processes.
  • Swap partitions improve system performance by preventing memory-related issues like out-of-memory crashes.
  • The size of the swap partition is typically determined based on the amount of physical RAM and system requirements.
  • Linux can also use swap files instead of dedicated swap partitions.

2.Give hardware requirement for installing Linux operating system.Also elaborate the steps for installing the Red-Hat Linux from DVD?​

The hardware requirements for installing a Linux operating system can vary depending on the specific distribution and your intended use case. Different Linux distributions may have slightly different requirements, but here are some general guidelines for installing a typical desktop Linux distribution:

Minimum Hardware Requirements for personal use:

  1. CPU: A modern x86 or x86-64 (64-bit) processor. Most Linux distributions support both 32-bit and 64-bit architectures.

  2. RAM: 512 MB to 2 GB of RAM is generally sufficient for basic desktop use. However, if you plan to run more memory-intensive applications or use a desktop environment like GNOME or KDE, consider having 4 GB or more for smoother performance.

  3. Storage: At least 10-20 GB of free disk space is recommended for the base installation. Additional space will be required for user data, applications, and software updates. Solid State Drives (SSDs) are recommended for faster performance.

  4. Graphics: A basic graphics card with 3D acceleration support is usually sufficient for most desktop environments.

  5. Display: A monitor with a resolution of 1024x768 pixels or higher is recommended for a comfortable desktop experience.

Recommended Hardware for Better Performance:

  1. CPU: A multi-core processor with higher clock speeds will provide better performance, especially for resource-intensive tasks.

  2. RAM: 4 GB or more RAM for a smoother and more responsive experience, especially if you run multiple applications simultaneously or use virtualization.

  3. Storage: More storage space for user data and applications. An SSD will significantly improve system responsiveness.

  4. Graphics: A dedicated graphics card with good driver support is beneficial if you plan to use graphics-intensive applications like ML model training or gaming. NVIDIA and AMD GPUs are well-supported on Linux.

  5. Network: An Ethernet or Wi-Fi adapter supported by Linux for internet connectivity.

Server-Specific Requirements:

For Linux servers, the hardware requirements depend on the server's intended purpose. Servers typically don't require a graphical user interface (GUI), so they can often run on lower-end hardware. However, factors such as the number of users, the type of services being hosted (e.g., web server, database server), and expected traffic can significantly affect hardware requirements.

To install Red Hat Linux from a DVD, follow these step-by-step instructions:

Note: This guide assumes you have already created a bootable Red Hat Linux DVD.

  1. Insert the Red Hat Linux DVD:

    • Place the Red Hat Linux installation DVD into your computer's DVD drive.

  2. Boot from the DVD:

    • Restart your computer and enter the BIOS/UEFI settings by pressing a specific key during the boot process (common keys include F2, Del, Esc, or F12, depending on your computer's manufacturer).
    • In the BIOS/UEFI settings, set the DVD drive as the first boot device in the boot order.
    • Save the changes and exit the BIOS/UEFI settings. Your computer will now boot from the Red Hat Linux DVD.

  3. Select Installation Language:

    • When the Red Hat Linux installer starts, you will be prompted to select your preferred language for the installation. Choose your language and click "Continue."

  4. Begin Installation:

    • On the next screen, click the "Install Red Hat Enterprise Linux" option to start the installation process.

  5. Network Configuration (Optional):

    • If your computer is connected to a network, you may be prompted to configure your network settings. You can choose to configure it now or later during the installation.

  6. Date and Time Settings:

    • Set your system's date and time settings as per your location and preferences.

  7. Storage Configuration:

    • You will be prompted to select the installation destination. Choose one of the following options:
      • Automatic Partitioning: Let the installer automatically configure the partitions based on your system's available storage.
      • Custom Partitioning: Manually configure partitions if you have specific requirements or need to preserve existing data. Be cautious when using this option, as it involves disk partitioning.

  8. Choose Installation Type:

    • Select the installation type that suits your needs:
      • Server with GUI: For a graphical desktop environment.
      • Server: For a text-based server installation.
      • Minimal Install: For a minimal installation with only essential packages.
      • Custom Software Selection: Allows you to customize software packages.

  9. Begin Installation:

    • Click the "Begin Installation" button to start the installation process. While the installation proceeds, you can configure the root user password and create additional user accounts.

  10. Configuration and User Setup:

    • Set the root password (administrator password) for your system.
    • Create one or more user accounts, specifying their usernames and passwords.

  11. Installation Complete:

    • Once the installation is complete, you'll see a message indicating the successful installation.
    • Click the "Reboot" button to restart your computer and complete the installation.

  12. First Boot:

    • After rebooting, your Red Hat Linux system will start up. Log in with the username and password you created during the installation.

You have successfully installed Red Hat Linux from the DVD.

3. What is Grub? What is the configuration file for grub loader? Explain​

GRUB, which stands for "GRand Unified Bootloader," is a bootloader used in many Linux distributions and other operating systems. It plays a critical role in the boot process by loading the operating system kernel into memory and initializing the system. GRUB is responsible for presenting a boot menu (if multiple operating systems are installed) and allowing users to select which operating system or kernel to boot.

The primary configuration file for GRUB is typically named "grub.cfg" (GRUB Configuration File), and it is located in the "/boot/grub" or "/boot/grub2" directory on your Linux system. This file contains the configuration settings that determine how GRUB behaves during the boot process, including the available boot options and the appearance of the boot menu.

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' 
   /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora_fedora25vm/root 
   rd.lvm.lv=fedora_fedora25vm/swap 
   rd.lvm.lv=fedora_fedora25vm/usr rhgb quiet"
GRUB_DISABLE_RECOVERY="true"

Listing 1: An original grub default file for Fedora 25.

Here's an overview of the key elements and structure of the GRUB configuration file: The article explains how to configure GRUB2, the bootloader used in many Linux distributions, using the "/etc/default/grub" configuration file. Here's a summary of the key points:

  1. GRUB and Configuration Files: GRUB (GRand Unified Bootloader) is responsible for managing the boot process on Linux systems. Configuration files control its behavior.

  2. Old vs. New GRUB: Configuring the original GRUB (GRUB Legacy) was straightforward by editing "/boot/grub/grub.conf." However, GRUB2 is more complex, and editing "/boot/grub2/grub.cfg" directly is discouraged.

  3. Configuration Location: Instead of editing "grub.cfg" directly, the primary configuration file for GRUB2 is "/etc/default/grub."

  4. Keys and Values: The "/etc/default/grub" file consists of key-value pairs, where keys represent configuration settings, and values can be modified to customize the bootloader's behavior.

  5. Common Configuration Keys: The article lists several common configuration keys found in the "/etc/default/grub" file:

    • GRUB_TIMEOUT: Determines the boot menu display time.
    • GRUB_DISTRIBUTOR: Specifies the distribution name in the boot menu.
    • GRUB_DEFAULT: Sets the default kernel to boot.
    • GRUB_SAVEDEFAULT: Saves the last selected kernel as the default.
    • GRUB_DISABLE_SUBMENU: Controls submenu creation in the boot menu.
    • GRUB_TERMINAL_OUTPUT and GRUB_TERMINAL_INPUT: Allow redirection of output and input.
    • GRUB_CMDLINE_LINUX: Contains kernel command-line arguments.
    • GRUB_DISABLE_RECOVERY: Enables or disables recovery entries in the boot menu.

  6. GRUB_TIMEOUT: You can adjust the timeout value to control how long the boot menu is displayed.

  7. GRUB_DEFAULT: Specifies which kernel is booted by default. It can be set to a number or the name of a specific kernel.

  8. GRUB_SAVEDEFAULT: When enabled, this option saves a different kernel as the default if a different one is selected for boot.

  9. GRUB_DISABLE_SUBMENU: This key can be set to "false" to enable submenu creation in the boot menu.

  10. GRUB_TERMINAL_OUTPUT and GRUB_TERMINAL_INPUT: These keys allow redirection of output and input to different terminals or devices.

  11. GRUB_CMDLINE_LINUX: Contains kernel command-line arguments. Users can customize this line to control kernel behavior during boot.

  12. GRUB_DISABLE_RECOVERY: When set to "true," it prevents the creation of recovery entries in the boot menu.

  13. Comments: Lines starting with a '#' character are considered comments and are ignored by GRUB. Comments can be used to provide explanations or notes within the configuration file.

While "grub.cfg" is the primary configuration file, it's important to note that it should not be edited directly by users. Instead, GRUB's configuration is often generated and managed by scripts or tools provided by the Linux distribution. These tools take user settings from files like "/etc/default/grub" (for Debian-based distributions) or "/etc/default/grub" (for Red Hat-based distributions) and use them to generate the "grub.cfg" file.

To make changes to GRUB's behavior or appearance, you should typically edit the appropriate configuration files in "/etc/default" and then regenerate the "grub.cfg" file using the appropriate command for your distribution (e.g., "update-grub" for Debian-based distributions or "grub2-mkconfig" for Red Hat-based distributions). This ensures that your changes are applied correctly and avoids potential errors in the "grub.cfg" file.

4. What is general partitioning scheme while installing Linux Operating System and what do you prefer or recommend. Explain.​

The choice of partitioning scheme when installing Linux depends on your specific needs and use case. However, We can provide a general partitioning scheme that is commonly recommended for most Linux installations. This scheme balances system performance, data organization, and flexibility.

Here's a common and recommended partitioning scheme:

  1. Root Partition (/): This is the primary partition where the Linux operating system is installed. It contains all system files, libraries, and application binaries. It should be relatively large to accommodate the OS and future updates. A typical size is 20-30 GB, but you can allocate more space if you have a larger disk.

  2. Swap Partition: The swap partition provides virtual memory for the system when physical RAM is fully utilized. The size of the swap partition can vary but is often set to 2x the amount of physical RAM. For systems with a large amount of RAM (e.g., 16 GB or more), you can allocate less swap space (e.g., 4-8 GB).

  3. Home Partition (/home): The home partition stores user data, documents, settings, and user-specific configurations. It provides data separation from the system files, making it easier to perform system upgrades or reinstallations without affecting user data. The size of the /home partition depends on your data storage needs. It can occupy the remaining space on the disk.

  4. Boot Partition (/boot): In some cases, a separate /boot partition is used, especially for systems with encryption or complex disk setups. This partition stores the kernel and bootloader files. It is typically small, around 500 MB to 1 GB.

  5. EFI System Partition (ESP): On UEFI-based systems, an EFI System Partition is required to store bootloader files and other EFI-related data. It is typically 100-500 MB in size.

  6. Data Partition (optional): If you have a large disk and want to keep your data separate from the /home partition, you can create a dedicated data partition for storing files, media, and other data. The size depends on your data storage needs.

  7. Other Partitions (optional): Depending on your specific requirements, you may create additional partitions for specific purposes, such as a /var partition for log files or a /tmp partition for temporary files. These are optional and depend on your system's intended use.

Recommendation: For most desktop and general-purpose Linux installations, the recommended partitioning scheme includes separate root (/), swap, and home (/home) partitions. This provides a good balance between system performance and data organization. If you have specific requirements or are setting up a server, you may need to customize the partitioning scheme further.

Always back up your important data before performing disk partitioning and installation to avoid accidental data loss.

5. Explain Partitioning in Linux and why we partition during linux installation? Define main partitions required during Linux installation.​

Partitioning in Linux refers to the process of dividing a physical hard disk drive into separate logical storage units or partitions. Each partition functions as an independent unit with its own filesystem, data, and directory structure. Partitioning is a fundamental step when setting up a Linux system as it allows for better data organization, isolation, and management.

The main purposes of partitioning in Linux are:

  1. Isolation and Organization: By creating separate partitions, you can isolate different types of data and system components. For example, the root partition (/) contains the operating system files, while the home partition (/home) stores user data and configurations. This isolation helps prevent data corruption or loss in case of issues with one partition.

  2. Performance: Disk performance can be improved by placing frequently accessed files and system components on separate partitions. For example, a separate /boot partition can store kernel and bootloader files for faster access during boot.

  3. Security: Partitioning can enhance security by isolating sensitive data or system directories. Encryption can also be applied to individual partitions to protect data.

  4. Backup and Recovery: Having separate partitions makes it easier to back up and restore specific parts of the filesystem, reducing the risk of data loss in case of system failures.

  5. Multi-Boot Configurations: When setting up a dual-boot or multi-boot system with multiple operating systems (e.g., Linux and Windows), partitioning allows you to allocate space for each OS independently.

Main Partitions Required During Linux Installation:

When installing Linux, you typically need the following main partitions:

  1. Root Partition (/): This is the primary partition where the Linux operating system is installed. It contains system files, libraries, and application binaries. The root partition is denoted by "/", and it should have sufficient space to accommodate the OS and future updates. A typical size is 20-30 GB, but you can allocate more space if you have a larger disk.

  2. Swap Partition: The swap partition provides virtual memory for the system when physical RAM is fully utilized. It helps prevent system slowdowns or crashes due to memory shortages. The size of the swap partition can vary but is often set to 2x the amount of physical RAM. For systems with a large amount of RAM (e.g., 16 GB or more), you can allocate less swap space (e.g., 4-8 GB).

  3. Home Partition (/home): The home partition stores user data, documents, settings, and user-specific configurations. It provides data separation from the system files, making it easier to perform system upgrades or reinstallations without affecting user data. The size of the /home partition depends on your data storage needs and can occupy the remaining space on the disk.

These three partitions (root, swap, and /home) constitute the minimum required for a typical Linux installation. Depending on your specific needs and system setup, you may also create additional partitions, such as a /boot partition (for systems with complex disk setups or encryption), a data partition (for storing files and media), or partitions for specific directories like /var or /tmp.

6. What is MBR and GPT? Explain the boot process in Linux.​

MBR (Master Boot Record):

  • MBR is a legacy partitioning scheme used on BIOS-based systems (non-UEFI).
  • It consists of a single 512-byte sector located at the beginning of a storage device (typically a hard drive or SSD).
  • MBR allows you to create up to four primary partitions or three primary partitions and one extended partition with multiple logical partitions inside it.
  • It has limitations, such as a maximum partition size of 2 terabytes (TB) and a limit of four primary partitions.
  • MBR does not support more modern features like secure boot or partitions larger than 2 TB.
  • It uses a 32-bit disk addressing scheme.

GPT (GUID Partition Table):

  • GPT is a modern partitioning scheme used on UEFI-based systems (although it can also be used on BIOS systems).
  • It uses a 64-bit disk addressing scheme, allowing for larger partition sizes (beyond 2 TB).
  • GPT does not have a fixed limit on the number of partitions, so you can create as many partitions as needed.
  • It includes redundancy and backup data structures to protect against data corruption.
  • GPT is a more flexible and robust partitioning scheme, suitable for modern hardware and features like secure boot.

Boot Process in Linux:

The boot process in Linux involves several stages, from BIOS or UEFI initialization to the loading of the Linux kernel and initialization of the system. Here is a simplified overview of the Linux boot process:

  1. BIOS/UEFI Initialization: When you power on or restart your computer, the BIOS or UEFI firmware initializes the hardware components, including the CPU, memory, storage devices, and peripheral devices.

  2. Bootloader Stage 1 (MBR or GPT):

    • On BIOS-based systems (MBR), the BIOS reads the Master Boot Record (MBR) from the boot device (e.g., hard drive) and executes the bootloader code stored in the MBR. This code is typically GRUB or another bootloader.
    • On UEFI-based systems (GPT), the UEFI firmware loads the bootloader from the EFI System Partition (ESP) based on the information stored in the UEFI firmware settings.

  3. Bootloader Stage 2 (GRUB):

    • GRUB (GRand Unified Bootloader) is a common bootloader used in Linux.
    • GRUB loads the kernel and initial RAM disk (initramfs) from the designated partition (e.g., /boot partition).
    • GRUB also presents a boot menu (if configured) that allows you to choose the Linux kernel to boot, including different kernel versions or other operating systems (if present in a multi-boot setup).

  4. Linux Kernel Initialization:

    • Once the kernel is loaded, it initializes the hardware and loads essential drivers for devices like the CPU, memory, storage, and input/output devices.
    • The kernel identifies and mounts the root filesystem specified in the bootloader configuration (e.g., / partition).

  5. Initramfs (Initial RAM Disk):

    • In some cases, an initramfs is used to provide essential drivers and modules required for early system initialization. This is often necessary for systems with complex storage setups, encryption, or specialized hardware.
    • The initramfs is a temporary filesystem loaded into RAM during boot.

  6. Init Process (Systemd):

    • The init process (typically Systemd on modern Linux distributions) is the first user-space process started by the kernel.
    • Systemd initializes the rest of the user-space components, including services, daemons, and user sessions.

  7. User Login: Once the system is fully initialized, it presents a login prompt or graphical user interface for user login.

Note The Linux boot process can vary slightly depending on the distribution and configuration, but these are the fundamental stages involved. The choice of bootloader (GRUB, LILO, etc.) and partitioning scheme (MBR or GPT) can affect certain aspects of the boot process, especially on BIOS vs. UEFI systems.

7. What is disk partition? Write about disk partition naming and numbering convention in Linux. What is fdisk command use for,explain.​

A disk partition is a logical division or section of a physical storage device, such as a hard drive (HDD) or solid-state drive (SSD). Each partition functions as an independent storage unit with its own filesystem, data, and directory structure. Disk partitioning is a way to organize and manage data on storage devices efficiently.

Disk Partition Naming and Numbering Convention in Linux: partition devices are listed in /proc/partition. This file is not a real file but is created on the fly.

In Linux, disk partitions are typically named and numbered following a specific convention:

  1. Primary Partitions: Primary partitions are numbered from 1 to 4 on a traditional Master Boot Record (MBR) partitioning scheme. You can create up to four primary partitions on an MBR disk.

  2. Extended Partitions (Optional): In an MBR partitioning scheme, you can create one extended partition in addition to primary partitions. The extended partition is used to hold multiple logical partitions. It does not have a specific number.

  3. Logical Partitions (Inside Extended): Logical partitions inside an extended partition are numbered starting from 5 onwards. For example, if you have an extended partition, you can create logical partitions as /dev/sda5, /dev/sda6, and so on.

  4. GUID Partition Table (GPT): In GPT partitioning, partitions are identified by globally unique identifiers (GUIDs) rather than numeric IDs. Each partition has a unique GUID, and there are no limitations on the number of partitions.

  5. Device Naming: In Linux, partitions are represented as device files under the /dev directory. For example:

    • The first partition on the first hard drive (e.g., /dev/sda1) or (in GPT) /dev/sda1.
    • The second partition on the second hard drive (e.g., /dev/sdb2) or (in GPT) /dev/sdb2.

fdisk Command: fdisk is a command-line utility used for disk partitioning on Linux systems. It allows you to create, modify, and delete partitions on a storage device. fdisk is commonly used for partitioning on MBR-style disks.

Here are some common fdisk commands and their explanations:

  • fdisk /dev/sdX: Launches fdisk and specifies the target storage device (e.g., /dev/sda) for partitioning.

  • p: Prints the partition table, displaying information about existing partitions on the disk.

  • n: Creates a new partition. You can specify the partition type, starting sector, and size.

  • t: Changes the partition type (e.g., from Linux to swap).

  • d: Deletes a partition. You'll need to specify the partition number.

  • w: Writes changes to the partition table and exits fdisk.

  • q: Quits fdisk without saving changes.

Here's a basic workflow for using fdisk to create a new partition:

  1. Launch fdisk on the target disk (e.g., fdisk /dev/sdX).
  2. Use the n command to create a new partition, specifying its type, starting sector, and size.
  3. Use the w command to write the changes to the partition table and exit fdisk.

Note Keep in mind that fdisk is suitable for MBR-style partitions. For GPT partitions, you would typically use gdisk or parted utilities. Always be cautious when using disk partitioning tools, as incorrect usage can result in data loss.

8. What do you mean by run level? Explain different run level with their function.​

A run level refers to a specific operating state or configuration of the system, which determines which services and processes are running. Run levels are typically used to manage the system's behavior and define its operational mode. Different run levels have distinct purposes and are often used to control system behavior for various tasks, such as booting up, shutting down, or switching between different modes of operation.

Traditionally, Unix-like systems, including Linux, use run levels to manage system states. While the specific run levels can vary between different distributions, here is a general overview of commonly used run levels along with their functions:

  1. Run Level 0 (Halt/Shutdown): This run level is reserved for shutting down the system. When you switch to run level 0, the system will halt and power down. No user-level processes or services are active in this run level.

  2. Run Level 1 (Single User Mode): This is the maintenance or recovery mode. It provides a minimal environment with a single superuser (usually root) logged in. It is often used for system maintenance tasks when you need exclusive access to the system.

  3. Run Level 2 (Multi-User Mode without Networking): In this run level, the system boots into a multi-user mode without network services. It's suitable for situations where networking is not required, such as a standalone desktop.

  4. Run Level 3 (Multi-User Mode with Networking): This is a full multi-user mode with networking enabled. It's the default run level for many Linux distributions when they start up in non-graphical mode. In this run level, you have access to networking services and can have multiple users logged in simultaneously.

  5. Run Level 4 (Undefined/Custom): Run level 4 is typically not used by default in most Linux distributions. It's left undefined, allowing system administrators to customize it for specific purposes or applications.

  6. Run Level 5 (Graphical Mode): This run level starts the system in a graphical user interface (GUI) mode, often with a display manager like GDM (GNOME Display Manager) or KDM (KDE Display Manager). It's suitable for desktop environments and provides a user-friendly interface.

  7. Run Level 6 (Reboot): Similar to run level 0, run level 6 is used for system rebooting. When you switch to this run level, the system will initiate a reboot.

The specific run levels and their functions can vary between different Unix-like operating systems and distributions. Additionally, modern Linux distributions, like systemd-based ones, often use target units instead of traditional run levels for managing system states. Target units offer greater flexibility and are more expressive in describing the desired system behavior. However, the concept of run levels is still useful for understanding the historical organization of system states in Unix-like systems.

9. What is initrd?​

initrd stands for initial RAM disk. It is a temporary filesystem that is mounted during the Linux boot process, typically before the actual root filesystem is mounted. The initrd contains essential programs, modules, and scripts needed to boot the system and load the appropriate kernel modules and drivers to access the root filesystem.