From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Carl Thompson <cet@carlthompson.net>
Cc: cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: cpuspeed daemon
Date: 23 Jun 2003 11:48:05 -0700 [thread overview]
Message-ID: <1056394085.5719.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1056393765.4cc7b6562be56@carlthompson.net>
On Mon, 2003-06-23 at 11:42, Carl Thompson wrote:
> Great minds think alike. I almost picked "Speed Freq" as my new name before
> settling on "Speed Daemon" !
Heh. I think the speed puns are inevitable with this kind of thing.
>
> > What does your daemon do?
>
> Pretty much the same thing except mine actually does make policy decisions
> and does not yet have a sophisticated plugin infrastructure like yours.
You must be thinking of something other project. I don't have a plugin
infrastructure, and I'm hoping to never have one. I'm just trying to do
a simple policy enforcement mechanism, on the grounds that there's
plenty of other people doing policy setting daemon/user interfaces.
J
prev parent reply other threads:[~2003-06-23 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 23:29 cpuspeed daemon Jeremy Fitzhardinge
2003-06-21 23:42 ` Carl Thompson
2003-06-23 5:43 ` Jeremy Fitzhardinge
2003-06-23 18:42 ` Carl Thompson
2003-06-23 18:48 ` Jeremy Fitzhardinge [this message]
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=1056394085.5719.2.camel@localhost.localdomain \
--to=jeremy@goop.org \
--cc=cet@carlthompson.net \
--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