I, for one, am a old school sysop that is very happy with systemd as a modern service manager. I bet there are literally dozens of us :). > A giant PID 1 that

I, for one, am a old school sysop that is very happy with systemd as a modern service manager. I bet there are literally dozens of us :). > A giant PID 1 that controls everything > monolithic systemd Technically speaking only small portion of systemd is running as pid 1. This has been explained many times: https://news.ycombinator.com/item?id=9515789 https://news.ycombinator.com/item?id=9515789 and I'm not going to explain this again. > re-implementing such basics as ntp Systemd-timesyncd is a minimal ntp client. This is not a replacement for ntp. You are free to use full blown ntpd if you want. Think of it as a dns resolver inside your libc vs running proper caching dns server. It's the same situation. > more and more things become part of monolithic systemd https://www.youtube.com/watch?v=bdmv2FQRHWg https://www.youtube.com/watch?v=bdmv2FQRHWg :)