From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: D-BUS patch for udev-008
Date: Wed, 10 Dec 2003 01:02:11 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107102296001996@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107083813306826@msgid-missing>
On Mon, Dec 08, 2003 at 09:11:10PM +0100, David Zeuthen wrote:
> I'm using Fedora 1 with D-BUS from CVS installed in /usr/local. I do get
> a few message from the linker because of static linking, see below, but
> it does link. What's the reason for linking statically?
udev will need to be able to go into initramfs for early boot. We will
not have access to glibc at that time (well, we could, but it would be a
lot of overkill...)
> Btw, Fedora 1 ships with D-BUS 0.13 which is way different from D-BUS in
> CVS, so you might need to set PKG_CONFIG_PATH to point to the correct
> dbus-1.pc and install udev_sysbus_policy.conf into the proper location.
Ok, thanks. I'll go try that later.
>
> Oh, and even though you have done this, you might still link with the
> old D-BUS because I made a mistake in the Makefile. You need to change
>
> LIB_OBJS += $(shell pkg-config --libs-only-l dbus-1)
>
> to something like
>
> LDFLAGS += $(shell pkg-config --libs dbus-1)
>
> yes? (I was tweaking the Makefile quite a lot myself; sorry about that)
Thanks, I've applied this to the repo.
> I've also found a problem with my patch: There's an issue where when two
> instances of udev is running at the same time (processing /block/sda and
> /block/sda/sda1 when plugging in usb-storage).
>
> One of the copies become a secondary owner of the org.kernel.udev
> service and this means that the emitted D-BUS signal doesn't appear to
> come from the owner of that service as I thought it would. I'm not sure
> if this is the intended behavior of D-BUS, it might be..
>
> The only reason it works in python is that, uhm, the python bindings are
> a bit broken. It only works in C if you ignore filtering on service
> owner.
Hm, eventually udev will turn into a daemon, and only have 1 version
running at a time. The events will be queued up into the udev daemon so
you will not have this problem.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2003-12-10 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 23:01 D-BUS patch for udev-008 David Zeuthen
2003-12-08 0:34 ` Rob Love
2003-12-08 19:40 ` Greg KH
2003-12-08 20:11 ` David Zeuthen
2003-12-10 1:02 ` Greg KH [this message]
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=marc-linux-hotplug-107102296001996@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).