NEWS revision f7b877ec498486a446c3f9239fe1aad62b79baf8
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNew and fixed keymaps.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncInstall systemd service files if applicable.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAll distribution specific rules are removed from the udev source tree,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmost of them are no longer needed. The Gentoo rules which allow to support
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncolder kernel versions, which are not covered by the default rules anymore
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe option --debug-trace and the environemnt variable UDEVD_MAX_CHILDS=
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwas removed from udevd.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUdevd now checks the kernel commandline for the following variables:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync udev.log-priority=<syslog priority>
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync udev.children-max=<maximum number of workers>
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync udev.exec-delay=<seconds to delay the execution of RUN=>
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto help debuging coldplug setups where the loading of a kernel
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmodule crashes the system.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe subdirectory in the source tree rules/packages has been renamed to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrules/arch, anc contains only architecture specific rules now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNow the udev daemon itself, does on startup:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync - copy the content of /lib/udev/devices to /dev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync - create the standard symlinks like /dev/std{in,out,err},
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync - use static node information provided by kernel modules
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync and creates these nodes to allow module on-demand loading
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync - possibly apply permissions to all ststic nodes from udev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync rules which are annotated to match a static node
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe default mode for a device node is 0600 now to match the kernel
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccreated devtmpfs defaults. If GROUP= is specified and no MODE= is
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncgiven the default will be 0660.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUdev now gradually starts to pass control over the primary device nodes
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand their names to the kernel, and will in the end only manage the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncpermissions of the node, and possibly create additional symlinks.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAs a first step NAME="" will be ignored, and NAME= setings with names
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncother than the kernel provided name will result in a logged warning.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncKernels that don't provide device names, or devtmpfs is not used, will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncstill work as they did before, but it is strongly recommended to use
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynconly the same names for the primary device node as the recent kernel
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprovides for all devices.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix broken firmware loader search path.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync"udevadm trigger" defaults to "change" events now instead of "add"
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevents. The "udev boot script" might need to add "--action=add" to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe trigger command if not already there, in case the initial coldplug
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevents are expected as "add" events.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe option "all_partitons" was removed from udev. This should not be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncneeded for usual hardware. Udev can not safely make assumptions
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncabout non-existing partition major/minor numbers, and therefore no
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynclonger provide this unreliable and unsafe option.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe option "ignore_remove" was removed from udev. With devtmpfs
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudev passed control over device nodes to the kernel. This option
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncshould not be needed, or can not work as advertised. Neither
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudev nor the kernel will remove device nodes which are copied from
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAll "add|change" matches are replaced by "!remove" in the rules and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncin the udev logic. All types of events will update possible symlinks
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand permissions, only "remove" is handled special now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe modem modeswitch extra was removed and the external usb_modeswitch
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprogram should be used instead.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNew and fixed keymaps.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncKernels with SYSFS_DEPRECATED=y are not supported since a while. Many users
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdepend on the current sysfs layout and the information not available in the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdeprecated layout. All remaining support for the deprecated sysfs layout is
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncremoved now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix for a possible endless loop in the new input_id program.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe option "ignore_device" does no longer exist. There is no way to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncignore an event, as libudev events can not be suppressed by rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIt only prevented RUN keys from being executed, which results in an
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinconsistent behavior in current setups.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBUS=, SYSFS{}=, ID= are long deprecated and should be SUBSYSTEM(S)=,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncATTR(S){}=, KERNEL(S)=. It will cause a warning once for every rule
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfile from now on.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe support for the deprecated IDE devices has been removed from the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdefault set of rules. Distros who still care about non-libata drivers
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncneed to add the rules to the compat rules file.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe ID_CLASS property on input devices has been replaced by the more accurate
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncset of flags ID_INPUT_{KEYBOARD,KEY,MOUSE,TOUCHPAD,TABLET,JOYSTICK}. These are
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdetermined by the new "input_id" prober now. Some devices, such as touchpads,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccan have several classes. So if you previously had custom udev rules which e. g.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncchecked for ENV{ID_CLASS}=="kbd", you need to replace this with
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncENV{ID_INPUT_KEYBOARD}=="?*".
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTo support DEVPATH strings larger than the maximum file name length, the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprivate udev database format has changed. If some software still reads the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprivate files in /dev/.udev/, which it shouldn't, now it's time to fix it.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncPlease do not port anything to the new format again, everything in /dev/.udev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncis and always was private to udev, and may and will change any time without
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprior notice.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncMultiple devices claiming the same names in /dev are limited to symlinks
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynconly now. Mixing identical symlink names and node names is not supported.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThis reduces the amount of data in the database significantly.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNAME="%k" causes a warning now. It's is and always was completely superfluous.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIt will break kernel supplied DEVNAMEs and therefore it needs to be removed
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfrom all rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncMost NAME= instructions got removed. Kernel 2.6.31 supplies the needed names
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncif they are not the default. To support older kernels, the NAME= rules need to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncbe added to the compat rules file.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSymlinks to udevadm with the old command names are no longer resolved to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe udevadm commands.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udev-acl tool got adopted to changes in ConsoleKit. Version 0.4.1 is
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrequired now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe option "last_rule" does no longer exist. Its use breaks too many
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthings which expect to be run from independent later rules, and is an idication
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthat something needs to be fixed properly instead.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe gudev API is no longer marked as experimental,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncG_UDEV_API_IS_SUBJECT_TO_CHANGE is no longer needed. The gudev introspection
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncis enabled by default now. Various projects already depend on introspection
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinformation to bind dynamic languages to the gudev interfaces.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udevadm trigger "--retry-failed" option, which is replaced since quite
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynca while by "--type=failed" is removed.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe failed tracking was not working at all for a few releases. The RUN
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncoption "ignore_error" is replaced by a "fail_event_on_error" option, and the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdefault is not to track any failing RUN executions.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNew keymaps, new modem, hid2hci updated.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix possible crash in udevd when worker processes are busy, rules are
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncchanged at the same time, and workers get killed to reload the rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncProperties set with ENV{.FOO}="bar" are marked private by starting the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncname with a '.'. They will not be stored in the database, and not be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncexported with the event.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFirmware files are looked up in:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncATA devices switched the property from ID_BUS=scsi to ID_BUS=ata.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncata_id, instead of scsi_id, is the default tool now for ATA devices.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe configure options have changed because another library needs to be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinstalled in a different location. Instead of exec_prefix and udev_prefix,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynclibdir, rootlibdir and libexecdir are used. The Details are explained in
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe README file.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncEvent processes now get re-used after they handled an event. This reduces
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe number of forks and the pressure on the CPU significantly, because
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccloned event processes no longer cause page faults in the main daemon.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAfter the events have settled, a few worker processes stay around for
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfuture events, all others get cleaned up.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTo be able to use signalfd(), udev depends on kernel version 2.6.25 now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAlso inotify support is mandatory now to run udev.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe format of the queue exported by the udev damon has changed. There is
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncno longer a /dev/.udev/queue/ directory. The current event queue can be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncaccessed with udevadm settle and libudedv.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncLibudev does not have the unstable API header anymore. From now on,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncincompatible changes will be handled by bumping the library major version.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTo build udev from the git tree gtk-doc is needed now. The tarballs will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncbuild without it and contain the pre-built documentation. An online copy
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncis available here:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe tools from the udev-extras repository have been merged into the main
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudev repository. Some of the extras have larger external dependencies, and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthey can be disabled with the configure switch --disable-extras.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe program vol_id and the library libvolume_id are removed from the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrepository. Libvolume_id is merged with libblkid from the util-linux-ng
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncpackage. Persistent disk links for label and uuid depend on the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncutil-linux-ng version (2.15) of blkid now. Older versions of blkid
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccan not be used with udev.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncLibudev allows to subscribe to udev events. To prevent unwanted messages
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto be delivered, and waking up the subscribing process, a filter can be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinstalled, to drop messages inside a kernel socket filter. The filters
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmatch on the <subsytem>:<devtype> properties of the device.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync This is part of the ongoing effort to replace HAL, and switch current
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncusers over to directly use libudev.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync Libudev is still marked as experimental, and its interface might
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynceventually change if needed, but no major changes of the currently exported
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinterface are expected anymore, and a first stable release should happen
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncA too old kernel (2.6.21) or a kernel with CONFIG_SYSFS_DEPRECATED
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncis not supported since while and udevd will log an error message at
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncstartup. It should still be able to boot-up, but advanced rules and system
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncservices which depend on the information not available in the old sysfs
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncformat will fail to work correctly.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncDVB device naming is supplied by the kernel now. In case older kernels
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncneed to be supported, the old shell script should be added to a compat
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe processed udev events get send back to the netlink socket. Libudev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprovides access to these events. This is work-in-progress, to replace
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe DeviceKit daemon functionality directly with libudev. There are
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncupcoming kernel changes to allow non-root users to subcribe to these
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync"udevadm settle" now optionally accepts a range of events to wait for,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinstead of waiting for "all" events.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe installed watch for block device metadata changes is now removed
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncduring event hadling, because some (broken) tools may be called from udev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrules and (wrongly) open the device with write access. After the finished
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevent handling the watch is restored.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncDevice nodes can be watched for changes with inotify with OPTIONS="watch".
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIf closed after being opened for writing, a "change" uevent will occur.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync/dev/disk/by-{label,uuid}/* symlinks will be automatically updated.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udevadm test command has no longer a --force option, nodes and symlinks
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncare always updated with a test run now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udevd daemon can be started with --resolve-names=never to avoid all user
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand group lookups (e.g. in cut-down systems) or --resolve-names=late to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynclookup user and groups every time events are handled.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncWe are currently merging the Ubuntu rules in the udev default rules,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand get one step closer to provide a common Linux /dev setup, regarding
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdevice names, symlinks, and default device permissions. On udev startup,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwe now expect the following groups to be resolvable to their ids with
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncglibc's getgrnam():
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync disk, cdrom, floppy, tape, audio, video, lp, tty, dialout, kmem.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncLDAP setups need to make sure, that these groups are always resolvable at
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncbootup, with only the rootfs mounted, and without network access available.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSome systems may need to add some new, currently not used groups, or need
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto add some users to new groups, but the cost of this change is minimal,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccompared to the pain the current, rather random, differences between the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncvarious distributions cause for upstream projects and third-party vendors.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIn general, "normal" users who log into a machine should never be a member
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncof any such group, but the device-access should be managed by dynamic ACLs,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwhich get added and removed for the specific users on login/logout and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncsession activity/inactivity. These groups are only provided for custom setups,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand mainly system services, to allow proper privilege separation.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncA video-streaming daemon uid would be a member of "audio" and "video", to get
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncaccess to the sound and video devices, but no "normal" user should ever belong
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto the "audio" group, because he could listen to the built-in microphone with
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncany ssh-session established from the other side of the world.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync/dev/serial/by-{id,path}/ now contains links for ttyUSB devices,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwhich do not depend on the kernel device name. As usual, unique
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdevices - only a single one per product connected, or a real
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUSB serial number in the device - are always found with the same
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncname in the by-id/ directory.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncCompletely identical devices may overwrite their names in by-id/
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand can only be found reliably in the by-path/ directory. Devices
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncspecified by by-path/ must not change their connection, like the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUSB port number they are plugged in, to keep their name.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTo support some advanced features, Linux 2.6.22 is the oldest supported
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncversion now. The kernel config with enabled SYSFS_DEPRECATED is no longer
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncsupported. Older kernels should still work, and devices nodes should be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncreliably created, but some rules and libudev will not work correctly because
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe old kernels do not provide the expected information or interfaces.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix for a possible segfault while swapping network interface names in udev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncversions 131-134.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe group "video" is part of the default rules now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBugfix for kernels using SYSFS_DEPRECATED* option and finding parent
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncblock devices in some cases. No common distro uses this option anymore,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand we do not get enough testing for this and recent udev versions. If
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthis option is not needed to run some old distro with a new kernel,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncit should be disabled in the kernel config.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBugfix for the $links substitution variable, which may crash if no links
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncare created. This should not happen in usual setups because we always
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccreate /dev/{block,char}/ links.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe strings of the parsed rules, which are kept in memory, no longer
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccontain duplicate entries, or duplicate tails of strings. This, and the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncnew rules parsing/matching code reduces the total in-memory size of
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynca huge distro rule sets to 0.08 MB, compared to the 1.2MB of udev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncversion 130.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe export of DEVTYPE=disk/partition got removed from the default
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrules. This value is available from the kernel. The pnp shell script
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmodprobe hack is removed from the default rules. ACPI devices have _proper_
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmodalias support and take care of the same functionality.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncInstallations which support old kernels, but install current default
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudev rules may want to add that to the compat rules file.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncLibvolume_id now always probes for all known filesystems, and does not
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncstop at the first match. Some filesystems are marked as "exclusive probe",
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand if any other filesytem type matches at the same time, libvolume_id
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwill, by default, not return any probing result. This is intended to prevent
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmis-detection with conflicting left-over signatures found from earlier
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfile system formats. That way, we no longer depend on the probe-order
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncin case of multiple competing signatures. In some setups the kernel allows
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto mount a volume with just the old filesystem signature still in place.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThis may damage the new filesystem and cause data-loss, just by mounting
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncit. Because volume_id can not decide which one the correct signature is,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe wrong signatures need to be removed manually from the volume, or the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncvolume needs to be reformatted, to enable filesystem detection and possible
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncauto-mounting.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix segfault if compiled without optimization and dbg() does not get
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccompiled out and uses variables which are not available.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBugfixes. (And maybe new bugs. :))
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe rule matching engine got converted from a rule list to a token
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncarray which reduced the in-memory rules representation of a full
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfeatured distros with thousends of udev rules from 1.2MB to 0.12 MB.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncLimits like 5 ENV and ATTR matches, and one single instance for most
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncother keys per rule are gone.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe NAME assignment is no longer special cased. If later rules assign
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynca NAME value again, the former value will be overwritten. As usual
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfor most other keys, the NAME value can be protected by doing a final
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncassignment with NAME:="<value>".
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAll udev code now uses libudev, which is also exported. The library
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncis still under development, marked as experimental, and its interface
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmay change as long as the DeviceKit integration is not finished.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncMany thanks to Alan Jenkins for his continuous help, and finding and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncoptimizing some of the computing expensive parts.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncKernel devices and device nodes are connected now by reverse indizes in
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync/sys and /dev. A device number retrieved by a stat() or similar, the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynckernel device directory can be found by looking up:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync /sys/dev/{block,char}/<maj>:<min>
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand the device node of the same device by looking up:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync /dev/{block,char}/<maj>:<min>
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix recently introduced bug, which caused a compilation without large
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfile support, where vol_id does not recognize raid signatures at the end
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncof a volume.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFirewire disks now create both, by-id/scsi-* and by-id/ieee-* links.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSeems some kernel versions prevent the creation of the ieee-* links,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncso people used the scsi-* link which disappeared now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncMore libudev work. Almost all udevadm functionality comes from libudev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudevadm trigger has a new option --type, which allows to trigger events
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfor "devices", for "subsystems", or "failed" devices. The old option
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync--retry-failed" still works, but is no longer mentioned in the man page.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udevadm info --device-id-of-file= output has changed to use
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe obvious format. Possible current users should use the --export
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncoption which is not affected.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe old udev commands symlinks to udevadm are not installed, if
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthese symlinks are used, a warning is printed.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncOptical drive's media is no longer probed for raid signatures,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncreading the end of the device causes some devices to malfunction.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAlso the offset of the last session found is used now to probe
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfor the filesystem.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe volume_id library got a major version number update to 1,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncsome deprecated functions are removed.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncA shared library "libudev" gets installed now to provide access
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto udev device information. DeviceKit, the successor of HAL, will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncneed this library to access the udev database and search sysfs for
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe library is currently in an experimental state, also the API is
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncexpected to change, as long as the DeviceKit integration is not
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncWe use ./configure now. See INSTALL for details. Current
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncoptions are:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync "/usr" - prefix for man pages, include files
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync --exec-prefix=
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync "" - the root filesystem, prefix for libs and binaries
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync --sysconfdir=
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync --with-libdir-name=
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync "lib" - directory name for libraries, not a path name
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync multilib 64bit systems may use "lib64" instead of "lib"
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync --enable-debug
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync compile-in verbose debug messages
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync --disable-logging
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync disable all logging and compile-out all log strings
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync --with-selinux
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync link against SELInux libraries, to set the expected context
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync for created files
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIn the default rules, the group "disk" gets permissions 0660 instead
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncof 0640. One small step closer to unify distro rules. Some day, all
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdistros hopefully end up with the same set of rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNo symlinks to udevadm are installed anymore, if they are still needed,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthey should be provided by the package.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncDefault udev rules, which are not supposed to be edited by the user, should
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncbe placed in /lib/udev/rules.d/ now, to make it clear that they are private to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe udev package and will be replaced with an update. Udev will pick up rule
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync /lib/udev/rules.d/ - default installed rules
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync /etc/udev/rules.d/ - user rules + on-the-fly generated rules
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync /dev/.udev/rules.d/ - temporary non-persistent rules created after bootup
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIt does not matter in which directory a rule file lives, all files are sorted
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncin lexical order.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTo help creating /dev/root, we have now:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync $ udevadm info --export --export-prefix="ROOT_" --device-id-of-file=/
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync ROOT_MAJOR=8
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync ROOT_MINOR=5
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIn case the current --device-id-of-file is already used, please switch to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe --export format version, it saves the output parsing and the old
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncformat will be changed to use ':' as a separator, like the format in the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncsysfs 'dev' file.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix cdrom_id to properly recognize blank media.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTape drive id-data is queried from /dev/bsg/* instead of the tape
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncnodes. This avoids rewinding tapes on open().
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe symlinks udevcontrol and udevtrigger are no longer installed by
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe Makefile.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe scsi_id program does not depend on sysfs anymore. It can speak
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSGv4 now, so /dev/bsg/* device nodes can be used, to query SCSI device
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdata, which should solve some old problems with tape devices, where
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwe better do not open all tape device nodes to identify the device.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncMany bugfixes.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe cdrom_id program is replaced by an advanced version, which can
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdetect most common device types, and also properties of the inserted
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmedia. This is part of moving some basic functionality from HAL into
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudev (and the kernel).
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe last WAIT_FOR_SYSFS rule is removed from the default rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe symlinks to udevadm for the debugging tools: udevmonitor and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudevtest are no longer created.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe symlinks to the udevadm man page for the old tool names are
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncno longer created.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAbstract namespace sockets paths in RUN+="socket:@<path>" rules,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncshould be prefixed with '@' to indicate that the path is not a
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUdevstart is removed from the tree, it did not get installed for
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynca long time now, and is long replaced by trigger and settle.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAll udev tools are merged into a single binary called udevadm.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe old names of the tools are built-in commands in udevadm now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSymlinks to udevadm, with the names of the old tools, provide
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe same functionality as the standalone tools. There is also
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynconly a single udevadm.8 man page left for all tools.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTools like mkinitramfs should be checked, if they need to include
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudevadm in the list of files.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe etc/udev/rules.d/ directory now contains a default set of basic
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncudev rules. This initial version is the result of a rules file merge
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncof Fedora and openSUSE. For these both distros only a few specific
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrules are left in their own file, named after the distro. Rules which
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncare optionally installed, because they are only valid for a specific
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncarchitecture, or rules for subsystems which are not always used are
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncDynamic rules can be created in /dev/.udev/rules.d/ to trigger
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncactions by dynamically created rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSYMLINK=="<value>" matches agains the entries in the list of
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccurrently defined symlinks. The links are not created in the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfilesystem at that point in time, but the values can be matched.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncRUN{ignore_error}+="<program>" will ignore any exit code from the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprogram and not record as a failed event.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFinal merge of patches/features from the Ubuntu package.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncControl characters in filesystem label strings are no longer silenty
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncremoved, but hex-encoded, to be able to uniquely identify the device
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncby its symlink in /dev/disk/by-label/.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIf libvolume_id is used by mount(8), LABEL= will work as expected,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncif slashes or other characters are used in the label string.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTo test the existence of a file, TEST=="<file>" and TEST!="<file>"
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccan be specified now. The TEST key accepts an optional mode mask
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncTEST{0100}=="<is executable file>".
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncScsi_id now supports a mode without expecting scsi-specific sysfs
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncentries to allow the extraction of cciss-device persistent properties.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIn the future, we may see uuid's which are just simple character
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncstrings (see the DDF Raid Specification). For that reason vol_id now
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncexports ID_FS_UUID_SAFE, just like ID_FS_LABEL_SAFE. For things like
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe creation of symlinks, the *_SAFE values ensure, that no control
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncor whitespace characters are used in the filename.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncPossible users of libvolume_id, please use the volume_id_get_* functions.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe public struct will go away in a future release of the library.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncRemoval of useless extras/eventrecorder.sh.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe directory multiplexer for dev.d/ and hotplug.d are finally removed
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfrom the udev package.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSymlinks can have priorities now, the priority is assigned to the device
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncand specified with OPTIONS="link_priority=100". Devices with higher
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncpriorities overwrite the symlinks of devices with lower priorities.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIf the device that currently owns the link, goes away, the symlink
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwill be removed, and recreated, pointing to the next device with the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynchighest actual priority. This should make /dev/disk/by-{label,uuid,id}
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmore reliable, if multiple devices contain the same metadata and overwrite
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthese symlinks.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe dasd_id program is removed from the udev tree, and dasdinfo, with the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncneeded rules, are part of the s390-tools now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncPlease add KERNEL=="[0-9]*:[0-9]*" to the scsi wait-for-sysfs rule,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwe may get the scsi sysfs mess fixed some day, and this will only catch
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe devices we are looking for.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUSB serial numbers for storage devices have the target:lun now appended,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncto make it possibble to distinguish broken multi-lun devices with all
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe same SCSI identifiers.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNote: The extra "run_directory" which searches and executes stuff in
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync/etc/hotplug.d/ and /etc/dev.d/ is long deprecated, and will be removed
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwith the next release. Make sure, that you don't use it anymore, or
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncprovides your own implementation of that inefficient stuff.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncWe are tired of reports about a "slow udev", because these directories
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynccontain stuff, that runs with _every_ event, instead of using rules,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthat run programs only for the matching events.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncDRIVER== will match only for devices that actually have a real
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdriver. DRIVERS== must be used, if parent devices should be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncincluded in the match.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncLibvolume_id's "linux_raid" detection needed another fix.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAdd additional check to volume_id detection of via_raid, cause
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncsome company decided to put a matching pattern all over the empty
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncstorage area of their music players.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix path_id for SAS devices.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udev daemon can be started with --debug-trace now, which will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncexecute all events serialized to get a chance to catch a possible
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncaction that crashes the box.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncA warning is logged, if PHYSDEV* keys, the "device" link, or a parent
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdevice attribute like $attr{../file} is used, only WAIT_FOR_SYSFS rules
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncare excluded from the warning. Referencing parent attributes directly
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmay break when something in the kernel driver model changes. Udev will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncjust find the attribute by walking up the parent chain.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUdevtrigger now sorts the list of devices depending on the device
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdependency, so a "usb" device is triggered after the parent "pci"
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncRevert persistent-storage ata-serial '_' '-' replacement.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncUdevtrigger can now filter the list of devices to be triggered. Matches
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfor subsystems or sysfs attributes can be specified.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe entries in /dev/.udev/queue and /dev/.udev/failed have changed to
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynczero-sized files to avoid pointing to /sys and confuse broken tools which
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncscan the /dev directory. To retry failed events, udevtrigger --retry-failed
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncshould be used now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe rules and scripts to create udev rules for persistent network
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncdevices and optical drives are in the extras/rules_generator directory
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncnow. If you use something similar, please consider replacing your own
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncversion with this, to share the support effort. The rule_generator
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinstalls its own rules into /etc/udev/rules.d.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe cdrom_id tool installs its own rule now in /etc/udev/rules.d, cause
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe rule_generator depends on cdrom_id to be called in an earlier rule.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncRenaming of some key names (the old names still work):
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBUS -> SUBSYSTEMS, ID -> KERNELS, SYSFS -> ATTRS, DRIVER -> DRIVERS.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync(The behavior of the key DRIVER will change soon in one of the next
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncreleases, to match only the event device, please switch to DRIVERS
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncinstead. If DRIVER is used, it will behave like DRIVERS, but an error
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncWith the new key names, we have a more consistent and simpler scheme.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncWe can match the properties of the event device only, with: KERNEL,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSUBSYSTEM, ATTR, DRIVER. Or include all the parent devices in the match,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwith: KERNELS, SUBSYSTEMS, ATTRS, DRIVERS. ID, BUS, SYSFS, DRIVER are no
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynclonger mentioned in the man page and should be switched in the rule
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncATTR{file}="value" can be used now, to write to a sysfs file of the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevent device. Instead of:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync ..., SYSFS{type}=="0|7|14", RUN+="/bin/sh -c 'echo 60 > /sys$$DEVPATH/timeout'"
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwe now can do:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync ..., ATTR{type}=="0|7|14", ATTR{timeout}="60"
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAll the PHYSDEV* keys are deprecated and will be removed from a
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfuture kernel:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync PHYDEVPATH - is the path of a parent device and should not be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync needed at all.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync PHYSDEVBUS - is just a SUBSYSTEM value of a parent, and can be
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync matched with SUBSYSTEMS==
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync PHYSDEVDRIVER - for bus devices it is available as ENV{DRIVER}.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync Newer kernels will have DRIVER in the environment,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync for older kernels udev puts in. Class device will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync no longer carry this property of a parent and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync DRIVERS== can be used to match such a parent value.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNote that ENV{DRIVER} is only available for a few bus devices, where
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthe driver is already bound at device event time. On coldplug, the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevents for a lot devices are already bound to a driver, and they will have
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthat value set. But on hotplug, at the time the kernel creates the device,
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncit can't know what driver may claim the device after that, therefore
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncin most cases it will be empty.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFailed events should now be re-triggered with:
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync udevtrigger --retry-failed.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncPlease switch to this command, so we keep the details of the /dev/.udev/failed/
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfiles private to the udev tools. We may need to switch the current symlink
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynctarget, cause some obviously broken tools try to scan all files in /dev
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncincluding /dev/.udev/, find the links to /sys and end up stat()'ing sysfs files
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmillion times. This takes ages on slow boxes.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe udevinfo attribute walk (-a) now works with giving a device node
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncname (-n) instead of a devpath (-p). The query now always works, also when
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncno database file was created by udev.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe built-in /etc/passwd /etc/group parser is removed, we always depend on
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncgetpwnam() and getgrnam() now. One of the next releases will depend on
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfnmatch() and may use getopt_long().
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBugfixes and small improvements.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix path_id for recent kernels.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsync%e is finally gone.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAdded support for swapping network interface names, by temporarily
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncrenaming the device and wait for the target name to become free.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe built-in MODALIAS key and substitution is removed.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncThe binary firmware helper is replaced by the usual simple
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncshell script. Udevsend is removed from the tree.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncBugfix release.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncSome more keys require the correct use of '==' and '=' depending
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncon the kind of operation beeing an assignment or a match. Rules
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncwith invalid operations are skipped and logged to syslog. Please
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynctest with udevtest if the parsing of your rules throws errors and
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncfix possibly broken rules.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncProvide "udevsettle" to wait for all current udev events to finish.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncIt also watches the current kernel netlink queue by comparing the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynceven sequence number to make sure that there are no current pending
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevents that have not already arrived in the daemon.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix rule to skip persistent rules for removable IDE devices, which
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncalso skipped optical IDE drives.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAll *_id program are installed in /lib/udev/ by default now.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncNo binary is stripped anymore as this should be done in the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncpackaging process and not at build time.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynclibvolume_id is provided as a shared library now and vol_id is
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsynclinked against it. Also one of the next HAL versions will require
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncthis library, and the HAL build process will also require the
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncheader file to be installed. The copy of the same code in HAL will
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncbe removed to have only a single copy left on the system.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncAdd persistent links for SCSI tapes. The rules file is renamed
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncCreate persistent path for usb devices. Can be used for all sorts
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncof devices that can't be distinguished by other properties like
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncmultiple identical keyboards and mice connected to the same box.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncProvide "udevtrigger" program to request events on coldplug. The
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncshell script is much too slow with thousends of devices.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix persistent disk rules to exclude removable IDE drives.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncWarn if %e, $modalias or MODALIAS is used.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix queue export, which wasn't correct for subsequent add/remove
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncevents for the same device.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncFix cramfs detection on big endian.
040abec2534dadc53ebc8fa378ef03f4feecb7dbvboxsyncMake WAIT_FOR_SYSFS usable in "normal" rules and silent if the whole
RUN="/bin/program" does not longer automatically add the subsystem
as the first parameter. This is from the days of /sbin/hotplug
to the key like RUN+="/bin/program $env{SUBSYSTEM}".
moving the class devices to /sys/devices.
Please report any new bugs/problems, that may be caused by this big
added /dev/disk/by-name/* for device mapper device names.
UDEV [1134776873.702967] add@/block/sdb
DEVNAME=/dev/sdb
DEVLINKS=/dev/disk/by-id/usb-IBM_Memory_Key_0218B301030027E8 /dev/disk/by-path/usb-0218B301030027E8:0:0:0
Default location for rule sripts and helper programs is now: /lib/udev/.
Also /lib/udev/devices is recommended as a directory where packages or
Kernel 2.6.15 will have symlinks at /class/input pointing to the real
Fix a stupid typo in extras/run_directory for "make install".
/dev/disk/by-label/* links, because we import untrusted data and
have stdin/stdout/stderr, which broke the forked tools in some
The new run_program() uncovered it, because /dev/null was not
persistent disk rules in /dev/disk/by-*/* on your distro, just
RUN+="socket:/org/freedesktop/hal/udev_event"
echo "" > /proc/sys/kernel/hotplug
make EXTRAS=extras/run_directory/
RUN+="/sbin/udev_run_hotplugd"
ACTION="add", DEVPATH="/devices/*", MODALIAS=="?*", RUN+="/sbin/modprobe $modalias"
needs to be documented, for now it's only visible in udev_rules_parse.c.
KERNEL="hd*[!0-9]", IMPORT="/sbin/ata_id --export $tempnode"
KERNEL="hd*[!0-9]", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_MODEL}_$env{ID_SERIAL}"
kay@pim:~> tree /dev/disk
handling. This is meant as a general replacement for the dev.d/-directories
We support log priority levels now. The value udev_log in udev.conf is used
make USE_KLIBC=true KLCC=/usr/bin/klcc all