Re: Why don't we separate menuconfig from the kernel?

[Krzysztof Halasa]

Matthias Andree <matthias.andree@xxxxxx> writes:

> One of Linux's main problems is that all daemons that drive kernel core
> functionality are cluttered over various separate projects. While this
> allows for independent development, it's annoying if you need to hunt
> down the various daemons (udev, autofs, hotplug, iproute, to name the
> first that come to mind) only to find out the new version doesn't suit
> your distro. I'd rather wish there was a standard kernel "daemons"
> package.

Who would select what is a standard kernel daemon and what is not?
Who would maintain the package?

> Why should other projects that recycle kernel code impact how the kernel
> itself is made.

It's NOT kernel code.
-- 
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/