From: James Simmons <jsimmons@infradead.org>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org, <terje_fb@yahoo.no>
Subject: Re: Real multi-user linux
Date: Fri, 13 Jun 2003 22:54:51 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0306132250500.29353-100000@phoenix.infradead.org> (raw)
In-Reply-To: <200306132030.h5DKUYlu000211@81-2-122-30.bradfords.org.uk>
> > > So, instead of trying to add more and more terminals to a single box,
> > > you could stick with four-headed X servers, which would probably be
> > > more scalable.
>
> > The biggest limitation is the PCI bus. Only so many cards can go in. I
> > guess you could fill the machine up with graphics cards and go with
> > external USB audio and TV tuner cards. One to match each graphics card.
>
> No need:
>
> A single machine can support four displays, keyboards, and mice easily. We
> can use such machines as X servers for four people. Each one can be connected
> via Ethernet to the Linux supercomputer. That way you get the cost advantages
> of the multi-headed setup, with the scalability of the X server setup. I think
> you could scale to 64 or 128 users like that.
Basically you are describing a thin client kind of model. I like to
create
high end thin clients but I don't have any funding. Currently thin
clients don't have the power to do multi-media as well as PCs.
I did everything so far with my own money and time. I don't think we
need a supercomputer. Here is a idea but it would require a good amount
of work. Create a X server that runs on one remote server and it programs
the hardware remotely. Now that would save enormously. I started to work on
this but didn't have time. Just some ideas to throw at you.
next prev parent reply other threads:[~2003-06-13 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 20:30 Real multi-user linux John Bradford
2003-06-13 21:54 ` James Simmons [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-16 8:12 Aivils.Stoss
2003-06-13 17:46 John Bradford
2003-06-13 17:43 John Bradford
2003-06-13 20:11 ` James Simmons
2003-06-13 17:34 John Bradford
2003-06-13 17:32 ` Alan Cox
2003-06-13 20:00 ` James Simmons
2003-06-13 8:13 John Bradford
2003-06-13 14:01 ` Terje Fåberg
2003-06-13 15:19 ` Gerhard Mack
2003-06-13 16:33 ` Alan Cox
2003-06-13 16:56 ` James Simmons
2003-06-13 20:39 ` Bernd Eckenfels
2003-06-12 23:19 Terje Fåberg
2003-06-13 0:43 ` Bernd Eckenfels
2003-06-13 17:00 ` James Simmons
2003-06-13 17:17 ` 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=Pine.LNX.4.44.0306132250500.29353-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terje_fb@yahoo.no \
/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;
as well as URLs for NNTP newsgroup(s).