Version 1 · Chapter 14Reading mode

Know the machine before changing it

By the end: Identify the kernel, distribution, CPU, and available hardware without assuming they are interchangeable.

The idea

The kernel version is not the distribution release. A container, virtual machine, and physical host can expose different slices of system information. Collect only what is needed for your diagnosis, and remove host identifiers or serial numbers before sharing output.

Your command toolkit

uname

What it solves: Identify the kernel and architecture.

bash

uname -srmo

Shows kernel name/release, machine architecture, and operating system where supported. Distribution branding needs a separate source.

hostname

What it solves: Read the current host name.

bash

hostname

A hostname identifies the machine locally; it does not prove that a matching public DNS record exists.

hostnamectl

What it solves: Inspect host metadata on systemd systems.

bash

hostnamectl status

Displays host and operating-system details. Setting a hostname is a separate administrative action.

lscpu

What it solves: Inspect CPU topology.

bash

lscpu

Distinguish logical CPUs, cores, and sockets. Virtualization and CPU quotas can limit the capacity actually available to a workload.

lsb_release

What it solves: Read distribution release information.

bash

lsb_release -a

This optional command summarizes distribution metadata. /etc/os-release is another common source when it is not installed.

lspci

What it solves: Identify PCI devices and drivers.

bash

lspci -k

Useful for identifying network and graphics hardware. Containers may not expose the host's devices.

dmidecode

What it solves: Understand firmware hardware inventory.

bash

dmidecode --help

Real inventory reads often need privileges and can contain serial numbers. Firmware-provided values may be incomplete or inaccurate.

Before you move on

Try the guided lab below. Compare the result with the explanation, then record your reasoning in the workbook. A missing optional program or a restricted environment is something to explain, not a reason to change system settings blindly.

Practice with evidence

Predict the result
Run the guided lab
Compare the output
Explain your choice

A worked example

Guided lab

bash

uname -srmo
cat /etc/os-release
lscpu | head -n 12

What to expect: Separate kernel and distribution information, followed by CPU metadata. Exact values depend on the environment.

Make it yours: Write a short environment report with kernel, distribution, and architecture. Explain one reason CPU counts might not equal the capacity available to an application.

Read further

Debian reference: Linux fundamentals ↗www.debian.org

Apply what you learned

Your private practice

Write a short environment report with kernel, distribution, and architecture. Explain one reason CPU counts might not equal the capacity available to an application.

Does uname -r identify the Linux distribution release?No, it identifies the kernel releaseYes, alwaysOnly when run as root

Answers are private. Completion requires the correct knowledge-check answer and a written response when an activity is included.

Restore a downloaded workbook

Choose a recovery file for this course and version. Review the recovered copy before saving it to your account.

Workbook recovery file

Ask a question or report a problem

Describe what needs attention. Your private answer is shared only if you select the option below.