> Breaking the device drivers, protocol stacks, disk drivers, file
> systems, etc. out of the kernel proper and forcing them to always be
> loadable modules would achieve this end with the added benefit of
> allowing folks to plug in their own optimized binary versions -- Like
It breaks if you distribute them seperately. We have this problem in the way
the model works. It suprised me until I understood what is going on
I claim:
Free software development is about minimising information exchange and knowledge
of external modules.
The practical upshot of this is we generate a fair amount of duplicated code.
Worse because of the 'minimising information exchange' aspect most developers
do not aggressively track the modules they initially took their skeleton code
from - thus we get bug replication.
One thing I have to do with many bug fixes is to grep the tree to see who
else copied the bug. That needs a single tree.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:17 EST