[SOLVED] ssh uses remote machine's hardware or local machine's hardware
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
im not 100% but i believe with X11 Forwarding there is zero rendering local. in other words all of the rendering is done on the system that is ssh'ed into, not the one you are physically on. this will be the same no matter what OS you use to access the remote application.
this is an issue with RDP as Microsoft would call it and X11 Forwarding as it is known for Linux.
keep in mind that even with RDP all you are passing is keystrokes and mouse clicks. 100% of the rendering is performed on the remote system.
Linux (X11 / XOrg / XWindows) uses a very differerent arrangement than does Windows (Remote Desktop).
Linux uses a client-server windowing system. (Even on your local machine, there are two processes running.) One sends instructions to the other, which does the actual rendering. And so, these two halves can be separated by some distance. You can use ssh forwarding, or VPN or any other sort of "tunnel," to send those commands "across the wire."
The rendering is always done by the client. The server might not even have a graphics-card installed ("headless" servers often don't ...), yet it can run a full GUI session.
By comparison, Windows' GUI system is very-tightly integrated into the server, and a remote-desktop actually sends bitmaps and such from one side to the other. The host is doing all of the graphics, and the remote is simply getting little slices of it.
Both arrangements work, but they work very differently.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.