Or hang on, this is just for what the killswitch _can_ control. I don't actually have any adapter:
$ udevadm trigger --verbose --dry-run --subsystem-match=bluetooth $
If I plug in my usb bluetooth dongle, your command adds a new one:
Device Name: hci0 Type: bluetooth
and now udev also knows about it:
$ udevadm trigger --verbose --dry-run --subsystem-match=bluetooth /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8.2/1-8.2:1.0/bluetooth/hci0 $
Or hang on, this is just for what the killswitch _can_ control. I don't actually have any adapter:
$ udevadm trigger --verbose --dry-run --subsystem- match=bluetooth
$
If I plug in my usb bluetooth dongle, your command adds a new one:
Device
Name: hci0
Type: bluetooth
and now udev also knows about it:
$ udevadm trigger --verbose --dry-run --subsystem- match=bluetooth pci0000: 00/0000: 00:1d.7/ usb1/1- 8/1-8.2/ 1-8.2:1. 0/bluetooth/ hci0
/sys/devices/
$