[lkml]   [2005]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why don't we separate menuconfig from the kernel?
Matthias Andree <> 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-09-19 18:31    [W:0.069 / U:2.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site