To view parent comment, click here.
To read all comments associated with this story, please click here.
Again as long as Novell is not including the code in Linux and there is from the community no IP infringement code added in Linux then again How is the deal a problem. The MS code would have to run on top as is the case with Groupwise and eDirectory!
Microsoft does not have a leg to stand on as long as the community stays true to innovation and creativity. Opposing this deal often seems like a way for the community to potentially include the code and ask vendors to duke it out vs. being accountable for the code that is included. Again Because Novell does not own the Linux I see nothing wrong with collaborating to have applications run on top of Linux It could be exchange for all I care as long as the Linux remains Linux. I do believe this will be the case
Again as long as Novell is not including the code in Linux and there is from the community no IP infringement code added in Linux then again How is the deal a problem. The MS code would have to run on top as is the case with Groupwise and eDirectory!
Because then only Novell would be able to interoperate by providing Linux file services to Microsoft Windows? That's not interoperability in my book, unless you consider the fact that software from one division of Microsoft works well with another as "interoperability".





Member since:
2006-04-21
The worry is this:
That MS will, in effect, create a proprietary Linux by, for example, launching a suit against RedHat which forces them to stop distributing GPL code for reading MS filesystems, and then allowing Novell to include code for reading MS filesystems, whether GPL'ed or not.
That will, in one stroke, create a significant barrier to interoperability between MS and any version of Linux distributed by anyone who isn't, to use a crude description, Microsoft's bitch.