LWN: Comments on "Who wrote 3.0 - from two points of view" https://lwn.net/Articles/451243/ This is a special feed containing comments posted to the individual LWN article titled "Who wrote 3.0 - from two points of view". en-us Sat, 25 Oct 2025 10:13:52 +0000 Sat, 25 Oct 2025 10:13:52 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Microsoft, co-author of the Linux kernel https://lwn.net/Articles/452084/ https://lwn.net/Articles/452084/ dgm <div class="FormattedComment"> IANAL either, but Microsoft is not distributing "the program" (the Linux Kernel) here. I don't know if the set of patches can be considered "the program" by themselves. <br> <p> Can I download the kernel from somewhere in microsoft.com? Is there a git tree somewhere? All those could count as "distributing".<br> </div> Tue, 19 Jul 2011 10:15:56 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/452079/ https://lwn.net/Articles/452079/ etienne <div class="FormattedComment"> IANAL, but by contributing, don't they also give patent rights to "the Program"?<br> (For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. )<br> </div> Tue, 19 Jul 2011 09:12:28 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/452026/ https://lwn.net/Articles/452026/ leoc <I>it wants its fair share of the result.</I> <P> If they are playing "fair", then why do they refuse to provide a list of the patents Linux allegedly violates? Seems to me that the only share they would ever consider fair is 100%. Mon, 18 Jul 2011 18:38:11 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451980/ https://lwn.net/Articles/451980/ giraffedata <blockquote> Do you think Microsoft is getting a fair share ? </blockquote> <p> That's a little off-topic, since we're talking about whether there is some inconsistency or irony in Microsoft contributing code to Linux while claiming that Linux infringes some Microsoft patents. The only thing that would be relevant is whether <em>Microsoft</em> thinks it's getting its fair share (because if it does, then I must be wrong about Microsoft's motivation in making claims of Linux patent infringement). Mon, 18 Jul 2011 15:25:13 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451976/ https://lwn.net/Articles/451976/ dag- <div class="FormattedComment"> Do you think Microsoft is getting a fair share ? I think they get more than they deserve, if they deserve anything at all. And no, we don't know how much they settle for patent-infringements with those large hardware vendors, but I don't think they deserve the tiniest bit.<br> <p> Personally, if patents are there to protect corporate investments in research for the benefit of the general public, I do think the same general public should get full insight into patent settlements. I do think one (patent law) contradicts the other (closed patent-infringement settlements).<br> <p> How can we make laws to protect the general public, if we don't know what backroom deals are made as a result of it? I also think if those deals were forced to be made public, support for patent law, especially in software development, will soon be impossible.<br> </div> Mon, 18 Jul 2011 14:40:57 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451896/ https://lwn.net/Articles/451896/ dgm <div class="FormattedComment"> Look up TomTom vs. Microsoft. I may be instructive for you.<br> </div> Sun, 17 Jul 2011 09:59:40 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451845/ https://lwn.net/Articles/451845/ giraffedata <blockquote> Isn't it a bit weird that Microsoft is simultaneously contributing code to the Linux kernel **and** claiming that it violates their patents? </blockquote> <p> Why? Because contributing code means you want to help Linux and claiming patent violation means you don't? I don't think it's that simple. <p> For one thing, Microsoft so far hasn't even prosecuted any of its patent claims. The main purpose for those claims seems to be to defend against insults against Microsoft of the form that a rag-tag bunch of people working for free put out something better than what the great Microsoft machine (or any other conventional software publisher) could make. The point of the claim is simply to say that Linux developers <em>didn't</em> do it alone. <p> Even if Microsoft were to sue over use of its patents in Linux, that wouldn't mean Microsoft doesn't like helping out Linux; only that it wants its fair share of the result. Fri, 15 Jul 2011 23:20:17 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451835/ https://lwn.net/Articles/451835/ leoc Isn't it a bit weird that Microsoft is simultaneously contributing code to the Linux kernel **and** claiming that it violates their patents? Fri, 15 Jul 2011 21:02:49 +0000 Who wrote 3.0 - from two points of view https://lwn.net/Articles/451824/ https://lwn.net/Articles/451824/ mlankhorst <div class="FormattedComment"> With background knowledge I meant all the things you have to worry about in kernel space that might not happen in userspace. Atomics, interrupt contexts, rcu, the fact that not the whole world is a VAX^Wx86.<br> <p> When writing a bugfix for EFI I had to deal with early memory allocators and the transition to the full page allocator. For fun I looked up what allocators were used in the kernel. I came up with brk, e820, memblock, bootmem, xen's special brew, and the kernel's full page allocator. This list is probably incomplete. ;)<br> </div> Fri, 15 Jul 2011 20:07:49 +0000 Who wrote 3.0 - from two points of view https://lwn.net/Articles/451821/ https://lwn.net/Articles/451821/ Julie <p><i>the thing that probably is lacking is the background knowledge</i></p> I'm a bit confused by your comment, I had taken Jon's remark about it becoming difficult for new volunteer developers to participate as meaning the same as the above (newcomers don't _have_ that knowledge). Along with a couple of other potential difficulties:<br><br> 1. Volunteers necessarily have less time than full-timers and therefore anything they swot up on at the time is likely to be dated when they come to try to put it into practice due to the current fast rate of development<br><br>2. The kernel's pretty much saturated with regards to experienced (sometimes full-time, paid) devs (at least in the areas of core work; I know Greg K-H is always looking for more contributors to staging).<br><br>What did you mean?<br><br> <p><i>Following lwn for a few years helps a lot to learn about that. ;)</i></p>Well, I can't agree with you here - I think that following LWN for a few years has become pretty _essential_ for learning about that ;-) Fri, 15 Jul 2011 19:28:10 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451749/ https://lwn.net/Articles/451749/ patrick_g <div class="FormattedComment"> If I understand correctly Steve Friedl's technical discussion, it was only about the 200+ initial patchs to clean the MS driver before entering -staging.<br> What about the 300+ patchs during this 3.0 cycle? It can't be coding style work because that was done previously. Perhaps he need to write another article and change his previous conclusion.<br> </div> Fri, 15 Jul 2011 06:21:36 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451736/ https://lwn.net/Articles/451736/ pr1268 <p>Somewhat amusing, but very enlightening. Thanks for the blog entry. I also found Steve Friedl's technical discussion you linked fun&mdash;it's reassuring that the Linux kernel source isn't polluted with <tt>DWORD</tt>s or <tt>HANDLE</tt>s or all other types in ALL_CAPS. Phew!</p> Fri, 15 Jul 2011 02:47:08 +0000 Microsoft, co-author of the Linux kernel https://lwn.net/Articles/451721/ https://lwn.net/Articles/451721/ david.a.wheeler These stats are so amazing that I just posted "<a href="http://www.dwheeler.com/blog/2011/07/14/#microsoft-linux-author">Microsoft, co-author of the Linux kernel</a>", to comment on this. You might find that article amusing. Fri, 15 Jul 2011 00:01:57 +0000 Who wrote 3.0 - from two points of view https://lwn.net/Articles/451720/ https://lwn.net/Articles/451720/ mlankhorst <div class="FormattedComment"> I respectfully disagree with the assertion that linux kernel development is hard for newcomers. However the thing that probably is lacking is the background knowledge every kernel hacker takes for granted. Following lwn for a few years helps a lot to learn about that. ;)<br> </div> Thu, 14 Jul 2011 23:48:20 +0000 MS only slightly behind IBM, really? https://lwn.net/Articles/451627/ https://lwn.net/Articles/451627/ dgm <div class="FormattedComment"> Wow. Should I take my skates in my next visit to hell?<br> </div> Thu, 14 Jul 2011 14:14:51 +0000 MS only slightly behind IBM, really? https://lwn.net/Articles/451609/ https://lwn.net/Articles/451609/ patrick_g See <a href="https://lkml.org/lkml/2011/6/6/669">the messages</a> posted on LKML with mail addresses ending with "microsoft.com". Thu, 14 Jul 2011 10:38:25 +0000 Who wrote 3.0 - from two points of view https://lwn.net/Articles/451584/ https://lwn.net/Articles/451584/ neilbrown <div class="FormattedComment"> Partly 2.6.1 had a lot fewer commits to subsequent releases. Commit counts for the first 10 are:<br> <p> 2.6.1 680<br> 2.6.2 1252<br> 2.6.3 1431<br> 2.6.4 1407<br> 2.6.5 1571<br> 2.6.6 2020<br> 2.6.7 2796<br> 2.6.8 2650<br> 2.6.9 4148<br> 2.6.10 4510<br> <p> <p> and partly because Andrew Morton was getting a lot of patches attributed that didn't really belong to him. The counts for akpm patches in that first 10 are:<br> <p> 2.6.1 201<br> 2.6.2 477<br> 2.6.3 294<br> 2.6.4 415<br> 2.6.5 345<br> 2.6.6 618<br> 2.6.7 764<br> 2.6.8 191<br> 2.6.9 102<br> 2.6.10 143<br> <p> So about 25% of 2.6.1 and 2.6.2, and much less in the later releases.<br> (A quick look shows that the first few releases have several patches with <br> <font class="QuotedText">&gt;&gt;&gt;&gt; From: NeilBrown &lt;neilb@cse.unsw.edu.au&gt;</font><br> in the comment, but:<br> <font class="QuotedText">&gt;&gt;&gt;&gt; Author: Andrew Morton &lt;akpm@osdl.org&gt;</font><br> so I figure I should be in the exclusive "41-club" too!!)<br> <p> </div> Thu, 14 Jul 2011 08:35:48 +0000 MS only slightly behind IBM, really? https://lwn.net/Articles/451580/ https://lwn.net/Articles/451580/ kragilkragil2 <div class="FormattedComment"> But K. Y. Srinivasan is a Novell employee, right? <br> This could become a big headline so it is probably better to be safe.<br> </div> Thu, 14 Jul 2011 08:07:40 +0000 Who wrote 3.0 - from two points of view https://lwn.net/Articles/451570/ https://lwn.net/Articles/451570/ dlang <div class="FormattedComment"> a combination of tracking problems and the fact that at the time many people were still using 2.4.x with little or no intention of _ever_ migrating to this scary new 2.6 thing.<br> </div> Thu, 14 Jul 2011 06:25:48 +0000 Who wrote 3.0 - from two points of view https://lwn.net/Articles/451566/ https://lwn.net/Articles/451566/ jamesmrh2 <div class="FormattedComment"> Why was 2.6.1 was so commonly missed?<br> </div> Thu, 14 Jul 2011 05:35:26 +0000