From: Gioele Barabucci <ml@gioelebarabucci.com>
To: linux-hotplug@vger.kernel.org
Subject: I'm lost: the udev workflow
Date: Fri, 24 Jun 2005 02:03:35 +0000 [thread overview]
Message-ID: <200506240403.35408.ml@gioelebarabucci.com> (raw)
Now I'm lost. I'm no longer sure about the way udev, the kernel and other
device management apps work together.
I was thinking that the workflow was:
* something happens to a device (add, remove, power state change)
* the kernel calls /sbin/hotplug
* udev is called and does its work (modprobe, rmmod, device node
creation/deletion)
* all the "interested listeners" (like HAL) are called and are told of what
has changed.
Now I read of netlink, listening daemons, KEYs... Can someone draft a quick
sketch of how kernel hotplug is going to work with the next udev releases?
--
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 reply other threads:[~2005-06-24 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 2:03 Gioele Barabucci [this message]
2005-06-24 10:23 ` I'm lost: the udev workflow Kay Sievers
2005-06-24 11:36 ` Gioele Barabucci
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=200506240403.35408.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.