![](https://seccdn.libravatar.org/avatar/21a84c434500dcff28acdd444df330b2.jpg?s=120&d=mm&r=g)
I posted recently about problems I had with upgrading from SuSE 6.0 to 5.1 and got a few responses primarily regarding issues with KDE. I would like to thank th email followups for setting me straight. I would like to address the inability of YAST to correctly identify key components or applications previously installed in my system and then allow a package to update itself over the existing version. I also am somewhat concerned with the upgrade process wiping out files like /etc/profile and not making copies of them whatsoever. I have found that generating a new .fvwm2rc file has become downright dangerous lately; any changes I make at even a minor level are not kept. As an example, I change knews to slrn and pine to mutt and these changes are not kept. I found that with netscape-communicator 4.04 rpm, that starting it with the -install switch gets rid of module errors I get when starting it by typing netscape alone. Each new .fvwm2rc rewrites this change back to the original. The continuing problems with mislinked libraries are rather perplexing since these were libs I compiled on my own. With programs, I do not understand why SuSE 5.1 upgrade would wipe out my compiled slrn 0943 with its own slrn 0943. I also am a bit puzzled about WABI and the file called /dev/zero (whatever in heck that is). Any enlightenment would be quite appreciated. And Bodo and SuSE list serving administrators... - email problems should be over now. I apologize. We had some dns routing errors here that are now resolved. -- --Michael Perry-- mperry@basin.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e