4 ms·
If systemd devs cared about proper modularity it would be much easier to collaborate. I believe the first step towards a rewrite is just making an init system+
by mixedCase 10y ago
If systemd devs cared about proper modularity it would be much easier to collaborate.
I believe the first step towards a rewrite is just making an init system+daemon supervisor that (at least partially) understands systemd unit files or a similarly simple solution.
systemd's huge grapple on Linux systems was 95% caused by just by people not wanting to maintain shell scripts (which is understandable).
- thegeomaster 10y agoThis. I see criticisms of systemd all around Hacker News, but I find it really easy to create a unit file on a production system and just go systemctl start <unit-file>. I sometimes even create shell scripts for some tasks and create one-off unit files so I can run them easily as the right user, and have proper logging for free. I'm not a system administrator and I just appreciate that the user-system interface is easy to work with, for the occasions when there's no dedicated sysop in the team.
- drinchev 10y agoI second this. As far back as I have been a Linux user ( back to Slackware 4 ) I was very pissed by the systemd ideas. Nowadays I think it's priceless when I can just create a unit file for my NodeJS and do journalctl -fu my_app. I think the criticism goes to the leader of systemd, who has exceptional arrogance ( as far as I have read ). Maybe if there is a competition between systemd and you name it, the init system will feel more natural.