From: Pavel Machek <pavel@suse.cz>
To: John Fremlin <chief@bandits.org>, Patrick Mochel <mochel@transmeta.com>
Cc: "Acpi-PM (E-mail)"
<linux-power@phobos.fachschaften.tu-muenchen.de>,
linux-kernel@vger.kernel.org
Subject: Re: Next gen PM interface
Date: Fri, 20 Apr 2001 19:08:44 +0200 [thread overview]
Message-ID: <20010420190844.C905@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10104182122250.7690-100000@nobelium.transmeta.com> <m2zodcoghs.fsf@bandits.org>
In-Reply-To: <m2zodcoghs.fsf@bandits.org>; from John Fremlin on Thu, Apr 19, 2001 at 08:07:43PM +0100
Hi!
> > This can also handle the user-dictated policy, which I haven't seen
> > discussed yet. For instance, when you close the lid or press the power
> > button, the system can enter suspend or it can power off. If the kernel
> > simply exported the event, the userspace daemon could simply check its
> > config file for the proper thing to do and initiate the transition.
>
> Exactly what I was suggesting. In this case, you'd get the event
>
> SLEEP ACPI Laptop case closed
>
> and your perl script could do something vaguely like
>
> /ACPI Laptop case closed$/ && system "shutdown -p now";
>
> to turn the machine off instead of sleeping.
Lid is polled device, at least in ACPI case. Take a look at current
/proc/power/ -- it contains file "ac" saying "on-line" or
"off-line". I believe we should add another device file "lid"
containing either "open" or "closed"
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
prev parent reply other threads:[~2001-04-20 17:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 0:07 Let init know user wants to shutdown Grover, Andrew
2001-04-18 0:51 ` Alan Cox
2001-04-18 1:56 ` John Fremlin
2001-04-18 11:55 ` Alan Cox
2001-04-18 19:10 ` John Fremlin
2001-04-18 20:10 ` Alan Cox
2001-04-18 20:21 ` John Fremlin
2001-04-18 21:05 ` Avery Pennarun
2001-04-18 21:34 ` John Fremlin
2001-04-20 17:02 ` Pavel Machek
2001-05-02 16:52 ` John Fremlin
2001-04-20 17:01 ` Pavel Machek
2001-04-20 23:41 ` John Fremlin
2001-04-21 7:54 ` Pavel Machek
2001-04-24 0:17 ` Jamie Lokier
2001-04-24 1:08 ` John Fremlin
2001-04-24 10:06 ` Pavel Machek
2001-04-25 14:28 ` Jamie Lokier
2001-04-25 16:11 ` Richard Gooch
2001-04-18 1:54 ` John Fremlin
2001-04-19 3:54 ` Next gen PM interface John Fremlin
2001-04-19 4:07 ` Alan Cox
2001-04-19 5:08 ` Patrick Mochel
2001-04-19 18:57 ` John Fremlin
2001-04-19 19:09 ` Patrick Mochel
2001-04-19 19:30 ` John Fremlin
2001-04-19 19:07 ` John Fremlin
2001-04-20 17:08 ` Pavel Machek [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=20010420190844.C905@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=chief@bandits.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-power@phobos.fachschaften.tu-muenchen.de \
--cc=mochel@transmeta.com \
/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