If you want modules loaded for devices that have been plugged in before you boot, use the coldplug package: udev update is blocked by coldplug on older systems and udev will block coldplug on newer systems. the two cannot co exist. the documentation should explain this and how to safly remove coldplug and update udev instead of users relying on long posts that are confusing in forums. [quote]Code Listing 2.3: Installing the coldplug package # emerge coldplug Don't forget to add coldplug to the boot runlevel: Code Listing 2.4: Adding coldplug to the boot runlevel # rc-update add coldplug boot [/quote]
*** Bug 156336 has been marked as a duplicate of this bug. ***
None of the udev versions you're talking about are stable yet, so the doc will not yet be fixed. Once those versions are marked stable for all arches, then we can update the guide. As it is, until coldplug/hotplug are kicked out of the tree (as is planned in the future, because of improved udev functionality), we can't break compatibility with the stable tree. The doc must stay as-is for the time being.
(In reply to comment #2) > None of the udev versions you're talking about are stable yet, sys-fs/udev-103 is stable on x86.
Bah. that version was stabled only yesterday, and only on x86. I'll take care of it, but with <notes> on which version this is possible for.
I added a note about udev version 103 and higher no longer requiring coldplug, and how to go about removing it on upgrading. I also took the liberty of adjusting not just the udev guide, but also the usb and bluetooth guides. Added the same <note> to all three. Fixed in CVS.
