From owner-freebsd-current Sun Nov 10 14: 0:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9FAA37B401 for ; Sun, 10 Nov 2002 14:00:47 -0800 (PST) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77CBD43E77 for ; Sun, 10 Nov 2002 14:00:47 -0800 (PST) (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 gAAM0kw06436 for ; Sun, 10 Nov 2002 14:00:46 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; 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) Date: Sun, 10 Nov 2002 14:00:34 -0800 Subject: Re: [acpi-jp 1931] Re: acpid implementation? 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 , Hiten Pandya , current@freebsd.org To: Terry Lambert From: Michael Smith In-Reply-To: <3DCE168F.33FC0BFE@mindspring.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message