First of all, let me say I support the decision to transition fully to yast2. Some of us old dinosaurs need a bit more of a push to adopt the new, and I'm getting more and more comfortable with it by the minute. For the past few days, I've been working on installing 8.0 on a rack-mounted server. To save my feet and back, I've preferred to use ssh and sit more comfortably at my desk. While yast2 isn't yet as intuitive as yast1 was for me, I'm finding it quite usable in the ncurses mode. I do wish, however, that the 'back-tab' function was implemented. All too often, I hit the tab key once too many, and then have to cycle all over the page again to get where I want to be. Today, once I got all the critical functions going, I decided to play, and see if I could make it prettier. I've heard about running X applications over an SSH link, so I thought I'd give it a try, and see if the performance was acceptable over a 10Mbit ethernet. However, I haven't been able to get it working - I still get the ncurses version. Here's what I'm doing: local> ssh -X serverhost <login> serverhost> echo $DISPLAY serverhost:10.0 serverhost> sux - password: ******* serverhost# echo $DISPLAY serverhost:10.0 serverhost# yast ...at this point I get the now-familiar yast2 ncurses opening screen. ...I also tried it starting with `ssh -l root -X serverhost` and got the same results. I remember from an earlier thread that it's supposed to use the X display any time it finds the $DISPLAY variable set. What else am I missing? My client workstation is running SuSE 7.2, kept up to date with YOU and yast1. I'm using openssh-2.9p1-25. Rick Green