From: Paul Ionescu <i_p_a_u_l@yahoo.com>
To: cpufreq@www.linux.org.uk
Subject: Re: [RFC] cpufreqtools
Date: Mon, 25 Oct 2004 13:07:05 +0300 [thread overview]
Message-ID: <pan.2004.10.25.10.07.03.511563@yahoo.com> (raw)
In-Reply-To: 1098635425.4442.1.camel@localhost
Hi Jeremy,
I think too that dbus is the way to go.
If there is not any big issue with dbus, we should use it for uniformity.
Why invent a new protocol for this if not really necessary ?
Consistent UI/policy tools is a nice thing to have.
On Sun, 24 Oct 2004 18:30:25 +0200, Jeremy Fitzhardinge wrote:
> On Fri, 2004-10-22 at 19:21 +0200, Bruno Ducrot wrote:
>> I do like Jeremy's idea to wrap all sysfs stuff in one deamon, then all
>> clients (via his library) will communicate with this daemon in order to
>> set different policies. So all you care is to secure this daemon, not
>> random setuid programs that others may wrote.
>
> Yep, that was the intent. Though I've been thinking of changing it to use
> dbus rather than its own protocol. If we can define a dbus protocol
> everyone is happy with, then we can have other implementations, while
> having consistent UI/policy tools.
>
> J
next prev parent reply other threads:[~2004-10-25 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 17:22 [RFC] cpufreqtools Dominik Brodowski
2004-10-21 18:51 ` Dave Jones
2004-10-22 14:39 ` Bruno Ducrot
2004-10-22 14:57 ` Dominik Brodowski
2004-10-22 17:21 ` Bruno Ducrot
2004-10-22 17:47 ` Dominik Brodowski
2004-10-22 18:19 ` Bruno Ducrot
2004-10-24 16:30 ` Jeremy Fitzhardinge
2004-10-25 10:07 ` Paul Ionescu [this message]
2004-10-26 19:57 ` Dominik Brodowski
2004-10-25 9:01 ` Mattia Dongili
2004-10-25 11:11 ` Dominik Brodowski
2004-10-25 12:17 ` Mattia Dongili
2004-10-25 12:42 ` Dominik Brodowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2004.10.25.10.07.03.511563@yahoo.com \
--to=i_p_a_u_l@yahoo.com \
--cc=cpufreq@www.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox