From: Matthew Tippett <matthew-+XluyfkzffvQT0dZR+AlfA@public.gmane.org>
To: Knut Neumann
<knut.neumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX@public.gmane.org>
Cc: Matthew Tippett <matthew-+XluyfkzffvQT0dZR+AlfA@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ospmd or acpid
Date: Thu, 12 Dec 2002 10:48:13 -0500 [thread overview]
Message-ID: <3DF8AFBD.1040200@casero.com> (raw)
In-Reply-To: <004c01c2a2bc$d19bdf80$8cfa6386-naq7wT523jg@public.gmane.org>
Thanks, you answered the question.
So I will be sticking with acpid until all the ACPI support for my
system is under control ;).
Matt
Knut Neumann wrote:
>>Just a quick question regarding the user space daemons for ACPI. There
>>is ospmd which is part of the acpi project, and there is acpid which is
>>a seperate project which Andrew is a member of both.
>
>
> Hmm...so what is your question? I assume you meant to ask which daemon to
> use, so if thats right read on:
>
> While acpid already reached version 1.0 and is quite ready to use, ospmd is
> supposed to be better of the two but it is still under development - though
> actually no one is really working on it. When its done it should replace not
> only acpid but also apmd and it is thought to handle UPSes and other power
> related devices as well.
>
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
prev parent reply other threads:[~2002-12-12 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 15:05 ospmd or acpid Matthew Tippett
2002-12-13 15:32 ` Knut Neumann
[not found] ` <004c01c2a2bc$d19bdf80$8cfa6386-naq7wT523jg@public.gmane.org>
2002-12-12 15:48 ` Matthew Tippett [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=3DF8AFBD.1040200@casero.com \
--to=matthew-+xluyfkzffvqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=knut.neumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX@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