- biruda
  - output spool files must contain arch, platform and host, now they collide!
  - start: workers names clash, so start must say which one to start.
    This depends on the architecture and the platform, so this is part
    of start. There can be multiple worker on same platforms/architectures
    on different coordinator hosts, this is ok: this is load-balancing
- http_lib:
  - POST
    - handle answer body too
- replace json-c with an embedded and thread-safe libcjson as in Tegano,
  especially the Windows port of json-c is shacky
- ideas for KISS deployment (which we would do additionally to normal
  packaging):
  - build static binaries for certain platforms, e.g. a biruda-static
    package
- grub2 grub-reboot
  - easy way to have multi-boot linux versions (if we don't want to
    chroot or virtualize)
  - how to we configure this?
  - how can we access the configuration zone of grub from other operating
    systems? most likely we have to build something on our own. Last resort
    is that a biruda on for instance FreeBSD just reboots back to Linux
    (one shot grub2 menu entry selection and boot and then falling back)