[12:23] <mbiebl> similar to the system and session bus concept from d-bus?
[12:23] <wasabi_> Yeah.
[12:23] <wasabi_> Basically, just using upstart as a process for managing parallel starts based on event emission.
[12:23] <wasabi_> Which is all it is.
[12:24] <wasabi_> One code base which is efficient at managing child processes and stuff, instead of many.
[12:24] <mbiebl> Well, imo there are more important issues than that atm though.
[12:24] <wasabi_> dbus could use it to do activation.
[12:25] <wasabi_> the system bus could do activation on the system upstart, the session bus could do activation on the session upstart.
[12:25] <mbiebl> complex-event-config being one ;-)
[12:25] <wasabi_> yeah.
[12:25] <mbiebl> pid file support is another.
[12:26] <mbiebl> There are still daemons out there which can't be run in the fg.
[08:33] <cyberix> Does upstart automagically react to changes in inittab?
[08:34] <AlexExtreme> no
[08:38] <cyberix> How can I tell it to react?
[08:38] <wasabi_> upstart doesn't use inittab, does it? heh
[08:38] <wasabi_> So that would be a "you can't."
[08:39] <cyberix> It has a similar configuration file?
[08:39] <wasabi_> /etc/event.d
[08:39] <wasabi_> It's quite different, so no.
[08:41] <cyberix> ok
[08:41] <cyberix> Thanks
[08:42] <mbiebl> wasabi_: The sysv compat layer in Debian/Ubuntu reads /etc/inittab (if existent) to determine the default runlevel.
[08:43] <mbiebl> Otherwise /etc/inittab is not used.
[08:43] <wasabi_> Ahh, but that's not upstart itself as much as one of the job files
[08:43] <mbiebl> Right, It's the rc-default job file.