I would definately concur with the following, however with our severs, we add one more step.
We *always* download the rpms locally, and do rpm -U to apply any errata or security patches from the Mandrake website. H > > I would stick with the RPM's for enterprise class servers needing anything > near 24/7. While I am not overly confident in Mandrake's update RPM's > (almost toasted my machine when they forgetting to link stuff in the /boot > dir on a kernel update), this still is the best way to go. The main > reasons include: > > Consistency among multiple servers-makes them all work alike and manage > alike > Their team, while imperfect, has a lot more experience building RPM's than > you. > Security updates, when made available would otherwise require you to grab > source and recompile. They've already done that. > > Management of multiple big-time servers is made much more feasible with > consistency. The security updates are almost enough on their own. > > <CHING>$0.02 </CHING> > > > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
