Re: [PATCH] use uevents in udevd

[Kay Sievers <kay.sievers@vrfy.org>]

On Fri, 2005-01-14 at 11:22 +0100, Hannes Reinecke wrote:
> Hi all,
> 
> this patch adds the capabilities to read uevents directly from the 
> kernel socket (CONFIG_KOBJECT_UEVENT=y).

Heh, I just split up the message handling in udevd last week to possibly
plug in a second source of events. Nice work!

Shouldn't we ignore events with a SEQNUM from udevsend, if we get the
first one from the uevent?

> The old behaviour is left in place, as with this we can still send 
> events manually.

./drivers/input/input.c
./drivers/pnp/pnpbios/core.c
./drivers/s390/crypto/z90main.c

are still "broken" from that view. They bypass the driver core and don't
send any uevent.

> And I've added a command-line option '-d' to start udevd as a daemon.

It is already running, right? We should read /sys/kernel/hotplug_seqnum
and initialize the next expected event number too, if the self-daemonize
is needed.

> Now we can do
> /sbin/udevd -p

-p? :)

> echo -n "" > /proc/sys/kernel/hotplug

This will break the complete input layer until now! :(

> no need for udevsend anymore.
> Plus we can finally do a load-limit for hotplug events.

Thanks,
Kay



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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