jabberd2 starttls client problems

I’ve recently setup another jabberd2 installation. This time I had option, in c2s.xml , enabled. Unfortunately this created a ton of problems with clients other than gaim…Users using clients like exodus, miranda and psi for example had problems with that and could not login. Is it SO hard for programmers to write secure code ? Is it so hard to implement starttls ?

yahoo’s expired certificate screenshots

such a shame for such a big company…

was it so difficult to replace the cert a bit earlier ?

Yahoo changed today it’s certificate with another one…

libmysqlclient.so.12 => not found

I’ve upgraded my mysql from 4.0.X to 4.1.X…and some progs gave me errors that they could not start because they couldn’t find they proper mysql library…
The solution is to download a mysql package called MySQL-shared-compat. Unfortunately it only comes as an rpm…but..for us gentoo users there’s a nice solution to installing it.

Go download one of those rpms http://rpm.pbone.net/index.php3/stat/4/idpl/2144706/com/MySQL-shared-compat-4.0.25-0.i386.rpm.html and then:

rpm2targz MySQL-shared-compat-4.0.25-0.i386.rpm
tar zxvf MySQL-shared-compat-4.0.25-0.i386.tar.gz
cp ./usr/lib/*.so.* /usr/lib/

and you are done…all progs continue to work just like before.

gentoo “broken” world file

Yesterday, I did an “eix xpad” and I saw that there were newer versions than I had installed…That was weird because I daily do my “emerge -uDav world”. That was not the first time though such a thing had happened. So I opened my “/var/lib/portage/world” file and started checking for some of my packages that should be in there, like gimp, k3b, etc. There were just not there.
What I did was copy the world file to the root dir and then “regenworld”. Magically around 40(!!) new packages appeared inside the world file.
“emerge -uDav world” gave me aroung 20 packages to upgrade. Then I did an “revdep-rebuild” and my system is rocking again 🙂
I still don’t have an explanation of why did this happen…why weren’t these packages inside the world file…possibly broken emerge commands…but why ?

flawless fbsplash

I’ve recently faced some problems with my fbsplash installation during a kernel upgrade. Until kernel linux-2.6.11-gentoo-r9 I had no problems at all…when I tried upgrading to linux-2.6.11-gentoo-r11 I had kernel messages all over my splash screen…

The solution was not quite obvious…I re-read the fbsplash HOWTO and I started checking out everything it says…
I ended up changing my lilo.conf to something that looks like this:

image = /boot/bzImage-2611-r11
root = /dev/hda6
label = G2.6.11-r11
append=”gentoo=nodevfs,video=radeonfb:ywrap,1024×768-32@85 splash=silent,fadein,theme:KillBillTux-Yellow quiet CONSOLE=/dev/tty1″
initrd = /boot/fbsplash-killbill-1024×768
read-only # read-only for checking

along with a nice re-emerging of splashutils.
Then it came to me…why have the bootsplash in the default runlevel and not on boot ? so I could get my bootsplash from the very beggining…like some modern distros like Ubuntu does.

rc-update add splash boot

And I thought that would be enough…wrong! Read again fool! http://gentoo-wiki.com/HOWTO_fbsplash#Adding_Background_To_All_Consoles

As the splash script requires ‘local’ to be run first, adding splash to runlevel BOOT will force local to execute earlier, which may cause some problems, eg. when you are using some web services in local (eg. ntp)

now what ? What if we create another “local” named local2 and put all our previous commands there ?

cp /etc/conf.d/local.start /etc/conf.d/local2.start
cp /etc/conf.d/local.stop /etc/conf.d/local2.stop
cp /etc/init.d/local /etc/init.d/local2

then edit /etc/init.d/local2 and change all occurances of local with local2
then it’s time for:

rc-update add local2 default

and…drums rolling…. it works!

collectd ebuild part2 – the rejection

my collectd ebuild that I had posted to bugs.gentoo.org was tagged as a duplicate of http://bugs.gentoo.org/show_bug.cgi?id=107076 even though it was created after mine…anyway 🙂

I might try to build an ebuild on something else someday 🙂