public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Brix Andersen <brix-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Untangling the sleep hotkey mess
Date: Sat, 7 Jan 2006 22:01:03 +0100	[thread overview]
Message-ID: <20060107210103.GA5961@osgiliath.brixandersen.dk> (raw)
In-Reply-To: <20060107205232.GA6445-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

On Sat, Jan 07, 2006 at 08:52:32PM +0000, Matthew Garrett wrote:
> On Sat, Jan 07, 2006 at 08:24:44PM +0100, Henrik Brix Andersen wrote:
> > Having ACPI hotkey events delivered as normal keyboard input makes it
> > difficult to run system scripts as root:root.
> 
> But that does nothing to help systems which only expose sleep keys via 
> the keyboard controller. It's not practical to get them to generate ACPI 
> events - however, it /is/ practical to get ACPI events to generate input 
> events. At that point there's nothing to stop a hotkey daemon running as 
> root.

So what you really propose is to abstract the handling of ACPI events
by yet another layer, a hotkey daemon?

./Brix
-- 
Henrik Brix Andersen <brix-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Gentoo Metadistribution | Mobile computing herd

[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]

  parent reply	other threads:[~2006-01-07 21:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 17:24 Untangling the sleep hotkey mess Matthew Garrett
     [not found] ` <20060107172446.GA3092-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-07 19:24   ` Henrik Brix Andersen
     [not found]     ` <20060107192444.GA21915-GgQh6P/XBPa901fzNV2Eubv56P54cF3WWmv/VHan8Is@public.gmane.org>
2006-01-07 20:52       ` Matthew Garrett
     [not found]         ` <20060107205232.GA6445-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-07 21:01           ` Henrik Brix Andersen [this message]
     [not found]             ` <20060107210103.GA5961-GgQh6P/XBPa901fzNV2Eubv56P54cF3WWmv/VHan8Is@public.gmane.org>
2006-01-07 21:14               ` Matthew Garrett
2006-01-08 12:58 ` [gpm] " Richard Hughes
2006-01-08 13:47   ` Matthew Garrett
     [not found]     ` <20060108134744.GA21538-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-08 14:13       ` Richard Hughes
2006-01-09  1:10         ` Yu Luming
2006-01-09  1:21           ` Richard Hughes
2006-01-09  1:14         ` Richard Hughes
2006-01-09  5:07           ` Dmitry Torokhov
     [not found]             ` <200601090007.43578.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2006-01-09  5:24               ` Matthew Garrett
2006-01-09  9:43               ` Richard Hughes
     [not found]             ` <20060109052407.GA4213@srcf.ucam.org>
     [not found]               ` <20060109052407.GA4213-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2006-01-09  6:09                 ` Dmitry Torokhov
     [not found]                   ` <200601090109.05791.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2006-01-09  9:44                     ` Richard Hughes

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=20060107210103.GA5961@osgiliath.brixandersen.dk \
    --to=brix-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@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