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?
A: Yes, udev can create /dev nodes using the devfs naming policy. A
configuration file needs to be created to map the kernel default names
- to the devfs names. See the initial udev.conf.devfs file in the udev
+ to the devfs names. See the initial udev.rules.devfs file in the udev
release. It is the start of such a configuration file. If there are
any things missing, please let the udev authors know.
A: udev will be placed in initramfs and run for every device that is found.
Work to get this implemented is still underway.
+Q: Can I use udev to automount a USB device when I connect it?
+A: Technically, yes, but udev is not intended for this. Projects that do
+ automount hotplugged storage devices are:
+ * Usb-mount http://users.actrix.co.nz/michael/usbmount.html
+ * devlabel http://linux.dell.com/projects.shtml#devlabel
+
+ Alternatively, it is easy to add the following to fstab:
+ /udev/pendrive /pendrive vfat user,noauto 0 0
+
+ This means that users can access the device with:
+ $ mount /pendrive
+ And don't have to be root but will get full permissions on /pendrive.
+ This works even without udev if /udev/pendrive is replaced by /dev/sda1
+
Q: I have other questions about udev, where do I ask them?
A: The linux-hotplug-devel mailing list is the proper place for it. The
address for it is linux-hotplug-devel@lists.sourceforge.net