@thechildofroth@mastodon.world
2025-05-02 10:47 UTC
Replies (3)
-
@jmaris@eupolicy.social 2025-05-02 10:55
@thechildofroth@mastodon.world @kde@floss.social I personally have never understood the hate for systemd. I think people are upset about feature creep, but honestly, I personally can't get excited or angry about a service manager.
-
@operand@todon.nl 2025-05-02 11:10
@thechildofroth@mastodon.world @jmaris@eupolicy.social @kde@floss.social systemd is a program responsible for managing a variety of system tasks on Linux systems, most notably managing the running and communication of background programs (such as the program which handles sound, the program which handles wifi, the program which controls printers, etc). But it also manages things like booting, networks, user sessions, DNS, etc. Systemd is relatively new and replaced a system where many different programs were responsible for all of the individual tasks, whereas Systemd is one monolithic whole. Some people preferred having many individual programs and thus dislike systemd. Some people also dislike that systemd is so ubiquitous it is almost mandatory (some programs won't work without it). But broadly these things are not really important to "normal" users.
-
@schrotthaufen@mastodon.social 2025-05-02 11:33
@thechildofroth@mastodon.world Sytemd takes care of managing system services like starting network interfaces (or software to manage them), or a daemon that mounts removable media so you don’t have to do these things on the terminal. It does *a lot* of other things, which is a huge point of contention. It all started when the udev device manager was merged into systemd. However, most critics just suck it up, because the init part is vastly superior to e.g. the old System V style init systems. @jmaris@eupolicy.social @kde@floss.social