summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgreg@kroah.com <greg@kroah.com>2003-12-17 00:04:23 -0800
committerGreg KH <gregkh@suse.de>2005-04-26 21:13:08 -0700
commit470e365d5338fbdcc8019d790c97ed1229de0196 (patch)
tree95cf0e0690fce5e91441cf7a0f5ec4f7c7ee98df
parent666269480900dd8d099b9e188c16acc9f7f31ee5 (diff)
[PATCH] update the FAQ with info about bad modprobe events from the devfs scheme...
-rw-r--r--FAQ6
1 files changed, 6 insertions, 0 deletions
diff --git a/FAQ b/FAQ
index d9aebde0da..1f7ceb0dd3 100644
--- a/FAQ
+++ b/FAQ
@@ -44,6 +44,12 @@ A: Such a functionality isn't needed on a properly configured system. All
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