Hacker News new | past | comments | ask | show | jobs | submit login

One of the things that boggles my mind is the "single responsibility principle violation" that they're calling.

What? Systemd will only handle the starting and stopping of services. How's that doing more than one thing?

This seems to me a technically better solution.




Doesn't it do logging? And cron? And login/console? And configure network interfaces? And a bunch of other stuff...

... systemv sucks enough that I'm in the middle of re-working our firmware at work to use systemd instead (I do like socket activation and supervisor stuff), but of all the systemd features one could like, "do one thing and do it well" isn't one of them.


only the journal is a required additional feature of systemd, and you can set it up to not store anything and just forward to your syslog/rsyslog/...

you don't need to use systemd-networkd, it's a separate program - but it's better than debians /etc/network/intefaces adn RH /etc/sysconfig/network-scripts/if* - so I do welcome the consolidation it'll bring to distros.

you can still run normal cron you don't need to run the kms console daemon either




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: