Posted by: Anonymous Coward
on April 16, 2005 12:43 AM
LTSP is platform for managing thin clients which also includes facilities for running X clients on the server delivered to the X servers on the thin clients (there's that oddball backwardness in X naming conventions). Specifically, it manages a bunch of NFS exports which the thin clients mount (eg., / and<nobr> <wbr></nobr>/usr/bin/).
NoMachines NX protocol is compression and caching layer which you can tunnel X through. I'm kinda of surprised that LTSP hasn't fully incorporated FreeNX yet, but you can use <A HREF="http://pxes.sourceforge.net/" title="sourceforge.net">PXES</a sourceforge.net>, which does have support for NX and also replaces most of the functionality of LTSP. Unlike how LTSP is usually run, PXES doesn't work with NFS exports. Instead it's more like a tiny compressed live cd image which the clients boot from either using local CD or over the network using PXE which grabs the boot image from a tftp server. Although I've never done it, it's my understanding that you configure LTSP to work in essentially the same fashion, and can even use the PXES image.
Learn about Linux
Download Linux
Get Linux help
Apples and oranges
Posted by: Anonymous Coward on April 16, 2005 12:43 AMNoMachines NX protocol is compression and caching layer which you can tunnel X through. I'm kinda of surprised that LTSP hasn't fully incorporated FreeNX yet, but you can use <A HREF="http://pxes.sourceforge.net/" title="sourceforge.net">PXES</a sourceforge.net>, which does have support for NX and also replaces most of the functionality of LTSP. Unlike how LTSP is usually run, PXES doesn't work with NFS exports. Instead it's more like a tiny compressed live cd image which the clients boot from either using local CD or over the network using PXE which grabs the boot image from a tftp server. Although I've never done it, it's my understanding that you configure LTSP to work in essentially the same fashion, and can even use the PXES image.
#