summaryrefslogtreecommitdiff
path: root/udev_node.c
AgeCommit message (Collapse)Author
2008-04-20logging: add trailing newline to all stringsKay Sievers
2008-03-13selinux: set context for real file name not the temp nameKay Sievers
2007-12-29do not skip RUN execution if device node removal failsAnthony L. Awtrey
2007-09-20prevent wrong symlink creation if database disagress with current rulesKay Sievers
2007-09-12ignore device node names while restoring symlinks from the stackKay Sievers
2007-08-30add /dev/rtc symlink if new rtc drivers are usedKay Sievers
2007-06-25always unlink temporary file before creating new oneKay Sievers
2007-06-21do not try to create existing fileKay Sievers
2007-06-21atomically replace existing nodes and symlinksKay Sievers
Based on a patch from Scott James Remnant <scott@ubuntu.com>.
2007-06-03add TEST=="<file>" keyKay Sievers
2007-03-21udevtest: add --force modeKay Sievers
2007-03-19if a node goes away, possibly restore a waiting symlinkKay Sievers
2007-03-18priority based symlink handlingKay Sievers
Symlinks can have priorities now, the priority is assigned to the device and specified with OPTIONS="link_priority=100". Devices with higher priorities overwrite the symlinks of devices with lower priorities. If the device, that currently owns the link goes away, the symlink will be removed, and recreated, pointing to the next device with the highest actual priority. This should solve the issue, that inserting an USB-stick may overwrite the /dev/disk/by-id/-link of another disk, and removes the entire link after the USB-stick is disconnected. If no priorities are specified, the new link will overwrite the current one, and if the device goes away, it will restore the old link. It should be possible to assign lower priorities to removable devices, if needed. In multipath setups, we see several devices, which all connect to the same volume, and therefore all try to create the same metadata-links. The different path-devices are combined into one device-mapper device, which also contains the same metadata. It should be possible, to assign multipath-table device-mapper devices a higher priority, so path-devices that appear and disappear, will not overwrite or delete the device-mapper device links.
2007-03-17read list of devices from index, make index private to databaseKay Sievers
2007-03-16remove old error messageKay Sievers
2007-03-16selinux: move selinux_exit() to the main programsKay Sievers
2007-03-15restore overwritten symlinks when the device goes awayKay Sievers
2006-08-28update source file headersKay Sievers
2006-08-19consistent key naming to match only the event device or include all parent ↵Kay Sievers
devices This scheme is more consistent and makes it obvious if a match happens against the event device only, or the full chain of parent devices. The old key names are now: BUS -> SUBSYSTEMS ID -> KERNELS SYSFS -> ATTRS DRIVER -> DRIVERS Match keys for the event device: KERNEL SUBSYSTEM ATTR DRIVER (in a future release, for now the same as DRIVERS) Match keys for all devices along the parent device chain: KERNELS SUBSYSTEMS ATTRS DRIVERS ID, BUS, SYSFS are no longer mentioned in the man page but still work. DRIVER must be converted to DRIVERS to match the new scheme. For now, an error is logged, if DRIVER is used. In a future release, the DRIVER key behaviour will change.
2006-08-18selinux: init once in the daemon, not in every event processHarald Hoyer
2006-06-14don't remove symlinks if they are already thereKay Sievers
Consecutive "add" events will not remove and recreate the same symlinks anymore. No longer valid links, like after changing a filesystem label, will still be removed.
2006-04-15udevtest: don't try to delete symlinksKay Sievers
2006-04-15apply format char to variables exported by ENVKay Sievers
2006-04-12remove old symlinks before creating current onesKay Sievers
This will prevent incorrect symlinks when a filesystem label is changed and the event is triggered again from sysfs.
2006-04-05merge device event handling and make database content available on "remove"Kay Sievers