54 ms·

It is like a modern car engine which is just a sealed black box under the hood, full of electronics. One of those fully open source sealed black boxes? I

It is like a modern car engine which is just a sealed black box under the hood, full of electronics. One of those fully open source sealed black boxes? I mean, for my simple uses, what is wrong with `sudo service nginx restart`, or `sudo killall nginx`? How is 'systemctl restart nginx' any harder? service is specified as 'Run System V Init Script' specifically in the man page, and there was a transition period where some scripts still were in /etc/init.d before all of them had been converted to systemd units, so at times both service and systemctl would have been present and doing slightly different things. So it makes a lot of sense that they didn't give systemctl the same name (see https://linux.die.net/man/8/service https://linux.die.net/man/8/service). Why do you think killall wouldn't work? It's present by default on my Fedora machine here...

captainmuon 9y ago
> One of those fully open source sealed black boxes? That's a fallacy. Webkit is open source, doesn't mean it is not completely opaque to the majority of developers. I'm not concerned about the legal free/open source status here, but about how well a casual user can grasp and change things (that is someone who has to start, stop, maybe install services, and isn't a systemd developer). I'm not bothered that the name of the tool is now `systemctl` of course. My problem is that is does way to many things. Want to list services? It shows you hundreds of pseudo-service-objects. They can get activated at any time by mysterious means. If you need this, it's great that it is available, but for me, the old ways (as many failings that they had) were good enough.
- vidarh 9y ago
  All of those dependencies were there before too. You just didn't have nearly as good visibility into them.