[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-hotplug
Subject:    Re: I'm lost: the udev workflow
From:       Gioele Barabucci <ml () gioelebarabucci ! com>
Date:       2005-06-24 11:36:05
Message-ID: 200506241336.05826.ml () gioelebarabucci ! com
[Download RAW message or body]

On Friday 24 June 2005 12:23, Kay Sievers wrote:
> udevd already keeps track of the event management as it does today. The
> only difference is that it receives the kernel-events directly from a
> netlink-socket instead of letting the kernel fork a notification process
> that feeds udevd.
So, if I got it correctly, in the future the "Good Way Of Doing Things" is 
going to be:

* /sbin/hotplug is empty
* udevd listens to hotplug events via netlink
* when one event is catch, udevd does its work loading modules and managing 
device files
* udevd notifies other applications (HALd & Co.) that something happened to 
the device foo whose device file is "/dev/foobar"

Seems nice :)

--
Gioele <dev@gioelebarabucci.com>


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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 in list] [next in list] [prev in thread] [next in thread]