; Alan Stern
I agree with you on this. The device_add and device_del functions
use notification chains
similar to how the USB subsystem can notify subscribers that new
devices have been added.
This was my initial implementation, USB already uses notification
chains for its device add/remove.
Th
ice add/remove audit (not log messages)
are being generated/implemented in the kernel or userspace for the
scenario I described?
Thanks,
Wade Mealing
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More ma
638): item=0
name=2F746D702FEAB68CEC84B1ECA3BC2E747874 inode=627534 dev=fd:00
mode=0100664 ouid=1000 ogid=1000 rdev=00:00
obj=unconfined_u:object_r:user_tmp_t:s0 objtype=NORMAL
Thanks,
Wade Mealing.
On Tue, Apr 5, 2016 at 11:51 AM, Wade Mealing wrote:
> That is a good question, maybe I've
deal place to log those
events also.
If (1) can entirely be done in systemd/udev with kobjects that is cool, I just
didn't think it could, especially for every subsystem type, and especially
before systemd starts.
Thanks,
Wade Mealing
--
To unsubscribe from this list: send the line "uns
this area.
Would this be considered the sane way to do it, and do you see any issues with
this ?
Thanks in advance,
Wade Mealing
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at ht
