summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKay Sievers <kay@pim.off.vrfy.org>2005-10-27 13:13:25 +0200
committerKay Sievers <kay@pim.off.vrfy.org>2005-10-27 13:13:25 +0200
commite4b1a0f608c2d00e458b5cb47a6fba4da9aafe7e (patch)
treec67a1a4fbd3c685aeb7e3882209c3d6484968d47
parent81d719a1d48f31f169487d043982aeabd3b2dd51 (diff)
FAQ: remove confusing statement about module loading
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
-rw-r--r--FAQ5
1 files changed, 0 insertions, 5 deletions
diff --git a/FAQ b/FAQ
index 1b9e56d8c5..abe88638b2 100644
--- a/FAQ
+++ b/FAQ
@@ -31,11 +31,6 @@ Q: But udev will not automatically load a driver if a /dev node is opened
A: Right, but Linux is supposed to load a module when a device is discovered
not to load a module when it's accessed.
-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