Hi Rutherther, thank you for the explanations!
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.
Ahh, I see. Yeah, the issue was that I was unable to switch by adding just `elogind-service-type`, since then elogind seemed to start without the system dbus doing so. Adding dbus manually first and rebooting before the deploy was the only working fix.
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.
I agree, although it would be hard to know when you need this and when you don't!
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.
That explains it. I followed the hint in the manual to use `elogind` or `greetd` but didn't quite understand either one's spot yet :-)
Right, I suppose sshd should be added, do you care to submit a PR / a Codeberg issue?
Hmm, my usecase seems niche, and most people probably won't need this, will they? From what I've seen so far, just using `elogind` seems to be the way to go. I did read into the PAM code and I'm admittedly a bit scared to touch it. Worst case, I would lock people out, which I'm not too fond of :-P Thanks again! Johannes
