How about just using RPM to install RPM's until SuSE can get a module to again do this via ftp and the like? YaST1 just ran 'rpm -Uvh or rpm -ivh' with --nodeps --force to install them and then it ran SuSEconfig. Are we so terribly frightened to do something from an xterm/console? I think that they get it now. This threat has been beaten like a dead horse in the desert. ;) Just use ncftp or gftp..put the RPM's that you download into /tmp as I do and then do this... Upgrades: rpm -Uvh --nodeps --force *.rpm New Installs: rpm -ivh --nodeps --force *.rpm If you want to find out the dependencies of a pkg then leave out the --nodeps and RPM WILL tell you what you need to have the package installed. If you have what it's bitching about then use the two arguements above and it will work fine. You should then run SuSEconfig which will update everything as it normally would. I'm missing YaST1 as well...but damn they will get a work around in place soon. 8.0 is a major change for SuSE in how things are layed out and YaST1 wasn't capable of handling these changes and they didn't have the man power to code new functions in to it. They decided to focus on YaST2. If ya'll wanna bitch about something bitch to feedback@suse.de(com) and get them to support apt4rpm..this would be the best solution. :) Cheers! And don't bother flaming me about this .. because I've just told how I do things most of the time. But then again I'm not afraid of the CLI. ;) Regards, -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--