LWN Weekly Edition
Front pageSecurity
Kernel development
Distributions
Development
Announcements
->One big page
This page
Previous weekFollowing week
| |||||||||||||
DistributionsNot quite precious: openSUSE releases SmeegolIt's been a rocky road for the openSUSE Goblin team. Initially an attempt to create an openSUSE netbook release based on openSUSE and Moblin (Goblin) that was led by Andrew Wafaa, the shift from Moblin to MeeGo took the project back a few steps. Now under the name Smeegol, the openSUSE netbook release is finally at 1.0 — but how does it fare? Smeegol 1.0 is an interesting release, but it's still rough around the edges. It is not surprising that Smeegol has some rough edges. MeeGo itself — despite the 1.0 label — is still a work in progress, as LWN's resident Grumpy Editor discovered back in June following the 1.0 Core release. There's also the fact that the MeeGo project doesn't seem to be going out of its way to work with distributions to produce derivatives. According to a recent post from Fedora Project Leader Jared Smith, the project hasn't released its compliance specifications to allow projects to use the MeeGo trademark. In an email exchange, Wafaa said that "it appears that things aren't as open now that it's MeeGo... there are certainly more hurdles in the way - the rigid trademark requirements are one example." It does appear that MeeGo has at least a draft compliance document for trademark usage. It's rather detailed, and forbids the MeeGo Core packages from being repackaged in the creation of a compliant implementation. At this point, it may be moot anyway — at least for the Fedora 14 release. Peter Robinson threw in the towel on the "mobility spin" based on MeeGo for the Fedora 14 release, citing "contention upstream" as well as a lack of time to finish it for the Fedora 14 release. Wafaa also says that MeeGo "doesn't appear to be too happy in a helping way with other distros re-spinning." When working with Moblin for the Goblin netbook project, Wafaa said that Intel seemed happy with projects using the user experience (UX) on top of another distro. Indeed, Intel took pains to assure the community that Moblin was not meant to be a distribution, but a reference platform. In one of its FAQs for Moblin developers, Intel touts the Moblin derivatives and says "Moblin is an open source project, not a product." MeeGo, on the other hand, seems a bit less eager to encourage offshoots and less responsive to requests. It wasn't until Smeegol was released that Ibrahim Haddad, director of technical alliances for the Linux Foundation, responded to the numerous requests about trademark usage. More discouragingly, Haddad says that the name Smeegol "is not in the benefit of MeeGo project" and requests that the project choose a new name. In a reaction to the trademark rejection, Wafaa posted about the difficulties in working with MeeGo. According to Wafaa, MeeGo has "closed the door" on contributions, and says that MeeGo appears to want "to build a community from OEMs and Partners" to the exclusion of the wider community. The switch from Moblin to MeeGo also impacted the Goblin/Smeegol development. Novell's engineers moved away from using a SUSE Linux Enterprise Desktop (SLED) base and to using MeeGo upstream. When Novell was working on Moblin, Wafaa says he could reuse much of that team's work in trying to package Goblin, but now the work doesn't carry over to openSUSE/Goblin as easily since it takes place in the MeeGo build system and is not SLED-based. MeeGo uses RPM for its package system, but the packages are built exclusively for the MeeGo distribution, and aren't compatible with Fedora or openSUSE. The Smeegol ExperienceSo how does Smeegol stack up? Smeegol is somewhat discriminating in what hardware it will run on. The post announcing Smeegol noted that it does not yet play well in virtualized environments, and attempting to install the Smeegol 1.0 release in VMware Workstation predictably ended unsuccessfully. The installer image also choked when trying to boot Smeegol on an Acer netbook with the dreaded Intel Poulsbo chipset. Using the "one-click" installer for openSUSE 11.3, Smeegol installed almost without a hitch on a regular laptop with an Nvidia card and an Atom-based Asus 1000HA Eee PC already loaded with openSUSE 11.3. Almost, in that the ![[Zones]](/images/2010/smeegol-zones-sm.png)
Smeegol inherits the MeeGo interface, with all that entails. That is to say, it's an interesting attempt to make the most of the netbook screen size that works well in some ways, but falls down in others. The interface is particularly frustrating when running several distinct applications and/or running applications that are not customized for the MeeGo interface. Rather than desktops, applications run in "Zones" for each window — which means a lot of switching back and forth, seeing one application at a time. In some cases only one window of an application at a time. A primary example would be GIMP, which has a default of three windows — the primary window for the image being edited, and two toolbars. Of course, it's unfair to lay all the blame on MeeGo or Smeegol here — GIMP is not an application that shines in a 1024x600 interface no matter what desktop environment it's running in. At least GIMP opens all of its windows in a single Zone, so it doesn't necessitate switching back and forth. Empathy, the default IM client, opens the contact list in one Zone and chats in another Zone — which makes it very confusing. In short, many applications are slightly out of place when run in the MeeGo UX. ![[Myzone]](/images/2010/smeegol-myzone-sm.png)
For users that are sticking to "netbook" applications, this isn't much of a problem. Smeegol's default browser (Chromium) blends into the environment, and there's a customized Banshee interface for MeeGo/Smeegol, as well a as custom Evolution interface, and so on. If you're using Smeegol for a netbook that will be doing netbook-type tasks (light Web browsing, mail, social media, etc.) then it's very pleasant to use. This is not a power-user's interface, though. Since Smeegol inherits so much from MeeGo, is there an advantage in running Smeegol over MeeGo? If users care about a wider range of packages than offered for MeeGo, or running on a wider range of hardware, the answer is yes. MeeGo doesn't offer many applications that users might want, like GIMP, AbiWord, etc. Smeegol may also be preferable for some users because of what it doesn't offer. Specifically, it uses the more mature NetworkManager instead of the default ConnMan, which is MeeGo's connection manager. Smeegol is offered as a 32-bit or 64-bit release, and users can install any packages from the openSUSE repositories. Wafaa also says that Smeegol should have a wider range of hardware support, and does not require CPUs with SSE3 support — so older Eee PCs (for example) should work with Smeegol whereas MeeGo does not. Smeegol is also, unlike MeeGo, a multiuser system. So if you share a netbook with a friend or family member, you can each have separate accounts. This is a good thing, since much of the system is meant to support very personal services like Facebook, Twitter, email, and so on. Unfortunately, Smeegol inherits one of MeeGo's less charming traits: The complete and befuddling lack of a shutdown or logout button. It seems to be a debate within MeeGo circles whether a netbook requires this, since the hardware will (in theory) be fully supported and users will simply suspend the system or power off using the hardware power button. Right now this is a bit glitchy on Smeegol, which powers off almost instantly if you press the power button. And if you wish to let someone else log in, it necessitates killing X with the Ctrl-Alt-Backspace combo. The Smeegol FutureNow that 1.0 has been released, what's next? Wafaa says that work has already begun on Smeegol 1.1, and he'd like to also develop a tablet version based on MeeGo 1.1 as well. openSUSE's Andreas Jaeger says that it's not yet certain whether Smeegol will be an official part of the 11.4 release, but would like to see that happen. Whether it makes it in probably depends on the success of Smeegol 1.0, and whether it serves as a catalyst to recruit more contributors. Wafaa noted that Smeegol is not a Novell-initiated project, though some of the team working with MeeGo from Novell have contributed as individuals. Much, though not all, of the work is being done by Wafaa in his spare time. More contributors would no doubt be very helpful to ensuring that it becomes a long-term offering and an official part of openSUSE. Smeegol is worth a look for openSUSE users who would like a customized netbook release, and for users who want the MeeGo UX without being limited to the MeeGo ecosystem of software. Smeegol has some warts, but most of those are related to the MeeGo heritage and are bound to improve over time as MeeGo matures. One hopes that the naming situation can be resolved amicably between openSUSE and the Linux Foundation, and that MeeGo will improve its coordination with downstream projects.
Brief items Distribution quotes of the week
> Why are we convinced throwing away bugs is a good idea?
-- Bryce Harrington responds to Scott Kitterman
Thank you for helping to make Ubuntu better! Unfortunately, you've not provided enough information for us to respond to the issue you've raised. We are marking your email Incomplete for now; it will expire in 30 days if we do not hear from you by then.
* if we are not granted the "right" (whatever that might mean) to use the
"MeeGo" trademark to refer to the "software that comes out of the MeeGo
project", what are we supposed to use instead? (Please don't make us use
things like "the name everyone knows but that I can't write").
-- Didier Raboud
Smeegol encounters a ring of powerSmeegol is an implementation of the MeeGo user experience on top of an openSUSE base; the 1.0 release was announced on October 6. On the 14th, the project was told that it cannot use the "Smeegol" name: "It is not in the benefit of MeeGo project to use 'Smeegol'. We therefore can not approve such usage of MeeGo mark in 'Smeegol'. We understand that you've already announced it and we will be happy to work with you to come up with a different name (for the good of the MeeGo project)." Some Smeegol developers are not pleased by this development and have announced their intent to "push back"; meanwhile, openSUSE community manager Jos Poortvliet has proposed renaming the distribution to "DarkRider". What the final resolution will be is unclear.
MeeGo 1.0 Update for NetbooksThe 4th update for the MeeGo v1.0 Core Software Platform & Netbook User Experience project release contains is available. This update fixes "many important security issues" and other bugs.
Version 2.1 of the openSUSE build serviceThe openSUSE build service 2.1 release is out, with a number of new features. "Users of the Build Service may now access a new concept called 'source services'. Source services allow, for example, the automatic checkout of source code for a package from a remote server via Git or Subversion, building a tar ball from these checked out sources, and using them for building a package. It also enables direct download of tar balls from remote sites. This allows packagers to work with external sources without downloading them to their own workstations, and makes it easy to rebuild packages after upstream changes with a single click."
Red Hat Enterprise Linux 6 Release Candidate Available to PartnersRed Hat has announced the limited availability of Red Hat Enterprise Linux 6 Release Candidate. "The Release Candidate is available to a small set of strategic testing partners, including our OEM partners, and Red Hat's independent software vendor (ISV) partners. We encourage all of our ISV partners to enable our joint customers to experience the significant enhancements in performance, reliability and security offered in this version of what is intended to become our new flagship platform by accelerating testing and final certification of ISV offerings on the Release Candidate. We expect no further changes to the ABI or API that might otherwise affect application compatibility as we finalize Red Hat Enterprise Linux 6 and make it generally available later this year."
Distribution News Debian GNU/Linux Debian welcomes non-packaging contributorsIt's official, the Debian project's general resolution which states that all contributors - not just those making packages - are welcome as project members, has passed. There were 285 votes in favor, 14 against, so it seems that this is not an especially controversial decision.
Fedora Fedora Board meeting recap, 2010 10-18Click below for a recap of the October 18 meeting of the Fedora Board. Topics include a review of blocker bugs, and F15 naming.
SUSE Linux and openSUSE Advance discontinuation notice for openSUSE 11.1SUSE Security has announced that the SUSE Security Team will stop releasing updates for openSUSE 11.1 after December 31, 2010. "As a consequence, the openSUSE 11.1 distribution directory on our server download.opensuse.org will be removed from /distribution/11.1/ to free space on our mirror sites. The 11.1 directory in the update tree /update/11.1 will follow, as soon as all updates have been published. Also the openSUSE buildservice repositories building openSUSE 11.1 will be removed."
How to contribute: openSUSE DocumentationJuergen Weigert has some pointers to finding and contributing to openSUSE documentation. "Currently the openSUSE documentation (listed below under 3.) is maintained mostly within Novell by the SUSE Documentation Team (http://en.opensuse.org/openSUSE:Documentation_team). The discussion on opensuse-marketing has shown that people are interested in contributing to this documentation--a fact that we really welcome!"
Ubuntu family Natty Narwhal open for developmentNow that Ubuntu 10.10 has been released, it's time for the cycle to begin again this time with Natty Narwhal (11.04).
Other distributions OpenBricks Embedded Linux Framework - Day 1The GeeXboX team has announced the "Day 1" of the OpenBricks Embedded Linux Framework project. "OpenBricks is a complete OpenSource and non-profit project which aims at bringing a coherent Linux distribution to run on as many embedded devices and architectures as possible. As much as possible, it tries to rely on standardized technologies, protocols and FOSS as to provide the most code re-usability. It can be used as a framework basis to build your very specific Linux distributions, corresponding to your exact and specific needs, whichever you're trying to build a Set-Top-Box, a touchscreen based multimedia tablet, a NAS, a router or whatsoever. Porting your board to Linux and adding your specific programs never has been so easy and one can easily create its own distribution flavour."
Newsletters and articles of interest Distribution newsletters
Fedora 14 Spotlight Feature: Keeping Secure with OpenSCAPRed Hat News has started a series of blog posts leading up to the Fedora 14 "Laughlin" release highlighting some of the new features. The first post looks at the inclusion of OpenSCAP. "SCAP is a line of standards managed by the National Institute of Standards and Technology (NIST). It provides a standardized approach to maintaining the security of systems, such as automatically verifying the presence of patches, checking system security configuration settings, and examining systems for signs of compromise. With OpenSCAP, the open source community is leveraging many different components from the security standards ecosystem."
Spotlight Feature: Get Mobile with Fedora 14Red Hat News continues its series with a look at Fedora for netbooks and other mobile devices. "The release of Fedora 14 is just around the corner, and one of the areas of active development for this release is mobile devices, such as netbooks. Fedora community members have integrated several different mobile development platforms for use with Fedora, including Sugar on a Stick and software from the MeeGo project. Fedora members also work to bring Fedora to new hardware platforms."
Page editor: Rebecca Sobol |
|||||||||||||