>> How about partition detection? When initramfs goes in that's one of the
>> things they're threatening to move to userspace. Also lots of the hardware
>> detection and setup (ACPI, hotplug style PCI probing...)
...
> It ought not be any more tightly bound than regular libc. Isn't that the
> point? If it still depends on non-generic services in the kernel, then we
> haven't succeeded in pulling it all the way into userspace.
Klibc is a neat hack, but makes little sense. In the end we wind up
with _more_ code to maintain, not less. The boot process becomes
more complicated too. A microkernel by any other name still smells. :-)
Not all of us have 2 GHz boxes BTW.
Moving partition code out of the kernel is just begging for bugs
and limited functionality. The EVMS people have the right idea.
Does anyone else remember the user-space isapnp disaster? I do.
Users everywhere were screaming "my sound card won't work".
-
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/