Slashdot Mirror


Microsoft Claims Firms 'Hitting a Wall' With Linux

maxifez writes writes to tell us that Microsoft has released yet another independent study downplaying the viability of Linux at the enterprise level. The study claims that Windows is "more consistent, predictable, and easier to manage than Linux." From the article: "The study, commissioned by the software giant from Security Innovation, a provider of application security services, claimed that Linux administrators took 68 per cent longer to implement new business requirements than their Windows counterparts." Vnunet.com has also provided a PDF of the original report.

20 of 717 comments (clear)

  1. Translation by suso · · Score: 5, Funny

    Here is a translation from babblefish for those that don't read bullshit.

    More consistent: It crashes the same way every time I press the start button.
    Predictable: It will crash at least once a week
    Easy to manage: There aren't any extra settings in the windows to set that confuse people.

    With Linux, they couldn't figure out what they needed to press to make it crash and couldn't determine out when it would crash.

  2. Nice to know by nizo · · Score: 5, Interesting
    Microsoft products are easier to manage than Linux? On the Linux side, I simply rsync software to all our of workstations. I can even upgrade software people are using right at that moment (like rsyncing the newest thunderbird to /usr/local/thunderbird-1.0.7 while they use the thunderbird in /usr/local/thunderbird-1.0.6, and then moving the /usr/local/bin/thunderbird symbolic link to point to the new version). On the windows side, I wander around bugging people to take an early lunch or whatever while I install/upgrade software on their machine.

    Also I am pleased to notice that the "independant company" that spewed out this "commissioned report" (see the microsoft page) lists Microsoft on their partners page, and from what I can tell no one who has even heard of Linux (with the exception of HP). Since it looks like their business depends on selling enhanced security products, I can see why they wouldn't be too keen on having people show an interest in Linux.


    Security Innovation designed this study to be repeatable, and we believe that the results are consistent with what customers are experiencing in the real world.


    And if I wander over and look at my main Linux file server, I see an uptime of 125 days (it had over a year uptime before I physically had to move the server to a different location). During that time the server's files were available 24/7 with absolutely zero problems. Needless to say we have had way fewer problems with the new Linux server; the old Microsoft server crashed or had to be rebooted on a regular basis; the people before me actually had a planned "weekly reboot every Friday evening". When it came time to replace the Microsoft server, Microsoft didn't fare so well, especially when it came time to pay big piles of $$$ to upgrade it: basically we could have bought two linux file servers for the cost of the Microsoft software upgrade costs alone. Hows that for a real-world example?

    1. Re:Nice to know by swillden · · Score: 5, Insightful

      On the Linux side, I simply rsync software to all our of workstations. I can even upgrade software people are using right at that moment (like rsyncing the newest thunderbird to /usr/local/thunderbird-1.0.7 while they use the thunderbird in /usr/local/thunderbird-1.0.6, and then moving the /usr/local/bin/thunderbird symbolic link to point to the new version). On the windows side, I wander around bugging people to take an early lunch or whatever while I install/upgrade software on their machine.

      There are plenty of ways in which Unix-style systems are easier to administer than Windows boxes, but this is not one of them. Windows actually has quite decent remote administration tools these days, including a fairly nice infrastructure for performing remote installations. Assuming you add some third party components (or are installing to a server with Terminal Services), ad-hoc remote access is also quite good.

      I'm a big fan of Linux (I have seven computers at home; six run Linux, one runs OS X, no Windows, not even a dual-boot), and I'd probably drive a bus before I'd work as a full-time Windows sysadmin, but even I can't let this sort of FUD pass.

      I suggest that you learn Windows first, then rant about it. You'll still have plenty to rant about, but you won't look like an idiot doing it.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    2. Re:Nice to know by Anonymous Coward · · Score: 5, Funny
      Windows actually has quite decent remote administration tools these days, including a fairly nice infrastructure for performing remote installations.

      This is true. I remotely administer several Windows machines owned by people I've never met. The Windows infrastructure makes it trivial to remotely install FTP servers that I use to share Warez.

    3. Re:Nice to know by swillden · · Score: 5, Informative

      The reason Windows locks an executable file that is in-use is that it uses it as a kind of mini-swap file. If you need to swap part of that binary's code out to disk, windows doesn't - it just forgets it. If it needs that code back in memory, it reads it directly from the file on disk.

      All modern Unix-type systems, including Linux, do the same thing. Yes, that means you can have a situation where:

      1. Program 'foo' is executed.
      2. Program 'foo' is swapped out (or perhaps just never loaded -- application code is paged in on-demand, so if there are big parts that were never executed, they were never loaded).
      3. Program 'foo' is deleted, while the process is still running.
      4. The running process needs to page in a portion of the deleted file.

      What happens? Nothing much. It works just fine. How? Because when I said the program was "deleted" in step three, I wasn't being precise. What really happened was that the program was "unlinked". That removes the directory entry and makes it so no process can create a new reference to the file. But any running processes already have a reference to the file, and the actual file stays in existence until all references (both filesystem references and process references) to it go away.

      This holds true for all files, too, not just executables. For example, it's not uncommon for me to start a download then, while the download is running, decide I don't like where it's being written. No problem. I just move it. As long as I'm not moving it to a different file system, the download process doesn't care, because it isn't writing to "/home/shawn/foo.tar.gz", it's writing to "the file handle referencing inode 274327". It doesn't matter a bit if that inode happens to get relinked into a different part of the file system.

      No, there's no excuse for this particular bit of Windows braindamage. The Unix solution is better in every way.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  3. Warning: possible incongruity detected! by Trelane · · Score: 5, Insightful
    "We invite other vendors, including Novell, IBM and Red Hat, to repeat their own independent analysis based on Security Innovation's methodology."
    Umm, is not "their own independent analysis" rather oxymoronic?
    --

    --
    Given enough personal experience, all stereotypes are shallow.
  4. It's all about the criteria. by khasim · · Score: 5, Informative

    The key, as always with these "studies", is to find the portion where it deviates from Reality. That is, where it uses some strange definition or where the sysadmins choose some bizarre action.

    In this "study", that step into UnReality begins where all systems are required to stay on the same time-line for upgrades.

    This means that what would otherwise be a normal upgrade from SLES 8 to SLES 9 instead becomes a strange mix of back-porting patches from SLES 9 to SLES 8. In other examples, the sysadmins are downloading code from the glibc and mysql sites and applying it to those server WITHOUT TESTING. So, over time, the SLES systems become unstable.

    Meanwhile, no non-Microsoft supplied code is applied to the Windows boxes.

    Of course, the one who commissions the "study" gets to choose the criteria ...

  5. In other news.... by gmuslera · · Score: 5, Funny

    ... an independent study commisioned by the Vatican demostrates that God exist.

  6. No suprises! by MoogMan · · Score: 5, Funny

    $someone_influenced_by_microsoft claimed that Linux administrators took 68 per cent longer to implement new business requirements than their Windows counterparts.

    Well, I'm not suprised - They're probably busy reading slashdot half of the time.

  7. My servers . . . by milkmood · · Score: 5, Interesting

    According to Netcraft:

    My Websites Hosted on Linux:
    Last Reboot: 468 days
    Last Reboot: 331 days
    Last Reboot: 664 days

    Other of My Websites Hosted on Windows:
    Last Reboot: 3 days
    Last Reboot: 9 days
    Last Reboot: 11 days

    Customers wanting to switch from Windows to Linux: 3

    99.999% Uptime and 50% happy customers: Priceless

    CP

  8. 98% of MSFT Funded Studies Favor MSFT! by HangingChad · · Score: 5, Funny
    This headline just in from the really, really obvious department.

    How pathetic is it when the only people who say nice things about you are the people you PAY to say nice things about you? That's like paying people to be your friend.

    MSFT has the best friends money can buy.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  9. oh yes... by Tom · · Score: 5, Funny

    Linux administrators took 68 per cent longer to implement new business requirements than their Windows counterparts.

    They forgot to mention that 67.3% of the windos counterparts did not solve the problem at all because they did not know of a vendor who had the software available, and those were not included in the statistics. Also, 23.1% of the windos projects were ten times over budget. 17.5% of the windos projects were fast, but in violation of on average 7 EULAs and 3 other license agreements. 55% of the Linux projects were slowed down by the requirement that no Free or Open Source software could be used, while 15.8% were limited by the requirement that no non-microsoft software could be employed, and Wine was specifically disallowed. Also, 97.5% of statistics are made up on the spot, including 87.3% of those who are conducted by so-called "independent institutes" for lots of money. Finally, 99.87% of studies paid for by someone surprisingly reveal exactly what the customer asked for.

    --
    Assorted stuff I do sometimes: Lemuria.org
  10. Re:speed by sedyn · · Score: 5, Funny

    "Most IT guys would rather it take longer to set up, but run smoothly with low maintenance, than to have an easy setup and lots of maintenance."

    Nah, most IT people would rather have jobs. Windows will keep the administrators going for years to come. Thanks windows, keep up the bad work!

    --
    Am I open minded towards open source, or closed minded towards closed source?
  11. No, THIS is the babelfish translation: by Ozymand+E.+Us · · Score: 5, Funny

    More consistent: it does, start button I press, same way crash.
    Predictable: A week crash will once it at least.
    Easy to manage: Extra Windows settings to confuse people it will, arent there?

  12. Maybe its time for a change... by dbolger · · Score: 5, Funny

    I've been using Fedora for a long time now, but this report has given me some doubts. In the interests of fairness, I should probably give this "Windows" a go. Sourceforge doesn't seem to have anything - does anybody know where I can download it for comparison? ;P

  13. Re:forgot the scare quotes by SatanicPuppy · · Score: 5, Insightful

    I think the flood of microsoft biased studies in the last year go a long way toward bolstering linux's claims. If they weren't to some extent true, microsoft wouldn't be trying so hard to discredit them.

    I don't know why they bother honestly. My bosses bosses boss recently informed me that we use Microsoft almost exclusively. I just nodded and smiled, because it was easier to do that than explain that even our DESKTOPS are mostly Mac, and our infrastructure is 90% unix (Solaris, linux, bsd). The only people who really read those studies don't know what the hell they're talking about anyway.

    I don't give a damn what microsoft's studies say. I've been using unix, linux, and windows for years, and unix and linux have ALWAYS been more reliable. I've got a 250,000 dollar machine hooked up to a brand new Dell box running 2003 that goes down as often as a nickel whore, and I am SICK of hearing from Microsoft that this is just my imagination!

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  14. Actually, it does. by khasim · · Score: 5, Informative

    Weekly reboots.

    Get a copy of Win2K3 on your box. Create a directory that's 3 directories below the root.

    Put 200,000 files in that directory (size of each file does not matter).

    Now, watch the application that reads and writes files to that directory get slower and slower over time. Until you need to reboot the box.

    For an instant problem, open that directory in Explorer. All of your processor speed will be eaten by the "system" process. Even after you close Explorer. Rebooting is the only thing that will clear the problem.

  15. Re:forgot the scare quotes by superpulpsicle · · Score: 5, Interesting

    "As they attempt to increase business capabilities over time, customers are telling us that they are hitting a wall with Linux" said Martin Taylor, general manager of platform strategy at Microsoft.

    I am sorry but this is the most sorry ass downhill marketing I have ever seen. It is like Pepsi hiring a guy to wear a Coca-Cola Tshirt and purposely choking. This guy changed title 3 times in a year. Just a couple months ago he was Microsoft's very own Linux strategist.

  16. Let me tell you our "independant study" by porkThreeWays · · Score: 5, Interesting

    4 red hat 7.3 DNS servers. Have never required a reboot since installation.
    1 red hat 6 machine that lasted 6 years without an OS related reboot (the hardware started to give and the box had to be decommissioned)
    1 database/web server running SLES 8 has gone over a year and a half without a reboot.
    1 webserver running debian stable no reboot since installation
    1 proxy server running SLES 9 w/ squid that was set up in under a 1/2 hour under emergency conditions (old proxy hardware died unexpectedly) running 20 days under extremely heavy load until new server came in.
    1 database server running SLES 8. A year since last reboot.
    And those are all the ancient boxes. We've got many more linux boxen that are too new to have aquired a long uptime.
    From the article:
    experiencing significant reliability issues resulting in higher total cost of ownership
    *shrug* I've had none of these issues they speak of. All of our installs are quick, stable and long lasting. In fact, I've never had a production upgrade break anything, and never had an install take longer than a couple of hours in even the most complex of setups.

    This whole "get the facts" campaign is just silly. I don't know why they keep on with it. I've been working with Linux for years and never run into any of the problems they have "documented".

    Hey Balmer, want an anecdotal story of Windows breaking? Our mapping department had a Windows 2000 installation with their mapping software. One day it just breaks. 5 people standing around the box scratching our heads. No one had any clue why. Random reboots, blue screens, the whole works. We reinstall many times. Nothing. Do all the upgrades, patches and fixes. Nothing. Sounds like hardware, right? Nope. Upgraded to 2003 and worked fine since.
    The fact that the box could have run 2 years without major issue then break out of nowhere with 5 very smart people trying to solve the issue and can't makes me wonder.

    Get the real facts.

    --
    If an officer ever threatens to taze you, say you have a pacemaker.
  17. Independent ... by Savage-Rabbit · · Score: 5, Interesting

    ... is a relative term I could compile a report like this demonstrating that Linux admins take 68% longer to perform a set of cherry picked tasks you can do alot faster on a Windows machine that has a nice easy to use GUI management tool specially designed to do those same tasks. I could also demonstrate to you that Windows admins take 68% longer to perform certain cherry picked tasks because those same Windows GUI management tools (Windows command line tools tend to suck ass) simply don't enable you to perform those tasks as efficiently as you can by doing them with shell/perl scripts on the Linux command line. Comparing Windows to Linux/Unix is to some extent akin to comparing cats and dogs. The design philosophies of Linux/Unix are fundamentally different from those of Windows. The former are meant to be more flexible and targeted at better educated operators while Windows seems to be geared firstly towards corporations who want something that a relatively low skilled person, preferably without a high level of education (and thus a lower salary), can easily administrate and secondly it is geared towards the mostly clueless average consumer. Then there is OS.X which does an admirable job of being just as easy, if not easyer to use than Windows, (while still being more secure) but it still has all the power of Linux/Unix making it a nice compromise.

    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow