| |||||||||||||
|
| |||||||||||||
NX too hard to useNX too hard to usePosted Aug 1, 2005 17:48 UTC (Mon) by scripter (subscriber, #2654)Parent article: The Arrival of NX, Part 1 (Linux Journal)
Maybe I'm missing something, but I found NX far too difficult to setup and use a month ago. I think it can be corrected, but for now, it's difficult.
I have SSH access on every machine I want to log in to. Seems like I should be able to fire up my NX client and connect WITHOUT having to import the NX server's (separate) key. SSH caches keys for me, and already has the sever's normal SSH key. Why does NX need a second, conflicting key? There can only be one key imported at a time. I regularly connect to several separate remote machines, so this is unworkable.
Getting NX installed is also something of a pain. The NoMachine NX client on Windows uses Cygwin, but their cygwin instance (cygwin.dll) conflicts with the one that I already had on the machine. So, I uninstalled the NX windows client.
NX was fast, and it looked promising. It's the finer points of usability that made me reject it for the time being.
(Log in to post comments)
NX too hard to use Posted Aug 1, 2005 20:22 UTC (Mon) by kobserver (guest, #30087) [Link] "NX far too difficult to setup and use (...)"
"Why does NX need a second, conflicting key?"
"There can only be one key imported at a time. I regularly connect
to several separate remote machines, so this is unworkable."
"The NoMachine NX client on Windows uses Cygwin, but their cygwin
instance (cygwin.dll) conflicts with the one that I already had on the
machine."
NX too hard to use Posted Aug 2, 2005 19:22 UTC (Tue) by scripter (subscriber, #2654) [Link] It would be nice if NX were easy to use out-of-the-box instead of having to search the excellent knowledgebase. Indeed, that's how I found answers to several of problems previously. I'm glad the client is improving, but I think it still needs to be easier to use. I don't want to have to copy down a client key just so that I can connect. I already have a user account plus ssh, so why can't that be good enough?
As for Cygwin, I hope NoMachine is getting their enhancements merged upstream. I've customized my copy of cygwin, remapping /cygdrive/c to /c and so forth. The NX cygwin instance doesn't play well with my existing config, making my pre-existing install nearly unusable. Also, the NX Windows client doesn't work for non-admin privileged user accounts. Believe it or not, I don't run as an admin on my Windows machines.
NX too hard to use Posted Aug 12, 2005 19:41 UTC (Fri) by kobserver (guest, #30087) [Link] "I've customized my copy of cygwin, remapping /cygdrive/c to /c
and so forth."
"The NX cygwin instance doesn't play well with my existing
config,..."
"...making my pre-existing install nearly unusable."
"Also, the NX Windows client doesn't work for non-admin privileged
user accounts...."
NX too hard to use Posted Aug 13, 2005 20:06 UTC (Sat) by scripter (subscriber, #2654) [Link] One of the things I've enjoyed about reading LWN is that most people, by and large, tend to be polite and less inflammatory than in some other linux related forums. I suppose one of the risks of making comments publicly is that someone may respond and resort to character attacks rather than intelligent dialog.
In any case, I hope my comments about NX difficulties will help others to be aware of and avoid trouble. I'm also sure that NX will continue to improve over time. It's a cool project and has great potential.
|
|
||||||||||||