From 8d31ed01c535804ca2f1273044f3bca1cf6e37ed Mon Sep 17 00:00:00 2001 From: Andreas Baumann Date: Thu, 11 Jun 2015 21:11:59 +0200 Subject: updated todo list --- TODOS | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) (limited to 'TODOS') diff --git a/TODOS b/TODOS index fb34f2b..820ee60 100644 --- a/TODOS +++ b/TODOS @@ -1,8 +1,24 @@ +- biruda + - 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 embeddd and thread-safe libcjson as in Tegano +- 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 + - 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) + -- cgit v1.2.3-54-g00ecf