linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: john@grabjohn.com, jsimmons@infradead.org, terje_fb@yahoo.no
Cc: linux-kernel@vger.kernel.org
Subject: Re: Real multi-user linux
Date: Fri, 13 Jun 2003 18:43:23 +0100	[thread overview]
Message-ID: <200306131743.h5DHhNdv000312@81-2-122-30.bradfords.org.uk> (raw)

> >     The next stage will be non PC boards supporting more than
> > one graphics display output. Every now and then you see such a
> > board. I seen a 8 graphics chip board with 8 video outputs.

> As the number of terminals increases you might want to investigate the
> possibility of terminal driving units connected to the main box, like
> this:

[snip diagram]

Of course, those terminal driving units could actually then just be
replaced with multiple-display-and-keyboard-enabled X servers.

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.

John.

             reply	other threads:[~2003-06-13 17:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 17:43 John Bradford [this message]
2003-06-13 20:11 ` Real multi-user linux James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2003-06-16  8:12 Aivils.Stoss
2003-06-13 20:30 John Bradford
2003-06-13 21:54 ` James Simmons
2003-06-13 17:46 John Bradford
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=200306131743.h5DHhNdv000312@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=jsimmons@infradead.org \
    --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).