X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=README;h=38459c6b226141408e3b7d2d33c32324dd42c822;hp=fe56095686f7c1e906cdf7e9b81abd88be152bf5;hb=6997e3b2dc0095985071e2f7496342a850cdb5ad;hpb=dfc9761d8846a5f6f437fb599bc6817d14efbec2 diff --git a/README b/README index fe5609568..38459c6b2 100644 --- a/README +++ b/README @@ -1,112 +1,101 @@ -udev - userspace device management +udev - Linux userspace device management -For more information see the files in the docs/ directory. +Integrating udev in the system has complex dependencies and may differ from +distribution to distribution. A system may not be able to boot up or work +reliably without a properly installed udev version. The upstream udev project +does not recommend replacing a distro's udev installation with the upstream +version. -Important Note: - Integrating udev in the system is a whole lot of work, has complex dependencies - and differs a lot from distro to distro. All reasonable distros depend on udev - these days and the system will not work without it. +The upstream udev project's set of default rules may require a most recent +kernel release to work properly. - The upstream udev project does not support or recomend to replace a distro's udev - installation with the upstream version. The installation of a unmodified upstream - version may render your system unusable! There is no "default" setup or a set - of "default" rules provided by the upstream udev version. +Tools and rules shipped by udev are not public API and may change at any time. +Never call any private tool in /usr/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 /usr/lib/udev and the entire contents +of the /run/udev directory are private to udev and do change whenever needed. Requirements: - - 2.6.x version of the Linux kernel. See the RELEASE-NOTES file in the - udev tree and the Documentation/Changes in the kernel source tree for - the actual dependency. - - - The kernel must have sysfs and unix domain socket enabled. - (unix domain sockets (CONFIG_UNIX) as a loadable kernel module may work, - but it is completely silly, don't complain if anything goes wrong.) - - - The proc filesystem must be mounted on /proc. - - - The sysfs filesystem must be mounted at /sys. No other location - will be supported by udev. - + - Version 2.6.34 of the Linux kernel with sysfs, procfs, signalfd, inotify, + unix domain sockets, networking and hotplug enabled + + - Some architectures might need a later kernel, that supports accept4(), + or need to backport the accept4() syscall wiring in the kernel. + + - These options are required: + CONFIG_DEVTMPFS=y + CONFIG_HOTPLUG=y + CONFIG_INOTIFY_USER=y + CONFIG_NET=y + CONFIG_PROC_FS=y + CONFIG_SIGNALFD=y + CONFIG_SYSFS=y + CONFIG_SYSFS_DEPRECATED*=n + CONFIG_UEVENT_HELPER_PATH="" + + - These options might be needed: + CONFIG_BLK_DEV_BSG=y (SCSI devices) + CONFIG_TMPFS_POSIX_ACL=y (user ACLs for device nodes) + + - The /dev directory needs the 'devtmpfs' filesystem mounted. + Udev only manages the permissions and ownership of the + kernel-provided device nodes, and possibly creates additional symlinks. + + - Udev requires /run to be writable, which is usually done by mounting a + 'tmpfs' filesystem. + + - This version of udev does not work properly with the CONFIG_SYSFS_DEPRECATED* + option enabled. + + - The deprecated hotplug helper /sbin/hotplug should be disabled in the + kernel configuration, it is not needed today, and may render the system + unusable because the kernel may create too many processes in parallel + so that the system runs out-of-memory. + + - The proc filesystem must be mounted on /proc, and the sysfs filesystem must + be mounted at /sys. No other locations are supported by a standard + udev installation. + + - The default rule sset requires the following group names resolvable at udev startup: + disk, cdrom, floppy, tape, audio, video, lp, tty, dialout, and kmem. + Especially in LDAP setups, it is required that getgrnam() be able to resolve + these group names with only the rootfs mounted and while no network is + available. + + - Some udev extras have external dependencies like: + libglib2, usbutils, pciutils, and gperf. + All these extras can be disabled with configure options. + +Setup: + - The udev daemon should be started to handle device events sent by the kernel. + During bootup, the events for already existing devices can be replayed, so + that they are configured by udev. The systemd service files contain the + needed commands to start the udev daemon and the coldplug sequence. + + - Restarting the daemon never applies any rules to existing devices. + + - New/changed rule files are picked up automatically; there is usually no + daemon restart or signal needed. Operation: - Udev creates and removes device nodes in /dev, based on events the kernel - sends out on device discovery or removal. - - - Directly after mouting the real root filesystem, wherever that - happens, in initramfs or with a directly mounted root, /dev should get - a tmpfs filesystem mounted, which is populated from scratch by udev. - Created nodes or changed permissions don't survive a reboot. - - - The content of /lib/udev/devices directory should be copied over to the - tmpfs mounted /dev, to provide the required nodes to initialize udev. - - - The udevd daemon must be started to receive netlink events from the kernel - driver core. - - - From kernel version 2.6.15 on, the hotplug helper /sbin/hotplug should - be disabled with an init script before the boot scripts are run and - kernel modules are loaded. - - - 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 requests a device node, udev will create one with - the default name or the one specified by a matching udev rules. - - -Compile Options: - prefix - Set this to the default root that you want to use. Only override - this if you really know what you are doing, even then, you probably - don't do the right thing. - DESTDIR - Prefix for 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. - STRIPCMD - If udev is compiled for packaging an empty string can be passed - to disable the stripping of the binaries. - 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 klibc. - Default value is 'false'. KLCC specifies the klibc compiler - wrapper, usually located at /usr/bin/klcc. - EXTRAS - If set, will build the "extra" helper programs as specified - as listed (see below for an example). - -If you want to build the udev helper programs: - make EXTRAS="extras/cdrom_id extras/scsi_id extras/volume_id" - - -Installation: - - The install target intalls the udev binaries in the default locations, - All at boot time reqired binaries will be installed in /sbin. - - - The default location for scripts and binaries that are called from - rules is /lib/udev. Other packages who install udev rules, should use - that diretory 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. - - - Copies of the rules files for all major distros are in the etc/udev - directory (you may look there how others distros are doing it). - - - The persistent disk links in /dev/disk are the de facto standard - on Linux and should be installed with every default udev installation. - The devfs naming scheme rules are not recommended and not supported. - -Please direct any comment/question/concern to the linux-hotplug-devel mailing list at: - linux-hotplug-devel@lists.sourceforge.net - + - Based on events the kernel sends out on device creation/removal, udev + creates/removes device nodes and symlinks in the /dev directory. + + - All kernel events are matched against a set of specified rules, which + possibly hook into the event processing and load required kernel + modules to set up devices. For all devices, the kernel exports a major/minor + number; if needed, udev creates a device node with the default kernel + device 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. + + - The events udev handles, and the information udev merges into its device + database, can be accessed with libudev: + http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/ + http://www.kernel.org/pub/linux/utils/kernel/hotplug/gudev/ + +For more details about udev and udev rules, see the udev man pages: + http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/ + +Please direct any comment/question to the linux-hotplug mailing list at: + linux-hotplug@vger.kernel.org