Deva, as library

[markus kaarn]

From what i've seen on here (address@hidden), there was suggestion
to treat/implement Deva as a library. What i can say here - this is not 
serious.
Because, even what comes from "Porting Hurd to L4" document by Marcus 
Brinkmann Figure 8.1,
the Deva is interface between _all-drivers-space_(PLMs), and the rest of 
the system.
So, if you want to implement Deva as library, this means one can access 
this "all-drivers-space"
directly, even without using libDeva by writing algorithms in its own code.
If you think of Deva as of a library, not some system service, then Deva 
lost it's point here.
Think if we have few Plugin Managers, and i start my program, which uses 
some device.
How can i find device i need? How can i at least find these Plugin Managers?
If you want Deva to be a library, then i can put "My-Code" name in place 
of "Deva"
to Figure 8.1.

What i think, there should be some centralization. Where all 
driver-resources registered and
managed.

p.s wasn't from beginning Deva was supposed to be a server?

Thanks,
Markus