From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian =?iso-8859-15?q?Borntr=E4ger?= Date: Fri, 11 Feb 2005 16:19:22 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <200502111719.23163.christian@borntraeger.net> List-Id: References: <20050211004033.GA26624@suse.de> <20050211031823.GE29375@nostromo.devel.redhat.com> <1108104417.32129.7.camel@localhost.localdomain> In-Reply-To: <1108104417.32129.7.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: Bill Nottingham , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org On Friday 11 February 2005 07:46, Greg KH wrote: > And finally, even if you do use udevstart to manager /sbin/hotplug > events, you still need a module autoloader program. This package > provides executables for that problem, if you don't want to (or you > can't) use the existing linux-hotplug scripts. udev will never do the > module loading logic, so there's no duplication in this case. Greg, the pci module autoloader is a real agent, which means it depends on having a hotplug event. Are you planning to support a scan for already present devices, like the pci.rc file in current hotplug solutions? cheers Christian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&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