Planet openSUSE

Nelson Marques: A chance to contribute to FOSS: Help ‘tatica’ going to Vienna

Sun, 29 Jan 2012 19:03:10 +0000

I would like to share something that came to my knowledge through Facebook, and though I don’t know ‘tatica’ personally, I did traded a few emails with her in the past and know that her contributions are always awesome.

If you can help, please consider donating a few bucks to help this awesome FOSS contributor attending one of the major events in the field of her contributions!

To help ‘tatica’ please click on the image!

Original Text from the Campaign (source: http://pledgie.com/campaigns/16632):

“Maybe you know that girl here. You know she does a lot for FLOSS, using GIMP, Inkscape and Blender. Its not that she makes only graphics for Fedora and a lot of othere FLOSS-projects or events. She also give her knowledge always to others, giving talks and workshops on events or producing screencasts.

She always wanted to see an FLOSS event in europe, so the Libre Graphics Meeting and LinuxWochen Vienna would be the right event for her.

There is only one problem, flights from south america to europe are really expensive. From Caracas to Vienna is mostly between 1500 and 1700 $, why 2500 then. So maybe we can pay the hotel also? “

Fred Blaise: btrfs consuming lots of sys cpu time

Sat, 28 Jan 2012 21:46:41 +0000

fblaise@snowball ~ $ ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10
%CPU PID USER COMMAND
7.4 2591 root [flush-btrfs-1]
5.9 905 root [btrfs-endio-0]
4.4 2907 root [btrfs-endio-wri]
4.3 1314 root /usr/bin/X :0 vt7 -nr -nolisten tcp -auth /var/run/xauth/A:0-VjxI1a
2.7 900 root [btrfs-worker-0]
1.7 2106 fblaise /usr/bin/knotify4
1.4 2094 fblaise kwin
0.6 10 root [kworker/0:1]
0.5 3643 fblaise top

And it is only on my /home filesystem… system is currently sitting idle. Wow.

This is on a Linux Mint laptop with 3.0.0-13-generic-pae.

Anyone experienced this?

Stefan Seyfried: Using IRMP with Arduino

Sat, 28 Jan 2012 12:10:24 +0000

I needed to implement an infrared remote control decoder, so certainly I took out my Arduino and hooked up an IR sensor chip to pin 2. Then the interesting thing started. Looking around, I found ladyada’s tutorial on IR sensors. However, the method used there is pretty limited (you basically record a sample of each key signal and then compare the received signal to your samples) and unreliable for many protocols.
Then I found IRMP (german only link, sorry) which is a very versatile IR decoder for many protocols. However, IRMP is made to be used with plain avr-gcc, not from within Arduino’s IDE.
But fixing that was really not very hard.
The results are available on gitorious, project arduino-addons/irmp-arduino, including a simple example sketch to test the decoder.

Note that I’ll probably rebase the git tree whenever something happens in the IRMP SVN repository, so be aware of that in case you make local changes to the code and want to update from my tree.

Have fun!

Bruno Friedmann: ATI/AMD fglrx 8.930 Catalyst 12.1 rpm available for openSUSE 11.3, 11.4, 12.1

Fri, 27 Jan 2012 16:35:39 +0000

AMD/ATI Catalyst 12.1 / fglrx 8.930 rpm are available

Sorry I missed in December the annoucement release for the 8.920, but from what I’ve seen. zypper up do the job for you

Quick Résumé about 12.1

AMD rename their installer, So Sebastian did the same for his script.

I will just copy/google translate/paste here the comment made by Sebastian Siebert on his blog :

With this version AMD Catalyst Gnome 3.2 issues (flickering and screen cracks) are finally resolved.
According to AMD, the notebook with the PowerXpress technology (Intel-/AMD-Grafikkarte – discrete GPU) should work again.
I would be grateful if someone could test this functionality for me and give me feedback. Thank you.

See more at Sebastian’s blog. Don’t be shy, you can leave there the result of test in english too
See below what to do in case of troubles.

The rpms version 8.930 are available from Friday January 27th

My advise is to firstly remove any existing version with zypper rm, then just zypper in the new version, even if 8.930 are the first version I’ve seen making its upgrade correctly.

As usual, I let the last 2 previous versions in the repository, just in case you need it.

Catalyst 8.930 fglrx 12.1 in action

Tested on a fresh 12.1 + updates with a stock kde 4.7.2

Factory rpms are not available actually, I’ve not be able to build a new building machine for it.
Anyways, factory and 12.2 should keep their effort on debuging and testing widely the free radeon driver.

One-click-installer

As nobody killed me about the one click installer available, I upgrade its status to RC (feedback welcome)
For 32bits system :

For 64bits system :

(*) To know which kind of system you have, open a console, then run uname -a, and look the output if you see x86_64 on the line you are running a 64bits, otherwise a 32bits.

Installation, Caution, Troubles

Installation

Please refer to my previous article where all the installation procedure are explained.

For a first installation, if you don’t remove radeon from the initrd, you will get in trouble. Don’t thanks who removed that from the wiki.

Caution

Wrong (to my point of view) create an xorg.conf file which is unneeded if you work with /etc/xorg.conf.d/50-device.conf and have driver “fglrx” inside
AMD CCLE didn’t get correctly upgraded if xorg is running during the upgrade. My advise, let’s go to console and as root do the following :
```
init 3
rcatievenstd stop
zypper ref
zypper up
init 6
```
Let the package rebuild the kernel driver. And for me I always remove the newly xorg.conf file created.
reboot is mandatory!

Debuging troubles

I recommend in case of trouble the use of his script which can collect the whole informations needed to help you. then you just have to issue a simple commande in console to collect all informations, you can review them, and finally transmit them

su -c 'sh makerpm-amd-12.1.sh -ur'
The sytem report 'amd-report.txt' was generated.                                                                                                                    [ OK ]
Do you want to read the system report 'amd-report.txt' now? yes/no [y/n]: y
Are you sure to upload the above-named system report to sprunge.to? yes/no [y/n]: y

The report was uploaded to sprunge.us.
   The link is:  http://sprunge.us/ZVRP

Copy paste the link in the comment zone of Sebatian post

Statistiques

December 2011 as shown a big bump on the server : 50,212 unique visitor for a roughly 320GB traffic for the rpm

1582GB has been distributed during 2011.

That’s all folks! Have fun!

Michael Wolf: yeah, sounds about right

Thu, 26 Jan 2012 19:49:19 +0000

Sascha Manns: Skype with Plasma Active

Thu, 26 Jan 2012 19:25:34 +0000

You have an Touchpaddevice and you're looking for an free and open source operatingsystem, touchfriendly and with a KDE UI?

Then you maybe have heard about Plasma Active. Plasma Active is a new UI specially developed for touch-devices. You can download it there from open-slx. That image is prepared to install Plasma Active on the Top of Balsam Professional.

In this Article you can see how to prepare the stick. After booting and installing you have a Plasma Active on your device. You also can use Plasma Active inside a Dual or Multiboot Installation.

But we want to use Skype for this device.

First of all you have to surft to: http://www.skype.com/intl/de/get-skype/on-your-computer/linux/downloading.suse . After accessing the site it will be prepare the download. Just save it any place.

Change now to that directory which contains the saved package. Type in your console:

sudo zypper in skype-2.2.0.35-suse.i586.rpm

After the installation you will see the Skype Icon in the Applicationlauncher.

Tap now on that icon. Now opens the graphical client as you maybe know from the desktop. Tap on Username and type there your Username with the virtual keyboard. Sadly the virtual keyboard doesn't see the Password field. That means that you have to use an external USB Keyboard for this field.

After the Login you can use it through tapping on it. If you tap on the Text field you can use the virtual keyboard. If you like to call anyone just tap on the phone icon.

The integrated WeTab Webcam is supported directly without any changes.

You can plug in a Headphone into the WeTab. A seperate port for a microphone isn't placed there. But the WeTab has a integrated microphone which pacify in most cases.

Updated 27.1.12: Changed the packageinstall from rpm to zypper.

Fridrich Strba: FOSDEM 2012 - How to make the best of it and become LibreOffice developer

Thu, 26 Jan 2012 14:49:15 +0000

FOSDEM 2012 is just round the corner and, as you might know, LibreOffice will have a DevRoom this year too. And, as it was already publicized, your servant and Eilidh McAdam of libvisio fame will attend too. The goal of this event will be to help you to become a LibreOffice developer, by helping you to get your first contact with the code from inside.

How to prepare for the event?

In order to give as many community members the possibility to speak, the presentations will not take more then 15 minutes each. But we will be there for one-to-one contacts and hacking goodness. If you are interested in contributing to our new Visio import filter, or the upcomming Corel Draw and MS Publisher filters, here is what you can do:

Find a bug that is bothering you in the current Visio import filter, or some simple feature that the importer currently does not support
Check out the following libraries:
- master branch of libwpd (git clone git://libwpd.git.sourceforge.net/gitroot/libwpd/libwpd)
- STABLE-0-2-0 branch of libwpg (git clone -b STABLE-0-2-0 git://libwpg.git.sourceforge.net/gitroot/libwpg/libwpg)
- master branch of libwps (git clone git://libwps.git.sourceforge.net/gitroot/libwps/libwps)
- master branch of libvisio (git clone git://anongit.freedesktop.org/libreoffice/contrib/libvisio), and
- master branch of libcdr (git clone git://anongit.freedesktop.org/libreoffice/libcdr)
Build them as system libraries and install them in the same order.
Then build LibreOffice according to these instructions. The important thing is to use those system libraries that you just built. To do so, be sure you added to the configure flags
- --with-system-liwpd
- --with-system-libwpg
- --with-system-libwps
- --with-system-libvisio
- --with-system-libcdr

With this kind of build, you will be ready to make the most from your Brussels weekend. Nevetheless, you can drop around at our IRC channel #libreoffice-dev channel at irc.freenode.net for more information and ideas.

Starting to do it instead of planning to do it ...

... is the best way to enter the FOSS development. That is why your servant and Eilidh will be around to hold your hand with debugging and finding way to implement your favourite features. We will answer your questions about the library design. We will point you to the place in the code where your bug might linger. And for more complicated stuff, we will debug it with you.

Don't expect us to give you a fish, but we will certainly teach you how to catch it by yourself. And in the same token, you will become a contributor inside a community of smart people that is fun to hang and hack with.

See you in Brussels the 4^th and 5^th of February 2012.

Duncan Mac-Vicar: On Java, Maven, JPP and rpm

Thu, 26 Jan 2012 10:06:39 +0000

Java on Linux has been always a “special” topic. They don’t mix well.

The mindset of Linux distributions is very different to the Java world when it comes to build software. This is understandable as they have different requirements.

In the Java world, there is the concept of artifacts. You build org.foo.bar:bar-moo:1.1 once and it stays there forever, archived for anyone to use it. Tools like maven and ivy allow developers to specify in their source tree the specific dependencies of their components and those are grabbed from the network, the software built and then publish the output as a new artifact that others can grab.

Linux distributions on the other hand, bootstrap the complete stack from source. They don’t take the binary artifact from upstream but build it, and then use the binary they built to build the next. This seems to work pretty well for C, C++, and for Ruby, Python, let’s say it “works”.

When it comes to package Java software, Linux distributors find themselves in the following situation:

If a buildable source tarball is provided then you are lucky.
If the buildable tarball is provided, it will either include a directory full of binary jars (the build dependencies) or it will have a very automatic build system grabbing them from the network.

This clashes with Linux in various edges:

Linux distributions have normally one version of each component. The Java method works well if you bundle your dependencies inside your application, but not if everything is a reusable component. I have mixed feelings here. I think bundling your dependencies in the application for everything that is not part of the “base” system is the right approach. Updating them can break the application and trying to control this via QA only moves QA from the application developers to the distribution itself. When I ship apache-commons-collection as part of my Foobar Java application as a Java package, I am inviting everyone to use it, forcing myself to give support for it out of the context of the application.
Distributions needs to build from source. Even if you get rid of the above requirement and you bundle all your dependencies, distributions want to build everything from source. This has technical and legal reasons. SUSE build system does very complex checks on every package that it builds. Those checks are part of the quality we sell to our customers. Other reasons are legal: I am still trying, for example, to build the Play! framework. Even if it is BSD, it includes some .jars inside of unknown origin. What would happen if one of these jars results to be proprietary?. Michael Vyskocil had a similar issue with openproj and its bundled dependencies.

Another reason to build from source is support. Enterprise distributions sell support and if a customer has a problem, we will fix it on our own and not wait for upstream to release a new version. Having a standardized way to build from source with our own fixes allows us to serve our customers. We can bundle jars in our application, but if a bug traces back to a jar we included, we would need to change the complete build description of the product in order to take this component. If we are able to rebuild this component at all. It already happened to us once with an XML-RPC library. And we were glad that it could be fixed by adding a patch to the rpm build description.
Grabbing dependencies from the network just does not work. All packages are built without network access for security reasons.

Because the Linux distributions know that they are not the center of the universe, they adapted. At the beginning things where still ok. Ant was very popular and basically you recursively packaged all build dependencies until you could build your package, in the same way:

unpack
delete all binary jars
set CLASSPATH to the jars grabbed by the packaged build dependencies
call ant
install the jars

Something like this:

%prep %setup -q


# remove all third party jars

find . -iname '*.jar' | xargs rm -rf
%build

export CLASSPATH=$(build-classpath foo)

ant

Until this was true, the world was still fine. ant needed bootstrapping, but this was doable.

Until Maven…

Maven is at the same time revolutionary and one of the biggest atrocities I have seen when building software.

On the positive side:

it defined a common convention for modules: groupId, artifactId, version.
it defined a standard layout for the source tree
it started a wave of convention over configuration that Java was always lacking

on the negative side:

it requires itself to build itself
it can’t build much itself, so it requires plugins to build anything
plugins require maven to be built, plus more dependencies, which are usually require maven to build, plus… plugins.

All the above means that maven basically requires all the software it is supposed to build. Not the best design for a build system.

To make things worse, maven grabs dependencies from the network, which is what is disabled in our distro build process.

Fedora has done quite a progress providing a maven stack, by improving extending on the conventions the JPackage project started for maven packages. This is implemented using what is called a “dependency map”.

The approach works by installing some xml files per-package that map the maven artefact identifiers (groupId, artifactId) to a local jar in the system. Then maven itself is patched to include a resolver for artefacts with some properties:

ignores multiple versions (usually in Linux you have one version installed)
resolves the artefact names to local installed jars. Every package uses macros to add stuff to the dependency map

What I don’t like for this approach is:

Why would anyone in their sane mind use XML files to create mappings to files when you are in a UNIX-like OS and you have the filesystem and symbolic links?.

It is very explicit. It does not rely on a simple convention.

A second issue is how packages are built. This is SUSE specific. Fedora can bootstrap packages with circular dependencies by introducing a binary package A, build other dependencies until it can build a real A. Once a package is built, it stays in the buildsystem frozen as an artefact (just like the Java world).

In the openSUSE Build Service, the repository is always ready to bootstrap. For circular dependencies you create a package A-bootstrap that provides A and set the project config to prefer A. When A does not exist, A-bootstrap is grabbed, but as soon as A is there, it is preferred and used. When a package changes the packages depending on it are rebuilt automatically. This approach has several advantages, but makes hard to bootstrap a collection of packages where everything depends on everything.

In openSUSE, we have successfully build many maven dependent packages in the Java:base project without having a maven package by using the maven ant plugin to generate a tarball with ant build files.

This method does not work for every package, specially when files are generated, then one needs also to include those. But they may be good enough for solving our specific bootstrapping problem. The question is how many bootstrap packages would we need.

Another idea is to use package with binary jars for bootstrapping.

Fedora is not very happy with the current situation either, and they have been researching adding native support to Koji to build maven packages.

In any case, I think there is room for improvement everywhere. I think the Maven infrastructure can be simplified taking into account that what maven contributed to the world was a (now) popular way to identify a module, and this is now being used also outside of Maven. Apache Ivy, SBT, Gradle, etc all support maven-style repositories and support refering to an artefact as groupId:artifactId:version.

Why not instead of a depmap just have:

/usr/share/java/foo.jar
/usr/share/java/org.bar/foo.jar -> /usr/share/java/foo.jar
/usr/share/java/org.bar/foo.pom

And have the Maven patched resolved to just look there?

If you need parallel versions, then just

/usr/share/java/foo1.jar
/usr/share/java/foo2.jar
/usr/share/java/org.bar/1.0/foo.jar -> /usr/share/java/foo1.jar
/usr/share/java/org.bar/2.0/foo.jar -> /usr/share/java/foo2.jar
/usr/share/java/org.bar/1.0/foo.pom
/usr/share/java/org.bar/2.0/foo.pom

Or use the standard alternatives:

/usr/share/java/foo.jar -> /etc/alternatives/foo.jar

The resolver would first look for the specific version described in the .pom file as /usr/share/java/$groupId/$version/$artifactId.ext. If it is not found, it could fallback to just look for /usr/share/java/$groupId/$artifactId.ext. This supports most cases where we just have one version for the system and exceptions for some packages where providing a specific version in parallel is also required. If the same jar is also known under a different groupId, well, then you create another symlink.

Then, build-classpath is enhanced so that in addition of being able to say ‘build-classpath commons-logging’ you can also call ‘build-classpath commons-logging:commons-logging’. Identify every module by this convention.

The same with Provides: java(commons-logging:commons-logging). Fedora is already doing this as mvn(..), but is this maven specific?.

Why do we need xml files with maps, fragments of XML files that need to be updated at install and uninstall time?.

Looking for a new solution…

I discussed this with Fedora developers Alexander Kurtakov and Stanislav Ochotnicky and they mostly agreed with my concerns. They pointed me to Carlo de Wolf’s work on a similar solution, but using a standard maven repository layout.

Carlo’s solution does not touch maven but is implemented as a plugin that gets loaded using a custom config file that is used when you call the wrapper script fmvn instead of mvn (for Fedora-Maven).

The whole solution as they described it has some extras like macros to symlink the maven repository artifacts so that they can be found as artifacts in the JPP layout. I am not sure if we need this. What I like from the solution alone:

It does what you expect: uses only the local repository and ignores versions (uses latest) if the requested version is not found.
It does not require macros. We need to build stuff on released distros and it is no fun to introduce new rpm macros.
It does not require patching maven. fmvn is a separate package, providing the plugins and the wrapper script.
As soon as Carlo gets “mvn install” working, there is no need to manually install the jar/pom in the spec file. Just calling “fmvn install” should build and install it.

I have been playing with Carlo’s plugins and it looks very promising. Fedora would need time to switch to a solution like this, but at SUSE we don’t have maven in our stack so we have nothing to lose and at the same time we can help serving as a test bed.

The current plan…

Not having the need to patch maven allows us to use a vanilla build of Maven for bootstrapping.

maven-bootstrap (upstream binary release, Provides: maven)
fmvn-bootstrap (binary jars built locally with maven, Provides: fmvn)

Note: If you have more than one package with the same capability and want to use it in (Build)Requires, you will need to setup “Prefer:” in prjconf.

We would like to build now maven using fmvn. Here is where the circular dependencies start. We need maven (provided by maven-bootstrap) and it dependencies, like plexus and a big bunch of maven plugins.

Here is where pom2spec comes to the rescue. This script allows to quickly create bootstrap packages from search.maven.org. It is based on Pascal Bleser’s script.

So lets say I need a bootstrap package for maven-compiler-plugin:

org.apache.maven.plugins:maven-compiler-plugin : using version 2.3.2 Writing maven-compiler-plugin-bin.spec Done Downloading maven-compiler-plugin-2.3.2.pom... ######################################################################## 100.0% Downloading maven-compiler-plugin-2.3.2.jar... ######################################################################## 100.0% t http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom _ http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar

Which generates the following files:

maven-compiler-plugin-2.3.2.jar maven-compiler-plugin-2.3.2.pom maven-compiler-plugin-bin.spec


If I build it, I get an rpm with the following layout:


/usr/share/java/maven-compiler-plugin.jar

/usr/share/maven/repository/org/apache/maven/plugins/maven-compiler-plugin/maven-compiler-plugin-2.3.2.jar

/usr/share/maven/repository/org/apache/maven/plugins/maven-compiler-plugin/maven-compiler-plugin-2.3.2.pom


/usr/share/java/maven-compiler-plugin.jar is just a symlink to the real jar. This layout is enough for fmvn to find the artifact and also for legacy packages to just use build-class-path. It would still be better to enhance build-class-path to also accept groupId:artifactId keys and return the path to the jar.
The -bin suffix is to allow then the real package (built from source) to coexist in the same repository. The package with the -bin suffix also "Provides:" the package without the suffix so it can be used by dependent packages. Actually both "Provide:" java(org.apache.maven.plugins:maven-compiler-plugin) which is what a package that depends on it should "BuildRequire:".
Once Carlo's resolver works with "mvn install" I will try to build a repository following this method.



SUSE Studio: Full functionality for openSUSE on EC2
Thu, 26 Jan 2012 08:56:07 +0000
If you were waiting for Studio to support the latest version of openSUSE on Amazon's EC2, listen up: Your wait is over.
The same goes if you tried to upload an older version of openSUSE to EC2's latest region, Sao Paulo. Studio finally offers full functionality for all openSUSE versions on all EC2 regions.


Of course, SLE still offers a wide range of advantages over openSUSE. Just think about long term support, stability or getting updates for your system. However, if you chose to create your appliance based on openSUSE, you are now finally able to use Studio to take your first steps into the cloud.


Have a lot of fun!


Nelson Marques: ‘tirpitz’ – you sunk my battleship…
Wed, 25 Jan 2012 22:10:10 +0000
I’ve forked Linux Mint Welcome Screen into ‘tirpitz’… and though I’ve used a lower case name so it wouldn’t be associated with Admiral Tirpitz, some people really like to make a big deal out of everything… so this ‘tirpitz’ actually never got to fire his main guns…
Since I really believe that this application can help openSUSE (at least I want to bundle it in a Cinnamon spin), it can be a great marketing tool for new users and it’s not really intrusive… I’ve decided to take suggestions for potential names for this fork…
I’ve spoken today with Clement and though we’re moving different ways, we’ve decided to work together whenever possible and look for features together and share our work… He seems to be a pretty accessible guy and it’s a great and fun opportunity to improve and learn a bit more on python.
Any suggestions for a name are welcome and if some are left in comments, I’m sure I will pick one of them…


Michael Meeks: 2012-01-25: Wednesday
Wed, 25 Jan 2012 21:00:00 +0000
 
	
		Chewed mail, quick call with Vojtech, then Charles. Finally
	got around to submitting a LinuxTag paper or two. Lunch. More mail,
	patch pieces.
	
	
		J. out for Rosemary's leaving pizza party. Up extremely late
	poking android's wedging on ANativeWindow_lock - sadly the debugger
	gives no trace: an thread un-attached to the VM ?
	



KDE at openSUSE: KDE SC 4.8 packages for openSUSE
Wed, 25 Jan 2012 19:08:54 +0000
KDE SC 4.8 seems to be a pleasant update, especially regarding KDE PIM. Though the latter still features bugs regarding filtering (filtering for List-Id or List-Post headers does not work for incoming mails on imap accounts) and has a few other issues left, it got a lot more stable and its active development is noticeable. Thanks to the new maintainer and the KDE PIM devs! Dolphin’s UI got a lot quicker and there are a lot more small improvements spread across KDE.
Unfortunately I’m once again fighting virtuoso-t eating CPU although the file indexer is idle and the dbus interface does not show any active queries – but that’s nothing a quick and dirty removal of all of nepomuk’s data can’t “solve”. I know, it’s not a nice solution but it worked for me in the past. I’m still trying to start using nepomuk+strigi with each release – e.g. hoping for some useful (e.g. google-like) search results that display more than a filepath when searching for a string.
Regarding openSUSE packages, you can check the build status in order to make sure all packages you have installed are available for an update. If the repo is rebuilding enable the “Last time results” checkbox at the top-right of that page to see whether the package did succeed before and was published. After that it’s as simple as (for openSUSe 12.1):
sudo zypper ar http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1/ KR48
sudo zypper mr -r KR48
sudo zypper dup --from KR48
Make sure you do not add any Qt repos since the required Qt packages are included. Disable the UpdatedApps repo! You can read more about the KDE repos available for openSUSE on the wiki and drop-by on the openSUSE KDE IRC channel #opensuse-kde or the forums in case you need help.

         


Sebastian Kügler: 4.8.0 is out :)
Wed, 25 Jan 2012 16:25:08 +0000
Simply the most polished, fast, flexible, beautiful and elegant desktop, ever.



Nelson Marques: Linux Mint’s Cinnamon 1.2 deployed for openSUSE
Wed, 25 Jan 2012 10:54:31 +0000
Cinnamon Desktop
Cinnamon is an alternative Linux Desktop which provides a traditional user experience, very close to GNOME 2 and it’s underlying technology is forked from gnome-shell. Cinnamon features the traditional gnome-panel layout with a main menu, notification area, work space indicators, etc. Cinnamon’s configuration is made through a configuration tool known as ‘cinnamon-settings’.

Cinnamon in openSUSE
Thanks to Vincent Untz and the GNOME Team it was possible to grab a GNOME:Cinnamon namespace/project on openSUSE Build Service to provide openSUSE users the latest release of Cinnamon (1.2). Currently this repository only hold the very own basic packages required for cinnamon which include:

cinnamon – cinnamon desktop
cinnamon-settings – cinnamon’s configuration utility
cinnamon-extensions – extension bundle for cinnamon
cinnamon-extension-weather – a weather applet for cinnamon
muffin – cinnamon’s window manager


Features

3 Desktop configuration available:


Traditional Layout – 1 panel at the bottom;
Flipped Layout – one panel at the top;
Classic Layout – one panel at the top and another at the bottom.

Easier configuration through a GUI configuration tool;
Support for Desktop effects: there’s currently 2 desktop effects available, very customizable;
Several applets available:

Accessibility;
Recent Documents;
Removable Drives;
Trash
XRandR Monitor Control

Improved Main Menu
Kinky look…

Availability (supported platforms)
Information: Cinnamon won't be available for openSUSE 11.4 unless someone wants to maintain it. We encourage openSUSE users to upgrade to openSUSE 12.1 for a better Desktop experience.

openSUSE 12.1
openSUSE Tumbleweed
openSUSE Factory


Repositories and Installation
Cinnamon is available through a 1-Click Installer for the supported platforms (rebuilding at the time of article publishing):

Install Cinnamon on openSUSE 12.1 GNOME
Install Cinnamon on openSUSE Tumbleweed GNOME


Screenshots
Cinnamon 1.2 in openSUSE 12.1
Cinnamon's configuration utility

TODO for openSUSE 12.2

Add the relevant cosmetic packages with the upstream themes;
Polish the default configuration;
A lot of testing;
Fix build errors;


Special Thanks

Cinnamon’s Developing teams;
Jigish Gohil – for packaging Cinnamon 1.3, creating and introducing the Cinnamon wiki page;
Vincent Untz – for supporting the implementation of Cinnamon and providing a development project under the GNOME namespace;


References

http://cinnamon.linuxmint.com
https://build.opensuse.org/project/show?project=GNOME:Cinnamon
http://en.opensuse.org/openSUSE:GNOME_Cinnamon



Michael Meeks: 2012-01-24: Tuesday
Tue, 24 Jan 2012 21:00:00 +0000
 
	
		Up early, misc. mail chew, question processing, patch review,
	re-building action etc. Inched through more startup problems, Lunch.
	
	
		Chat with Kendy, more mail cleanout. Lydia over for dinner.
	Up late hacking android main-loop pieces with Tor.
	



Nelson Marques: Cinnamon 1.2 on openSUSE 12.1
Tue, 24 Jan 2012 12:57:49 +0000
Cinnamon 1.2 on openSUSE 12.1
Anyone who wants to test… hit the link! (finishing rebuilding on OBS)…

cinnamon
cinnamon-extensions
cinnamon-extension-weather
cinnamon-settings
muffin





Ladislav Slezak: Switching from Gettext to FastGettext in a Rails3 app
Tue, 24 Jan 2012 10:13:31 +0000
From Gettext to FastGettext
In SLMS we use Gettext for i18n support.Unfortunately it doesn't work with new Rails 3. But we found out that there is FastGettext Ruby gem which does work with Rails 3 and we decided to switch to this different implementation.

In this blogpost I'll describe the needed steps when switching from Gettext to FastGettext. And here also are solutions for some problems we found during the transition.
Using the new Ruby gems
You will need these new Ruby gems:  fast_gettext: https://github.com/grosser/fast_gettext
  gettext_i18n_rails: https://github.com/grosser/gettext_i18n_rails (FastGettext Rails integration)
  rails-i18n: https://github.com/svenfuchs/rails-i18n (Default Rails translations)

The first step is to remove the old Gettext gems and replace them by FastGettext gems.
So replace these gems in your Gemfile:

gem 'locale'
gem 'locale_rails'
gem 'gettext'
gem 'gettext_activerecord'
gem 'gettext_rails'
by:
gem 'fast_gettext'

# 0.4.3 contains fixes in
#'rake gettext:store_model_attributes' task
gem 'gettext_i18n_rails', '>= 0.4.3'

# rails-i18n provides translations for ActiveRecord
# validation error messages
gem 'rails-i18n'

# needed to collect translatable strings
# not needed at production
group :development do
  # needed for HAML support (optional)
  gem 'ruby_parser'

  # no need to load the gem via require
  # we only need the rake tasks
  gem 'gettext', '>= 1.9.3', :require => false
end

Then you need to initialize FastGettext, create config/initializers/fast_gettext.rb file:
# define your text domain
FastGettext.add_text_domain 'foo', :path => File.join(File.dirname(__FILE__), '..', '..', 'locale')


# set the default textdomain
FastGettext.default_text_domain = 'foo'

# set available locales
# (note: the first one is used as a fallback if you try to set an unavailable locale)
FastGettext.default_available_locales = ["en_US","ar","cs","de","es",...]
Replace foo with your textdomain.Now you need to add FastGettext initialization in your application controller:
class ApplicationController < ActionController::Base
  # replace these old Gettext calls:
  #   init_gettext "your_domain"
  #   GetText.textdomain("your_domain")
  # by this:
  include FastGettext::Translation

  before_filter :set_users_locale 

  def set_users_locale
    I18n.locale = FastGettext.set_locale(params[:locale] || cookies[:locale] ||
      request.env['HTTP_ACCEPT_LANGUAGE'] || 'en_US')
    cookies[:locale] = I18n.locale if cookies[:locale] != I18n.locale.to_s
  end
end 
The set_users_locale before filter handles setting the correct locale for every request.The locale is set via a cookie and can be changed using ?locale=locale URL option. It is possible to use different solution for switching the locale, e.g. as path prefix aor domain name - see the Rails guide

Note: The application needs to be restarted after any change in the translations.
Solved Problems
Automatic detection of available locales
Using fixed list in the available locales list might not be nice, especially if you want to dynamically add new translations later. In this case you need to find theavailable locales dynamically at start. The solution si to put this code to config/initializers/fast_gettext.rb file:# put 'en_US' as first, the first item is used as a fallback
# when requested locale (via ?locale= URL parameter) is not found
FastGettext.default_available_locales = ["en_US"]

# get available locales automatically
Dir[File.join(File.dirname(__FILE__), '..', '..', 'locale', "/*/LC_MESSAGES/*.mo")].each do |l|
  if l.match(/\/([^\/]+)\/LC_MESSAGES\/.*\.mo$/) && !FastGettext.default_available_locales.include?($1)
    FastGettext.default_available_locales << $1
  end
end
Language and Country Separator in locale name
Rails native localization support uses I18n module for translation support. The problem is that it uses dash (-) separator between langugage and country code in locale names.

This makes a problem when using with standard gettext locale schema which uses underscore (_) as the separator. For example translations from rails-i18n gem will not be found when the current locale in en_US, it expects en-US locale.

The problem can be solved by defining locale fallbacks like this (put this to config/initializers/fast_gettext.rb file):
# enable fallback handling
I18n::Backend::Simple.include(I18n::Backend::Fallbacks)

# set some locale fallbacks needed for ActiveRecord translations
# located in rails_i18n gem (e.g. there is en-US.yml translation)
I18n.fallbacks[:"en_US"] = [:"en-US", :en]
I18n.fallbacks[:"en_GB"] = [:"en-GB", :en]
I18n.fallbacks[:"pt_BR"] = [:"pt-BR", :pt]
I18n.fallbacks[:"zh_CN"] = [:"zh-CN"]
I18n.fallbacks[:"zh_TW"] = [:"zh-TW"]
I18n.fallbacks[:"sv"] = [:"sv-SE"]
This means that if for example a translation for en_US locale is not found then en-US will be tried and then en locale.
Including source file name and line number is the final POT file
By default when you run 'rake gettext:find' task to collect the translatable string the output will not contain the source file name and the line number. It's very useful if you get a feedback from translator (like a typo in the original message) then you don't have to scan all file but you immediately know where to fix the problem.

If you want to change this behavior and include the line numbers add this configuration to config/initializers/fast_gettext.rb file:
# configure default msgmerge parameters (the default contains "--no-location" option
# which removes code lines from the final POT file)
Rails.application.config.gettext_i18n_rails.msgmerge = ["--sort-output", "--no-wrap"]
Sorting messsages in the final POT file
The 'rake gettext:find' task sorts the messages in the final POT file alphabetically. The advantage is that if you add a new string and regenerate the file thenthe files will be similar and the diff will be small.

The problem is that the sorting is done at the merge step, when merging the new found translation wit the old ones. At the very first run (when the final POT file does not exist yet) the merge step is skipped and thus the messages are not sorted. This can be fixed by starting the task once more (the second run will find existing messages and do the merge with sorting).

But the problem is that you can easily forget to run the task for the second run. The workaround is to create an empty target POT file when the it doesn't exist yet. Unfortunately simple touch command is not sufficient (msgmerge failed for me with some strange UTF-8 error), we have to create valid POT but without any messages.

The workaround it to put this code to lib/tasks/gettext.rake file:# 'gettext:find' sorts the messages alphabetically only when it is merging existing messages
# copying empty pot file from the template forces sorting even at the first run
namespace :gettext do
  task :create_pot_template do
    FileUtils.cp("locale/template.pot", "locale/textdomain.pot") unless File.exists?("locale/textdomain.pot")
  end
end

# add task dependency
task :'gettext:find' => :'gettext:create_pot_template'
The locale/textdomain.pot template should look like this:
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <email@address>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: version 0.0.1\n"
"POT-Creation-Date: 2012-01-16 17:56+0100\n"
"PO-Revision-Date: 2012-01-16 17:56+0100\n"
"Last-Translator: FULL NAME <email@address>\n"
"Language-Team: LANGUAGE <ll@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
Automatic translation in HAML files
It is possible to extend HAML parser to automatically translate all plain text strings. The advantage is than you don't have to explicitly use _() function and you cannot forget to mark a text to translation.

This can be done using this code snippet. Save it to a file, remove the require calls at the beginning (they are obsoleted and do not work with new gettext) and require it in your ApplicationController.

Then you need to add support to 'rake gettext:find' task. Save this code snippet to lib/haml_parser.rb file. You need to replace require 'gettext/parser/ruby' by require 'gettext/tools/parser/ruby' so it works with newer gettext gem.

Then put this to lib/tasks/gettext.rake file:# extend the HAML parser to extract plain text messages
# to support automatic translations (without need to mark the text with _())
namespace :gettext do
  task :haml_parser do
    require 'haml_parser'
  end
end

# extend the HAML parser before collecting the translatable texts
task :'gettext:find' => :'gettext:haml_parser'



Michael Meeks: 2012-01-23: Monday
Mon, 23 Jan 2012 21:00:00 +0000
 
	
		Mail chew, read the git commits over the weekend.
	Call with Simon, improved the LibreOffice donation page
	to include a nice image rotation.
	
	
		Misc. android hackery - got past several unpleasant
	roadblocks in the UNO bootstrapping. Reviewed slideware.
	Dinner, babes to bed. J. under the weather, but out to a
	meeting. Back to the hackery - started on the first-start,
	user-installation creation code.
	



Federico Mena-Quintero: Mon 2012/Jan/23
Mon, 23 Jan 2012 16:40:00 +0000

	  
	    
	      Nuevo blog de Carpintería
	    

	    
	      He comenzado a escribir un blog de carpintería, trabajo en madera
	      y fabricación de herramientas: La
		Viruta Rebelde.
	    

	    
	      Este blog es parte de nuestra inmensa red de Talleres Libres de Artes y
		Tecnologías (artículo anterior sobre esto).
	    

	    
	      El blog corre sobre un sitio hecho con Plone, entonces todavía no
	      es la cosa más amigable del mundo, pero con el tiempo irá
	      mejorando.  Sean bienvenidos :)
	    

	    
	      New woodworking blog
	    

	    
	      I have started writing a new blog about woodworking and
	      toolmaking: The
		Rebel Shaving (in Spanish).
	    

	    
	      This blog is part of our immense network of Free Workshops for Arts and
		Technologies (previous article on this).
	    

	    
	      The blog runs on a Plone site, so it's not the friendliest thing
	      in the world, but it will get better over time.  Be welcome :)
	    
	  
	


Jörg Stephan: The release event revisited
Mon, 23 Jan 2012 12:58:06 +0000
Key-Systems, a domain registrar from the Saarland with more than 3.2 million domains , as the main sponsor of the event, could welcome openSUSE enthusiastic from the Saarland and the adjacent France  at the premises of the company.
It was a lively exchange about the new technologies related to openSUSE but also from other parts of the open source world.
We were able to experience live one a Nokia N9. The Nokia N9 is a smartphone which Meegoo as well as a full shell (BusyBox) and an SSH server contains.

On the other hand, there was a glimpse of the possibilities the Nepomuk Systemd and KDE 4.7 to have an SSD powered notebook.
There were also lively exchanges about Btrfs and snapper, which were presented by the administrators of the SkyWay Data Center. In this context, it was SUSE insiders, a brief overview of the features of the new Service Pack 2 for SUSE ENTERPRISE SERVER will bring with it. The subject of linux container and the opportunities it brings with it, such as the exact allocation of resources or individual CPU cores Rambänken and the switch between these resouces have been in operation to feel very welcome.

With this technology it is now possible to the failure of individual processors, but not prevent, but to shift the impact of such a hardware replacement and restart at least until the night maintenance window.


Michael Meeks: 2012-01-22: Sunday
Sun, 22 Jan 2012 21:00:00 +0000
 
	
		J. dropped me to NCC to practise with the band, service,
	Thea spoke. Back for lunch with Keziah over. Out to a service of
	Christian Unity in the town. Back. Played games, lazed on the sofa.
	Tea, told stories to babes, put them to bed & read more stories.
	Sermon from Hugh Palmer, silly Naked Gun movie, bed.
	



Bruno Friedmann: Winter outside? Summer inside! Keep Geeko’s head warm!
Sun, 22 Jan 2012 11:53:14 +0000
Why
If you live in the North hemisphere as I do, it’s winter time actually: cold temperature, freezing wind, snow … and 20 years older than your twenties, then you want to keep your head warm.

So the mission was : “what can I design (in other words : what crazy new idea can I have?) funky to wear, well fitting with the car design, and the rest of a geek’s wardrobe?

A beanie sounds perfect!


What
Something simple, quickly available, uni-geek-sex, nice etc. So 10 days ago, I’ve done my shopping with my favorite partner, and agree on a model, then checked cost and delivery time.

Here’s the picture, of how it should look.

I hope you will love it, and fight to get one for you?
Where When can I grab one?
There will be a small series (99) available on openSUSE’s booth during Fosdem (4-5 Feb) in Brussels. I will sold them 10€/piece, and half the money will goes to Fosdem organization. The rest cover the pre-serie cost.
My advice, don’t be in late!  
How to build your own?
If you can’t attempt Fosdem, or can’t have one, you can easily start your own local production. I’ve choose the Myrtle Beach (MB 7584) white/lime,a Beanie with contrasting border, 100% polyacryl. They should be available in any clothes advertising shop. Then the logo is printed on it, better to have it embroidered but this is more expensive.
Have fun!


Manu Gupta: The Lohri Experience
Sun, 22 Jan 2012 04:37:06 +0000
So often have we said or heard that it is from the simplest of things that we derive pleasure from the simplest of things in life. Listening to the birds chirping or the fragrance of the first rain or having a beer with your friends or taking a walk in a windy wintry weather and I can a zillion of more ors to the list. These things at times are so obvious to us that we tend to undermine the importance of these very simple things in our life.
One such experience was the Lohri experience for me. Being a student and staying away from home, I never had time to enjoy a festival. However, back in Delhi NCR the heart of India, I had my chance to celebrate Lohri. A few things that I noticed

Families coming together and meeting each other
Kids playing in the lawn
Meeting the knowns and unknowns and wishing each other
My WARMEST winter experience  
The beautiful bonfire
The Ladies  

These are a few things that are right at the top of my head but then it was an awesome experience to remind me of the old age phrase “In Simplicity Lies Beauty”

         


Michael Meeks: 2012-01-21: Saturday
Sat, 21 Jan 2012 21:00:00 +0000
 
	
		Up earlyish, H. and N. off to Bury to do music & book
	buying. Cleaned the house up, hacked a bit at some androidish
	pieces: discovered some problems with unit tests not being
	compiled.
	
	
		Lunch, Mary Rogers over in afternoon, sat by the fire and
	played with babes. Lydia over in the evening - more hacking at sal/
	stopped readLine corrupting/writing to it's input buffer and
	crashing and fixed misc. build issues.
	



Nelson Marques: A bit more of free time… Adding a few more packages to the MATE Desktop
Sat, 21 Jan 2012 20:02:22 +0000
It’s been a cold weekend (January is often the coldest month in the year in Portugal) and it feels nice to be next to the fireplace enjoying a Leffe beer or a glass of “Cabeça de Burro” Douro wine, while building a few more packages for MATE.
I’ve got brainwashed the other day to try out Mint and decided to nuke of my Red Hat installations to check it out (I do like to try things on real hardware and not on VM’s, though they run quite nice with Intel VT Technology). I also wanted to take a real look into MATE and see how this works on it’s native platform. I’ve installed VirtualBox and on it a openSUSE 12.1 minimal install (from the NET install iso) and I’m using this virtual machine to continue the builds of MATE for openSUSE.
Currently 26 packages are building for 12.1 and I hope to add a few more during this weekend. As my $dayjob tasks are pretty much getting under control, I expect to take a week off in February (first or second week) to finish MATE and give it a ride on openSUSE 12.1. If all goes OK, then it’s time to clean up the mess and start submitting it to openSUSE:Factory and file a request to get a project for MATE (maybe X11:MATE, GNOME:MATE or even just MATE).



Andres Silva: Two More Wallpapers
Sat, 21 Jan 2012 19:31:00 +0000
I worked on these two wallpapers along with another friend who does photography and Camy. If you want to check out my friend's pictures, feel free to drop in here.



Enjoy my friends :D


openSUSE News: openSUSE 11.3 EOL’ed, 12.2 On The Way!
Sat, 21 Jan 2012 16:51:30 +0000

 
As Benjaman Brunner announced yesterday, openSUSE 11.3 has reached end of life.  As a quick refresher, openSUSE releases new versions every 8 months, and each version has a life cycle of 18 months.  As 11.3 was released in July of 2010, the time has come to embrace our newer versions, including the successful release of 12.1 in November of 2011.
As Brunner’s announcement indicates, we worked hard to maintain 11.3 while developing its subsequent two releases (11.4 and 12.1.) And of course, we’re already gearing up for 12.2, slated for release in July.  And the first milestone release is already just around the corner.  You’ll be able to try out Milestone 1 on February 9th.
The roadmap for openSUSE 12.2 is as follows:
9 February – Milestone 1
3 March – Milestone 2
5 April – Milestone 3
26 April – Milestone 4
24 May – Beta 1
14 June – Release Candidate 1
28 June – Release Candidate 2
6 July – Gold Master
11 July – 12.2 Final Release
As always, testers and contributors are welcome throughout the release development process.  Join the Factory Mailing List and have a lot of fun!
Graphic courtesy of Michael Fox – openSUSE Artwork Team member.


Michael Meeks: 2012-01-20: Friday
Fri, 20 Jan 2012 21:00:00 +0000
 
	
		Chewed mail and misc. vcl fixing - and finally calc unit test
	runs to completion on Android (great work from Tor); getting the process
	slowly better documented in README.Android and no pixels yet of
	course. Chat with Simon, then Charles.
	

	
		The LibreOffice
	FOSDEM Devroom Schedule went live - a really great set of shortish
	talks (to get the most grist we can into eight hours) and some great speakers,
	I'm really looking forward to it.
	
	
		Planned my day, interspersing the tedious stuff with fun hackery, so
	that at least -some- tedious things get done. Lunch.
	
	
		Filed a few more easy-hacks
	around cleaning up the horrible old tools/ - a duplicate system
	abstraction that still malingers underneath LibreOffice. Hid a few more unused
	locking methods in SvStream, and made the FSysRedirector more obviously a no-op.
	There are big blocks of easy-to remove cruft in tools needing a beginner or two.
	



Danny Kukawka: PandaBoard: get persistent MAC address by default
Fri, 20 Jan 2012 16:23:04 +0000
The PandaBoard/PandaBoard ES, as the BeagleBoard too, don't have a EEPROM on the (USB-) network card to store the MAC address. That's why you get a new MAC and subsequently a new IP address with each boot. You can set the MAC manually via e.g. 'ifconfig eth0 hw ether 01:23:45:67:78:01' or also automatically via the network scripts.

The other solution would be to generate a MAC on OMAP (version > 2) machines by reusing another unique hardware identifier. There is already an old patch written by Mark Crichton for the BeagleBoard. And there was also an patch on the kernel mailing list from Andy Green and some related discussion, but none of them got into the kernel.  The problem was that if there are more than one card in the system without EEPROM they all would get the same MAC address. That sounds reasonable to me while I'm not sure that something like this will happen with a high chance out in the field. And since there are objections against exporting the OMAP die ID to the sysfs there is no simple way to handle the MAC generation in userspace (e.g. via udev).

While investigating how u-boot handle the no-EEPROM problem, I've found out that the u-boot code already contain functions to generate a persistent MAC for such devices. The MAC gets also exported to the u-boot environment as usbethaddr. That's why I wrote a patch for the smsc95xx kernel driver (based on a patch from Sebastien Jan) to take a module parameter to set the MAC address via the kernel command line. With this patch the driver takes the following parameter: macaddr=01:23:45:67:89:ab;[tgt-netdevname] and assign the given MAC address to the first device in the system without a MAC on the EEPROM. If there is more than one device without EEPROM you can add the netdevice name to the parameter - separated by a ';' - to assign it to a special device (e.g. for eth0: macaddr=01:23:45:67:89:ab;eth0). If there is no MAC given, the device still gets a random MAC as before.

After patching and installing your kernel, you need to change the u-boot config to pass the $usbethaddr from the environment along to the kernel cmdline. I used a uEnv.txt file (on my boot partition) instead of the legacy/obsolete boot.scr, since you simply can change the file without call mkimage after each change. That's the content of the uEnv.txt file I currently use to set the MAC of my PandaBoard ES:

bootargs=root=/dev/mmcblk0p2 rw rootwait rootfstype=ext3 console=ttyO2,115200n8 vram=16M omapfb.vram=0:16M
bootcmd=mmc rescan ; setenv bootargs ${bootargs} smsc95xx.macaddr="${usbethaddr}" ; fatload mmc 0 0x82000000 uImage; bootm 0x82000000
uenvcmd=boot
You can find the patch here, I plan to include it into the openSUSE OMAP2+ kernel and to send it upstream as soon as I have some reports back that it also works for others. You can find an kernel RPM for openSUSE Factory here.



Michael Meeks: 2012-01-19: Thursday
Thu, 19 Jan 2012 21:00:00 +0000
 
	
		Poked mail, fixed misc. build problems, poked at and
	spent the morning extending the tools/ stream abstraction also
	fixing some build issues. Nice to finally get some hacking done.
	
	
		Chat with Jonathan, lunch, SUSE team meeting, LibreOffice
	ESC call, Vojtech's staff, discovered I'm late at my travel budget
	planning; bother.
	
	
		Pondered the LibreOffice team. There is one set of very
	skilled hackers that perhaps people don't notice. As of today, we
	have quite a chunk of people working full-time on LibreOffice that
	used to be on Sun's OpenOffice.org team (in order of migration):
	seven guys: Caolan McNamara (RedHat), Noel Power (SUSE), Thorsten
	Behrens (SUSE), Bjoern Michaelsen (Canonical), Stephan Bergmann
	(RedHat), Eike Rathke (Redhat), Michael Stahl (RedHat) - making
	(I think) the largest concentration of full-time ex. StarDivision
	hackers on any project with a nice cluster in Hamburg still. It'd
	be great to grow that list of course.
	
	
		More hackery and build fixing; late call with Camilo.
	Read babes stories, J. out for a run, final emulator hackery
	and bed.