Forgot your password?
typodupeerror
Microsoft Software Linux

Microsoft and Novell Open Interoperability Lab 113

Posted by ScuttleMonkey
from the still-in-the-skeptic-camp dept.
An anonymous reader writes to mention that the Microsoft and Novell Interoperability Lab in Cambridge, Massachusetts opened today. The lab is supposed to allow both Novell and Microsoft developers to work together for better interoperability between SUSE and Windows Server. "Located in Cambridge, the 2,500-square-foot lab and workspace will be home to a combined team of the best and brightest Microsoft and Novell engineers focused on making Windows Server and SUSE Linux Enterprise work better together. The first priority for the lab team will be to ensure interoperability between Microsoft and Novell virtualization technologies. Additional work will include standards-based systems management, identity federation and compatibility of office document formats."
This discussion has been archived. No new comments can be posted.

Microsoft and Novell Open Interoperability Lab

Comments Filter:
  • Peer or puppet? (Score:5, Interesting)

    by alext (29323) on Wednesday September 12, 2007 @01:22PM (#20575567)
    An obvious benchmark to track is the number of changes going into the Windows Server product for compatibility vs. those going into Suse Linux.

    If Suse has to make all the running it will be pretty obvious who is wearing the trousers (as we say).
  • by Weaselmancer (533834) on Wednesday September 12, 2007 @01:37PM (#20575819)

    Phase one - embrace. [linux-watch.com]

    Phase two - extend. [slashdot.org]

    Phase three - extinguish. [wikipedia.org]

    Been good knowing you, Novell.

  • No research needed (Score:3, Interesting)

    by Mateo_LeFou (859634) on Wednesday September 12, 2007 @01:44PM (#20575947) Homepage
    I love the monthly new-years-resolutions to work harder at/invest more in interoperability.
    It's actually not that difficult. Have most of your apps spit out strings of text in some documentable (or, ideally, document*ed) format and basically voila!
    What's difficult is having interoperability without actually having it. In fact, I suspect they could research that until doomsday.
  • Re:itsatrap? (Score:2, Interesting)

    by ch-chuck (9622) on Wednesday September 12, 2007 @01:45PM (#20575961) Homepage
    I remember the "Novell Migration Tool" from circa 1996 - it allowed you to 'legally' voilate Novell license agreement (more than the licensed number of users could connect to a Novell server).
  • by Anonymous Coward on Wednesday September 12, 2007 @01:46PM (#20575993)
    Having this on one's Resume is going to be a red flag. I for one will be shooting down anyone with this on their Resume. It's right up there with having semi-recent SCO experience on your Resume IMO.

    Good luck to the "top" engineers who end up working there. You are a pariah, possibly to both camps.
  • Re:itsatrap? (Score:3, Interesting)

    by value_added (719364) on Wednesday September 12, 2007 @02:03PM (#20576329)
    In this case, for instance, I'm willing to believe that the MS engineers joining this interoperability effort will genuinely do good work towards making MS products work with Linux in a smart and efficient way.

    Not to be flippant, but wouldn't a "smart and efficient way" include a decision on the part of Microsoft to stop "not interoperating"? Seems to me that over the years they've actively and repeatedly pursued a course that was designed to maintain monopoly and thwart interoperability of any sort.

    Then again, maybe this development is like the situation in the Middle East. Having members of the opposite sides in the same room talking with one another while everyone outside is fighting can be viewed as a positive step, even if shouts of "traitor" are heard through the windows.
  • Re:Hmmm... (Score:3, Interesting)

    by h4rm0ny (722443) on Wednesday September 12, 2007 @02:33PM (#20576815) Journal

    WINE actually provide a useful service that helps third party applications that were originally only developed for Windows to migrate to Linux. The project that does what you warn about is Mono, which encourages Linux developers to adopt proprietary Sue You Later frameworks without thinking about it. And Mono, co-incidentally enough, is the one with the close, close ties to Novell. I wouldn't touch SuSE with a 50m CAT5e cable, right now.
  • Re:itsatrap? (Score:4, Interesting)

    by michrech (468134) on Wednesday September 12, 2007 @02:42PM (#20576967)
    What's worse, MS really never had to do any of the work. All they had to do was document their protocols (and provide them in a GPL friendly way) so that the Samba folks (for example) could create *all* the software to make everything work. On top of that, MS could have reaped TONS of free positive publicity.

    Though I am stuck using MS at work, and at home (for a couple games I like to play that aren't available/playable on any other platform), and don't really mind using the products (because, in this case, they are the right tool for the job), I very much dislike the company (in the way it does business... I'm sure at least some of the people that work there are great people otherwise...)

    Not to be flippant, but wouldn't a "smart and efficient way" include a decision on the part of Microsoft to stop "not interoperating"? Seems to me that over the years they've actively and repeatedly pursued a course that was designed to maintain monopoly and thwart interoperability of any sort.
  • notice something? (Score:2, Interesting)

    by AlgorithMan (937244) on Wednesday September 12, 2007 @05:47PM (#20579719) Homepage

    making Windows Server and SUSE Linux Enterprise work better together. The first priority for the lab team will be to ensure interoperability between Microsoft and Novell virtualization technologies.
    notice, that the aim is interoperability with NOVELL, not GNU+Linux
    This must mean that they're mixing SUSE with MS Patents again, which means more vendor lock-in for Novell customers...

    I don't think there is any reasonable explanation, why MS is creating vendor lock-ins for Novell customers, except that they plan to buy Novell some day... (remember: Steve Ballmer saied they had found THE strategy against linux, "the enemy" - and only 7 month later, after "several months of negotiations" they made the deal with Novell.... there HAS to be something wrong about that....)

"Life, loathe it or ignore it, you can't like it." -- Marvin the paranoid android

Working...