> I consider 'abuse' for example a kernel derivative with a 'modified'
> scheduler. The day it will be possible to put a binary-only sched.o into
> the kernel i'll stop doing Linux. I am not here to develop some 'lite'
> version of the OS, where all the interesting stuff happens behind closed
> doors. I'm not here either to see the quality of the OS degrade due to
> sloppy programming in widely used binary-only modules, without being able
> to fix it.
Absolutely agreed. I've already seen it happen a few times that
a user needed _2_ binary-only modules, modules which weren't even
available for the same kernel version.
As it stands right now it is IMPOSSIBLE to support binary only
drivers and I can only see two ways out of this situation:
(1) don't allow binary only modules at all
(2) have a stable ABI for binary only modules and don't allow
these binary only modules to use other symbols, so people
in need of binary only modules won't be locked to one
particular version of the kernel (or have two binary only
modules locked to _different_ versions of the kernel)
kind regards,
Rik
-- Bravely reimplemented by the knights who say "NIH".http://www.surriel.com/ http://distro.conectiva.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/