3) interface files between user space and kernel space.
These files translate between user space names and kernel names. Kernel
space exports names to this interface. User space imports names from
this interface. The interface does fixups and translations, nothing
else.
That seems to me at least to make the "problem" the business of
something distinct, as opposed to the present situation, in which two
sets of developers blame each other for the difficulties of making
changes.
"A month of sundays ago David S. Miller wrote:"
> Now here is the set of crutches most people bitch about as a result of
> this, via an example. What do I do when I wish to add a new routing
> flag to provide some new facility in the networking? Or even better,
> what if I add a new protocol stack to the kernel, how do I go about
> getting the interfaces into the userland compiler's header file
> scope? For these cases, do I:
>
> 1) Maintain headers locally in my userland tools.
> Result: Bad, same piece of information maintained in two places.
>
> or
>
> 2) Propagate the interfaces into glibc
> Result: Bad, the delay is far too long and most people don't
> ever upgrade glibc let alone "often".
>
> David S. Miller
> davem@dm.cobaltmicro.com
Peter ptb@it.uc3m.es
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu