The sysfsutils bugs #562939 and #473413 are sort of similar, both
involve what sysfs should do upon particular dynamic (not at boot) events.
I think this is maybe something better handled by udev? It already knows
how to do things by matching keys in sysfs. But I don't know about
modifying sysfs attribs triggered by udev events.
I guess an argument could be made that sysfs is at a lower level than
udev and that maybe a better analogy is modprobe. But modprobe is a
userspace utility that loads the module and can check for module
parameters before doing so. In the sysfs case we're expecting that once
a new /sys/ interface shows up, if there exist things in
/etc/sysfs.{conf,d/*} that match it should apply them? I'm not sure how
that should be implemented.
--
Matt Taggart
m...@lackof.org
