From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug-Perl?
Date: Mon, 17 Oct 2005 23:20:48 +0000 [thread overview]
Message-ID: <20051017232048.GB2347@vrfy.org> (raw)
In-Reply-To: <43542395.7090808@ukonline.co.uk>
On Mon, Oct 17, 2005 at 10:20:05PM +0000, raid517 wrote:
> Hi, are you guys aware of hotplug-perl?
> http://opensource.idealcorp.com/hotplug-perl/ This seems like a very
> promising improvement on the original hotplug and promises a significant
> speed enhancement. Would anyone consider including it as part of Udev?
> Is this even possible?
This is no longer needed. The whole "hotplug" package is almost dead, as nobody
needs to parse *.map files these days to load a module. The kernel exports
the MODALIAS string in sysfs and the event environment, which can be
natively handled by modprobe. No need for _any_ magic script.
The remaining part of the "hotplug" package is mostly converted to udev
rules. We are currently working on getting rid of the coldplug *.rc scripts
as well.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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-10-17 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 22:20 Hotplug-Perl? raid517
2005-10-17 23:20 ` Kay Sievers [this message]
2005-10-27 10:03 ` Hotplug-Perl? Olivier Blin
2005-10-27 10:10 ` Hotplug-Perl? Marco d'Itri
2005-10-27 10:30 ` Hotplug-Perl? Olivier Blin
2005-10-27 10:33 ` Hotplug-Perl? Marco d'Itri
2005-10-27 10:44 ` Hotplug-Perl? Olivier Blin
2005-10-28 1:16 ` Hotplug-Perl? 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=20051017232048.GB2347@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).