Open Source

Mobile OS MeeGo code opened to developers, SCO smackdown, Microsoft updates Linux code

There has been some fairly substantial Linux news this week; MeeGo mobile OS code is now open to the Linux community, another nail is hammered in SCO Group's coffin, and Microsoft updates its Hyper-V Linux code.

Intel and Nokia announced the next step of the Maemo-Moblin merger, which opens the source code to the open source community for development. From the MeeGo community blog, this is specifically what is available:

What are we opening? The MeeGo distribution infrastructure and the operating system base from the Linux kernel to the OS infrastructure up to the middleware layer. The MeeGo architecture is based on a common core across the different usage models, such as netbooks, handheld, in-vehicle, and connected TV. The MeeGo common core includes the various key subsystems including the core operating system libraries, the comms and telephony services, internet and social networking services, visual services, media services, data management, device services, and personal services.

The available images can be downloaded here, the corresponding RPM repositories here, and the git repositories here.

Earlier, I wrote about MeeGo as the possible Linux answer to Apple's iPad. The challenge for MeeGo remains in getting developer interest when everyone and her brother wants to develop apps for iPhones and iPads, not to mention Google's Android and RIM. Still Intel and Nokia are forging ahead:

Intel and its partners plan to release a finished version of MeeGo in May. Third-party applications will be available for MeeGo devices through Intel's AppUp Center, an online store that will also be open to consumer electronics makers.

SCO beat-down

If you're still following the long-running SCO vs. the World battle over Unix copyrights, you can get the full scoop at Novell won it's latest case against them when a jury decided that Novell owned the Unix copyrights. Groklaw quotes the statement from Novell, short and sweet:

Today, the jury in the District Court of Utah trial between SCO Group and Novell issued a verdict.

Novell is very pleased with the jury's decision confirming Novell's ownership of the Unix copyrights, which SCO had asserted to own in its attack on Linux. Novell remains committed to promoting Linux, including by defending Linux on the intellectual property front.

This decision is good news for Novell, for Linux, and for the open source community.

Microsoft updates code for Hyper-V Linux Integration Services

Microsoft released several enhancements to Hyper-V Linux that it first introduced in 2009. These updates include:

  • SMP support for up to 4 virtual CPUs
  • Integrated shutdown, which provides the ability to gracefully shutdown Linux from the Hyper-V console (management partition)
  • Timesync, which keeps the time in the guest OS synchronized with the management partition.

The beta version can be acquired through Microsoft's Connect page here.


Selena has been at TechRepublic since 2002. She is currently a Senior Editor with a background in technical writing, editing, and research. She edits Data Center, Linux and Open Source, Apple in the Enterprise, The Enterprise Cloud, Web Designer, and...

Neon Samurai
Neon Samurai

While no one really contributes to the kernel or other FOSS code for unselfish reasons, MS only contribution apears to be an update to the minimal code provided to make Linux based platforms run better under Microsoft's virtualization. I'd give them more credit if it was voluntary contributions to more general areas rather than one's meant to maintain Windows dominance. We'll see what MS latest "we love Open Source" anouncement actually results in though as one of the promises is code and information related to more general code areas. I'm personally open to the idea of a newer more resonsible fair-competition Microsoft, but I need to see ongoing actions not just marketing sound bites.


MS is so big that can do that. MS = 93% linux = 0.8%

Neon Samurai
Neon Samurai

I really have to do some digging around the Maemo forums and see if anyone else understand this; why RPM? I get merging Maemo Linux and Moblin but shouldn't that involve the strengths from each distribution? They seriously looked at DEB and RPM then chose the latter over and apt-get or aptitude management? This is like deciding to go offroading and choosing your Pinto instead of your Jeep. Unless they have done some serious work around the RPM package format or compiled all apt-get related tools to work with RPM; it's a big enough decision to turn me off Meego and I've been a frothing Nokia fan since discovering the Debian forked Maemo Linux on my N800 years ago. I'd honestly like to understand the reasons behind that decision. Since Meego updates where announced for the N900, the packaging decision is probably the only sticking point for me. Simply put, the number of "crap, how do I fix this" RPM related issues I've had simple DEB solutions for alone cause me questions over this one.

Editor's Picks