          MODULE=udev
         VERSION=175
          SOURCE=$MODULE-$VERSION.tar.bz2
         SOURCE2=$MODULE-175-rules.patch.bz2
         SOURCE3=raid-devfs.sh-udev-088
   SOURCE_URL[0]=http://people.freedesktop.org/~kay/$MODULE
   SOURCE_URL[1]=$KERNEL_URL/pub/linux/utils/kernel/hotplug
     SOURCE2_URL=$PATCH_URL
     SOURCE3_URL=$PATCH_URL
      SOURCE_VFY=sha1:2ef42ca4b11e6b9d0d5c7f47da39eb2e64695e44
     SOURCE2_VFY=sha1:167ccb5c31a7cc3afd84957baf6a8adf55d6a4fa
     SOURCE3_VFY=sha1:44a12035774c2b42b784267d38e61a34aa0b645b
        WEB_SITE=http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
         ENTERED=20040104
         UPDATED=20111108
      MAINTAINER=moe@lunar-linux.org
           SHORT="hotplug and device handling daemon"

cat << EOF
udev is supposed to provide a framework for hotpluggable devices
under linux 2.6.x carrying an event listening daemon that also
creates the necesserary nodes for the hotplugged devices inside
the /dev directory.

Its behaviour can be altered by a set of rules defined in udev(7).
udev superseeds devfs and renders it obsolete. Some of the
differences are:

* udev runs completely in userspace. No kernel interaction especially
  in device naming.
* udev creates a dynamic /dev directory with ever changing device nodes
  that fit your needs and rules
* udev provides LSB standard device names
* udev is also the hotplug handler of the future
EOF
