08.04.09

Gemini version available ♊︎

Microsoft Only Gave 14,010 Lines of Code

Posted in Courtroom, GNU/Linux, GPL, Kernel, Microsoft, Novell, SCO, Servers, UNIX, Virtualisation, Windows at 5:55 am by Dr. Roy Schestowitz

Source code

Summary: 14,010 lines of actual Linux code, not 20,000 as Microsoft claimed

Microsoft has claimed that its self-serving loadable module for Linux [1, 2, 3, 4, 5, 6, 7], which only advances Microsoft’s interests by polluting the kernel with Microsoft APIs, comprises 20,000 lines of code. Not quite the case, alleges Slated, who has taken a look at the code. Last night he wrote about this patch (managed by a Novell employee by the way):

For those who might want to keep an eye on what the Vole is injecting into the software we use:

http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh..

The consolidated patch is here:

http://www.kernel.org/pub/linux/kernel/people/gregkh…

This is essentially what it adds:

. Microsoft Hyper-V client drivers
. Microsoft Hyper-V virtual storage driver
. Microsoft Hyper-V virtual block driver
. Microsoft Hyper-V virtual network driver

The kernel config options are listed as:

. CONFIG_HYPERV
. CONFIG_HYPERV_STORAGE
. CONFIG_HYPERV_BLOCK
. CONFIG_HYPERV_NET

Here’s the license:

Copyright (c) 2009, Microsoft Corporation.

This program is free software; you can redistribute it and/or modify it under the terms and conditions of the GNU General Public License, version 2, as published by the Free Software Foundation.

This program is distributed in the hope it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place – Suite 330, Boston, MA 02111-1307 USA.

Authors:
Hank Janssen <hjanssen[at]microsoft.com>
######

Oh and BTW, after removing all the non-Microsoft copyrighted code from the above consolidated patch, all the diff declaration headers, and all the empty lines, the number of lines remaining (i.e. the actual code Microsoft generously “contributed”) is 14,010, which is a good six thousand lines short of Microsoft’s claim.

That’s OK though … it’s six thousand fewer lines for me to remove.

Microsoft contributes nothing to Linux, except lawsuits for the most part. Microsoft funded SCO’s lawsuit against Linux (more than once) and right now Microsoft is suing companies for using Linux (also more than once). People who do not yet know all of this ought to wake up and get the facts. Microsoft is always attacking Linux and the code mentioned above is no contribution. If Oracle writes a new file system for Linux (btrfs as the example in mind), then that file system is valuable also to IBM, to H-P and even to us home users. It really enriches Linux. Microsoft’s patch, on the other hand, is helping nothing but Windows, turning GNU/Linux servers into just a virtual appliance running under Windows.

“Microsoft funded SCO’s lawsuit against Linux (more than once) and right now Microsoft is suing companies for using Linux (also more than once).”Whenever Microsoft claims that it “contributes” to Linux, remember that its long-standing CEO, Steve Ballmer, said: “Linux is a cancer that attaches itself in an intellectual property sense to everything it touches.”

Ballmer never retracted that statement and under his leadership Microsoft has also paid SCO, as confirmed in the courtroom under oath. For background about the past month’s SCO developments (a little from June too), see:

More bizarre twists in the SCO case have only led to the point where, according to Pamela Jones, SCO is nearly finished for good.

So those are the various possibilities I see. Do you see any good ones, if you are SCO management? I don’t see even one. If we are marking on a curve, SCO’s suggestion in its letter is the least toxic, but none of the possibilities now are really ideal from SCO’s point of view, and how realistic do you think it is as a suggestion at this late date, considering all that came out in discovery and at the hearing?

I think this may be the very first time in the entire SCO saga where SCO seems to have no really good options on the table that I can see.

And that’s probably why after the hearing on the 27th, I was overwhelmed by the incandescent realization that we had just turned a real corner, one that changes everything, and that we’re in end-game territory, at last.

Microsoft may have moved on from SCO. Now it has Novell at its disposal — the company which is the real owner of UNIX. SCO — like Microsoft and Novell — also used to contribute to Linux before chaos began.

“Pamela Jones [...] has told Infoworld that Microsoft will be the next SCO Group”

Heise

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

