From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] dbus missing /var/lib/dbus directory
Date: Thu, 17 May 2012 10:21:06 +0200 [thread overview]
Message-ID: <20120517102106.221ad0e7@skate> (raw)
In-Reply-To: <1337225037.1496.51.camel@kepler.gfxmuse.org>
Le Wed, 16 May 2012 21:23:57 -0600,
"Michael J. Hammel" <buildroot@graphics-muse.org> a ?crit :
> I enabled NetworkManager, which got me dbus, but then disabled
> NetworkManager, but dbus remained (that part is okay).
That's the normal kconfig behavior. The NetworkManager package
"selects" the D-Bus package, so when you enable the NetworkManager
package, it automatically enables D-Bus. But when you disable
NetworkManager, it doesn't automatically disable D-Bus.
> I noticed today that the init script for dbus tries to run dbus-uuidgen but fails with a
> message about not being able to open /etc/machine-id. I dug around and
> then strace'd dbus-uuidgen and found that if /var/lib/dbus is present
> this message goes away.
>
> Should the init script also try to create /var/lib/dbus with "mkdir -p"?
> Of is that something the specific rootfs needs to address on its own?
Well, it should rather be done at build time, when the D-Bus package is
built. And, reading the code, it actually is created:
define DBUS_INSTALL_TARGET_FIXUP
rm -rf $(TARGET_DIR)/var/lib/dbus
ln -sf /tmp/dbus $(TARGET_DIR)/var/lib/dbus
$(INSTALL) -m 0755 -D package/dbus/S30dbus $(TARGET_DIR)/etc/init.d/S30dbus
endef
DBUS_POST_INSTALL_TARGET_HOOKS += DBUS_INSTALL_TARGET_FIXUP
It doesn't exist in your filesystem?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-17 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 3:23 [Buildroot] dbus missing /var/lib/dbus directory Michael J. Hammel
2012-05-17 8:21 ` Thomas Petazzoni [this message]
2012-05-18 4:33 ` Michael J. Hammel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120517102106.221ad0e7@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox