From owner-acpi-jp@jp.FreeBSD.org Sun Nov 10 08:56:25 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gA9NuPS40194;
	Sun, 10 Nov 2002 08:56:25 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gA9NuPm40189
	for <acpi-jp@jp.freebsd.org>; Sun, 10 Nov 2002 08:56:25 +0900 (JST)
	(envelope-from msmith@freebsd.org)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id gA9NuNI29814
	for <acpi-jp@jp.freebsd.org>; Sat, 9 Nov 2002 15:56:23 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5e75ecc7f6118164e13c4@mailgate2.apple.com>;
 Sat, 9 Nov 2002 15:56:17 -0800
Received: from freebsd.org ([17.219.195.12])
	by scv2.apple.com (8.11.3/8.11.3) with ESMTP id gA9NuBi19940;
	Sat, 9 Nov 2002 15:56:11 -0800 (PST)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: Frode Nordahl <frode@nordahl.net>,
   Hiten Pandya <hiten@angelica.unixdaemons.com>, current@freebsd.org
To: acpi-jp@jp.FreeBSD.org
From: Michael Smith <msmith@freebsd.org>
In-Reply-To: <3DCCFB94.C964C09D@mindspring.com>
Message-Id: <D062BB22-F43E-11D6-83BB-0050E4660701@freebsd.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Sat, 9 Nov 2002 15:56:07 -0800
X-Sequence: acpi-jp 1936
Subject: [acpi-jp 1936] 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 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.

> o	replacing devices in a multipurpose bay, which may take one
> 	of a number of devices, including a battery

Does not require (and could not practically be assisted by)
a daemon.

> o	port replicators with devices in them

Does not require (and could not practically be assisted by)
a daemon.

> o	Docking adaptors

Does not require (and could not practically be assisted by)
a daemon.

> o	Forced hibernate and/or shutdown, pending an empty battery

Does not require a daemon.

> o	Software implementation of features (e.g. selective powerdown
> 	or operational level, based on idle time, user preferences,
> 	or other things not settable by "sysctl"

In other words, "misc stuff".  Still nothing concrete.

  = Mike

