systemd/rules.d/60-cdrom_id.rules

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="cdrom_end"
SUBSYSTEM!="block", GOTO="cdrom_end"
KERNEL!="sr[0-9]*|vdisk*|xvd*", GOTO="cdrom_end"
ENV{DEVTYPE}!="disk", GOTO="cdrom_end"

# unconditionally tag device as CDROM
KERNEL=="sr[0-9]*", ENV{ID_CDROM}="1"

# stop automatically any mount units bound to the device if the media eject
# button is pressed.
ENV{ID_CDROM}=="1", ENV{SYSTEMD_MOUNT_DEVICE_BOUND}="1"

# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode", GOTO="cdrom_end"

# import device and media properties and lock tray to
# enable the receiving of media eject button events
IMPORT{program}="cdrom_id --lock-media $devnode"

# ejecting a CD does not remove the device node, so mark the systemd device
# unit as inactive while there is no medium; this automatically cleans up of
# stale mounts after ejecting
ENV{DISK_MEDIA_CHANGE}=="?*", ENV{ID_CDROM_MEDIA}!="?*", ENV{SYSTEMD_READY}="0"

KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"

LABEL="cdrom_end"
cdrom_id: add Xen cdrom support 2009-04-17 02:29:56 +04:00			`# do not edit this file, it will be overwritten on update`
cdrom_id: add rules file to call cdrom_id 2006-09-05 05:43:14 +04:00
replace "add\|change" with "!remove" 2010-04-12 18:52:41 +04:00			`ACTION=="remove", GOTO="cdrom_end"`
cdrom_id: always set ID_CDROM regardless if we can run cdrom_id 2010-04-12 03:12:23 +04:00			`SUBSYSTEM!="block", GOTO="cdrom_end"`
rules: allow SPARC vdisk devices when identifying CD drives (#5599) 2017-03-20 13:22:54 +03:00			`KERNEL!="sr[0-9]\|vdisk\|xvd*", GOTO="cdrom_end"`
cdrom_id: always set ID_CDROM regardless if we can run cdrom_id 2010-04-12 03:12:23 +04:00			`ENV{DEVTYPE}!="disk", GOTO="cdrom_end"`

cdrom_id: add tray lock and eject handling 2011-06-18 22:54:47 +04:00			`# unconditionally tag device as CDROM`
cdrom_id: only mark sr[0-9]* as ID_CDROM we cannot be sure for xvd* 2010-04-27 14:26:00 +04:00			`KERNEL=="sr[0-9]*", ENV{ID_CDROM}="1"`
cdrom_id: add tray lock and eject handling 2011-06-18 22:54:47 +04:00
core: make mount units from /proc/self/mountinfo possibly bind to a device (#4515) Since commit 9d06297, mount units from mountinfo are not bound to their devices anymore (they use the "Requires" dependency instead). This has the following drawback: if a media is mounted and the eject button is pressed then the media is unconditionally ejected leaving some inconsistent states. Since udev is the component that is reacting (no matter if the device is used or not) to the eject button, users expect that udev at least try to unmount the media properly. This patch introduces a new property "SYSTEMD_MOUNT_DEVICE_BOUND". When set on a block device, all units that requires this device will see their "Requires" dependency upgraded to a "BindTo" one. This is currently only used by cdrom devices. This patch also gives the possibility to the user to restore the previous behavior that is bind a mount unit to a device. This is achieved by passing the "x-systemd.device-bound" option to mount(8). Please note that currently this is not working because libmount treats the x-* options has comments therefore they're not available in utab for later application retrievals. 2016-12-16 19:13:58 +03:00			`# stop automatically any mount units bound to the device if the media eject`
			`# button is pressed.`
			`ENV{ID_CDROM}=="1", ENV{SYSTEMD_MOUNT_DEVICE_BOUND}="1"`

cdrom_id: add tray lock and eject handling 2011-06-18 22:54:47 +04:00			`# media eject button pressed`
remove mknod() logic and rely on 'devtmpfs' 2012-01-01 07:21:15 +04:00			`ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode", GOTO="cdrom_end"`
cdrom_id: add tray lock and eject handling 2011-06-18 22:54:47 +04:00
			`# import device and media properties and lock tray to`
			`# enable the receiving of media eject button events`
remove mknod() logic and rely on 'devtmpfs' 2012-01-01 07:21:15 +04:00			`IMPORT{program}="cdrom_id --lock-media $devnode"`
cdrom_id: always set ID_CDROM regardless if we can run cdrom_id 2010-04-12 03:12:23 +04:00
rules: clean up stale CD drive mounts after ejection Ejecting a CD with the hardware drive button only causes a change uevent, but the device node stays around (just without a medium). Pick up these uevents and mark the device as SYSTEMD_READY=0 on ejection, so that systemd stops the device unit and consequently all mount units on it. On media insertion, mark the device as SYSTEMD_READY=1 again. https://bugs.freedesktop.org/show_bug.cgi?id=72206 https://bugzilla.opensuse.org/show_bug.cgi?id=909418 https://bugs.archlinux.org/task/42071 https://bugs.launchpad.net/bugs/1168742 2015-01-28 15:57:47 +03:00			`# ejecting a CD does not remove the device node, so mark the systemd device`
			`# unit as inactive while there is no medium; this automatically cleans up of`
			`# stale mounts after ejecting`
			`ENV{DISK_MEDIA_CHANGE}=="?", ENV{ID_CDROM_MEDIA}!="?", ENV{SYSTEMD_READY}="0"`

extras: cdrom_id - create /dev/cdrom and conditionally /dev/dvd for sr0 Udev does no longer automatically create udev rules in /etc from the device hotplug path. No device name reservation will happen anymore; this model creates too many problems for setups with many device changes or media which is booted on different hardware. Enumerated device names which are based on device discovery order or on persistent on-disk name reservation will in general not be supported by udev in the future. It is a problem that can not be solved properly, and it always creates new problems at the same time it tries to solve the original one. Udev will no longer pretend it can solve these issues, and people should switch to available alternatives which provide the far better compromise. From now on, udev will only create /dev/cdrom for the first optical drive, and if the drive is capable /dev/dvd. No other devices will get any compatibility symlinks or enumerated device names like cdrom1, cdrom2, and so on. The /dev/cdrom and /dev/dvd links have by default a negative link priority, which will cause them to be overwritten by any other device which clains the same names with already existing udev rules. If stable device names are needed, the /dev/disk/by-id/ links, which uniquely identify a specific piece of hardware should be used. The links usually contain a device serial number and the link names will not depend on device discovery order. If completely identical devices with identical or no serial number need to be handled at the same time, the /dev/disk/by-path/ links can be used. These links depend on the physical port which is used to connect the device. It will change when the same device is moved to a different port or host adapter. If custom names are needed, custom udev rules which match on specific device properties need to be added by the administrator. 2012-01-30 18:08:45 +04:00			`KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"`

cdrom_id: always set ID_CDROM regardless if we can run cdrom_id 2010-04-12 03:12:23 +04:00			`LABEL="cdrom_end"`