From: iSteve <isteve@rulez.cz>
To: linux-hotplug@vger.kernel.org
Subject: hotplug2 v0.8 -- added linux2.4 hotplug support
Date: Tue, 26 Sep 2006 10:03:19 +0000 [thread overview]
Message-ID: <20060926120319.3d85ef0e@silver> (raw)
Greetings,
I'd like to announce a major upgrade in Hotplug2, version 0.8.
The significance of this release lies in added support for Linux 2.4 kernel
(and older 2.6 kernel) hotplug system.
The system of support of Linux 2.4 hotplug is following:
User uses generate_alias to create modalias for every module available, out of
modules.[bus]map (eg. modules.pcimap, modules.isapnpmap etc.) into
/lib/modules/`uname -r`/modules.alias.
/proc/sys/kernel/hotplug calls hotplug2-dnode, which crafts possibly missing
MODALIAS out of given information (and also sets SEQNUM), transforms the event
into uevent format and writes it to netlink socket. Therefore, hotplug2-dnode
basically converts old style hotplug events into uevents.
hotplug2 receives the uevent (and it doesn't care if it is an event from the
hotplug2-dnode or from kernel, because it can't really tell) and processes it as
usually.
In dumb mode, hotplug2 (during startup) checks whether the /sbin/modprobe
binary is of module-init-tools, and if it is not, it uses
/sbin/hotplug2-modwrap instead (which simply matches given alias to
/lib/modules/`uname -r`/modules.alias and executes /sbin/modprobe for each
match, since modutils use strcmp for alias matching, while module-init-tools
and hotplug2-modwrap use the desired fnmatch).
To perform coldplugging, hotplug2-coldplug-2.4 looks at information exported
through /proc/bus and, again, computes MODALIAS and invokes the event by writing
to the netlink socket. Currently, pci, usb and isapnp are supported.
Most of this is documented (including frequently asked questions) in here:
http://isteve.depressant.org/hotplug2/Linux24_interface.html
Homepage of the project:
http://isteve.depressant.org/hotplug2/
Thanks in advance for any comments whatsoever.
PS: I've looked at Busybox mdev; hotplug2 is way, way ahead (and taking a
different path, too).
--
-- iSteve
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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
reply other threads:[~2006-09-26 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060926120319.3d85ef0e@silver \
--to=isteve@rulez.cz \
--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).