this post was submitted on 16 Dec 2024
78 points (89.8% liked)
Linux
48681 readers
368 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
All of those are entirely separate components; I have no idea what you're attempting to imply here.
Those are all things systemd manages.... as well as logs, udev, etc etc.
What kind of gui too could you even imagine would sanely present all of that?
As mentioned, those are entirely separate and even independent components.
Systemd (as in: pid1) only "manages" them insofar as that it controls their running processes just like any other service on your system.
systemd-boot doesn't interact with systemd at all; it's not even a Linux program.
The reason these components have "systemd" in their name is that these components are maintained by the same people as part of the greater systemd project. They have no further relation to systemd pid1 (the service manager).
Whoever told you otherwise milead you and likely had an agenda or was transitively mislead by someone who does. Please don't spread disinformation further.
Without going into the weeds and all, given they all are in the same project, regardless...
You said "a gui for managing systemd", so which part? Boot, udev, and journal? All three are required and not optional for systemd the OS infrastructure layer suite (or whatever it's called these days), so minimally, assume that?
If so, what kind of sane gui could manage those three very disparate things?
If you talk about "a GUI for systemd", you obviously mean its most central and defining component which is the service manager. I'm going to assume you're arguing in bad faith from here on out because I consider that to be glaringly obvious.
systemd-boot still has no connection to systemd the service manager. It doesn't even run at the same time. Anything concerning it is part of the static system configuration, not runtime state.
udevd doesn't interact with it in any significant user-relevant way either and it too is mostly static system configuration state.
journald would be an obvious thing that you would want integrated into a systemd GUI but even that could theoretically be optional. Though it'd still be useful without, it would diminish the usefulness of the systemd GUI significantly IMHO.
It's also not disparate at all as it provides information on the same set of services that systemd manages and i.e. systemctl has journald integration too. You use the exact same identifiers.