Index ¦ Archives ¦ RSS > Tag: hacking

BitlBee-Skype 0.8.4

I just released 0.8.4. The happy thing about it is that basically the only fix I added to this release is to make it work when python is python3k (so we need to use python2.7 to get python2 support), but the rest is just merge from:

  • email

  • github

  • Debian

Now the total number of contributors increased to 7. :)


I tried to search back when did I create Java bindings for libwpd - it seems this was the first commit.

First I kept back the source code to get some money for it (there were a customer who seemed to be willing to pay, but then disappeared), then I just abandoned the idea and pushed it to to some CVS repo, (I even mentioned it in a blog post), which is finally now converted to git.

Long story short, a week ago finally Fridrich released the first version of the code, after about 2.75 years. :)


Background: OSL_TRACE() is an internal LibreOffice macro that is like printf(), but it’s only enabled in debug mode. Without it, you would add a debug printf during development:

printf("debug, foo\n");

then you would comment it out when the code started working,:

//printf("debug, foo\n");

then remove the comment when it breaks again, etc.

In the past, if you built a LibreOffice module, then you executed:


inside a module, and in case you wanted debug symbols and such messages you built using:

build debug=t

which increased the debug level to 2 (from 0), where 1 is required for debug symbols, 2 for debug messages. (See the OOo wiki page.)

The recent update, why I’m writing this post: Now this has been changed, and debug=t gives you debug symbols only, but no extra debug output. While this is great in most cases, sometimes you still want the old behaviour to get the debug messages. In that case the solution (as pointed out in the mailing list post) is to use:

build debug=t dbglevel=2

(Hopefully this post will be handy for who missed that post, like I did the first time.) vmiklos01 CWS integrated

Once I was ready with this year’s GSoC work I started to submit it back to Before that was completed, LibreOffice was launched, though I thought if I started working on submitting it to as well, I’ll finish it. About 6 weeks later they now integrated (merged) the vmiklos01 CWS (the branch containing my GSoC work) to DEV300, what will became 3.4 later.

tgt is now available as a package

Today I packaged tgt an iSCSI target (server). The upstream package provides a large number of examples, though I thought it’s a good idea to note what I used for testing:

# egrep -v '#|^$' /etc/tgt/targets.conf
default-driver iscsi
<target iqn.2010-11.local.test:storage>
    backing-store /dev/sdb

Something offtopic: a rejourn patch accepted and a LibreOffice bug fixed today.

Slides of my GSoC 2010 Presentation

As requested, the slides of my presentation, titled "GSoC project: Improving RTF Export - Presentation of a Go-OO student" are available here.

openSUSE Conference 2010

So I have been invited to this year's openSUSE conference in Nurnberg to give a short presentation about my GSoC work (the RTF export rewrite in LibreOffice).

As I expected, the really interesting part was to meet people I never had the ability to meet in person previously - and of course to learn other new stuff. :)

So some of the items I really liked:

  • We actually did some hacking, see here (thanks Cedric for pointing out the issue for me).
  • I learned about trigraphs - thanks Fridrich!
  • I now heard about flat ODF from Muthusuba.
  • Nice jokes by Tor about old UNIX systems where the default installation added a login for Kernighan and Ritchie by default. :)
  • Met great people from the LibreOffice team (Kohei, Noel, Muthu, Cedric, Tor, Fridrich, Petr, Lubos), and outside: Stephan Kulow (coolo, the ex-kde-master) and others.

To sum up: thank you for the invitation, I enjoyed it! :)

LibreOffice: even on ppc

You probably have read that ooo-build has been renamed to LibreOffice (technically it's just a rename).

Test packages for i686 available here if you want to test it on Frugalware.

Aaand this time, as a very special gift, ppc packages are available as well! :)

I just built it, but Bouleetbil was kind enough to provide a screenshot when he tested it.

gammu-1.28 issue

I recently upgraded gammu from 1.27 to 1.28 in -current and I noticed that the backup of my phone is now way slower than before. The fix was trivial (already backported to the Frugalware package as well) for the maintainer so it's now fine again.

