From: Alessandro Di Marco <dmr@gmx.it>
To: "Scott Preece" <sepreece@gmail.com>
Cc: 7eggert@gmx.de, "Pavel Machek" <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: [ANNOUNCE] System Inactivity Monitor v1.0
Date: Thu, 25 Jan 2007 16:43:10 +0100 [thread overview]
Message-ID: <878xfrglip.fsf@gmx.it> (raw)
In-Reply-To: <7b69d1470701250718l58dfbc35rd0b24e5935e32331@mail.gmail.com> (Scott Preece's message of "Thu\, 25 Jan 2007 09\:18\:43 -0600")
"Scott Preece" <sepreece@gmail.com> writes:
On 1/25/07, Bodo Eggert <7eggert@gmx.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
next prev parent reply other threads:[~2007-01-25 15:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7ELhf-4rC-9@gated-at.bofh.it>
[not found] ` <7FKM6-7Gy-1@gated-at.bofh.it>
[not found] ` <7G6ME-1g2-11@gated-at.bofh.it>
[not found] ` <7GqrZ-6YY-1@gated-at.bofh.it>
[not found] ` <7GuFj-5pj-5@gated-at.bofh.it>
[not found] ` <7GwQL-h3-7@gated-at.bofh.it>
[not found] ` <7GzF3-4L6-47@gated-at.bofh.it>
2007-01-25 12:28 ` [ANNOUNCE] System Inactivity Monitor v1.0 Bodo Eggert
2007-01-25 15:18 ` Scott Preece
2007-01-25 15:43 ` Alessandro Di Marco [this message]
2007-01-25 16:03 ` Scott Preece
2007-01-18 19:29 Alessandro Di Marco
2007-01-19 7:38 ` Arjan van de Ven
2007-01-19 14:49 ` Alessandro Di Marco
2007-01-19 17:45 ` Scott Preece
2007-01-19 22:21 ` Jan Engelhardt
2007-01-19 22:30 ` Scott Preece
2007-01-19 10:11 ` Pavel Machek
2007-01-21 21:04 ` Jan Engelhardt
2007-01-23 9:38 ` Pavel Machek
2007-01-22 12:46 ` Alessandro Di Marco
2007-01-23 9:41 ` Pavel Machek
2007-01-23 14:14 ` Alessandro Di Marco
2007-01-23 16:34 ` Pavel Machek
2007-01-23 17:11 ` Alessandro Di Marco
2007-01-23 18:44 ` Pavel Machek
2007-01-24 2:51 ` Alessandro Di Marco
2007-01-26 17:15 ` Pavel Machek
2007-01-26 17:55 ` Alessandro Di Marco
2007-01-27 17:45 ` Pavel Machek
2007-01-27 19:20 ` Vojtech Pavlik
2007-01-29 13:58 ` Alessandro Di Marco
2007-01-29 22:28 ` Pavel Machek
2007-01-29 22:42 ` Alessandro Di Marco
2007-01-30 0:03 ` Pavel Machek
2007-01-30 9:42 ` Vojtech Pavlik
2007-01-30 12:33 ` Alessandro Di Marco
2007-01-30 13:09 ` Vojtech Pavlik
2007-01-30 15:22 ` Alessandro Di Marco
2007-01-29 8:24 ` Stefan Seyfried
2007-01-24 18:08 ` Alessandro Di Marco
2007-01-23 19:01 ` Mattia Dongili
2007-01-23 19:02 ` Pavel Machek
2007-01-23 20:07 ` Mattia Dongili
2007-01-23 19:34 ` Scott Preece
2007-01-24 2:02 ` Alessandro Di Marco
2007-01-24 14:01 ` Pavel Machek
2007-01-19 21:18 ` Bill Davidsen
2007-01-20 15:37 ` Alessandro Di Marco
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=878xfrglip.fsf@gmx.it \
--to=dmr@gmx.it \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sepreece@gmail.com \
--cc=vojtech@suse.cz \
/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