I'm sure this has been discussed to some extent here, nonetheless, I would like to get an idea of where SuSE are going with YaST. There are some features which I really liked in YaST which are missing in YaST2. The biggest thing I find lacking is the ability to determine what is currently installed on my system while browsing the updates. For example, if I go to the KDE update directory on the SuSE ftp site, I would like to know which applications are already on my system. We used to be able to do this with YaST. Another thing I find a bit disorienting is the way the contents of the /etc/rc.config have been moved into /etc/sysconfig. This certainly has its good points. It is easier to find a particular configuration item this way. I suspect it also lays the groundwork for bigger and better things to come. One of these is, I hope, a return to providing a mask over these configuration items. Now it seems necessary to start processes such as Apache by explicitly modifying the runlevels. That's fine, if that's what SuSE intend for us to do. The interface we have for that is likewise very nice. The difficult part seems to be figuring out what SuSE expect us to do. That is, *should* I be using the runlevel editor for starting services automatically? Is there a paradigm shift in YaST? Am I just having trouble adjusting to a new and better way of doing things, or are there really shortcomings in the current (SuSE 8). I very much like the new look and feel of the GUI based YaST2. The terminal based version, well....(how 'bout using tab to move the focus?) What do others think of YaST verses YaST2? Please note, this is NOT an exercise in SuSE bashing. In a world where the integrity of corporations seem to be vanishing faster than the forests, I can honestly say my trust in SuSE is rock solid. This is the only operating system I chose to use. Any other that I use is due to circumstances of employment. Steven