Hey! Great questions.

It seems like what you’re asking about are more what I’d think of as components of an a Linux “system” or “install.”

First off, it’s definitely worth saying that there aren’t a lot of rules that would apply to “all” Linux systems. Linux is huge in embedded systems, for instance, and it’s not terribly uncommon to find embedded Linux systems with no shells, no DE/WM, and no package manager. (I’m not 100% sure a filesystem is technically necessary. If it is, you can probably get away with something that’s… kinda sorta a filesystem. But I’ll get to that.)

Also, it’s very common to find “headless” systems without any graphical system whatsoever. Just text-mode. These are usually either servers that are intended to be interacted with over a network or embedded systems without screens. But there are a lot of them in the wild.

There’s also Linux From Scratch. You can decide for yourself whether it qualifies as a “distribution”, but it’s a way of running Linux on (typically) a PC (including things like DE’s) without a package manager.

All that I’d say are truly necessary for all Linux systems are 1) a bootloader, 2) a Linux kernel, 3) A PID 1 process which may or may not be an init system. (The “PID 1 process” is just the first process that is run by the Linux kernel after the kernel starts.)

The “bunch of default applications and daemons” feels like three or four different items to me:

• Systemd is an example of an “init system.” There are several available. OpenRC, Runit, etc. It’s main job is to manage/supervise the daemons. Ensure they’re running when they’re supposed to be. (I’ll mention quickly here that Systemd has a lot more functionality built in than just for managing daemons and gets a bad rap for it. Network configuration, cron, dbus for communication between processes, etc. But it still probably qualifies as “an init system.” Just not just an init system.)
• Daemons are programs that kindof run in the background and handle various things.
• Coreutils are probably something I’d list separately from user applications. Coreutils are mostly for interacting with low-ish level things. Formatting filesystems. Basic shell commands. Things like that.
• User applications are the programs that you run on demand and interact with. Terminal emulators, browsers compilers, things like that. (I’ll admit the line between coreutils and user applications might be a little fuzzy.)

As for your question about graphical systems, X11 and Wayland work a little differently. X11 is a graphical system that technically can be run without a desktop environment or window manager, but it’s pretty limited without one. The DE/WM runs as one or more separate processes communicating with X11 to add functionality like a taskbar, window decorations, the ability to have two or more separate windows and move them around and switch between them, etc. A Wayland “compositor” is generally the same process handling everything X11 would handle plus everything the DE/WM would handle. (Except for the Weston compositor that uses different “shells” for DE/WM kind of functionality.)

As far as things that might be missing from your list, I’ll mention the initrd/initramfs. Typically, the way things are done, when the Linux kernel is first loaded by the bootloader, it an “initial ramdisk” is also loaded. Basically, it creates a filesystem that lives only in ram and populates it from an archive file called an “initramfs”. (“initrd” is the older way to do the same thing.) Sometimes the initramfs is bundled into the same file as the kernel itself. But, that initial ramdisk provides an initial set of tools necessary to load the “main” root filesystem. The initramfs can also do some cool things like handling full disk encryption.

So, the whole list of typical components for a PC-installed Linux system to be interacted with directly as I’d personally construct it would be something like:

• Bootloader
• Linux Kernel
• Initramfs
• Filesystem(s)
• Shell(s)
• Init system
• Daemons
• Coreutils
• Graphical system (X11 or Wayland potentially with a DE/WM.)
• User applications
• Package manager

But techinically, you could have a functional, working “Linux system” with just:

• Bootloader
• Linux Kernel
• Either a nonvolatile filesystem or initrd/initramfs (and I’m not 100% sure this one is even strictly necessary)
• A PID 1 process

Hopefully this all helps and answers your questions! Never stop learning. :D

I would say, that from most important to least important components are:

1. kernel
2. init system (systemd, openrc, runit…)
3. C library (glibc, musl)
4. filesystem
5. coreutils
6. shell
7. bootloader
8. package manager
9. x11/Wayland (if any)
10. sound system (if any)
11. WM (if any)
12. DE (if any)

I think you would also need an initial run process such as systemd or the sysV runlevels.

The logo.

Also:

• init system, without which you’d be left with only one program running at a time
• some programs are written in interpreted language (e.g python, shell, perl), so the interpreter would also be required
• C library, without which none of the above would function (yes, even if all the programs are statically compiled, it still has that library included with each executable)
• this one is not necessary for the runtime, but is needed for creating a working system: toolchain – preprocessor, compiler, linker, assembler – all the stuff for transforming the source code into executables

Another comment mentioned Linux From Scratch, I’d totally recommend that, but it would take so much of your time manually building stuff (which is why it is so educational). If you don’t have the time, you may want to opt with Gentoo instead.

You pretty much got it, except for the fifth point.

A desktop environment (“DE”) is separate from the compositor (X11 or Wayland), but can’t exist without it.

At the end of the day, a DE is really just a “window manager” with a bunch of bundled applications, like taskbars/panels, a file manager, an app menu, etc. It’s as minimal or as feature rich as you want it to be.

The window manager dictates what to draw on the screen and where, but the compositor is what actually does the work. One is kind of useless without the other.

Hopefully that makes sense, I’m not a rocket surgeon.

Systemd has gone way and beyond what was supposed to be a replacement for init.rc.

Most important thing… not ALL Linux distros include systemd as the default init system. That’s the beauty of Linux (and POSIX in general), you can choose.

A biggie you miss is the toolchain: the compiler/binutils/linux-headers/libc/libstdc++ combination. The libc and usually libstdc++ are key components of any install. The other parts usually don’t make it to non-dev-desktops, but the distro couldn’t be made without them, so they’re virtually always available as packages.

Only exception is if the entire distro is cross-compiled or it’s made exclusively for containers, but those kinds of special distros break every rule imaginable anyway. Some might not even ship a bootloader or a Linux kernel by themselves.

It’s easier to think about Linux on the context of what an individual application needs to run. Pretty much everything you do will have these components.

• configuration
• an executable
• a communication mechanism (dbus, networking, web server, etc)
• something that decides if the application runs or not (systemd, monit, docker/docker compose, kubernetes scheduler, or you as the user)
• a way of accepting input (keyboard and mouse, web requests, database queries, etc)
• a way of delivering an output (logging to unique log files, through syslog, or to stdout/stderr, showing something on a screen, playing a sound, returning a message to the client, etc)
• storage (optional)
• some cpu and memory capacity

That’s really it. If something isn’t working, it’s pretty much exclusively going to fall into one of those categories. What that means is going to vary significantly from app to app but understanding this is how literally everything works makes the troubleshooting process a lot easier.

Systemd.

You need the “Userland” programs. Basic things like ls, cp, cat, etc. Usually it’s GNU core tools, but there’s also BusyBox or BSD equivalents.

Package management is optional according to Slackware and Linux From Scratch.

A key part you left out is the init scripts. Without those you don’t have the fundamental under the hood flavor of a distribution.

If I understand correctly, the filesystem driver is contained within the kernel for all linux-native filesystems (Ext4, XFS, BtrFS, F2FS, etc.), just as drivers for computer components and devices are. But drivers to access NTFS (Windows) and HFS+ (Mac OS) drives are programs in userspace

Honestly, I wouldn’t worry too much about how the OS works. If you’re very ambitious, you could try to install Arch in a virtual machine environment: https://wiki.archlinux.org/title/Installation_guide

Installing Arch for the first time taught me a lot about how my system works, since you have to choose all the parts that make up your system yourself.

Package manager needs to be higher since Linux distros are software distribution projects mainly.

1. Package manager
2. Config tools
3. Config defaults
4. Kernel
5. Init process
6. Software