From: Phillip Susi <psusi@cfl.rr.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Multiple consoles
Date: Mon, 09 Jan 2012 16:32:14 -0500 [thread overview]
Message-ID: <4F0B5CDE.8000700@cfl.rr.com> (raw)
In-Reply-To: <20120109212125.GO4266@type.famille.thibault.fr>
On 1/9/2012 4:21 PM, Samuel Thibault wrote:
> Phillip Susi, le Mon 09 Jan 2012 16:11:36 -0500, a écrit :
>> Does this make sense or am I missing something?
>
> It used to be planned, but nobody took the job, because X doesn't need
> this (see option -sharevts).
If you do that, you can't use vcs. AFAICS, there won't be any on the
second seat, and if you switch the first seat back to a vc, it will read
input from both keyboards. And what about magic-sysrq? A SAK on either
keyboard will kill the primary X won't it?
next prev parent reply other threads:[~2012-01-09 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 21:11 Multiple consoles Phillip Susi
2012-01-09 21:21 ` Samuel Thibault
2012-01-09 21:32 ` Phillip Susi [this message]
2012-01-09 21:56 ` Samuel Thibault
2012-01-09 22:07 ` Geert Uytterhoeven
2012-01-09 22:22 ` Alan Cox
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=4F0B5CDE.8000700@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
/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