SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor · Updated 2026-11-06

Linux distros: Slackware, Debian and Red Hat family tree

See how Linux distros grow from Slackware, Debian or Red Hat, plus the package managers and release choices your VPS image inherit.

Wetin Linux distribution really be

The history of Linux distributions start with one gap: Linux kernel by itself no fit do anything wey person fit use. E go boot and find hardware. Then e go stop. Somebody must add userland, choose how to install and update software, and promise to keep fixing am for years. Distribution na that set of choices, plus the group of people wey remain afterwards.

E get five parts. Projects wey choose dem differently na different distributions, even when most of the binaries match:

  • Kernel, for version wey the project choose, with the patches and drivers wey e add. One release fit offer more than one: Ubuntu 24.04 LTS dey install GA (general availability) kernel for servers by default and e offer the newer HWE (hardware enablement) kernel as option.
  • Userland: C library, shell, init system, and standard commands.
  • Package format, plus the tool wey install am.
  • Release policy: wetin fit change, how often e fit change, and how long dem go fix each release.
  • People: package maintainers, security team, and person wey go answer when package break.

Kernel na the shared part, so two Linux distributions dey much closer to each other than either one dey to another Unix. Make you remember this when you compare Linux and FreeBSD as server platforms, where one project build and release the kernel and base userland together. For Linux, separate upstreams provide those parts, and distribution na the thing wey make dem agree.

History of Linux distributions for three families

Three projects wey start for 1993 and 1994 later become families: Slackware, Debian and Red Hat. Almost every image wey dey VPS control panel today na one of dem or descendant of one. Descendant dey inherit package format, file layout and usually release habits. Na why Debian derivative still dey feel like Debian even after dem remove the branding.

The independent distributions deserve their own line because nobody fork dem. Arch, Gentoo, Alpine, NixOS and Void each write their own package manager and their own rules. Two of dem, Arch and Alpine, still end up for your provider image list, but the reason no relate to desktop.

1992: the distributions wey come before the families

