In noticed that the reason for this is an OS switch() in
hobbitd/hobbitd_client.c line 1763 ff.
Back to the client:
Adding a new OS in general isn't difficult with hobbit on the client
side, you just copy some shell script, perhaps edit it and it
works. With GNU/kFreeBSD it
looks a little bit different:
14/0/0 root (at) c-metisse:pts/ttyp3 22:49:51 [~] # uname -o
GNU/kFreeBSD
15/0/0 root (at) c-metisse:pts/ttyp3 22:49:54 [~] #
There is a slash in the OS name. So all my workarounds are quite ugly
since they all involve the creation of directories to allow filenames
like
hobbitclient-gnu/kfreebsd.sh
Not nice, but works.
The solution suggested by the GNU/kFreeBSD developers for this problem
is to replace all slashes in the output of "uname -o" with
underscores (written in Perlish: s(/)(_)g) so that the above example
would look like this:
hobbitclient-gnu_kfreebsd.sh
Hernik: How do you think that problem is solved best from your view as
hobbit developer? You probably have more an idea which code may need
to be patch. I've lost the overview at the moment, since hobbit seems
to use the output of "uname -o" in a lot of places. Do you think, you
can generate a patch I can test? If not: with a few pointers to most
of the places in the source, I probably also can try to create a patch
on my own... Alternatively I should be able to get you an account on a
Test machine running Debian GNU/kFreeBSD. (I'm currently testing
inside a virtual machine using QEMU/KVM.)
P.S.: No, it's not for the job this time, it's for my own boxes and
those of friends. :-)
Kind regards, Axel Beckert