From mboxrd@z Thu Jan 1 00:00:00 1970 From: Diego Zuccato Subject: Re: Runlevel for Sleep? Date: Mon, 09 Sep 2002 23:52:22 +0000 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <3D7D3436.8C579CCD@otello.alma.unibo.it> References: <200209081126.g88BQjn05186@pfn1.pefnos> <3D7C5FDF.4FB4E759@otello.alma.unibo.it> <200209090855.g898rbA19798@pfn1.pefnos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org "P. Christeas" wrote: > The whole point of the initscripts is that this is your call. The kernel [...] > I just try to imagine situations thay may need design consideration. Uhm... Then just call your scripts from acpid. Or manage yourself ACPI events. It's all in userspace. If a service needs special handling, simply do it before (suspend) or after (resume) echoing to /proc/acpi/sleep. IMO there's no need to provide extra hooks. The timer setting, IIRC, is one of the "services" that need that kind of special handlin (at resume, you have to set current time from hw clock). Think echoing to /proc/scpi/sleep as a REALLY slow ATOMIC operation :-) BYtE, Diego. ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390