ExamFinch.com My Study

Study guide

4.2 Understanding Computer Hardware

Practice this exam

LPI Linux Essentials Certificate 010-160

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Study Strategy & Blueprint Weights

2 Topic 1: The Linux Community and a Career in Open Source

1.1 Linux Evolution and Popular Operating Systems 1.2 Major Open Source Applications 1.3 Open Source Software and Licensing 1.4 ICT Skills and Working in Linux

3 Topic 2 Part A: Command Line Basics & Getting Help

2.1a Bash Shell, Command Syntax & Variables 2.1b Quoting, History & Safe Command Syntax 2.2 Using the Command Line to Get Help

4 Topic 2 Part B: Directories, Listing & File Operations

2.3 Using Directories and Listing Files 2.4 Creating, Moving and Deleting Files

5 Topic 3 Part A: Archiving & Searching Data

3.1 Archiving and Compression on the Command Line 3.2a Pipes, Redirection, and Basic Regular Expressions 3.2b grep and Text Extraction Tools

6 Topic 3 Part B: Turning Commands into Scripts

3.3a Script Basics: Shebang, Variables, and Arguments 3.3b Loops, Exit Status, and Simple Conditionals 3.3c Editors, chmod +x, and Running Scripts

7 Topic 4 Part A: Choosing an OS, Hardware & FHS Basics

4.1 Choosing an Operating System 4.2 Understanding Computer Hardware 4.3a Where Programs and Configuration Live (FHS Basics)

8 Topic 4 Part B: Processes, Logs & Networking

4.3b Processes, Memory & Logs 4.4 Your Computer on the Network

9 Topic 5: Security and File Permissions

5.1 Basic Security and Identifying User Types 5.2 Creating Users and Groups 5.3 Managing File Permissions and Ownership 5.4 Special Directories and Files

4.2 Understanding Computer Hardware

Key Takeaways Explain This Topic AI

The motherboard connects the CPU, memory, storage controllers, and expansion slots; the power supply (PSU) delivers stable electrical power to those components

Processors (CPUs) execute instructions; peripherals (keyboard, mouse, printers, NICs) extend the system beyond the case

Hard disk drives (HDDs) and solid-state disks (SSDs) store data; partitions divide a disk into separately managed regions

Linux traditionally exposes SCSI/SATA-style disks as /dev/sd* device nodes (for example /dev/sda , /dev/sda1 )

Drivers are software that lets the kernel talk to hardware; missing or wrong drivers mean devices may not work even if they are physically installed

Last updated: July 2026

Understanding Computer Hardware

Linux runs on physical (or virtualized) hardware. Objective 4.2 expects familiarity with the components that make up desktop and server computers—not electronics engineering. Know what each part does, how storage is divided, how Linux names disks under /dev , and why drivers matter.

Partial list from the official objectives: motherboards , processors , power supplies , optical drives , peripherals ; hard drives , solid state disks and partitions , /dev/sd* ; and drivers .

Core building blocks

  • Component Role
  • Motherboard Main circuit board; sockets/slots connect CPU, RAM, storage controllers, NICs, and expansion cards
  • Processor (CPU) Executes program instructions; cores and clock speed affect throughput

Memory (RAM) Fast volatile storage for running programs (not listed alone in 4.2’s short list, but tied to motherboard/CPU operation)

  • Power supply (PSU) Converts wall power to the voltages components need; undersized PSUs cause instability
  • Optical drive Reads/writes CDs, DVDs, or Blu-ray discs (less common on modern laptops, still exam vocabulary)
  • Peripherals External or add-on devices: keyboards, mice, monitors, printers, USB gadgets, webcams, extra NICs

The motherboard is the traffic hub. The CPU plugs into a socket and talks to RAM through memory channels designed into the board. Storage devices attach via SATA, NVMe, or USB bridges wired to controllers on the board. Expansion slots (PCIe and similar) accept graphics cards, RAID controllers, or additional network cards. If the motherboard fails, the whole system usually fails even when disks and PSUs are healthy.

The PSU is easy to underestimate. Servers and workstations with many disks and GPUs need higher wattage and reliable connectors. When a machine randomly reboots under load, hardware technicians often check power before blaming the OS.

