3 ms·
I started with sys-v init and other init systems about 30 or so years ago. systemd as an init system is far better than any other I used. I'm not very happy w
by dekhn 5y ago
I started with sys-v init and other init systems about 30 or so years ago. systemd as an init system is far better than any other I used. I'm not very happy with systemd-resolver and some of its other non-init components.
- baa-z 5y agoYeah systemd init is kinda good (although still bloated) But systemd isn't a init it's a hole mess of utilities that can't do their job well !(also have you tried runit?)
- dekhn 5y agoyes, I've used runit. Athough systemd's overall software engineering is not impressive, I believe the value of having a centralized admin system for all common base functionality of a modern linux workstation or server is high. Of the non-init components of systemd, my experience is: networkd is really powerful but there are serious gaps (that's your mess), resolvd (I spend a lot of time debugging their resolver; I like dnsmasq better). udevd: have never noticed anything about it working any differently from before. timesyncd (versus ntpd): has generally been painless and worked well. I haven't really looked into the container support.