Oomd, oh yea, good idea, but WHY it has to be in systemd? The same applies to about 3/4 of things in there. Because of this i've started to call it LennartOS. And also I don't feel like linux is about freedom anymore but more like some sort of weird power display games.
I use several of these projects because I like the systemd design philosophy (ex the way the CLI interface and config files are) and trust the developers of their software. However, there are popular altenatives available for all of these components, should you choose to use them:
systemd-resolved: bind9, dnsmasq, powerdns
systemd-networkd: NetworkManager, ConnMan
systemd-boot: GRUB2, Refind, EFISTUB
systemd-oomd: earlyoom, nohang, oomd (the facebook one, not systemd)
It's a service manager for your Linux OS which manage all services down to initial startup related services.
Just viewing it as a init system is misleading.
As a side note I think a service manager directly above the kernel is a must have for any modern server or desktop operating system ;=)
Systemd is the name of the init system. Systemd is also the name of the project developing multiple systemd-* services. Maybe they could help the situation a bit by renaming the service itself systemd-init, but we've had enough time for people to learn to deal with a tiny bit of ambiguity...
However, you should probably switch to FreeBSD because you think it’s great too, not because you hate systemd.
«It (systemd) provides a system and service manager» (from https://www.freedesktop.org/wiki/Software/systemd/).
So it manages services and manages the system, as a whole.
> Every time I see all the stuff packed into it I feel extreme urge to switch to freebsd again.
Meh, a lot of people bring this up, but they never switch.
Try understanding a bit more than just the name's prefix before getting so bent out of shape.
Lennax
https://papers.freebsd.org/2018/bsdcan/rice-the_tragedy_of_s...
Joke's on you.