[FreeNX-kNX] Thin-Client-Network

[Doug Burks]

Installing FreeNX on an existing LTSP server is possible:
http://ltsp.criticalcontrol.com/freenx.html

NX may be integrated directly into the LTSP distribution in the future:
https://listman.redhat.com/archives/k12osn/2004-September/msg00006.html

Doug


On Wed, 29 Sep 2004 20:38:01 +0200, Lindner <lindner_marek at yahoo.de> wrote:
> 
> 
> Doug Burks wrote:
> 
> >I think the best way to understand the concept is to see it in action.
> > The easiest way to set up an NX server is to download the Knoppix 3.6
> >.iso (linked in my previous email), burn to CD, and boot a PC from
> >that CD.  Once Knoppix boots, follow the instructions here:
> >http://www.tinyapps.org/freenx/
> >
> >Once you've connected from the NX client, you'll notice that KDE and
> >all applications are running on the NX server and the screen is being
> >transported across the network to the NX client.  While you have this
> >NX session open, you could go to another PC and fire up another NX
> >session.  The NX client could be a PXES Thin Client, a Windows PC
> >running the Windows NX client, a Linux PC running the Linux NX client,
> >or a PC booted on the Knoppix 3.6 CD running the included NX client.
> >Thus, one NX server serves multiple clients.
> >
> >Once you've seen it action and understand the concept, then you'll
> >want to build a real NX server (running from a hard drive instead of
> >the Knoppix CD).  To do this, you could install Knoppix to the hard
> >drive, or install a regular Debian, Red Hat, or Gentoo distribution,
> >or just about any flavor of Linux.  Install all of the apps that your
> >thin-client users will need on the NX server.  Then install NX and
> >test an NX client like you did above.  Once you've tested
> >successfully, then you can start adding more and more thin clients--5,
> >10, perhaps 20 or more, depending on what applications the end-users
> >will be using.
> 
> Ok, I'll do that first.
> 
> >I have no experience with LTSP, but my understanding is that it uses
> >the raw X protocol to transmit the screen over the network.  This is
> >VERY inefficient as NX can compress the raw X protocol and decrease
> >the client/server round-trip latency at the same time, decreasing
> >network traffic and increasing responsiveness.
> 
> Thats why I would like to use NX as a proxy.
> The advantage is that LTSP is almost "ready-to-use". DHCP / TFTP / NFS
> and all the rest (on the client and server side) is preconfigured and
> can easily be customized. I'd like to combine both advantages ...
> 
> Regards,
> Marek
> 
> 
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>