On Sat, 10 Mar 2007, [EMAIL PROTECTED] wrote:

> To clarify this issue:
>
> Thin clients have all the features of the server desktop just about without
> restriction. (fiddles: local devices, sound)
> Thin clients work well with 32M RAM and are the 'keyboard and display' on the
> server
> BUT *some* applications, running on your server (where they are called the
> client application) use local(thin client) memory for graphics stuff (Called
> X-server memory) eg Firefox
>
> Most of your questions are not relevant to thin-clients.
> The bottom line is 'how much ram on the thin client' to never crash the
> client: (I do not use swap) (so for me)
> 128M - almost never has a problem
> 256M - never had a problem
> 512M - smallest ram that I can purchase today
>
> In terms of CPU I notice, but its not bad, the ebox-2300 ($85, 128M and
> 200MHz)
> My via 633MHz clients are just like the desktop on the server (256M)

So these clients are running (just to make sure I understand) nothing
but the kernel, minimal libraries, X, and any devices you care to set
up?  Or are they running even less -- a built-in X?

I hate to have to ask, but for me over the decades a "thin client" has
been everything from a short-lived custom PC that networked back to a
host PC on a network nobody has ever heard of before or since (mid 80's)
through a variety of Sun SLC and ELC diskless systems (that ran a fully
copy of the OS, albeit booted diskless) through a range of linux boxes
booted diskless the hard way, pre-PXE.  A 512 MB client damn well ought
to be able to just boot and run the entire OS locally and even do it
nearly transparently and extremely fast.

There has over the years also been forever the question of just where
the apps get run -- with X remotely (which even with thick clients and X
servers can have mediocre performance on a heavily burdened network or
server) or locally (where they occupy what used to be a biggish chunk of
memory.

The neoware online docs do not help at all with this, and while I'm
working my way through the ltsp docs, I haven't been able to figure out
yet whether you can boot any terminal image you care to set up (it seems
like you could, with ltsp or not) and e.g. mount /usr to become a simple
"instant" diskless node.  That's why I was asking.  Are the terminals
set up to be so thin (with LSTP in general) that one pretty much has
a bare X server and a desktop, every thing running remote, or do they
use their local CPUs for anything like an actual workstation boot into
which one can login outside of X?

    rgb

>
> James
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

-- 
Robert G. Brown                        http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:[EMAIL PROTECTED]



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to