Another question that needs to be asked is what operating system is running on your workstation. If it's windows, then you need to have some sort of X-Windows server installed and running, before any of this will work.
If it is a Linux workstation, then to make what you did work, you'd also have to do the command xhost +s390_ip. Otherwise, it won't let outside clients open windows on your X-Windows server. But as was pointed out, if you're doing X tunneling with ssh, then this wouldn't be necessary. Yet another question: What userid do you log into via the ssh command? If you are installing via root, that is the userid you need to log in with; otherwise, if you have to do an su - after logging in, the ssh tunneling is lost. At that point, you WOULD have to set your own $DISPLAY, and be sure to do the xhost + on the target machine. -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Monday, April 25, 2005 6:47 PM To: [email protected] Subject: Re: export DISPLAY If you're using the -X option on the SSH command, and if the SSH server on the Linux/390 system has "X11Forwarding yes" set, then you should not need to do _anything_ with the DISPLAY environment variable. It should already be set to something like "localhost:10.0," which means that SSH is doing its job of tunneling the X traffic back over the encrypted link. So, do the "ssh -X" command, and then as soon as you're logged in, do an "echo $DISPLAY" to see if it is set or not. If not, examine the /etc/ssh/sshd_config file to see what value it has for X11Forwarding. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim Sibley Sent: Monday, April 25, 2005 4:42 PM To: [email protected] Subject: export DISPLAY I'm learning now to put DB2 and WAS on, both java installs. Before issuing the setup commands I set up as follows: fm workstation ws-ip, I issue ssh -X s390-ip .... .... fm s390-ip, I issue export DISPLAY=ws-ip:0.0 The work station is an i386 SLES9 under KDE. When YaST2 is issued on the s390, it uses GUI on the WS. When I try the installs for DB2 and WAS, they fail, saying the export is not set up correctly. Does anyone know the magical combination to get GUI to work (other than use console install mode). Jim Sibley "Computers are useless.They can only give answers." Pablo Picasso (The NSHO's expressed here represents no-one but myself). __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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
