Linux is just the kernel

The exchange with Vivian started from a recruiting diagram that ranked sysadmin profiles across four “layers”, from the base OS up to containers. The recruiting critique I grant him gladly, it lands: plenty of adverts say “Linux” to mean Debian plus systemd plus Docker and never look below that. But to spar properly on the subject you first need a bit of pedantry, the kind I get gently ribbed for and happily own: Linux is just the kernel.

The useful pedantry

Linux, strictly speaking, is the kernel and nothing else. What we handle daily and call “a Linux distribution” is the kernel packaged with a userspace, most often the GNU project’s, hence the famous GNU/Linux that Stallman reminds us of at regular intervals. This is not a purist’s tic for the pleasure of correcting people: the distinction has concrete consequences.

The proof by absurdity is that a distribution can run without Linux. Debian, for instance, has existed on kernels other than Linux, with Debian GNU/kFreeBSD (FreeBSD’s kernel) and Debian GNU/Hurd (GNU’s microkernel). In those variants the kernel changes, but what makes Debian stays identical: the GNU system on top, the social contract, the package format, the organization of the distribution. In other words, what you identify as “Debian” is precisely not the kernel, it is everything else.

Hence the value of a good distribution tree, which shows the real genealogy (what derives from what, Debian, Red Hat, Slackware, Arch and their children) rather than a ranking by “level” that does not mean much. There is one circulating on Wikimedia, not necessarily up to date or exhaustive, but already more coherent than most recruiting diagrams.

What the “layers” actually measure

Now to the substance, because the pedantry was only a warm-up. The four layers people stack to sort profiles (the base OS, the distribution and its tooling, orchestration, containers) do not measure the system, they measure the distribution. They describe how well you know a given ecosystem (Debian’s apt, more or less everyone’s systemd, the Docker on top) and that is real information, but it is not what you think you are ranking when you talk about mastery of Linux.

Because the common denominator of all these systems, the one you find from Alpine to Fedora to Gentoo, is the kernel. And that is precisely the layer you actually administer: you configure it, you recompile it when you must, you patch it, you sign its modules, you tune the sysctls. That work does not depend on the distribution, it moves intact from Alpine to Fedora to Gentoo and that is exactly why the four layers measure the distribution rather than the system.

Someone who can recompile a kernel with the right config, diagnose a module that refuses to load, or adjust a sysctl to hold a network load, carries that skill everywhere, whatever the package manager on top. Someone who only knows their favourite distribution’s apt and systemctl is, by contrast, genuinely slotted into a layer, but it is not the system they master, it is an ecosystem. The nuance is not cosmetic, it changes what you are evaluating.

Above the kernel, even less of a layer

And all of that is before we even mention Ansible, which finishes off the layered ranking entirely. I drive it from BSD and Linux to Windows hosts (yes, seriously: WinRM, Kerberos, CredSSP, PowerShell payloads and all those ugly things). The day the same playbook drives all of it, from the Alpine server to the Windows workstation, the four layers are simply no longer what defines the job.

Because the skill that counts at that level is no longer “I know this distribution” but “I know how to bring a heterogeneous fleet to a desired state, idempotently, whatever the system in front of me”. That is a cross-cutting skill, indifferent to whether the target runs Linux, BSD or Windows and it demonstrates on its own that the layers sort the tooling, not the know-how.

That is why kernel administration stays, for me, the real foundation. You go down there when you need to load or write a module (which I cover in LKMs ) and it is also there, at the boundary between userspace and the kernel, that the real interface of the system plays out, which I detail in Linux syscalls . Above that boundary the distributions vary, the tooling changes names, but the contract stays the same.

Where to land

I am not out to correct everyone on GNU/Linux and the provocation in the original diagram was useful, as I said. But when you want to rank sysadmin profiles, you had better know what you are measuring: the usual layers tell you how comfortable you are in a distribution ecosystem, which is real information, not a system skill. The system skill is found lower down, at the kernel you configure, recompile, patch and sign and higher up, in the ability to drive a heterogeneous fleet toward its desired state. Between the two sits the distribution and it is the distribution, not the system, that the four layers are sorting.