Adrian Bunk wrote:
> On Sat, May 20, 2006 at 07:33:08AM +0300, Al Boldi wrote:
> > Not that I would agree with the in-Kernel X idea per se, but it does
> > raise the issue of a stable API once more, as it would allow more
> > freedom to create a module against a version line w/o fear of being
> > rejected.
>
> It does not raise the issue of a stable kernel API:
>
> The solution is to work on getting the module included into the kernel.
> All problems with changing kernel APIs vanish as soon as your module is
> included. This is independent from what the module in question is doing.
Yes, but the question is:
What's the trick to get the module into the kernel?
It seems that we are currently under the mercy of the few, who have the power
to control this. And forking isn't really a solution.
With a stable API, I can just implement whatever w/o caring whether it is
included into the kernel. Now that's freedom!
Thanks!
--
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
