On Fri, 2006-04-14 at 07:39 -0500, Johnny Hughes wrote: > We have created a new version of freenx (freenx-0.5.0-8.c4.noarch.rpm) > and moved it to the testing repo. > > This is based on the code displayed at the LWE in San Francisco ... > > http://lwn.net/Articles/146825/ > > http://www.linuxjournal.com/article/8489 > > (though it is not officially released as stable by the freenx people) > > This version should handle printing and reconnecting to running sessions > much better. > > Running sessions (on the nx server, that is the machine you are > connecting to) are stored in "/var/lib/nxserver/db/running" ... if you > have been disconnected in the past, there may be several old sessions > out there that need to be cleaned up ... go remove the sessions that are > invalid (all of them in that directory if you do not have any open > sessions to that server). There is no real auto cleanup of these if > your session breaks ... I will try to develop something that works > later. In the meantime, if you session list is to big and some are dead, > you will have to delete them manually. > > This version also allows rootless mode, which is faster compression. > > So far, this is a major improvement to my user experience for NX. > > ------------------ > Copy the testing CentOS-Testing.repo file from here: > > http://dev.centos.org/centos/4/ > > to /etc/yum.repos.d/ , then use this command to install freenx: > > yum --enablerepo=c4-testing install freenx nx > > Report issues with this to the freeenx tracker here: > > http://bugs.centos.org/view.php?id=1307 > > ------------------- > A guide for setting up the NoMachine client (to connect to the freenx > server, if you installed it) is here: > > http://fedoranews.org/contributors/rick_stout/freenx/ > > (you only need to do the client items, as the server is taken care of > with the above yum install). ---- fwiw - I just downloaded and installed last night so I don't have much history to report but I did install freenx-0.5.0-8 last night, rebooted, deleted all the old sessions and connected and worked fine until earlier today when I lost power on my home system (the remote). I fired back up and resumed the session without issue and I am very happy about that as that was one of the issues (resuming sessions) so in that regard, any improvement is appreciated. Also, I no longer get the errors on login which I am sure were caused by my trying to use remote cups but I haven't read a thing about configuration so the errors are gone but it's obvious that cups doesn't automatically configure remote printers ;-( so I will probably have to read up on this to see if I have a chance to print on my home printer from the remote freenx server. Things definitely 'seem' better anyway Thanks Craig