From owner-acpi-jp@jp.FreeBSD.org Mon Nov 11 07:00:54 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gAAM0sx32545;
	Mon, 11 Nov 2002 07:00:54 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gAAM0pm32540
	for <acpi-jp@jp.freebsd.org>; Mon, 11 Nov 2002 07:00:51 +0900 (JST)
	(envelope-from msmith@freebsd.org)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id gAAM0nw06444
	for <acpi-jp@jp.freebsd.org>; Sun, 10 Nov 2002 14:00:49 -0800 (PST)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5e7aa93b58118164e13c4@mailgate2.apple.com>;
 Sun, 10 Nov 2002 14:00:36 -0800
Received: from freebsd.org (vpn-scv-x3-39.apple.com [17.219.194.39])
	by scv3.apple.com (8.11.3/8.11.3) with ESMTP id gAAM0Zq22308;
	Sun, 10 Nov 2002 14:00:36 -0800 (PST)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: acpi-jp@jp.FreeBSD.org, Frode Nordahl <frode@nordahl.net>,
   Hiten Pandya <hiten@angelica.unixdaemons.com>, current@freebsd.org
To: Terry Lambert <tlambert2@mindspring.com>
From: Michael Smith <msmith@freebsd.org>
In-Reply-To: <3DCE168F.33FC0BFE@mindspring.com>
Message-Id: <D6B06ABC-F4F7-11D6-8D49-0050E4660701@freebsd.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Sun, 10 Nov 2002 14:00:34 -0800
X-Sequence: acpi-jp 1938
Subject: [acpi-jp 1938] Re: acpid implementation?
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: msmith@freebsd.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021107


On Sunday, November 10, 2002, at 12:19 AM, Terry Lambert wrote:

> Michael Smith wrote:
>> On Saturday, November 9, 2002, at 04:12 AM, Terry Lambert wrote:
>>> Repeat: #1 is power profiles
>>
>> I don't see why this requires an 'acpid'.  You want a control tool,
>> sure, but power policy is not something that needs a daemon.
>
> The tool has to change the settings based on events, like
> unplugging external power from a laptop, resulting in the
> display backlighting being dimmed or turned off.

Ok, so the basic problem here is that you think that these
are discrete events that can be managed or tied together in
userspace.

The bad news is that they aren't.  Policy management is trivial,
and you can (and should) do it inside the kernel.  The real work
lies in implementing the base features and structuring it all in
a fashion that will actually work with the hardware that's shipping.

None of this requires a daemon.

  = Mike

