# 02 - Linux Core Concepts # What is Linux Kernel? * The **Linux kernel** is the core part of the Linux operating system and acts as a bridge between software applications and the computer hardware. * It is responsible for managing the system's resources, such as the CPU, memory, and input/output devices, ensuring efficient and secure operation. * The Linux kernel is **monolithic**, this means that the kernel carries out CPU scheduling, memory management and several operations by itself. * The Linux Kernel is also **modular**, which means it can extends its capabilities through the use of dynamically loaded kernel modules. ## Key Functions of Linux Kernel 1. **Process Management:** * Manages running processes by scheduling them to share CPU resources. * Ensures efficient multitasking and handles process prioritization. 2. **Memory Management:** * Allocates and deallocates memory to processes. * Manages virtual memory, which allows systems to run applications even when physical memory is limited. 3. **Device Management:** * Provides a unified interface for hardware devices (keyboards, disks, network adapters). * Uses device drivers to communicate with hardware components. 4. **System calls and Security:** * Ensures user isolation and process security. * Implements permissions and encryption to safeguard data. ## Linux Kernel Versions * Use `uname` command to get the information about the kernel (by itself it doesn't provide much information except that the system uses the `Linux` Kernel). ```bash $ uname ``` * Use the `uname -r` or `uname -a` comamnd and option to print the kernel version ```bash $ uname -r $ uname -a 4.15.0.72-generic # 4 = kernel version, 15 = major version, 0 = minor version, 72 = path release, generic = Distro specific info ``` ## Kernel Space and User Space * In Linux, the system operates in two distinct regions of memory: **kernel space** and **user space**. * These regions separate system-level operations from user-level processes. ### Kernel Space * **Kernel space** is the memory region in which the kernel executes/operates and provides its services. * A process running in the kernel space has unrestricted/full access to the hardware and system resources. * This space is reserved for core system tasks and cannot be directly accessed by user applications. * It is strictly reserved for running the kernel code, kernel extensions, and device drivers. ### User Space (Userland) * **User space** is the memory region where user applications and processes run. * Applications in user space cannot directly access hardware or system resources; they rely on the kernel to mediate access. * Most Unix-like operating systems, including Linux come pre-packaged with all kinds of utilities, programming languages and graphical tools. This are called user-space applications. ### Interaction Between Kernel Space and User Space * User space and kernel space communicate via **system calls**. * These calls act as a controlled gateway, allowing user applications to request kernel services. * **How System Calls Work:** 1. A user application makes a request (e.g., to open a file). 2. The request is passed to the kernel via a system call (e.g., `open()`). 3. The kernel processes the request and returns the result to the application. --- # Working with Hardware * We will look at how linux works with the hardware resources available to the system and how to make use of kernel modules: * Lets take an example of `USB Disk` be used in the system. * As soon as the `USB device` is attached to the system a corresponding device driver which is part of the kernel space detects the stage change and generates an event. * This event which is called `uevents` is then sent to the `User Space` device manager daemon called `udev`. * The `udev` service is then responsible for dynamically creating a device node associated with the newly attached USB drive in the `/dev/` filesystem. * Once the process is complete, the newly attached disk should be visible under `/dev/` filesystem. ![working-with-hardware](https://github.com/kodekloudhub/linux-basics-course/raw/master/images/working-with-hardware.PNG align="left") * Use `dmesg` display messages from the area of kernel called `Ring Buffer`. * When a linux operating system boots up there were numerous messages generated by the kernel that appear on the display screen. These messages also contain logs from the hardware devices that the kernel detects and provide good indication wheather it is able to configure. ```bash $ dmesg $ dmesg | grep -i usb ``` * The `udevadm` is the management utility for `udev` which queries the database for device information. ```bash $ udevadm info --query=path --name=/dev/sda5 ``` * The `udevadm monitor` listens to the kernel new `uevents` upon detecting an event, it prints the details such as the `device path` and the `device name` on the screen. This command is handy to determine the details of the newly attached or removed device. ```bash $ udevadm monitor ``` * The `lspci` command list all PCI (Peripheral Component Interconnect) devices that are configured in the system. Examples of PCI devices are `Ethernet Cards`, `RAID Controllers`, `Video Cards` and `wireless Adaptors` that directly attached to PCI slots in the motherboard of the computer. ```bash $ lspci ``` * To list information about `Block Devices` ```bash $ lsblk ``` * To display detail information about the `CPU` such as CPU architecture, the number of cores, threads, model, cpu op-modes (32 bit, 64 bit) etc. ```bash $ lscpu ``` * To list available memory in the system. ```bash $ lsmem --summary ``` * Another alternate command to see the information about the memory. This command will list total used and free memory. ```bash $ free -m # -m is to display the memory in mb, use k for kb and g for gb ``` * To extract detail information about the entire hardware information of the machine such as exact memory configuration, firmware version, mainboard configuration, CPU version and speed, cache configuration, bus speed, etc. ```bash $ lshw ``` ## SUDO * In Linux, `sudo` (short for "superuser do") is a command that allows users to execute commands with elevated privileges, typically as the **root user.** ### **How Does** `sudo` Work? 1. **Privileges:** * When a user runs a command with `sudo`, the system temporarily elevates their privileges, allowing them to execute commands that require administrative rights. 2. **Password Prompt:** * By default, `sudo` requires the user's password (not the root password) to confirm their identity and authorize the command. 3. **Time-limited Access:** * Once a user successfully enters their password, they won’t need to re-enter it for subsequent `sudo` commands within a default timeout period (typically 15 minutes). ### **The** `sudoers` File * The `sudoers` file controls who can use `sudo` and what commands they are allowed to execute. * **Location:** `/etc/sudoers` * **Editing Safely:** Use `visudo` to edit the `sudoers` file to prevent syntax errors. ```bash sudo visudo ``` * **Example Entry in** `sudoers` File: ```plaintext username ALL=(ALL:ALL) ALL # This gives username full administrative privileges ``` --- # Linux Boot ## Sequence Overview * The boot process can be broken down into four stages: 1. BIOS POST 2. Boot Loader (GRUB2) 3. Kernel Initialization 4. INIT Process ### How to initiate a linux boot process? * This can be achieved in one of the two ways. 1. The first method is to start a linux device which is in a halted or stopped state. 2. Second method is to reboot or reset a running system. ### BIOS POST * The first stage, called **BIOS POST** has very little to do with linux itself. * POST Stands for Power On Self Test. * In this stage, BIOS runs a POST test, to ensure the hardware components that are attached to the device are functioning correctly, if POST fails the computer may not be operable and the system will not be proceed to next stage of the boot process. ### Boot Loader * The next stage after BIOS POST is **Boot Loader**. * BIOS loads and executes the boot code from the boot device, which is located in the first sector of the hard disk. In Linux this is located in the `/boot` file system. * The boot loader will provide the user with the boot screen, often with multiple options to boot into, such as Microsoft windows OS or Ubuntu 18.04 OS in an example of a dual boot system. * Once the selection is made at the boot screen, boot loader loads the kernel into the memory supplies it with some parameters and hands over the control to kernel. * A popular example of the boot loader is `GRUB2` (Grand Unified Bootloader Version 2). ### Kernel Initialization * After the kernel is selected, it decompress and then loads kernel into the memory. * At this stage, kernel carries out tasks such as initializing hardware and memory management tasks among other things. * Once it is completely operational , kernel looks for INIT Process to run. Which sets up the `User Space` and the process is needed for the environment. ### INIT Process * The INIT function calls the `systemd` daemon. The `systemd` is responsible for bringing the linux host to usable state. * `systemd` is responsible for mounting the file systems, starting and managing system services. * Once of the key advantages of using `systemd` over `system V(five) init` (used before) is that it reduces the system startup time by parallelizing the startup of services. ### Note: * `ls -l /sbin/init`: To check the `init` system used. * If it is `systemd` then you will see a pointer to `/lib/systemd/systemd`. ```bash $ ls -l /sbin/init # command lrwxrwxrwx 1 root root 20 Feb 6 2020 /sbin/init -> /lib/systemd/systemd # output ``` --- # Run Levels ## Systemd Targets (Run Levels) * We can setup the server to boot either into graphical mode or non-graphical mode. * Linux can run in multiple modes and these modes are set by something called `runlevel`. * The operation mode which provide a graphical interface is called `runlevel 5` * The operation mode which provide a non-graphical mode is called `runlevel 3` * To see the operation mode run in the system. Run the command `runlevel` from the terminal ```bash $ runlevel ``` * In the boot process section, the `systemd` is used as the `init` process in most new linux distributions suchs as `Ubuntu 18.04`. * In `systemd`, runlevels are called as `targets`. * The RunLevel 5 is called as the `graphical target` * The Runlevel 3 is called as the `multiuser target` ![run-levels2](https://github.com/kodekloudhub/linux-basics-course/raw/master/images/run-levels2.PNG align="left") ## Viewing and Changing Systemd Target * `systemctl get-default`: To see the default target. This command looks at the file located at `/etc/systemd/system/default.target` ```bash $ systemctl get-default # command graphical.target # output ``` * `systemctl set-target `: To change the default target. ```bash $ systemctl set-default multi-user.target ``` ## Note: Runlevels * The term runlevels is used in the **sysV init** systems. These have been replaced by systemd targets in **systemd** based systems. * The complete list of runlevels and the corresponding systemd targets can be seen below: **runlevel 0 -> poweroff.target** **runlevel 1 -> rescue.target** **runlevel 2 -> multi-user.target** **runlevel 3 -> multi-user.target** **runlevel 4 -> multi-user.target** **runlevel 5 -> graphical.target** **runlevel 6 -> reboot.target** --- # File Types in Linux * There are three types of files. 1. **Regular File:** Most common type of files that contains text, data, images, etc. 2. **Directory:** Is a type of file that stores other files and directories within. 3. **Special Files:** Are categorized into five other file types: 1. **Character Files:** * These files represent devices under the `/dev` file system that allows OS to communicate to IO devices serially. * Examples: keyboard, mouse, etc. 2. **Block Files:** * These files represent block devices also located under `/dev/` file system. * Examples: hard disks, RAM, etc. 3. **Links:** * Links in linux is a way to associate two or more file names to the same set of file data. * There are two types of links: * **The Hard Link:** * It associates two or more file names that share the same block of data on the physical disk. * Although they behave as an independent files, deleting one link will delete the data. * **The Soft Link:** * Also known as symbolic link or symlink (can be compared to the shortcut we create in Windwos). * Deleting a symlink does not affect the data in the actual file. 4. **Sockets:** * A sockets is a special file that enables the communication between two processes. 5. **Named Pipes:** * The Named Pipes is a special type of file that allows connecting one process as an input to another. * The data flow in a pipe is unidirectional from the first process to the second. ![file-types1](https://github.com/kodekloudhub/linux-basics-course/raw/master/images/file-types1.PNG align="left") ## Identify File Types * Use of the `file` command. ```bash $ file /home/rohit # command /home/rohit/: directory # output $ flle bash-script.sh # command bash-script.sh: Courne-Again shell script, UTF-8 Unicode text # output $ file insync1000.sock # command insync1000.sock: socket # output $ file /home/rohit/bash-script # command /home/rohit/bash-script: symbolic link to /home/xyz/bash-script.sh # output ``` Another way to identify a file type is by making use of the `ls -ld` command ```bash ls -ld /home/rohit # command drwxr-xr-x 3 root root 4096 Mar 18 17:20 /home/rohit # output ls -l bash-script.sh # command -rwxr-xr-x 3 root root 4096 Mar 18 17:20 bash-script.sh # output ``` | **File Type** | **Identifier** | | --- | --- | | DIRECTORY | d | | REGULAR FILE | \- | | CHARACTER DEVICE | c | | LINK | l | | SOCKET FILE | s | | PIPE | p | | BLOCK DEVICE | b | --- # File System Hierarchy * Linux uses single rooted, inverted tree like file system: ![filesystem](https://github.com/kodekloudhub/linux-basics-course/raw/master/images/filesystem.PNG align="left") 1. `/home` : It is the location that contains the home directories for all users, except the `root` user (root user home directory is located at `/root`) 2. `/opt` : If you want to install any third party programs put them in the `/opt` filesystem. 3. `/mnt` : It is the default mount point for any partition and it is empty by default. It is used to mount filesystems temporarly in the system 4. `/tmp` : It is used to store temporary data 5. `/media` : All external media is mounted on `/media` 6. `/dev` : Contains the special block and character device files 7. `/bin` : The basic programs such as binaries `cp`, `mv`, `mkdir` are located in the `/bin` directory 8. `/etc` : It stores most of the configuration files in Linux. 9. `/lib` : The directory `/lib` and `/lib64` is the place to look for shared libraries to be imported into your program 10. `/usr` : In older systems, `/usr` directory is used for `User Home Directories`, however in the modern linux operating systems it is the location where all user land applciations in their data reside 11. `/var` : It contains variable data like mails, log files * To print all the mounted filesystems, run `df` (disk filesystem) command ```bash $ df -hP ``` ---
⏮
Previous Topic: 01 - Working with Shell - I
⏭
Next Topic: 03 - Linux Package Management