MCC Interim Linux show for February 1992. Owen Le Blanc assemble am for Manchester Computing Centre. E put the kernel and GNU (GNU's not Unix) tools for two floppy images, with menu-driven installer. E exist because to do all that by hand fit take one full day work.

Peter MacDonald release SLS (Softlanding Linux System) for 1992. E go further by adding X (the X Window System) and TCP/IP networking. SLS na why the word distribution get the meaning wey e get today. But e get plenty bugs and maintenance slow. For 1993, two people separately decide to fix am. One rebuild am. The other start again with written rules.

Slackware, 1993: family wey still dey release till today

Patrick Volkerding release Slackware 1.00 on 16 July 1993. E build am from SLS after e remove the bugs. Dem still dey maintain am, so na the oldest Linux distribution wey still survive.

Slackware package na compressed tar archive wey get install script inside. Dependency resolution no dey happen: nothing dey check whether the library wey your new package need don already dey disk. That one decision shape everything wey follow. If the tool no fit resolve dependencies, the package set wey dem release must make sense by itself. So releases dey come rarely and dem dey conservative. Slackware 15.0 arrive for February 2022, six years after 14.2.

The family small. SUSE first releases for middle of the 1990s build on Slackware, before the project take its own direction with YaST and, later, the RPM package format. Na this last part dey confuse people. SUSE and openSUSE dey use RPM packages, and dem no be Red Hat derivatives. The format travel. The lineage no travel with am.

Debian, 1993: social contract and pipeline wey get three suite

Ian Murdock announce Debian on 16 August 1993, one month after Slackware and for the same reason. Dem form the name from im partner Debra name and im own name. Debian Manifesto follow for January 1994 and set the terms: volunteers go maintain this distribution openly, no be company.

Debian later write the terms down. Dem adopt Debian Social Contract and DFSG (Debian free software guidelines) for July 1997, and DFSG become the basis for Open Source Definition for 1998. Document wey dem write to settle wetin fit enter one distribution later define licence category for the whole industry. Na also why your sources.list get components: main hold software wey meet the guidelines and no need anything outside main, contrib hold software wey also meet dem but need something outside main to build or run, non-free hold software wey no meet dem, and Debian 12 add non-free-firmware so laptop wey get wireless card fit install without plenty searching.

The tooling na the other inheritance. dpkg install one package and refuse when something dey missing, then print dpkg: dependency problems prevent configuration of. APT (Advanced Packaging Tool), wey become the default with Debian 2.1 for 1999, na the layer wey work out wetin else to fetch and the order to fetch am. Every apt command for every Debian derivative come from that work.

The release machine get three suites and one rule. Maintainer upload to unstable, wey always get codename sid. Script dey migrate the package go testing after 2, 5 or 10 days, depending on the upload urgency, if dem build am and e up to date for every architecture wey dem build am for before, e no get release critical bug wey the testing version no get, and e install without breaking anything wey already dey for testing. Testing later freeze, release team clear wetin remain, and stable ship when the bug list don short reach enough. No be on fixed date. Na why Debian stable dey look old and dey behave well: version numbers mostly stop for the freeze, while security fixes dey backport into dem. Mostly, because security team sometimes release newer upstream version instead, like dem do for Tomcat 11 for June 2026.

Governance too dey written down, with project leader wey dem elect and binding general resolutions. For 2014, Technical Committee choose systemd as the default init system, and people wey disagree fork Devuan, wey make im first stable release for 2017. Debian no be the first distribution to make that change, and e no be the last. The reasons why e keep happening, together with objections wey later turn out correct, dey explain for the account of how systemd replace SysV init. The bigger descendants na Ubuntu, Raspberry Pi OS, Proxmox VE, Kali and Linux Mint.

Red Hat, 1994: RPM, then how e split into Fedora and RHEL

Marc Ewing release the first Red Hat Linux around Halloween 1994. Bob Young company buy am for 1995, and the two build Linux business wey first dey sell software for box. Red Hat enter public market on 11 August 1999. IBM complete the company acquisition for July 2019 for about 34 billion dollars, so IBM don own the distribution wey most enterprise software dey certify against ever since.

The technical contribution wey last na RPM (Red Hat package manager), wey Erik Troan and Marc Ewing write for Red Hat Linux 2.0 for 1995. RPM dey declare the dependencies wey e need, and dem dey produce am from spec file, wey be build recipe anybody fit run. Na this second property make independent rebuilds of Red Hat enterprise product possible later.

Red Hat Linux 9 for 2003 na the last for the original line. The company split am into two: Fedora Core 1 for November 2003 as the fast community release, and RHEL (Red Hat Enterprise Linux), wey start as Advanced Server 2.1 for 2002, as the slow paid one. The reason clear. One product no fit be both the place wey new versions dey get test and the platform wey bank go run untouched for ten years. The two halves still connect: major RHEL version branch from Fedora release, dem stabilise am, then freeze am. The package tool move with the same schedule, from yum for the 2000s to dnf as Fedora default for 2015, with rpm underneath both.

Why CentOS stop to be free RHEL rebuild

CentOS start for 2004 with one simple work: take the source packages wey Red Hat publish, remove the trademarks, rebuild dem, then give the result free. E become the default free server distribution for ten years, and Red Hat bring the project inside the company for 2014.

For 8 December 2020, Red Hat announce say CentOS Linux 8 go end for 31 December 2021, eight years before the date wey dem publish before, and say the name go continue as CentOS Stream. Stream no be rebuild. Na the branch wey RHEL use cut minor releases from, so e dey ahead of RHEL instead of behind am. For machine wey you plan to keep for years, ahead no be the correct direction, because you go receive changes before Red Hat paying customers receive dem.

Two rebuilds show for 2021. Gregory Kurtzer start Rocky Linux; na him co-found CentOS. CloudLinux fund AlmaLinux. For June 2023, Red Hat stop publishing RHEL sources for git.centos.org and direct public collaboration go CentOS Stream. Customers and partners still get RHEL source access through the customer portal, and source images remain publicly available together with the UBI (Universal Base Image) containers. Rocky continue to target identical rebuilds. AlmaLinux change its target to ABI (application binary interface) compatibility. This mean say software wey dem build for RHEL go run, but dem no promise say the bug list go match line by line. Oracle, SUSE and CIQ set up OpenELA later that year to publish shared sources. The full sequence, from the 2003 split to the 2023 source change and wetin each rebuild promise now, dey explained for the longer account of Red Hat, CentOS, Rocky and AlmaLinux.

If provider image list still get CentOS, first find out which one e mean before you build on top am.

cat /etc/os-release

NAME="CentOS Stream" na rolling development branch wey dey lead to RHEL. NAME="AlmaLinux" or NAME="Rocky Linux" na RHEL compatible distribution wey get ten-year window for each major release.

Ubuntu, 2004: Debian unstable wey dey follow calendar

Ubuntu 4.10 release on 20 October 2004, and Mark Shuttleworth fund am. The relationship between Ubuntu and Debian na mechanical matter, e no be sentiment. Every cycle dey start by importing packages from Debian unstable enter the new Ubuntu release. The imports dey continue until Debian Import Freeze for middle of the cycle. After that, Ubuntu dey carry its own changes. Plenty Ubuntu packages na Debian package plus one delta, and changelog dey show which one.

The other half na the calendar. Debian dey release when e ready. Ubuntu dey release for April and October, and version number na the date: 24.04 come out for April 2024. Every second April release na LTS (long term support), and na this one provider mean when e list Ubuntu without qualifier. Which of the two you suppose use for server na the main subject of choosing between Ubuntu LTS and interim releases, and moving from one LTS go the next one get its own procedure, wey the 24.04 to 26.04 upgrade cover.

One detail dey catch server admins every year. Ubuntu archive split into components. main Canonical dey maintain am for the full support window. universe community dey maintain am, and the security coverage get different promise. apt install no show anything about the difference. One command go show am:

apt-cache policy nginx

Repository line wey end with /main mean say Canonical security team dey responsible for that package. Line wey end with /universe mean community security coverage under standard support; Ubuntu Pro add Canonical security coverage through ESM Apps. Check am for anything wey dey face the internet.

Arch, 2002: rolling releases and the cost of a partial upgrade

Judd Vinet release Arch 0.1 on 11 March 2002, with package manager wey e write by himself, pacman, and build recipes wey be plain shell scripts. Arch no get versioned releases at all. The install media na dated snapshots of the same rolling repositories, so machine wey dem install for 2019 and update every week dey run the same Arch as machine wey dem install today. AUR (Arch user repository) hold build recipes wey users contribute. Dem na recipes, no be reviewed packages, so reading PKGBUILD before you run am na part of the work.

Rolling get one failure mode, and na user dey cause am every time. If you install one package with pacman -Sy foo, e go refresh package database and then install one new binary wey link against libraries newer pass the ones wey dey disk. Programs go then fail like this:

error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory

The supported operation na pacman -Syu, wey dey update everything together. The project still dey post news entries wey explain when manual intervention dey required before some upgrades, and if you run the upgrade without reading dem, e fit leave machine wey no go boot.

Because of this, Arch no too good for server wey you plan to ignore. Machine wey you update every week dey okay. Machine wey you update once, then wait one year, go bring every skipped intervention come for one run.

Alpine start around 2005 as fork of Gentoo. LEAF (Linux embedded appliance framework) shape am, and LEAF itself come from Linux Router Project. Natanael Copa build Alpine for appliances, no be for desktops. E replace most of the usual userland: musl instead of GNU C library, BusyBox instead of GNU core utilities, OpenRC instead of systemd, and apk as package manager. Alpine 3.0 for 2014 na the release wey move go musl.

Containers make am popular. Alpine base layer na small part of Debian or Ubuntu base size. So from 2016, e become common base image. Plenty people wey never install Alpine still dey run am every day.

The cost be say musl no be glibc, and the difference dey show as bugs wey look unrelated. Binary wey link against glibc go fail for Alpine with message wey make people search for file wey already dey there:

sh: ./myapp: not found

The program dey there. But e ELF interpreter no dey because glibc loader no dey installed. Python na another regular surprise. Prebuilt wheels wey build for manylinux no go install for musl. So pip go fall back to compiling from source, then stop when compiler no dey installed. musllinux wheel standard from 2021 fix this for projects wey publish those wheels, but e no fix am for any other project.

As host operating system for VPS, Alpine install small and dey update fast. But e put you for path wey most documentation no assume. Every guide wey tell you make you run systemctl enable need translate to rc-update add.

The immutable generation: atomic updates and image based servers

This new branch dey change how updates work instead of changing the package list. An ostree based system dey keep /usr read only. Update na complete new filesystem tree wey system go download, stage, then switch to am for the next reboot. The previous tree remain as boot entry, so if update bad, you fit undo am by rebooting into the old one.

Fedora Silverblue bring this model come desktop for 2018, and Fedora CoreOS bring am come servers for 2019, after Red Hat buy CoreOS for 2018. Flatcar Container Linux continue the original Container Linux after dem retire am for 2020. openSUSE MicroOS reach the same result through btrfs snapshots and transactional-update. For 2024, Red Hat add image based mode to RHEL, built on bootc, where operating system dey ship as container image and you update machine by pointing am to new tag. Talos Linux go furthest and remove shell and SSH completely: you configure the machine through an API, so nothing dey to log in to. NixOS, wey first stable branch come out for 2013, take another direction. The whole system dey build from one declarative configuration, and previous generations remain bootable.

Your provider probably no offer any of these as one-click image, because dem expect you to configure dem for first boot with Ignition or cloud-init, instead of administrator editing files over SSH. Dem dey useful across plenty identical machines. Na the situation you dey enter once you dey manage several Linux servers at once and need proof say every one match the others.

How long one release dey get support?

Release policy na the part of distribution wey you go live with for the longest time, and dem dey publish am as number of years. Na these windows cover 5 current server releases.

ChartSecurity update window for one server release, in years, published policies as of November 2026
Di data wey dey behind dis chart
[
  {
    "distro": "Alpine 3.x",
    "standard_years": 2,
    "extended_total_years": 2
  },
  {
    "distro": "Debian 13",
    "standard_years": 3,
    "extended_total_years": 5
  },
  {
    "distro": "Ubuntu 26.04 LTS",
    "standard_years": 5,
    "extended_total_years": 10
  },
  {
    "distro": "AlmaLinux 10",
    "standard_years": 10,
    "extended_total_years": 10
  },
  {
    "distro": "RHEL 10",
    "standard_years": 10,
    "extended_total_years": 14
  }
]

Alpine dey support the main repository for each 3.x branch for 2 years. E dey support the community repository only until the next stable release. Na why e fit better for container image wey you rebuild often, instead of host wey you leave untouched. Debian security team dey cover stable release for about 3 years. After that, LTS team dey carry selected architectures reach about 5 years altogether. Ubuntu LTS give you 5 years for packages inside main. Ubuntu Pro subscription extend am reach 10 years, and personal users fit use am free for small number of machines. Paid Legacy add on for Ubuntu Pro stretch am further reach 15 years. RHEL 10 publish 10 years. Paid Extended Life Cycle Premium add on stretch am reach 14 years for the final minor release. Renewable Long-Life terms fit extend coverage pass that. AlmaLinux 10 match RHEL window of 10 years without any subscription. Na the whole reason why dem rebuilds dey exist.

Arch no get row here because rolling distribution no get release wey need support. The number wey matter for Arch na how long you fit leave machine untouched. Dem dey measure am in weeks.

Where these numbers come from

Each figure na the vendor own published policy, wey dem read on 4 November 2026. Check dem before you plan around any date, because vendors fit change dem, as CentOS users discover for December 2020.

Why your VPS image list dey look like this

A provider dey ship the images wey customers dey ask for by name and wey fit install unattended for im hypervisor. Na why almost every list dey start with Ubuntu LTS and Debian stable, add AlmaLinux or Rocky for people wey dem software get certification against RHEL, then keep Alpine, Arch and Fedora further down the page. Once you know wetin VPS be and how the image reach the disk, the pattern go clear: the provider dey choose operating systems wey fit survive unattended install and stay supported longer than the average customer dey keep the server.

The choice commit you to more than package manager. E set the upgrade wey you go run in three years, and dem upgrades dey different completely by family. Debian and Ubuntu support in-place major upgrades. RHEL dey run dem through leapp, AlmaLinux get ELevate, and Rocky Linux require fresh installation for supported move between major versions. Arch no get upgrade because e no get version. Alpine own na to edit /etc/apk/repositories and run apk upgrade --available. The choice also set which software you fit install without adding third party repository, who go ship the patch when CVE (common vulnerabilities and exposures) entry land for something wey you dey run, and which init system and C library your future software go expect to dey present.

One more effect dey wey easy to underrate. Most answers wey people write for internet dey assume Debian family path or Red Hat family path, so if you pick outside those two, you go dey translate instructions for the whole life of the machine. Pick the family wey release policy match how often you dey ready to touch the server, then stick with am. To change packages on top easy. To change the distribution under dem mean say you go rebuild the box.

FAQ

Which Linux distribution family my server dey inside?

Run cat /etc/os-release. The ID field dey name the distribution, while ID_LIKE dey name the family. So, Ubuntu machine go report ID_LIKE=debian, and AlmaLinux machine go report ID_LIKE="rhel centos fedora". The package manager na the other clue. apt and dpkg mean Debian family, dnf and rpm mean Red Hat family, apk mean Alpine, while pacman mean Arch.

CentOS still be free version of RHEL?

No. CentOS Linux 8, wey be the last rebuild with that name, end on 31 December 2021. CentOS Linux 7 reach end of life on 30 June 2024. The project wey remain, CentOS Stream, na the branch wey dem dey build RHEL minor releases from. So e dey receive changes before RHEL, no be after am. The free RHEL compatible distributions wey take over the old role na AlmaLinux and Rocky Linux. Both get ten year support window for each major release.

Why Debian stable dey ship version numbers wey old like this?

Because the version number mostly freeze, while the fixes dey continue to come. For most packages, Debian backport security patches into the version wey e release instead of importing newer upstream release. So, package wey show 2.4.57-2+deb13u1 fit carry fix wey dem publish last week. The suffix after the upstream version na the Debian revision, and apt changelog <package> list wetin enter inside am. If you judge Debian server security by the version numbers, you go always get wrong answer.

I suppose run rolling release like Arch for VPS?

Only if you go update am according to schedule. Rolling distribution assume say every machine go reach the current package set. So, if you update one package with pacman -Sy foo, libraries fit mismatch and errors like cannot open shared object file fit happen. Run pacman -Syu regularly, read the project news page before each run, and the system go stable. If you leave am for one year, the first upgrade go become the risky one.

Wetin immutable or atomic distribution really change?

E change when updates dey apply and how you fit undo dem. /usr dey mount read only. An update dey stage as one complete new tree, then the switch happen when system reboot. The previous tree remain as boot entry for rollback. You get machine wey either fully update or fully no update, without half-applied state. You no fit install software by editing files in place again, so applications move enter containers or layered packages.

Dis article help you?