2.1.9. Identify common features and tools of the Linux client/desktop operating system. (Obj. 1.9)

💡 First Principle: Proficiency in the Linux command line is essential for managing files, permissions, and packages efficiently.

Linux is a powerful, open-source operating system that comes in many different flavors called distributions (or "distros"). While less common on corporate desktops than Windows, it's the backbone of the internet, running on the vast majority of servers, cloud infrastructure, and embedded devices. As a technician, you may encounter it on developer workstations or in specialized environments. Each distro (like Ubuntu, Fedora, or Mint) might have a different look and feel (desktop environment), but they all share the same underlying Linux kernel and a powerful command line.

Figure: Linux terminal (GNOME Terminal with Bash shell) - command-line interface for Linux administration

The command line, or terminal, is the heart of Linux administration. While modern Linux distros have excellent GUIs, a technician must be comfortable with the terminal for efficient management.

• Core Commands:
  • ls: Lists the contents of a directory (ls -l for a detailed list).
  • cd: Changes the current directory (e.g., cd /var/log).
  • pwd: Prints the working directory (shows you where you are).
  • mv, cp, rm: Move, copy, and remove files/directories, respectively.
  • chmod: Changes the permissions of a file. For example, chmod 755 script.sh makes a script executable. Numeric (octal) mode uses three digits - owner, group, others - each the sum of read = 4, write = 2, execute = 1: 7 = rwx, 5 = r-x, 0 = no access, so chmod 640 gives the owner read/write, the group read-only and others nothing. Symbolic mode changes one bit at a time: chmod +x file adds execute, chmod u+x file adds it for the owner only.
  • chown: Changes the owner of a file.
  • sudo: The most important command to know. It stands for "Super User Do" and allows a standard user to execute a single command with root (administrator) privileges. This is the preferred method for performing administrative tasks, as it's more secure than logging in as the root user directly.
  • apt / dnf / yum: These are package managers. They are the primary way to install, update, and remove software on Linux. Debian-based systems like Ubuntu use apt (e.g., sudo apt update and sudo apt install gimp). Red Hat-based systems like Fedora use dnf or yum.
  • ip or ifconfig: Used to view and manage network interface configurations. ip addr is the modern command to show IP addresses.
  • grep: A powerful search tool that finds lines of text matching a pattern within files. Syntax: grep "pattern" file (add -i to ignore case, -r to search a directory tree). It searches file contents; use find to locate files by name, size or date.
  • ps: Lists currently running processes.
  • top: Interactive, continuously updating view of processes with their CPU and memory use (ps is a one-time snapshot; htop is a friendlier add-on version).
  • find: Locates files by name, size, owner or time, e.g., find /var/log -name "*.log", -size +50M (larger than 50 MB), -mtime -7 (modified in the last 7 days); -ls or -exec ls -l {} + lists the matches in detail.
  • cat, head, tail: Print a whole file, its first lines, or its last lines (10 by default, -n N to change); tail -f follows a log as it grows.
  • man: Opens the manual page for a command (man chmod); Windows-style /? does not work.
  • su vs. sudo: su - switches the whole session to another account (root by default); sudo elevates a single command. root is the superuser account with unrestricted privileges.
  • fsck: Checks and repairs a Linux filesystem (the chkdsk equivalent); run it on an unmounted partition. mount attaches a filesystem to a directory; df / du show free and used space.
  • curl: Transfers data to or from a server using URL syntax across many protocols (HTTP/S, FTP, SFTP and more) - handy for fetching a page or testing an API. wget is a simpler HTTP/HTTPS/FTP downloader; dig queries DNS.
• Key Configuration Files: /etc/passwd (user accounts), /etc/shadow (hashed passwords, root-readable only), /etc/hosts (static hostname-to-IP mappings checked before DNS), /etc/resolv.conf (which DNS servers to use) and /etc/fstab (filesystems mounted automatically at boot).
• OS Components: The kernel is the core that sits between hardware and software, managing CPU scheduling, memory and devices. The shell (e.g., Bash) is the command interpreter users type into; the bootloader (GRUB) loads the kernel at startup; systemd is the init system on most modern distributions - the first process the kernel starts - and manages services.

Technician's Action Plan: Scenario: A developer is using a laptop running Ubuntu Linux. She needs to install the htop utility, a popular interactive process viewer, to monitor her application's resource usage. She has tried to run apt install htop but gets a "permission denied" error.

1. Identify the Error: Recognize that the "permission denied" error when using a package manager is almost always due to a lack of administrative privileges. Installing software affects the entire system and requires elevated rights.
2. Explain the sudo Command: Explain to the user that on Linux, standard users cannot make system-wide changes by default for security reasons. To perform an administrative task, they must preface the command with sudo. This temporarily elevates their privileges for that single command, and they will be prompted for their own password to authorize it.
3. Provide the Correct Command: Instruct the user to run two commands in sequence:
   • First, sudo apt update. Explain that this command doesn't install anything but instead synchronizes the local package list with the online software repositories to ensure they are getting the latest version.
   • Second, sudo apt install htop. This is the command that will actually download and install the application.
4. Guide the Execution: Tell the user to enter their password when prompted after the first sudo command. Note that for a short period after, subsequent sudo commands may not require a password.
5. Verify the Installation: Once the installation completes without errors, instruct the user to simply type htop in the terminal and press Enter. The htop interface should launch, confirming that the application was installed successfully and is now ready to use.

Reflection Question: Why is the sudo command considered a more secure way to perform administrative tasks on Linux than logging in directly as the root user?