Thanks to all who responded. And I apologize for my client/server confusion. It does take a different meaning when talking about X .
I do want to run the x-server and the window manager on the intel box to avoid the cpu hit on the mainframe. The missing piece that I was looking for is: startx -- :1 This starts a 2nd kde desktop on the intel. Go to it : ctl-alt-f8 ssh -X to the mainframe and startkde on the mainframe It now all works fine. All my mainframe stuff is now on the 2nd desktop. (I do had to kill the 2nd "kicker" prior to the ssh, but I think this is a kicker bug) Ismael -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Meanor, Tim Sent: Friday, February 18, 2005 12:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: KDE Try running Xnest on your Linux desktop (it's in the XFree86-Xnest package on Red Hat, not sure what the equivalent is on SLES). It's basically an xserver that is nested within another xserver, and it just appears as another window on your intel linux desktop. You could run your mainframe Linux KDE desktop within Xnest. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ifurung, [EMAIL PROTECTED] Sent: Friday, February 18, 2005 1:47 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: KDE OK, here's the process that I've tried: 1) Using desktop intel linux, boots up and login in kde environment. 2) start a "konsole" shell 3) ssh -X mainframeLinux 4) while login to mainframeLinux, I can run things like, xeyes, xclock, yast2, konqueror successfully with no problems. I know that the x-server runs OK. 5) run "kde". Corrupts the window and kills kicker but continues to run somewhat. ---------------------- What I'd really want to do is run the mainframe kde client on a separate window. Ismael -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Friday, February 18, 2005 10:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: KDE If you make sure that you forward X11 traffic through ssh, then there will be a DISPLAY variable set to a local socket the the authentication is taken care of as well. That's probably simpler than fiddle with xhost stuff. Rob -- Rob van der Heij rvdheij @ gmail.com ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
