On Fri, Mar 07, 2003 at 02:52:44PM -0500, Bob Paige wrote: > What about running X locally and starting the window manager remotely?
Doable, though I can't tell you offhand how to get the window manager to run remotely, since I don't recall where it's started from. > 1. less sensitive to NIC hiccups; assuming my NIC is being flaky, I > never noticed before when running locally-hosted applications, so I > would think that the connection would be re-established before a TCP > timeout (wouldn't it?) > 2. window manager would present a list of apps installed on the server > (not the client) Both make sense to me. > Of course, the biggest disadvantage is starting the whole thing up > because it would require a manual step to go to connect to the server > and start the window manager, but I might be able to script that. No manual intervention needed. Create an ssh keypair with a null passphrase (so ssh will connect without requiring a password) and replace the standard window manager invokation with `ssh -X server /path/to/windowmanager`. Simple as that. -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
