139
Is Systemd that bad afterall?
(sopuli.xyz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Jun 2023
139 points (100.0% liked)
Linux
48033 readers
663 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 5 years ago
MODERATORS
As service manager systemd nice, but look all services:
That's look as overkill. I use only systemd, journald, systemd-boot, systemd-networkd, systemd-resolved and systemd-timesyncd, but that a lot systemd. Feel like system make monolith.
systemd-nspawn for example. Systems manager for containers. Seriously. Why than exists? I don't understand. Really, someone use that daemon?
I think that's a bad argument. If you go out of your way to install and configure all of these, then yes, they exist and you can do that - but that doesn't automatically mean they're bad.
But in most operating systems they're not installed, not configured, and you'll never have to deal with any of that.
I actually use systemd-boot because it's very easy to install and configure and systemd-resolved, but for a lot of those I haven't even heard about.
And furthermore even if more of them (I think it's highly unlikely that any OS would use all of those services by default) were preinstalled, they'd only be an issue if they'd cause trouble. If your system is running systemd-whatever and it works well then what's the issue? The name itself?
As I wrote below, the problem is that this does not comply with the principle of K.I.S.S. One application should solve one task and can be replaced. Even now it is quite difficult to remove systemd-logind, for example. Because, although these are different services, they have long merged into a huge tangle.
you can use EFISTUB If you don't have dual boot. This literally load kernel from UEFI. I don't know more simple way. https://wiki.archlinux.org/title/EFISTUB
That's not KISS, but the UNIX principle. And even that part is wrong, as in traditional UNIXes applications were certainly not replaceable.
can't you replace UNIX applications in user space? Why, besides the fact that some simply have nothing to replace?