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:
Tunneled SSH:
ssh -fY remotehost /usr/bin/wmaker
or spray directly:
xhost +remotehost
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.
__________________________
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- RSS Feeds
- Validate an E-Mail Address with PHP, the Right Way
- Readers' Choice Awards
- Tech Tip: Really Simple HTTP Server with Python
- DynDNS
33 min 25 sec ago - Reply to comment | Linux Journal
1 hour 5 min ago - All the articles you talked
3 hours 29 min ago - All the articles you talked
3 hours 32 min ago - All the articles you talked
3 hours 33 min ago - myip
7 hours 58 min ago - Keeping track of IP address
9 hours 49 min ago - Roll your own dynamic dns
15 hours 2 min ago - Please correct the URL for Salt Stack's web site
18 hours 14 min ago - Android is Linux -- why no better inter-operation
20 hours 29 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
"Extremely frustrating"?
It seems like a lot of work - are you guys running Windows on desktop machines?
This is what I do - I find it works a charm; but then I run Linux on my desktop:
Open a local xterm or similar. Log on to the remote machine with 'ssh -X user@remote'. The '-X' means that X programs on the remote machine are displayed on your local desktop. No need for 'export DISPLAY' or 'xhost +'. You have to set up the configuration files on you local as well as remote machine, though (they are in /etc/ssh).
Couldn't make it run.
Its a pity that it does not work for me because I am needing desperately such a kind of feature for my system. I Installed wmaker in the remote host, but it didn't work. It says:
/usr/bin/wmaker fatal error: could not open display "CompUBUNTU:1"
where "compUBUNTU" is the name of my local machine which, by the way, runs a UBUNTU Hardy distro, while the remote host is running Fedora 8. It shouldn't be a network issue because the two computers are connected to the same LAN with no particular filters or firewalls between them.
Any suggestion?
And if you dislike Window Maker?
Will this tech tip still work with a window manager that doesn't have a "-display" option, such as xmonad?
Sometimes the delete key serves best.
Used to do this
I used to do this, holy moley, 18 years ago. We had a lab full of Mac II's running Apple's A/UX. The machines struggled to run much besides the X server. Since I was already running most everything else remotely, one day I fired up TWM remotely and it worked reasonably well. So I hacked up my .xinitc so that when I started X on one of the A/UX boxes, it ran TWM and everything else from our 10 processor Sequent box.