Optical drives matter historically for installing media and for archival discs. Many cloud VMs have no optical hardware at all; physical desktops may still include one or rely on USB optical drives. On the exam, treat “optical” as CD/DVD-class removable optical media hardware.

Peripherals are everything that extends the computer for humans or for I/O: input devices, printers, scanners, external disks. Linux must load an appropriate driver (kernel module or userspace support) before many peripherals become usable.

Storage: HDD, SSD, and partitions

Storage type Characteristics

HDD (hard disk drive) Spinning magnetic platters; larger capacities historically cheaper per GB; mechanical latency

  • SSD (solid state disk) Flash memory; much faster random I/O; no moving parts; common for OS and databases
  • Partition A bounded region of a disk treated as a separate block device for filesystems

An HDD stores data magnetically on rotating platters; an SSD stores data in flash chips. Both appear to the OS as block devices once the controller and driver initialize them. You typically partition a disk before installing filesystems: for example, a small boot partition, a root filesystem, and maybe a separate /home . Partitioning lets you isolate data, choose different filesystem types, and reinstall the OS without wiping user files when layouts are planned carefully.

Virtual machines still present virtual disks that look like HDDs/SSDs to the guest; the same partition ideas apply.

Linux disk names: /dev/sd*

Linux represents many devices as special files under /dev . Traditional SCSI, SATA, and USB mass-storage disks commonly appear as:

  • Path pattern Meaning
  • /dev/sda First disk of the sd class
  • /dev/sdb Second disk
  • /dev/sda1 First partition on /dev/sda
  • /dev/sda2 Second partition on /dev/sda

The letters increment ( a , b , c …) for successive disks; partition numbers append to the disk name. Essentials highlights /dev/sd* because it is the classic pattern in learning materials. Modern NVMe devices often use names like /dev/nvme0n1 instead—useful to know in practice—but when an exam item mentions /dev/sda1 , think “first partition of the first sd disk.”

Never confuse the device node ( /dev/sda ) with a mounted directory ( /mnt/data ). The device is the raw disk; after you create a filesystem and mount it, you access files through a path in the directory tree.

Drivers: software that unlocks hardware

A driver is software—often a kernel module —that teaches the OS how to communicate with a specific device. Without a working network driver, the NIC may power on but never pass packets. Without a printer driver (or a compatible driverless protocol), print jobs stall.

On Linux, many drivers ship with the kernel and load automatically when hardware is detected. Others come from distribution packages or, less ideally, proprietary vendor blobs. Virtual machines use paravirtual or emulated devices with well-supported drivers; bare metal may need firmware files under paths such as those used by linux-firmware packages.

Symptoms of driver problems: device missing from lsusb / lspci visibility tools (when available), network interface not appearing, blank screens on unsupported GPUs, or USB gadgets that show power but no functionality. Essentials-level response: understand that hardware alone is not enough —the kernel needs matching driver support.

How the pieces fit for an Essentials candidate

Picture a server build: motherboard + CPU + RAM + PSU + SSD. You connect a USB keyboard (peripheral) for the installer, boot an ISO from USB or optical media, partition /dev/sda , install Linux, and confirm the NIC driver brings up networking. Each buzzword in 4.2 maps to a step in that story.

Cloud instances hide the motherboard and PSU behind the hypervisor, but the guest still sees virtual CPUs, virtual disks ( /dev/sd* or similar), and needs drivers for virtio or emulated devices. The vocabulary remains the same.

  • Exam traps to avoid
  • Treating /dev/sda as a folder of files instead of a block device node
  • Assuming every disk is still named /dev/hd* (old IDE naming)—Essentials emphasizes /dev/sd*
  • Forgetting that partitions are numbered ( sda1 , sda2 )
  • Believing drivers are optional “extras” rather than required for many devices
  • Confusing optical drives with SSDs—optical is disc media; SSD is solid-state primary storage

Master the table of components, the HDD/SSD/partition distinction, the /dev/sd* pattern, and the purpose of drivers, and objective 4.2 becomes a straightforward vocabulary section.