Linked by Nik Tripp on Mon 2nd Mar 2009 21:40 UTC
SuSE, openSUSE IT solutions companies have been generating lots of buzz regarding thin clients basically since the early 1990s, but have yet to really penetrate into many suitable environments. These relatively cheap computer appliances carry broad promises like energy efficiency, space efficiency, and centralized maintenance and data storage. These claims could sound like the computer industry equivalent of snake oil. Kiwi-LTSP, a combination of KIWI imaging technology and Linux Terminal Server Project, is one open source solution for thin client servers.
Permalink for comment 351790
To read all comments associated with this story, please click here.
Kebabbert
Member since:
2007-07-27

Ok, there are still some serious misunderstandings going on. Lets try to establish the definitions. As you start with in math.



"In a thin-client setup, 0 CPU, 0 RAM, 0 processing is done on the client. Everything is done on the server. The client is just an I/O hub: mouse and keyboard events are sent to the server, video is sent back to the client. That's it. The local CPU/RAM is only used to boot the client. Nothing else."

As I have understood it, a thin client processes all software on it's weak CPU with little RAM. A typical thin client has 1GHz CPU and 256 MB RAM, and boots from it's server and downloads all applications from the server and runs the all of the applications or parts of the applications, on it's 1GHz CPU.

Whereas an ultra-thin-clients doesnt process any software at all, it just handles I/O. That is SunRay. The server processes all software. On the SunRay no software is processed at all, it just shows the bitmaps that the server transmits.


You are telling me that this is wrong? You are telling me that any thin client act the way as the SunRay does. Every thin client just shows the picture from the server, and no processing is done on its 1GHz CPU and 256MB RAM? Everything is processed on the server? Is this so? Can you show me a link to a thin client that behaves like this? (Other than SunRay). I have never found any ultra-thin-client other than SunRay.

Either you or my understanding of thin-clients is very wrong. Who is correct? You or me? If you can show links on thin clients working as you described, then you are correct and I am wrong. If you can not show links, then you are wrong and I am correct.





"I don't know how many times I can say this: a dual-P3 system with 4 GB of RAM **DOES SUPPORT** 30 thin-clients, where Firefox, Java, OpenOffice.org, and Flash, are all running on the server, with just the display being shot back to the client. WE DO THIS EVERY FRIGGING DAY!! WE HAVE BEEN DOING THIS FOR 7 YEARS ALREADY!!! THIS WORKS!! Get it yet?"

And you also say that a dual P3 system with 4GB does support 30 thin clients. Where the thin clients does not process any software at all. All software processing is done on the dual P3 cpus. You claim.

I find this very very hard to believe. If it is really is true, then I should look into this solution instead.

I mean, for one user, at least a 1GHz P3 cpu and 512 MB RAM computer is necessary. For 30 users, you would logically need a server with 30 x 1 = 30 GHz P3 and 30 x 512 MB = 6GB RAM. But now you are telling me that it is not necessary. Something is very wrong here. How in earth could it be possible to run 30 users on a dual P3 and 4GB RAM? I dont get it. That config is needed for one single user. How can it support 30 users???

There are some grave misunderstandings going on right now. Even the nick "broken_symlink" is confused. He also believes the same thing as me. He states that a thin-client solution should need a ton of RAM.

We can settle this out, if you post some links to thin-clients. Then I can read about them myself. And study the datasheets. And then I can tell if I have misunderstood the thin client concept.

Reply Parent Score: 2