8 Comments

  1. JohnD said,

    August 4, 2009 at 8:00 am

    Gravatar

    Talk about picking nits.
    I’m willing to bet that most developers look at the line count in their IDE to determine lines of code. I’m also willing to bet that if you take the same approach with other contributions, the lines “actually” contributed would drop as well.
    Does anyone really think that the community opinion of the M$ contribution will drastically change by finding out it was only 14k of “original” code? I doubt it.
    Looks like a slow news day to me.

    Jose_X Reply:

    I agree that this may not change anyone’s opinion, but, for accuracy’s sake, it’s quite off to count the diff program’s existing context lines and the repeating headers as your contribution. I think you can have diff spit our a larger number of context lines. If you do this, you can grow “your” contribution many-fold.

    JohnD Reply:

    Will the code work if you strip out the headers etc? Probably not.
    Is 30k of NEW code more worthy than 10k of new code? I don’t think so.
    When someone spouts off about how many lines of code they’ve written the first thing I wonder is – how much of it is bloat. I’m more impressed by code that works with as few lines as possible than anything else.
    If someone is measuring themselves by LOC, they have cranial-rectal inversion.
    A 5 line patch that fixes 100 bugs is more worthwhile then 50k lines of work around code.

    Jose_X Reply:

    Not C header files but the headings in the diff output.

    Eg, to patch a file, the patch program requires context lines and the file name to find out where to patch in the lines of code. These context lines (existing lines in the kernel) and file name headings are not source code to the kernel but rather are information created by “diff” for use by “patch” to carry out its work of patching the kernel properly. These lines are not written by Microsoft developers but are written by the diff program automatically using the existing kernel.

    I haven’t looked at the diff file but that is what I expect is going on here.

    zatoichi Reply:

    I haven’t looked at the diff file but that is what I expect is going on here.

    “I don’t actually know what I’m talking about, but that doesn’t stop me from talking about it anyway.”

  2. verofakto said,

    August 6, 2009 at 11:36 pm

    Gravatar

    How many lines of code have /you/ contributed to the Linux kernel, Roy?

    Just curious.

    zatoichi Reply:

    Roy hasn’t contributed any. Roy is an advocate. He “contributes” misinformation and slanted “news”—like this article—to a general reaction of derision amongst the folks who do actually contribute to FLOSS development.

    Roy is about “advocating” “freedom the way Roy tells you to.”

  3. zatoichi said,

    August 7, 2009 at 10:30 am

    Gravatar

    This is silly, Roy. As Linus has noted, Microsoft is no more “polluting the kernel with Microsoft APIs” by supplying these drivers than Intel is “polluting the kernel with Intel APIs” when they supply power management code for their CPUs.

    The fact is that you’re not in support of “Freedom Zero” here, the freedom to “run the program for any purpose“, Roy: you want to deny the folks who choose to run a Linux distro virtualized on a Windows Server 2008 system the liberty to do so.

    Why is that, Roy? (And do you support the FSF? If so, how, specifically? I’m still waiting to hear an answer on that one…)

