On Thu, 26 Aug 2004 suse@rio.vg wrote:
Quoting "b@rry.co.za" :
A mistake has happened, been recognised, and guaranteed will be analysed to try and prevent the same mistake from happening again.
Most kids fall off their bucycle at some point. They learn at that point that turning in the sand at high speed is a bad idea and don't do it again (unless the truck they are trying to avoid takes their eyes off the road for a moment).
So all in all, SuSE keep it up, everyone else, shut up, I am getting to see this thread as SPAM in my security mailbox and am sure that while I am only adding to the problem now, hopefully you will all grow up and spend more time fixing your problems than whining because someone else isn't.
Here here!
Perhaps you haven't had any problems at all, I don't know. But let's take an example that's been biting me: tripwire.
I almost made a comment, like the one i'm about to make, months ago but I decided to drop it and not create flames. But here's my opinion. Suse doesn't make tripwire, they don't maintain tripwire, they don't do anything except add tripwire to their distro. They add, best guess, over 3000 different rpm packages to their distro. I don't find it terrible that each and every one of those aren't fully quality tested and that they don't work the first time. Sure, they shouldn't include it if they didn't test it, but really who is going to sit there and test each and every package. Is there anyone here who test each and every package distributed with Suse? I think not. So what, a package doesn't work, go get the source and compile/install it yourself. That's what Linux is all about, you don't have to use the proprietary vendors stuff ALL the time. It doesn't really bother me that a package doesn't work, if I really want that package then I'll find other means to obtain it. BB