From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [RFC] cpufreqtools Date: Sun, 24 Oct 2004 18:30:25 +0200 Sender: cpufreq-bounces@www.linux.org.uk Message-ID: <1098635425.4442.1.camel@localhost> References: <20041021172227.GA24663@dominikbrodowski.de> <20041022143927.GE22405@poupinou.org> <20041022145738.GA2136@dominikbrodowski.de> <20041022172109.GF22405@poupinou.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20041022172109.GF22405@poupinou.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk Content-Type: text/plain; charset="us-ascii" To: Bruno Ducrot Cc: cpufreq list 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