10:09 AM - Windows vs Linux: Is the study right?
I just read an interesting blog entry on zdnet today. The author critiqued the recent study proving windows was more reliable than linux.
http://blogs.zdnet.com/Murphy/?p=473=rss&tag=feed&subj=zdblog
What i found interesting is that the author points out a real linux admin would test patches on a workstation and only install what they needed. I don't think many linux sys admins actually do that. Really its a good idea on linux and windows servers. Why enable DNS if you only need IIS or apache? Another issue is the study used Novell's suse linux. Novell products are not known for their stability. Only novell zealots from the 80s think otherwise. Just send emails to everyone in a company or large college campus through novell and watch the buffer overflow take out winodws. (groupwise 6.5 sp2) Thats novell quality. Arguably windows is at fault as well since it allowed the attack. If you try to run novell products with microsoft's buffer overflow protection on they crash! They must overflow buffers to work! Back to the argument at hand. Why didn't they use redhat enterprise linux ES or AS? That is on level ground. The study used sql server so why didn't they use oracle on the linux side. I don't see a war of enterprise products here. I see mysql which is not a real database prior to version 5 and apache/php. Essentially they took on LAMP which is NOT a secure, reliable choice. Using linux is one thing, but choosing a kitchen sink distro and running php is NOT a smart thing to do. PHP is as bad as ASP running on NT4 in windows in terms of security. In addition, you get broken api's from the PHP people that did not happen in ASP's glory period. .NET was the first breakage and it was an entirely different architecture. PHP pretends to be compatible.
I wish someone would do a real impartial study and include several operating systems. Lets see linux vs solaris vs freebsd vs windows. Many people use these four as webservers. Also use several distros for linux and try out java solutions, oracle, ibm db2, mysql, postgresql, php, perl, and ruby on rails. Lets see what the roadmap really looks like.
http://blogs.zdnet.com/Murphy/?p=473=rss&tag=feed&subj=zdblog
What i found interesting is that the author points out a real linux admin would test patches on a workstation and only install what they needed. I don't think many linux sys admins actually do that. Really its a good idea on linux and windows servers. Why enable DNS if you only need IIS or apache? Another issue is the study used Novell's suse linux. Novell products are not known for their stability. Only novell zealots from the 80s think otherwise. Just send emails to everyone in a company or large college campus through novell and watch the buffer overflow take out winodws. (groupwise 6.5 sp2) Thats novell quality. Arguably windows is at fault as well since it allowed the attack. If you try to run novell products with microsoft's buffer overflow protection on they crash! They must overflow buffers to work! Back to the argument at hand. Why didn't they use redhat enterprise linux ES or AS? That is on level ground. The study used sql server so why didn't they use oracle on the linux side. I don't see a war of enterprise products here. I see mysql which is not a real database prior to version 5 and apache/php. Essentially they took on LAMP which is NOT a secure, reliable choice. Using linux is one thing, but choosing a kitchen sink distro and running php is NOT a smart thing to do. PHP is as bad as ASP running on NT4 in windows in terms of security. In addition, you get broken api's from the PHP people that did not happen in ASP's glory period. .NET was the first breakage and it was an entirely different architecture. PHP pretends to be compatible.
I wish someone would do a real impartial study and include several operating systems. Lets see linux vs solaris vs freebsd vs windows. Many people use these four as webservers. Also use several distros for linux and try out java solutions, oracle, ibm db2, mysql, postgresql, php, perl, and ruby on rails. Lets see what the roadmap really looks like.
location: Home
music: - -