summaryrefslogtreecommitdiff
path: root/src/udev/udevadm-trigger.c
diff options
context:
space:
mode:
authorKay Sievers <kay@vrfy.org>2014-07-15 17:35:53 +0200
committerKay Sievers <kay@vrfy.org>2014-07-15 17:35:53 +0200
commit30632d97d9d68c8202e562f34afae8f8d6e9c377 (patch)
tree6d281c9abc7261a82bc095206765873b9cea8b40 /src/udev/udevadm-trigger.c
parent285cd771cbe275265e165bdb5650b92b31eeab47 (diff)
rules: uaccess - add ID_SOFTWARE_RADIO
On Tue, Jul 15, 2014 at 1:52 PM, Alick Zhao <alick9188@gmail.com> wrote: >>> >>> So maybe ID_SOFTWARE_RADIO ? >> >> Hmm, SDR is more a term for a generic technology than for a device >> class. To me it does not really sound like an administrator would know >> what this is. >> >> What exactly is the device or subsystem you want to make accessible to >> locally logged-in users only? > > Initially it is bladeRF, but many more are of interest: USRP, rtl-sdr, > HackRF, ... [1] > > I agree an administrator might not know what SDR is, since it is > currently still not widely known, and makes sense only for amateurs > and researchers. But as a SDR fan, I see many new SDR peripherals > are created recently, and expect to see more. So a generic ID seems > reasonable to me. > > [1] http://en.wikipedia.org/wiki/List_of_software-defined_radios
Diffstat (limited to 'src/udev/udevadm-trigger.c')
0 files changed, 0 insertions, 0 deletions