> On SLES7 I am able to SSH to the Linux instance. When I enter > yast2 I get > the following: > > lnxsftwm:~ # yast2 > Xlib: extension "RENDER" missing on display "lnxsftwm:10.0" > > I copied the xdm init scripts to rc3.d from rc5.d
DON'T DO THAT! There is a deliberate difference between runlevel 3 and runlevel 5, and the X stuff is in runlevel 5 for a reason. 390 linux doesn't go there because it doesn't have any of the necessary hardware. You're also confusing the xdm solicitor with running an X server. Starting an X server on a 390 is a pointless exercise -- there's no framebuffer to talk to, so it won't work anyway. Also, xdm does not require a running X server on the host, it requires a X server on the client and a XDMCP compatible client on the workstation AND clear IP connectivity between the two. xdm on the host responds to XDMCP requests to indicate that it is capable of managing the client, so you need to configure xdm properly. > When the Linux instance scomes up I can see the xdm process > using top but > then it goes away. Under SLES8 I see the xdm process and it > stays running. > > I must be missing something in setting up xdm for ssh support ? some > environment variables not being set ? SSH doesn't get involved for xdm sessions. SSH can only set the DISPLAY variable after login, which is useless to you for XDM sessions (XDM happens before login). If you want to use XDM, you need to somehow route or bridge between the client and the server, ie you need a VPN solution. > Any thoughts or suggestions ? If you have to use SSH to get in, look at the startx script rather than XDM. Or use VNC. -- db
