From: Lennart Poettering <mzxreary@0pointer.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Werner Fink <werner@suse.de>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: tty: add 'active' sysfs attribute to tty0 and console device
Date: Tue, 16 Nov 2010 22:42:50 +0100 [thread overview]
Message-ID: <20101116214250.GB17824@tango.0pointer.de> (raw)
In-Reply-To: <20101116204906.29d840e9@lxorguk.ukuu.org.uk>
On Tue, 16.11.10 20:49, Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> /dev/tty* and sysfs nodes don't track permissions, owner with each other,
> so you are providing interfaces that either expose information they
> shouldn't (which screen is valuable info in some environments), or don't
> expose info they should.
Well, I find the informatoin who is logged in much more valuable then
the information whether I am active or not. And the who is logged in
informatin I can find out with a simple stat() on the tty caller.
> sysfs also lacks vhangup so you can't fix it right now either.
Which is a feature, no a bug. It would be kinda messy if the service
which manages device access based on whose session is active would
always be forcibly stopped from doing so if somebody calls vhangup().
Lennart
--
Lennart Poettering - Red Hat, Inc.
next prev parent reply other threads:[~2010-11-16 21:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 15:46 tty: add 'active' sysfs attribute to tty0 and console device Kay Sievers
2010-11-16 15:57 ` Alan Cox
2010-11-16 16:13 ` Kay Sievers
2010-11-16 17:14 ` Alan Cox
2010-11-16 18:51 ` Kay Sievers
2010-11-16 19:55 ` Alan Cox
2010-11-16 20:15 ` Kay Sievers
2010-11-16 20:49 ` Alan Cox
2010-11-16 21:29 ` Kay Sievers
2010-11-16 21:42 ` Lennart Poettering [this message]
2010-11-16 22:51 ` Alan Cox
2010-11-16 22:58 ` Lennart Poettering
2010-11-16 23:04 ` Alan Cox
2010-11-16 23:18 ` Lennart Poettering
2010-11-16 23:49 ` Etched Pixels
2010-11-16 21:36 ` Lennart Poettering
2010-11-16 22:56 ` Alan Cox
2010-11-16 23:10 ` Lennart Poettering
2010-11-16 23:45 ` Alan Cox
2010-11-17 16:31 ` John Stoffel
2010-11-17 22:01 ` Valdis.Kletnieks
2010-11-17 23:40 ` Kay Sievers
2010-11-17 23:56 ` Alan Cox
2010-11-18 1:27 ` Greg KH
2010-11-18 1:48 ` Lennart Poettering
2010-11-18 1:53 ` Greg KH
2010-11-18 2:29 ` Lennart Poettering
2010-11-18 11:00 ` Dr. Werner Fink
2010-11-18 11:23 ` Alan Cox
2010-11-18 12:12 ` Dr. Werner Fink
2010-11-18 12:58 ` Alan Cox
2010-11-18 13:14 ` Dr. Werner Fink
2010-11-18 14:41 ` Alan Cox
2010-11-19 13:21 ` Dr. Werner Fink
2010-11-19 15:47 ` Alan Cox
2010-11-19 17:07 ` Dr. Werner Fink
2010-11-19 18:02 ` Greg KH
2010-11-19 18:41 ` Dr. Werner Fink
2010-11-20 12:40 ` Alan Cox
2010-12-01 11:15 ` Dr. Werner Fink
2010-11-18 12:04 ` Kay Sievers
2010-11-18 10:15 ` Alan Cox
2010-11-18 11:55 ` Kay Sievers
2010-11-18 13:01 ` Alan Cox
[not found] <20101201112004.12d78cd7@lxorguk.ukuu.org.uk>
2010-12-01 12:32 ` Dr. Werner Fink
[not found] ` <tiocgdev1@mdm.bga.com>
2010-12-03 11:48 ` Dr. Werner Fink
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=20101116214250.GB17824@tango.0pointer.de \
--to=mzxreary@0pointer.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jslaby@suse.cz \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@suse.de \
/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