Slashdot Mirror


Microsoft Deploys Linux, Open Software in Test Lab

securitas writes "Microsoft has deployed Linux and other open-source software in test labs used by business customers to experiment with Microsoft's products. The products include Linux, Apache, MySQL and Open LDAP directory-access software on Intel-based computers, according to Martin Taylor, who is in charge of Microsoft's Linux competitive strategy. He said the goal was to learn 'what can you do and how can you do it' using open-source software in a competitive analysis. This step comes after Microsoft's recent admission that Linux is Microsoft's biggest threat after economic conditions. Mirrors at CMPnetAsia and InternetWeek." It'd be cool to see some patches come from Redmond, but that's probably wishful thinking.

53 of 595 comments (clear)

  1. MIcrosoft Linux by RhoryCalhoon · · Score: 5, Funny

    Is a Microsoft flavor of Linux coming? It could be this week's sign of the Apocalypse.

    --
    www.freshlymixed.com
    1. Re:MIcrosoft Linux by AvitarX · · Score: 4, Interesting

      Or figuring out a strategy to get the GPL tossed out so they could use other strategies to be able to use the code.

      hmmm, I wonder what this whole SCO ordeal is?

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    2. Re:MIcrosoft Linux by Anonymous Coward · · Score: 5, Insightful

      Seriously, though, if M$ thought they could profit from Linux they'd be using it in their products already and biting the GPL bullet

      Actually I disagree. Despite what most people think, Microsoft isn't nessesarily just after money all the time. Why wouldn't MS support Linux? It's a matter of control. MS just has to have control of EVERYTHING and they refuse to let go. Release after release of windows shows that less and less of the system can be manipulated by the user/admin, and typically is purposly obscured to make sure that doesn't happen. Linux, being open as it is; goes directly against MS's phylosophy there. So in short, MS will play a game for money, but only if it's in their own yard.

    3. Re:MIcrosoft Linux by Mitchell+Mebane · · Score: 4, Funny

      Is a Microsoft flavor of Linux coming?

      It sure is. It's scheduled to be out in November:

      Microsoft Linux - the premier linux distro

      --

      The roots of education are bitter, but the fruit is sweet.
      --Aristotle
    4. Re:MIcrosoft Linux by doi · · Score: 4, Funny
      Is a Microsoft flavor of Linux coming? It could be this week's sign of the Apocalypse.

      Only if it includes GNotepad for X written in GNU.Net, and an MS-Ogg version of the Free Software Song sung by Bill Gates.

      --
      A man's reach must exceed his grasp, or what's an erection for?
    5. Re:MIcrosoft Linux by Amiga+Trombone · · Score: 4, Interesting

      Seriously, though, if M$ thought they could profit from Linux they'd be using it in their products already and biting the GPL bullet. Or figuring out a strategy to get the GPL tossed out so they could use other strategies to be able to use the code.

      They really wouldn't need to do that. If they were seriously interested in competing in the open source realm, they could go the BSD route, like Apple did.

      Wouldn't it be fun to see a Microsoft OS based on Darwin?

      Hey, it was just a thought. Nevermind.

    6. Re:MIcrosoft Linux by Alien+Being · · Score: 5, Insightful

      MS just has to have control of EVERYTHING
      Because that's how they get the money.

      Why wouldn't MS support Linux? It's a matter of control.
      Flashback to 1994 and you could say the same thing about supporting the Internet. But once they realized that they couldn't stop it, they had to get in the game, cheat like bastards, and attempt to "move it to their own yard".

    7. Re:MIcrosoft Linux by jbolden · · Score: 4, Insightful

      Microsoft and Bill Gates in particular were for many years the primary advocates of user controlled computing, the empowerment from thick clients over the thin client dumb terminal minis and mainframes. Windows for Workgroups is a remarkably liberal product in terms of what it lets people do.

      However the PC revolution led to very high support costs and the customers (corporate workers and corporate management) pretty much agreed they wanted resonably priced reliability more then freedom. The lockdown of NT came from this. However in no meaningful sense is an NT box really locked down for a knowledgeable user.

      Gates/Microsoft cares more about customer satisfaction than about freedom but I certainly would not argue they are anti freedom in principle.

    8. Re:MIcrosoft Linux by linzeal · · Score: 5, Informative

      That is because microsoft had no server OS robust enough to serve dumb clients at the time. They marketed what they had.

    9. Re:MIcrosoft Linux by TheOldFart · · Score: 5, Funny

      >> Control

      >> It'd be cool to see some patches come from Redmond...

      Yeah. I can see that. The patches coming out of Microsoft would come in stages. Patch number 1 should be worn for two weeks, and then patch number 2 for another 3 weeks, and finally, if the symptoms of addictions were still present, wear patch number 3 for another 2 weeks. Once we've all gone through the patch process, we would finally be free of this awful habit of smok... I mean, using non Microsoft nicot... I mean, software.

    10. Re:Microsoft Linux by deranged+unix+nut · · Score: 4, Interesting

      Since Microsoft products are all closed source, who the hell would ever find out if Microsoft was using GPLed code in any of their products?

      AFAIK, there's really no way to tell... for all I know, they could have been using GPL code for quite a while and no one would ever notice.

      Well, to help answer your question:

      1) Microsoft has over 54000 employees. Around 10% of which are temporary contractors whose contracts can't go over a year. That's quite a few people who could snitch.

      2) As long as you sign a NDA, you too can see the source code for Windows NT for academic purposes.

      3) Source code is regularly licensed to other companies and governments.

      4) The embedded products are compiled by the customer!

      5) Microsoft is very visible, people reverse engineer parts of Microsoft software all the time.

      6) The legal liability scares Microsoft to death! A couple years ago they went so far as to decree that no Microsoft programmer is allowed to even look at GPL code, let alone contribute to a GPL project on personal time. One programmer I know had to have his manager hire a contractor to reverse engineer sample code for a netscape plug-in because the sample code was GPLed and he wasn't allowed to look at it!

    11. Re:Microsoft Linux by deranged+unix+nut · · Score: 4, Informative

      Yes, I also do testing for:

      Regressions - Make sure that previous bugs don't pop up again.
      Integration - Make sure that all the pieces work when you put them together.
      Globalization - Make sure that none of the user messages / interfaces are hard coded.
      Localization - Make sure that it is translated into other languages correctly.
      Accessiblity - Make sure that handicapped users (blind / deaf / etc.) can use the product. (Can you use the program without a mouse? Does it work with large fonts, high contrast, etc?)
      Scalability - Large numbers of records, large amounts of data.
      Performance - Is it sufficiently fast?
      Reliability / Memory leaks - Can the system stay up for multiple months without hint of reliability problems?
      Security - Do we verify the data before we use it? Do we protect sensitive data?
      Update testing - Does data persist and functionality work correctly after upgrades?

      Dogfood deployments - run the business on alpha and beta releases to make sure we find problems before the customers do.

      etc...

      There are hundreds of criteria for each item on this list and there are a number of other major quality areas that most test teams attempt to cover in their test passes.

      You would probably be surprised at how much testing actually happens at Microsoft.

    12. Re:Microsoft Linux by MSZ · · Score: 4, Insightful

      You would probably be surprised at how much testing actually happens at Microsoft.

      I AM surprised, that with all this testing, so many ugly bugs get through. Your list of QA is long and nice, sure, then how come there is so many big ugly bugs in MS products? Especially security-related bugs :-(

      --
      The moon is not fully subjugated. I demand a second assault wave preceded by a massive nuclear bombardment.
  2. Why do I get the feeling... by rekkanoryo · · Score: 5, Insightful

    ...that this will be a venue to generate more FUD as well as an attempt to get a competitive edge? Am I just paranoid or what?

  3. Comment removed by account_deleted · · Score: 4, Funny

    Comment removed based on user account deletion

  4. Old Chinese Tatic. by schwep · · Score: 5, Insightful

    Keep your enemy close to you so you can keep your eye(s) on it. A wise move by Microsoft.

  5. Coming soon... by nacturation · · Score: 4, Funny

    He said the goal was to learn 'what can you do and how can you do it' using open-source software in a competitive analysis.

    You can find the new revised feature set for Longhorn here.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    1. Re:Coming soon... by RzUpAnmsCwrds · · Score: 4, Insightful

      Lets see... what's new in Panther?

      Fast user switching.
      XP has it.

      Videoconfrencing combined with IM
      XP has it.

      HTML Email
      XP has it.

      Encrypting File System
      XP has it.

      Folder Syncronization
      XP has it.

      Hmmm.... you might as well call it "Mac OS XP".

    2. Re:Coming soon... by ender81b · · Score: 4, Informative

      Journaling file system xp doesn't have it

      Wrong. NTFS

      Why did MS choose to have every menu in the entire system cascade down except for the single most important one? Any sane UI designer would put the Start button in the upper-left of the screen.

      Click on start bar, drag to upper part of screen. Done.

  6. Here's the MS distro by Snoopy77 · · Score: 4, Funny
    --
    "She's a West Texas girl, just like me" - G.W Bush Iraqis
  7. Know your enemy, then attack. by nurb432 · · Score: 4, Insightful

    Now that they have offically declared OSS as the enemy, it only makes business sence to learn as much as you can.

    And since its 'open' that wont be all that hard.

    --
    ---- Booth was a patriot ----
    1. Re:Know your enemy, then attack. by deranged+unix+nut · · Score: 4, Insightful

      Exactly.

      They are setting up a test lab to deploy OSS software in, so they can measure it, find out what works well, what doesn't work, how it interoperates with other software, how it performs, and how hard it is for normal users to use. Then they are going to take that data and use it to improve their products and marketing.

      All smart companies do this...why is this news?

  8. do you want me to believe... by civilengineer · · Score: 5, Insightful

    that they did not bother to look at it so far?

    --

    New year Resolution: Don't change sig this year
  9. Re:What is it running on? by Jack+Comics · · Score: 4, Funny

    You're being optimistic. 386 is my guess. Or even more dastardly, running it on a 286 and claim that Linux and its apps break on Intel hardware.

    Jack

    --
    "We are all in the gutter, but some of us are looking at the stars." - Oscar Wilde
  10. The most amusing part of this whole thing... by JessLeah · · Score: 5, Interesting

    ...is the bit in the referenced article where Steve "Monkey Boy" Ballmer is claiming that not only does Windows have a lower TCO than Linux, but MS is faster at patching bugs than the OSS/FS community...

    If it weren't such a sobering reality that many businesspeople actually believe such BS, it would be funny...

  11. typical MS - aiming at the product by sentientbeing · · Score: 5, Insightful

    from the article: 'In an effort to better understand its main source of competition'

    IMO The problem with MS is they no longer understand the customer

    --

    ------
    beware he who would deny you access to information, for in his mind he dreams himself your master
    1. Re:typical MS - aiming at the product by Alien+Being · · Score: 4, Informative

      "IMO The problem with MS is they no longer understand the customer"

      But they understand the customers' wallet. MS is doing this to find subtle ways of breaking LinWin compatibility wherever they can. Then they'll offer expensive connector software to restore the broken functionality. They'll spin it like they're playing nice with the other kids, but all the while, they'll just be taking everyone for a ride.

    2. Re:typical MS - aiming at the product by Xpilot · · Score: 5, Insightful

      IMO The problem with MS is they no longer understand the customer

      I think they understand the customer all too well. Remember, M$ does not target geeky hackers who love fiddling with command lines and compiling source. They market their stuff with propaganda such as "command lines are hard, look at this happy friendly colorful GUI, it'll make you productive even if you're incredibly stupid". You have no idea how much that affects the hearts and minds of people. Over here in the CS department, I've had former classmates who were fanatically loyal to M$, for no other reason than "it has a more colorful GUI" and "easy to use, just clickety click and everything is magically done!". And these are computer science students. Think of how much influence M$ has on PHB's and decision makers.

      --
      "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
  12. Re:What is it running on? by Sophrosyne · · Score: 5, Funny

    It's actually being emulated within Windows XP... that way engineers are exposed to a "regular" rate of crashing and don't get too suspicious.
    The last thing Microsoft wants is for its engineers to switch over themselves.

  13. Not That Weird by KrispyKringle · · Score: 5, Insightful
    The point, presumably, is to "know your enemy." MS are merely researching how their competition can be used in business to figure out its strengths and weaknesses, and how to compete with it.

    The suggestions that this is an attempt to create FUD seem a bit off the mark to me. I'm sure MS aren't going to be touting the benefits of Linux, but in a closed environment they have far more to gain from honest testing and competition than they do from convincing a very small number of customers, presumably devoted ones, that Linux sucks.

    Were they do do that, they'd just end up looking like fools. And while marketing may help in the desktop market, those who spend large amounts of corporate money on enterprise software research it thoroughly. MS won't beat Linux in the server market just by marketing, no matter how much they spend. They know that, and have clearly decided to take Linux seriously as a competitor.

  14. Why this won't work by SeanTobin · · Score: 5, Interesting

    Sorry for any MS bashing later in this post, but thier marketing department is asking for it.

    First off, lets talk hardware. I'm assuming here that both sets of hardware are going to be identical and normalized. By that I mean no paladium test beds, or winmodems, or other odd hw pieces that would skew things in one direction or another. Just some off the shelf dell's would be good. This is the easy part.

    Next, on to the software. We have a company that doesn't know much about linux (I do mean as a company. I'm sure there are some very smart folks up there that know what they are doing. Its just in MS's best interests not to have them around the linux machines.) setting up a linux system. Heck, this sounds like it is just slightly more shady than an "independant testing" lab doing the comparision.

    Now, software tuning. Somehow I doubt that the win2k installs are going to be stock. They will tune everything to get every last cycle they can out of it. Now, I wonder if they will do the same in the linux boxen? Heck, I'd put money on them actually slowing down thier benchmarks for thier tuning efforts.

    The only set of benchmarks/comparisons I'd respect is a side by side setup. One side has MS's lackies fiddiling with thier server to tune the heck out of it. The other side would have the folks from MySQL*, Apache, RedHat*, and probably ESR for good luck. Then some independant testing machine connected to both doing the same task. (i.e. an actual demo transaction). Why hasn't anyone done something like that?

    And tell ESR that hacking the Windows machine before they had a chance to patch it is no fair.

    [*] Please substitute your favorite software package if you feel the need to do so.

    --
    Karma: SELECT `karma` FROM `users` WHERE `userid`=138474;
  15. MS Patch to Linux Kernel by rjamestaylor · · Score: 5, Funny

    diff -urN ms-linux/CREDITS linux/CREDITS
    --- ms-linux/CREDITS Wed Jul 31 17:39:29 2001
    +++ linux/CREDITS Wed Jul 31 17:41:45 2001
    @@ -973,8 +973,8 @@
    /*
    -ALL YOUR BASE
    +BELONGS TO US
    */

    --
    -- @rjamestaylor on Ello
  16. Good to see by jormurgandr · · Score: 4, Interesting

    With M$ realizing that they have competition, they will strive to improve their products (with how much success?). If they actually do improve their wares, the Linux community will ralley to improve the software in Linux.
    Everybody wins.

  17. Having worked with Linux at MS... by danshapiro · · Score: 5, Interesting
    ...I'm about to get modded down. But in serious reference to the final comment about patches, MS has a strict executable-only policy for non-MS source in general, and GPL'd source in particular. They are rightfully concerned that if a developer looks at source, they can be sued if s/he produces something similar later. Even if it wasn't pirated, it's hard to prove that. In the case of GPL'd code, it's even more severe. It's MS's worst nightmare that Windows would have GPL-licensed code checked in, as they could conceivably be forced to open-source the whole product.

    BTW, my work was investigating Linux desktop environments to see what the state of the art was. Lots of the devs monkeyed around with Linux, but everyone was very hardcore about not touching the sources.

    --
    This posting is provided "AS IS" with no warranties, and confers no rights.
    1. Re:Having worked with Linux at MS... by danshapiro · · Score: 5, Insightful
      Nothing "prevents" devs from looking at the code (except their concern about being fired). Nothing prevents them from checking the whole Linux kernel source tree into Windows (assuming "them" is a developer with checkin privs). But there is a clear company policy not to do it, which means that if it does happen, they can legitimately claim that it was a terrible accident etc. It's a CYA move. If they didn't, then they're open to claims that it was deliberate infringmenet.

      Besides which, if you know anyone who works there now, they'll happily tell you that it is indeed the policy.

      --
      This posting is provided "AS IS" with no warranties, and confers no rights.
  18. Re:Microsoft Math by swtaarrs · · Score: 4, Insightful

    The main argument is that Windows sysadmins get paid less than Unix/Linux sysadmins. I can almost understand this point, but I've gotten the impression that one *nix admin can handle more computers than one Windows admin can, so that would even out the sysadmin costs. In addition to that, I have a lot of trouble believing that the difference in sysadmin cost is enough to make up for the fact that Linux is infinitely cheaper than MS software. Also, with MS software, some companies have had to hire an extra person to make sure they are in compliance with all the MS license oddities, so that has to add to Windows' TCO.

  19. Microsoft has some very talented programmers by adiposity · · Score: 5, Interesting

    And I'd be happy to get patches from them, especially since they'd be open-source, and reviewable. If they were helpful, of course they would be accepted under the GPL.

    If you look at early white papers from Microsoft, it becomes obvious that some very intelligent people worked there at one time. Surely some of them are still there, as well as fresh talent. Many people I know "sold out" to Microsoft in college, but were actually experienced Linux hackers.

    Software bloat (happens to everyone), company overhead (impossible to avoid in a company the size of MS), and economical agendas driving poor design decisions have all made MS' codebase an unsightly beast, I'm sure. But to think they are incapable of creating working, useable, and even secure code is preposterous. Some of the most talented programmers in the world work for MS.

    However, I'm fairly sure that very little help will be given to GNU/Linux from MS, whether by the company as a whole, or specific employees. MS would consider it a waste of time, and dangerously helpful to a competitor. The only reason I could see them doing this is to convince a court they weren't "anti-competetive." Judging by the overly-lenient rulings as of late, however, I doubt they need to do so.

    -Dan

  20. Re:Patches from Redmond by blackwizard · · Score: 5, Funny

    Maybe they could put in a patch that would make Linux display a friendly blue screen when it crashes instead of a kernel panic message. Embrace and extend!

  21. I'd like to see them do this by BoomerSooner · · Score: 4, Interesting

    Get 2 Pentium III 450MHz with 768MB of RAM
    Install like software:
    Windows 2000 Server - RedHat Linux 7.3
    IIS 5.0 - Apache/Tomcat 4.1
    Sql Server 2000 - MySQL Or Postgres Or oracle 8i .Net Framework - JSP in Tomcat
    Exchange Server 2000 - QMail

    Which perform better under a low, medium and heavy load? That is an excellent test because it takes the hardware out of the equation and does a real stress test on the OS & applications.

    I did this and believe me it is like night and day. The linux server ran without a hitch. The windows server was painfully slow. I guess being able to run all your apps without a gui is an advantage. Hell ssh versus terminal services is no contest. If you need a gui just tunnel vnc through ssh.

    Oh did I mention the cost for the software?
    Windows 2003 Server, Exchange 2000, SQL 2000, .Net developer tools (you need to be able to program that server) are around 1200 + 800 + 1200 + 900 for a total of $4100 (approx). Not too expensive but not free either.

    Plus the added bonus of checking technet for patches twice daily.

    1. Re:I'd like to see them do this by Anonymous Coward · · Score: 4, Informative

      Exchange Server 2000 - QMail
      ^^^^^^^^^^

      If all you want is a pop3/smtp server than of course qmail would be cheaper. If you need a fully collaboration based mail server with calendaring/scheduling/tasks and many features I can't think off the top of my head you got with Exchange 2000. There's nothing remotely close yet that works out of the box in less than an hour. I just installed a seventh exchange server in our environment last week, flawlessly. Note: this isn't for redunancy either. Remote offices prefer to use a local server instead of crossing the internet via a vpn.

      Some companies would die without the functionality of Exchange so in their eyes price does not matter.

  22. Re:MS uses Linux internally by YU+Nicks+NE+Way · · Score: 4, Interesting

    I'm an employee. There's no reason for me to respond anonymously: the corporate policy is well publicized.

    Internally, corporate policy has always been that we can use whatever tools we want, provided that they serve the purposes of our jobs best. The only restriction under which we work is that developers or other people who have direct check-in rights to any of our trees (think "committer privileges"; it's the closest thing in the FOSS world) are not permitted to examine code released under GPL or any other viral license.

    So, yes, for testing interop, we have a lot of Linux/Apache boxes around. We have a lot of Perl. (We've been supporting ActiveState for years, after all.) If there were a competitive FOSS compiler available, I'm sure that some groups would use it. There isn't. We've certainly had teams do comparitive analyses.

    One of the developers in my group is a forty-something year old guru who run XEmacs on his main dev machine. Whenever he reformats his machine, he does a pure binary install and deletes the .el files to keep things clean. His attitude is that it's easier for him to keep using a tool which he recommends other developers avoid than it is to learn a newer and more efficient tool. I've asked him if he ever received any pressure to change. His answer was, "Never. [Our boss] doesn't care what we use to write code; he cares that we write code."

    Maybe he's drunk too much of the KoolAid -- but my experience tracks his. Think about it. Why would we care? If one of our gurus is more productive using XEmacs, that is at worst a data point for the Visual Studio folks.

  23. Re:OSS/FS community should do the same by Hatta · · Score: 4, Insightful

    I don't think most OSS developers are out to kill M$. They have an itch that needs scratching. So they do their developer thing, and make a system that works for them. And thus we all benefit.

    Destroying microsoft is beside the point. As a matter of fact I'd be happier if more developers would ignore windows and stop copying windows. KDE, OpenOffice, Evolution. Give me Blackbox, vim/latex, and mutt any day. Remember, imitation is the sincerest form of flattery.

    --
    Give me Classic Slashdot or give me death!
  24. Re:Patches from Redmond by EvilTwinSkippy · · Score: 4, Funny

    I wouldn't mind Linux patches from Microsoft if they were tastefully embroidered, and matched the color of my jacket.

    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
  25. Respect by chuckw · · Score: 4, Insightful

    If anyone from Microsoft is reading this, take this advice to heart:

    You would gain an amazing amount of respect that you desperately need if you stopped fighting Linux and made an effort to join the community. Many of my customers are chomping at the bit to dump Microsoft and go Linux on the desktop. The day is coming when that'll be possible. I've already begun the migration with the help of CrossoverOffice.

    Inaction on your part is creating a vacuum in the marketplace. Someone will fill it like they always do. Unfortunately for you, this time you won't be able to use your competitive advantage to stop them.

    --
    *Condense fact from the vapor of nuance*
  26. The real reason by ratfynk · · Score: 4, Insightful
    What they are really looking for is if they can identify any software system function sequences that have obviously been reversed. Then add that to the fire against open source. The exercise is to also find as many new coding common sense short cuts that they can use. The thing is they do not have to reverse open source to steal any good ideas from it, but they can sue open source people if they can prove that a patented function sequence or interface has been reversed.

    If they do succeed in discouraging OSS coders from coding to fill application requirements of business, then this will not kill Linux but it will surely entrench MS as the only business software you can get. Do they deserve the market share that they have? No. How will they keep the market share? Like they always have by destroying anything they cannot absolutely control. Fortunately Intel has been getting a little pissed at them lately, as have alot of hardware manufacturers. Hopefully the industry will gang up on them and finally kick the shit out of Billy and Co.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  27. Ridiculous assertion. GPL doesn't work that way. by maynard · · Score: 4, Insightful

    It's MS's worst nightmare that Windows would have GPL-licensed code checked in, as they could conceivably be forced to open-source the whole product.

    Well, looks like you got modded up. But you're wrong just the same. The assertion that Microsoft might have to release Windows, Office, or some portion thereof, because a copyright holder, who happened to license under the GPL, claimed -- and proved -- copyright infringement within one of Microsoft's products, would therefor force Microsoft to release some or all of their product line under the GPL, is plain absurd. It would never happen, nor should it.

    Suppose SCO is right and within a few files of the Linux kernel it's proven that someone illegally copied a section, or even whole files, from their source tree into the Linux kernel. Does that mean SCO owns all of the kernel, even those parts they didn't write? No. The outcome would be that those parts which were infringing would be excised and then rewritten.

    Suppose it turns out that an engineer in Microsoft illegally copied gzip into Windows, and then Microsoft distributed Windows under their proprietary license. The FSF would have cause for a copyright infringement suit, and they would win. But could they demand a judgment that Microsoft release Windows under the GPL as a result? No. The best they could do would be to demand financial damages plus the removal of their code from the Windows source tree.

    Suppose Microsoft management distributed gzip withing Windows, even knowing it's licensing terms under the GPL, could the FSF then enforce the redistribution terms license beyond Microsoft paying damages and removing the infringing code under court order? I seriously doubt it. And that's willingly breaking copyright law by corporate officers (which they have done -- see Stacker).

    So, the assertion that Microsoft doesn't allow it's engineers to view GPL'd source under the assumption that said source could illegally make it into their product line and then force them to release their product under the GPL is patently ridiculous. It wouldn't work that way, period. This is, of course, speaking as a layman and not a lawyer.

    Cheers,
    --Maynard

  28. From the secret MS strategic OS file! by SuperKendall · · Score: 4, Funny

    No, not Darwin...

    In the next few years, prepare for - Microsoft Hurd!!

    And you were wondering why the nextgen OS was codenamed "Longhorn"....

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  29. GNU/Hurd 1.0 by gatesh8r · · Score: 4, Funny

    Coming Fall of 2092.

    --
    Karma whorin' since 1999
  30. SCO Connection! (Microsoft paid SCO license fees) by innosent · · Score: 5, Funny

    Wow, somebody actually did pay SCO to license and use Linux!

    --
    --That's the point of being root, you can do anything you want, even if it's stupid.
  31. The begining of the end for Microsoft. by rusty0101 · · Score: 5, Funny

    First Linux gets deployed for testing in a test lab at Microsoft.

    In order to get it's performance down to a level that they can compare Microsoft software to it they start storing internal documents on it and tell internal users to use that store to stay current.

    Since the internal servers are now getting fewer hits, they start consolidating some of the services they had spread across several servers onto fewer servers, freeing up those servers.

    A few of the free servers get rouge installs of Linux with Samba, and people discover that they can actually store files on these servers with some reliable expectation of seeing the files again a couple of minutes down the line.

    The Micorsoft Win2k+3 servers start to respond even faster to the test systems and more consolidation goes on.

    Someone in the test lab isn't happy that the Linux boxes are still outperforming the Win2k+3 boxen, so he convinces management to use them as DHCP servers for the campus.

    This frees up even more of the internal Win2k+3 servers from consolidation, and someone says, let's show that SQL Server is better than (insert favorite Open Sourc or proprietary RDB engine that runs on Linux here) and people in the company realize they are actually getting close to real time results off of these servers, and start migrating applications over to them.

    Since Microsoft is trying to move to a dbfs anyway, even more of the internal infrastructure starts getting moved over to Linux as the original Microsoft OS servers are relieved of the duties that they were originally tasked with.

    Marketing comes along and asks how the new Windows 2K+3 is going, and IT is able to say with a straight face:

    "We were able to consolidate the entire campus server farm down to a single system runing Win2k+3. And since no-one in house is actually using it, response time and recovery from failures has become a non-issue. We are saving millions of dollars every year because the quiet migration to an all Linux infrastructure has reduced the actual demand for systems to the point that we have been able to reduce our electrical usage by shutting down systems and reducing the demands on the cooling systems significantly. Our phone support teams are somewhat confused as they are getting calls about server issues that they have never experienced, however our developers have been able to get Win2k+3 running on a VMWare image under Linux and we have been able to simulate the issues that customers have been experiencing, without actually loosing any data or having any significant down time."

    Marketing, "Huh?".

    Ok, it's not likely to happen, but we can fantasize.

    -Rusty

    --
    You never know...
  32. Re:not good enough. by ambar1073 · · Score: 4, Insightful

    I can't believe this troll flamebait is modded as "interesting." Such is /. Be afraid, be very afraid. Building labs like this, and investing in "learning the enemy", is the singular reason why Microsoft wins time and again. Regardless of what you think of their tactics, you have to admit that building a Linux testing lab -- from a "learn the enemy" standpoint -- is a damn good idea.

  33. What Microsoft Linux would be like by kasperd · · Score: 4, Interesting

    Lets forget about the jokes. And instead lets try to imagine, what Microsoft Linux would really be like, if it was ever released.

    I'm pretty sure it would include patches to the kernel, and they might even play by the rules and release the source for those. But there might very well be some closed source kernel modules as well. In addition you will not be allowed to copy those kernel modules. We can start guessing about what modules there will be. But I'm pretty sure one of them would be an ntfs driver.

    Microsoft could get their usual GUI to run on top of Linux. Since others have done most of it, Microsoft could do it as well. The exact details about how Microsoft would do it are not easy to guess. They could use parts of Wine, but maybe, Microsoft want to do it another way. If they are going to use Wine, they could either use the latest version, or the last non GPL version.

    But Microsoft could take a completely different route and not use any Wine code at all, instead they could use as much of the existing Windows code as possible. I wonder if this would be best done in a library or a kernel module. Probably they would like a real binfmt_exe.o kernel module with its own personality. It is probably going to map some large DLLs into the process address space, and maybe even some shared memory.

    I believe programs written for Windows when running on this Microsoft Linux will have access to some NTFS features, that are not easilly accesible by normal Linux programs. It could be done either by the closed source library knowing about some secret ioctl implemented by msntfs.o, or by cooperation between msntfs.o and binfmt_exe.o. Possibly a combination; an ioctl, which is not only secret, but also only allowed to programs running with the exe personality.

    I wonder what graphics drivers are going to look like. I guess they will probably ship with closed source kernel modules implementing drivers for various graphics chips. But of course they are probably going to be incompatible with XFree86. And might even prevent the ones needed for XFree86 from being loaded at the same time.

    --

    Do you care about the security of your wireless mouse?
  34. Why are they announcing this? by Lokist · · Score: 4, Insightful

    I'm sure they have had a test lab setup for quite some time now...Have you ever worked for a company and they have NOT bought the competitors product and put it in a restricted area... Our old company used to do that all the time... No one had access to the area, but a select few... Microsoft is doing the same...Yes they will improve there software by copying or at least duplicating the hard work the OSS community has done... They arn't a threat to us people... How many of you WANT all of your users in your office to run Linux? Honestly... at this point in development? It runs GREAT on our machines... Could stay up years if you know how to maintain it right... and WE do... but the average user wouldn't. If Microsoft comes out with some new feature that interests us... Trust me, we will have programmers on it in two seconds to duplicate there new feature and add it into our system. Remember Internet Connection sharing? well we came up with that first... ipfwadm.... The stupid little Start button... well I THINK (don't quote me on this) we took that from them... We definatly took the "control panel idea"... Mix and match... If WE want it bad enough... It will be done... A good example is new hardware... If it only works on windows... and it's crap even while working there... no point in making drivers for it here...but if it's something good... Watch out for a new "so and so driver coming next month"... - Just my 2 cents... but you'll have to give the 2 cents back if you will, I'm kinda on social assistance.