Hacker News new | ask | show | jobs
by Bombinator 1054 days ago
Don't you think it does a bit too much as an init system?
6 comments

It’s not just an init system and you can opt into resolved, networkd, etc. but you knew that already!
Just being able to treat period tasks the same as I treat long-lived services, and never having to think about crontab vs cron.d vs cron.hourly vs /etc/crontab, has improved my quality of life dramatically.

I also use systemd-timesyncd / networkd / resolved on most of my systems, but in places where I've wanted to not, swapping them out is as easy as swapping any other services (looking at you, rsyslog and syslog-ng).

No, it does what I want well. It never surprised me.
What does it do as an init system that is too much?
Not really, no. Systemd-init seems fairly focused. systemd the project also makes other stuff, which all neatly fits together.
No. It’s great, replacing and unifying a whole collection of random tooling you otherwise had to cobble together yourself.