Well done, mcihar! :)

Playing with libvirt

I've been playing with libvirt in the last two days. My motivation was that I saw:

  1. plain kvm is not that fast
  2. there is this virtio framework which aims to make it faster
  3. using virtio directly is hard, better not reinventing the wheel and just try libvirt

So if you want to try it yourself, you need to pacman -S libvirt, service libvirtd start. Check /var/log/syslog for error messages, in case it can't find some commands (bridge-utils, dnsmasq, etc.), install them.

If you want to create a new virtual machine, you need pacman -S virtinst. Then you can use something like:

virt-install --name=syncpkgcd-helicon --arch=x86_64 --vcpus=1 --ram=1024 --os-type=linux --os-variant=virtio26 --connect=qemu:///system --network network=default --cdrom=/virt/iso/frugalware-1.3-i686-net.iso --disk path=/virt/syncpkgcd/syncpkgcd.img,size=40 --accelerate --vnc --noautoconsole --keymap=us

See man virt-isntall for more info about the meaning of the switches. One trick: kvm can't handle the gfxmenu in our grub on the install cd, so you need to disable that. One way to do it is to use vim -b frugalware-1.3-i686-net.iso, search for "menu /boot", and change "gfx" to "#fx". Then you can run virt-install. It'll start the install in the background. The easiest way (for me) to connect to the console is to create an ssh tunnel to the server running the kvm machine (for example ssh -L 5900:localhost:5900 server), then run krdc localhost:0 on my own machine.

Next trick is that you need kernel support to boot from virtio disks (/dev/vda), that's enabled in frugalware-current.git but there were no rebuild yet, so you need to build it yourself for now.

Once the installation finished, the machine will be shut down. You can use virsh to start it. Here is a great summary about virsh subcommands. Something not to forget: if you want to automatically start the machine after the host booted, use virsh autostart $name.

(You can also do a service libvirt-guests add, that way all guests will be automatically suspended/resumed on shutdown/boot. Just to be clear: if you want the "resume if it was a proper shutdown, start if there was a power cut" feature: you need both init scripts because libvirtd will always start/resume autostart guests, but it will never suspend them on shutdown.)

If grub hangs after reboot, try creating a small (I used 32MB) separate /boot partition first, that should fix the issue.

virsh shutdown $machine won't work if you don't install acpid and enable it as well, so it's a good idea to do so.

The last trick: if you want to use the virt-manager gui from your local machine to manage a remote host, it isn't trivial to do so. First, it would try to login via ssh as root, and that's disabled by default. (And why would you enable it?). Also, even if you allow that, it would try to use nc -U which is supported by the openbsd nc only, the gnu nc does not have such a switch. Instead, we can use socat to connect to unix sockets. So I created a wrapper script under ~/bin with the following contents:

if [ "$1" == "-U" ]; then
        sudo socat - unix-client:$2
        /usr/bin/netcat $@

Don't forget to add PATH=what_you_want line to ~/.ssh/environment, and include the full path of ~/bin there. This way you can keep using gnu nc and you can also login as a user to manage your machines, as long as you set up nopasswd sudo for your user for socat.

Finally a mini-benchmark:

The SBU of yugo (i686 buildserver, a bit old HW) is 645 seconds, SBU of an i686 guest on helicon (c2q machine with 8g ram) is 264, SBU of the host build on helicon is 76.

I would call this usable (not right now, but once we sort out the kernel part). Finally something that is free software and is comparable to VMware ESX. :)

Update: I recently did the same install with 1.4pre1 (which installs -current, so the kernel is 2.6.36), the list of tricks you still need:

  • separate /boot (haven't tried without)
  • edit iso image to get rid of gfxboot (tried, still fails without)
  • some problem with grub, you need to manually add "(hd0) /dev/vda" to /boot/grub/, then run grub-install /dev/vda

So no more custom kernel, boot from virtio works by default! :)

© Miklos Vajna. Built using Pelican. Theme by Giulio Fidente on github.