There’s also a few cases of feature and scope creep, including the infamous systemd-resolved.
Systemd, your job is to launch services, manage logs, and do timers and relaunches on a service crash. DNS is out of scope, leave that to existing services.
You’ve misunderstood something.
systemd-resolved is one of the services that uses systemd’s service management system
You’re saying “don’t use this service management system to manage your services”
There’s also a few cases of feature and scope creep, including the infamous
systemd-resolved.Systemd, your job is to launch services, manage logs, and do timers and relaunches on a service crash. DNS is out of scope, leave that to existing services.
You’ve misunderstood something.
systemd-resolved is one of the services that uses systemd’s service management system
You’re saying “don’t use this service management system to manage your services”
I may have written that in a confusing way. I’m saying systemd’s job is service management. Systemd-resolved is an unnecessary bit of scope creep.
systemd-resolved is a service. It’s not scope-creep. It’s its own thing built in the systemd framework.
resolved is entirely optional and disabled by default, I use it on case of non-mobile devices but leave it on laptops etc.
DNS resolution isn’t something exotic, it makes sense for systemd to implement it in a simple optional daemon