On Mon, 8 Mar 2010, Andreas Hasenack wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm trying the lucid AMI (specifically ami-9ffe11f6) and can't get the > "official" nx client to work with it. I just verified functionality on the latest ubuntu-lucid-daily-i386-desktop-20100308 in us-west-1 ami-5b70211e .
Heres how: - download an NX client to your local system. The 2 clients available are "qtnx" (in universe) and the commercial NX client [1]. - launch an ec2 instance. To do this you have to have a ec2 account set up [2]. Then, get the AMI id of the machine image you want to start. You can get that from the table at [3]. Launch the image either via the AWS interface or the command line. Make sure you give the instance your key, or you will not be able to reach it. - ssh to the instance as 'ubuntu' user set the 'ubuntu' user password (required for the nx server) $ sudo passwd ubuntu - Launch nx client and point it at your new instance. Cross you fingers. I had initial problems with the qtnx client. It spun but but nothing really happened. Everything "just worked" with the commercial client. There is a blog post of similar at [4] -- [1] http://www.nomachine.com/download-client-linux.php [2] https://help.ubuntu.com/community/EC2StartersGuide [3] http://uec-images.ubuntu.com/desktop/lucid/current/ [4] > I then noticed that the nx ppa that is installed in this image was pointing to > karmic: > # cat /etc/apt/sources.list.d/freenx-team-ppa.list > deb http://ppa.launchpad.net/freenx-team/ppa/ubuntu karmic main > r...@domu-12-31-39-0a-4a-22:~# I hadn't realized that the freenx team had started making lucid packages available. I've not tested them, and have tested (as above) the karmic ones. That said, if there is lucid packages we should be using them. I'll switch the nightly builds to those. -- Ubuntu-cloud mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-cloud
