Being a lazy embedded software engineer has several advantages, like being able to control every gadget in your house from your couch. Needless to say, you also remotely log in to the several boxes spread around the house.
However, if you happen to be using a windows machine (e.g. a laptop, you are on your couch of course... and only because your smartphone probably does not have a capable enough client just yet) to log in to a unix box and desire to partake in the advantages a GUI offers (all you ssh console people, the GUI is a major advancement, so get with the times already!), then you have to contend with the beast known as VNC.
if you are on a Ubuntu machine (yes, no self-respecting engineer has only a windows machine.. it will, at the very least, dual-boot in to Linux), then ubuntu's Remote Desktop works splendidly. However, if you are ssh-ing over the "nekked inter-webs" then VNC is your only option. and that blows.
Or so I used to think, before running into FreeNX. Google, thou truly art a friend! FreeNX blows VNC completely out of the water. No more need to juggle between Hextile, CoRRE, Tight and other sub-par encodings. No more jiggling of the colormaps, image quality and compression levels only to have the entire processor reduced to competing with molasses, and failing.
also ALT +TAB works! Though it does require one keystroke to enable: "CTRL + ALT + K"
Thanks Mark!
Adios VNC-viewer / REAL VNC. you suck. Hello, FreeNX!
1 comment:
though in all fairness, I still have real use for UltraVNC on my Windows Vista laptop. Vista Home Premium does NOT include remote desktop, so UltraVNC is a very viable solution.
there is a minor hitch with using UVNC with UAC enabled though: you have to log in as an administrator and set a VNC server password. Once you do that, it's a breeze.
Post a Comment