6 ms·
Not sure if you're aware, so I apologise if you are: 1) X11 is already a network aware display system, so it wouldn't take too much work to run remote. 2) SSH
by dijit 7y ago
Not sure if you're aware, so I apologise if you are:
1) X11 is already a network aware display system, so it wouldn't take too much work to run remote.
2) SSH has built-in X11 forwarding with `ssh -X <host>`, when you run commands they will be rendered locally. On OSX this needs an X11 server (XQuartz) to work properly.
3) There are "better" remote desktop solutions like "parsec"[0] which run on Windows and Linux. They offer much lower latency and higher bit-depth. They're designed for games. (obviously this comes at the price of bandwidth).
[0]: https://parsecgaming.com/features/ https://parsecgaming.com/features/
- FullyFunctional 7y agoIsn't RDP more akin to VNC than X11? You can connected and reconnect to existing sessions, something you cannot do with X11 (but can with VNC). I have never heard of Parsec before but it's not immediately obvious that it's an alternative to RDP (Desktop usage)
- paulirwin 7y agoAs far as connecting to existing sessions goes, yes, RDP is closer to VNC to X11. In that respect only though: you can't also simultaneously use the same session locally unlike with VNC. However, as far as the actual implementation goes, RDP is closer to X11 than VNC. VNC is basically a remote frame buffer, akin to streaming video. This makes it very cross platform friendly, but also IMO feels very slow, even on a local network. RDP is closer to X11 in that it sends display directives (AFAIK, please correct me if I'm wrong) so that it can draw them on the client as they would be drawn on the server. Think sending a "draw button" command rather than sending an image of pixels that are how the button would be rendered. This, combined with compression, helps make RDP feel very fast compared to VNC, and can be used very well even over the internet, unlike X11. I connect to RDP servers in Azure all the time and sometimes forget I'm not working locally, while with VNC you're always aware that it's not as performant. I really wish there was something like RDP as a server for Linux. (OP seems to be a client AFAICT?) Given Microsoft's recent investment in Linux, maybe this will happen soon?
- vel0city 7y agoRDP is definitely closer to the framebuffer style rendering than sending explicit draw commands. Newer versions of the RDP protocol have made this very efficient so it only ends up having to transmit compressed data of the changes per frame, but overall its still more of a video-like stream than true local rendering a la X11.
- paulirwin 7y agoThanks! I guess I had been misinformed on that. I was also probably thinking of the RemoteFX stuff, like GPU and media redirection: https://en.wikipedia.org/wiki/RemoteFX https://en.wikipedia.org/wiki/RemoteFX
- rlkf 7y agoNo, you are not misinformed. Both RDP and X11 can send both drawing commands and bitmaps. However, as /u/moonchild says, only older programs seems to be sending drawing commands directly. Newer programs want to be fancy and uses toolkits that do their own drawing to have visual effects. (Witness the speed of Emacs vs. editor-du-jour)
- Const-me 7y ago> Newer programs want to be fancy and uses toolkits that do their own drawing to have visual effects Good toolkits like WPF and UWP implement their own drawing by utilizing Direct3D. These two are using DX 9.0c and D3D 11.0 respectively, and both are supported in RDP protocol. If you connect to a remote PC and run dxdiag.exe there, you’ll see 3D acceleration is supported, you’ll also see the GPU driver got replaced with completely different one, it’s no longer Intel, Nvidia or AMD, but the one from MS. This has interesting consequences, e.g. all D3D APIs which move data from system RAM or VRAM or back now become network calls, the system RAM is on the server, VRAM is on the client. P.S. Modern web browsers use Direct2D and DirectWrite to render stuff on Windows, there’s D3D 11 underneath, i.e. RDP remote rendering is fully supported for browsers and Electron apps.
- 7y ago
- loeg 7y agoX11 is network aware, in that is theoretically possible to speak the protocol over a network. However, anyone considering it should be aware that it is (1) extremely chatty, (2) extremely synchronous, and (3) extremely latency sensitive. It only works well on fast local networks. SSH certainly doesn't make it any faster. In contrast, RDP and VNC type protocols are screen-replicating designs more suited to higher latency connections. Finally, if you're using RDP, I'd suggest Remmina as an client. It's fantastic.
- hjkgfdfgh 7y agoTo pile on against X11 over ssh, forwarding on a modern Linux workstation is spectacularly painful. I recently needed to forward a lightweight gtk app from one workstation to another over 10gbe and a single switch hop. With ssh and X forwarding, my local gnome constantly threw up modal dialogs that the forwarded window was unresponsive, forcing me to keep clicking "Wait" to dismiss the modal, then quickly interact with the forwarded window before the next "unresponsive" modal popped up.
- inetknght 7y agoForwarding Firefox over X11 _sometimes_ works. Sometimes Firefox on the remote machine will try to join the session of your local firefox -- but fail and then complain that there's Firefox already running. Adding `--new-instance` helps if Firefox is running in a container and X11 socket file is forwarded to the container but it doesn't seem to help if X11 is forwarded over SSH.
- jabl 7y agoTry '-no-remote'. Or was that '--no-remote'? Anyway, that's what I've used for years and years when needing to run firefox over ssh X forwarding.
- inetknght 7y agoFirefox is running on the remote, connected to a different X11 session. It is not running on the local. When I use `firefox --new-session --no-remote` on the remote, I see a dialog pop up on my local machine stating Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.
- brimstedt 7y agoX11 works remote, but to my knowledge only to start new applications. Connect to an existing session and just "continue where you were" is not easy though there might be unmaintained solutions. If you use ssh forwarding and for some reason gets disconnected, the application dies. I'd love for you to tell me I'm wrong :-) The way rdp works on windows is the only thing where I think windows is superior. Vnc, TeamViewer and similar are not remotely close and they will leave your remote screen open for anyone to see.
- aksss 7y agoAlthough with teamviewer (maybe others) I think a display driver install can black out the far-end screen.
- alexhutcheson 7y agoXpra is what you want for this: http://xpra.org/ http://xpra.org/
- dhd415 7y agoI was hopeful that Xpra would provide reconnectable remote sessions for me on my Linux workstations but I found it pretty difficult to configure with poor documentation. If there are any better installation guides out there, I'd appreciate a pointer to them.
- GranPC 7y agoParsec for Linux is only a client; you can't share a Linux desktop using Parsec.
- tssva 7y agoAlong with better performance and reliability than X11 RDP allows redirection of sound, folders, USB devices, and can present a virtual GPU which allows access to the physical GPU of the remote end.
- makkesk8 7y agoparsec does not support multiple monitors which is a deal breaker in many use cases, so far windows rdp is the best free solution for at least windows -> windows remoting.