X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=README;h=1eecf9d847e75e79c424269c0a9452ecff9e82c5;hp=92a23724c1a5c7f3bf42013bbcb0a551d065a675;hb=600b2584566a44b8a57f546f5ce27f5b1cce21d6;hpb=a2ddee73920673aae645ab7fde322251a249024f diff --git a/README b/README index 92a23724c..1eecf9d84 100644 --- a/README +++ b/README @@ -10,10 +10,10 @@ The upstream udev project's set of default rules may require a most recent kernel release to work properly. This is currently version 2.6.31. Tools and rules shipped by udev are not public API and may change at any time. -Never call any private tool in /lib/udev from any external application, it might +Never call any private tool in /lib/udev from any external application; it might just go away in the next release. Access to udev information is only offered -by udevadm and libudev. Tools and rules in /lib/udev, and the entire content of -the /dev/.udev directory is private to udev and does change whenever needed. +by udevadm and libudev. Tools and rules in /lib/udev and the entire contents of +the /dev/.udev directory are private to udev and do change whenever needed. Requirements: - Version 2.6.27 of the Linux kernel with sysfs, procfs, signalfd, inotify, @@ -70,7 +70,7 @@ Setup: - Restarting the daemon does never apply any rules to existing devices. - - New/changed rule files are picked up automatically, there is no daemon + - New/changed rule files are picked up automatically; there is no daemon restart or signal needed. Operation: @@ -80,7 +80,7 @@ Operation: - All kernel events are matched against a set of specified rules, which possibly hook into the event processing and load required kernel modules to setup devices. For all devices the kernel exports a major/minor - number, if needed, udev will create a device node with the default kernel + number; if needed, udev will create a device node with the default kernel name. If specified, udev applies permissions/ownership to the device node, creates additional symlinks pointing to the node, and executes programs to handle the device.