| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 24 Jan 2007 03:02:29 +0100 From: Alessandro Di Marco <dmr@....it> To: "Scott Preece" <sepreece@...il.com> Cc: "Pavel Machek" <pavel@....cz>, linux-kernel@...r.kernel.org, vojtech@...e.cz Subject: Re: [ANNOUNCE] System Inactivity Monitor v1.0 "Scott Preece" <sepreece@...il.com> writes: My own hot button is making sure that the definition of what constitutes user activity is managed in exactly one place, whether in the kernel or not. My naive model would be to put the response at user level, but to provide a single point of definition in the kernel (say, /dev/useractivity or the equivalent) that the user-level daemon could listen to. Unfortunately the term "user activity" seems a bit too vague for this. IMHO different users (but also applications) present different needs that you cannot fit with a single device node. Example. The user expects that the keyboard light is turned off after 10 minutes of keyboard inactivity, disregarding the mouse movements. This makes sense since the glare at the bottom disturb the Quake sessions. :-) However when the screen is blanked, the user expects that either keyboard or mouse events can unblank it... -- All of the significant battles are waged within the self. - Sheldon Kopp - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists