Remote Window Managers
Lots of times it's extremely frustrating or time consuming to run an xterm on a remote host just to fork your programs from that remote machine. Why not just run your window manager there even though you're not on its console? The window manager is just another X application, after all, isn't it?
Fire off your local X server
xinit /usr/bin/xterm -- :1 &
yields a vanilla X session with merely an xterm running - no window manager. Now you need to add permissions to this window session for the remote host. You can tunnel the connection through SSH if your network is insecure but there's a distinct performance hit. If your network is secure, you can just "xhost +remotehost" and spray directly to your X server:
ssh -fY remotehost /usr/bin/wmaker
or spray directly:
ssh -f remotehost /usr/bin/wmaker -display localmachine:1
The first option, if your remote SSH server supports it, will use a locally defined DISPLAY that then gets tunneled to your local side over SSH. The second option allows remotehost to send X data directly to your local display, then runs WindowMaker there but displaying it locally. Now all your desktop actions are done on the remote machine, not locally.
Our special thanks to Bill from Washington state for this tech tip.
|Privacy Is Personal||Jul 02, 2015|
|July 2015 Issue of Linux Journal: Mobile||Jul 01, 2015|
|July 2015 Video Preview||Jul 01, 2015|
|PHP for Non-Developers||Jun 30, 2015|
|A Code Boot Camp for Underprivileged Kids||Jun 30, 2015|
|Comprehensive Identity Management and Audit for Red Hat Enterprise Linux||Jun 29, 2015|
- Physics Analysis Workstation
- Attack of the Drones
- Django Templates
- Secure Server Deployments in Hostile Territory
- PHP for Non-Developers
- Practical Books for the Most Technical People on the Planet
- The AtoMiC Toolkit!
- Take Control of Growing Redis NoSQL Server Clusters
- Comprehensive Identity Management and Audit for Red Hat Enterprise Linux
- Privacy Is Personal