[ohm] OHM vs. PPM

[Holger Macht]

On Mi 30. Apr - 18:11:14, Marcel Holtmann wrote:
> Hi Rob,
> 
> > > might be a quite provoking subject, however, I like to attract some
> > > responses... ;-)
> > > 
> > > For quite some while now, I'm looking into finding a replacement (and
> > > starting to become active in the development for it), for the powersave
> > > daemon we use on openSUSE based distributions. Actually it's about the
> > > question: "Who does the power management job when there's no desktop
> > > applet?"
> > > 
> > > Obviously, two frameworks caught my eye... open-hardware-manager (OHM [1])
> > > and the power-policy-manager (PPM [2]). So I have a couple of questions:
> > > 
> > >  1. Is OHM aught to be used on usual desktop/laptop systems? I mean, it
> > >     would be a valid target to define that OHM is "just" meant for
> > >     embedded devices and thus, development wouldn't consider
> > >     problems/drawbacks on the desktop side.
> > 
> > OHM needs some work before its usable on a desktop system, mainly in 
> > that it should become a session daemon rather than a system daemon - 
> > connecting up to X from the system is not ideal.
> 
> why? Leave it as system daemon and have an "agent" running in the X
> session that OHM can refer requests to. You might wanna check out on how
> BlueZ does it with PIN requests and mode change confirmations.

These two sentences are too short for getting a complete overview about
the BlueZ way of doing these things, but this sounds like what we already
had with the powersave daemon and kpowersave (the time kpowersave was only
a client for powersaved).

> D-Bus works beautiful for us in these cases. You can even easily monitor
> if an agent process dies etc.

Exactly.

Regards,
	Holger