> What I'd really want to do is run the mainframe kde client on > a separate > window.
You're confusing client, server and window manager. In X terms, the X *server* runs on the machine with the keyboard and mouse, as does the window manager. Clients run *anywhere* and point their DISPLAY env variable back to the machine running the server and window manager for display. If you want a separate screen for "mainframe" stuff, KDE creates separate desktops that can be addressed by X clients as server:0.1, server:0.2, etc where server is the machine you are sitting in front of. The default 'kde' script is intended to be run on the machine where the X *server* is running, as it starts the X server and the window-manager. You *really* don't want to run your window manager remotely. *REALLY*, you don't. People will be very upset with you if you do this. Also, your mainframe has no GUI display, so running an X server on a remote system is kind of pointless. What you want to do is modify your Intel KDE configuration to start the individual client programs via ssh to the remote system. That way the default kde startup script can do it's thing with the framebuffer and run the window manager locally on the Intel box, and you run the client applications on the remote machines. If you REALLY want to have a remote desktop and waste the 390 cycles on it, install VNC on your mainframe linux systems and install vncviewer on your Intel box. That will give you a desktop running on the mainframe inside a window on your Intel box (albeit at a hefty cost in CPU and network cycles). -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
