because is better than cause

[elogind.git] / FAQ

diff --git a/FAQ b/FAQ
index 1b9e56d8c5ad14a7bfd5f03b90a70533c547dbd3..4285d98ff77e53c7f53ec5a12203db9d7df6b760 100644 (file)
--- 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
@@ -56,7 +51,7 @@ A: Yes, udev can create /dev nodes using the devfs naming policy.  A
    to the devfs names.  See the  udev.rules.devfs file in the udev
    release.
    Note that the devfs scheme is not recommended or officially supported
-   cause it is a really stupid idea to simply enumerate devices in a world
+   because it is a really stupid idea to simply enumerate devices in a world
    where devices can come and go at any time. These numbers give you nothing
    but problems, and are not useful to identify a device. Have a look at the
    persistent disk rules for an example how to do it correctly in userspace