Novell and Intel Team Up For Moblin On Netbooks

ruphus13 writes "The Mobile and Netbook space already has several Open Source OS providers. Android has been making its way into netbooks, and Moblin, LiMo and Ubuntu are also alternatives for OSes on netbooks and mobile handhelds. Now, Novell has also joined the fray, but rather than porting openSuSE, they have teamed up with Intel to get OEMs to use Moblin for their mobile devices. From the article: 'With the other tools and benefits that Moblin offers OEMs and developers, it's really a rather smart approach that could potentially yield a better netbook experience (for developers and consumers), maximize development resources, and produce quality software in minimal time. I don't think Novell is eschewing SUSE, but in its current form, it's not as suited for netbooks as it is systems like the HP ProBooks. Paired with Moblin's netbook-centric bent and coming from a desktop/server market (rather than a true mobile device background), bringing a SUSE/Moblin system to netbooks has as much potential (if not more) for success as an Android adaptation does.'"

Re:Moblin?

[Anonymous Coward]

Is it not more like MOBile LINux?

Re:Great a notebook with a broken package manager

[crush]

Most of the tasks which you list below can be handled by Fedora-originated, distro-agnostic tools such as YUM or PackageKit. (Well, YUM is only distro-agnostic to the extent that it must be an RPM-based distro).

* unused packages removal - ie, if a a package is only installed as a dependency, and if no package which depend on it are still installed, the package can be automatically removed.

This is handled in Fedora with the use of the yum extension package-cleanup and using one of the "leaf-node" options.

* suggested packages, ie., packages has a list of packages which enhances the package in quesiton.

PackageKit does this in recent versions of Fedora, see this link [fedoraproject.org] for information on Fedora 11 font and mime-type installation.

* recommended packages, ie, packages which are not strictly required but should normally be installed with a package.

Not sure about this, seems like the previous point?

* support for packages deprecating and/or providing other packages

Obsoletes: is a feature of RPM since way-back

* support for running configuration utilities and such during installation

Again, since way back whenever it has been possible to run scriptlets in RPM specfiles.