On Tue, 2010-02-09 at 09:57 -0800, T.Michael Turney wrote: > Under karmic the generated filesystem doesn't do so well, > and I tracked it down to dbus not being included. The udevd > daemon was unhappy and most of the /dev tree didn't get created. > > I believe that upstart has a dependency on dbus and this > issue surfaces with karmic because upstart is now in charge of > the boot process. > Upstart has a dependency on libdbus (as noted in README), but you can link that statically if your distribution doesn't ship libdbus in /lib (most do nowadays).
It doesn't require the D-Bus bus daemon, Upstart's own tools like initctl talk to Upstart via a private socket bypassing the daemon. The bus daemon is only used when you run these tools as a non-root-user. So if your distribution is having boot problems, it's fairly likely to be unrelated to that - and you should file a bug on the tool you used; in this case rootstock. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
