Re: Should libpam-elogind Provide libpam-systemd ?
Adam Borowski <email@example.com> writes:
> Conflicts would greatly simplify packaging, but I'm afraid we need
> coinstallability at least for upgrades. With d-i installing systemd,
> the user needs to be able to switch to sysvinit -- and, horrors, some
> might want to go the other way.
> It'd be damage to allow two loginds running at the same time, thus what
> * the "systemd" package starts its logind only if systemd is pid 1
> * elogind starts its logind only if pid 1 is not systemd
I may be missing some complexity here, but it feels as if there should be
a PAM module that determines which logind is running and then dispatches
the PAM calls to the appropriate module for the running logind.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>