summaryrefslogtreecommitdiffstats
path: root/rules (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Rename udev's rules/ to rules.d/Zbigniew Jędrzejewski-Szmek2019-10-1026-800/+0
| | | | | | This change is only about the source tree. We have tmpfiles.d/, modprobe.d/, sysctl.d/, and sysusers.d/, but for historical reasons, rules/ didn't fit this pattern. We also *install* it as rules.d/. Let's rename to be consistent.
* trivial: rename chromeos to chromiumosTim Teichmann2019-10-072-3/+3
|
* rules: Add automatic suspend udev rulesMario Limonciello2019-10-042-0/+29
| | | | | | | | | | | | | | | | | | | The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
* rules: Allow quirks for platform IIO accelerometersDaniel Stuart2019-09-241-1/+1
| | | | | Chromebooks have IIO accelerometers with modalias as platform:cros-ec-accel. This commit allows these devices to use systemd orientation quirk.
* udev: Add id program and rule for FIDO security tokensFabian Henneke2019-09-062-0/+8
| | | | | | | | | | | | | | Add a fido_id program meant to be run for devices in the hidraw subsystem via an IMPORT directive. The program parses the HID report descriptor and assigns the ID_SECURITY_TOKEN environment variable if a declared usage matches the FIDO_CTAPHID_USAGE declared in the FIDO CTAP specification. This replaces the previous approach of whitelisting all known security token models manually. This commit is accompanied by a test suite and a fuzzer target for the descriptor parsing routine. Fixes: #11996.
* Merge pull request #13360 from keszybz/udev-watch-moreLennart Poettering2019-08-202-2/+4
|\ | | | | udev: set "watch" for more devices
| * udev: allow persistent storage rules work for ubi devicesZbigniew Jędrzejewski-Szmek2019-08-162-2/+2
| | | | | | | | | | | | | | | | Back in dbbf424c8b77c1649e822c20c0b1fee1d2cfd93d, we merged a rule to add persistent storage for /dev/ubi*, but this rule could have never worked because of the top-level exclude. Also set "watch" for /dev/ubi*.
| * udev: assume all devices which have persistent links also need to be watchedZbigniew Jędrzejewski-Szmek2019-08-161-1/+3
| | | | | | | | | | | | | | | | We had two similar lists, but one was accepting many more device types. I assume that this is by mistake, simply because the lack of device links is easier to notice than the lack of synthesized event after the device is written to. This uses the same list in both places, effectively adding "watch" attribute to /dev/nbd*, /dev/zd*, etc.
* | tmpfiles: override permissions of static nodes that need thisZbigniew Jędrzejewski-Szmek2019-08-191-0/+3
|/ | | | Fixes #13350.
* rules: enable hardware-related targets also for user instancesZbigniew Jędrzejewski-Szmek2019-05-281-6/+6
| | | | | | | | | | > the odd thing is that these units are also defined for the systemd user > instance. However, because these are bound to SYSTEMD_USER_WANTS rather than > SYSTEMD_WANTS they are effectively useless unless some other software > installs the corresponding udev rules first. This adds the rules and starts those targets also for user instances. Fixes #12330.
* udev-rules: add udmabuf to kvm groupMarc-André Lureau2019-04-231-0/+2
| | | | | | | It will have the default 0660 mode. Fixes: #12283 Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
* units: add usb-gadget targetAndrzej Pietrasiewicz2019-02-151-0/+2
| | | | | | | | | | Linux can be run on a device meant to act as a USB peripheral. In order for a machine to act as such a USB device it has to be equipped with a UDC - USB Device Controller. This patch adds a target reached when UDC becomes available. It can be used for activating e.g. a service unit which composes a USB gadget with configfs and activates it.
* rules: watch metadata changes on nbd devicesTony Asleson2019-02-151-1/+1
| | | | | | Include nbd* in match for watch option assignment. Signed-off-by: Tony Asleson <tasleson@redhat.com>
* rules: watch metadata changes on DASD devicesVojtech Trefny2018-12-041-1/+1
| | | | | To make sure the change event is emitted and udev db is updated after metadata changes.
* Merge pull request #7411 from joergsteffens/tapechangerLennart Poettering2018-10-221-2/+12
|\ | | | | udev-rules: extend tape and tape changer rules
| * udev-rules: make tape devices also accessable by ENV{ID_SCSI_SERIAL}Joerg Steffens2017-12-271-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tape and tape changer devices from Amazon Webservice Storage Gateway VTLs and maybe other iSCSI VTLs all have the same ENV{ID_SERIAL}. The results is, that only the last device is available in /dev/tape/by-id/, as the former devices have been overwritten. However, the devices can be distinguished by ENV{ID_SCSI_SERIAL}. ENV{ID_SCSI_SERIAL} is not set on directly connected SCSI devices. This rule additional creates links based on the ENV{ID_SCSI_SERIAL}, if it is set. In my case, it creates (ID_SCSI_SERIAL) /dev/tape/by-id/scsi-AMZN_SGW-6BF81D02_MC_00001 /dev/tape/by-id/scsi-AMZN_SGW-6BF81D02_TD_00001 /dev/tape/by-id/scsi-AMZN_SGW-6BF81D02_TD_00002 ... instead of only (ID_SERIAL) scsi-2414d5a4e5f5347572d364246
| * udev-rules: make tape-changers also apprear in /dev/tape/by-path/Joerg Steffens2017-11-211-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is important to be able to access tape changer ("Medium Changers") by persistant name. While tape devices can be accessed via /dev/tape/by-id/ and /dev/tape/by-path/, tape-changers could only be accessed by /dev/tape/by-id/. However, in some cases, especially when accessing Amazon Webservice Storage Gateway VTLs (or accessing iSCSI VTLs in general?) this does not work, as all tape devices and the tape changer have the same ENV{ID_SERIAL}. The results is, that only the last device is available in /dev/tape/by-id/, as the former devices have been overwritten. As this behavior is hard to change without breaking consistentcy, this additional device in /dev/tape/by-path/ can be used to access the medium changes. The tape devices can also be accessed by this path. The content of the directory will now look like: # SCSI tape device, rewind (unchanged) /dev/tape/by-path/$env{ID_PATH} -> ../../st* # SCSI tape device, no-rewind (unchanged) /dev/tape/by-path/$env{ID_PATH}-nst -> ../../nst* # SCSI tape changer device (newly added) /dev/tape/by-path/$env{ID_PATH}-changer -> ../../sg* Tape devices and tape changer have different ID_PATHs. SCSI tape changer get the suffix "-changer" to make them better distinguishable from tape devices.
* | rules: Add ID_REVISION environment var for NVMe devicesHarry Mallon2018-10-161-0/+2
| |
* | don't ignore zd* block devicesMarcin Skarbek2018-08-271-1/+1
| |
* | rules: Add by-id symlinks for persistent memoryKeith Busch2018-07-101-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds a by-id symlink to persistent memory namespace if it exports a uuid attribute. The result looks like the following example: # ls -l /dev/disk/by-id/* lrwxrwxrwx 1 root root 13 Jul 9 15:24 pmem-206dcdfe-69b7-4e86-a01b-f540621ce62e -> ../../pmem1.2 lrwxrwxrwx 1 root root 13 Jul 9 15:24 pmem-73840bf1-4e74-4ba4-a9c8-8248934c07c8 -> ../../pmem1.1 lrwxrwxrwx 1 root root 13 Jul 9 15:24 pmem-8137bdfd-3c4d-4b26-b326-21da3d4cd4e5 -> ../../pmem1.4 lrwxrwxrwx 1 root root 13 Jul 9 15:24 pmem-f43d1b6e-3300-46cb-8afc-06d66a7c16f6 -> ../../pmem1.3 Signed-off-by: Keith Busch <keith.busch@intel.com>
* | Drop my copyright headersZbigniew Jędrzejewski-Szmek2018-06-141-2/+0
| | | | | | | | | | | | | | perl -i -0pe 's/\s*Copyright © .... Zbigniew Jędrzejewski.*?\n/\n/gms' man/*xml git grep -e 'Copyright.*Jędrzejewski' -l | xargs perl -i -0pe 's/(#\n)?# +Copyright © [0-9, -]+ Zbigniew Jędrzejewski.*?\n//gms' git grep -e 'Copyright.*Jędrzejewski' -l | xargs perl -i -0pe 's/\s*\/\*\*\*\s+Copyright © [0-9, -]+ Zbigniew Jędrzejewski[^\n]*?\s*\*\*\*\/\s*/\n\n/gms' git grep -e 'Copyright.*Jędrzejewski' -l | xargs perl -i -0pe 's/\s+Copyright © [0-9, -]+ Zbigniew Jędrzejewski[^\n]*//gms'
* | tree-wide: beautify remaining copyright statementsLennart Poettering2018-06-141-1/+1
| | | | | | | | | | | | Let's unify an beautify our remaining copyright statements, with a unicode ©. This means our copyright statements are now always formatted the same way. Yay.
* | udev: create /dev/disk/by-label symlink for LUKS2 (#8998)Milan Broz2018-05-151-1/+1
| | | | | | | | | | | | | | | | LUKS2 header supports to device label and blkid since 2.32 version already supports this option. Persistent udev storage rules should create symlink for this label. For older devices this value is not set so changed rule should be compatible.
* | tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | | | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* | rules: skip btrfs check if devices are not ready in 64-btrfs.rules (#8304)Franck Bui2018-02-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | If any devices are marked with 'SYSTEMD_READY=0' then we shouldn't run any btrfs check on them. Indeed there's no point in running "btrfs ready" on devices that already have SYSTEMD_READY=0 set. Most probably such devices are members of a higher layer aggregate device such as dm-multipath or software RAID. Doing IO on them wastes time at best, and may cause delays, timeouts, or even hangs at worst (think active-passive multipath or degraded RAID, for example). It was initially reported at: https://bugzilla.opensuse.org/show_bug.cgi?id=872929
* | rules: Mark the kvm device as static_node (for s390x and ppc64) (#7795)Thomas Huth2018-01-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On s390x and ppc64, the permissions of the /dev/kvm device are currently not right as long as the kvm kernel module has not been loaded yet. The kernel module is using MODULE_ALIAS("devname:kvm") there, so the module will be loaded on the first access to /dev/kvm. In that case, udev needs to apply the permission to the static node already (which was created via devtmpfs), i.e. we have to specify the option "static_node=kvm" in the udev rule. Note that on x86, the kvm kernel modules are loaded early instead (via the MODULE_DEVICE_TABLE(x86cpu, ...) feature checking), so that the right module is loaded for the Intel or AMD hypervisor extensions right from the start. Thus the "static_node=kvm" is not required on x86 - but it also should not hurt here (and using it here even might be more future proof in case the module loading is also done delayed there one day), so we just add the new option to the rule here unconditionally.
* | meson: re-attach rule-syntax-check.py testZbigniew Jędrzejewski-Szmek2017-11-221-0/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 39/248 rule-syntax-check OK 0.07 s --- command --- /home/zbyszek/src/systemd-work/test/rule-syntax-check.py \ /home/zbyszek/src/systemd-work/build/../rules/60-block.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-cdrom_id.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-drm.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-evdev.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-input-id.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-persistent-alsa.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-persistent-input.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-persistent-storage.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-persistent-storage-tape.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-persistent-v4l.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-sensor.rules \ /home/zbyszek/src/systemd-work/build/../rules/60-serial.rules \ /home/zbyszek/src/systemd-work/build/../rules/70-joystick.rules \ /home/zbyszek/src/systemd-work/build/../rules/70-mouse.rules \ /home/zbyszek/src/systemd-work/build/../rules/70-touchpad.rules \ /home/zbyszek/src/systemd-work/build/../rules/75-net-description.rules \ /home/zbyszek/src/systemd-work/build/../rules/75-probe_mtd.rules \ /home/zbyszek/src/systemd-work/build/../rules/78-sound-card.rules \ /home/zbyszek/src/systemd-work/build/../rules/80-drivers.rules \ /home/zbyszek/src/systemd-work/build/../rules/80-net-setup-link.rules \ /home/zbyszek/src/systemd-work/build/rules/50-udev-default.rules \ /home/zbyszek/src/systemd-work/build/rules/64-btrfs.rules \ /home/zbyszek/src/systemd-work/build/rules/99-systemd.rules --- stdout --- ... ------- It got dropped by mistake in 72cdb3e783174dcf9223a49f03e3b0e2ca95ddb8.
* Add license headers and SPDX identifiers to meson.build filesZbigniew Jędrzejewski-Szmek2017-11-191-0/+17
| | | | | | | So far I avoided adding license headers to meson files, but they are pretty big and important and should carry license headers like everything else. I added my own copyright, even though other people modified those files too. But this is mostly symbolic, so I hope that's OK.
* Add SPDX license headers to various assorted filesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* rules: run all persistent-input rules for rmi and i8042 (#7287)Simon Arlott2017-11-101-2/+2
| | | | | | | Commit 83b48159 set ID_BUS for these subsystems but copied the intent of commit c49df207 by not creating symlinks for those devices. Remove the GOTO so that the rest of the rules are still processed and symlinks are created for rmi and i8042 devices.
* udev-rules: Add rule for /dev/kfdTom Stellard2017-11-081-0/+1
|
* udev-rules: Permission changes for /dev/dri/renderD*Tom Stellard2017-11-081-1/+3
| | | | | | | | - Remove the uaccess tag from /dev/dri/renderD*. - Change the owning group from video to render. - Change default mode to 0666. - Add an option to allow users to set the access mode for these devices at compile time.
* Merge pull request #7212 from whot/masterLennart Poettering2017-10-301-0/+1
|\ | | | | hwdb: add a hwdb for custom ID_INPUT_* overrides
| * hwdb: add a hwdb file to override ID_INPUT assignmentsPeter Hutterer2017-10-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | The input_id builtin assigns the various ID_INPUT based on the exported evdev bits. In some cases, the device may not have the properties required to label a device as one specific type but the physical form factor is clear. e.g. in the case of #7197 it's a tablet pad that does not have x/y axes which the kernel exports for pads for historical reasons. A custom override is needed, best to be solved with a hwdb entry. Related #7197
* | rules: add Freescale IMX serial ports name to serial port udev rule (#7203)Maciej S. Szmigiero2017-10-301-1/+1
|/ | | | | Freescale IMX SoCs serial ports driven by kernel "imx-uart" driver have names of "ttymxcN", let's add this pattern to an udev rule for serial ports so they will have proper ownership applied.
* rules: Add MODEL_ID for NVMe device (#7037)gwendalcr2017-10-101-2/+6
| | | | | | | | | | | | To mimic MODEL_ID variable built for ATA and SCSI devices, add rules to add MODEL_ID variable for NVMe devices. TEST: Check on a system with NVMe device that MODEL_ID variable is present: udevadm info --query=all -n /dev/nvme0n1p1 | grep ID_MODEL and udevadm info --query=all -n /dev/nvme0n1p1 | grep ID_MODEL return: E: ID_MODEL=SAMSUNG...
* fix path in btrfs rule (#6844)Christian Hesse2017-09-151-1/+1
| | | | | Commit 0e8856d2 (assemble multidevice btrfs volumes without external tools (#6607)) introduced a call to udevadm. That lives in @rootbindir@, not @rootlibexecdir@. So fix the path.
* rules: ubi mtd - add link to named partitions (#6750)Michael Grzeschik2017-09-141-0/+3
| | | | | | [zjs: - rebase onto recent master - drop signed-off-by]
* rules: load drivers only on "add" eventsDmitry Torokhov2017-09-111-1/+1
| | | | | | | | | | Previously we were loading kernel modules on all device events save for "remove". With the introduction of KOBJ_BIND/KOBJ_UNBIND this causes issues, as driver modules that have devices bound to their drivers get immediately reloaded, and it appears to the user that module unloading does not work. Let's change the rules to only load modules on "add" events instead.
* assemble multidevice btrfs volumes without external tools (#6607)g0tar2017-09-072-1/+4
| | | | | | | | assemble multidevice btrfs volumes without external tools This self-contained approach introduce very little overhead, unless someone has a large number of devices composing many btrfs volumes, in which case btrfs device scan would be faster. Still, having robust implementation is a nice to have alternative for btrfs-progs.
* rules: split the rfkill subsystem rule (#6556)Xiang Fan2017-08-081-1/+2
| | | | | | This patch makes sure both rules are applied to rfkill devices. Otherwise the ENV rule may be skipped if path_id fails. Fixes: #6528
* build-sys: drop gitignore patterns for in-tree buildsZbigniew Jędrzejewski-Szmek2017-07-181-2/+0
| | | | ... and other autotools-generated files.
* build-sys: drop automake supportZbigniew Jędrzejewski-Szmek2017-07-181-1/+0
| | | | | v2: - also mention m4
* build-sys: install udev rule 70-joystick.{rules,hwdb} (#6363)Christian Hesse2017-07-141-0/+1
| | | | | * meson: install udev files 70-joystick.{rules,hwdb} * Makefile: install udev file 70-joystick.hwdb
* build-sys: fix installation of new 60-input-id.rulesZbigniew Jędrzejewski-Szmek2017-06-281-0/+1
| | | | Fixup for 38887d1bd5eb037a532279b2b75d6a87ce381419.
* rules: move input_id rule to a separate fileMichal Suchanek2017-06-273-2/+8
| | | | | | | | | This places the input_id call after the evdev hwdb calls. With this the hwdb fixups in evdev can affect the device capabilities assigned in input_id. Remove the ID_INPUT_KEY dependency in atkbd rule because it is now not assigned at this point.
* hwdb: Add ID_INPUT_JOYSTICK_INTEGRATION property (#5413)hadess2017-06-261-0/+12
| | | | | | | | When the joystick is integrated directly into the machine, knowing that the device is internal allows us to disable attached functionality when the device is not used or inaccessible. For example, this allows disabling rumble and accelerometer on flip-console-like devices like the GPD-XD.
* 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: Handle MMC boot partitions by-path correctly (#6026)George McCollister2017-05-261-1/+2
| | | | | | | | | | | | | | | | | | | | | | Many eMMC devices have separate boot partitions that aren't part of the normal partition table that show up as /dev/mmcblk[0-9]boot[0-9]. These partitions are generally small (128KB to 16MB) and typically hold a boot loader, boot loader data or a recovery image. Match these and create -boot%n by-path symlinks. Prior to this change by-path symlinks for the main device would be incorrectly linked to one of the boot partitions. For instance before: /dev/disk/by-path/platform-219c000.usdhc linked to /dev/mmcblk1boot1 Now: /dev/disk/by-path/platform-219c000.usdhc links to /dev/mmcblk1 /dev/disk/by-path/platform-219c000.usdhc-boot0 links to /dev/mmcblk1boot0 /dev/disk/by-path/platform-219c000.usdhc-boot1 links to /dev/mmcblk1boot1 On systems that support multiple SD/MMC devices it can be essential to have by-path links to these devices since device names vary depending on which other devices are connected.
* 50-udev-default.rules.in: set correct group for mediaX/cecX (#5921)Lennart Poettering2017-05-091-0/+2
| | | | | | | | | | | The /dev/mediaX and /dev/cecX devices belong to the video group. Add two default rules for that. The /dev/cecX devices were introduced in kernel 4.8 in staging and moved out of staging in 4.10. These devices support the HDMI CEC bus. The /dev/mediaX devices are much older, but because they are not used very frequently nobody got around to adding this rule to systemd. They let the user control complex media pipelines.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-29 21:58:54 +0100