Linux is a family of systems built around the Linux kernel, not a single product from one vendor.
Which object answered Linux?
The kernel is the privileged component that manages hardware-backed resources and provides system calls to user space.
A distribution combines that kernel with user-space programs, package policy, defaults, and an update channel. That distinction matters during incident response: a kernel version, a distribution release, and a shell version answer different questions.
| Question | Inspect | Example answer |
|---|---|---|
| Which kernel is running? | uname -sr | Linux 6.8.0 |
| Which distribution describes itself? | /etc/os-release | Debian GNU/Linux 12 |
| Which shell is executing? | $SHELL and the process tree | /bin/bash |
The name GNU/Linux highlights the substantial GNU user-space contribution, while “Linux” remains common shorthand for the complete system.1
Inspect without executing output
The metadata on this transcript says that only prompt lines are copyable and that the example must never be executed automatically.
$ uname -s
Linux
$ . /etc/os-release
$ printf '%s\n' "$PRETTY_NAME"
Debian GNU/Linux 12 (bookworm)The same idea in a script keeps code distinct from its output:
#!/usr/bin/env bash
set -o errexit -o nounset -o pipefail
uname -srTrust boundaries
flowchart LR
User[User space] -->|system call| Kernel[Linux kernel]
Kernel --> Hardware[Hardware]
Packages[Distribution packages] --> UserThe diagram is intentionally local: it has no initialization directive, click handler, script, or remote resource.
This unsafe link remains text but loses executable attributes.
A small checklist
- Separate the kernel from the distribution.
- Treat console output as evidence, not as a command.
- Record the exact package and update source during an investigation.
Attribution is part of technical accuracy: identify the component that actually supplied the behavior you observed.
Footnotes
-
Naming conventions vary by community. This chapter uses the more precise term when attribution affects the technical explanation. ↩