From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: linux hotplug/hotplug-ng
Date: Thu, 11 Aug 2005 13:48:13 +0000 [thread overview]
Message-ID: <42FB571D.8080908@ums.usu.ru> (raw)
In-Reply-To: <1123747167.31868.11.camel@localhost>
Kasper Sandberg wrote:
>then i read up, and it seems that i still need them, however, hotplug-ng
>should now be able to do this stuff for a few of the things hotplug bash
>scripts did, namely the pci "agent" as it was called in /etc/hotplug,
>which will autoload modules for pci stuff, which i guess also includes
>stuff like amd64-agp, which stopped being autoloaded after stopping to
>use coldplug...
>
>
>
Yes, hotplug-ng was a replacement for *.agent, not *.rc scripts, and
thus it cannot handle coldplug.
>updates:
>i already wrote an ebuild and installed hotplug-ng, however hotplugging
>isnt happening, when inserting stuff it doesent load modules.. is there
>a way to make hotplug-ng do what hotplug/coldplug does? also, if you
>should want my hotplug-ng ebuild its availiable here:
>http://kaspersandberg.com/~redeeman/hotplug-ng-002.ebuild
>
>
hotplug-ng is dead. Forget that it exists. It was superseded by the
"modalias" support in the recent kernels (>=2.6.12). Now there are
several coldplug approaches proposed to replace the original hotplug
scripts.
One is based on a tiny program that sits in initramfs and accumulates
early hotplug events for passing them to udev. This completely elminates
the need for separate coldplug scripts.
The second one is the proposal to modify the existing "udevstart"
program so that it reconstructs the events nearly in the same way as the
original *.rc scripts did.
Also it is necessary to mention the hotplug-light package from
http://www.bofh.it/~md/debian/ (to be used with either of the approaches).
--
Alexander E. Patrakov
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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-08-11 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 7:59 linux hotplug/hotplug-ng Kasper Sandberg
2005-08-11 13:48 ` Alexander E. Patrakov [this message]
2005-08-11 18:20 ` Greg KH
2005-08-12 0:09 ` Kasper Sandberg
2005-08-14 14:12 ` Kasper Sandberg
2005-08-14 19:33 ` Kay Sievers
2005-08-15 4:01 ` Kasper Sandberg
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=42FB571D.8080908@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).