DecorWhat Else is New


  1. IRC Proceedings: Tuesday, January 31, 2023

    IRC logs for Tuesday, January 31, 2023



  2. Links 31/01/2023: Catchup Again, Wayland in Xfce 4.20

    Links for the day



  3. Links 31/01/2023: elementary OS 7

    Links for the day



  4. Intimidation Against Nitrux Development Team Upsets the Community and Makes the Media Less Trustworthy

    Nitrux is being criticised for being “very unappealing”; but a look behind the scenes reveals an angry reviewer (habitual mouthpiece of the Linux Foundation and Linux foes) trying to intimidate Nitrux developers, who are unpaid volunteers rather than “corporate” developers



  5. Links 31/01/2023: GNOME 44 Wallpapers and Alpha

    Links for the day



  6. Free and Open Source Software Developers' European Meeting (FOSDEM) and KU Leuven Boosting Americans and Cancellers of the Father of Free Software

    The Free Software Foundation (FSF) and its founder, Richard M. Stallman (RMS), along with the SFLC one might add, have been under a siege by the trademark-abusing FSFE and SFC; Belgium helps legitimise the ‘fakes’



  7. Techrights in the Next 5 or 10 Years

    Now that I’m free from the shackles of a company (it deteriorated a lot after grabbing Gates Foundation money under an NDA) the site Techrights can flourish and become more active



  8. 60 Days of Articles About Sirius 'Open Source' and the Long Road Ahead

    The Sirius ‘Open Source’ series ended after 60 days (parts published every day except the day my SSD died completely and very suddenly); the video above explains what’s to come and what lessons can be learned from the 21-year collective experience (my wife and I; work periods combined) in a company that still claims, in vain, to be “Open Source”



  9. IRC Proceedings: Monday, January 30, 2023

    IRC logs for Monday, January 30, 2023



  10. Taking Techrights to the Next Level in 2023

    I've reached a state of "closure" when it comes to my employer (almost 12 years for me, 9+ years for my wife); expect Techrights to become more active than ever before and belatedly publish important articles, based on longstanding investigations that take a lot of effort



  11. The ISO Delusion: When the Employer Doesn’t Realise That Outsourcing Clients' Passwords to LassPass After Security Breaches Is a Terrible Idea

    The mentality or the general mindset at Sirius ‘Open Source’ was not compatible with that of security conscientiousness and it seemed abundantly clear that paper mills (e.g. ISO certification) cannot compensate for that



  12. Links 30/01/2023: Plasma Mobile 23.01 and GNU Taler 0.9.1

    Links for the day



  13. EPO Management Isn't Listening to Staff, It's Just Trying to Divide and Demoralise the Staff Instead

    “On 18 January 2023,” the staff representatives tell European Patent Office (EPO) colleagues, “the staff representation met with the administration in a Working Group on the project “Bringing Teams Together”. It was the first meeting since the departure of PD General Administration and the radical changes made to the project. We voiced the major concerns of staff, the organization chaos and unrest caused by the project among teams and made concrete proposals.”



  14. Links 30/01/2023: Coreboot 4.19 and Budgie 10.7

    Links for the day



  15. IRC Proceedings: Sunday, January 29, 2023

    IRC logs for Sunday, January 29, 2023



  16. [Meme] With Superheroes Like These...

    Ever since the new managers arrived the talent has fled the company that falsely credits itself with "Open Source"



  17. Not Tolerating Proprietary 'Bossware' in the Workplace (or at Home in Case of Work-From-Home)

    The company known as Sirius ‘Open Source’ generally rejected… Open Source. Today’s focus was the migration to Slack.



  18. The ISO Delusion: A Stack of Proprietary Junk (Slack) Failing Miserably

    When the company where I worked for nearly 12 years spoke of pragmatism it was merely making excuses to adopt proprietary software at the expense of already-working and functional Free software



  19. Debian 11 on My Main Rig: So Far Mostly OK, But Missing Some Software From Debian 10

    Distributions of GNU/Linux keep urging us to move to the latest, but is the latest always the greatest? On Friday my Debian 10 drive died, so I started moving to Debian 11 on a new drive and here's what that did to my life.



  20. Stigmatising GNU/Linux for Not Withstanding Hardware Failures

    Nowadays "the news" is polluted with a lot of GNU/Linux-hostile nonsense; like with patents, the signal-to-noise ratio is appalling and here we deal with a poor 'report' about "Linux servers" failing to work



  21. Microsofters Inside Sirius 'Open Source'

    Sirius ‘Open Source’ has been employing incompetent managers for years — a sentiment shared among colleagues by the way; today we examine some glaring examples with redacted communications to prove it



  22. Links 29/01/2023: GNOME 43.3 Fixes and Lots About Games

    Links for the day



  23. The Hey Hype Machine

    "Hey Hype" or "Hey Hi" (AI) has been dominating the press lately and a lot of that seems to boil down to paid-for marketing; we need to understand what's truly going on and not be distracted by the substance-less hype



  24. IRC Proceedings: Saturday, January 28, 2023

    IRC logs for Saturday, January 28, 2023



  25. Unmasking AI

    A guest article by Andy Farnell



  26. The ISO Delusion/Sirius Corporation: A 'Tech' Company Run by Non-Technical People

    Sirius ‘Open Source’ was hiring people who brought to the company a culture of redundant tasks and unwanted, even hostile technology; today we continue to tell the story of a company run by the CEO whose friends and acquaintances did severe damage



  27. Links 28/01/2023: Lots of Catching Up (Had Hardware Crash)

    Links for the day



  28. IRC Proceedings: Friday, January 27, 2023

    IRC logs for Friday, January 27, 2023



  29. Microsoft DuckDuckGo Falls to Lowest Share in 2 Years After Being Widely Exposed as Microsoft Proxy, Fake 'Privacy'

    DuckDuckGo, according to this latest data from Statcounter, fell from about 0.71% to just 0.58%; all the gains have been lost amid scandals, such as widespread realisation that DuckDuckGo is a Microsoft informant, curated by Microsoft and hosted by Microsoft (Bing is meanwhile laying off many people, but the media isn’t covering that or barely bothers)



  30. This is What the Microsoft-Sponsored Media Has Been Hyping Up for Weeks (Ahead of Microsoft Layoffs)

    Reprinted with permission from Ryan


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts