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.

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.

AB

-------------------------------------------------------------------------
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

Reply via email to