Hi Johannes,
"Johannes Christ" <[email protected]> writes: > ... so I add `dbus-system-service-type` first, run deploy. Then re-add > elogind, redeploy. It passes. sudo works, but su throws me out. And relogin > fails. > > After a reboot, it all seems to work. And my $XDG_RUNTIME_DIR is there :-) Yes. Installing elogind can even lock you out. It is not simple to switch from non-elogind to elogind on the fly, it changes how the logging in operates quite largely. So having to reboot is expected here for full operation. Although undocumented and not ideal since in such cases Guix System should give the user a possibility to activate the system only after reboot. > > Now this got me thinking: When I test deploying our system as a container > without `--network`, I get: > > guix system: error: service 'unattended-upgrade' requires 'networking', > which is not provided by any service > > Should Guix perhaps do something similar for elogind, e.g. depend on a > hypothetical `dbus-system` which would be provided by > `dbus-system-service-type`? No, elogind-service-type already pulls in dbus-root-service-type by extending it. But again, installing dbus on a running system is not easy. There is no need for manually adding dbus-root-service-type from your side, it would work either way after a reboot. > > FWIW, I've also tried greetd, but that service did not seem to do anything. Greetd runs on TTY and allows you to log in to the system, it's a greeter. It's typically used for starting an X or Wayland session. So I am not sure what you would use it for on a server. You're right that it won't do much without configuration, you need to specify what tty it should run on and what it should start specifically. > So I also tried `pam-mount`, but that seems unsuccessful, as it does not > modify the `sshd` config for PAM, and the `sshd` config does not include > anything else. Right, I suppose sshd should be added, do you care to submit a PR / a Codeberg issue? Rutherther
