public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martijn van de Streek <martijn-Qnkk5oMnPFw@public.gmane.org>
To: Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>
Cc: ACPI Development - Sourceforge
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: lid state?
Date: Mon, 7 Oct 2002 16:11:36 +0200	[thread overview]
Message-ID: <20021007141136.GA26168@o2w.nl> (raw)
In-Reply-To: <OE13CngokVNTmgEVg3U0000c5a1-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>

On Mon, 07 Oct 2002, Derek Broughton wrote:

> It's far from ideal, but it's robust enough, because the lid state bears no
> connection to acpid.  Whether or not acpid is running, events get generated.
> I suppose, conceivably, the lid could be closed when the system boots and
> ACPI starts - but how realistic is that?  I can't see it happening on my
> system.

It's very well possible to do that. And it breaks any on/off type script
you set up for the lid button.

I'd like separate open and close messages as well actually..

Martijn
-- 
You may be infinitely smaller than some things, but you're infinitely 
larger than others.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2002-10-07 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06  5:13 lid state? John Belmonte
2002-10-07 12:10 ` Derek Broughton
     [not found]   ` <OE13CngokVNTmgEVg3U0000c5a1-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2002-10-07 14:11     ` Martijn van de Streek [this message]
2002-10-07 14:22     ` Frank Mehnert
     [not found]       ` <E17yYmP-0004wp-00-Hkr6DilkjYZTIIw02KIYYwp9XTrnmqkB@public.gmane.org>
2002-10-07 18:15         ` James D Strandboge

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=20021007141136.GA26168@o2w.nl \
    --to=martijn-qnkk5omnpfw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org \
    /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