From: "Sérgio Monteiro Basto" <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
To: Stephen Torri <storri-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
Cc: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Daemon that handles ACPI
Date: 27 Mar 2003 01:46:06 +0000 [thread overview]
Message-ID: <1048729567.1490.17.camel@darkstar.portugal> (raw)
In-Reply-To: <1048723591.3593.2.camel-NN61vRp3iFIP0m8IYG7BWw@public.gmane.org>
Hi
you have a very basic example made by me in
http://codecs.home.sapo.pt/acpi/ in topic ACPI Deamon.
and talking about ospmd, yes, it never worked, we have a missing config
file that make GUI doens't work, and in this case I never knew about a
basic example...
Normally is the thing that is missed on every man and help pages of
Linux :)
On Thu, 2003-03-27 at 00:06, Stephen Torri wrote:
> On Wed, 2003-03-26 at 07:57, Derek Broughton wrote:
>
> > ospmd aside - it really should be an improvement over acpid when done - acpid
> > hasn't changed in months because there hasn't been any change to ACPI that would
> > require a change to acpid. It simply listens for ACPI events and runs user
> > defined scripts when they occur. If ACPI changes to trigger new events, acpid
> > doesn't need to change, but the user would need to define new rules.
>
> The very fact of how to create rules and having no examples made me stop
> trying to use acpid. If you have an example on a webpage that would be
> great.
>
> Stephen
> --
> Stephen Torri <storri-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
--
SérgioMB
email: sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org
Who gives me one shell, give me everything.
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
next prev parent reply other threads:[~2003-03-27 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 2:07 Daemon that handles ACPI Stephen Torri
[not found] ` <1048644460.2910.39.camel-NN61vRp3iFIP0m8IYG7BWw@public.gmane.org>
2003-03-26 2:33 ` Randy.Dunlap
2003-03-26 13:57 ` Derek Broughton
[not found] ` <005901c2f39f$ac481530$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2003-03-27 0:06 ` Stephen Torri
[not found] ` <1048723591.3593.2.camel-NN61vRp3iFIP0m8IYG7BWw@public.gmane.org>
2003-03-27 1:46 ` Sérgio Monteiro Basto [this message]
[not found] ` <1048729567.1490.17.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-03-27 15:08 ` Ducrot Bruno
2003-03-27 13:25 ` Derek Broughton
-- strict thread matches above, loose matches on Subject: below --
2003-03-27 2:24 Grover, Andrew
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=1048729567.1490.17.camel@darkstar.portugal \
--to=sergiomb-hho3weeoaswvhhzd4jos4w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=storri-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org \
/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