Linked by Eugenia Loli on Wed 8th Oct 2008 20:12 UTC
Thread beginning with comment 333103
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.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links




Member since:
2006-01-28
The dependencies on a modern linux system are so complex that a human check is not enough. The packages have to be built carefully and with an awareness of how they fit with the rest of the system and complete binary rebuilds of the entire system are needed to make sure that the system remains in a consistent state.
Why do you think that Suse keeps their Build Service around? You can have a complete distribution rebuilt when you introduce a change into a package so that if there are any potential repercussions throughout the whole software stack, they will be caught.
No human "checker" can do that. This is not to say that a good admin should not keep a very watchful eye on a server and a good log of what he installs and why. But there is a role for automated dependency checking.
The mindset that everything an admin's head is the only sound repository for all knowledge about a server is a recipe for disaster at a datacenter.
The needs of a small home server cannot be compared to the needs of larger organizations.