em1 instead of eth0?

Since a little while, few machines using "biosdevname" started appearing.
One of the consequences of having em1 instead eth0 for part of the autoyast autoinstallation process is to end up with a machine without network at the end of stage 2.

If you are one of the lucky owners, make sure to append "biosdevname=0" so to get rid of once and for all of the em device.

Autoyast, sles11sp3 and logical partitions

Is your old profile (yes, the one that used to work on sp2) not setting up your partitions as you would like?
Well, the reason is, autoyast went trough several changes, including not relying anylonger on the <parttion_nr> tag in order to decide if a partition will be a primary one or not.
If before a partion_nr set to 1,2 and 5 was giving you two primary and one logical as result, now you'll end up with 3 primary ones.

The discussion is still ongoing on about the new VS old behaviour, stay tuned for more news and hopefully the final decision on the topic.

Welcome to Germany, Spotify

So, finally spotify made it to Germany.

If you tried to fetch the linux client, you  probably have noticed that nothing but the .deb is currently available.
You might also have tried to use alien, and get few requires not  met although the libraries are all where they should be.

Here's a quick x86_64 version:

spotify-client-qt-0.6.6.10.gbd39032.58-2.x86_64.rpm

(a 1:1 alien conversion plus a couple of Requires: adjusted to fit the bill) originated from spotify-client-qt_0.6.6.10.gbd39032.58-1_amd64.deb.

Tested on OpenSuSE 11.4 and SLES11sp1
I don't need a 32 bit package, but if you do, let me know: that can be arranged.
Works on my box, but feel free to give it a try if you feel lazy.

Code is not mine, all the usual terms and conditions of Spotify still apply: I just repackaged it.
If anyone has a problem with this, I'd gladly take if offline.

Octave segfaulting at start?

Just in case someone still tries to run octave on a SLE 10, let me warn you that 
https://savannah.gnu.org/bugs/?30685 
is going to bite you.
A segfault awaits you behind the corner.

I've prepared a package that implements the (in)famous hack consisting of removing the gnulib:: namespace.
If you want to spare yourself some time, either fetch it from OBS or add this repo and feel free toping me in any update is needed/wanted.

by-uuid, where are you?

Are you missing entries in /dev/disk/by-uuid ?

 Run "uuidgen" this will spawn a uuid like:
2edddab5-d555-414f-9db6-4c80c11897f5

After that, run tune2fs to assign the generated uuid to the filesystem on the device:

elbereth:~ # tune2fs /dev/yourdevice -U
2edddab5-d555-414f-9db6-4c80c11897f5

You're ready to go, don't forget to retrigger you udev rules with

udevadm trigger

Enjoy your new persistent name !

Openais - zombies and the revenge of the undead

Are you trying to start your cluster and all you get out of it is a set of duplicate and defunct processes, similar to the following?

4129 ?        Ssl    0:01 /usr/sbin/corosync
4134 ?        S      0:00  \_ /usr/lib64/heartbeat/stonithd
4135 ?        S      0:00  \_ /usr/lib64/heartbeat/cib
4136 ?        Z      0:00  \_ [lrmd] <defunct>
4137 ?        S      0:00  \_ /usr/lib64/heartbeat/attrd
4138 ?        Z      0:00  \_ [pengine] <defunct>
4139 ?        Z      0:00  \_ [crmd] <defunct>
4141 ?        S      0:00  \_ /usr/lib64/heartbeat/stonithd
4142 ?        S      0:00  \_ /usr/lib64/heartbeat/cib
4143 ?        S      0:00  \_ /usr/lib64/heartbeat/lrmd
4144 ?        S      0:00  \_ /usr/lib64/heartbeat/attrd
4145 ?        S      0:00  \_ /usr/lib64/heartbeat/pengine
4652 ?        S      0:00  \_ /usr/lib64/heartbeat/crmd


Check /etc/corosync/service.d/
If in there you see a pcmk file *and* Pacemaker is specified as service in your /etc/corosync/corosync.conf  you have your answer.
Just leave your .config file as is and get rid of the pcmk file instead.
Reboot your node, and you' re ready to go.

Autoyast - yast2-samba-client: bits and pieces

Your autoinstallation fails to join your AD domain unless you run a net join as post installation script?
You can specify  the join credentials within the samba-client section of your profile like this  ( this goes after samba's </global> )

<join>         
     <password>whatever</password>
     <user>Administrator</user> 
</join>  

Also, are you setting your <realm> and the result in your smb.conf is an empty "realm=" entry?
Try setting it twice, in both <samba-client> and <samba-server> sections, that should do the trick.