path_id: add platform and serio support

[elogind.git] / FAQ

diff --git a/FAQ b/FAQ
index 1b9e56d8c5ad14a7bfd5f03b90a70533c547dbd3..1fe374cf91a460c59df5ad13f2b09b3715212f1d 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.
 
 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
 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
    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
    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


@@ -89,7 +84,7 @@ A: udev can be placed in initramfs and run for every device that is found.
 Q: Can I use udev to automount a USB device when I connect it?
 A: Technically, yes, but udev is not intended for this. All major distributions
    use HAL (http://freedesktop.org/wiki/Software_2fhal) for this, which also
 Q: Can I use udev to automount a USB device when I connect it?
 A: Technically, yes, but udev is not intended for this. All major distributions
    use HAL (http://freedesktop.org/wiki/Software_2fhal) for this, which also

-   watches devices with removable media and integrates into the desktop software.
+   watches devices with removable media and integrates the Desktop environment.

 
    Alternatively, it is easy to add the following to fstab:
      /dev/disk/by-label/PENDRIVE /media/PENDRIVE  vfat user,noauto 0 0
 
    Alternatively, it is easy to add the following to fstab:
      /dev/disk/by-label/PENDRIVE /media/PENDRIVE  vfat user,noauto 0 0


@@ -111,13 +106,12 @@ A: When using dynamic device numbers, a given pair of major/minor numbers may
    (The same problem exists when using PAM to change permissions on login.)
 
    The simplest solution is to prevent the creation of hard links by putting
    (The same problem exists when using PAM to change permissions on login.)
 
    The simplest solution is to prevent the creation of hard links by putting

-   /dev in a separate filesystem like tmpfs.
+   /dev on a separate filesystem like tmpfs.

 
 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
 
 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
-   Information on joining can be found at
-      <https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel>
-   Archives of the mailing list can be found at:
-      <http://marc.theaimsgroup.com/?l=linux-hotplug-devel>
+   address for it is:
+      linux-hotplug-devel@lists.sourceforge.net
+   Information on joining can be found at:
+      https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel