Slashdot Mirror


Ballmer Admits 'Linux Changed Our Game'

wackybrit writes: "We've all known Linux has got Microsoft all worried, but they've always denied it. On Monday at a conference in LA, however, Steve Ballmer (of Microsoft) confessed that the FUD surrounding Linux isn't quite what it was made out to be. The Register has also covered the story in an easier to read fashion. They point out that Microsoft has just changed a page on their site which originally derided Linux, but now simply states what 'Windows does better.'"

16 of 628 comments (clear)

  1. Read Microsoft's page ... by dougmc · · Score: 3, Informative
    It's remarkably ... fair.

    Not like the old page that said `Linux only had 128 MB swap files' and FUD like that. This page actually lists things that Microsoft does better, in a mostly factual, hype-limited way. They're not trying to be really fair to Linux, but at least they don't pull things that don't matter out of their rear and say `see? we're better!'. The things they list are, at least for a large part of it, actually important, and things that Microsoft does do better.

    As much as I love to bash Microsoft, they're finally doing this right. At least with this page, anyways.

    1. Re:Read Microsoft's page ... by bilbobuggins · · Score: 5, Informative
      Actually it seems to me that a lot of the drawbacks on the page can be summed up as 'incompatible with Windows', which depending on how you look at it isn't a drawback at all.
      For reference see points:

      -Windows users need a seperate account on *nix boxes
      -Linux doesn't have native ASP support
      -Linux doesn't have native Active Directory support
      etc.

      And this still doesn't stop some good old fashioned flaming FUD from slipping in, and I quote:
      'Given the recent cutbacks and layoffs at many commercial Linux vendors, including Red Hat's recent 17 percent reduction in it workforce, it is questionable whether commercial Linux vendors will be around to provide support in the long term'

      Not to mention the obligatory paragraph about why the GPL leads to anarchy.
      So sure, maybe it's an improvement over the old page but as expected still mostly hot air blowing...

    2. Re:Read Microsoft's page ... by frankie_guasch · · Score: 3, Informative

      -Windows users need a seperate account on *nix boxes
      pam_smb will help you here a lot. :)

    3. Re:Read Microsoft's page ... by Nailer · · Score: 5, Informative
      The `new' document isn't much of a replacement for the old. The new one is talking about embedded OSs, the formar one was talking about servers in general. I think someone got confused...MS still publish their Competing With Linux Partner Guide (or did last month, anyway) which has the same arguments re: TCO as their old comparative guides.

      Not to mention, the new guide isn't very fair either:
      1. SMB is integrated into Linux about as much as it is under Windows (the service is called smbd or server in each OS, turn it on, and go). We have multiple clients for network browsing and attaching to shares is handles as natively as NFS is. Server Appliance manufacturers simply don't have to do any Samba programming to make Samba function in an ordinary network - it works by default. Its also repeatedly benchmarked faster than the Windows implementation.
      2. Linux can and is performing Active Directory in real world enterprise environments. Check out Quantum's Guardian 14000 NAS device, which runs a AD Enabled Samba to provide Linux native AD support for its 1.4TB of storage. Although the Samba code used contains beta code from Samba 3, but these aren't cheap boxes and the utmost of reliability is expected from them.
      3. Scalability does not mean the ability to run on massively parallel x86 boxes. Windows 2000 runs on currently one platform. It does not scale to server class hardware beyond IA64. Linux does.
      4. last time I saw a Specweb test, Tux on Linux trouced IIS on Win32, just like Samba on Linux trounced `Server' on Win32.
      5. PHP is more popular than ASP Windows doesn't do PHP without addon software. The source is Netcraft, also quoted by Microsoft in their own benchmarks.
      6. Again. Microsoft's definition of integrated is flawed. Its possible to build a modular OS where applications communicate with each other using standard protocols - you don't have to turn on everything by default.
      7. Windows File Protection isn't necessary on Linux because Linux doesn't allow Joe User to save a trojan as C:\EXPLORER.EXE. Kudzu handles automatic configuration of hardware and requires less reboots to do so (test: configure a Linux / Windows XP dual boot on one system, pull out the hard disk, put it in another machine, time how long it takes for Kudzu /Windows Plug and Play to fix things)
      8. NTFS is a semi journaling filesystem. Hence chkdisk takes a few minutes to recover the journal on NTFS 5.1, whereas Ext3 does it in a half second.
      9. Red Hat does only have 2 official `certified' RAID for 7.3 drivers but according to the same HCL will support over thirt drives - whose vendors have not used Red Hat for testing, and thus are not `certified'. Likewise, there were only two certified apps for Windows 2000 professional when it was released (Omnipage and another app, IIRC).
      10. Integration is why distributions exist. That is their function. Standards are handled by the Linux Standard Base.
      11. The Web User Interface in Windows 2000 SAK is limited in out of the box functionality, requiring users to log directly into the device (rendering the device prone to significant danger through user tampering) to perform basic functions advertised in Win2000 SAK devices, like send alerts to an email address. As soon as users go out of your web based GUI (and they are required to) your server appliance is no longer an appliance - its a 2GB default install of Windows 2000 which users can and will modify (because the system encourages them to), increasing your support costs.
      12. If you want to program an app for Linux, and don't wish to Open Source your application, simply write your own code. You don't even get this choice with Windows 200 SAK - you MUST write your own code.
      13. That Microsoft would assume that the number of bug announcements for a product is indicative of that products security status illustrates a non existent understanding of basic security principles. All vulnerabilities are not reported, and bugs differ in severity and mitigation. According to ZDNet, Microsoft take a average of more than four times longer than Red Hat to patch a known flaw in their products, leaving MS customers exposed for longer periods of time. Furthermore Microsoft has a habit of not patching vulnerabilities at all - anyone who purchased Exchange 5.0 years ago (which had a known vulnerability allowing spammers to steal bandwidth from companies deploying the product) will know this - Microsoft never fixed the problem - customers had to PAY to upgrade to Exchange 5.5 to do this. As far as I know, the problem persists to this day (I'm not as involved in the Microsoft world as I used to be, having focused on Linux for the last three years).
      14. Last time I saw, Kerberos 5 was supported in Red Hat Linux as a stanard option. Run setup, turn on Kerberos, enter the server details, done. Modern Linux does not authenticate in clear text, this is a falsehood. The MD5 algorithm used in Linux's shadow password file is stronger than the MD4 used in NTLM2 authentication, which has known flaws and is no longer recommended by those who originally created it. NTLM2 is necessary to authenticate Windows clients pre Windows 2000, such as NT4 and Windows 98, the most popular versions of Windows in existence.
      15. Soon after Microsoft's alleged `security refocus' third parties found major vulnerabilities in Microsofts web server and browser platforms that were missed during the one month long `audit'
      16. The GNU Public licensing model also does not contain licensing provisions that require an OEM, and potentially its licensees, to disclose the source code for its intellectual property in a widespread fashion to open source participants. To suggest otherwise is a fabrication. It does offer the option to use Open Source application code within an OEMs products. If this option is exercised, and the resultant application distributed, the company has obligations to also distribute source code of that application. This does not apply to Windows systems because Windows OEMs do not have this option. Linux OEMs may choose as they wish.
  2. Still a lot of the same old FUD by grylnsmn · · Score: 5, Informative

    While Microsoft's new page is a nice change from the old one, it still contains quite a bit of their same old FUD. Here's a nice tidbit from the very bottom of the page:

    To ensure proper management of its intellectual property rights, an OEM must carefully examine an array of licensing complexities around the General Public License (GPL) that govern Linux. These complexities have resulted in embedded and dedicated operating system companies such as Wind River saying that they are seeing "a growing problem due to the growing uncertainty of using GPL-based code in embedded devices". An example of this risk can be taken from NVIDIA. An NVIDIA programmer, in the course of developing a driver for one of its products, used a portion of code from a freely available video driver. The developer failed to realize the code was licensed under the GPL and would therefore require NVIDIA to release the source code for its entire driver. Because NVIDIA did not want to release the source code to its commercial software, the company incurred substantial cost to develop a new driver that did not contain the GPL code.

    Companies need to recognize that in embedded and dedicated devices, such as server appliances, significant gray areas exist in the implications of the GPL's terms. Some forms of code linking and commingling may or may not trigger legal obligations under the GPL. As Michael Scott and Michael Krieger, a lawyer and computer science professor respectively, recently wrote, "Rare is the month when a lawyer who specializes in technology does not have a new client asking for help in untangling an open source code problem".


    In other words, they are still yelling "GPL bad! MS good!", they're just using a more dignified approach now.

    I find it especially telling to look at the example they used. They place all the blame for the NVIDIA programmer's mistake on the GPL. I'm sorry, but if you are going to use someone else's code in your program, it is your fault if you don't abide by their rules, not theirs.

  3. web benchmark by Ramadog · · Score: 4, Informative

    I followed the link towards the bottom of the ms/linux comaprison where it says ms makes a better web server platform. The benchmark they are quoting is over 1 1/2 years old and show that the ms based system had faster hardware.

    Run your operating system on faster hardware then claim it is faster than the opposition. One way to get benchmarks in your favour.

  4. Top quality FUD, from your favorite provider... by CondeZer0 · · Score: 5, Informative

    Wow, I just took a look at the top three items of the Win2k/Linux comparisons, and it's really good FUD:

    Linux:

    - No support for SSO, thus requiring end users to use at least two logon names and passwordsone for Windows and one for Linux/UNIX.
    What? Have you ever heard about OpenLDAP? Kerberos? Samba? even NIS allows you to do that!

    - Support for CIFS but only via Samba, not as an integrated, tested solution.
    Not integrated and tested by who?? HP, NEC, SGI, IBM, Apple... all them sell Samba based solutions. I'm quite sure that Samba implementation of CIFS is way betters than MS's, well known for being broken and quite buggy...(on purpose maybe?)

    - [...]it is questionable whether commercial Linux vendors will be around to provide support in the long term, [...]
    <sarcasm>Yea, I'm sure IBM, HP, Sun, Dell, Intel, and SGI will all go out of business next week... and then, I will not be able to contact any other linux Company, that will not have access to the src, and will not be able to provide support for my uber-closed Linux systems</sarcasm>



    Win2k:

    - Integrated support for Windows NT®, FTP, HTTP, Appletalk, and Novell environments, which enables consolidated administration in heterogeneous networks. Wow! They have "integrated support" for FTP and HTTP!!! OMG!
    And you only need to patch it every 5min!
    <sarcasm>I doubt that any OSS operating system will ever match that level of astounding functionality</sarcasm>
    Not to mention that MS ftpd is one of the worst ftp implementations I have ever seen.
    BTW, have you every tried to get Appletalk working on Win2k? I had to do it once, I would prefer to burn in hell for the rest of eternity than having to do it again...

    I will not bother with the rest of the list... but it's funny how people can bluntly lie like this and get away with it... *sigh*

    Enough time wasted with this, I'm going back to work with my "inferior" OS, that saves my company loads of money, not to mention headaches... thanks God that I have a smart boss(hi Carl!) that isn't fooled by shit like this...

    \\Uriel

    --
    "When in doubt, use brute force." Ken Thompson
  5. This is just more insidious FUD by aibrahim · · Score: 5, Informative

    I am not going to go through every point MSFT has on that page, but what I hope to show is that they are not changing their strategy, just their tactics to carry out the strategy.

    It used to be that MSFT FUD was a set of bald faced lies, apparently the hope was that no one would check them out at all. Well people did, found out they were lies and went to Linux.

    All of the new MSFT FUD is now more subtle, and appears to have supporting material in some cases. Now you can even check this stuff out, and if you are not very knowledgeable about software you can be fooled.

    Point 1

    Sum up as "Linux/Samba is not really compatible with Windows networking."

    In fact Linux, and Samba do support almost all features of CIFS. When Samba has been incompatible it is because MSFT changed their implementation. For this matter, Win95 and Win98 are incompatible with W2K CIFS networking.

    Point 2

    Sum up as "Linux is not fully compatible with Active Directory"

    True enough, but Linux is compatible to the extent that Active Directory is compatible with LDAP. In truth, MSFT is the one failing to comply with existing standards...neat how they twist this one around.

    Point 5

    Sum up as "IIS 5 is faster than Linux for SpecWeb99"

    This is just FUD. The link they point to seems to agree with their assertion but how about this link instead. It sure seems to tell a different story on identically configured hardware.

    Point 11

    Sum up as "Windows has reliable drivers that are signed by MSFT, Linux doesn't"

    Windows has NEVER had reliable drivers. Not all the best drivers are signed by MSFT if at all.

    The situation is only somewhat better than Windows for Linux to be fair. First off most drivers are delivered with an MD5 checksum, which is good enough for most uses. Secondly you get the source most of the time. Finally, since when has NASA written drivers for MSFT ? (Thanks to Don Becker, NASA GSFC.)

    Point 16

    My favorite..."The GPL is nasty and dangerous and can force you to give away all your secrets."

    First off the GPL is easy to understand, and very consistent. You get quite a lot for a simple price, "our changes to the code are to be made public with your codes binary release."

    MSFT has a problem with this because they are in the business of keeping code secret, not open sharing of ideas. Frankly that is OK, and can be a fair way to do business, despite what many OSS evangelists will tell you. What it fails to be however is an advantage to the consumer of the final product.

    --

    Don't post innacurate information
    If you do, I swear by my pretty floral bonnet I will end you.
  6. no he is not by Edmund+Blackadder · · Score: 3, Informative

    you will be asked to remove the GPLd code you used. If you remove that code you will not lose your rights to the other code because:

    a) the fsf and its general council have clearly stated that they will give people chance to remove GPLed code.

    b) no court will force you to surrender your code if you stop the breach of the GPL.

    So the whole "you may accidentaly lose all your IP" story is a bunch of bs.

  7. Re:HA HA HA HA by Anonymous Coward · · Score: 1, Informative

    The problem is that (as far as I know, someone with more experience, please correct me) if it was compiled with gcc, it's GPL software.

    Wrong. GPL only "infects" a software project when code is linked in, either dynamically or statically.

    LGPL relaxes this restriction by allowing a non-GPL software to dynamically link with a LGPL library, thus ensuring the freedom of the library, but allowing non-free software to be built against it.

    LGPL was the pragmatic compromise, and the GPL remains the most idealistic license.

  8. I'm afraid you misunderstand the GLP by vrt3 · · Score: 5, Informative
    Now there is an exception (caveat: IANAL) - if identifiable sections of a work incorporating GPL software are not derived from a GPL'ed work, then you don't have to disclose the source.
    That exception is nowhere in the GPL. If you distribute GPL-derived software, you have to distribute the source. But, when you don't distribute the software (when it's only for internal use), you don't have to disclose anything.
    The problem is that (as far as I know, someone with more experience, please correct me) if it was compiled with gcc, it's GPL software.
    Huh? Absolutely not! GPL doesn't have anything to do with the input and output of GLP'ed programs, only with the code. Code compiled with gcc is definitely not GPL'ed (unless you license it that way, of course).
    --
    This sig under construction. Please check back later.
  9. Re:How do they do it? by Quai · · Score: 2, Informative

    you cant compare a webserver running on a win2k box, and a webserver running on a win2k through WMWare, through SCO. A virtual machine will allways be slower than the host-machine running the virtual machine.

    Try to reinstall your computer with only your SCO disto. Then you will see the difference.

    (hmm, was your comment suppose to be funny? :P)

    --
    --
  10. Re:HA HA HA HA by mpe · · Score: 4, Informative

    The problem is that (as far as I know, someone with more experience, please correct me) if it was compiled with gcc, it's GPL software.

    No if you write original code and compile it with gcc you as the copyright holder can lience it however you like.

  11. Re:Licensing by rseuhs · · Score: 5, Informative
    Actually that part gave me a very good laugh too.

    You might think of the GPL whatever you want, but there are 2 undeniable facts:

    1) It does not randomly change like Microosft's EULAs
    2) All restrictions that apply to GPL also apply to MS EULAs (but not vice-versa, obviously).

  12. The Register got it wrong... by Anonymous Coward · · Score: 1, Informative

    People should go read the original VARBusiness article and not just the 'summary' at The Register. Ballmer only admits that you pay less for Linux then for Windows. He'ld be stupid not to admit that since anyone who can count can tell that. He still claims that you get more value out of Windows. He even invokes "lower cost of ownership". All this means is that Microsoft is switching to use the same arguments against Linux that Sun, Oracle, and others have tried to use against Microsoft over the years. This probably means that they are losing on the 'basically suitable for task' technical discussions. That in itself should be considered a win for Linux and Opensource.

    From the VARBusiness article:

    Instead of leading with price, the company has changed its
    go-to-market strategy to present a value proposition to customers and
    partners to explain why a solution from Microsoft delivers more
    capability at an appropriate price.

    "We are actually having to learn how to say, 'We may have a high price
    on this one, but look at the additional value and how that value
    actually leads to a lower cost of ownership despite the fact that our
    price may be higher,'" he said.

  13. Re:Comments on the FUD by matman · · Score: 3, Informative

    There's always acl.bestbits.at for Linux ACL support. Also, RSBAC (rsbac.org) patches allow Linux to support more fine grained and advanced authorization mechanisms than Windows does.