Mountain wrote:
Thank you for the nice tutorial and the Google search terms.
I read your stuff and I also read several articles that came up from your search link. I have to admit that I am now a bit confused about the best way to do this. In particular, the comments at this post left me with a lot of questions:
http://digg.com/linux_unix/Tutorial_For ... E_over_SSHSo far -- just with ssh -- I have been able to open an SSH terminal session to my Linode, and I have been able to connect Nautilus. I was also able to use my local text editor to create and edit files on the Linode. Things got a bit dicey when I tried to edit and copy files that required root permissions. I am not sure how to smoothly handle that.
Am I off base in thinking that I can have the kind of experience I'm used to when I connect to a Windows server with Remote Desktop (or Ubuntu's Terminal Server Client)? Windows 2003 server has a full GUI obviously, and when I connect to a remote Windows server over the Internet, I have an experience almost exactly the same as if I were sitting at the machine. I often run the remote session full screen across dual monitors (1920 x 1200 each) and there are almost no restrictions on the work/tasks I can do on the server.
What I think I understand so far about connecting to my Linode (which does not have a GUI installed) is that if I want this kind of experience, I need to use nomachine.com's NX server. Is that correct?
Thanks for all the help!
in my experience, nomachine's NX server would suit your needs.. but I must highly stress you as a beginner to linux to become accustomed to navigating command line as well. I do not say this for any "elitist" reasoning, but just because this is how Linux has been founded and built... and while desktop wise it is making a progression to GUI, server wise it is still behind.
Also, you find interest in knowing that as of W2k8, almost everything is powershell (command line) again, and in fact 2k8 has an install mode that does not function with a gui.