Comments on: Microsoft submits GPLv2 code to the Linux Kernel http://thedaneshproject.com/posts/microsoft-submits-gplv2-code-to-the-linux-kernel/ Knowledge bling's the finer things in life. Fri, 10 Feb 2012 05:10:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Danesh http://thedaneshproject.com/posts/microsoft-submits-gplv2-code-to-the-linux-kernel/comment-page-1/#comment-47159 Danesh Tue, 21 Jul 2009 09:38:57 +0000 http://thedaneshproject.com/?p=1656#comment-47159 well said dude.... PR for sure!! I agree... let's see what happens.. I'm still Linux all the da way... well said dude…. PR for sure!! I agree… let’s see what happens..

I’m still Linux all the da way…

]]> By: Arstan http://thedaneshproject.com/posts/microsoft-submits-gplv2-code-to-the-linux-kernel/comment-page-1/#comment-47158 Arstan Tue, 21 Jul 2009 09:29:15 +0000 http://thedaneshproject.com/?p=1656#comment-47158 Few concerns: 1. What? What is it that they want to submit? It's a set of drivers which enables better performance(Linux already works on it) of Linux on top of Hyper-V(M$ Virtualization product). Microsoft would like to commit those drivers directly into the core of the kernel. Now this all rises second question WHY? 2. WHY? Sun, VMWare have been doing the same thing without committing their drivers into the kernel core! Why not just follow their steps? It is already known that out of the tree modules are great. You do not need to tie up for specific kernel version to run your guest OS. 3. If you pay attention at the codes, it is written in the M$ style. Not following coding standards of linux kernel. As well as they brought in all NT way of writing codes. I dunno, if they even defined NULL nothing more to say. :) 4. M$ again in its glory. This is just pure PR. Now before this codes gets to the staging tree of the linux kernel there must be hell of a job to be done. You can just take a look at any driver developments for the kernel. You will see that until the drivers have met all the requirements, coding styles/standards, make sure they run on all archs it will be sent back to the developer. Since they release it open source, that means lots of devs will be involved in the process. Which is win for M$, release shitty code and wait others to fix it. Arstan Few concerns:

1. What? What is it that they want to submit? It’s a set of drivers which enables better performance(Linux already works on it) of Linux on top of Hyper-V(M$ Virtualization product). Microsoft would like to commit those drivers directly into the core of the kernel. Now this all rises second question WHY?

2. WHY? Sun, VMWare have been doing the same thing without committing their drivers into the kernel core! Why not just follow their steps? It is already known that out of the tree modules are great. You do not need to tie up for specific kernel version to run your guest OS.

3. If you pay attention at the codes, it is written in the M$ style. Not following coding standards of linux kernel. As well as they brought in all NT way of writing codes. I dunno, if they even defined NULL nothing more to say. :)

4. M$ again in its glory. This is just pure PR. Now before this codes gets to the staging tree of the linux kernel there must be hell of a job to be done. You can just take a look at any driver developments for the kernel. You will see that until the drivers have met all the requirements, coding styles/standards, make sure they run on all archs it will be sent back to the developer. Since they release it open source, that means lots of devs will be involved in the process. Which is win for M$, release shitty code and wait others to fix it.

Arstan

]]>