From: Gioele Barabucci <ml@gioelebarabucci.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: I'm lost: the udev workflow
Date: Fri, 24 Jun 2005 11:36:05 +0000 [thread overview]
Message-ID: <200506241336.05826.ml@gioelebarabucci.com> (raw)
In-Reply-To: <200506240403.35408.ml@gioelebarabucci.com>
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_idt77&alloc_id\x16492&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
next prev parent reply other threads:[~2005-06-24 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 2:03 I'm lost: the udev workflow Gioele Barabucci
2005-06-24 10:23 ` Kay Sievers
2005-06-24 11:36 ` Gioele Barabucci [this message]
2005-06-24 11:50 ` Kay Sievers
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=200506241336.05826.ml@gioelebarabucci.com \
--to=ml@gioelebarabucci.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).