From: Gerhard Mack <gmack@innerfire.net>
To: "Terje Fåberg" <terje_fb@yahoo.no>
Cc: John Bradford <john@grabjohn.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Real multi-user linux
Date: Fri, 13 Jun 2003 11:19:51 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0306131117280.5168-100000@innerfire.net> (raw)
In-Reply-To: <20030613140111.34979.qmail@web12901.mail.yahoo.com>
On Fri, 13 Jun 2003, Terje Fåberg wrote:
> John Bradford <john@grabjohn.com> skrev:
>
> > This idea has come up before, have a look at:
> > http://marc.theaimsgroup.com/?.....
>
> Thank you for providing these references. Especially
> the first thread discusses some thoughts I had, too.
>
> To summarize: People have thought about of one linux
> box directly supporting multiple (X-)consoles before.
> But this is not possible as of now, because X would
> have to be told to stop switching consoles and because
> the kernel cannot activate more than one console at
> one time. Additionately, multiple video cards may
> require mappings into the same memory area for certain
> functions. Some people have started to work on a
> solution, but these projects were orphaned.
>
> My motivation is simply a private one. I have a
> P3-866 with 1.5G RAM and a scsi raid here which serves
> its own console and an old P133 as X terminal.
> Although this machine is already some kind of
> outdated, it has plenty of power to serve two users
> with one KDE session each.
>
> I started to think about this, because the P133 died
> away due to a failing processor fan. Although
> replacing the whole machine with a similar one
> probably is cheaper than a good usb keyboard and
> mouse, it is also a question of comfort. No waiting
> for the terminal to boot up, no double administration,
> less power consumption, less space needed and so on.
>
> Although I have some C/C++ expirience, I have
> absolutely no clues about kernel and or X internals,
> so I guess I have to forget this for now.
You can gain most of those advantages by using the machine as a terminal
server. http://neoware.com has solid state(fanless) clients. So you
still get the lower admin costs and a nice quiet office. Hopefully
someone else will reply with an even cheaper thin client.
Gerhard
--
Gerhard Mack
gmack@innerfire.net
<>< As a computer I find your faith in technology amusing.
next prev parent reply other threads:[~2003-06-13 15:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 8:13 Real multi-user linux John Bradford
2003-06-13 14:01 ` Terje Fåberg
2003-06-13 15:19 ` Gerhard Mack [this message]
2003-06-13 16:33 ` Alan Cox
2003-06-13 16:56 ` James Simmons
2003-06-13 20:39 ` Bernd Eckenfels
-- 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: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-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.0306131117280.5168-100000@innerfire.net \
--to=gmack@innerfire.net \
--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).