I decided not to use FreeNX because of two things
1) Could not find any way to use the GDM login screen that I love so much
2) Multinet configuration and low cost Giga bit NIC's removed the bandwidth problem
I can buy D-Link Giga bit NIC's for $30 each and Asus 24 10/100 with Giga bit uplink for just over $100.
I set the entire school up on a multiple zone network with equal number of terminals on each zone. Each zone has it's own Asus switch and it's own Giga bit NIC in the server.
THIS NETWORK IS SMOKIN' FAST!
The server is a dual core AMD that still has an empty socket to add another dual core CPU. It has 4G RAM and a 250 SATA drive ( RAID 1 soon ).
I can have the entire school logged in and doing stuff. The computer lab can be full of students playing TuxTyping (a very graphic intense game) and a teacher can click on the OpenOffice icon and in about the time it takes you to blink OpenOffice is up and ready to use.
Sorry for going off topic a bit. I don't think FreeNX is needed for internal networks using LTSP.
On Wed, 2006-03-01 at 07:15 -0500, Lonnie Cumberland wrote:
I see. So in what situation would you want to use LTSP with FreeNX together? Would it be that FreeNX is used just like VNC so that someone with a Windows machine could access the LTSP server in a similar way that VNC allows for you to do? My guess would also be that if this is the case are there FreeNX client software similar to VNC as well? Thanks, Lonnie Kanwar Ranbir Sandhu wrote: >On Tue, 2006-28-02 at 12:52 -0500, Lonnie Cumberland wrote: > > >>Now I am confused in that I am not sure why a person would need FreeNX >>when LTSP is a very similar item? >> >> > >They're actually not. LTSP will boot a thin client: FreeNX won't. >Think of NX as a super-duper-crazy-fast upgrade to VNC. They're not >exactly the same, but the overall concept is. > > > >>Also, when would you use them together? >> >> > >1. LTSP over a WAN. Boot locally, but work globally (TM). :) >2. Session saving. Can't do that with plain old XDMCP. > >There are many more reasons, but that's it from me. I hope that helps >some. > >Regards, > >Ranbir > > >
|
signature.asc
Description: This is a digitally signed message part
