[11:40] <keesj> what is wrong when initctl list returns strange strings like service_5fapm
[11:40] <keesj> and is it normal that initctl start with no argument segfaults
[14:38] <keesj> what is the replacement for logd?
[16:54] <keesj> what happens why is intrepid not uing 0.5?
[16:54] <keesj> is 0.5 used somewhere?
[16:55]  * keesj is getting a bad feeling
[16:58] <ion_> 0.5 wasn’t released early enough to get to intrepid.
[17:33] <sadmac2> keesj: Fedora has had some stability issues with 0.5
[18:58] <keesj> but I could look at fedora as ref platform
[19:01] <notting> no, fedora 10 does not use upstart 0.5
[19:01] <keesj> the main problem I have now is that initctl doesn't return the same output as it did on 0.3.8 
[19:02] <sadmac2> keesj: we had issues with it when we /tried/ it I should say
[19:06] <keesj> I really pushed to get the change to update...
[19:07] <sadmac2> keesj: notting has a mystery box that 0.5 segfaults on. We still aren't sure what best to do about it.
[19:08] <keesj> but the segfault I have when for example running start without arguments 
[19:09] <keesj> or basic stuff like that. did you experiance such things or did I really screw up the setup
[19:09] <sadmac2> I never noticed, but its possible
[19:11] <keesj> and what does the output of initctl list or initctl status return?
[19:11] <sadmac2> yeah, that stuff is different
[19:11] <sadmac2> and weird
[19:11] <sadmac2> for a variety of reasons
[19:15] <keesj> but dbus doesn't make is easyer to understand for me
[19:23] <sadmac2> brb kernel