summaryrefslogtreecommitdiff
path: root/rules/60-block.rules
Commit message (Collapse)AuthorAgeFilesLines
* rules: watch metadata changes in mmcblk devices (#6050)kjackiewicz2017-05-301-1/+1
| | | | | | | Formatting sd-cards does not trigger "change" uevents. As a result clients using udev API don't get any updates afterwards and get outdated information about the device. Include mmcblk* in a match for watch option assignment.
* rules: block: add support for pmem devices (#3683)bgbhpe2016-07-081-1/+1
| | | | | | | | | | | | | | Persistent memory devices can be exposed as block devices as /dev/pmemN and /dev/pmemNs. pmemN is the raw device and is byte-addressable from within the kernel and when mmapped by applications from a DAX-mounted file system. pmemNs has the block translation table (BTT) layered on top, offering atomic sector/block access. Both pmemN and pmemNs are expected to contain file systems. blkid(8) and lsblk(8) seem to correctly report on pmemN and pmemNs. systemd v219 will populate /dev/disk/by-uuid/ when, for example, mkfs is used on pmem, but systemd v228 does not. Add pmem to the whitelist.
* rules: whitelist xvd* devicesAlex Crawford2015-06-081-1/+1
| | | | Xen disks need to be whitelisted as well.
* rules: restore block watch after CHANGE eventsTom Gundersen2015-05-301-1/+1
| | | | | When processing an event, the watch is disabled, make sure it is restorted after a CHANGE event has been processed.
* rules: fix typo in block watch ruleTom Gundersen2015-05-301-1/+1
| | | | | The intention was to turn this rule from using a blacklist to a whitelist, but there was a stray '!'.
* rules: move block device rules to its own rules fileKay Sievers2015-03-121-0/+11