+ - The udevd daemon must be started on bootup to receive netlink uevents
+ from the kernel driver core.
+
+ - All kernel events are matched against a set of specified rules in
+ /etc/udev/rules.d/ which make it possible to hook into the event
+ processing to load required kernel modules and setup devices. For all
+ devices the kernel exports a major/minor number, udev will create a
+ device node with the default kernel name, or the one specified by a
+ matching udev rule.
+
+
+Compile Options:
+ DESTDIR
+ Prefix of install target, used for package building.
+ USE_LOG
+ If set to 'true', udev is able to pass errors or debug information
+ to syslog. This is very useful to see what udev is doing or not doing.
+ It is enabled by default, don't expect any useful answer, if you
+ need to hunt a bug, but you can't enable syslog.
+ DEBUG
+ If set to 'true', very verbose debugging messages will be compiled
+ into the udev binaries. The actual level of debugging is specified
+ in the udev config file.
+ USE_SELINUX
+ If set to 'true', udev will be built with SELinux support
+ enabled. This is disabled by default.
+ EXTRAS
+ list of helper programs in extras/ to build.
+ make EXTRAS="extras/cdrom_id extras/scsi_id extras/volume_id"
+
+
+Installation:
+ - The install target intalls the udev binaries in the default locations,
+ All binaries will be installed in /lib/udev or /sbin.
+
+ - The default location for scripts and binaries that are called from
+ rules is /lib/udev. Other packages who install udev rules, may use
+ that directory too.
+
+ - It is recommended to use the /lib/udev/devices/ directory to place
+ device nodes and symlinks in, which are copied to /dev at every boot.
+ That way, nodes for broken subsystems or devices which can't be
+ detected automatically by the kernel, will always be available.
+
+ - Default udev rules and persistent device naming rules are required by other
+ software that depends on the data udev collects from the devices,
+ and should be installed by default with every udev installation.
+
+Please direct any comment/question/concern to the linux-hotplug-devel mailing list at:
+ linux-hotplug@vger.kernel.org