[...]
> > Just that an errant libXwhatever can't screw up your disks, a broken module
> > certainly can; you are running a _much_ higher risk with modules.
> It won't screw up your disks unless it locks the hardware or
> chain-oopses the kernel.
No, it just needs a wild pointer and some (bad) luck to trample all over
the structures VFS keeps in memory.
[...]
> > Just look at the Changes file in
> > your nearest kernel source, and ask yourself why you have to run those
> > library and program versions... the flamewars about kernel interface
> > changes have been memorable.
> That is because of this dependency web libc generates - see above.
Exactly! An if you want to change the kernel, and have userpsace see the
changes, you have to change libc. And you also want to change libc to make
it more standard conformant/less buggy. And as everybody depends on that,
you _have_ to change stuff. Tough, no way around it.
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- 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.altern.org/andrebalsa/doc/lkml-faq.html