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>
Scott
<[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>
Sent by: cc:
expert-owner@linux-ma Subject: [expert] RPM or source
install
ndrake.com
01/14/2002 09:46 AM
Please respond to
expert
Good news last week as our CEO has given the approval to Linux deployment!
We are going to start replacing several NT servers in the next serveral
months.
I have a question concerning source or rpm install. I am making a
migration plan now and one of the options is to install Apache from source
or to use the RPM's. Now, if I install the RPM version with PHP I must
wait for Mandrake to release updates, correct? What if I installed
Apache, php 4.06 during install and php 4.1.1 is released? I must wait
for the rpm's, correct? I know I can do --nodeps, but these will be
enterprise class systems and need to up 24/7.
Thanks,
-Scott
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
