On Friday 29 September 2006 12:31, Alan Brown wrote: > On Fri, 29 Sep 2006, Kern Sibbald wrote: > > > After having been totally frustrated chasing this kernel crash for the last > > few weeks (I really could not believe that it was not a Bacula bug), I have > > finally found a work around and at the same time, proven that it is a SuSE > > problem. > > One of the reason we dumped SLES on our production machines in favour of > RHEL was that SUSE was consistently shipping with mismatching dynamic and > static library versions - and would not fix it even when notified. > > SuSE may be great for home systems but having endured it (and SuSE's > so-called "support desk") for 4 years, I do not believe it is suitable for > enterprise or business production use.
Well, with the exception of three things, I have found the installation and stability 10x better than Fedora. RHEL stability is exceptional, so I cannot comment, but the SuSE installer is far superior to the RHEL installer. However, I cannot afford to be on RHEL, and at least for the moment, would prefer not to be on one of the "clones". One is the terribly slow speed for Yast2 doing rpm updates. That I have resolved by switching to yumex, which was what I preferred under Fedora anyway. The second problem is that they don't take enough care to make sure that their updates have all dependencies resolved. With Yast it is a catastrophe because of the slowness, with yumex, one just excludes a few updates and away you go. And finally, what is really disturbing me is this kernel oops. It really killed me -- for two weeks I beat tried everything (lots of work) thinking it was a Bacula bug. In the end, I had to "reluctantly" admit it was either a compiler or a kernel bug -- I've now proved it to be a kernel bug -- very frustrating. > > Novell (SuSE's owners) management in the UK even tried to intervene on our > behalf and were completely stonewalled by SuSE. If a company is this > dysfunctional internally, then I don't hold out much hope for getting any > problems fixed at all, let alone in a reasonable timeframe. I suspect that has changed and evolve even more in the future. They seem to be taking it seriously and were quite polite in their response -- them taking it seriously is surely in part due to those of you who quickly responded to my call -- there are now 13 votes for fixing the bug. Thanks :-) If anyone can spare a few minutes to create a login and vote and/or signup for a CC on the bug, please do so. https://bugzilla.novell.com/show_bug.cgi?id=208782 Regards, Kern PS: I'm going to test it against their SuSE 10.2 kernel (to be released in Dec if I remember right) and if it fails, I'll file a "blocker", which will ensure that it is fixed. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
