From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Date: Fri, 25 Feb 2005 21:56:47 +0000 Subject: Re: event sequencing Message-Id: <9e473391050225135656b9945c@mail.gmail.com> List-Id: References: <9e473391050225081838f673c7@mail.gmail.com> In-Reply-To: <9e473391050225081838f673c7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, 25 Feb 2005 17:53:27 +0100, Kay Sievers wrote: > >In my probe function I do a class_simple_device_add() to create the > >class entry. Later in the probe function I do > >kobject_hotplug(&info->class_device->kobj, KOBJ_MOUNT); to indicate a > >monitor change. > > Don't use that function. It is only for the driver core. It will execute > a usermode_helper which is not the way to do new stuff. Use the netlink > events for that: If your application is some low-level stuff, listen > directly to uevents: > http://www.kernel.org/pub/linux/utils/kernel/hotplug/uevent_listen.c What do I use instead of this to generate the netlink event? kobject_hotplug(&info->class_device->kobj, KOBJ_MOUNT); The user mode helper for monitor change needs to run as root. Do I use the same /etc/hotplug.d directories for netlink? Is there a write up on how to use netlink in conjuntion with dbus somewhere? -- Jon Smirl jonsmirl@gmail.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&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