I'm in the process of sending patches. I'll cc you on the actual postings.
CUSE creates actual devices but those devices are all cuse class
devices. To play nicely with sysfs/hal, the ADD/REMOVE uevents should
have about the same variables as the actual device including the
SUBSYSTEM, so that's where the overriding comes in. CUSE client tells
CUSE that it needs to set such such envs for uevents and CUSE overrides
uevents before sending it out so that sysfs/hal can be fooled.
Thanks.
--
tejun
--