Ira Abramov wrote:

Quoting Shlomi Fish, from the post of Sun, 17 Nov:

That is actually a good thing for servers. It means that security
upgrades are much less likely to break something, which in turn means
that you are much more confident applying them. The only problem I am
aware of is false positives when doing vulnerability scans of the machine.

I don't think it is a good thing, because these patches are hard to
maintain separately, and often the maintainer of the package cannot
maintain all previous versions.


Shlomi, with all due respect, your system administration experiance is
not as rich and long as Shachar's and mine. we both see the way that
Debian does this as the preferable one, and respect very much their
brave decision to do the hard thing (backport fixes) rather than taking
risks with new versions.

Personally, I don't like to say stuff like "I am older/more experienced/have a bigger dick than you do, so you should listen to me". If I cannot back my experience with self maintaining reasons, than what good is it?

I personally can't go bac, and Shachar's recent brush with
MDK sent him looking for Debian again :)

While factually true, I would like to point out that it was a brush with MDK 9.0, and some of the reasons for going back were bugs. It's just that if I need to work really hard to find what bug in the locale generation code prevents me from getting Hebrew characters in Wine, and therefor stops me from doing open source development, I rather switch back to something I know. I also had serious bugs with the supermounts, which caused me to unmount and then manually mount whenever I wanted to run something off a CD.

What I am trying to say is that I didn't switch back in a hurry because of something fundemental, but because of x.0 release bugs.

My experience with the software update tool, however, has been REALLY bad. It took it over an hour(!!!!!) to add a new source to the list (modifying a text file+ apt-get update on debian - 2 minutes top), and I had little to no control over what was updated.

Shachar


Reply via email to