Pages

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:

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.

If you are using modules you need to load these first: modprobe loop;modprobe cryptoloop;modprobe cipher-aes Basically you: losetup -e ...

MooLux is a Live USB Linux distribution based on Slackware that utilizes the KDE desktop environment. MooLux is a portable operating system that can be taken with you containing tools for Internet browsing, email, chat, multimedia, office and software for C, Python, Perl programming tasks.
Send your tips to moodjair@moolux.org