+Q: But wait, I really want udev to automatically load drivers when they
+ are not present but the device node is opened. It's the only reason I
+ like using devfs. Please make udev do this.
+A: No. udev is for managing /dev, not loading kernel drivers.
+
+Q: Oh come on, pretty please. It can't be that hard to do.
+A: Such a functionality isn't needed on a properly configured system. All
+ devices present on the system should generate hotplug events, loading
+ the appropriate driver, and udev will notice and create the
+ appropriate device node. If you don't want to keep all drivers for your
+ hardware in memory, then use something else to manage your modules
+ (scripts, modules.conf, etc.) This is not a task for udev.
+
+Q: But I love that feature of devfs, please?
+A: The devfs approach caused a lot of spurious modprobe attempts as
+ programs probed to see if devices were present or not. Every probe
+ attempt created a process to run modprobe, almost all of which were
+ spurious.
+
+Q: I really like the devfs naming scheme, will udev do that?