Re: udevsynthesize as a udevstart+coldplug replacement

[Olivier Blin <oblin@mandriva.com>]

Kay Sievers <kay.sievers@vrfy.org> writes:

> As pinted out earlier, it's a very different approch with complete
> different problems to do it async.

Yes, it's the one you've described in reply to my posts, but you
haven't said you would implement it :-)

>> I'd still like a --disable-bus= option so that distro vendors can
>> forbid bus coldplug they don't like.
>> I'm not sure most distro are ready to have udevstart automatically
>> load modules on the pci bus. For example network and sound drivers are
>> often handled separately.
>> Should I take care of this patch?
>
> _Not_ handling these events is just a special case of handling it, so a
> rule can prevent the event from doing anything. I prefer a single source of
> policy as long as this is possible.

One may want to handle USB hotplugging, but not USB coldplugging.
I don't think there is a solution to differentiate hotplug from
coldplug in udev rules (but maybe I'm missing something).

> As said earlier, udevstart is the most critical part of udev. We should
> not play around with that. And Olaf was right, the name is misleading
> and should change anyway. :)

Fair enough.

-- 
Olivier Blin
Mandriva
Mandrakesoft becomes Mandriva



-------------------------------------------------------
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