Adding rules to udev: easy or a consenus best practice

x7c2d · June 17, 2026, 2:12pm

One neat bit from that thread is TLATER’s solution includes a check to verify the custom rule:

Add custom udev rule without using "99-local.rules"

{ pkgs, lib, ... }: {
  services.udev.packages = [
    (pkgs.writeTextFile {
      name = "91-opentabletdrive-adds.rules";
      text = ''
        KERNEL=="hidraw*", ATTRS{idVendor}=="256c", ATTRS{idProduct}=="0067", TAG+="uaccess", TAG+="udev-acl"
        SUBSYSTEM=="usb", ATTRS{idVendor}=="256c", ATTRS{idProduct}=="0067", TAG+="uaccess", TAG+="udev-acl"
      '';
      destination = "/lib/udev/rules.d/91-opentabletdrive-adds.rules";

      checkPhase = ''
        ${lib.getExe' pkgs.systemd "udevadm"} verify $out/lib/udev/rules.d/91-opentabletdrive-adds.rules
      '';
     })
  ];
}

I’d like some built-in module options to define custom udev rules too. I quite like the interface that rnhmjoj suggested so setting the priority isn’t essential (assuming there would be a sensible default) but can be easily adjusted.