From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: linux-hotplug@vger.kernel.org
Subject: udev and hotplug
Date: Sun, 19 Mar 2006 20:12:14 +0000 [thread overview]
Message-ID: <dvkdta$4ai$1@sea.gmane.org> (raw)
as far as I know the current recommendation is to
disable /proc/sys/kernel/hotplug and let udevd
handle everything via user space events. right?
and is the hotplug package still needed, required, used?
or does udev and hotplug even conflict?
here are some sources that might need an update:
udev README:
- From kernel version 2.6.15 on, the hotplug helper /sbin/hotplug should
be disabled with an init script before actions like loading kernel
modules are taken, which may cause a lot of events.
http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
Requirements
It requires a 2.6 Linux kernel with CONFIG_HOTPLUG enabled to run. It is
recommended that you also have the Linux Hotplug scripts installed, but it
is not necessary for it to work properly.
http://www.gentoo.org/doc/en/udev-guide.xml
udev
Every time the kernel notices an update in the device structure, it calls
the /sbin/hotplug program. Hotplug runs the applications linked in the
/etc/hotplug.d/default directory where you will also find a symlink to the
udev application. Hotplug directs the information given by the kernel to
the udev application which performs the necessary actions on the /dev
structure (creating or deleting device files).
http://fedora.redhat.com/docs/udev/
udev gets called by hotplug, if a module is loaded, and a device is added
or removed. udev looks in /sys/, if the driver provides a "dev" file,
which contains the major and minor number for a device node to communicate
with the driver. After looking in the udev rules (in
the /etc/udev/rules.d/ directory), which specify the device node filename
and symlinks, a device node is created in /dev/ with the permissions,
which are specified in /etc/udev/permissions.d/.
I use none of those distributions, but maybe these people are on the list?
Regards, Andreas
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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:[~2006-03-19 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 20:12 Andreas Jellinghaus [this message]
2006-03-20 0:49 ` udev and hotplug Kay Sievers
2006-10-11 9:21 ` Raj Kumar Yadav
2006-10-11 9:28 ` Kay Sievers
2006-10-11 11:06 ` Gioele Barabucci
2006-10-12 12:48 ` 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='dvkdta$4ai$1@sea.gmane.org' \
--to=aj@dungeon.inka.de \
--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).