Linux Distributions and Release Models

1. What a distribution actually provides

A distribution selects a kernel build, user-space utilities, package manager, repositories, installer, boot defaults, security policies, release process, and support lifecycle. It also decides which versions are tested together.

2. Major distribution families

3. Fixed, LTS, and rolling release models

flowchart TB
  N["Operational need"] --> S{"Change tolerance"}
  S -->|"Low"| LTS["Long-term support release"]
  S -->|"Moderate"| FIX["Regular fixed release"]
  S -->|"High"| ROLL["Rolling release"]
  LTS --> A["Long support window and conservative versions"]
  FIX --> B["Periodic upgrades and balanced freshness"]
  ROLL --> C["Continuous updates and frequent integration work"]

4. Package formats, repositories, and dependency graphs

Package files are only one part of distribution management. Repositories provide signed metadata, dependency relationships, update channels, and mirrors. The package manager resolves a graph of compatible versions rather than simply downloading one executable.

• Debian family: .deb, dpkg, and higher-level APT commands.
• RPM families: .rpm, the RPM database, and higher-level tools such as DNF or Zypper.
• Alpine: .apk packages managed by apk.
• Arch: packages managed by pacman.

5. Identify a distribution reliably

# Standard distribution metadata
cat /etc/os-release

# Selected fields suitable for scripts
. /etc/os-release
printf 'ID=%s\n' "$ID"
printf 'VERSION_ID=%s\n' "${VERSION_ID:-unknown}"
printf 'ID_LIKE=%s\n' "${ID_LIKE:-none}"

# Kernel information is a separate concern
uname -r

# Detect an available package manager
for tool in apt-get dnf yum zypper apk pacman; do
  if command -v "$tool" >/dev/null 2>&1; then
    printf 'Found package manager: %s\n' "$tool"
  fi
done

ID_LIKE can indicate ancestry, but scripts should still test the exact command or capability they require. Distribution labels are weaker than capability detection.

6. Select by operational constraints

7. Host distributions and application environments

DevOps teams often separate the host operating system from application runtime environments. A stable host may run containers containing different user-space distributions. CI pipelines may build on several images to test compatibility.

8. Hands-on lab: create a distribution capability report

lab="$HOME/devops-academy/linux/chapter01/lesson03"
mkdir -p "$lab"
cd "$lab"

. /etc/os-release

{
  printf '=== identity ===\n'
  printf 'NAME=%s\n' "$NAME"
  printf 'ID=%s\n' "$ID"
  printf 'VERSION_ID=%s\n' "${VERSION_ID:-unknown}"
  printf 'ID_LIKE=%s\n' "${ID_LIKE:-none}"

  printf '\n=== kernel ===\n'
  uname -sr

  printf '\n=== package capabilities ===\n'
  for tool in apt apt-get dpkg dnf rpm zypper apk pacman; do
    if command -v "$tool" >/dev/null 2>&1; then
      command -V "$tool"
    fi
  done

  printf '\n=== service manager ===\n'
  ps -p 1 -o comm=

  printf '\n=== C library ===\n'
  getconf GNU_LIBC_VERSION 2>/dev/null || ldd --version 2>&1 | head -n 1 || true
} > distribution-report.txt

less distribution-report.txt

9. Common selection mistakes

10. Knowledge check

11. Summary

A distribution is an integration and lifecycle system around the Linux kernel. Families differ in packaging, defaults, governance, and support. Fixed and LTS releases optimize controlled change; rolling releases optimize continuous freshness. Sound selection starts with workload and operating constraints.

12. Further reading

• os-release(5) manual page — standard operating-system identification fields.
• Debian, Ubuntu, Fedora, Red Hat Enterprise Linux, openSUSE, Alpine, and Arch official lifecycle documentation.
• Filesystem Hierarchy Standard — cross-distribution directory conventions.
• Distribution package-manager documentation for APT, DNF, Zypper, apk, and pacman.
• OCI Image Specification — container image layers and configuration.