RFD: Rework/extending functionality of mdev

[Harald Becker]

On 16.03.2015 09:19, Natanael Copa wrote:
> I am only aware of reading kernel events from netlink or kernel hotplug
> helper.

Where as I'm trying to create a modular system, which allows *you* to 
setup a netlink usage, *the next* to setup hotplug helper usage (still 
with speed improvement, not old behavior), and ...

> What is this new, third plug mechanism? I think that is the piece I am
> missing to understand why fifo manager approach would be superior.

... the *ability* to setup a system, with a different plug mechanism, 
not yet mentioned, using same modular system. Just putting together the 
functional blocks, the system maintainer decides.

Think of, for simplicity, about doing the event gathering from sys file 
system with some shell script code, then forward the device event 
message to rest of system. Looks ugly? What about older or small systems 
without hotplug feature?

My intention is *not* to *solve your needs*, it is to give *you* the 
*tools to build* the system with *your intended functionality*, by 
putting together some commands or command parameters, without writing 
code (programs). At the only expense of some (possibly) dead code in the 
binary. Where dead code means, dead for you, but be used by others who 
want to setup there system in a different way (build your own BB version 
and opt out, if you dislike).