4 ms·
I'd love to see Guix with SystemD, but there's no work going in that direction that I am aware of. While I appreciate the work on [GNU Shepherd](https://www.gnu
by phaer 5y ago
I'd love to see Guix with SystemD, but there's no work going in that direction that I am aware of. While I appreciate the work on [GNU Shepherd](https://www.gnu.org/software/shepherd/manual/shepherd.html https://www.gnu.org/software/shepherd/manual/shepherd.html), especially their documentation quality and the use of scheme instead of the rather obscure nix language, learning yet another init system on top of a new distro while systemd seemingly has won most of the market makes NixOS more attractive. At least to me
- mbakke 5y agoEven if Guix were to switch to systemd (it won't), end users would primarily be interacting with services through the same high-level APIs as now. https://guix.gnu.org/manual/devel/en/guix.html#Services https://guix.gnu.org/manual/devel/en/guix.html#Services That is, the only difference in practice would be replacing 'herd' with 'systemctl' when stopping and starting services manually. Anything else, such as modifying a service, has to go through the configuration system. Similarly, for service authors, whether the API you design ends up creating a systemd unit file or shepherd service object is an implementation detail and would be mostly transparent.