Re: the future of GNOME Applets

[Bastien Nocera <hadess hadess net>]

On Tue, 2004-09-21 at 17:47 -0700, Stephane Demurget wrote:
> On Tue, 2004-09-21 at 16:52 +0200, Carlos Garcia Campos wrote: 
> > > You want more than monitor - a lot of the systems can set policies so
> > > you want policy selector. These tend to include "performance", "maximum
> > > battery life" and the like. Sometimes you need to switch at runtime (eg
> > > when playing bzflag) to avoid the CPU speed change messing with your
> > > game.
> > 
> > For to set a policy is necessary to be root and in a common case an
> > applet is not running as root. I think it can be solved by using an
> > external program as a policy selector. It will prompt for root password,
> > like the clock applet does calling to gst to set the time. The problem
> > is that it could be an annoying process for a so simple task.
> that's what is completely solved by emifreq applet:
> http://zzrough.free.fr/emifreq.php
> If the little daemon is started, you get the ability to have a really
> simple popup menu to
> change of governor and or frequency, like other desktop does, but the
> "it works" way.
> 
> I can understand we don't want a daemon at this stage though. The only
> security flaw involved is being more vulnerable by DOS attack I
> suppose.

That's exactly for this sort of thing that D-Bus was created, ie. you
can limit the number of messages, who can do what, etc. at the D-BUS
level.

---
Bastien Nocera <hadess hadess net>