package dependency

Scott James Remnant scott at
Mon Mar 1 15:37:44 GMT 2010

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.

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : 

More information about the upstart-devel mailing list