From: Adam Huuva <sventon@easter-eggs.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Several concurrent terminals.
Date: Thu, 02 Nov 2000 11:31:26 +0000 [thread overview]
Message-ID: <3A01508E.A992B792@easter-eggs.com> (raw)
Greetings,
We'd like to have two sets of keyboard/mouse/screen connected to the
same computer with each set having the control and output of an
independent X
session each, concurrently. There might for instance be the ps/2
keyboard and mouse and
USB dittos. After attempting (and failing) we believe the problem is
really one of the kernel only allowing one virtual terminal to be active
at one time. Is this so and what can be done?
Cheers,
--
Adam Huuva / Easter-eggs Spécialiste GNU/Linux
44-46 rue de l'Ouest - 75014 Paris - France - Métro Gaité
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 41 35 00 76
mailto:sventon@easter-eggs.com - http://www.easter-eggs.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-02 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 11:31 Adam Huuva [this message]
2000-11-03 7:20 ` Several concurrent terminals 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=3A01508E.A992B792@easter-eggs.com \
--to=sventon@easter-eggs.com \
--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