I’m just tired. On the last post about having Linux at our work, many people that seems to be an IT worker said there have been several issues with Linux that was not easy to manipulate or control like they do with Windows, but I think they just are lazy to find out ways to provide this support. Because Google forces all their workers to use Linux, and they have pretty much control on their OS as any other Windows system.
Linux is a valid system that can be used for work, just as many other companies do.
So my point is, the excuse of “Linux is not ready for workplaces” could be just a lack of knowledge of the IT team and/or a lack of intention to provide to developers the right tools to work.
Is there something I’m missing? Teamviewer is available for Linux and I’ve done remote support with it: https://www.teamviewer.com/en/download/linux/
I…assume it also works as the machine being remoted into?
Teamviewer on Linux works… ish. It doesn’t do Wayland and it’s basically the Windows version of Teamviewer packaged with Wine.
My experience with it hasn’t been very great. Even as a client I’ve run I to Teamviewer having trouble getting connected. Restarting the service (running as root, of course) a couple of times seemed to help but that may have been random luck.
Ir could just be me, but if my experience is anything to go by, it’s not something I would use for a business.
I would probably go with VNC or something else instead of Teamviewer for supporting Linux desktops remotely. Maybe set people up with a pointy-clicky script to do a reverse SSH tunnel to a central host, or do it over a VPN connection.
Getting xvnc to actually see the user desktop and controlling the user’s mouse is kind of a pain to set up, but I suppose it’s better than some proprietary software that works through compatibility layers.
I think X2Go is probably better, though I haven’t used it in a while; I don’t know how well it’s maintained.
Yeah, I’m not sure what the state of the art is these days. Maybe SPICE? I’ve used that to control VMs through tunneled SSH before.
Ah, I see. I only used it once, so it’s not something I do often, but it worked perfectly for me as a client to a Windows computer.