From: "Gabor Z. Papp" <gzp@myhost.mynet>
To: linux-kernel@vger.kernel.org
Subject: X and console paralell
Date: Sat, 5 Jan 2002 09:00:09 +0100 [thread overview]
Message-ID: <20020105080009.GI22314@gzp2.gzp> (raw)
In-Reply-To: <20020104233745.GG22314@gzp2.gzp> <Pine.LNX.4.21.0201041604290.8385-100000@dhcp-199-10.nvidia.com>
In-Reply-To: <Pine.LNX.4.21.0201041604290.8385-100000@dhcp-199-10.nvidia.com>
* Mark Vojkovich <mvojkovich@nvidia.com>:
| > Plugging extra USB keyboard and mouse would solve the
| > problem, and I would be able to run X and console
| > simultanously?
|
| No, both the console and X need a VT. As far as I can tell
| Linux only lets you have one VT active at any time. You can
| have a different mouse and keyboard used by the console and
| by X (in theory at least), but I don't think that solves the
| mutual exclusivity of VTs.
|
| Some people may have kernel hacks to allow this sort of
| thing, but I haven't been keeping track of this stuff. It's
| not an area that I've been involved in.
Any idea? Basically I would like to run 2 monitor, one for X
and one for console paralell, with 1 keyboard/mouse.
Switching between them like with one monitor, but when no
work on the one, I would like to keep the signal on the
unused monitor, eg I would like to see the (not blank) screen.
next parent reply other threads:[~2002-01-05 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020104233745.GG22314@gzp2.gzp>
[not found] ` <Pine.LNX.4.21.0201041604290.8385-100000@dhcp-199-10.nvidia.com>
2002-01-05 8:00 ` Gabor Z. Papp [this message]
2002-01-05 11:40 ` Davidovac Zoran
2002-01-05 16:44 ` James Simmons
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=20020105080009.GI22314@gzp2.gzp \
--to=gzp@myhost.mynet \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®