trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: June 2018

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

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 10 Jun 2018 02:42:27 -0500
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.

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?...

-- 
David C. Rankin, J.D.,P.E.