Michael I am getting to the same point as you are. I just can't use SuSE for anything, NOW, except a test bed. I could not recommend this version for production. As you are finding an upgrade, I am finding that even a new installation has too many unanswered questions. I find that there are too many things that are going wrong. I could not compile mutt with slang, why, the only slang library installed is aout! This on an ELF system. Yes, I could go and compile slang up myself (I've done it for Slackware) but why should I have to? My sendmail has quit working after using yast for various package loads. Why, well the sendmail.cf had changed but I still can't find out why. I enabled samba on Suse, then copied my working samba.conf from my Slackware working network. SuSE samba won't let the Win95 systems log in with out a password. Funny that, I have it configured for NO passwords. I switch back to Slackware and the Win95 systems log is fine. This might get better but too many things don't work that way "I" think they should. The re-boot thing really bugs me. Maybe I should disable SuSE from doing my sys admin. Then maybe I should mot use Yast. Then I wonder why I bought this anyway! To give credit where due. I do like the SuSE ET600 server better then the Xfree server. Hope you get your problems worked out. I will monitor the list but I will not be using SuSE as a production enviroment quite yet. I have to get back to work, can't spend so much time working out SuSE "funny" problems right now. Good Luck. Wayne Subject: [S.u.S.E. Linux] EArlier problems - some solutions; still questions abound Date: Tue, Feb 03, 1998 at 07:25:46PM -0800 In reply to:Michael Perry Quoting Michael Perry (mperry@basin.com):
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
.
-- -- Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e