linux-kernel - Re: [ANNOUNCE] System Inactivity Monitor v1.0

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <878xfrglip.fsf@gmx.it>
Date:	Thu, 25 Jan 2007 16:43:10 +0100
From:	Alessandro Di Marco <dmr@....it>
To:	"Scott Preece" <sepreece@...il.com>
Cc:	7eggert@....de, "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:

   On 1/25/07, Bodo Eggert <7eggert@....de> wrote:
   > Imagine one computer serving two users. Two monitors, two keyboards ...
   ---

   Good point! Of late I've been working on single-user systems, so it
   was not at the front of my brain, despite years of building and using
   multi-user systems.

   It's a point that multi-user systems have struggled with forever (when
   somebody inserts a CR in the drive mounted in the system box, which user do
   you pop up a media player for?).

sed s/user X's screensaver/suspend to disk/g <<EOF

   I tend to think it's not a kernel-vs-user-space issue, though. To
   solve it you need, somewhere, a notion of a "user session" and you
   need some way to separate system-level issues (like low-battery) from
   user-level issues (like activiating user X's screensaver).

EOF

Are you sure?

best,

-- 
Experience teaches slowly and at the cost of mistakes. - James A. Froude
-
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/