--=-t/zDTQspN1hYpRtbNjoQ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > # First make sure your workstation allows X connections > # from your server > bob@workstation $ xhost >=20 > # Then connect to your server > bob@workstation $ ssh >=20 > # Tell the server where to send your X gui widgets > bob@server $ export DISPLAY=3D":0.0" >=20 > # become root > bob@server $ su >=20 > # run your gui tool > root@server # red-carpet I don't know if you know this, but I want to mention that in general you don't want to use generic X connections to share data. When you do this you are creating a binary stream between the client and server that is basically plain text. So every key you press gets sent across the network, passwords, what ever. This is the same reason that XDMCP (logging in to a host graphically over the network) is a bad idea. (I can tell stories about sniffing passwords off of hapless sysadmins in college using this... :) While that sounds grim, SSH fixes this problem for you if you allow it to handle X stuff. Basically what SSH will do is set up an encrypted tunnel for the X binary stream to travel across. I use this even on local networks, but some have called me paranoid. Another feature of SSH that helps here is compression. SSH will compress the byte stream so that you applications run a little faster (assuming both machines have the CPU to handle it). Probably a better way to do this is: # Then connect to your server bob@workstation $ ssh -l root # run your gui tool root@server # red-carpet Have fun, Ted --=-t/zDTQspN1hYpRtbNjoQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEABECAAYFAj23jBYACgkQLE335pRPGp0/ggCgnbypJVvLf0iDs0yFKYRIFyHj Ak4AoLEIuc8zthzYSUTMalZKHcXMhNpT =Oi4a -----END PGP SIGNATURE----- --=-t/zDTQspN1hYpRtbNjoQ--