Slashdot Mirror


Greg Kroah-Hartman Gripes About Microsoft's Linux Contribution; MS Renews Effort

dp619 writes "Microsoft's developers were missing in action after the company donated GPL-licensed drivers to the Linux kernel community in July, leaving significant work to the Linux community, according to Linux driver project lead and Novell fellow Greg Kroah-Hartman. The company rekindled its involvement after Kroah-Hartman published a status report this week. Kroah-Hartman said that other companies were also laggards in Linux development, and that Microsoft's lack of involvement was nothing out of the ordinary."

213 comments

  1. Thanks by El+Lobo · · Score: 0, Funny

    Hmm.. did they forget to thank? It's quite common to cry about this and that... when the only think needed is to shut your mouth and THANK for the little help.

    --
    It's time to realise that Abble's products are the biggest abomination these days. Just say NO to the dumb iAbble way!!
    1. Re:Thanks by noundi · · Score: 3, Insightful

      Hmm.. did they forget to thank? It's quite common to cry about this and that... when the only think needed is to shut your mouth and THANK for the little help.

      If you're here to build me a bridge, then tell me so and build it. If you're here to bring me a stone, then don't tell me you're here to build me a bridge.

      --
      I am the lawn!
    2. Re:Thanks by Grishnakh · · Score: 4, Insightful

      Thank them for what? MS's contributed drivers are useless to anyone who isn't running MS's own hypervisor and Linux underneath (i.e., MS's customers). They didn't donate this code out of any altruism, only pure self-interest.

      So don't act like they're doing the Linux community any favors, because they're not.

      Sounds to me like MS dumped this pile of crap code on the kernel maintainers, and then faded away instead of sticking around to deal with the inevitable problems that result when trying to merge code into the mainline (i.e. fixing all the problems that the maintainers point out).

    3. Re:Thanks by FudRucker · · Score: 2, Interesting

      yup, that is why I would dump this code microsoft donated in to the trash = not even include it in the kernel, and just leave it up to microsoft to to offer it as a third party patch.

      --
      Politics is Treachery, Religion is Brainwashing
    4. Re:Thanks by nxtw · · Score: 2, Insightful

      Thank them for what? MS's contributed drivers are useless to anyone who isn't running MS's own hypervisor and Linux underneath (i.e., MS's customers). They didn't donate this code out of any altruism, only pure self-interest.

      Paying Hyper-V users will probably be running SLES or RHEL, and Microsoft provides support for SLES and RHEL in Hyper-V.

      And neither distribution will distributing a kernel new enough to have these drivers in the mainline source for a while.

    5. Re:Thanks by Desler · · Score: 1

      They didn't donate this code out of any altruism, only pure self-interest.

      And that's any different than any other corporation that contributes code to the Linux kernel, how?

    6. Re:Thanks by Grishnakh · · Score: 5, Insightful

      Yeah, I'd want to do that too. But if the kernel maintainers do that, it would look really bad and arbitrary (no one ever remembers MS's long, long history of unethical behavior), so to be fair, they have to accept the code.

      However, that doesn't mean they have to do MS's work for them. I've submitted kernel patches before (pretty minor ones), and part of the process is making your patch meet the standards of the maintainers: the coding style has to match the rest of the kernel (no Hungarian notation crap, which MS is a big fan of), and they usually find all kinds of nitpicky things they want fixed to meet their standards (which is a good thing; this is a place where perfectionism is useful). So it usually takes a few back-and-forth iterations before the patch is accepted and merged.

      If I, Joe User, were to submit a patch and then disappear, it would NOT make it into the kernel. They'd write back with their complaints, wait for me to resubmit with the fixes, and then forget about it when I never resubmit.

      MS shouldn't be treated any differently. They're not special, and a patchset of this size represents a lot of work to merge into the kernel. If MS wants it merged for the benefit of their customers, it's their responsibility to make the required changes, not expect it to be done for them.

    7. Re:Thanks by mocheeze · · Score: 0

      Yeah! And we should strip out every other patch from companies that contributed drivers that work with their hardware only! Down with Intel-specific drivers! They only work for Intel's customers, right?

    8. Re:Thanks by malus314 · · Score: 1

      They didn't donate this code out of any altruism, only pure self-interest.

      I'm not sure if that's the right way to be putting it. Isn't most code submitted out of pure self-interest, rather than altruism? "Scratching one's own itch", if you will? I agree, they're not doing the Linux community any favors, they dumped crap code on us and then bolted, but whether they did it out of self-interest or not doesn't seem like much of a point, and its not going to serve them much if the code is crap, because if its crap that doesn't scratch someone's itch, then no one will stick around to improve or maintain it. So if the code is really that bad, then what's going to happen is that it'll be abandoned, won't make it into the mainline kernel and MS will have ended up with a little bit of temporary publicity and nothing else, the community will move on, and MS will still be a bastard.

      All in all, I can't see this having any sort of major effect on anything, of course, I may be wrong....

    9. Re:Thanks by Grishnakh · · Score: 2, Informative

      Well, for one thing, most corporations that contribute code do so so that Linux will work better with their hardware. That's why a lot of the code comes from companies like Intel. As a Linux user with an Intel CPU, that makes me want to buy more Intel CPUs in the future.

      MS isn't a hardware company, it's a software company, and it competes directly with Linux.

      Anyway, other than this, it really isn't different, but several posters here are acting like it's some kind of useful contribution to Linux. It's not. It's only useful for MS customers running Hyper-V who want to run Linux on top of that.

      Just like it's incumbent on other kernel contributors to jump through the hoops necessary to make their code meet the maintainers' standards to be merged into the mainline kernel, MS has to do the same. They can't just dump the code on them and expect them to do all the work. Other companies already do it this way, because they want the code merged into the mainline, for the benefit of their customers. If MS doesn't do this, it's their customers who will suffer, not the Linux community at large.

      It's not like they're contributing something that's generally useful to most Linux users, like a codec or a font, or a filesystem. So stop acting like it is.

    10. Re:Thanks by Grishnakh · · Score: 3, Interesting

      Don't be stupid.

      When Intel contributes a patch, they go through the required process necessary to make the patch meet the maintainers' standards. I actually did this a couple times when I worked at Intel.

      If MS isn't going to do the work necessary to make their patches meet the standards, then it shouldn't be merged. I'm actually a little disappointed that they merged it in at all before going through this process fully.

    11. Re:Thanks by Grishnakh · · Score: 1

      I'm not sure if that's the right way to be putting it. Isn't most code submitted out of pure self-interest, rather than altruism?

      Yes, of course. I'm not saying MS should donate code out of altruism (though it'd be nice...). My point was that previous posters were acting like it was some kind of "gift" to the Linux community, and it's not. It's for their own purposes, and it would only benefit MS (and their customers using Hyper-V) if it were to be merged into the mainline. If they want that, then they need to do the work required to get it merged, and not expect the kernel maintainers to do it all themselves.

      So if the code is really that bad, then what's going to happen is that it'll be abandoned, won't make it into the mainline kernel and MS will have ended up with a little bit of temporary publicity and nothing else, the community will move on, and MS will still be a bastard.

      Exactly right.

      I'm not really complaining about MS here, I'm complaining about the other Slashdotters who are trying to paint MS's "contribution" as some kind of great gift, when it's not at all.

    12. Re:Thanks by socsoc · · Score: 1

      MS isn't a hardware company

      The MS mouse, keyboard, webcam, fingerprint reader, wireless card, wireless router, Xbox and Xbox 360 (with related peripherals) in my home beg to differ on the notion that they do not brand hardware. http://www.microsoft.com/hardware/

    13. Re:Thanks by Grishnakh · · Score: 1

      None of those require kernel drivers, except for the wireless card which uses a chipset made by a real hardware company like Broadcom or Marvell.

      "Hardware company" in this context means a company that makes semiconductors, not one that contracts with FlexTronics to make hardware for them using other company's off-the-shelf chips.

    14. Re:Thanks by ThePhilips · · Score: 1

      You forgot Oracle.

      But IMO it make no difference. The whole point of GPL is to create leveled ground for cooperation so that all participants can benefit.

      MS benefits because one more OS would run well under its VM. Linux benefits because it has now one more supported platform.

      If MS drops from the cooperation and nobody would step in to support the code, then the code is really useless and there is no hard removing it.

      --
      All hope abandon ye who enter here.
    15. Re:Thanks by Qubit · · Score: 4, Funny

      Hmm.. did they forget to thank? It's quite common to cry about this and that... when the only think needed is to shut your mouth and THANK for the little help.

      If you're here to build me a bridge, then tell me so and build it. If you're here to bring me a stone, then don't tell me you're here to build me a bridge.

      Oh, cry me a river...

      --

      coding is life /* the rest is */
    16. Re:Thanks by Desler · · Score: 1

      Well, for one thing, most corporations that contribute code do so so that Linux will work better with their hardware.

      Which means they aren't contributing out of altruism but in their own self-interest. Way to refute yourself in the same sentence.

      It's not like they're contributing something that's generally useful to most Linux users, like a codec or a font, or a filesystem. So stop acting like it is.

      Funny cause I never made any such claim. Secondly, what do codecs and fonts have to do with kernel hacking? And secondly, most corporate contributions are really of no benefit but to themselves and their own hardware/software platforms and not to the users at large.

    17. Re:Thanks by Grishnakh · · Score: 1

      You forgot Oracle.

      That's a good point, but Oracle (before the Sun acquisition, which still hasn't been approved) doesn't make OSes, only software that runs on top of them. So just like the hardware makers, it's to Oracle's benefit to support Linux if their customers demand it. Plus, I've heard Larry Ellison really hates Bill Gates and MS.

      How the Sun/Oracle merger would affect Oracle's relationship with Linux, I don't know.

    18. Re:Thanks by Grishnakh · · Score: 1

      Funny cause I never made any such claim.

      Way to miss out on context. You didn't make that claim, "El Lobo" did when he wrote:

      Hmm.. did they forget to thank? It's quite common to cry about this and that... when the only think needed is to shut your mouth and THANK for the little help.

      which started this entire thread.

      I never refuted myself. I'm simply pointing out that this isn't some kind of "gift" like MS sycophants such as El Lobo are trying to convince us it is. You should take some reading comprehension courses, because you completely misunderstood my post.

      Secondly, what do codecs and fonts have to do with kernel hacking?

      Nothing. Those are simply examples of things that MS already has (and does fairly well with) which they could donate to the OSS community if they wished to be altruistic.

    19. Re:Thanks by Anonymous Coward · · Score: 0

      You're an idiot. You are either too stupid to distinguish between what you are arguing and the GP is saying or you are intentionally being obtuse.

      Either way, my sentiment stands.

    20. Re:Thanks by ThePhilips · · Score: 1

      You are stepping into dangerous waters.

      Single Oracle license can buy you a lot of OS licenses - along with servers for the change.

      Oracle is as evil as MS. If not more: their involvement with Linux is what in greater part makes up for the server bias in development as Linux became in past years the top Oracle platform. IOW, they one of the largest supporters of ruining Linux on desktop, as fat chunk of Red Hat and Novell profits comes from supporting and selling certified Oracle platform.

      --
      All hope abandon ye who enter here.
    21. Re:Thanks by Anonymous Coward · · Score: 1, Funny

      they dumped crap code

      In Microsoft's defense, I've used quite a few of their products over the years and if the quality of those products is any indication, I can but assume that they figured the code they contributed to the kernel was actually really good. In essence, they probably just don't know any better.

      Why anyone would expect quality code to come out of MS, I don't understand. That's like going to McDonald's and expecting a gourmet meal. Sure, I could always go back up to the counter, Big Mac in hand, and patiently explain how I came really expecting champagne and caviar, but I would probably just succeed in getting myself thrown out.

      Hopefully, this sheds some light on the situation we have under scrutiny here.

    22. Re:Thanks by PixetaledPikachu · · Score: 1

      >

      Anyway, other than this, it really isn't different, but several posters here are acting like it's some kind of useful contribution to Linux. It's not. It's only useful for MS customers running Hyper-V who want to run Linux on top of that.

      "Who want to run Linux on top of that"? Don't you mean "RHEL/SLES customers"

    23. Re:Thanks by Grishnakh · · Score: 1

      Single Oracle license can buy you a lot of OS licenses - along with servers for the change.

      I don't think Oracle customers are running Linux just to save money on MS licenses; I think they simply prefer the platform.

    24. Re:Thanks by Vancorps · · Score: 3, Insightful

      No offense but you just sound like a rabid anti-Microsoft person who would hate anything they do simply because they are the ones doing it. The reality is that all corporations have self interest at heart when contributing to the Linux community. IBM for one mainly sells software services for Linux/Unix even though they also sell hardware. Oracle sells purely software but have always supported Linux/Unix.

      The reality is that I went with XenServer instead of Hyper-V because Linux wasn't a supported guest OS. Since MS has made this change their product is much more competitive with the other players who support multiple operating systems. Microsoft's customers won't suffer because MS doesn't offer drivers for a VM, they will simply migrate to another platform which happens to free.

      As far as most Linux users I think you are way the hell off base in that every shop I have ever encountered runs some Windows in their environment and those people will find that virtualizing their infrastructure saves them a ton of money especially since they already bought their Windows license. Get off your anti-MS high horse and come back to reality friend, it's not as bad as you make it out to be. MS is finally starting to embrace the Linux community and they face criticism the whole way, it's a stupid way of doing business and an even less intelligent method of getting what you want which is interoperability between all the major platforms. If only Apple would play so well with others... given the state of networked support in OS X I think your rabid hatred is best reserved for them although I can understand a strong distaste of Windows too.

      For those of us out there that run just about everything, we'll continue on and enjoy the small improvements each platform makes and encourage continued improvement from all sides.

    25. Re:Thanks by Vancorps · · Score: 1

      As a Oracle customer that runs Linux I can say that cost savings plays a lot into it given that I have a named user license for 10g allowing me to run many servers in a RAC providing real up-time. Because I don't have to pay for licenses on every server I get the benefit of high availability without the usual costs and for a relatively small business that means a lot! I can state that Oracle runs just as well on Windows as it does on Linux as I run both for mitigation purposes and because it's convenient to have a single log shipping server for both Oracle and SQL Server which I'm required to run for our general ledger application which accounting purchased without consulting me.

    26. Re:Thanks by BitZtream · · Score: 1

      You got the source, which is generally what you whine about, you knew EXACTLY what you got, thats the advantage of the source thats touted as one of the awesome benefits of OSS.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    27. Re:Thanks by BitZtream · · Score: 2, Funny

      So I guess the people who run Linux on MS servers aren't part of the Linux community?

      I guess the poor guys that have to do this sort of thing because some manager says so, aren't cool enough to be part of your retarded little club?

      Get a grip, god Linux fanboys are a pile of whiney bitches. Add another thing to the list of reasons Linux will always be the third world country of software world, no one likes a bunch of whiney bitches.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    28. Re:Thanks by Anonymous Coward · · Score: 0

      Hey Grishnakh, if you turn their code into goblin style then do not expect MS or anybody else to return back or contribute further, pretty obvious.

    29. Re:Thanks by Grishnakh · · Score: 1

      They might be RedHat or Novell customers, but if they're running Hyper-V, then by definition they're also MS customers.

      If this is that important to RH and Novell, maybe they can do the work necessary for getting these patches merged. I guess we'll see soon how important that is to any of these 3 entities.

    30. Re:Thanks by Trongy · · Score: 2, Informative

      Ever heard of back ports? Redhat does this quite a lot. New drivers into their own kernel tree. Redhat's latest 2.6.9 kernel in RHEL4 is way different to the one Linus released all those years ago.

    31. Re:Thanks by Anonymous Coward · · Score: 2, Insightful

      Beggars cannot be choosers and like it or not, Linux community = beggars.

    32. Re:Thanks by drsmithy · · Score: 4, Insightful

      They didn't donate this code out of any altruism, only pure self-interest.

      Everyone using the GPL is doing so out of self-interest. If it was altruism, they'd be released their code into the public domain.

    33. Re:Thanks by im_thatoneguy · · Score: 2, Insightful

      But aren't we just seeing this process dramatized before us.

      Microsoft: "Here you go. Hyper-V Code."
      Kernel Maintainer: "Wait. There are some problems with it that you need to deal with or we aren't going to include it in the kernel."
      [Slashdot story]
      Microsoft: "Oh we'll look into that."

      If Microsoft cares enough about getting it into the Kernel they'll fix it. Otherwise they wont... problem solved.

    34. Re:Thanks by beuges · · Score: 1

      MS isn't a hardware company, it's a software company, and it competes directly with Linux.

      Anyway, other than this, it really isn't different, but several posters here are acting like it's some kind of useful contribution to Linux. It's not. It's only useful for MS customers running Hyper-V who want to run Linux on top of that.

      SO WHAT?

      If MS doesn't do this, it's their customers who will suffer, not the Linux community at large.

      Are you saying that the people that run linux on microsoft platforms don't count? You keep on going on about how this only benefits people running linux on windows servers, but really, SO FUCKING WHAT?

      Why is Intel allowed to make drivers that directly benefit running linux on only intel hardware, but when microsoft delivers a driver that benefits linux running on a microsoft hypervisor, suddenly that's being greedy and the contribution is worthless?

      Both intel and microsoft are providing a platform on which linux runs. Intel's happens to be actual hardware, microsoft's happens to be a virtualized environment. Either way, it doesnt fucking matter because they have contributed a driver that improves the performance of running linux on a particular platform, yet because it's from the evil microsoft, you refuse to acknowledge the benefit of it.

      Or is software contributed under the GPL only worthwhile if it meets your sophisticated requirements?

      If MS doesn't do this, it's their customers who will suffer, not the Linux community at large.

      No, you are so very wrong. The customers that this driver will benefit are already running windows servers, and have decided to virtualize linux on top of that, instead of virtualizing windows on top of linux. If the linux performance sucks because people like you are too arrogant to work with microsoft patches, then those companies will simply decide that linux doesn't suit their needs and move the software they were planning on running in linux, onto windows. So the linux community will suffer, not MS.

      It's not like they're contributing something that's generally useful to most Linux users, like a codec or a font, or a filesystem. So stop acting like it is.

      So a driver that improves linux's performance on a new platform isn't useful? Please pull your head out of your ass and stop looking at it as something from the evil microsoft corporation, and instead see it as something beneficial to the linux community.

      This xkcd comic seems like it was written especially for you

    35. Re:Thanks by msclrhd · · Score: 2, Interesting

      Don't you mean;

      Microsoft: Here is a binary Linux kernel module for Hyper-V.
      Someone: But wait... it is using GPL-only kernel interfaces.
      Microsoft: Oh, er...
      Grek KH: You need to release the code to be compliant.
      Microsoft: Here you go. Here is the code for the driver.
      Microsoft PR: Microsoft has generously donated a lot of code to the Linux kernel under the GPL license. We did this because it is the right thing to do.
      [Slashdot story #1]
      [Greg KH spends a lot of time thanklessly getting the code to the point where it is ready for inclusion with the kernel.]
      [Greg KH sends e-mail to Microsoft asking for help.]
      [Greg KH posts a summary for the upcoming .32 drivers.]
      [Slashdot story #2]
      Microsoft: Ok, we'll help maintain it.
      Microsoft PR: Microsoft is actively involved with the Linux community.

    36. Re:Thanks by TheRaven64 · · Score: 1

      So are a lot of people making public domain contributors. People like the contributors to SQLite do so because it's easier for them to have their patches in the main tree than to maintain a fork.

      --
      I am TheRaven on Soylent News
    37. Re:Thanks by GaryOlson · · Score: 2, Interesting

      I think the mods are on crack again. This is a plausible scenario -- not thru malicious action on MS part but just the inevitable turpitude of a large uncaring monopoly.

      --
      Every mans' island needs an ocean; choose your ocean carefully.
    38. Re:Thanks by Simetrical · · Score: 1

      Thank them for what? MS's contributed drivers are useless to anyone who isn't running MS's own hypervisor and Linux underneath (i.e., MS's customers). They didn't donate this code out of any altruism, only pure self-interest.

      Um, so what? Are you forgetting that at least 80% of kernel development is done by people paid by corporations? Red Hat and Novell aren't bankrolling Linux development out of altruism any more than Microsoft is. Since when should altruism be expected of any for-profit corporation?

      --
      MediaWiki developer, Total War Center sysadmin
    39. Re:Thanks by Simetrical · · Score: 2, Informative

      Don't be stupid.

      When Intel contributes a patch, they go through the required process necessary to make the patch meet the maintainers' standards. I actually did this a couple times when I worked at Intel.

      If MS isn't going to do the work necessary to make their patches meet the standards, then it shouldn't be merged. I'm actually a little disappointed that they merged it in at all before going through this process fully.

      It hasn't been merged to drivers/ proper, only drivers/staging/. This is the normal procedure these days for subpar driver code: it gets merged to staging/ in the hopes it will be cleaned up and can be merged to mainline proper.

      --
      MediaWiki developer, Total War Center sysadmin
    40. Re:Thanks by Grishnakh · · Score: 1

      I'm getting really sick of this discussion with you idiotic MS sycophants. Please explain to me why when Intel contributes a driver, Intel goes through all the necessary work to make their driver meet the Linux maintainer's standards, but when MS contributes a driver, MS is somehow excused from all that work.

    41. Re:Thanks by akleos · · Score: 1

      Then you could build a bridge over it...

    42. Re:Thanks by Anonymous Coward · · Score: 0

      And therefore... A WITCH!!

    43. Re:Thanks by Anonymous Coward · · Score: 0
  2. Of course. by NoYob · · Score: 1, Interesting

    Kuhn credited the community for using a "friendly" strategy to enforce GPL by quietly working with Microsoft to inform it of its obligations, and by helping the company into compliance.

    If you're over zealous about it, MS will just stop contributing. They really don't have much to gain financially from this and as far as PR is concerned, well, I have a feeling that MS' actions won't be good enough for some in the F/OSS community.

    --
    It's NOT me! It's the meds! I'm on 1000mg of Fukitol.
    1. Re:Of course. by Anonymous Coward · · Score: 2, Insightful

      'scuse me?
      They weren't contributing out of the goodness of their hearts?
      They were legally obligated to, and since then have avoided doing much of anything further.

      It wasn't over zealousness. If they hadn't been reminded of their obligation they wouldn't have contributed at all.

    2. Re:Of course. by petrus4 · · Score: 1, Interesting

      If you're over zealous about it, MS will just stop contributing.

      Bradley Kuhn is a dangerous fanatic. If there's one thing I'm tired of around here, it is people who are willing to condemn Microsoft as being entirely evil on the one hand, yet completely overlook individuals among their own who behave in largely the same ways.

      Also, for anyone who wants to me to cite sources to back up the claim that Kuhn is evil, just ask. There's any amount of material on the Web, and I'm more than happy to link to it.

    3. Re:Of course. by Grishnakh · · Score: 1, Insightful

      If you're over zealous about it, MS will just stop contributing.

      So what? They haven't contributed anything useful anyway. This "contribution" was only so their own customers, running MS's hypervisor, could better run Linux underneath. For Linux users not running MS's hypervisor (99.999% of them), it's completely useless.

      Wake me when MS actually contributes something genuinely useful to FOSS, such as some fonts or codecs or something.

    4. Re:Of course. by NoYob · · Score: 0
      Obligation?

      They could have changed their minds and released the drivers under a different license, kept the source to themselves, and there's nothing anyone could have done about it.

      --
      It's NOT me! It's the meds! I'm on 1000mg of Fukitol.
    5. Re:Of course. by h4rr4r · · Score: 4, Insightful

      No, they were violating the GPL.
      They had to at least give source to their customers.

      Rather than to continue to do that they made this driver the kernel maintainers problem. If they don't want to help maintain it, I say drop it from the kernel.

    6. Re:Of course. by Tubal-Cain · · Score: 3, Insightful

      If they don't want to help maintain it, I say drop it from the kernel.

      Indeed. Just because they are obligated to release it, that doesn't mean the Linux kernel is obligated to use it.

    7. Re:Of course. by schon · · Score: 1

      for anyone who wants to me to cite sources to back up the claim that Kuhn is evil, just ask

      Let's see: a guy who works for the FSF and SFLC, helps enfoce the GPL? Yeah, that's real evil.

      I'm guessing that since you didn't include your "sources", that you need time to fabricate them?

    8. Re:Of course. by 7+digits · · Score: 1

      Go ahead, post the links...

    9. Re:Of course. by BitZtream · · Score: 1

      No, they didn't, they could have simply rewritten it sans GPL, contrary to popular belief, its really not that hard, hence why they've managed to do it and ... hate to burst your bubble, produce a far more set of products.

      Don't get cocky with the 'they had to do it' bullshit, they could have stopped distributing the drivers until the rewrote them.

      More likely, they would have put this in their media kit to point out why people who work with Linux are retarded and why you as a business don't want to have anything to do with Linux if you want someone you don't have to worry about.

      You guys talk shit about how MS behaves but could you all please stop acting like a 7 year old?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    10. Re:Of course. by petrus4 · · Score: 1

      http://linux.omnipotent.net/article.php?article_id=12503

      This is probably about the most incriminating one that immediately springs to mind.

    11. Re:Of course. by gbjbaanb · · Score: 1

      Incriminating? That's an opinion piece, which barely describes what he's opinioning about. I think it had something to do with a discussion regarding the old hippie 'property is theft' mantra, but I'm not sure.

      Mainstream companies are beginning to get with this anyway, very many are into open source as a free product that is monetised in non-standard ways. Its no longer about making money by selling software, but selling services. That's hardly an extreme viewpoint anymore, especially when you consider you never buy software in the first pace, but a licence to use it.

    12. Re:Of course. by petrus4 · · Score: 1

      The incriminating part was Kuhn's implication that the GPL is the only license which should exist. Of course, thankfully there is no way for him to enforce such a position; but if he has it, that in itself is alarming enough.

    13. Re:Of course. by gbjbaanb · · Score: 1

      There are people who think that the only software that should be used is Microsoft's. I suppose that's a similarly extreme view, however, in the case of the GPL licence(s) if he takes the view that all software should follow the open source methodology, then only having the GPL as a licence is not so extreme. Perhaps he means all OSS should be licenced under the GPL only, I think that's the view of the FSF.

    14. Re:Of course. by Simetrical · · Score: 1

      So what? They haven't contributed anything useful anyway. This "contribution" was only so their own customers, running MS's hypervisor, could better run Linux underneath. For Linux users not running MS's hypervisor (99.999% of them), it's completely useless.

      The same applies to essentially all drivers. If you aren't using piece of hardware X, it's useless. So what? So it makes Linux more useful for the ones who do want to use this product. Interoperability and compatibility are only good things.

      --
      MediaWiki developer, Total War Center sysadmin
    15. Re:Of course. by 7+digits · · Score: 1

      Thanks for posting the links, even if I'm afraid that I have to tag them "tl;dr". It seems that the article is a claim of evilness for the following Kuhn statements:

      I believe strongly that all published software should be Free Software. Users should get all the freedoms as defined in the Free Software Definition and Today, some argue that the "right to choose your own software license" is the greatest software freedom. By contrast, I think that, like slavery, it is an inappropriate power, not a freedom. are the points of contention.

      Well, first, I write proprietary software for a living, and I don't think that his position is particularly "evil". Extreme, yes. Evil ? Not that sure. I can see his point that law should be written to avoid enslavement of people by software. If you think in the long term, it sortof make sense:

      See, when copyright was created, it was absolutely reasonable, and served the purpose of information and culture diffusion. Today, you don't have the right to sing Happy Birthday in a movie. And you will never have it again.

      So, I can totally understand the FSF concern that, in some not so distant future, you may be totally locked out of software you use, due to restrictive licensing. I can easily envision a world where you can't develop an application that send data on the internet without having to pay for a specific license, and in which that license will only be granted by an opaque process, where you can be locked out if your application is not welcome.

      So, it is his opinion, it is maybe excessive, but I don't find the guy "evil" for that...

    16. Re:Of course. by Grishnakh · · Score: 1

      Yes, that's why the people who care about that driver do the necessary work to get it merged in, instead of just throwing some code at the maintainers and expecting them to do it all.

    17. Re:Of course. by Simetrical · · Score: 1

      Yes, that's why the people who care about that driver do the necessary work to get it merged in, instead of just throwing some code at the maintainers and expecting them to do it all.

      Except when they don't, like the authors of the half-dozen other drivers GKH mentioned he'll cut for 2.6.32 if he doesn't see some activity. Microsoft is fairly typical here for a new Linux kernel contributor. Long-established companies like Intel that commit tons of high-quality code to support their hardware are the exception, not the rule. Heck, Google was one of the ones Greg panned in his status report, for being uninterested in getting Android drivers into shape, and they're a quite significant kernel contributor.

      The ones turning this into an anti-Microsoft flamefest are really not being reasonable. No, Microsoft didn't do a lot more than it had to do, but it's hardly special in that regard. I certainly hate MS just as much as the next Slashdotter, but let's keep our heads on straight. We should be flaming Microsoft for its genuinely reprehensible behavior, like its anticompetitive practices, not for not being as enthusiastic as we'd like in cleaning up a driver for one of its largest competitors. Looking only for the worst in everything MS does just paints us as deranged extremists. (Which, sadly, some of us are.)

      --
      MediaWiki developer, Total War Center sysadmin
    18. Re:Of course. by Grishnakh · · Score: 1

      We should be flaming Microsoft for its genuinely reprehensible behavior, like its anticompetitive practices, not for not being as enthusiastic as we'd like in cleaning up a driver for one of its largest competitors. Looking only for the worst in everything MS does just paints us as deranged extremists. (Which, sadly, some of us are.)

      THIS is exactly what I'm really sick of explaining over and over here. I never flamed MS for not being enthusiastic about cleaning up its stupid driver. This whole discussion started when some moron named "El Lobo" painted this as an altruistic gift from MS that the Linux community should be thankful for, and I pointed out that it's no gift at all, just something to help their own customers, and they shouldn't expect any special favors. Hit "Parent" a few times and you'll see what I'm referring to.

    19. Re:Of course. by Anonymous Coward · · Score: 0

      They had to? Had to *OR WHAT*?

      The GPL is the most toothless thing in the world. There simply is nothing enforceable after the "or what" UNLESS you happen to repackage the GPLd product of a major and well funded firm which itself controls all or nearly all of the code in question.

       

  3. Not shocked... by filesiteguy · · Score: 3, Informative

    From the blog,

    "hv (Microsoft Hyper-V) drivers. Over 200 patches make up the massive cleanup effort needed to just get this code into a semi-sane kernel coding style (someone owes me a bit bottle of rum for that work!) Unfortunately the Microsoft developers seem to have disappeared, and no one is answering my emails. If they do not show back up to claim this driver soon, it will be removed in the 2.6.33 release. So sad..."

    In other words, there is some coding to do. Did the Kernel devs coordinate with the managers at MS to ensure resources would be available to work on these patches? (200 patches is not a lot in my opinion. I have a minor patch coming out on the 21st for my in-house system with 2000+ users and it has over 300 fixes.)

    I wonder if there was a minor miscommunication... ...hmm - hyper-v in Linux?

    Cool!

    1. Re:Not shocked... by ma1wrbu5tr · · Score: 1

      That seems a little risky. 300 fixes in a single patch? Hope you're not patching the dB that way.

      --
      Why can't we go back to using jumpers to configure slot adapter cards? Why? I say!
    2. Re:Not shocked... by thatkid_2002 · · Score: 1

      The code is not for the Hyper V hypervisor to run in Linux - it is for Linux to run properly in Hyper V on Windows.
      The code is just extensions like VMware Tools or VIrtualbox Guest Additions. There is probably some links for better I/O and stuff like that.

    3. Re:Not shocked... by filesiteguy · · Score: 1

      Patching the DB? No - these are modules that are being either patched, updated, or added. This is a pretty big program with over 350,000 lines of (C#) code, some 80 assemblies on the servers (there are about 35 servers running the application services) and handles around 2,000 simultaneous users. The database is decent sized - it has around 80 tables. Some of the bigger ones have more than 275,000,000 rows.

      I have seven developers writing and fixing code and five analysts testing, reporting bugs and validating fixes.

      Nah, 300 fixes isn't *that* big a deal. :P

      The really big deal - and the reason we've been testing this build for over a month already - is the fact that we are now ready to accept credit/debit card payments as a payment type in the point-of--sale module. We previously only had cash, check and house charges. Now all the accounting functions have to ensure proper accountability of the new payment type and all 78 reports need to be able to property credit where appropriate.

  4. Kinda funny. by palegray.net · · Score: 3, Insightful

    I don't get it. Microsoft donates code to the community, licensed under the GPL. Anyone is free to do whatever they like with this code (well, within the constraints of the license), and people are actually bitching about this? I've released quite a few pieces of software under various OSI licenses, and I don't actively maintain the code. If somebody else wants to, fine. Would everyone be happier if Microsoft weren't releasing anything at all?

    I use Debian for almost all my server needs, and I'm a big fan of Ubuntu on the desktop. That said, I'm certainly not going to bitch at someone or some company because they aren't slaving away maintaining code I got free of charge.

    1. Re:Kinda funny. by Desler · · Score: 3, Insightful

      Because it's Microsoft and no matter what they do these people will still criticize them regardless.

    2. Re:Kinda funny. by QuantumG · · Score: 3, Funny

      Wow, did you not even read the summary? Greg KH bitches about everybody.

      --
      How we know is more important than what we know.
    3. Re:Kinda funny. by shentino · · Score: 3, Insightful

      MS only gave it because they got caught with their hands in the open source cookie jar and nanny GPL made them sit in the sharing corner.

    4. Re:Kinda funny. by Desler · · Score: 1

      I was talking about the point in general. Yes, I did read the summary and know that he's bitched at other companies. Though it seems that he has the generosity to not publicly flame them unlike Microsoft.

    5. Re:Kinda funny. by Desler · · Score: 4, Insightful

      Well then they released what they were supposed to so either take it or shut up.

    6. Re:Kinda funny. by Bill,+Shooter+of+Bul · · Score: 4, Interesting

      A good point. Anyone is free to do what ever they like with the gpl donated code that doesn't violate the gpl. That includes not including it in a future official Linus sanctioned Linux kernel. But, I think GKH is trying to get companies to stay active in development of their own donated code,using the carrot of inclusion in the Official Linus Kernel. That's not a bad idea. Someone has to fund the ongoing maintenance costs of the drivers.

      As the drivers usage primarily benefits Microsoft, why not them?

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    7. Re:Kinda funny. by clang_jangle · · Score: 4, Informative

      As was mentioned earlier, MS got caught infringing and so *had* to "donate" the code in question. They did the minimum they could get away with, no big surprise there...

      --
      Caveat Utilitor
    8. Re:Kinda funny. by QuantumG · · Score: 5, Insightful

      No, you're wrong. Whereas everyone else sees contribution of code as a nice bit of corporate philanthropy, Greg KH sees something completely different. He sees it as corporations dumping their code on the community so they can off-load its support. As such, he often calls on corporate contributors to step up and fund a developer or two to work on the kernel full time. This flame is no different.

      --
      How we know is more important than what we know.
    9. Re:Kinda funny. by petrus4 · · Score: 0, Flamebait

      I don't get it. Microsoft donates code to the community, licensed under the GPL. Anyone is free to do whatever they like with this code (well, within the constraints of the license), and people are actually bitching about this? I've released quite a few pieces of software under various OSI licenses, and I don't actively maintain the code. If somebody else wants to, fine. Would everyone be happier if Microsoft weren't releasing anything at all?

      In the minds of the neurological cripples who are bitching about this, Microsoft are the Great Satan, no matter what.

      It doesn't matter what they do; it's always part of an Evil Plot. At this point, Steve Ballmer could donate the entirety of Microsoft's net worth to World Vision if he wanted to, and the FSF would still try and portray him laughing maniacally in the background.

    10. Re:Kinda funny. by palegray.net · · Score: 2, Interesting

      I have to admit, that's one of the funniest ways I've heard such a process described :). All the same, they have released the code. This isn't the first time something like this has happened, and it certainly won't be the last. I'd just like to see more positive reinforcement, lest their devs lose any inclination to release code voluntarily in the future.

    11. Re:Kinda funny. by petrus4 · · Score: 1, Insightful

      MS only gave it because they got caught with their hands in the open source cookie jar and nanny GPL made them sit in the sharing corner.

      I know this has been modded insightful, but am I the only one who's noticed how chronically juvenile it also sounds?

    12. Re:Kinda funny. by Anonymous Coward · · Score: 2, Insightful

      Welcome to crowdsourcing, my friend! The new corporate model where pathetic geeks will be exploited by the big moguls, and just see promises of profit sharing. After you make my code work, I will close the source, become richer than I already am, and you will go back to watch online pr0n and play WoW...

    13. Re:Kinda funny. by palegray.net · · Score: 1

      Yeah... I'm kind of impressed that my original post is still moderated above zero.

    14. Re:Kinda funny. by ma1wrbu5tr · · Score: 1

      Greg, is this you? Or are you just wearing his glasses?

      --
      Why can't we go back to using jumpers to configure slot adapter cards? Why? I say!
    15. Re:Kinda funny. by shaitand · · Score: 1

      Microsoft didn't donate anything. They were violating the GPL and preemptively released this source before they were caught. The code also is only of benefit to microsoft customers.

    16. Re:Kinda funny. by petrus4 · · Score: 0, Offtopic

      Yeah... I'm kind of impressed that my original post is still moderated above zero.

      LOL. Yes, I wrote a rant about that as well. I'm fully expecting it to go down to -1. Two of my other comments in this thread have already been hit.

      "Onward, brothers! Comrades Stallman and Kuhn appreciate your efforts! The enemies of freedom must be stopped!"

    17. Re:Kinda funny. by Anonymous Coward · · Score: 0

      > and you will go back to watch online pr0n and play WoW...

      Is that part really such a bad thing?

    18. Re:Kinda funny. by Anonymous Coward · · Score: 0

      He has complained about the lack of contribution of other companies before as well, such as Ubuntu for example, who do not contribute to the kernel at all. There's a video on youtube of a speech he gave at Google, where he mentions that fact.

    19. Re:Kinda funny. by Anonymous Coward · · Score: 0

      To only share code because you were using someone else's work illegally? Yeah, that is pretty juvenile, but it's about what we expect from Microsoft, honestly.

    20. Re:Kinda funny. by LordNimon · · Score: 0, Troll

      That's true, but it also demonstrates the Microsoft's Linux developers are second-rate, at best. If I were a hiring manager, and I got a resume from a Microsoft employee who claims to have worked on the Linux kernel, I would assume that can't write code properly.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    21. Re:Kinda funny. by Anonymous Coward · · Score: 0

      That they released puts the kernel team under no obligation to do anything whatsoever with it. If MS doesn't want their Hyper-V drivers to be an abortion, they'll have to do more than an infodump.

    22. Re:Kinda funny. by Anonymous Coward · · Score: 0

      Shut up! You're not the boss of me!

    23. Re:Kinda funny. by LearnToSpell · · Score: 3, Funny

      I don't think the GPL has a defined coding style. Maybe we can put that in v.4.

    24. Re:Kinda funny. by palegray.net · · Score: 1

      Let's have a little positive reinforcement for doing the right thing, even in light of the circumstances. This can go a long way toward encouraging developers within Microsoft to push open source initiatives in the company, whereas lambasting them at every opportunity does nothing but reinforce stereotypes about "crazy open source people" in their community.

      Frankly, I don't care if the code only benefits Microsoft customers. I choose to use Linux on my servers, along with Linux and MacOS X on the desktop. That doesn't mean open source code targeted at my platforms is any more "worthy" than code targeted at Windows. To believe otherwise is simply naive. People use what they believe best fits their needs; I encourage open behavior on any platform.

    25. Re:Kinda funny. by pembo13 · · Score: 2, Insightful

      I think the point is, that kernel contributions in general, even if it's MS, don't get included just because they exist. In fact, it is my understand that patches more often get rejected than accepted. If this contribution less public, and not not from MS, it might have been rejected outright.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    26. Re:Kinda funny. by symbolset · · Score: 3, Funny

      I'd just like to see more positive reinforcement, lest their devs lose any inclination to release code voluntarily in the future.

      This code supports Linux guests in Hyper-V. In other words, it takes the legendary speed, security and stability of Windows and fuses it to the famous app compatibility and user friendliness of Linux.

      It's fair to say the world is better off without it. I'd just as soon people didn't encourage such foolishness.

      --
      Help stamp out iliturcy.
    27. Re:Kinda funny. by Anonymous Coward · · Score: 0

      first of all, they "donated" it after they were found to be infringing on the GPL in the same code.

      secondly, GregKH called them out because MS gave code which they wanted integrated into linux, so linux would work right on windows server 2008 virtualization (running as a virtual machine inside win2008 server). (so they were going to benefit too!) but expecting kernel devs to fix their shit.

    28. Re:Kinda funny. by Anonymous Coward · · Score: 0

      No, they didn't. There was a even Slashdot article referencing a first-hand source saying this wasn't the case, but the FOSS-tards here will ignore reality and substitute their own.

      That doesn't mean MS is nice. They probably did just dump the driver so they could satisfy their requirements with RedHat's contract and get the hell out of Dodge.

    29. Re:Kinda funny. by Anonymous Coward · · Score: 0

      Ubuntu not contributing to the kernel is a good thing. Read the Ubuntu forums for an hour and tell me you'd trust that collection of morons to write code for your machine.

    30. Re:Kinda funny. by quickOnTheUptake · · Score: 1

      How has this not been modded up? Thanks for making my week.

      --
      Mod points: Guaranteed to remove your sense of humor.
      Side effects may include gullibility and temporary retardation
    31. Re:Kinda funny. by shentino · · Score: 1

      There was an article on either the register or ars that reported them using GPL'ed code in one of their virtualization dealies.

    32. Re:Kinda funny. by shaitand · · Score: 1

      "People use what they believe best fits their needs; I encourage open behavior on any platform."

      I encourage open behavior as well but I don't go so far as to believe that someone who commits copyright infringement and then only does the right thing in an attempt to avoid paying the debt their illegal action incurs deserves a pat on the back.

      Even at that, the driver they opened serves only one purpose, to attempt to drive people away from the open solutions that already dominate this area and to Microsoft's proprietary virtualization solution.

    33. Re:Kinda funny. by a_n_d_e_r_s · · Score: 1

      Yes you are. You might not like it but slashdot is an internet phenom and as such many different persons from many different countries post here. So you really need to take that into consideration when doing character asassinations.

      --
      Just saying it like it are.
    34. Re:Kinda funny. by BitZtream · · Score: 1

      Yea, cause its not like they don't have the resources to write it without any GPL code ... or even better, point out how dangerous it is to deal with GPL in general and just drop support on the grounds that its not worth their time, add it to their press kit, then watch you guys scream some more that they are spreading FUD when it starts to look more and more like you're just a bunch of whiney angst ridden high school students that hate everyone/thing/where and can't be pleased regardless.

      The more idiots the rant about shit like this, the smaller GPL and Linux is going to look. The only people who appreciate GPL at this point are people who go out of their way to ensure that no one can make a profit off the work put into GPL'd code.

      So ... brilliant programmers ... when no one pays you to code, are you going to be ready to pickup the phone and do desktop support, since thats going to be whats going to pay your bills. For intelligent people, you guys do some really stupid shit.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    35. Re:Kinda funny. by shentino · · Score: 1

      Seeing the number of folks that are calling shenanigans on the above post I'm taking the courtesy of proving my point.

      It was even mentioned in a slashdot article.

      http://news.slashdot.org/article.pl?sid=09/07/28/0045229

      http://www.sdtimes.com/link/33641

    36. Re:Kinda funny. by shentino · · Score: 1
    37. Re:Kinda funny. by drsmithy · · Score: 1

      Whereas everyone else sees contribution of code as a nice bit of corporate philanthropy, Greg KH sees something completely different. He sees it as corporations dumping their code on the community so they can off-load its support.

      Which seems rather odd, given that one of the most common arguments put forth from the OSS community is that by open-sourcing their code, commercial vendors will save money because the community will keep them maintained.

    38. Re:Kinda funny. by Anonymous Coward · · Score: 0

      That's true, but it also demonstrates the Microsoft's Linux developers are second-rate, at best. If I were a hiring manager, and I got a resume from a Microsoft employee who claims to have worked on the Linux kernel, I would assume that can't write code properly.

      They may be excellent coders being used not to the "sane [Linux] kernel coding style" but to another coding style which is just as sane.

    39. Re:Kinda funny. by Rogerborg · · Score: 1

      It's modded insightful because it is insightful.

      What's "juvenile" is Microsoft's utterly facile claim that they had been "working towards" releasing the source - which they were required to do immediately by their acceptance of the GPLv2 freedoms - for two months before Greg got in touch with them to ask "Where the source at, bitches?"

      --
      If you were blocking sigs, you wouldn't have to read this.
    40. Re:Kinda funny. by msclrhd · · Score: 1

      And Greg KH has put in a lot of effort getting the Hyper-V drivers into shape.

      Now, lets say that there is some code that the maintainer does not understand. Because they don't have access to the hardware, software (in the case of virtualisation platforms) or technical specs, what should they do?

      And yes, it is the *community* (of which Microsoft has become a part). If Microsoft has a vested interest in these drivers, they need to help the community (it is, after all a two-way process).

    41. Re:Kinda funny. by msclrhd · · Score: 1

      How much of the problems are due to Ubuntu using bleeding-edge packages?
      How much of the problems are due to interfacing with binary-only drivers (e.g. nVidia drivers, which are needed for acceleration and 3d graphics; yes, there is nouveau, but that is still a work-in-progress)?

    42. Re:Kinda funny. by Anonymous Coward · · Score: 0

      They will save money: if multiple companies need the code, they can pool the money needed to pay the maintainer.

    43. Re:Kinda funny. by gbjbaanb · · Score: 1

      Or... it was more a marketing campaign right from the start. How else would you describe the large number of self-congratulatory 'Microsoft loves linux, really' blogs and announcements, while the actual code (the real work part of this) is so poor?

      If Microsoft was serious about this code, about assisting Linux with the Hyper-V integration, then they would be at least helping to support the code themselves.

    44. Re:Kinda funny. by Fred_A · · Score: 1

      Welcome to crowdsourcing, my friend! The new corporate model where pathetic geeks will be exploited by the big moguls, and just see promises of profit sharing.

      Ok Greg, get off /. and go back to your desk.
      And take your pills, you know what you're like when you forget them.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    45. Re:Kinda funny. by Anonymous Coward · · Score: 0

      "am I the only one who's noticed how chronically juvenile it also sounds"

      Right, 'cause slashdot is all about mature discussion. Of course your little rant wasn't about getting mod points was it? Tell us grandpa, what was Slashdot like when you were a kid?

    46. Re:Kinda funny. by the_womble · · Score: 1

      You could say the same about adding content to website by leaving comments.......

    47. Re:Kinda funny. by TheRaven64 · · Score: 1

      Well, if you're going to be like that then I won't release my HURD ABI compatibility layer for FreeDOS!

      --
      I am TheRaven on Soylent News
    48. Re:Kinda funny. by StormReaver · · Score: 1

      I don't get it.

      You apparently don't read, either. Microsoft didn't make any effort to ensure that the lump of code they were forced to release conformed in any way to the Linux kernel coding standards. In other words, the code was a clusterfuck that MS dumped onto Greg's plate and then abandoned. After Greg invested a significant amount of his time in cleaning up said clusterfuck, the code is now in a semi-reasonable condition for inclusion in the kernel.

      However, Greg is not going to be the one to maintain someone's abandonware. If no one from Microsoft wants to maintain it, then the code is going to be dropped from the kernel. This is common practice for kernel development, and has nothing to do with where the code originated. Code without a maintainer tends to get removed.

    49. Re:Kinda funny. by ClosedSource · · Score: 1

      "Microsoft didn't make any effort to ensure that the lump of code they were forced to release conformed in any way to the Linux kernel coding standards."

      Jeesh. Who cares about coding standards? If the code is useful than use it. You can dot the "i"s and cross the "t"s later.

    50. Re:Kinda funny. by Simetrical · · Score: 1

      Microsoft didn't donate anything. They were violating the GPL and preemptively released this source before they were caught. The code also is only of benefit to microsoft customers.

      When Random Hardware Company X GPLs drivers for their hardware, it's also only of benefit to their customers, and possibly also because their lawyers have told them they have to. So what?

      --
      MediaWiki developer, Total War Center sysadmin
    51. Re:Kinda funny. by Anonymous Coward · · Score: 0

      I don't get it. Microsoft donates code to the community, licensed under the GPL. Anyone is free to do whatever they like with this code (well, within the constraints of the license), and people are actually bitching about this?

      Greg wasn't doing anything of the sort. He maintains the staging/ directory. Drivers are supposed to be submitted there so they can be cleaned up (usually with help from the original authors) and eventually included in mainline. They are not meant to be submitted there and then left to bitrot. He understandably gets annoyed when the drivers are submitted into staging, significant effort is put into cleaning them up, and then the effort is wasted because the original submitters aren't willing to follow up. Microsoft was free to not submit the drivers to staging if they didn't care enough to get them all the way to mainline. (Actually, Greg was the one who submitted them to staging, but I assume he wouldn't have complained as he did if the guys at Microsoft who he got the code from didn't indicate they'd be willing to put some resources in getting them fixed up.)

      That said, GKH can hardly be accused of picking on Microsoft here, given the criticism he's leveled at even major Linux supporters like Ubuntu.

    52. Re:Kinda funny. by palegray.net · · Score: 1

      If no one from Microsoft wants to maintain it, then the code is going to be dropped from the kernel.

      You apparently assume entirely too much. I'm quite familiar with "common practices" for kernel development; I've been using and developing for Linux and BSD-based systems since 1996. Frankly, I don't care if their code is "up to standards" or not; if it isn't, it'll get dropped, and I'm fine with that.

    53. Re:Kinda funny. by shaitand · · Score: 1

      If Random hardware company x intentionally used gpl'd code, distributed their drivers without releasing the source, were caught breaking the law, and then complied in the minimum manner in order to dodge paying the price for their crime.

      They don't deserve a pat on the back either.

      Most companies who open something are doing it for business purposes. That is fine, there is nothing wrong with that but that isn't the same thing as doing it for copyright infringment purposes.

      Besides, have our values really fallen so much that we give credit to people who provide a tangent benefit to others out of pure self interest?

      It is like the old story of a man falling off a snowmobile who breaks his leg and craws three miles through the snow back to the highway. Such a man is not courageous or brave. He merely has a survival instinct and saved his own ass.

    54. Re:Kinda funny. by Anonymous Coward · · Score: 0

      If I was Microsoft I'd pay a few full time developers to work on Linux development. It'd help the development effort AND it will help keep these people from complaining about Microsoft not helping open source development.

      -XcepticZP

  5. How did it make it into the kernel in that state? by harmonise · · Score: 3, Insightful

    Quote from the article:

    It did take over 200 patches to get their code into reasonable shape, which is a bit excessive

    GKH also said:

    If they do not show back up to claim this driver soon, it will be removed in the 2.6.33 release.

    If the driver was in such poor shape and didn't follow the kernel coding guidelines, then how did it make it into the kernel in the first place? I was under the impression that the kernel maintainers had pretty strict guidelines about coding style and what is and isn't acceptable.

    --
    Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
  6. A little credit where it's due by pathological+liar · · Score: 2, Informative

    Two thirds of the summary are lifted directly from the sdtimes link...

    1. Re:A little credit where it's due by Tubal-Cain · · Score: 2, Funny

      So the editors are trying to trick us into reading the article by hiding it in the summary? Good thing it didn't work.

    2. Re:A little credit where it's due by Anonymous Coward · · Score: 0

      Odd, usually it's more like 90%

  7. Re:How did it make it into the kernel in that stat by Chirs · · Score: 5, Informative

    This is for the drivers/staging tree, which is specifically set aside for drivers that don't meet normal code standards but where the intent is to bring them up to par for merging into the "real" tree.

  8. The FSF's enforcement bots have mod points today by petrus4 · · Score: 0, Offtopic

    I've already had a few posts of my own down modded with, "Overrated." That's the moderation reason which, when FSF drones get mod points, they typically use, because it's the closest thing available to, "-1, Disagree," or, "-1, Author is writing statements contrary to our programming, which is unacceptable."

    I'm also noticing that everyone who says the right things, about how evil Microsoft are, and about how perfectly just the community response is, predictably gets modded Insightful, as well.

    How long is Linux going to be choked and held back by your existence, FSF? How long will we have a scenario here on Slashdot, where it is forbidden to make statements which are contrary to your mind control?

    Keep modding me down, you corrupt, brainwashed cowards. My karma here is high enough that I can withstand it just fine. You haven't silenced me in nearly 10 years now, and I don't know why you'd think you're going to be able to at this point.

    I will be interested to see if any of you actually have the spine to respond to this, or if you'll just respond rapidly and predictably, by down-modding me to -1. I've made it easy for you; you can almost claim your use of -1, Offtopic was legitimate!

  9. Just amazing, by sbeckstead · · Score: 1, Troll

    First I don't blame MS for doing what they did, I do thank them, though I don't use or benefit from their code.
    Second, how can anyone actually defend MS actions here. They got caught benefiting from public efforts and were forced to release the minimum code. They put little effort into the task and delivered crap (as usual). So Good on you MS, now can you please clean up the pile of $%# you left in the corner, thank you.

    astonishing

    1. Re:Just amazing, by Anonymous Coward · · Score: 0

      So why do you think it is crap what they delivered? Because the code doesn't fit the Linux kernel coding guidelines? That's some bullshit metric.

    2. Re:Just amazing, by Simetrical · · Score: 1

      They put little effort into the task and delivered crap (as usual). So Good on you MS, now can you please clean up the pile of $%# you left in the corner, thank you.

      There's no reason to think that the code is of particularly poor quality, given the circumstances. It just doesn't meet Linux kernel coding standards. Obviously full-time Linux kernel hackers are going to find a lot of ways things can be done better in a Linux driver written by outsiders. Few people at Microsoft are likely to be nearly as familiar with how the Linux kernel APIs as lkml denizens.

      Moreover, there are all sorts of problems that Linux hackers might have with the code that aren't issues of code quality for a standalone driver (which is what this was originally designed as). A driver that duplicates functionality, or even does something in a different and better way that similar drivers could benefit from, might not be accepted into the kernel until all the good stuff is factored out so that it benefits all drivers. But if you're writing a standalone driver, you can't do that: you don't want to ask your customers to patch the kernel, so you have to hack around it.

      --
      MediaWiki developer, Total War Center sysadmin
  10. Re:How did it make it into the kernel in that stat by Lennie · · Score: 2, Informative

    It only got accepted after the cleanup, done by GKH.

    --
    New things are always on the horizon
  11. I get it now by Anonymous Coward · · Score: 0

    The driver is deliberately a mess, so it distracts Linux developers from working on Linux and wastes their time with Microsoft's kludge

  12. Nice Work if You can Get It by segedunum · · Score: 1

    I fail to see why Novell should be doing the work for a competitor, but I suppose that's what they're best at these days.

    1. Re:Nice Work if You can Get It by pseudonomous · · Score: 1

      Well, Novel has that whole "interoperability" advertising campaign going, I imagine this might have something to do with this...

    2. Re:Nice Work if You can Get It by pembo13 · · Score: 1

      I don't think Novell is a competitor with Microsoft at this point. This particular code only benefits Novell through their Microsoft partnership, and +200 patches by Mr. Kroah-Hartman must cost Novell a lot of money for someone of his position.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  13. It's all good by steveha · · Score: 4, Insightful

    Greg K-H's public comments about the code being abandoned had the desired effect: people at Microsoft got in touch with him again. The same thing happened with code contributed by several other companies:

    Although not hesitant to point a finger at Microsoft, Kroah-Hartman refused to name these other companies, claiming it would be "rude" to disclose private e-mail information.

    "But what's the big deal here?" he asked. "This is the normal development process happening, and a company learning how to deal with it. It happens every single day with all companies who are new to the Linux kernel development process. Sure, some do it better than others, but in the end, it's all good."

    This is Microsoft (and other companies) learning how to deal with kernel development. Greg K-H has a good attitude about it, so let's not build a mountain out of this. Perhaps Microsoft will do better next time.

    Not everything and everyone associated with Microsoft deserves abuse and scorn. Save it for their next DRM initiative or something.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
    1. Re:It's all good by Rogerborg · · Score: 3, Insightful

      Indeed - Microsoft were (eventually) fully in compliance with their GPLv2 "freedoms". They squatted down and strained and squeezed out a steaming dump of their actual source. There is no - zero - onus on them to make that source fit in with the Linux kernel zeitgeist, only to provide what was used to build their binary, everything that was used to build their binary, and only what was used to build their binary.

      Their "freedoms" ends with bundling source with the binary or making it available to "any third party", not to massage it until it fits the whims of any particular Linus-kernel Nazi. And thus ends the thread.

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:It's all good by Anonymous Coward · · Score: 0

      Their "freedoms" ends with bundling source with the binary or making it available to "any third party", not to massage it until it fits the whims of any particular Linus-kernel Nazi. And thus ends the thread.

      Cute.

      The problem for Microsoft as far as I'm concerned is that I watch what they do, not what they say. When viewed thusly things don't look good.

      Of course, neither you nor Microsoft care one bit about what I happen to think.

      Which is perfectly fine.

      *yawn*

    3. Re:It's all good by petrus4 · · Score: 1

      There is no - zero - onus on them to make that source fit in with the Linux kernel zeitgeist, only to provide what was used to build their binary, everything that was used to build their binary, and only what was used to build their binary.

      You neglected to mention that given that it is Microsoft that we're talking about here, there are no sane standards for them to adhere to, anyway.

      The GPL doesn't work as a legal agreement in the usual sense of the word. You don't purely have to fulfill the letter of the GPL in a legal sense, in order to be in compliance. You have to consume as many gallons of the Stallmanite Kool-Aid as the "community," feels like arbitrarily decreeing at any given point, as well. It's not purely about source with binaries; it's about thinking in a manner which the cult approves of.

      The truly laughable element of all of this, of course, is the fact that generally speaking, the most rabid elements of the "community," generally wouldn't know decent code if they fell over it. The people doing the real development work where Linux is concerned, don't give a damn about the FSF's bullshit.

      They're just working away, down in the trenches, making things work. They're not narcissists; they don't insist on taking credit for everything possible. They're not paranoid; they don't literally poison the very air around them with the intensity of their hatred for Microsoft.

      They just write code.

  14. I'd do the same by Anonymous Coward · · Score: 0

    When I can get clueless geeks to work for free why would I spend my company's resources on it?

  15. Re:The FSF's enforcement bots have mod points toda by NoYob · · Score: 2, Funny
    I'm just hoping for a day when Apple does the same thing - watching the Apple fanboys against the FOSS fanboys go at it and the dual Apple/FOSS fanboys having aneurysms would be an incredibly entertaining set of threads!

    If it has happened, please oh please post the link!

    --
    It's NOT me! It's the meds! I'm on 1000mg of Fukitol.
  16. Microsoft's Linux "Contribution" by Vexorian · · Score: 4, Insightful

    Ok, honestly, when VMWare released GPLed drivers LOOOOOOOOONG ago, how many blogs did we have talking about how VMWare is contributing code to Linux, and how many people needed to state that those were simply self-serving drivers for VMWare? Nooone... These are self-serving, there is nothing fundamentally wrong with it, they wanted their virtualization stuff to be able to run GNU/Linux, and they released drivers. It is not an 'evil' move but simply a logical one. But for sure it is not a 'contribution' to Linux. It is nothing out of the ordinary and honestly, I am tired of having to read countless of stories about...

    --

    Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    1. Re:Microsoft's Linux "Contribution" by QuantumG · · Score: 2, Interesting

      VMWare was releasing their changes to the kernel and to X11 back when the technology was being developed at Stanford. When the company was formed that process continued. Of course, that didn't stop anyone from claiming they were violating the GPL and were bad to the community months ago. If it bleeds it leads.

      --
      How we know is more important than what we know.
    2. Re:Microsoft's Linux "Contribution" by slimjim8094 · · Score: 1, Insightful

      They didn't attempt to violate the GPL, get caught, and then take a crap on the floor either.

      Had Microsoft gone and said "We have these drivers for you, benefiting us, that we want in the kernel. We've made a good-faith effort to do everything right, stylistically and otherwise, what do we do next?" everybody would be applauding them (as it is, people are still applauding them).

      What they did instead was try to sneak them out like a thief in the night, then get caught and need to hand the code over or risk a lawsuit. So they had half-assed it to begin with, and now weren't answering questions. They've been working in bad faith.

      That's the difference.

      --
      I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
    3. Re:Microsoft's Linux "Contribution" by BitZtream · · Score: 1

      VMWares products exist because of Linux. They are built on Linux.

      I can't think of a single MS product that exists because of Linux.

      These drivers are unlike to be 'useful' to Microsoft in any way that I can see. All it does is helps facilitate moving to Linux in a completely Microsoft shop.

      Yes, its a little different, VMWare depends on Linux, MS does not.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    4. Re:Microsoft's Linux "Contribution" by Yvanhoe · · Score: 1

      Microsoft cleverly got mor /. coverage by calling the GPL a cancer. And by being one hell of a big software company.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    5. Re:Microsoft's Linux "Contribution" by CAIMLAS · · Score: 0

      VMWares products exist because of Linux. They are built on Linux.

      I can't think of a single MS product that exists because of Linux.

      I can - quite a few, actually. Though, in most cases, it's not directly:

      * Hyper-V itself exists because of Linux - because of VMWare and the like, which pioneered the VM market, using Linux.
      * A lot of the UI effects in W7 have been directly or indirectly 'stolen' from (primarily) Linux desktop environments
      * Office 2k7 exists, arguably, because OpenOffice has been able to support their older document formats mostly-flawlessly for some time now.
      * Silverlight was brought out because ASP.NET wasn't cutting it when competing to LAMP and similar software stacks for web development (as well as Flash).
      * IIS was a direct response to Apache, which has primarily been run on Linux and BSD.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    6. Re:Microsoft's Linux "Contribution" by Blakey+Rat · · Score: 1

      They didn't attempt to violate the GPL, get caught,

      Please, that's made-up Slashdot bullshit. Don't believe everything you read on this site, hell, don't believe anything you read on this site: Microsoft intended to release the drivers under the GPL from day 1. (Why would they even bother making them, otherwise? Think about it-- they're useless outside the kernel, and they need to be GPL to get in the kernel!)

  17. Re:The FSF's enforcement bots have mod points toda by Anonymous Coward · · Score: 1, Funny

    When it comes to Apple, you suddenly start hearing sentiments such as "closed environment is a good thing for the users because it Just Works" and "it works so well because they won't let you touch it with your dirty hands" from the very same people who are bitching about Windows kernel not being GPL'd five minutes ago.

    My theory is that, so long as an OS has bash/sed/grep/awk and properly-working Flash and no-headache audio and video, no-one cares about the license anymore.

  18. Re:The FSF's enforcement bots have mod points toda by gbarules2999 · · Score: 5, Insightful

    All your posts have been so far have all been complaining about how everyone around here thinks Microsoft is evil, and how the group mindthink is fucking you over. No wonder you got modded down.

  19. Re:The FSF's enforcement bots have mod points toda by bootup · · Score: 4, Interesting

    Get over yourself... nobody here cares what you think. This isn't the propaganda arm of MS so if people say things that you see as "anti-Microsoft" it is probably because is is true. Certainly a site that is a "Source for technology related news with a heavy slant towards Linux and Open Source issues." clearly identifies itself and needs to be read with a bit of scepticism-even if a significant number of those you see as "anti-Microsoft" are right most of the time. I don't see BestBuy, Staples, PC World, or any other "MS Windows" propaganda arm identifying itself so blatantly as Microsoft for the good of the people.

  20. It's actually even lamer than that... by MoxFulder · · Score: 2, Insightful

    Thank them for what? MS's contributed drivers are useless to anyone who isn't running MS's own hypervisor and Linux underneath (i.e., MS's customers). They didn't donate this code out of any altruism, only pure self-interest.

    Yeah, and they only decide to "donate" this code after it was pointed out to them that keeping the code private was a violation of the GPL, since it's clearly a derivative work of the Linux kernel.

    So what do they do? Instead of GPL'ing it and working to maintain and clean up the code themselves, they just dump it on the kernel maintainers. Lame.

    In my mind, it shows that Microsoft still doesn't take Linux seriously on some level. They don't bother to build a useful working relationship with the kernel devs because they see this as a one-off interaction just to "get Linux working with Windows."

    Contrast this with, say, Intel or AMD or Realtek or IBM or pretty much any hardware company. Of course, contributing to the Linux kernel is a matter of "pure self-interest" for those companies too: they want to make their Linux-using customers to buy and happily use their hardware. But those companies learn to work with the mainstream kernel development process, because they see a long-term interest in a good relationship with the community of Linux developers and users.

    1. Re:It's actually even lamer than that... by Grishnakh · · Score: 1

      Exactly. And the main reason for getting stuff into the mainstream kernel is not only to help your customers, but to make things easier for you, because once it's merged in, you no longer have to worry about maintaining it: the kernel devs do that. So if some big architectural change comes along, or naming changes, or whatever, they deal with any changes that might impact your code. It's a lot easier than trying to maintain your own separate branch of code, and then having to deal with fixing it every time a new kernel version comes out and breaks your patch.

      It's pure idiocy to not take advantage of the ability to have your code merged in, and condemns your customers to not only having to build their own kernels or use ones you provide, but keeps them stuck with old kernel versions.

    2. Re:It's actually even lamer than that... by MoxFulder · · Score: 1

      It's pure idiocy to not take advantage of the ability to have your code merged in, and condemns your customers to not only having to build their own kernels or use ones you provide, but keeps them stuck with old kernel versions.

      Right... there's a quite a mess in the embedded world with a lot of device makers stuck on bug-ridden, horribly hacked-up 2.4 kernels. In particular, the execrably unhelpful Broadcom has never released any open-source drivers for its WiFi chipsets, and no binary drivers for 2.6.x kernels (except recently for x86).

      Microsoft just doesn't "get" the way Linux works. It's kind of astonishing that even the developers responsible for writing Linux kernel code there haven't figured out the value of cooperating with the kernel team. Well... maybe they have and the suits overruled them. Hard to say.

  21. In true Spirit of CodePlex then ? by TravisHein · · Score: 2, Insightful

    Kind of funny how today there was that other announcement here about Microsoft sponsoring CodePlex foundation to help bridge the gap between commercial developers and open source projects, which kind of seems to be what they should have done a bit more here right.

  22. Re:The FSF's enforcement bots have mod points toda by fermion · · Score: 1
    You know I say unpopular things and get modded down,but I don't go and cry like a baby and create crazy conspiracy theories. I accept that some people are motivated by dogma or money rather than reason and logic. That is why some people, adults not kids, feel they can deny statements and ideas that most reasonable people would consider valid.

    What is worse, some people can have temper tantrums, promote insance conspiracy theories, call others who disagree with them corrupt, brainwashed cowards, and get modded up. Uncivilized discussion should never be tolerated in a civilized world. When I go crazy, I expect to be modded down. I hope I never write anything as hypocritical as the parent. I also have mode points, almost always, and my karma is high. However, as the faq says, karma is not dick or teat size. Abusing the karma, or treating it as something real, is pretty pathetic. Saying the no one can hurt you because your karma is so high is not dissimilar to a person who goes on a murder spree because they feel they cannot be caught.

    To the matter at hand, no one knows why MS is all of the sudden being so nice, but there is evidence it is not completely benign. They probably have violated GPL and similar licenses in the past, and some of the donations may have been settlements for those illegal activities. The courts are pretty convinced that MS destroyed the i4i bussiness, and it is only the massive number of MS lawyers that keep MS Word on the market. MS is not apologetic about this piracy, and claim that since the business is already destroyed, why should there be any damages? Then there is the matter of the patents that MS tried to sell on the idea that the price could be recouped by suing OSS providers. In all, there is no evidence that the MS tactics of sneak attacks and massive budgets for lawyers has changed.

    It is easy for the young people to just use the OSS without realizing that it is a right that many had to work for. MS helped in this fight, by giving software away, but then kind of lost the faith by writing whiny letter, not unlike the parent, and randomly asserting copyrights as it needed extra cash. But know the kids have OSS, and are willing to take it for granted. Just like women who can now work, vote, and wear pants. Or non-whites who have equal rights and justice. Or kids who get a minimum wage and have some assurance of actually receiving the money.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
  23. Invisible downmodded posts by Draykwing · · Score: 2, Informative

    By default, _really_ heavily downmodded posts are not viewable to users who aren't logged in. If you log in, you can set your view preferences to allow them to be seen.

    1. Re:Invisible downmodded posts by Anonymous Coward · · Score: 0

      Actually, the current situation for people not logged in is that all posts at 0 or below are not visible... so AC posts are being "censored" in a sense.

  24. Re:The FSF's enforcement bots have mod points toda by Anonymous Coward · · Score: 2, Insightful

    Somebody call the wambulance please.

  25. Re:The FSF's enforcement bots have mod points toda by tolkienfan · · Score: 2, Funny

    That's weird - I have mod points, and your comment is both overrated (5-insightful) and off-topic (as you pointed out).
    Damn! I've posted, now I can't mod it. Oh well - I'll go mod some of your posts in another thread...
    This one is underrated and hilarious. I'll start there.

  26. Flame by gd2shoe · · Score: 4, Informative

    You think this constitutes "publicly flame"ing Microsoft? He's just asking them to step it up and contribute. He's much harder on others in that list. It also doesn't seem like he went out of his way to be interviewed. It sounds like he just responded to a few questions that a reporter put to him. "Unfortunately" and "so sad" do not, of themselves, constitute a flame.

    Here are a few other choice passages: (these may be interpreted as weak flames)

    heci A wonderful example of a company throwing code over the wall, watching it get rejected, and then running away as fast as possible, all the while yelling over their shoulder, "it's required on all new systems, you will love it!" We don't, it sucks, either fix it up, or I am removing it.

    me4000 and meilhaus They work on the same hardware, and they duplicate the existing COMEDI drivers. Someone thinks that custom userspace interfaces are fun and required. Turns out that being special and unique is not what to do here, use the COMEDI drivers instead. These will be removed. Heck, I'll go remove them for .32, there is no reason these should still be around, except to watch the RT guys squirm as they try to figure out the byzantine locking and build logic here (which certainly does count for something, cheap entertainment is always good.)

    rspiusb A weird, very expensive camera, from a company that does not want to release the specs, and wants custom userspace interfaces. The code hasn't built since the 2.6.20 days. I'll go delete it now from .32, it doesn't deserve to live as no one cares about it, least of all, the original authors of the code :(

    In other words: "Though it seems that he has the generosity to not publicly flame them unlike Microsoft." is pure hogwash... on both counts.

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  27. Staging by gd2shoe · · Score: 1

    It's still in "staging". from the article:

    Here's a summary of the state of the drivers/staging/ tree, basically what will be coming in the 2.6.32 merge, and what the status of the different drivers are so far.

    First off, drivers/staging/ is NOT a dumping ground for dead code. If no one steps up to maintain and work to get the code merged into the main portion of the kernel, the drivers will be removed.

    Further examples:

    asus_oled This only needs minor cleanups to get merged properly into the main tree. If someone wants an easy project, this would be it.

    phison What? I thought I asked for this to be merged a while ago, sorry about that, no reason it should still be in staging anymore, it's just so small it slipped through the cracks...

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  28. Home and End by gd2shoe · · Score: 1

    Yes, but is bash nearly so friendly without the @#$% "home" and "end" keys! (Thank you Apple for hampering an otherwise useful tool.)

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  29. Except they're here to teach you to fish by tlambert · · Score: 4, Insightful

    "If you're here to build me a bridge, then tell me so and build it. If you're here to bring me a stone, then don't tell me you're here to build me a bridge."

    Except they're here to teach you to fish, not to become your unpaid fishermen/code slaves for the rest of eternity.

    I actually expect that this was an intern project for one or more interns (intern season just ended), and that there was never any expectation that the people who did the work would be around to maintain it. It was in fact a very large move for Microsoft to release this code at all, and it probably took a lot of begging internally to get management to agree to that much concession. Then they went above and beyond, and released the code patches under the GPL, which meets their requirements under the GPL to donate the code back to the Linux project. You seem to expect them to stick around and maintain that code in perpetuity, which wasn't the contract, and wasn't the license. So you're complaining and threatening to remove the drivers in the next release unless they commit resources in perpetuity to maintaing the drivers vs. *your* code base.

    This is really a stupid demand on your part;if the kernel level APIs (what Sun calls their DDI/DKI - Device Driver Interface/Device Kernel Interface) in Linux were stable and not such a moving target, you could just forget the drivers and they'd keep working indefinitely.

    As one of the people who struggles internally in a company to keep certain sources out there and available for anyone who wants them, IMO it's really ungrateful of you to look the gift horse in the mouth and demand more just because you can't maintain stable APIs.

    -- Terry

    1. Re:Except they're here to teach you to fish by srwalter · · Score: 4, Informative

      So you're complaining and threatening to remove the drivers in the next release unless they commit resources in perpetuity to maintaing the drivers vs. *your* code base.

      I don't think that's the situation. The drivers currently only exist in the -staging tree. That is far different than Linus' official tree. The -staging tree is home to driver code that does not meet the standards of Linus' tree, and it's purpose is to assist the maintainers of the code to increase its quality such that it can be included in Linus' tree. MS is not being asked to "commit resources in perpetuity," but merely to get the code up to the state where it can be included in Linus' kernel tree.

      This is really a stupid demand on your part;if the kernel level APIs (what Sun calls their DDI/DKI - Device Driver Interface/Device Kernel Interface) in Linux were stable and not such a moving target, you could just forget the drivers and they'd keep working indefinitely.

      See above. Once the driver is included in the kernel proper, the kernel developers themselves fix drivers when API's change. That's one of the primary benefits of being included in the kernel proper. If you're developing driver code and just dropping it on some corner of the web, then You're Doing It Wrong.

      --
      Freedom is the freedom to say that 2 + 2 = 4
    2. Re:Except they're here to teach you to fish by Simetrical · · Score: 1

      I don't think that's the situation. The drivers currently only exist in the -staging tree. That is far different than Linus' official tree. The -staging tree is home to driver code that does not meet the standards of Linus' tree, and it's purpose is to assist the maintainers of the code to increase its quality such that it can be included in Linus' tree. MS is not being asked to "commit resources in perpetuity," but merely to get the code up to the state where it can be included in Linus' kernel tree.

      staging/ is part of mainline at this point, and has been for a while. Entirely correct aside from that, though. When they're cleaned up they'll be moved from drivers/staging/ to drivers/.

      --
      MediaWiki developer, Total War Center sysadmin
  30. Crucial Missing Routine: BSOD by renuk007 · · Score: 1

    "We are sorry, but your Linux system has crashed. The Microsoft Code that enables this feature is fully activated, but has not been updated. Please log on to the Microsoft Update site to get a new version of this exact same code. Now you may reboot your computer and come back later to this screen."

  31. Re:The FSF's enforcement bots have mod points toda by tokul · · Score: 2, Insightful

    People don't have to be under mind control in order to think that Microsoft is evil. They might have enough work experience to know that Microsoft, Adobe, Autodesk and Corel don't care about end customer and care only about own profits and suppressing opposition. Such corporate behavior fits definition of evil in human world.

  32. Obligatory xkcd by Anonymous Coward · · Score: 0
  33. Re:The FSF's enforcement bots have mod points toda by BitZtream · · Score: 1

    Yet no one offers any evidence to the contrary. You guys are awesome. Get what you want, you whine about it. Someone does the same shit you do, you whine about it and act like its a bad thing.

    Gee ... I wonder why so many businesses avoid this particular group of people ...

    You know, when you had no friends when you were younger ... ever thing maybe there was a reason for it. Theres a reason no one likes you.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  34. Re:The FSF's enforcement bots have mod points toda by BitZtream · · Score: 1

    Good job, you proved his point to the letter with your post and your modding.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  35. Re:The FSF's enforcement bots have mod points toda by BitZtream · · Score: 1

    You mean for him or for the douche bag complaining about the quality of the kernel drivers? Its difficult for me to determine whos whining you're referring to.

    I have to assume you're referring to the person you are replying to, but to most sane rational people, it would seem that the original article is more whiney than this guys post. Looks like you just proved his point for him.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  36. Microsoft's coding style! :-) by jkrise · · Score: 1

    "Their code needed lots of work to get to normal Linux coding style acceptance, that's nothing new. It did take over 200 patches to get their code into reasonable shape, which is a bit excessive," he said. Microsoft did not contribute to the patching effort.

    Normal Linux coding style:
    10 START
    20 GET JOB DONE
    30 STOP

    Microsoft coding style:
    10 START
    11 IF $OS=Vista, Sleep 10
    12 IF $OS=XP, Sleep 5
    13 IF $OS=Windows 7, Sleep 2
    14 IF $Customer_Uses_Linux=true, Sleep 100 .. .. ..
    20 GET JOB DONE
    21 IF $OS=Windows, STOP
    22 IF $Customer_uses_Linux=true, CRASH
    30 Profit

    The same pattern repeated hundreds of times in all code. It takes a lot of effort to cleanup to Linux standards, no wonder!

    --
    If you keep throwing chairs, one day you'll break windows....
  37. Code Quality by Anonymous Coward · · Score: 0

    It must be a new experience for the mircosoft developers to be asked to actually deliver good quality code that will interact well with other companies code. It can turn out to be a good learning experience for the code monkey working for the evil empire.

  38. Abandonware or Denial of service by SgtChaireBourne · · Score: 2, Interesting

    No, they were violating the GPL.
    They had to at least give source to their customers.

    Rather than to continue to do that they made this driver the kernel maintainers problem. If they don't want to help maintain it, I say drop it from the kernel.

    It was a twofer. MS weaseled out of punishment for license violation ( GPL ) and at the same time just shat in the kernel maintainers' collective pocket.

    Denial of Service attacks work in meatspace, too. The maintainers have no obligation to burn up hours coding and supporting someone else's abandonware.

    For that matter, so do injection attacks. For example, find out who gave the order to install any given Windows server, assuming you can still find one these days. No one will 'fess up.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
    1. Re:Abandonware or Denial of service by 91degrees · · Score: 1

      It was a twofer. MS weaseled out of punishment for license violation ( GPL ) and at the same time just shat in the kernel maintainers' collective pocket.

      Following the terms of the licence isn't weaseling out of anything. They have no obligation to do anything other than abide by the terms of the GPL, which they have done.

      The maintainers have no obligation to burn up hours coding and supporting someone else's abandonware.

      Don't then. MS will probably provide patches and support to their customers and provide source for the patches. It doesn't make a jot of difference to MS whether they're compliant with the Linux coding standards. They just want their software to run Linux well.

  39. Hit and run. by SgtChaireBourne · · Score: 2, Insightful

    From the blog,

    "hv (Microsoft Hyper-V) drivers. Over 200 patches make up the massive cleanup effort needed to just get this code into a semi-sane kernel coding style (someone owes me a bit bottle of rum for that work!) Unfortunately the Microsoft developers seem to have disappeared, and no one is answering my emails. If they do not show back up to claim this driver soon, it will be removed in the 2.6.33 release. So sad..."

    I'm not shocked. M$ reputation is so bad that this kind of behavior is not a surprise.

    Was is a bit of a shock is that GKH actually wasted one minute longer than rejecting the fake drivers with a missive to "hold off on re-submission of the code until it actually works" What happened to the idea of showing something that works? There used to be pretty strict guidelines about coding style and what is and isn't acceptable, including having some working code first.

    Anyway, what are these so-called developers from M$ off doing while the Linux team is cleaning up from this hit and run?

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  40. Re:The FSF's enforcement bots have mod points toda by extintor · · Score: 2, Insightful

    You seem like one paranoid individual.

  41. Thick skin. by leuk_he · · Score: 1

    This is just a part of the process of open source coders that are builing up a thick skin. You better do NOT thank him. you either contribute, or STFU. giving him thanks makes him more sensitive, and will be harde hit by the next attack to some of hiss code.

    Just give him his bottle of rum..

    "(someone owes me a bit bottle of rum for that work!) "

  42. Re:The FSF's enforcement bots have mod points toda by Anonymous Coward · · Score: 0

    Yet no one offers any evidence to the contrary.

    If he'd actually made any points that could be disputed you might have a point. Random, incoherent flaming is always going to get modded down. Why is that a surpise?

  43. Re:The FSF's enforcement bots have mod points toda by petrus4 · · Score: 0, Troll

    Get over yourself... nobody here cares what you think.

    I submit the GP's moderation, and my aforementioned karma, as evidence to the contrary. ;)

    You're right about one thing; my freaks list genuinely is rather extensive. However, I view it more or less as a roll call of Stallman's footsoldiers here on Slashdot. They know exactly who they are.

  44. Re:The FSF's enforcement bots have mod points toda by petrus4 · · Score: 0, Troll

    Predictably, you got modded Offtopic.

    Thank you for this, however. :)

  45. donated? by Anonymous Coward · · Score: 0

    Donated is a very poor choice of words. The Linux Kernel Organization is a California Public Benefit Corporation established 2002 to distribute the Linux kernel and other Open Source software to the public without charge.
    http://www.kernel.org/nonprofit.html
    The fsf is a charity.
    The Linux kernel project is part of a non-profit organisation. It is not a charity.

    Microsoft are not contributing the tiny piece of (Very poor quality and not good enough to make it past the staging area) Driver code to the Linux kernel because they want to. They are doing it because the have to. They violated the gpl.

  46. Re:When will it be enough. by petrus4 · · Score: 0, Troll

    Just curious, will anyone ever be able to do enough to get the GPL fanboys to stop their fucking whining?

    Truthfully, they only really got bad after 2005. Before that point, the FSF was gradually sliding towards irrelevance; but unfortunately, Microsoft had to go and start the DRM flap. Because of that, Stallman was able to reinvent himself and change focus to real-world activism, (since actual code development of the GNU Project had been taken over by either Red Hat or Debian a few years earlier) and the cult came back.

    These days, the slide back towards irrelevance has resumed, but they're resisting it every step of the way. They have a #gnu_generation channel on FreeNode which targets teenagers, (interesting when you consider that one of the key allegations levelled against Microsoft by the FSF on the Windows7Sins site is poisoning education) and there are reasonably regular reports of them taking on (and brainwashing) new interns as well.

    Then there's the ever-present Trotskyite Debian cheerleading squad, as well. Because Ubuntu is Debian-based, and the Debian crowd are as heavily Stallmanite (and Communist) as they are, the cult is managing to skim off a steady trickle of the Windows refugees who are adopting Ubuntu.

    Eventually the FSF are going to hang themselves. The Windows7Sins campaign doesn't look like anything other than a byproduct of toxic, crippling autism; it is pure preaching to the choir, and won't be earning them any credibility points at all with the general public.

    The literature of cults provides very few examples of a cult outliving its' founder, as well. Stallman could hypothetically be around for as long as another 35 years yet; but it is unlikely that he could remain active as its' leader for all of that time. I could see Kuhn definitely becoming the FSF's David Miscavige, although that will probably depend on how old he is when the time comes.

    Either way, they won't last forever; but the real issue, as you've pointed out, is how much damage they stand to do to Linux's reputation in the meantime. Linux is already largely recognised as being synonymous both with Stallman and with cultic radicalism by the online trade press. Red Hat might be doing well enough in the enterprise, but the non-profit community are generally regarded as hard leftist, extremist loons, and all too often with good reason, tragically. You'll never see a single article from the online trade press which dissents from the FSF party line, where the author isn't subjected to the most foul, blistering forms of abuse in the comments/talkback sections, if they have one.

    Another recent issue of some concern is the "Linux Youth," phenomenon that has begun to be observed among Ubuntu users. These are generally teenagers, and are usually both fanatically pro-Ubuntu and pro-Stallman. They may be a product of the "GNU Generation," initiative, or they may simply be developing due to Ubuntu's aforementioned association with Debian. Either way, it is troubling, if only because it demonstrates the FSF's ability to gain new victims/footsoldiers from diverse sources.

  47. Re:The FSF's enforcement bots have mod points toda by Anonymous Coward · · Score: 0

    No it's overrated. Clear partisan hackery is rarely broadly funny. It's only funny to narrow-minded people that like a "us-versus-them" mindset codified in text.

  48. Re:The FSF's enforcement bots have mod points toda by walterbyrd · · Score: 1

    I'm also noticing that everyone who says the right things, about how evil Microsoft are, and about how perfectly just the community response is, predictably gets modded Insightful, as well.

    I've noticed just the oppostie. I have also noticed that you post is modded fairly high.

    Ten years ago, slashdot was pro-linux, not so much anymore. It seems to me that, a few years back, msft learned to start flooding the board with their "technology evangelists." And that is not some mad conspiracy theory - msft has been caught doing just that.

    With typical msft hypocrisy, the shills bitch about linux advocates, while msft is known to pay posters.

  49. You Freakin' Annoy Me by Anonymous Coward · · Score: 0

    I swear you open source people whine so much.
    Microsoft gave us all these drivers....waaaaahhh!! Now we have to do work...waaaaahhh!!!

    Sew it up!

  50. And just because they released it by Anonymous Coward · · Score: 0

    Doesn't mean they can't be sued for previous breech of copyright.

  51. Re:Bait and switch by b4dc0d3r · · Score: 1

    Linux: Here's some code, have fun with it.
    MS: Ah OK, so we need to do this to make Hyper-V work
    Linux: Um, you're violating a license
    MS: Go away, we just want to make our stuff work
    Linux: Source code or (court case + source code)?
    MS: Oh fine, here you go
    Linux: Thanks. It's not good enough.
    MS: What? What are they talking about now?
    Linux: Not good enough, we fixed it for you.
    MS: Invalidating our test cases and documentation...
    Linux: So, when are you going to maintain this pile?
    MS: You took our code, changed it, and now expect *US* to troubleshoot and fix issues that people who aren't our customers find?
    Linux: Uhm, yeah, or we'll call you out on a blog.
    MS: FUCK YOU PEOPLE SIDEWAYS! NO ONE ANSWER THE PHONE!!! NO E_MAILS!!! NOTHING!!! THEY'LL GET NOTHING!!!!!!!!!!!

  52. Re:Bait and switch by SiChemist · · Score: 1

    Possibly the most inaccurate summary of the circumstances that I have yet seen in this discussion. Kudos for shooting for the stars!

  53. Re:When will it be enough. by SiChemist · · Score: 1

    And you've posted 9 comments in this thread yourself, whining about the "GPL fanboys". Pot, Kettle, you know the rest.

  54. Why are we even surprised? by HitoGuy · · Score: 1

    Why are we even surprised Microsoft is only half-assing their GPL'd virtualization drivers for Linux?

    After all, the ONLY reason we got them opened in the first place was someone busted them for violating the GPL in the first place, and they were never interested in releasing real FOSS anything in the first place. How they got the OSI approval for one of their licenses is a mystery to me. I would have rejected it outright simply on grounds of principle. Here we have a company that has internally and publicly declared FOSS its enemy, after all.

    Thus, I don't feel warm fuzzies when Microsoft does stuff like release GPL drivers, establish an "open" source license, supports projects like Mono or Moonlight, or opens sites like CodePlex. Their history is enough, in fact, for me to stand back and look for the ulterior motive and wonder when Microsoft is going to pull the rug out from under and screw those gullible folks who actually think Microsoft turned over a new leaf purely for the reasons stated above. I'm too familiar with their history for me to think they've actually changed, especially when their faux-friendly behavior towards FOSS doesn't look like a change from any other case of EEE or "partner and screw," two of Microsoft's favorite tactics.

    --
    I am beginning to think that maybe Darl McBride was attacked viciously by a penguin as a child.
    1. Re:Why are we even surprised? by petrus4 · · Score: 1

      How they got the OSI approval for one of their licenses is a mystery to me. I would have rejected it outright simply on grounds of principle. Here we have a company that has internally and publicly declared FOSS its enemy, after all.

      Not bad, not bad. You've got the red eyed, foaming at the mouth vibe working well, but I'm afraid this is lacking the true vitriol usually seen in a member of the "community." The degree of paranoia about Microsoft, however, is a good start. However, you're also lacking any statement which could remotely be construed as anarcho-Communist, so I'm afraid I'll have to deduct points for that.

      I'm feeling generous today, however, so I'll give you 6 out of 10, for this effort.

      Some other points to work on would be ranting about how FOSS in general wouldn't exist if not for the FSF, and also implying that the GNU project represents the [b]only[/b] FOSS toolchain currently in existence.

    2. Re:Why are we even surprised? by HitoGuy · · Score: 1

      Paranoia? Sure. However, your implication that its uncalled for is off the mark. Microsoft's history is way too littered with bad acts for me to trust them now just because they make warm fuzzy PR stunts. Perhaps you're just being a troll, but I'll bite

      I'm not anarcho-communist. And I am *not* an FSF supporter. And I'm far from being a Stallmanist, too. In fact, I really despise the man. I use Linux because it is superior, not purely because it is FOSS. I support FOSS because my experience thus far is a higher quality, if at the sacrifice for quality.

      I'm Linux camp, not GNU camp. It's "Linux" and not "GNU/Linux." Are you done trolling?

      --
      I am beginning to think that maybe Darl McBride was attacked viciously by a penguin as a child.
  55. Microsoft are laggards in Linux development? by Anonymous Coward · · Score: 0

    That may be true, but don't even get me started about how much those Linux kernel developers are slacking off when it comes to developing for Windows.

    By the way, there are some hardware companies that merely publish hardware details and let the Linux community write drivers from scratch. At least Microsoft provided some code to start with.

  56. foss development = anarcistic greedy meritocracy by thtrgremlin · · Score: 1

    Which is why it works :)

    One of the arguments I make to promote GPL is that it is entirely selfish and meritocratic. It is economically inefficient for a person to produce a product that is not useful to the producer. For example, it is useful for doctors to know medicine whether or not they practice. Same is true of plumbers, carpenters, farmers, etc. It also applies to engineers, software or otherwise. Microsoft "produces" a product for the purpose of selling it. They must make the product something people want, or think they want (Oversimplified I know, but still true). By contrast, people producing GPL work are initially producing something strictly for themselves. With information distribution having reached a cost of effectively zero, and development cost covered (because the intent of the product was the product), all that can happen by releasing the code (assuming it is a tool and not a trade secret) is that other people will selfishly take the code, rather than reinvent the wheel, and change or improve the product for THEIR own purpose. From there, a somewhat natural evolution occurs; the software replicates as people find it useful, and it mutates as people find it worth their time to take what exists and improve it for their own purpose, and hopefully re-releasing it back into the wild.

    So I think this whole argument is totally obnoxious. Whatever Microsoft's motivation for the release of their code may be, all you have is more information available for which anybody may do with as they please. I may be inclined to assume that Microsoft has put in the minimal effort to tease the community with information that could be useful in producing a useful product, and whether or not it is controversial to put in the effort to make the information useful to them doesn't take away from the fact that Microsoft has done NOTHING (this time) to harm the community. An ability or inability to rationalize a decision must be the sole responsibility of the person making that decision.

    If Microsoft is trying to bait the community into doing work for them, who cares. It is either worth it, or isn't. Microsoft's hope is that they can get SOMEONE do do the rest of the work. It is a calculated risk. As far as the community goes, I see no hostility in informing Microsoft that their half-ass contribution isn't worth the effort of implementing, if that be the case, and Microsoft can recalculate their move.

    The code isn't going to be deleted, it will either be commented out, or stored elsewhere and a line item added to a TO-DO list somewhere. This happens all the time. Last Ubuntu release (9.04) I put the majority of my time into two projects. Upon review for implementation, one was accepted and merged. The other, despite the fact I had managed to close out almost a dozen bug reports, was implemented incorrectly (for the sake of argument), and rejected. The days of work were not recoverable and basically wasted. Nobody picked up where I had left off, including myself. Those bugs are still open. It is just how things work. I wasn't offended, nor do I think the maintainer was rude for not accepting the work as is. I learned a lot from the experience and I still use my own version of the package.

    The only thing notable this time is that the 'contribution' was made by Microsoft. If some sloppy hacker pieced this together by way of reverse engineering, threw it out there and walked away, who knows what would happen to the code. It might rouse some discussion on the mailing list with comments like "wow cool, but wtf? Anyone want to tackle this s***?" for awhile, but it certainly wouldn't make headline news, because in my observation, that is just another day in the life.

    --
    Want Big Business out of government? Take away the incentive and start by getting government out of big business!
  57. Contradictory messages by Asgaard · · Score: 1

    I can't help but contrast this with the kernel driver project's message, where they call for open HW specifications so they can maintain code for them.
    I realize that contributing specs isn't the same as contributing shabby code, but save for that difference, it almost seems like a contradictory message:
    * on one hand it's ok for hardware companies to just drop specs and leave it to the community to code and maintain drivers
    * on the other, it's not ok if Microsoft drops code and then doesn't maintain it.

    It would seem as though no one wants to maintain Microsoft code. If that was so, I wonder how much of it is due to community bias against MS, and how much because of a lack of community interest. Also, no use cases maybe?

  58. top down fail by thtrgremlin · · Score: 1

    I am going to have to agree with the people that modded this troll, though personally, I think it is more like flame. You say that MS donated this code out of pure self interest as if it is different from any one else's contribution. Take the Wacom Driver project for example. Wacom only writes drivers for platforms they can "profit" from which they have determined are Windows and MacOSX. The Wacom Project Team has selfishly determined that isn't good enough for them AND that they have the necessary skill to remedy the situation. Why would a person who is greedy and selfish go out of their way to be inefficient and non-pragmatic about their approach? If what they desire is a driver, their greedy selfish desires are better met as an open source community project. The more people like them that want that driver sooner than later will selfishly commit resources towards improving the project. But keep in mind that their purpose is the driver. If they were producing the driver for money to sell to people that want support, it might make sense to keep it closed source and simply hire as many people necessary to slap together something together that looks good enough that will get people to buy it and sell updates as they implement new features to the best of their ability with the hope that nobody trys to compete against them. One thing I think may be different if such a company existed is that you would see drivers for more than just Wacom tablets, doesn't matter to them that people are buying inferior tablets.

    To my understanding, one of the reasons why there is no support for any other tablet is that it would run their resources thin. They selfishly believe Wacom makes the best tablets despite the fact that there are likely a lot of people out there that can't afford the most expensive brand. So for now there is just one driver. So what? If it is worth it to someone to develop drivers for other brands, then it will happen, but I expect that for most people the difference in cost of the tablets does not justify the cost of development. (Oooh, those greedy developers!)

    Just like any other code contribution, which is nothing more than information, people may or may not choose to review it, may or may not choose to fix it, may or may not choose to implement it, may or may not choose to maintain it, may or may not choose to extend it. That could be 1 person, a hundred people, or nobody. What you are doing is passing judgment on how other people should feels about it and calling for censorship, as if you need to protect people from how they choose to spend their time.

    How altruistic of you. :)

    Sorry, but I put your comments in the same category as the complainers on brainstorm.ubuntu.com that DEMAND (often in quite colorful language) their ideas that are highly rated by other non-programs be implemented by the development team. There have even been "resolutions" passed giving timelines in which developers must respond to their inquiries. WTF? These people obviously don't have the first clue about how people become "Official Ubuntu Developers", let alone how the dev process works. Personally, I might like to call Project Brainstorm a total flop and just get rid of it. On the other hand, evidently some people like it, sometimes devs respond. I'll just try to convince myself that it is a conspiracy to keep idiots off of launchpad. What I can do about this 'issue' is reserve the right not to go there.

    As a side note, I guess, take a look at the number of open bugs with patches over a year old that nobody has bothered to take the few moments necessary to test and confirm so that it can be implemented. It is astounding! But somehow there is still rapid progress.

    --
    Want Big Business out of government? Take away the incentive and start by getting government out of big business!
    1. Re:top down fail by Grishnakh · · Score: 1

      I am going to have to agree with the people that modded this troll, though personally, I think it is more like flame. You say that MS donated this code out of pure self interest as if it is different from any one else's contribution.

      No shit, sherlock. I never claimed otherwise. Go back and read the prior comments and try to understand what I'm saying in my comments. I'm sick of explaining it all you morons who have no reading comprehension.

  59. Re:The FSF's enforcement bots have mod points toda by tolkienfan · · Score: 1

    I found it funny, and I could never be called narrow-minded; not by anyone who knows me anyway.
    On the other hand, it's not "broadly" funny, I suppose.
    There are large numbers on the so called "christian-right" though, who deserve to be the target of such comments. I'm talking about the biggoted zealots. Those who expect the world to end within the decade, and therefore care more about converting and correcting those around them than helping society make progress.

  60. Re:How did it make it into the kernel in that stat by Sam+Ramji · · Score: 1

    Correct; these drivers were not originally built according to the kernel coding standards. At the time that was not a requirement.

    The incredibly cool thing is that kernel community developers submitted over 200 patches to the code. The team (Hank Janssen, Haiyang Zhang, and Hashir Abdi and a small test team) have spent their time integrating and testing the results to ensure that there were no regressions. As an example, the team spent roughly three weeks tracking down a crashing issue in the kernel that turned out to be fixed in the 2.6.31-rc8 release. For a first release and integration with the kernel I am happy with the results, and appreciate the work that Greg KH has put in to accept the changes and educate us on both process and coding style.

    With the regressions resolved and testing complete from this initial integration phase, the team is back to dealing with net new issues as well as adding features according to the customer roadmap. One of the top requests we've had is to add SMP (symmetric multiprocessing) support, so that is on the immediate term development list. This is a dedicated, long-term team that is still learning the cadence of kernel development and communication.

    Cheers,

    Sam
    sramji@microsoft.com

  61. Re:FSF shill by Anonymous Coward · · Score: 0

    You're just another paid FSF shill. How much is Stallman giving you for your FUD?