Nomachine recently released a new major version (3.3.0), which did not introduce many new features, but fixed some bugs (some keys did not work here on my french keyboard for example), and generally feels “snappier” (in my opinion of course, test and check it for yourself 😉 ). It is available in portage for both free server edition (binary only, 2 concurrent connections), and for freenx (open-source, no connections limit).
For some time an alternative client/server from 2X has been available in portage, as net-misc/nxclient-2xterminalserver and net-misc/nxserver-2xterminalserver. Based on old NX 1.5, it provided both a GPL client (missing the > 2.0.0 NX features though) and a working server close to Nomachine one. However it never really got any updates since it was made available. Upstream closed down the website, the client needs fixes for gcc 4.3 and –as-needed, does not work well with current NX servers, the server is still based on old NX code (and is probably vulnerable to some xorg security issuse), so this is last rites time for both of them. They will still be available in the NX overlay if you need them.
Open-source alternatives are availble in portage: net-misc/qtnx for client, net-misc/nxserver-freenx for server.
Now I promised to talk about newer NX systems right? A new bug report was recently opened on x2go, a “server based computing environment” which uses NX technology but is not a clone of current nxclient/nxserver. Nice thing is everything is open-source, including the client (ebuild for it already works). Now some work is needed before there is a x2goserver package in portage, but that will certainly make a nice alternative to current NX servers available. If you already use it, don’t hesitate to come and comment on the bug!
Note to myself: I really need to write some documentation on all of these one day…
2 thoughts on “NX servers and clients, old and new”
Is this ready for prime time yet on amd64? I remember trying out NX a while ago on amd64 and it was a real mess (I pretty-much ended up building 32-bit in a chroot and getting it to work in the amd64 environment). I’ve been living with tightvnc over ssh and that generally works, but NX sounds like it would be a lot more responsive.
Indeed, in fact in the beginning the net-misc/nx ebuild was multilib-only, as it was built in 32bit. Full 64bit support was added in 3.0.0 version, with NoMachine providing 64bit client and server, and providing sources for NX libs working on amd64.
So now, clients and servers (both closed and open source) work as well on amd64 than x86 🙂 I use it daily to connect to my home computer (sometimes just an app like pidgin, sometimes full desktop)
Comments are closed.