We are trying to help you avoid pitfalls of the Ubuntu solution offers. VNC or RDP really are terrible on many levels. There are better solutions that are in the Canonical repos.
Video editing just can't be done over remote connections. But almost any other "productivity" program can be run easily over the LAN from another system.
It is only the new people who try to use VNC or RDP. I really wish they'd stop acting like those are options. They are not. The Gnome project does some excellent work, but not this stuff. Perhaps in another 2-5 yrs, it will be ready for production use, but not today. Gnome has a habit of inflicting their ideals on the world - at the cost of terrible performance and bloat. IMHO.
On the LAN, using remote X forwarding through X11 is the easiest, most likely answer to running remote programs. I do it all day, everyday. Right now, I have about 20 windows open. 3 of those are local. All the others are into remote systems - using X11 forwarding through ssh. That includes this browser window, my password manager, fat email program and shells.
When ever I see RHEL training show how to setup vnc-server between Linux/Unix systems, I want to puke. They should spend that time on ssh and ssh techniques instead. THAT would be more useful.
By using remote X11 forwarding, you don't care what the resolution of the remote system is. Each window appears like a local window and uses the resolution of the local system.
Humor me for 10 seconds. Try this:
Code:
$ ssh -X {userid}@{remote IP} {name of terminal program}
Change the stuff for your setup as needed. I'd use:
Code:
$ ssh -X thefu@172.22.22.66 xterm -sb &
If my username on both systems is the same, that part isn't needed. If your system doesn't come with the xterm program, use whatever terminal you like or install xterm.
Should take 1-2 seconds and an xterm window from the other system should be displayed. 99.9% of the programs on that remote system can be run from this terminal window and each will be displayed as a new window where you sit.
Because my remote desktop system is known via DNS, I can use:
Code:
$ ssh -X regulus libreoffice &
to have LibreOffice run on a remote system, but displayed locally. On the LAN, I don't notice any slowness. But video editing is problematic and is a bad test for remote programs. I can control and move that window between the different monitors on my local workstation. It behaves like a local program. If the LAN is fast enough, watching 1080p video works as well, though that's a not-so-great idea. It is smarter to share the storage over the network using NFS and run the video stuff locally. Use NFS for Unix-to-Unix file sharing.
Bookmarks