+ - all kernel events are matched against a set of specified rules which
+ make it posible to hook into the event processing
+
+ - there is a copy of the rules files for all major distros in the etc/udev
+ directory (you may look there how others distros are doing it)
+
+Setting which are used for building udev:
+ prefix
+ set this to the default root that you want to use
+ Only override this if you really know what you are doing
+ DESTDIR
+ prefix for install target for package building
+ USE_LOG
+ if set to 'true', udev will emit messages to the syslog when
+ it creates or removes device nodes. This is helpful to see
+ what udev is doing. This is enabled by default. Note, if you
+ are building udev against klibc it is recommended that you
+ disable this option (due to klibc's syslog implementation.)
+ DEBUG
+ if set to 'true', verbose debugging messages will be compiled into
+ the udev binaries. Default value is 'false'.
+ USE_SELINUX
+ if set to 'true', udev will be built with SELinux support
+ enabled. This is disabled by default.
+ USE_KLIBC
+ if set to 'true', udev is built and linked against the
+ included version of klibc. Default value is 'false'.
+ KERNEL_DIR
+ If this is not set it will default to /lib/modules/`uname -r`/build
+ This is used if USE_KLIBC=true to find the kernel include
+ directory that klibc needs to build against. This must be set
+ if you are not building udev while running a 2.6 kernel.
+ EXTRAS
+ if set, will build the "extra" helper programs as specified
+ as listed (see below for an example.)
+
+if you want to build udev using klibc with debugging messages:
+ make USE_KLIBC=true DEBUG=true
+
+if you want to build the udev helper program cdrom_id and scsi_id:
+ make EXTRAS="extras/cdrom_id extras/scsi_id"
+
+Please direct any comment/question/concern to the linux-hotplug-devel mailing list at:
+ linux-hotplug-devel@lists.sourceforge.net