Linked by Thom Holwerda on Thu 27th Dec 2007 22:41 UTC, submitted by Patrik Buckau
Thread beginning with comment 293492
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2006-02-24
I'm no Debian expert, but I think Debian sticks to version numbers (like for instance Red Hat does) which makes it indeed stable as in "predictable", but then Red Hat does more backporting of packages from newer releases, often to increase its stability.
And sticking with older versions is actually something that I think makes Debian unstable sometimes. A recent example I stumbled upon, was a problem in the OpenISCI initiator: it didn't take me long before I found some bugs that were already solved. Another advantage of the more active backporting that Red Hat does, is that you get to benefit from some new features (like with Xen, being able to run 64-bit next to 32-bit: I'm afraid we'll have to wait for that with Debian for the next stable release? And cyrus 2.3 was released I think just before the freeze of etch, but it still has 2.2 and it seems like it will stay like that. Although during sarge I believe there was an major upgrade from mysql that I was surprised about, that was actually an example where Debian didn't stick to older versions - which is good, but also problematic in this case.
We've had serious problems with kernel images in the past too, problems with (too new) hardware that just were not solved in Debians stock kernels...)
Oh well, that said: I like Debian, I just wished it had the release cycle and freshness/packaging policy of other distributions sometimes. But it serves us really well, for some machines we pick Debian, others get Red Hat (or FreeBSD, or, or...)