mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: simone.weiss@fau.de
To: "David Herrmann" <dh.herrmann@gmail.com>
Cc: simone.weiss@fau.de, "Greg KH" <gregkh@linuxfoundation.org>,
	helene.gsaenger@studium.fau.de, "Jiri Slaby" <jslaby@suse.cz>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Peter Hurley" <peter@hurleysoftware.com>,
	"Takashi Iwai" <tiwai@suse.de>,
	mark.d.rustad@intel.com, "Joe Perches" <joe@perches.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	linux-kernel@i4.cs.fau.de
Subject: Re: questions to planned lock-functionality for vts
Date: Mon, 23 Mar 2015 14:02:48 +0100	[thread overview]
Message-ID: <efd8dbe1963af0bb849841f4fd5e718b.squirrel@faumail.uni-erlangen.de> (raw)
In-Reply-To: <CANq1E4RYXHQzcxrEZnLBYFN3NvUNHNa+19G96H=cHyX-SeFetw@mail.gmail.com>

hello

> By moving these calls into the kernel, you don't make them necessarily
> fail-safe. This can all be implemented in user-space. By switching to
> a dedicated VT (say, VT12) and running VT_SETMODE+VT_PROCESS, you lock
> the machine. You can now implement your screensaver. If you run a
> spawner-process, you're even safe if your screensaver crashes.

Yes but this would lock the whole machine. Our plan is to make it posible
to lock a specific set of VTs - owned by the user who wants to lock.

e.g if user A locked all his VTs user B would still be able to switch to
his VTs.

Thanks
Simone Weiss


  reply	other threads:[~2015-03-23 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 22:03 helene.gsaenger
2015-03-22 22:23 ` Greg KH
2015-03-23 10:29   ` simone.weiss
2015-03-23 12:29     ` David Herrmann
2015-03-23 13:02       ` simone.weiss [this message]
2015-03-23 13:26         ` David Herrmann
2015-03-23 14:48           ` simone.weiss
2015-03-23 14:58             ` David Herrmann

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=efd8dbe1963af0bb849841f4fd5e718b.squirrel@faumail.uni-erlangen.de \
    --to=simone.weiss@fau.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helene.gsaenger@studium.fau.de \
    --cc=joe@perches.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.d.rustad@intel.com \
    --cc=peter@hurleysoftware.com \
    --cc=tiwai@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
all inboxes | Powered by JetHome®