From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: linux-kernel@vger.kernel.org
Subject: Re: linux as a minicomputer ?
Date: Thu, 11 Apr 2002 17:43:31 +0100 [thread overview]
Message-ID: <20020411164331.GR612@gallifrey> (raw)
In-Reply-To: <20020411154601.GY17962@antefacto.com>
* John P. Looney (john@antefacto.com) wrote:
> Sorry if this isn't the place for this question, but it's something that
> came up in general office talk today.
>
> Many many moons ago, the GGI project promised us the ability to buy a
> four-processor box, four PCI video cards, four USB mice & keyboards, and
> let four people use that machine at once, with benefits all around.
<snip>
> Are there any plans to bring this sort of functionality to Linux 2.6 ? As
> I remember, some of the problems were that the GGI code was never going to
> get into Linux proper, and enumeration of multiple keyboards and mice, but
> I would have thought that was there a need, these problems would have been
> fixed by now.
I'm not sure, but I don't think any code is needed if you run X. Bung
four USB mice, four USB keyboards in and four video cards. Write a
separate X config for each one specifying which PCI card should be used
and which mouse/keyboard device should be used. Now start an X server
for each one.
(Fun should form in the efforts to figure out which mouse is associated
with which keyboard and with which video output).
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2002-04-11 16:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 15:46 linux as a minicomputer ? John P. Looney
2002-04-11 16:43 ` Dr. David Alan Gilbert [this message]
2002-04-11 16:49 ` Vojtech Pavlik
2002-04-11 17:07 ` Ed Sweetman
2002-04-11 17:12 ` Vojtech Pavlik
[not found] ` <3CB69032.D332FA51@aitel.hist.no>
2002-04-12 8:08 ` Vojtech Pavlik
2002-04-11 17:09 ` Dr. David Alan Gilbert
2002-04-11 17:13 ` Vojtech Pavlik
2002-04-11 17:49 ` John P. Looney
2002-04-11 17:59 ` Rene Rebe
2002-04-11 18:46 ` James Simmons
2002-04-11 19:06 ` Vojtech Pavlik
2002-04-12 7:41 ` Helge Hafting
2002-04-12 8:09 ` Vojtech Pavlik
2002-04-11 18:01 ` James Simmons
2002-04-11 19:07 ` Vojtech Pavlik
2002-04-13 19:03 ` Alan Cox
2002-04-11 19:45 ` H. Peter Anvin
2002-04-11 20:05 ` James Simmons
2002-04-12 7:31 ` Helge Hafting
2002-04-13 18:56 ` Alan Cox
2002-04-13 19:29 ` H. Peter Anvin
2002-04-13 19:37 ` Richard Gooch
2002-04-13 19:40 ` H. Peter Anvin
2002-04-13 19:49 ` Richard Gooch
2002-04-13 22:08 ` J.A. Magallon
2002-04-13 23:46 ` Richard Gooch
2002-04-13 19:51 ` Alan Cox
2002-04-13 19:36 ` H. Peter Anvin
2002-04-14 4:30 ` Bill Davidsen
2002-04-14 13:45 ` Alan Cox
2002-04-14 16:44 ` Sten
2002-04-14 16:50 ` Dr. David Alan Gilbert
2002-04-14 20:20 ` H. Peter Anvin
2002-04-15 16:05 ` Thomas Molina
2002-04-15 0:37 ` Rob Landley
2002-04-15 8:46 ` Helge Hafting
2002-04-15 9:10 ` Alan Cox
[not found] ` <3CBB522C.8070704@bcgreen.com>
2002-04-15 18:09 ` Rob Landley
2002-04-14 2:35 ` ux " jw schultz
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 17:42 linux " Ivan Ivanov
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=20020411164331.GR612@gallifrey \
--to=gilbertd@treblig.org \
--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