Message: previous - next
Month: June 2018

Re: [trinity-users] why consolekit & policykit & elogind?

From: "Dr. Nikolaus Klepp" <office@...>
Date: Sun, 10 Jun 2018 10:38:33 +0200
Am Sonntag, 10. Juni 2018 schrieb David C. Rankin:
> On 06/09/2018 03:51 PM, Dr. Nikolaus Klepp wrote:
> > That's an interesting article. So aparently consolekit/polkit/udisk and
> > desendents are still around to solve a the multiseat "problem" which died
> > when? 1995? Am I missing some bigger picture here?
> Well, depending on how your system is used -- it's actually quite a big deal.
> If you track the article closely, it isn't something that died, it more or
> less functionality that has been passed around between packages since that
> time. HAL, console kit, systemd, etc.. As far as it's importance, it was a
> blocker for KDE4+ until it was capable of being implemented without console kit.

I remember reading some chatter about that, but I did not get the point. What did not work? And what could not be solved much easier by providing a glue layer by some call to external programs instead of depending on volatile 3rd party libraries? Ok, maybe that did not look as unstable as it's now, but anyway. From my point of view the missing documentation for practicly anything from has reached the point where at least I want to get rid of that stuff, because I cannot rely on the system behaving in a sane predictable way any more.

> Apparently the next step-parent will be systemd-logind (most of which will
> remain only partially documented, if at all -- just like the fact that console
> blank and powerdown defaults were removed from the 4.16 kernel and supposedly
> given to systemd to implement -- but nobody got around to writing a service to
> replace the default (600) in /sys/module/kernel/parameters/consoleblank.
> Ain't moving targets fun?...

systemd-logind is on devuan in the form of elogind :-/. This does not sound good at all.


Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...