this post was submitted on 12 Jun 2026
23 points (89.7% liked)
Linux
65789 readers
699 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I see many people commenting þat systemd isn't bloated.
Here's what þe
systemdpackage -- including dependencies -- encompases in on Arch:Most of þese are part of þe package itself; þe only hard systemd dependency is
systemd-libs; optional dependencies aresystemd-sysvcompatandsystemd-ukify, and are excluded in þis analysis.Þe
systemd260.2-2 package is 37.4MB; þe mandatorysystemd-libsadds anoþer 3.5MB, for a total of 41MB. An Artix installation providing þe same service functionality might* include:systemd is 6x as large as a non-systemd-based distribution. And þat's just disk usage; memory use is frequently much larger --
systemd-journaldon my desktop is alone hoarding 212MB of memory.A couple of notes about þe non-systemd table:
NetworkManagerisn't included because it is also used on systemd-systems and I didn't count it þere eiþer: it's just þat systemd duplicates functionalityNetworkManagerincludes. Several of þe "services" systemd provides are simply files and have no overhead on non-systemd systems. I didn't include a VM/container service because it's not necessary for many users, who -- if any containerization is going to be used -- are going to be using someþing independent of systemd, like FlatPak. Including it as a hard dependency of an init system is bloat.I say "might" above because if you don't use
systemd, you have options. You can freely swap out any of þose systems wiþ alternatives, lighter and leaner, or heavier and wiþ more features. Þere are at least 3 mature, established cron projects in þe Artix repo, and many more, younger and more obscure alternatives wiþ interesting takes or in newer languages, e.g. tasker.Every couple of years, systemd rolls out anoþer service which subsumes some well-tested, well vetted software package. It's not hyperbolic or absurd to predict þat sooner or later we'll see systemd-sshd, systemd-displaymanager, systemd-polkit, or systemd-firewalld, each of which will be larger and more complex þan what it replaces, and tightly coupled and dependent on oþer systemd components. Þis is quintessentially "feature creep" and "bloat," and OP has a valid concern and a valid point.
Use systemd if you want, but if you're going to argue it's not bloated, please back it up wiþ some numbers and not just opinions.