On your client machine, you should download the nx client from this page appropriate for your platform.> /usr/NX/scripts/setup/nxserver -install Once downloaded, install as usual per rpm:.From this page, I chose the rpm packages. Installation of NoMachine’s NX server involves installing 3 packages that depend on each other to function.The previous install of nx/freenx created a user ‘nx’, and the ‘yum remove’ command above failed to delete that user, so I manually removed user ‘nx’.Uninstall nx and freenx previously installed through yum.In summary: installation was trivial, and performance is remarkably better with far fewer quirks seen in the previous version. So, I decided to see how difficult it would be to install the free version of nxserver 3.1.0 on my Fedora server. According to the changelogs, there are a number of fixes over the version 2.1.0 installed by yum. One minor problem is that there is an updated version of the NX Server available (as of this writing, version 3.1.0-2 ). Basically, you use yum to install 2 packages on the server, install a client program on the clients, sync the ssh keys, and you’re done. Assuming you already have sshd running on the server, then a great set of installation instructions is here.  Searching around a bit, I found freenx, a GPL implementation of NX by NoMachine. VNC has been around a long time, and I’ve used it for years in the Windows world, but it’s performance is not so great, and setting it up to run over ssh is not so fun. So, I thought I’d see if there was an easy way to remotely access the desktop of my Fedora box. Because of the way Aptana is able to generate code on the fly during development, it’s a lot easier to develop on the target server than it is to develop on my Windows Vista laptop and transfer (or sync) the pages repeatedly. I’ve been writing code in the wonderful Aptana Studio, including projects in Ruby on Rails.
0 Comments
Leave a Reply. |