4 ms·
> In Void, which is using Runit, enabling a service (like alsa, crond, cupsd, etc) is a matter of creating a symlink, which feels very transparent and reliable.
by majewsky 9y ago
> In Void, which is using Runit, enabling a service (like alsa, crond, cupsd, etc) is a matter of creating a symlink, which feels very transparent and reliable.
It's exactly the same in systemd, although people usually use systemctl. It will report what it does:
$ sudo systemctl enable sshd
Created symlink /etc/systemd/system/multi-user.target.wants/sshd.service → /usr/lib/systemd/system/sshd.service.
- a-nikolaev 9y agoThank you, I did not know that )
- daptaq 9y agoI belive his point is that you actually use "ln -s" to activate a service, instead of it being done by some utility, without you knowing what else it might have done too.
- majewsky 9y agoYou can just as well do the same in systemd. In fact, I'm shipping these symlinks in my configuration packages to enable services, e.g. https://github.com/majewsky/system-configuration/blob/f1326a086d55ed0730befbb683ca4c45bdc020cc/hologram-openssh.pkg.toml#L10-L13 https://github.com/majewsky/system-configuration/blob/f1326a...
- shevy 9y agoAre you really reasoning in favour of some obscure program rather than a simple "ln -s"? Dude, we have been using *nix since decades. There is nothing wrong with keeping things simple - no need for systemd whatsoever.