On Fri, Sep 23, 2011 at 10:39 PM, Rajagopal Swaminathan <raju.rajs...@gmail.com> wrote:
> I can see that that Shri Rahul Sundaram has aptly answered to this query. If the 10-year support cycle interests you, RHEL is not the lone provider; SUSE Linux Enterprise also provides a comparable 10-year support life-cycle. http://support.novell.com/inc/lifecycle/linux.html http://www.redhat.com/rhel/server/extended_lifecycle_support/ (quick illustration: http://dag.wieers.com/blog/sites/dag.wieers.com.blog/files/rhel-business-continuity.png ) > The point is, a production environment runs long after its deployment. > I know of clipper and foxpro production systems running to date (and > fate) to this day. The original poster was referring to the LAMP stack. I can understand organizations holding on to their old proprietary solutions for ages (like IE6 and Active-X based Intranet apps). I can even understand people not upgrading their email servers as SMTP, POP or IMAP may not see radical changes. But why should the dynamically changing nature of *Open* Web technologies be limited by stale deployments? I for one, would really not want to limit myself to an age old MySQL server, when a newer release would greatly enhance the scalability of my web application. Nor would I want to miss a significant upgrade to PHP features in the name of maintaining stability. Just compare how the web was 5 years ago and how much it has evolved now. If the enterprise wants a 10-year locked-down deployment even for an Open Web Apps stack, that makes me really sad. I was under the impression that only proprietary, commercial products lock down their customers and make upgrades a costly affair. Regards, Kumaraguru _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc